RE: Why people still want to encode precomposed letters

From: philip chastney (
Date: Sun Nov 23 2008 - 05:37:06 CST

  • Next message: philip chastney: "Re: Why people still want to encode precomposed letters"

    there would indeed be no end to it, but if the spec were restricted to known combinations found in natural languages with alphabetic orthographies, the list needn't be that long
    this list could encompass ligatures as well as characters with diacritical markings, and include ligatures with diacritical markings  --  maybe not three tied characters, though, unless it was clear that they were few in number  --  and probably not vowel shaping
    such a list would be an asset to font designers
    and it would help re-assure users of minority languages that their needs are known, and will (eventually) be met
's website would be suitable repository
    apparently the list cannot be named "namedsequences.txt"  --  OK, how about "knowncombinationsfoundinnaturallanguageswithalphabeticorthographies.txt"?
    unless, of course, someone has a better suggestion   . . .   /phil

    --- On Sun, 23/11/08, Peter Constable <> wrote:

    From: Peter Constable <>
    Subject: RE: Why people still want to encode precomposed letters
    To: "Andrew West" <>, "unicode Unicode Discussion" <>
    Date: Sunday, 23 November, 2008, 3:31 AM

    That is *not* the intended purpose for namedsequences.txt. I don't think it
    would be a good idea to start filling it with combining mark sequences --
    there'd be no end to that.


    -----Original Message-----
    From: [] On Behalf
    Of Andrew West
    Sent: Tuesday, November 18, 2008 1:34 AM
    To: unicode Unicode Discussion
    Subject: Re: Why people still want to encode precomposed letters

    2008/11/17 <>:
    >>> The combinations of base character and combining diacritic(s)
    >>> is a decision of the font developers. No font will support all
    >>> combinations, maybe ot even most. What they will try to do is add
    >>> combinations that fullfill the purpose fo the font.
    >> There is no guidance or help for font developers. So they just make
    >> in the code charts.
    > Which of course begs the question where such guidance should be kept .



    This archive was generated by hypermail 2.1.5 : Sun Nov 23 2008 - 05:40:44 CST