Before you do conversion with the source po, sometimes worthy to use
msgfmt -c parameter, to check there is any incompatibility with the
syntax, or like missing end of line, or other chars. Then is easier,
before you force through with errors. Sometimes it stops, sometimes
makes with standard headers, but without checking on the completed
source po, you can avoid nasty UI text breaking, parsing errors too.
2016-03-29 18:39 GMT+02:00 Florian H. <firstname.lastname@example.org>:
> Thanks for your quick reply, and the explanations given!
> On 29.03.2016 12:28, Zoltan Hoppar wrote:
>> Hi Florian,
>> [...] But to use these completed translation files, you have to
>> convert/compile them to binary with gettext, and that has .mo
>> extension. To see your work, you have to insert this .mo binary to
> OK, I downloaded the translation from zanata (as .po) file and tried to
> convert it to .mo in order to be able to use it.
> What I did: msgfmt file.po -o file.mo
> The error message was something that .po file is not GNU compatible. I
> gave up, and interestingly I just tried it again, and the file got
> converted. So, I think I am good for now.
> Thanks again!
>> [...] Fedora we use an complete translation system called Zanata.
>> 2016-03-29 17:42 GMT+02:00 Florian H. <email@example.com>:
>>> Dear all,
>>> I recently joined of the trans team here and was wondering where to find
>>> a good overview or guide on how translation actually works.
>>> Specifically, I am confused about the different file extensions,
>>> probably also about the file formats. When I do something in zanata, I
>>> have the possibility to download the translation as .po. In
>>> /usr/share/locale/<locale>/LC_MESSAGES/ I do find a few .mo files. And
>>> somewhere I read something about .pot.
>>> Any hint for some introduction that I obviously need to get started.
>>> trans mailing list
> trans mailing list
trans mailing list
Post a Comment