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

peter sikking peter at mmiworks.net
Mon Sep 21 09:04:46 PDT 2015



Begin forwarded message:

> From: Dave Crossland <dave at lab6.com>
> Subject: Re: [CREATE] otf•UI product vision, warm off the press...
> Date: 21 Sep 2015 16:22:03 deber
> To: peter sikking <peter at mmiworks.net>, Khaled Hosny <khaledhosny at eglug.org>
> 
> 
> On Sep 21, 2015 9:27 AM, "peter sikking" <peter at mmiworks.net> wrote:
> >
> > Dave wrote:
> >
> > > btw: thinking through this, I do believe that the way the
> > > character entry – character encoding – standard font tables +
> > > mandatory (automatic) otf has come about, there are no cases
> > > where user-controllable otf _must_ be used to get just the
> > > correct glyph to display.
> > >
> > > if I am wrong about this, I would really appreciate a chat with
> > > an expert in this field.
> > >
> > > I think this depends on what you mean by "correct" glyphs;
> >
> > true, I was not clear enough. I was really talking about that
> > it does not need any otf to get a ‘5’ or a ‘b’ put in and
> > displayed.
> >
> > for me it is possible to think of all the environments where
> > there is near-zero typography knowledge (homes, offices, yeah
> > just about anywhere) and to see that for _latin_ script there
> > is are no cases where user-controllable otf _must_ be used to
> > get just the correct glyph to display.
> >
> > after all, these people did get their 5s and bs in for decades.
> >
> > for non-latin scripts, I do not know this (note: user-controllable,
> > not the automatic stuff).
> 
> Yes, I believe this is true for all scripts. Khaled, is this true for arabic?
> 
> > > I think 'unreadable' is an overstatement
> >
> > in usability terms (context: doing a convincing presentation)
> > it is a goner.
> >
> > > (Of course, a program could have some 'smart' features to activate optional OpenType features when available, such as detecting a col of numbers, the availability of a tnum feature in the font, and thus activating it.)
> >
> > 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. another one we discussed in the
> > video session: turn all ligatures off when the letter-spacing is
> > not the default.
> 
> 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.
> 
> >
> >     --ps
> >
> >         designs interaction for creatives +
> >         solutions with a wide impact on society
> >
> >         teacher, mentor, author, lecturer
> >         http://mmiworks.net/peter
> >



    --ps

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

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/create/attachments/20150921/a554b30a/attachment.html>


More information about the CREATE mailing list