Re: The translator credits



François Pinard <pinard iro umontreal ca> writes:

> Otherwise, I guess it would be rather sensible that one relies on the
> MIME headers in the PO file header for the whole file, including the
> value fields in the header itself.

This will confuse things.  As long as the header lines are looking like
mail message header lines we should treat them as such, please.

> We would need more proper documentation for it, especially since a
> format revision is being discussed, from time to time.

This would help a lot.

> To get proper input and feedback, we need to well explain where we
> are, and where we go.  Some people volunteered to produce drafts to
> work on, we should revive this project :-).

Are these drafts available (maybe, as mail folders from your site?);
since we at SuSE starting to use the PO file for more than just
translating C programs I'd like to help to find somebody (one of my
co-workers) who has the skills to document the PO file format.

> MIME encoding would help inter-operability with other MIME tools.  I'm not
> sure how PO files are being used in practice, enough to have a strong
> opinion about it.  So var, a PO file is not a MIME multi-part construction,
> and there is probably no strong need to have the PO file header having a
> neutral encoding like for MIME messages: I would be tempted to say that
> we could assume, by default, and for simplicity, that the PO file header
> use the same encoding as for the remainder of the file.

>From time to time I like to query a MO file to see who was the last
translator.  In an 8859-1 environment this work pretty well.  But you'll
start to see wierd result if you're working in an 8859-2 environment.
Please try:

    xterm -fn '-*-*-medium-r-*-*-*-*-*-*-*-*-iso8859-2'

and inside the new xterm call:

    LC_MESSAGES=pt gettext fileutils "" | grep Last-Translator

And you'll see that "João" is displayed wrongly as 
`Joăo'.

-- 
work : ke suse de                          |          ------    ,__o
     : http://www.suse.de/~ke/             |         ------   _-\_<,
home : keichwa gmx net                     |        ------   (*)/'(*)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]