[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using iconv in stand-alone info
From: |
Gavin Smith |
Subject: |
Re: Using iconv in stand-alone info |
Date: |
Mon, 21 Dec 2015 20:53:40 +0000 |
On 21 December 2015 at 20:24, Eli Zaretskii <address@hidden> wrote:
> No, cp1255 doesn't have it, if I understand what you are asking. The
> problem is that some cp1255 characters are combining characters, so
> libiconv composes them with the preceding character into a single
> codepoint of the corresponding precomposed character, and only after
> that produces the UTF-8 sequence of that codepoint. So it needs to be
> told there will be no next character for it to output the last UTF-8
> sequence.
Yes, I see how that could be a problem. (I suppose with the benefit of
hindsight, it would have been better to have had the combining
character appear first.)
- Using iconv in stand-alone info, Eli Zaretskii, 2015/12/21
- Re: Using iconv in stand-alone info, Gavin Smith, 2015/12/21
- Re: Using iconv in stand-alone info, Eli Zaretskii, 2015/12/21
- Re: Using iconv in stand-alone info,
Gavin Smith <=
- Re: Using iconv in stand-alone info, Eli Zaretskii, 2015/12/23
- Re: Using iconv in stand-alone info, Gavin Smith, 2015/12/23
- Re: Using iconv in stand-alone info, Eli Zaretskii, 2015/12/23
- Re: Using iconv in stand-alone info, Eli Zaretskii, 2015/12/23
- Re: Using iconv in stand-alone info, Eli Zaretskii, 2015/12/23
- Re: Using iconv in stand-alone info, Gavin Smith, 2015/12/23
- Re: Using iconv in stand-alone info, Eli Zaretskii, 2015/12/24
- Re: Using iconv in stand-alone info, Gavin Smith, 2015/12/24
- Re: Using iconv in stand-alone info, Eli Zaretskii, 2015/12/24
- Re: Using iconv in stand-alone info, Gavin Smith, 2015/12/24