Nathaniel Hourt

I'm guessing this is due to the use of char\* and std::string in fc's filesystem.cpp in the home_path() and app_path() functions. I imagine the fix would be to use wchar_t\*...

Between https://github.com/BitShares/qt_wallet/commit/21748f00564775478522c609884cc75f5f4fa234 and https://github.com/InvictusInnovations/fc/commit/6cddd42cfe5a86ab8e339728bec1aeb07506750f this should be resolved. Can you still reproduce the issue (with BitShares XT, not BitShares X)

Assuming this is resolved unless we hear otherwise.

Resolved: https://github.com/BitShares/qt_wallet/commit/deff9ef0cccb072255e8edf5f70d77c89136218c

Is this still happening? Have you tried it with a fresh data dir?

Right, I understand, but I've had an issue before where logs weren't being generated correctly because my config.json was generated by an outdated client.

If you specify a data dir with non-ASCII characters, it works?

@theoreticalbts That's an interesting find. If both Qt and FC are initializing OpenSSL, we may have problems. Most likely this is caused by using https to fetch the manifest. If...

This is planned, but not yet implemented. We definitely want to have this feature.

I am not aware of a way a website can register itself to handle certain URL schemes, though I imagine browser plugins could do this. It's also very possible that...