The colors have actually no effect on the logic, but this is deffinitely a bug.

Thank you for re-reporting this one, it will be fixed in the next release.

Thank you for the report, this has been fixed for the next release.

Yes, this was an attempted fix for japanese OS X problems, it will be fixed in next release.

Damn, I expected something wild... I will revert the change for the next patch, sorry for the inconvenience.

This was an attempt to fix problems with japanese Mac, it seems that I will have to revert it then. Could you send me your system usernames and languages?

This has been fixed for next release.

This will be fixed in the next release.

Thank you for the report, this has been fixed for the next release.

Thank you for the report, this has been fixed for the next release.

This has been resolved for the next release.

We already had reports of these problems, I am not entirely sure what causes this and I haven't been able to reproduce it, but since the train code has seen a lot of changes during the integration of chain signals, I hope this won't happen anymore in 0.12. I'll mark this as resolved, and if it happe...

ssilk wrote:0.12.4, because I think 6 developers can do much more than 2.

By 6 you mean 8, right?

We did some reworking and fixing for trains and signals, so although I was not able to reproduce this, I think it should be fixed for 0.12. If this still happens to you in the next version, please report it.

This information will be available in 0.12.

I forced CFStringGetCStringPtr to use kCFStringEncodingUTF8 and then told boost to use utf8_codecvt_facet to represent it properly, so that should work, if the CFString manages to convert itself to UTF-8. I unfortunately have no way of testing this and getting a Japanese OS X is no easy task, even h...