Am Montag, 9. Mai 2016 um 01:34:52, schrieb Uwe Stöhr <uwesto...@web.de> > Am 08.05.2016 um 22:36 schrieb Georg Baum: > > > 3) A translator sends a .po file with unix line ends > > 4) A translator sends a .po file with windows line ends > > The question is how can I check this? > > > For cases 1) and 3) a commit is OK, for cases 2) and 4) a commit would > > produce a huge pseudo diff. > > Why is this huge a problem? We live with this for years now. It is in my > opinion also not important to have clean diffs for languages we cannot > speak. I'll check the compilability before I commit. > > > Which choice would be more convenient for windows users? > > To commit the po-file as it is ;-). The reason is that we have usually > only one translator per language. So if e.g. the Hungarian po-file was > edited on Windows it will be in future also be modified on Windows. I > think it is more important to please the translators. If I transform hiw > Windows-edited po-file to Unix-style and he compares what I committed > with his version, he wil get huge diffs and might be confused. So > whatever is the most convenient way for te translators will get my vote. > ---------- > > Georg, why do you create a gmo-file for every commit of a po-file. Up to > now the policy was that gmo.files will be created before a release by > the release maintainer. If possible I would keep this policy because it > saves me time and creating the gmo several times is also no benefit.
The policy dates back to 2013. The reason is to distribute sources together
with .gmo files,
so that the requirement for gettext-tools is not needed to compile and use
localized lyx.
> regards Uwe
Kornel
signature.asc
Description: This is a digitally signed message part.
