[CREATE] otf•UI product vision, warm off the press...

[peter sikking]

Dave wrote:

> > right on: I was already thinking that a set of recommendations
> > (only based on what is hard-as-nails in the otf standard) must
> > be part of the deliverable.
> 
> Hmm. Maybe out of scope. But... There are a heap of conversions that a smart rich text editor is likely to do, eg change quote " to curly quotes, minus - to en/em dash, 3 periods ... to ellipsis, etc etc, which depend on the encoded glyphs being present in the font.
> 
> This relates to OT because, like OT, different languages have different typographic conventions, which OT can respond to also, so " may become《 instead, if the script/lang is Latin/French.
> 
> There are also some case responsive OT features which manual letter-spacing could collide with, being designed by the font developer for default letter spacing.

I realise this gets tricky, fast. it would be only about
switching otf, not subbing char codes.

if any of these guidelines are not clear-cut, then it is better to
leave it out. they do address however the “without the need to
obtain openType/typographical domain knowledge” part for developers.

will see…

    --ps

        designs interaction for creatives +
        solutions with a wide impact on society

        teacher, mentor, author, lecturer
        http://mmiworks.net/peter