Re: [Fvwm-crystal-users] fvwm translation bug

[Alwin <tra...@zi...>]

That looks fine to me. Although < and > have a special meaning in shell 
script, I don't think that's the case within quoted strings like "$[gt. 
... ]".


Dominique Michel schreef:
> I replaced the "'" by U+2019 into the existing locales everywhere but
> not in constructs like "\\'path\\'".
>
> For these constructs, I think it could be best to change them to
> "<path>", and that including into the original English. What do you
> think?
>
> Cheers,
> Dominique
>
> Le Sun, 17 Nov 2019 12:13:17 +0100,
> Alwin<tra...@zi...>  a écrit :
>
>> Hi Dominique,
>>
>> I think you're right, and counting how much escape characters would
>> be needed in every single translation string is too much of a burden.
>>
>> It seems that FVWM does the gettext conversion before execution of
>> the scripting task. Using the Unicode apostrophe U+2019
>> unbackslashed, works under a UTF-8 locale, and it's looking nice. But
>> under another character set (8859-1 family) it's replaced again by
>> the ASCII apostrophe which is also used by the script, so it ruins
>> the menu. Maybe FVWM-Crystal should declare using translations not
>> using UTF-8 broken for the time being, and use the Unicode apostrophe
>> for now.
>>
>> The real solution would probably be, that FVWM doesn't take the 'gt.'
>> string for gettext into account for the scripting part.
>>
>>
>> Cheers,
>>
>>
>> Dominique Michel schreef:
>>> I found a bug when making the French translation. If your language
>>> contain the apostrophe "'", to have it into a menu translated
>>> string, will screw up the corresponding menu entry and associated
>>> function. That imply not only the displayed string can and will be
>>> wrong, but that menu entry will not work at all. To escape the "'"
>>> into the translation doesn't help, or help randomly in a few cases.
>>>
>>> The same string into a FvwmForm will work fine. I reported this to
>>> the Fvwm workers list, but get no answer at that time. The only
>>> workaround I find is to not use "'" into translated menu strings,
>>> and when not possible, to replace "'" by something like "_" or " ".
>>> I think it will be the same issue with other characters used by
>>> fvwm as quoting characters, and I rally hope they will be the only
>>> ones causing that issue.
>>>
>>> Thanks for your time.
>>> Dominique


-- 
[alwin]