FontLab Forum
2012-05-16, 12:21:09 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to the FontLab forum, read how to use it! Update: Archives from old MSN forums are now available on our forum.
 
   Home   Help Search Calendar Downloads Tags Login Register  
Del.icio.us Digg FURL FaceBook Stumble Upon Reddit SlashDot

Pages: [1]
  Print  
Author Topic: case feature  (Read 2675 times)
ArchivePoster
Guest
« on: 2008-03-05, 19:33:00 »

Posted by: sanides2
         
Hi there!
Just wondering if anyone else is unhappy with the "case" feature... (In InDesign it moves glyphs like "hyphen", "emdash" etc upward when text is marked as "All Caps" , but it doesn't work when text is directly written in caps or capitalized by selecting "Type/ Change Case".
I tried to make the case sensitivity work whenever caps are in use by including the following lookup in the "liga" feature. Seems to work.

Maybe someone would like to try it or comment it.


lookup liga25 {
sub @positionNormal' [@uppercaseLetters ] by @positionHigh;
sub @positionNormal' @positionNormal [@uppercaseLetters] by @positionHigh;
sub @positionNormal' @positionNormal @positionNormal [@uppercaseLetters] by @positionHigh;
sub [@uppercaseLetters @positionHigh] @positionNormal' [@uppercaseLetters @positionNormal space] by @positionHigh;
} liga25;


The classes contain:

@positionNormal:
parenleft, parenright, braceleft, braceright, hyphen,
exclamdown, questiondown, endash, emdash etc
IN NORMAL POSITION

@positionHigh:
parenleft, parenright, braceleft, braceright, hyphen,
exclamdown, questiondown, endash, emdash etc
IN HIGH POSITION

@uppercaseLetters:  all the capital letters
         
Logged
ArchivePoster
Guest
« Reply #1 on: 2008-03-09, 12:08:00 »

Posted by: kltf
         
Hello! In general I'm pretty fond of handling these issues in a smart way. I remember having played with similar solutions, but finally abandoned them because they led to undesired effects in some combinations.
For example, it seems that with your code, if you have a capitalized word in parenthesis like "(Otto)", you get a cased opening parenthesis and a non-cased closing parenthesis.
But even if this would work correctly on word level, you may still end up with things like this: "... (UNO), (and ..." where a cased closing parenthesis is close to a non-cased opening parenthesis. I would not consider this as a typographic improvement.

My conclusion was that it is better to let the typographer decide where to apply case variants. Except maybe that you have an antomatism which works extremely well and reliable.
         
Logged
ArchivePoster
Guest
« Reply #2 on: 2008-03-09, 18:41:00 »

Posted by: sanides2
         
I checked once more, and you are right...as the pdf shows. Obviously it depends on the kind of font you are designing.. in this kind of freely varying script font a bit of jumping up and down is probably acceptable.
I just noticed that many graphic designers in my surroundings hardly ever make use of the OpenType feature variants, so it seems to me an advantage to get some of them to work by default ...

js
         
Logged
ArchivePoster
Guest
« Reply #3 on: 2008-03-09, 18:59:00 »

Posted by: sanides2
         
well, here is the pdf now
js
         
Logged
Tags:
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!