Re: [PATCH] iconv.3: Clarify the behavior when input is untranslatable

Alejandro Colomar
2023-05-21T20:57:54Z

[-- Attachment #1.1: Type: text/plain, Size: 1611 bytes --]

Hi Bruno,

On 5/21/23 21:37, Bruno Haible wrote:
> Hi Alejandro,
>
>> Please use semantic newlines. See man-pages(7):
>
> Thanks for explaining. I wondered whether I should use one space or two spaces
> after the end of a sentence, but found no precedent for either style. This
> explains it :)
>
>>> +In the GNU C library and GNU libiconv, if
>>> +.I cd
>>> +was created without the suffix
>>> +.B //TRANSLIT
>>> +or
>>> +.BR //IGNORE ,
>>> +the conversion is strict: lossy conversions produce this condition.
>>> +If the suffix
>>> +.B //TRANSLIT
>>> +was specified, transliteration can avoid this condition in some cases.
>>
>> What do you mean by "can" and "some cases"?
>
> GNU libc and GNU libiconv support transliteration, for example, of "½" to "1/2",
> or of "å" to "aa" in a Danish locale. Here I want to give a hint at the
> transliteration facility, but without going into too much detail.
> "transliteration can avoid this condition if there is a transliteration rule
> for the multibyte character and it fits the character encoding of the output"
> is too detailed, IMO.
> Do you have a better wording than "can ... in some cases"?

If you include the full version in the commit log, to be able to
understand it in the future, I'm fine with it.

>
>> I recommend either using \[aq]*\[aq] for producing valid C code,
>> or just having an unquoted *.
>
> I made the requested style changes.

Thanks,
Alex

>
> New patch is attached.