Christian,

This is a conscious decision as many Asian languages, when the UI 
point size is small, prefer to switch text attributes such as this 
off. This is therefore the easiest place to do it on "by message" 
string basis. It shouldn't interfere excessively with any TM.

thanks much
Andrew

At 0:54 +0200 30/8/04, Christian Rose wrote:
>Sadly, the player localization file seems to include many messages
>unnecessaringly including surrounding markup. Surrounding markup is
>markup of the type "<b>This whole message is bold.</b>".
>
>Surrounding markup in the translateable messages adds no information of
>value for translators, and makes it so much more difficult to
>successfully use a translation memory for producing a translation. The
>solution for the problem is for programmers to move the surrounding
>markup outside of the gettext calls.
>
>I've added a bug report for this at
>https://bugs.helixcommunity.org/show_bug.cgi?id=2989.
>
>It would probably be useful if some recommendation to *not* include
>surrounding markup inside translatable messages was added to Helix
>Project coding guidelines, if such exist.
>
>
>Christian
>
>
>_______________________________________________
>Player-l10n mailing list
>Player-l10n at lists.helixcommunity.org
>http://lists.helixcommunity.org/mailman/listinfo/player-l10n


--