From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/59931 Path: news.gmane.org!not-for-mail From: Taco Hoekwater Newsgroups: gmane.comp.tex.context Subject: Re: Palatino Linotype under MKIV Date: Wed, 30 Jun 2010 09:33:43 +0200 Message-ID: <4C2AF357.1040306@elvenkind.com> References: Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------040600050305020308090605" X-Trace: dough.gmane.org 1277883249 29445 80.91.229.12 (30 Jun 2010 07:34:09 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 30 Jun 2010 07:34:09 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Wed Jun 30 09:34:06 2010 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([195.12.62.10]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OTro6-0004Tm-2N for gctc-ntg-context-518@m.gmane.org; Wed, 30 Jun 2010 09:34:06 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id D97EEC9B16; Wed, 30 Jun 2010 09:34:05 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 2VhLLIxObDZX; Wed, 30 Jun 2010 09:33:59 +0200 (CEST) Original-Received: from balder.ntg.nl (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id B0206C9A8A; Wed, 30 Jun 2010 09:33:59 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id D09C2C9A8A for ; Wed, 30 Jun 2010 09:33:58 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id yMwveiMErXbA for ; Wed, 30 Jun 2010 09:33:56 +0200 (CEST) Original-Received: from smtp-vbr2.xs4all.nl (smtp-vbr2.xs4all.nl [194.109.24.22]) by balder.ntg.nl (Postfix) with ESMTP id 746BFC9A70 for ; Wed, 30 Jun 2010 09:33:56 +0200 (CEST) Original-Received: from boo.fritz.box (boo.demon.nl [83.163.247.99]) (authenticated bits=0) by smtp-vbr2.xs4all.nl (8.13.8/8.13.8) with ESMTP id o5U7XoFM024229; Wed, 30 Jun 2010 09:33:56 +0200 (CEST) (envelope-from taco@elvenkind.com) User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100614 Mandriva/3.0.4-11mdv2010.1 (2010.1) Thunderbird/3.0.4 In-Reply-To: X-Virus-Scanned: by XS4ALL Virus Scanner X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl Xref: news.gmane.org gmane.comp.tex.context:59931 Archived-At: This is a multi-part message in MIME format. --------------040600050305020308090605 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, On 06/29/2010 11:15 AM, Paul Schalck wrote: > Hi, > > I'm trying to use the full glyph range of the Palatino Linotype font > shipped with XP (version 1.40; significantly different from the Windows > 7 one) under MKIV. Everything works fine (oldstyle figures, sups for > instance), except that the small cap "i" character has a dot whereas it > shouldn't. I borrowed one of the fonts from my wife's XP install (pala.ttf). The short answer: the font is borked, complain to Microsoft. The long answer: lookups are name-based, and if there are two glyphs with the same name, you can't know which one is used in any particular piece of software. > As far as I can see, it has to do with the messy name list of the > glyphs. Both the normal small cap i and the small cap dotted i are named > "i.sc" The one with a dot is meant for Turkish. > Moreover, the small cap glyphs have no unicode numbers in this font, so > I cannot pick them manually with \char"XXXX or even with \charXXXXX. > > Any ideas how I can get the right dottless i? Context always maps all unencoded glyphs into a private area starting at 0xF0000. For this font, the first i.sc (the one without dot) is at 0xF00AF and has glyph index 0x456, and the second is at 0xF00EB with glyph index 0x492. To find these numbers, run a file like this: \usemodule[fnt-10] \starttext \ShowCompleteFont{file:pala.ttf}{20pt}{1} \stoptext This means that to get the dotless version, you could enter \char"F00AF Really long answer: to fix the problem nicely, we have to rename one of the two glyphs. This could be done in an external editor, but as this is a system font, that may not be wise or even possible. Luckily, context allows to do this using a patching system that is active during initial font loading time (when the cache is generated). In the following, we will be patching the generated cache file before it is saved (by putting some lua code at the beginning of your test file). Remember that you have to delete the generated cache files after each iteration. In my case, they were /opt/tex/texmf- cache/luatex-cache/context/c24894930eb65eadf7b71f1e305ff518/fonts/otf/pala.tm*. If you forget to do this step in between runs, nothing will change in the output! The existing font patches are in font-pat.lua, and from that file it is possible to deduce that something like this is the correct program structure, theoretically: \startluacode function palapatch (data,filename) -- to be filled in end fonts.otf.enhancers.patches["^pala"] = palapatch \stopluacode The two arguments to the patch function are the data table from the luafontloader and the font file name, respectively. The function should patch the data table to our liking and does not have to return anything. In order to have a good look at the data, the first thing to do is to dump the data to a file. Put this code at the top of your test file, delete the data cache files, and run: \startluacode function palapatch (data,filename) io.savedata(filename .. '.lua', table.serialize(data)) end fonts.otf.enhancers.patches["^pala"] = palapatch \stopluacode \definefontfeature [...] Afterwards, open pala.ttf.lua (or pala.TTF.lua. not sure how this works out on an actual XP install) in an editor for browsing. Looking at the lua code in pala.ttf.lua, you will see that there is a pretty large sub-array called 'glyphs', which happens to be indexed by glyph id. There are two entries in that sub-array called 'i.sc' and we will want to change the second of those to 'i.scturkish' (the one at 0x492, the number we discovered above). Change the lua code to the code below, save your test file, delete the data cache again, and rerun. \startluacode function palapatch (data,filename) data.glyphs[0x492].name = "a.scturkish" end fonts.otf.enhancers.patches["^pala"] = palapatch \stopluacode That's one problem fixed. If you look at the test's pdf, it will now have dotless i's in the smallcaps. But now we have broken the turkish smallcaps code (it will now also use the first i.sc, which is wrong) so it is nice to fix that as well. Some searching back and forth through the pala.ttf.lua code reveals that there are two lookups that use i.sc: ss_latn_l_13_s (for normal latin) and ss_latn_l_14_s (for turkish). These lookups are part of the glyph definition of 'i' which lives at 0x92 (I found that number in the earlier font dump, but you could also count the entries in pala.ttf.lua, if you are bored or like counting stuff). Named lookups are small arrays (you can deduce that from the double braces in pala.ttf.lua), so the needed patch is: data.glyphs[0x92].lookups["ss_latn_l_14_s"][1].specification.variant="a.scturkish" And that will fix the turkish lookup. Now, I want to make sure we only run this code for palatino version 1.40 (it should be obvious why), and it is nice to do a terminal message as well. (note: testing for just the font version ignores the fact that different vendors may use the same font name for different fonts, but that is a complication that I think can be ignored in this particular case). The end result is: \startluacode function palapatch (data,filename) if data.version == "1.40" then logs.report("load otf", "patching smallcaps i") data.glyphs[0x92].lookups["ss_latn_l_14_s"][1].specification.variant="a.scturkish" data.glyphs[0x492].name = "a.scturkish" end end fonts.otf.enhancers.patches["^palatino"] = palapatch \stopluacode Updated test file attached. I hope this makes sense to someone who is willing to wikify the process. Best wishes, Taco --------------040600050305020308090605 Content-Type: application/x-tex; name="palasc.tex" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="palasc.tex" \startluacode function palapatch (data,filename) if data.version == "1.40" then logs.report("load otf", "patching smallcaps i") data.glyphs[0x92].lookups["ss_latn_l_14_s"][1].specification.variant="a.scturkish" data.glyphs[0x492].name = "a.scturkish" end end fonts.otf.enhancers.patches["^pala"] = palapatch \stopluacode \definefontfeature[palatinolt-default][script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality] \definefontfeature[palatinolt-smcp][script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality,smcp=yes,onum=yes] \definefontfeature[palatinolt-sups][mode=node,script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality,sups=yes] \starttypescript[serif][palatinolt][name] \usetypescript[serif][fallback] \definefontsynonym[Serif][file:pala.ttf][features=palatinolt-default] \definefontsynonym[SerifBold][file:palab.ttf][features=palatinolt-default] \definefontsynonym[SerifItalic][file:palai.ttf][features=palatinolt-default] \definefontsynonym[SerifBoldItalic][file:palabi.ttf][features=palatinolt-default] \definefontsynonym[SerifCaps][file:pala.ttf][features=palatinolt-smcp] \stoptypescript \definetypeface[palatinolt][rm][serif][palatinolt][default] \setupbodyfont[palatinolt] \enableprotruding\setuppagenumbering[location=] \starttext {\sc \input knuth } \stoptext --------------040600050305020308090605 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________ --------------040600050305020308090605--