Re: [NTG-context] font encodings (glyph lossed with Gentium in T5)
On 1/21/06, Henning Hraban Ramm
Ok, Gentium is now online including t5 encoding. (That's not yet mentioned on the page.)
Just tested your package. I loss a glyph which I dont know the name. Its shot is at : http://people.vnoss.org/~vnpenguin/pub/shots/gentium-dd.png It seems that you use Gentium 1.01. With Gentium 1.02 in my box, I could use this glyph no problem (the shot was done with Gentium 1.02 in Leafpad editor). I try to replace your ttf by 1.02 release by modifying map file. But this does not help. Maybe we need to recreate files with 1.02 ? Thank you, -- http://vnoss.org Vietnamese Open Source Software Community
Am 2006-01-21 um 20:26 schrieb VnPenguin:
Ok, Gentium is now online including t5 encoding. (That's not yet mentioned on the page.)
Just tested your package. I loss a glyph which I dont know the name. Its shot is at : http://people.vnoss.org/~vnpenguin/pub/shots/gentium-dd.png
It seems that you use Gentium 1.01. With Gentium 1.02 in my box, I could use this glyph no problem (the shot was done with Gentium 1.02 in Leafpad editor).
I try to replace your ttf by 1.02 release by modifying map file. But this does not help. Maybe we need to recreate files with 1.02 ?
Sorry, I missed that update. Just downloaded it and created the files anew (now online), but no change. I guess the strike-through d should be in slot 31; probably an encoding problem. I guess I should update ConTeXt, another encoding problem in ec was fixed. Greetlings from Lake Constance! Hraban --- http://www.fiee.net/texnique/ http://contextgarden.net http://www.cacert.org (I'm an assurer)
Sorry, I missed that update. Just downloaded it and created the files anew (now online), but no change. I guess the strike-through d should be in slot 31; probably an encoding problem. I guess I should update ConTeXt, another encoding problem in ec was fixed.
It didn't help, 'dcroat' is still missing. Ok, I tracked it down: The tool that creates AFMs from TTFs, that is called by texfont, doesn't get all characters! I opened the font files with FontForge and wrote AFMs with that, now it works (same with Junicode). A new upload will follow in some minutes. Greetlings from Lake Constance! Hraban --- http://www.fiee.net/texnique/ http://contextgarden.net http://www.cacert.org (I'm an assurer)
On 1/21/06, Henning Hraban Ramm
Sorry, I missed that update. Just downloaded it and created the files anew (now online), but no change. I guess the strike-through d should be in slot 31; probably an encoding problem. I guess I should update ConTeXt, another encoding problem in ec was fixed.
Just tried your new package. 1. In the file t5-sil-gentium.map, I see: ---------------------------------------------------------------------------------------------------------------------- t5-raw-genai101 GentiumAlt-Italic 4 < genai101.ttf t5.enc t5-raw-genar101 GentiumAlt 4 < genar101.ttf t5.enc t5-raw-geni101 Gentium-Italic 4 < geni101.ttf t5.enc t5-raw-genr101 Gentium 4 < genr101.ttf t5.enc t5-raw-genai102 GentiumAlt-Italic 4 < genai102.pfb t5.enc t5-raw-genar102 GentiumAlt 4 < genar102.pfb t5.enc t5-raw-geni102 Gentium-Italic 4 < geni102.pfb t5.enc t5-raw-genr102 Gentium 4 < genr102.pfb t5.enc ----------------------------------------------------------------------------------------------------------------------- Why 1.01 ttf are still there ? And why 1.02 PFB while there are only TTF in your package ? 2. I don't think that files fonts.cache-1 are necessary for ConTeXt :-) $ unzip -l sil-gentium.zip | grep fonts.cache 0 08-10-05 11:50 fonts/afm/sil/gentium/fonts.cache-1 0 08-10-05 11:51 fonts/tfm/sil/gentium/fonts.cache-1 3334 08-10-05 11:51 fonts/truetype/sil/gentium/fonts.cache-1 0 08-10-05 11:53 fonts/vf/sil/gentium/fonts.cache-1 Thank for your work, Regards, -- http://vnoss.org Vietnamese Open Source Software Community
Am 2006-01-21 um 23:13 schrieb VnPenguin:
1. In the file t5-sil-gentium.map, I see: ---------------------------------------------------------------------- ------------------------------------------------ t5-raw-genai101 GentiumAlt-Italic 4 < genai101.ttf t5.enc t5-raw-genar101 GentiumAlt 4 < genar101.ttf t5.enc t5-raw-geni101 Gentium-Italic 4 < geni101.ttf t5.enc t5-raw-genr101 Gentium 4 < genr101.ttf t5.enc t5-raw-genai102 GentiumAlt-Italic 4 < genai102.pfb t5.enc t5-raw-genar102 GentiumAlt 4 < genar102.pfb t5.enc t5-raw-geni102 Gentium-Italic 4 < geni102.pfb t5.enc t5-raw-genr102 Gentium 4 < genr102.pfb t5.enc ---------------------------------------------------------------------- ------------------------------------------------- Why 1.01 ttf are still there ? And why 1.02 PFB while there are only TTF in your package ?
texfont never deletes a mapfile - it writes not only a .bak, but also only appends entries, even if the old stuff is wrong... Additionally, it always writes entries for PFB files, even if there are only TTF. A known bug (at least for me), but sometimes I forget to fix that. Ok, I'm uploading the next version.
2. I don't think that files fonts.cache-1 are necessary for ConTeXt :-)
You're right, but they don't hurt also ;-) I tried to config pango/fontconfig of my LilyPond installation so that it also finds TeX fonts. Until now it only writes these cache files, but never uses the fonts... At the moment I'm struggling with a font that uses different names in PFB, AFM and else. Chaos! It doesn't even provide accentes characters. I guess I'll drop it. Greetlings from Lake Constance! Hraban --- http://www.fiee.net http://www.cacert.org (I'm an assurer)
On 1/21/06, Henning Hraban Ramm
Ok, I'm uploading the next version.
Just tested. ... ){/work/apps/teTeX/share/texmf-local/fonts/enc/dvips/vntex/t5.enc}
Output written on test-gentium.pdf (1 page, 25034 bytes). Transcript written on test-gentium.log. The glyph "dcroat" was not found :( I think there is problem in Gentium fonts with this glyph. Thank you, Regards, -- http://vnoss.org Vietnamese Open Source Software Community
Am 2006-01-22 um 08:03 schrieb VnPenguin:
... ){/work/apps/teTeX/share/texmf-local/fonts/enc/dvips/vntex/t5.enc}
Output written on test-gentium.pdf (1 page, 25034 bytes). Transcript written on test-gentium.log.
The glyph "dcroat" was not found :( I think there is problem in Gentium fonts with this glyph.
Yes, I saw that. For pdfTeX's tool ttf2afm doesn't see a lot of letters in some fonts I guess pdfTeX's code for accessing letters in TT fonts is somewhat broken. Or something in ConTeXt, I don't know. E.g. if I install the Junicode fonts with texfont, the t5 table is half empty. If I create the AFMs with FontForge, it's mostly filled, but I get some of the glyph ... not found' warnings, i.e. it can access some more characters, but still not all. But *all* of the characters should be there (they *are* in the font!). 'dcroat' (striked-through d) is a typical case. Please, any of the wizards, what can we do? Greetlings from Lake Constance! Hraban --- http://www.fiee.net/texnique/ http://contextgarden.net http://www.cacert.org (I'm an assurer)
On 1/22/06, Henning Hraban Ramm
Please, any of the wizards, what can we do?
I asked Han The Thanh this problem. He has done support for MS Core Fonts (truetype) in VnTeX. So I hope he will give us some help. Thanks, -- http://vnoss.org Vietnamese Open Source Software Community
On Jan 22, 2006, at 1:36 PM, Henning Hraban Ramm wrote:
E.g. if I install the Junicode fonts with texfont, the t5 table is half empty. If I create the AFMs with FontForge, it's mostly filled, but I get some of the glyph ... not found' warnings, i.e. it can access some more characters, but still not all. But *all* of the characters should be there (they *are* in the font!). 'dcroat' (striked-through d) is a typical case.
Please, any of the wizards, what can we do?
OK, this may not be of much help, but I just converted GenR102.TTF to pfb via fontforge, and now the font correctly picks up the dcroat glyph. I mus admit I had similar situations in the past where simply regenerating the font would solve mysterious problems, so I shrugged my shoulders and did what a man must do. I think the new Gentium license allows for this conversion, and the LaTeX people will be distributing pfbs anyway, so why not convert to pfb (which is easier for TeX to use anyway?) Best Thomas
On 1/22/06, Thomas A. Schmitz
OK, this may not be of much help, but I just converted GenR102.TTF to pfb via fontforge, and now the font correctly picks up the dcroat glyph. I mus admit I had similar situations in the past where simply regenerating the font would solve mysterious problems, so I shrugged my shoulders and did what a man must do. I think the new Gentium license allows for this conversion, and the LaTeX people will be distributing pfbs anyway, so why not convert to pfb (which is easier for TeX to use anyway?)
Hi Thomas, You're completely right ! Just tried with PFB (converted by fontforge) and it works :) Thank you, -- http://vnoss.org Vietnamese Open Source Software Community
OK, this may not be of much help, but I just converted GenR102.TTF to pfb via fontforge, and now the font correctly picks up the dcroat glyph. I mus admit I had similar situations in the past where simply regenerating the font would solve mysterious problems, so I shrugged my shoulders and did what a man must do. I think the new Gentium license allows for this conversion, and the LaTeX people will be distributing pfbs anyway, so why not convert to pfb (which is easier for TeX to use anyway?)
Hi Thomas, You're completely right ! Just tried with PFB (converted by fontforge) and it works :)
Package Gentium (PFB converted by fontforge) with qx,t5,texnansi, ec : http://people.vnoss.org/~vnpenguin/pub/context/fonts/Gentium102-context.tgz Tested ok with T5. -- http://vnoss.org Vietnamese Open Source Software Community
participants (3)
-
Henning Hraban Ramm -
Thomas A. Schmitz -
VnPenguin