Richard Heck wrote:
> On 04/09/2016 11:36 AM, Uwe Stöhr wrote:
>> Am 07.04.2016 um 23:37 schrieb Richard Heck:
>>
>>> Then maybe the solution is to disable the writing of native line
>>> endings. Apparently, we can do this by opening the output files in
>>> binary mode. The attached patch does
Richard Heck wrote:
> No, it's bad. I'm faikrly sure there should be almost no difference
> between the files if it is working correctly. Something has happend
> involving this sort of thing:
>
> -#: src/frontends/qt4/ui/WrapUi.ui:173 src/frontends/qt4/GuiParagraph.cpp:163
> +#:
On 04/09/2016 11:36 AM, Uwe Stöhr wrote:
> Am 07.04.2016 um 23:37 schrieb Richard Heck:
>
>> Then maybe the solution is to disable the writing of native line
>> endings. Apparently, we can do this by opening the output files in
>> binary mode. The attached patch does this. Can someone test?
>
>
Richard Heck wrote:
> The attached patch does this. Can someone test?
More precisely, Uwe could you remerge strings using this patch on clean master
and give us single sample .po file so we can check it is identical when we
remerge it on linux machines?
Pavel
On 04/07/2016 05:21 PM, Pavel Sanda wrote:
> Richard Heck wrote:
>> I think the problem may not be that gettext works differently but,
>> perhaps, that it works the same. I am guessing that what happens is this.
>> First, lyx_pot.py writes the po files with native line endings.
> Yep, that might
