Re: Segmentation fault in dcigettext.c:925 using Apache + PHP

[Wiebe Cazemier]

----- Original Message -----
> From: "Bruno Haible" <bruno@clisp.org>
> To: "Wiebe Cazemier" <wiebe@halfgaar.net>
> Cc: bug-gettext@gnu.org
> Sent: Thursday, 25 June, 2020 13:05:40
> Subject: Re: Segmentation fault in dcigettext.c:925 using Apache + PHP
>
> Wiebe Cazemier wrote:
>> I was (quietly) also wondering if msgfmt would do better creating a new file
>> instead of truncating the existing one. But, looking at search results, we 
>> are
>> the only ones who have this problem, so probably creating .mo files 
>> frequently,
>> based on user interaction, is a uncommon use case.
> 
> You mean, you create the file $LOCALEDIR/$locale/LC_MESSAGES/$domain.mo
> directly by invoking 'msgfmt', not involving an intermediate file?
> That is indeed uncommon, because in theory it's possible that msgfmt fails
> (due to an unsupported combination of the input and options), and then you
> would overwrite the previous .mo file and not have a backup.

To be more precise: using .mo files for website translations where the 
translations are actively edited through the CMS. Others implementing a similar 
technique are bound to repeat the same mistake, and overwrite the existing .mo 
file with msgfmt. But, the lack of people having issues like this, suggests few 
people do. And if they do, now they will find this post :)


> 
> The typical way is that .mo files are created while building a package
> and copied to $LOCALEDIR/$locale/LC_MESSAGES/$domain.mo by installing the
> built package.

With a website CMS, that's hard to do, naturally.