Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Peter Constable


Peter Constable
Last Active
  • Re: [OTVar] Axes Proposals:

    [A bit meta:

    We have no formal process in place for registering new axes in the new OT Design-Variation Axis Tag Registry. ...
    The goal you describe, of avoiding dead, redundant or inconsistently-implemented axes, is a goal I share. As for process, my first step was to get the OT spec into a form better amenable to that. I need to work on the next step. In the meantime, getting some discussion of potential axes is helpful, I think: a process will need some group of interested and informed contributors.
  • Re: [OT] Any way to select line breaks?

    OpenType lookups cannot be sensitive to line or paragraph boundaries since there are no glyphs that correspond to these. At best, lookups can recognize the ends of runs (by the absence of any glyph), though note that runs can be affected by several things, including line breaks, bidi, styling, and script itemization. If you want an effect at the beginning or end of a paragraph, then the only way to do that would be to have a feature applied to the first or last glyph/character/cluster of the paragraph.
  • Re: Egyptian Hieroglyphs

    Booo! Unicode supplementary-plane characters have been around since Unicode 3.1 -- published over 16 years ago!
  • Re: [OTSpec] Use of term "Character"


    "Function: To minimize the number of glyph alternates, it is sometimes desirable to decompose the default glyph for a character into two or more glyphs. Additionally, it may be preferable to compose default glyphs for two or more characters into a single glyph for better glyph processing. This feature permits such composition/decompostion. The feature should be processed as the first feature processed, and should be processed only when it is called."
  • Re: Mapping a Unicode range to another

    John and Khaled have been providing the right answers here. The 'ccmp' feature can map glyphs into other glyphs, and should be processed in all shaping engines (certainly will be on Windows); but the application of 'init'/'medi'/'fina' features for Arabic-style cursive connection happens only in certain shaping engines based solely on Unicode characters. If you have Hebrew characters, the text will be processed in a Hebrew shaping engine that does not apply the 'init'/etc. features, and use of 'ccmp' will not change that.