Hi,
I did have this problem. I doubt the problem is selection of characters in passwords. I managed to work-around by launching an earlier version of the software - that I have put in my Trash for safe-keeping (and don't want to launch), created on Friday 12th December 2014, 113,364,444 bytes (sorry!).
This version allowed me to import my wallet with my funny password. I then shut down, renamed that app, and installed the current version. Relaunched, re-synced and re-exported my wallet json.
The json I was trying to import, that the new software gave me Error: invalid password (20001). for, does have exactly this formatting.
[
{
"type": "master_key_record_type",
"data": {
"index": -1,
"encrypted_key": "b7fab8babebf3c18027fa498460c7a64b3d3abe211b1f6440b8b5483a6c0271b8930ecf1945a7467eae73aef1e5c6922536f89f615058293f24f79f48e6742edec249d4518b9336c993393bbc5e3f538",
"checksum": "bae28fc07bbcbc3f629de4879cd1f75fbfc660efb68ded09c191d9d85fe2890eb8905ec11090d5f8e6992fd6b5ec6c695e05a7c76780dd8478072c6831347679"
}
},
{
"type": "property_record_type",
...
Without actually describing my password, it would seem certain that there is nothing wrong with our jsons or our passwords, but there is a problem with the recent 0.6.1 import.