On Mon, Sep 11, 2006 at 05:01:24PM +0200, Lars Gullik Bjønnes wrote: > Helge Hafting <[EMAIL PROTECTED]> writes: > > | Lars Gullik Bjønnes wrote: > | > Abdelrazak Younes <[EMAIL PROTECTED]> writes: > | > > | > | But what if I want to translate some unicode (usc4) string? That's the > | > | case in a couple of place in the code and that's the reason I added > | > | this method. > | > > | > That is just not allowed. Msgid is only allowed to be pure ascii, so > | > we should not pretend that anything else is allowed either. > | > > | What a limitation! > | So, translations must always be from english then? > > No, but ascii. > Sure, but english is one of very few languages that does fine with ascii only. Almost anything else wants a few extra characters, or some accent and umlauts.
> | Not > | an issue in lyx, but generally. And menus entries and > | such can't use "nice quotes", the language dialog > | has to have the ugly <<text>> construct instead of > | real guillemets? > > Correct. If you want f.ex. real guillemets in english, you create a > .po file for english that contain the correct "translation". Smart trick. By the way, what will happen to LyX .po files? Will they now move to UTF-8, or perhaps some other unicode encoding? (I mean the translated strings, obviously.) Helge Hafting
