bashareteam team mailing list archive

[Emilien Klein <emilien@xxxxxxxx>]

Yeah, .mo are necessary if you want to have the application
translated, because the app uses the .mo (and not the .po).
However, we can not have those .mo files in the source code repository
because they automatically get out of sync each time someone
translates or changes a string. And I think that it would be really
confusing to see that the .po file has a new translation, but that the
old translation still appears in the program. If we have something in
the repository, it must be accurate and up to date. And I am not going
to manually compile each language after each automatic import... ;)

We need to remove those .mo, and find how we can add the script into
./configure, so that it automatically compiles the translations when
you compile the program.
Because now I have doubts about the RCs that we made, how can we be
sure that the most recent .mo files were included, and not older ones?
For example, if you created a new package right now, you would have
invalid translations for the last automatic committed languages...


2009/11/12 guido iodice <guido.iodice@xxxxxxxxx>:

>well, I tried. .mo are necessary.
>
>I have not idea why it worked first... but they are necessary, definitely






2009/11/12 guido iodice <guido.iodice@xxxxxxxxx>:
>
>
> 2009/11/12 Emilien Klein <emilien@xxxxxxxx>
>>
>> Remember when you added the .mo files back into the repository (rev
>> 43)? As you explain in
>> https://lists.launchpad.net/bashareteam/msg00059.html the reason was
>> that if you got a fresh copy of BaShare from Bazaar, the program would
>> not be translated. That seems to be the case because Gambas only
>> "compiles/creates" the .mo files if you actually modify the
>> translation from within Gambas IDE...
>
> yes, but:
>
> a) it is possible that it was a old gambas ide bug OR
> b) the problem was only the absense of extra .pot files
>>
>> But I don't know if this is still a problem? Apparently, you are
>> telling me that everything worked fine without the .mo files? Did
>> Gambas automatically compile them? Did you close Gambas before
>> deleting the .mo, and then restart Gambas?
>
> well, really, extra (mo, po, pot, images, etc) files are not necessary once
> the program is compiled. Gambas make a .gambas file that include all. I
> tried to remove .mo files and Gambas IDE was in agree :) and the same
> autotools.
> I'll again downloading the branch from bazaar and trying to compile it.
>
>
> P.S.: Watch out when you say "Every one knows that 3 commands". People
>>
>> might think that you intend BaShare to be only for geeks and
>> developers... There are people that get software from version control
>> and don't know how to compile it (a good example can be
>> translators...) This is also why it is always important to describe
>> how to compile the program in a README file...
>>
>> ;)
>
>
> oh yes :) but it is described in INSTALL (this is an autotools standard
> file).
>
> But yes, README must be in English
>
>
>