You sure make round trip safe?

There are still many people out there using Carbon based application on Mac OS X for working with Unicode text. When it comes to localization business, it is critical to use Unicode based editor because the most materials you get come from Cocoa application.

When you open a Unicode file with a Carbon application, it converts the text into classic encodings, utilizing the system services that suggest which script system a particular string belongs to, and which font best suits for it. Let's assume it works okay for you now.

The problem is that there are unknown number of characters in Unicode (depending on the language you deal with) that cannot make a round-trip conversion back from Carbon. It might be very difficult for you to tell what goes wrong when you get "looks the same but doesn't match" letters.

Or maybe you would say there is no such trip without trouble...