Am 05.04.2016 um 08:46 schrieb Georg Baum:
Which strings? These might require a remerge of the other languages as
well
I remerged all po files yesterday because I noticed that e.g. the
longtable name change was not present in fr.po, de.po etc.
In pt_BR.po I saw that too but after I committed Georger's changes, I
saw that actually nothing was changed because this was already in - strange.
Concerning the layouttranslations file i cannot see a difference to the
file in today's git. Maybe Georg already included your updates.
I did that indeed, and the .po file was also already submitted. Uwe, at
some time we need to figure out why your .po file submits change the
line endings in some cases.
I don't think that this is me. I receive the different po-files from
different people using different editors. I only add them to my git
tree, check if they are compilable and then commit. In the vast majority
I commit without any change to the files. Up to now I was not aware that
there are problems with scripts. I do this for years now and Richard is
on Linux preparing there the .x releases.
This causes trouble with our python scripts
which parse them, they always have to be in unix form (\n, not \r\n).
Until we found out the reason please look at the diffe before
submitting, and if the .po file has windows line endings please change
them to unix line endings (could be done e. g. by notepad2).
But how could I check if there are the wrong line endings? Why can the
python scripts not handle both line ending types? Here the scripts can
handle also Unix line endings so it should be possible to have the
opposite on Linux too and obviously it works at least for Richard.
Richard, do you have an idea?
regards Uwe
