Re: [bug-gettext] Hardcoded escaping

Hi Serj, You have well described the issue. > we'll have to maintain slightly different strings in source code (escaped) > and in `.pot` files (unescaped), which feels kinda wrong. > ... > we will have different strings in source code and l10n files, which is > against consistency This "feels

Re: [bug-gettext] Duplicated words in gettext-runtime/m4/*.m4

Jakub Wilk writes: > There are some duplicated words in the copying permission statements > in gettext-runtime/m4/*.m4: > > ... This file can can be used ... > ... gettext package package is covered ... Thanks, fixed. Regards, -- Daiki Ueno

Re: [bug-gettext] Hardcoded escaping

Serj Lavrin writes: > There seems to be an issue with hardcoded escaping in > http://git.savannah.gnu.org/cgit/gettext.git/tree/gettext-tools/src/po-lex.c?id=b75a50bc5f30666fb36469a90245e1d7856d672c#n750 > > If I will explain an issue, is there any chances that it will be

Re: [bug-gettext] Hardcoded escaping

Serj Lavrin writes: > ``` > gettext('My magic ain\'t working string') > ``` > Not big deal — now that works. > But then comes into play `xgettext`. During extraction `xgettext` will get > string as it is — with > escaped single quote. For the record, this is not the case.