I've experienced some cases in my work that translator uses unicode character set(using UTF-8) in their translation and use 'oe' in one character as U+0153 code, but there is not corresponding character in 8859-1, Lattin-1 character set. Though, this, one character 'oe' is better for native speakers.

Of course, there are huge number of characters which 8859-1 does not have, but this is one of the good example that we need to take care at translation. If we use Unicode message file to show messages on other smaller charset locales, there would be conversion error on such locale at runtime.

I converted it to 'o' and 'e' with translator's advice in source side at that time.

投稿されたコメント:

コメント
コメントは無効になっています。

This blog copyright 2008 by kazuhiko