Angus Leeming <[EMAIL PROTECTED]> writes:

| Georg Baum wrote:
>> I just looked it up in the gettext manual, and if I understood it
>> correctly, gettext does not provide a mechanism to supply additional
>> context information. Instead, they suggest to mark ambigous strings like
>> "Menu|File|Open" and "Menu|Printer|Open" and then use a special
>> translation function that strips the part before the first "|". See
>> http://tinyurl.com/3sy5v
>
| Why not use strings "Menu|File|Open" etc and then define an "en" po
| file.

this was my thought as well.

| Jean-Marc has already established the precedent by ensuring that only
| ASCII characters are passed to the translation functions.
  ^^^
  Me, and required by gettext actually. Jean-Marc might have enforced it.

-- 
        Lgb

Reply via email to