On 2/13/2013 2:58 PM, Buck Golemon wrote:
> On Wed, Feb 13, 2013 at 2:30 PM, Asmus Freytag <asmusf_at_ix.netcom.com> wrote:
>
>> On 2/13/2013 1:24 PM, Stephan Stiller wrote:
>>
>>> It looks like something that has not been encoded.
>>> What is the reason for not having a true "combining grapheme joiner", one
>>> that overlays graphemes? Or a code point that instructs that the preceding
>>> (or following, I guess) code point should be printed at this position but
>>> otherwise be treated as having zero width?
>>>
>>>
>> The reason is that Unicode is not a text layout language.
>>
>> A./
>>
>>
> That addresses his second quesiton, but not the first.
Actually --- not. It is intended to address the entire quoted section.
>
> A grapheme combining character would only be usable if a normalized
> combined character was also defined, and the mapping between the combined characters and the un-combined characters with combiner.
Where do you get that?
> In other words adding such a thing wouldn't solve the problem you've posed (adding a combined sj character) since combining characters are (as I understand it) intended to be ephemeral and only fully combined characters are inteneded for communications.
That understanding of combining characters does not seem to be backed up
by anything in the standard.
A./
>
Received on Wed Feb 13 2013 - 17:51:40 CST
This archive was generated by hypermail 2.2.0 : Wed Feb 13 2013 - 17:51:47 CST