Sencode Parse Error with importing and exporting pubkeys about codecrypt

[exaexa]

Hello,

it's actually much simpler - key import and all other data-reading operations still require --ascii switch when you try to read ascii-formatted data. Actual "missing" code (for this case) is on the beginning of this function:

https://github.com/exaexa/codecrypt/blob/master/src/actions.cpp#L1007

As this is not very userfriendly indeed, it's going to get fixed in next release; probably just with the automatical attempt to fallback to ascii. Please leave this bug open for tracking.

[liamzdenek]

In the meantime, you should update README.md to show importing with the same encoding. It is misleading to have the keys written using ASCII:

ccr -p -a -o my_pubkeys.asc -F Doe  # export your pubkeys for friends

and then imported without ASCII:

ccr -i -R friends_pubkeys.asc --name "Friendly Frank"

Edit: noticed that you just did this. Disregard me

[exaexa]

Fixed by f2d1ba9 -- it prints out helpful message, user will know what to do.

I was thinking about the possibility that codecrypt would automatically try switching to ascii/non-ascii mode on failure, but that would bring possible logic errors and a need for a switch that disables the auto-fallback, and a lot more of code only for human convenience.... No way. :D