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

Re: Bug#53981: language-chooser



On Thu, Jan 13, 2000 at 10:47:12PM +0900, Taketoshi Sano wrote:
> Then we should modify the code in dbootstrap/main.c, which currently
> stops if the specified trm file is wrong.
>
> Maybe the following one will work as a work around ?
>

[nitpicking: :) ]

    if (LOAD_TRMFILE (TRMFILE) == 0 || LOAD_TRMFILE (C_TRMFILE) == 0)

Maybe.  There is a small problem though.  Or, to be more correct, a small issue
to consider.  If we have an incomplete .trm file, it's better to give
translations where possible.  While such a construction says: if we do not have
a complete .trm file, just show everything in English.  I do not think users
will find it good to have English messages after they choose the language they
would like the system to show the messages in. :)

To resume.

>  Enrique Zanardi <ezanardi@id-agora.com> writes:
> 
>  | > The translated string is searched by its position on the trm file (not by
>  | > its non-translated counterpart as it is in gettext) so, if there's a
>  | > different number of strings on the trm file than expected, there's no way
>  | > to tell which one goes where (and usually some of them won't be there,
>  | > NULL pointer, so the segfaults). 
We do not expect to have different number of strings.  This is by design.
Look, we have a set of .c files in utilities/dbootstrap directory.  We build
utilities/dbootstrap/po/dbootstrap.pot file (which is the source for C.po)
file.  Now it's easy to update all translations.  Yes, the resulted translation
may have certain items marked as "fuzzy", and certain items just are not
translated.  BUT the number of messages is exactly the same.  And all these
.trm files are generated at once.  I believe we are not going to separately
supply trose .trm files, which simplifies the situation a lot.

> I think that loading both files may not work in the current .trm structure.
> We have to change the procedure to generate .trm files to include English 
> messages if the translated messages are not available.
Exactly.

> It may be possible to use C.po and LANG.po to generate .trm files.
It does not matter (if I understand correctly) what to use: .mo file or .po
file as the former is just a compiled (read: not that wordy) of the latter.

--
Mike


Reply to: