How do you implement ijacute and IJacute?

Dave CrosslandDave Crossland Posts: 1,052
edited December 2015 in Technique and Theory
Following up on this discussion, 

How do people set up ijacute and IJacute?

They have Unicode values, and while Underware's Latin Plus encodes them in the private use area as U+E133 which I think is not a good idea, it seems clear that either way the glyphs may need to be created and relevant OpenType 'locl' features written. 


  • Thank you John. –
    I wonder if there could be a more simple and straightforward way to implement a viable solution.

    I also wonder: you code <I acutecomb>. What if people type in <acutecomb I>?
    (I always type the accent first, and it works).

    any more insights, good practice advice?
  • Exceptions always require additional attention, but once you have a solution, you can easily copy it to your other fonts.

    script latn {
    language NLD {
    feature GlyphCompositionDecomposition1;

    feature GlyphCompositionDecomposition1 ccmp {
    lookup LigatureIJ;

    lookup LigatureIJ {
    sub I acutecomb J acutecomb -> IJacute;
    sub I J -> IJ;
    sub i acutecomb j acutecomb -> ijacute;
    sub i j -> ij;
    sub Iacute acutecomb -> IJacute;
    sub iacute j acutecomb -> ijacute;

  • @Erwin Denissen 
      sub Iacute acutecomb -> IJacute;
    should be
      sub Iacute J acutecomb -> IJacute;
    in your example.
  • Good catch! Now you mentioned it I wonder how I could have missed it.
  • John HudsonJohn Hudson Posts: 1,851

    I also wonder: you code <I acutecomb>. What if people type in <acutecomb I>?
    (I always type the accent first, and it works).

    You're probably using a deadkey input mechanism that maps that series of key strokes to the precomposed í character. This is a different mechanism from using Unicode combining marks, which the standard specifies are always ordered after the base character to which they apply.

    Remember, the relationship of what you hit on a keyboard to the encoded characters stored on the computer isn't necessarily one-to-one. It's even possible to make Keyman keyboards that enable you to key Unicode combining marks before bases as if they were deadkey input, but the resulting text is stored correctly, with the marks after the bases.
Sign In or Register to comment.