Bug#406701: fails on example file CJKutf8.tex
Hi! From: Frederik Eaton <[EMAIL PROTECTED]> > > The reason is that TeX tried to look for Type1 fonts, but didn't find > > them so it started to look for PK fonts. Since they have never been > > created before, MakeTeXPK started to build them. Of course, it can't > > and the non-working PK files just sit in your ~/.texmf-var/. When > > kpathsea looks again for CJK fonts, it will use the PK fonts in your > > local TEXMF directory thining that they have been correctly > > converted. Hence your problem. > > > > I will clarify this in the README.Debian documentation, after which I > > think I can close this bug. I will upload a new version of the Debian > > CJK package in February. > > OK. Doesn't this sound like a bug in MakeTeXPK? It seems like the > fonts should be built in a temporary location, and only moved to their > final destinations if the build was successful. Indeed. After my exams, I hope to get more time to investigate this further. I'll keep this bug open as a reminder for me. Cheers Danai SAE-HAN 韓達耐 -- 題目:《和子由澠池懷舊》 作者:蘇軾（１０３６－１１０１） 人生到處知何似，應似飛鴻踏雪泥： 泥上偶然留指爪，鴻飛那復計東西。 老僧已死成新塔，壞壁無由見舊題。 往日崎嶇還記否，路上人困蹇驢嘶。
Bug#406701: fails on example file CJKutf8.tex
Hi Danai, > > > If updmap.cfg does contain these lines, then something has gone wrong > > > with updmap-sys. Please run updmap-sys again as root, and see for > > > *any* output relating to "wadalab". Also, none of the output of > > > updmap-sys may refer to files in your own /root/.texmf(-var)/ > > > directory or to /usr/local/share/. They should all point to > > > configuration files inside /usr/share/texmf(-tetex)/. > > > > There are also /usr/share/texmf-texlive lines, as well as > > /etc/texmf/map/dvips/hlatex/uhc-base.map. I've attached the output so > > there is no confusion. Only one line refers to wadalab: > > > > updmap-sys: using map file > > `/usr/share/texmf/fonts/map/dvips/wadalab/wadalab.map' > > All looks fine; I've never considered mixing teTeX and TeXlive, but > apparently it works on your computer. ;) OK, I just installed a bunch of packages that seemed like they might be relevant... > > > Also rename /home/frederik/.texmf-var/ to /home/frederik/.texmf-var2 . > > > If there are any leftovers from previous attempts to build PK fonts, > > > then dvips will prefer these dysfunctional fonts rather than use the > > > Type1 fonts. > > > > > > The ratio behind this is to ascertain that we're dealing solely with > > > files from the Debian package, and not local files. > > > > That solves the problem! > > > > $ dvips JIS.dvi > > This is dvips(k) 5.95a Copyright 2005 Radical Eye Software > > (www.radicaleye.com) > > ' TeX output 2007.01.13:1936' -> JIS.ps > > . > > > 1> [1] > > > > When I move the directory back, then the error returns. > > OK. Now remove the old and dysfunctional PK fonts: > > rm -rf ~/.texmf-var/fonts/pk/ljfour/wadalab > > Or better yet, remove ~/.texmf-var/ completely to be sure that > older remnants and your locally created "updmap" files are removed as > well. If you choose this option, then fonts like cm, ec, etc. will be > recompiled next time you need them with xdvi, dvips, etc. Done. > > I'm now curious what the moral should be - did I do something wrong at > > some point? I was trying to use 'ucs.sty' earlier, and I put a bunch > > of files from that package in texmf/tex/ so they would be in my path, > > was that what caused the problem? I'll attach a listing of the > > contents of those directories if that helps. > > No, this is a problem that few people know of, so don't worry. It's > got nothing to do with UCS. > Tip though: don't mix UCS with CJK; they don't like each other too > well. And with CJKutf8 you don't need UCS anymore. Cfr. several > emails in the CJK archives (see below). OK. > The reason is that TeX tried to look for Type1 fonts, but didn't find > them so it started to look for PK fonts. Since they have never been > created before, MakeTeXPK started to build them. Of course, it can't > and the non-working PK files just sit in your ~/.texmf-var/. When > kpathsea looks again for CJK fonts, it will use the PK fonts in your > local TEXMF directory thining that they have been correctly > converted. Hence your problem. > > I will clarify this in the README.Debian documentation, after which I > think I can close this bug. I will upload a new version of the Debian > CJK package in February. OK. Doesn't this sound like a bug in MakeTeXPK? It seems like the fonts should be built in a temporary location, and only moved to their final destinations if the build was successful. > [Some extra information; I just can't stop writing.] > > Other TeX fonts like Computer Modern, EC, etc. will create PK fonts > from other font formats. This was also the "old way" of CJK fonts > using ttf2tfm: the thus created TFM files would guide MakeTeXPK to > create PK fonts. There are three reasons why this isn't the best > option, and why I chose Type1 for CJK (the "modern way", also > preferred upstream). > > The first is quality: PK files are bitmap fonts, and if you print on a > higher quality printer, results are a bit blocky, making CJK glyphs > more difficult to read. > > The second is time. For every font table (which consists of max. 255 > glyphs each) you need to create a PK font. This is only created ad > hoc when TeX needs it, e.g. when viewing it with xdvi or using dvips. > Not only that, but it also needs to create PK fonts for each > resolution: 720dpi, 1440dpi, and so on. So if you change from 10pt to > 12pt or if you enlarge your view in xdvi, the whole PK creation > process begins all over again. Creating a set of subfonts with > ttf2tfm is done in seconds at the beginning, but after a while you'll > get irritated by the MakeTeXPK process. > > The third is that such PK fonts are now always saved in your local > TEXMF directory in ~/.texmf-var/, even if you are root or if you have > set the permissions in /var/cache/fonts/ (this used to be an option in > Debian teTeX2 and early versions of teTeX3). If you have a > single-user computer then that's no problem, but imagine if you have a > few users who use TeX, and they all
Bug#406701: fails on example file CJKutf8.tex
Hi Frederik! From: Frederik Eaton <[EMAIL PROTECTED]> > > If updmap.cfg does contain these lines, then something has gone wrong > > with updmap-sys. Please run updmap-sys again as root, and see for > > *any* output relating to "wadalab". Also, none of the output of > > updmap-sys may refer to files in your own /root/.texmf(-var)/ > > directory or to /usr/local/share/. They should all point to > > configuration files inside /usr/share/texmf(-tetex)/. > > There are also /usr/share/texmf-texlive lines, as well as > /etc/texmf/map/dvips/hlatex/uhc-base.map. I've attached the output so > there is no confusion. Only one line refers to wadalab: > > updmap-sys: using map file > `/usr/share/texmf/fonts/map/dvips/wadalab/wadalab.map' All looks fine; I've never considered mixing teTeX and TeXlive, but apparently it works on your computer. ;) > > Also rename /home/frederik/.texmf-var/ to /home/frederik/.texmf-var2 . > > If there are any leftovers from previous attempts to build PK fonts, > > then dvips will prefer these dysfunctional fonts rather than use the > > Type1 fonts. > > > > The ratio behind this is to ascertain that we're dealing solely with > > files from the Debian package, and not local files. > > That solves the problem! > > $ dvips JIS.dvi > This is dvips(k) 5.95a Copyright 2005 Radical Eye Software > (www.radicaleye.com) > ' TeX output 2007.01.13:1936' -> JIS.ps > . > 1> [1] > > When I move the directory back, then the error returns. OK. Now remove the old and dysfunctional PK fonts: rm -rf ~/.texmf-var/fonts/pk/ljfour/wadalab Or better yet, remove ~/.texmf-var/ completely to be sure that older remnants and your locally created "updmap" files are removed as well. If you choose this option, then fonts like cm, ec, etc. will be recompiled next time you need them with xdvi, dvips, etc. ["updmap" is user-specific, "updmap-sys" is system-wide and is to be preferred.] > I'm now curious what the moral should be - did I do something wrong at > some point? I was trying to use 'ucs.sty' earlier, and I put a bunch > of files from that package in texmf/tex/ so they would be in my path, > was that what caused the problem? I'll attach a listing of the > contents of those directories if that helps. No, this is a problem that few people know of, so don't worry. It's got nothing to do with UCS. Tip though: don't mix UCS with CJK; they don't like each other too well. And with CJKutf8 you don't need UCS anymore. Cfr. several emails in the CJK archives (see below). The reason is that TeX tried to look for Type1 fonts, but didn't find them so it started to look for PK fonts. Since they have never been created before, MakeTeXPK started to build them. Of course, it can't and the non-working PK files just sit in your ~/.texmf-var/. When kpathsea looks again for CJK fonts, it will use the PK fonts in your local TEXMF directory thining that they have been correctly converted. Hence your problem. I will clarify this in the README.Debian documentation, after which I think I can close this bug. I will upload a new version of the Debian CJK package in February. [Some extra information; I just can't stop writing.] Other TeX fonts like Computer Modern, EC, etc. will create PK fonts from other font formats. This was also the "old way" of CJK fonts using ttf2tfm: the thus created TFM files would guide MakeTeXPK to create PK fonts. There are three reasons why this isn't the best option, and why I chose Type1 for CJK (the "modern way", also preferred upstream). The first is quality: PK files are bitmap fonts, and if you print on a higher quality printer, results are a bit blocky, making CJK glyphs more difficult to read. The second is time. For every font table (which consists of max. 255 glyphs each) you need to create a PK font. This is only created ad hoc when TeX needs it, e.g. when viewing it with xdvi or using dvips. Not only that, but it also needs to create PK fonts for each resolution: 720dpi, 1440dpi, and so on. So if you change from 10pt to 12pt or if you enlarge your view in xdvi, the whole PK creation process begins all over again. Creating a set of subfonts with ttf2tfm is done in seconds at the beginning, but after a while you'll get irritated by the MakeTeXPK process. The third is that such PK fonts are now always saved in your local TEXMF directory in ~/.texmf-var/, even if you are root or if you have set the permissions in /var/cache/fonts/ (this used to be an option in Debian teTeX2 and early versions of teTeX3). If you have a single-user computer then that's no problem, but imagine if you have a few users who use TeX, and they all use CJK. A waste of space. Thanks for reporting and helping me make this package even better. =D When you've got more general questions about the use of CJK, you can send an email to the CJK user list at cjk@ffii.org, or browse the archives at http://lists.ffii.org/pipermail/cjk/ . Best wishes Danai SAE-HAN 韓達耐 -- 題目:《惠崇春江晚景》 作者:蘇
Bug#406701: fails on example file CJKutf8.tex
Hi Danai, > > > From what I gathered, xdvi works fine (it has found for example > > > dmjhira.pfb), but dvips doesn't. It's not even trying, because it > > > switches from searching for OVF right into searching for PK (packed > > > bitmap fonts), and since they don't exist either, it will try to make > > > the fonts all by itself. > > > > > > Please try this: > > > > > > dvips -P wadalab JIS.dvi > > > > > > This calls wadalab.map directly. > > > > That works! > > Ah, now we're getting somewhere. > So the problem is that all the fonts are correctly installed, and so > is the map file that brings all these individual Type1 subfonts > together. > > The problem is that somehow the global configuration file for Type1 > fonts is not properly configured. This involves the commands > update-updmap and updmap-sys (also updmap, but that is only for TeX > settings in your own TeX home directory). The Debian TeX managers > have created a quite ingenious system to make life easier for TeX > package maintainers: a tool that registers Type1 fonts centrally and > automatically updates the configuration files for a bunch of > applications, such as dvips. > > > /usr/share/texmf/dvips/config/config.wadalab should have the following > single line: > > p +wadalab.map > > > I'm about 99,9% sure that this is the case, otherwise dvips -P > wouldn't work lest there was a miracle. > > > /etc/texmf/updmap.d/10latex-cjk-japanese-wadalab.cfg should have the > following lines: > > # 10latex-cjk-japanese-wadalab.cfg > # You can change/add entries to this file and changes will be preserved > # over upgrades, even if you have removed the main package prior > # (not if you purged it). You should leave the following pseudo comment > # present in the file! > # -_- DebPkgProvidedMaps -_- > # > Map wadalab.map > > > /var/lib/texmf/web2c/updmap.cfg should contain the following section: > > ### From file: /etc/texmf/updmap.d/10latex-cjk-japanese-wadalab.cfg > # 10latex-cjk-japanese-wadalab.cfg > # You can change/add entries to this file and changes will be preserved > # over upgrades, even if you have removed the main package prior > # (not if you purged it). You should leave the following pseudo comment > # present in the file! > # -_- DebPkgProvidedMaps -_- > # > Map wadalab.map > ### End of file: /etc/texmf/updmap.d/10latex-cjk-japanese-wadalab.cfg > > > I suspect that update-updmap doesn't include the content of > 10latex-cjk-japanese-wadalab.cfg in updmap.cfg. Please tell me if I'm > wrong here. So far, all the files are as you have described them. The lines are present in updmap.cfg. > If updmap.cfg does contain these lines, then something has gone wrong > with updmap-sys. Please run updmap-sys again as root, and see for > *any* output relating to "wadalab". Also, none of the output of > updmap-sys may refer to files in your own /root/.texmf(-var)/ > directory or to /usr/local/share/. They should all point to > configuration files inside /usr/share/texmf(-tetex)/. There are also /usr/share/texmf-texlive lines, as well as /etc/texmf/map/dvips/hlatex/uhc-base.map. I've attached the output so there is no confusion. Only one line refers to wadalab: updmap-sys: using map file `/usr/share/texmf/fonts/map/dvips/wadalab/wadalab.map' > Also rename /home/frederik/.texmf-var/ to /home/frederik/.texmf-var2 . > If there are any leftovers from previous attempts to build PK fonts, > then dvips will prefer these dysfunctional fonts rather than use the > Type1 fonts. > > The ratio behind this is to ascertain that we're dealing solely with > files from the Debian package, and not local files. That solves the problem! $ dvips JIS.dvi This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2007.01.13:1936' -> JIS.ps . [1] When I move the directory back, then the error returns. I'm now curious what the moral should be - did I do something wrong at some point? I was trying to use 'ucs.sty' earlier, and I put a bunch of files from that package in texmf/tex/ so they would be in my path, was that what caused the problem? I'll attach a listing of the contents of those directories if that helps. Many thanks, Frederik -- http://ofb.net/~frederik/ .texmf-var2/ .texmf-var2/web2c .texmf-var2/web2c/updmap.log .texmf-var2/fonts .texmf-var2/fonts/map .texmf-var2/fonts/map/dvips .texmf-var2/fonts/map/dvips/updmap .texmf-var2/fonts/map/dvips/updmap/download35.map .texmf-var2/fonts/map/dvips/updmap/builtin35.map .texmf-var2/fonts/map/dvips/updmap/psfonts_t1.map .texmf-var2/fonts/map/dvips/updmap/psfonts_pk.map .texmf-var2/fonts/map/dvips/updmap/ps2pk.map .texmf-var2/fonts/map/dvips/updmap/psfonts.map .texmf-var2/fonts/map/pdftex .texmf-var2/fonts/map/pdftex/updmap .texmf-var2/fonts/map/pdftex/updmap/pdftex_dl14.map .texmf-var2/fonts/map/pdftex/updmap/pdftex_ndl14.map .texmf-var2/fonts/map/pdftex/updmap/pdftex.map .texmf-var2/fonts/map/dvipdfm .texmf-var2/fonts/map/dvipdfm/updmap .texmf-var2/fo
Bug#406701: fails on example file CJKutf8.tex
Hi Frederik! From: Frederik Eaton <[EMAIL PROTECTED]> > > From what I gathered, xdvi works fine (it has found for example > > dmjhira.pfb), but dvips doesn't. It's not even trying, because it > > switches from searching for OVF right into searching for PK (packed > > bitmap fonts), and since they don't exist either, it will try to make > > the fonts all by itself. > > > > Please try this: > > > > dvips -P wadalab JIS.dvi > > > > This calls wadalab.map directly. > > That works! Ah, now we're getting somewhere. So the problem is that all the fonts are correctly installed, and so is the map file that brings all these individual Type1 subfonts together. The problem is that somehow the global configuration file for Type1 fonts is not properly configured. This involves the commands update-updmap and updmap-sys (also updmap, but that is only for TeX settings in your own TeX home directory). The Debian TeX managers have created a quite ingenious system to make life easier for TeX package maintainers: a tool that registers Type1 fonts centrally and automatically updates the configuration files for a bunch of applications, such as dvips. /usr/share/texmf/dvips/config/config.wadalab should have the following single line: p +wadalab.map I'm about 99,9% sure that this is the case, otherwise dvips -P wouldn't work lest there was a miracle. /etc/texmf/updmap.d/10latex-cjk-japanese-wadalab.cfg should have the following lines: # 10latex-cjk-japanese-wadalab.cfg # You can change/add entries to this file and changes will be preserved # over upgrades, even if you have removed the main package prior # (not if you purged it). You should leave the following pseudo comment # present in the file! # -_- DebPkgProvidedMaps -_- # Map wadalab.map /var/lib/texmf/web2c/updmap.cfg should contain the following section: ### From file: /etc/texmf/updmap.d/10latex-cjk-japanese-wadalab.cfg # 10latex-cjk-japanese-wadalab.cfg # You can change/add entries to this file and changes will be preserved # over upgrades, even if you have removed the main package prior # (not if you purged it). You should leave the following pseudo comment # present in the file! # -_- DebPkgProvidedMaps -_- # Map wadalab.map ### End of file: /etc/texmf/updmap.d/10latex-cjk-japanese-wadalab.cfg I suspect that update-updmap doesn't include the content of 10latex-cjk-japanese-wadalab.cfg in updmap.cfg. Please tell me if I'm wrong here. If updmap.cfg does contain these lines, then something has gone wrong with updmap-sys. Please run updmap-sys again as root, and see for *any* output relating to "wadalab". Also, none of the output of updmap-sys may refer to files in your own /root/.texmf(-var)/ directory or to /usr/local/share/. They should all point to configuration files inside /usr/share/texmf(-tetex)/. Also rename /home/frederik/.texmf-var/ to /home/frederik/.texmf-var2 . If there are any leftovers from previous attempts to build PK fonts, then dvips will prefer these dysfunctional fonts rather than use the Type1 fonts. The ratio behind this is to ascertain that we're dealing solely with files from the Debian package, and not local files. > > You are also using an older version of tetex-base and tetex-bin. > > If you could try to install tetex-bin (>=3.0.22)? I think this might > > be the source of the problem. In fact, I am 95% sure. =D > > I've installed the latest version of tetex-bin, 3.0-29, and > tetex-base, 3.0.dfsg.3-5. OK. > > I might have to adjust the dependency of tetex-bin from (>=3.0) to > > something much higher. > > > > So if you could also try to purge all the latex-cjk-* packages as well > > as upgrade tetex-bin to a version equal or higher than 3.0.22? Some > > big changes for udpmap have been introduced from 3.0.16 onwards. > > I've purged the latex-cjk-* and reinstalled, but no luck. Same problem > with dvips. (unless I add -P wadalab) OK. Cheers Danai SAE-HAN 韓達耐 -- 題目:《村行》 作者:王禹稱（繁體“稱”，換“亻”旁）（９５４－１００１） 馬穿山徑菊初黃，信馬悠悠野興長。 萬壑有聲含晚籟，數峰無語立斜陽。 棠梨葉落胭脂色，蕎麥花開白雪香。 何事吟余忽惆悵，村橋原樹似吾鄉。
Bug#406701: fails on example file CJKutf8.tex
Hi Danai, > From what I gathered, xdvi works fine (it has found for example > dmjhira.pfb), but dvips doesn't. It's not even trying, because it > switches from searching for OVF right into searching for PK (packed > bitmap fonts), and since they don't exist either, it will try to make > the fonts all by itself. > > Please try this: > > dvips -P wadalab JIS.dvi > > This calls wadalab.map directly. That works! > You are also using an older version of tetex-base and tetex-bin. > If you could try to install tetex-bin (>=3.0.22)? I think this might > be the source of the problem. In fact, I am 95% sure. =D I've installed the latest version of tetex-bin, 3.0-29, and tetex-base, 3.0.dfsg.3-5. > I might have to adjust the dependency of tetex-bin from (>=3.0) to > something much higher. > > So if you could also try to purge all the latex-cjk-* packages as well > as upgrade tetex-bin to a version equal or higher than 3.0.22? Some > big changes for udpmap have been introduced from 3.0.16 onwards. I've purged the latex-cjk-* and reinstalled, but no luck. Same problem with dvips. (unless I add -P wadalab) Thanks, Frederik -- http://ofb.net/~frederik/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#406701: fails on example file CJKutf8.tex
Hi Frederik! From what I gathered, xdvi works fine (it has found for example dmjhira.pfb), but dvips doesn't. It's not even trying, because it switches from searching for OVF right into searching for PK (packed bitmap fonts), and since they don't exist either, it will try to make the fonts all by itself. Please try this: dvips -P wadalab JIS.dvi This calls wadalab.map directly. You are also using an older version of tetex-base and tetex-bin. If you could try to install tetex-bin (>=3.0.22)? I think this might be the source of the problem. In fact, I am 95% sure. =D I might have to adjust the dependency of tetex-bin from (>=3.0) to something much higher. So if you could also try to purge all the latex-cjk-* packages as well as upgrade tetex-bin to a version equal or higher than 3.0.22? Some big changes for udpmap have been introduced from 3.0.16 onwards. Thanks Danai SAE-HAN 韓達耐 -- 題目:《牧童詩》 作者:黃庭堅（１０４５－１１０５） 騎牛遠遠過前村，短笛橫吹隔隴聞。 多少長安名利客，機關用盡不如君。
Bug#406701: fails on example file CJKutf8.tex
Hi Danai, Sorry I forgot about the attachments, and sorry for the delay (napping)! Now there should be three files, corresponding to: $ strace -f dvips CJKutf8-japanese-only.dvi |& tee dvips.strace.log $ KPATHSEA_DEBUG=-1 dvips JIS.dvi -o JIS.ps &> dvips-debug.log $ KPATHSEA_DEBUG=-1 xdvi JIS.dvi &> xdvi-debug.log Of course, I recompiled the latex files in each case... Actually they were too big so I've put them here: http://ofb.net/~frederik/latex-cjk-logs.zip Thanks, Frederik -- http://ofb.net/~frederik/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#406701: fails on example file CJKutf8.tex
Also, recompile your LaTeX file. The DVI file needs to take into account the recent changes in the TEXMF font directories. Danai SAE-HAN 韓達耐 -- 題目:《新開棋軒呈元珍表臣》 作者:歐陽修（１００７－１０７２） 竹樹日已滋，軒窗漸幽興。 人間與世遠，鳥語知境靜。 春光靄欲布，山色寒尚映。 獨收萬籟心，于此一枰競。
Bug#406701: fails on example file CJKutf8.tex
From: Frederik Eaton <[EMAIL PROTECTED]> > I have now purged and reinstalled the Wadalab package, still no luck. Hmmm. Yet the problem lies with updmap, I'm sure of it, since that is the key to get the Type1 fonts. Does xdvi work? > Surely there are some commands which I could run to debug the > situation? KPATHSEA_DEBUG=-1 xdvi JIS.dvi &> xdvi-debug.log KPATHSEA_DEBUG=-1 dvips JIS.dvi -o JIS.ps &> dvips-debug.log If you could gzip or bzip2 these two files and send them to me? > I have attached some strace output from dvips. Missing here on my end. Could you please resend it? Thanks. Danai SAE-HAN 韓達耐 -- 題目:《江村晚眺》 作者:戴復古（１１６７－？） 江頭落日照平沙，潮退漁船閣岸斜。 白鳥一雙臨水立，見人驚起入蘆花。
Bug#406701: fails on example file CJKutf8.tex
Hello Danai, > > However, strangely enough, the problem with creating ps and pdf files > > remains. > > Hmm, try to purge and reinstall the Wadalab package. > If that doesn't work, then it could be that there's still something > left from the Cyberbit installation. Make sure that you really have > removed the .map and .cfg files, as well as all .afm, .tfm and .pfb > font files in /usr/local/share/texmf/fonts/ and c70song.fd. > > Then run texhash, update-updmap and updmap-sys again. > > If it still doesn't work, then there is indeed a bug in latex-cjk. > > > > > I've got one theory, but I'm not confident that it would actually > > > work: > > > > > > Remove or move away the Cyberbit Type1 and TFM fonts and the .map > > > file (basically undoing the installation from README.Debian), and > > > run texhash, update-updmap and updmap-sys as root. > > > > > > Now recompile the .tex file and view the DVI. Now run dvips or > > > dvipdfmx. Please show me the error message if it fails. > > > > OK. I did all this; I'm attaching the output files from dvips and > > latex. > > From what I see, this means that dvips doesn't find the Type1 fonts > from Wadalab and tries to make these fonts by itself (which is > impossible, of course). > > Please purge and reinstall the Wadalab package and see what it > gives. > > When everything works, dvips should create the PS output in a blink of > an eye. I have now purged and reinstalled the Wadalab package, still no luck. Surely there are some commands which I could run to debug the situation? I have attached some strace output from dvips. Thanks for looking at my problem. Frederik -- http://ofb.net/~frederik/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#406701: fails on example file CJKutf8.tex
From: Frederik Eaton <[EMAIL PROTECTED]> > I installed latex-cjk-all, with apt-get - if there were recommended > packages, I must have ignored the recommendations (should I always > follow recommendations?). No, as long as you read the package description. ;D But I'll make latex-cjk-all dependent on all font packages; that way there won't be any misunderstanding. And those who don't want the font packages, can still install the language-specific packages separately without having to install the font packages. > > > There is a remaining problem, which is that I can't convert either of > > > the dvi files to ps or pdf successfully - all of the Japanese > > > characters are blank. Am I correct in imagining that the problem is > > > again one of fonts? If so, what should I install? > > > > Most interesting. That shouldn't happen. > > Could you give me an output of the error? Or the last lines of > > missfonts.log, if it exists? > > > > Did something go wrong during the installation of > > latex-cjk-japanese-wadalab? > > Yes, you are exactly right. The problem was that updmap-sys was > failing, because of not being able to find cyberbit.map. I fixed that > (I had incorrectly followed the Cyberbit instructions in > README.Debian.gz, for some reason I mixed one of the "NEW way" > instructions into the "OLD way" method which I had chosen; I'm not > very good at following instructions - sorry!). > > However, strangely enough, the problem with creating ps and pdf files > remains. Hmm, try to purge and reinstall the Wadalab package. If that doesn't work, then it could be that there's still something left from the Cyberbit installation. Make sure that you really have removed the .map and .cfg files, as well as all .afm, .tfm and .pfb font files in /usr/local/share/texmf/fonts/ and c70song.fd. Then run texhash, update-updmap and updmap-sys again. If it still doesn't work, then there is indeed a bug in latex-cjk. > > I've got one theory, but I'm not confident that it would actually > > work: > > > > Remove or move away the Cyberbit Type1 and TFM fonts and the .map > > file (basically undoing the installation from README.Debian), and > > run texhash, update-updmap and updmap-sys as root. > > > > Now recompile the .tex file and view the DVI. Now run dvips or > > dvipdfmx. Please show me the error message if it fails. > > OK. I did all this; I'm attaching the output files from dvips and > latex. >From what I see, this means that dvips doesn't find the Type1 fonts from Wadalab and tries to make these fonts by itself (which is impossible, of course). Please purge and reinstall the Wadalab package and see what it gives. When everything works, dvips should create the PS output in a blink of an eye. Cheers Danai SAE-HAN 韓達耐 -- 題目:《霰》 作者:楊萬里（１１２７－１２０６） 雪花遣霰作前鋒，勢破張皇欲暗空。 篩瓦巧尋疏處漏，跳階誤到暖邊融。 寒聲帶雨山難白，冷氣侵人火失紅。 方訝一冬暄較甚，今宵敢嘆臥如弓。
Bug#406701: fails on example file CJKutf8.tex
Hello Danai, > > I have tried installing latex-cjk-japanese-wadalab (I didn't know it > > had to be installed) and removing everything but the Japanese from > > CJKutf8.tex, and now a dvi is produced which has Japanese text in it. > > > > The same for the JIS.tex from the latex-cjk-japanese package. > > Ah, great to hear that. > > Which package installer did you use? > Because latex-cjk-japanese-wadalab is recommended by > latex-cjk-japanese. And if you used "aptitude", it would normally > select the font package as well. I installed latex-cjk-all, with apt-get - if there were recommended packages, I must have ignored the recommendations (should I always follow recommendations?). > > It is a bit confusing that the error which occurs when a font is not > > installed is a parse error, "Undefined control sequence." - I would > > have thought that fonts would not affect actual LaTeX parsing. > > You're right that the Type1 fonts are not considered when LaTeX > compiles the .tex font: they are only used when you actually view the > DVI file or when you convert it to PS or PDF. > > However, TeX needs to calculate the amount of space that each glyph > needs, so it consults the .tfm (TeX Font Metric) files in > /usr/share/texmf/fonts/tfm/wadalab/. > > Hence the parsing error. I know it isn't too helpful for us, CJK > users, but I'm no TeXpert (yet ;). I see, that makes sense. > > There is a remaining problem, which is that I can't convert either of > > the dvi files to ps or pdf successfully - all of the Japanese > > characters are blank. Am I correct in imagining that the problem is > > again one of fonts? If so, what should I install? > > Most interesting. That shouldn't happen. > Could you give me an output of the error? Or the last lines of > missfonts.log, if it exists? > > Did something go wrong during the installation of > latex-cjk-japanese-wadalab? Yes, you are exactly right. The problem was that updmap-sys was failing, because of not being able to find cyberbit.map. I fixed that (I had incorrectly followed the Cyberbit instructions in README.Debian.gz, for some reason I mixed one of the "NEW way" instructions into the "OLD way" method which I had chosen; I'm not very good at following instructions - sorry!). However, strangely enough, the problem with creating ps and pdf files remains. > I've got one theory, but I'm not confident that it would actually > work: > > Remove or move away the Cyberbit Type1 and TFM fonts and the .map > file (basically undoing the installation from README.Debian), and > run texhash, update-updmap and updmap-sys as root. > > Now recompile the .tex file and view the DVI. Now run dvips or > dvipdfmx. Please show me the error message if it fails. OK. I did all this; I'm attaching the output files from dvips and latex. Thanks for your help, Frederik -- http://ofb.net/~frederik/ This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2007.01.13:0605' -> CJKutf8-japanese-only.ps kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 dmjsy mktexpk: don't know how to create bitmap font for dmjsy. kpathsea: Appending font creation commands to missfont.log. dvips: Font dmjsy not found, characters will be left blank. kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 dmjhira mktexpk: don't know how to create bitmap font for dmjhira. dvips: Font dmjhira not found, characters will be left blank. kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 dmjkata mktexpk: don't know how to create bitmap font for dmjkata. dvips: Font dmjkata not found, characters will be left blank. kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 dmjkh mktexpk: don't know how to create bitmap font for dmjkh. dvips: Font dmjkh not found, characters will be left blank. kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 dmjke mktexpk: don't know how to create bitmap font for dmjke. dvips: Font dmjke not found, characters will be left blank. kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 mc2jkb mktexpk: don't know how to create bitmap font for mc2jkb. dvips: Font mc2jkb not found, characters will be left blank. kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 dmjkk mktexpk: don't know how to create bitmap font for dmjkk. dvips: Font dmjkk not found, characters will be left blank. kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 dmjkt mktexpk: don't know how to create bitmap font for dmjkt. dvips: Font dmjkt not found, characters will be left blank. kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/600 --dpi 720 dmjki mktexpk: don't know how to create bitmap font for dmjki. dvips: Font dmjki not found, characters will be left blank. kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+120/60
Bug#406701: fails on example file CJKutf8.tex
Hi! From: Frederik Eaton <[EMAIL PROTECTED]> > I have tried installing latex-cjk-japanese-wadalab (I didn't know it > had to be installed) and removing everything but the Japanese from > CJKutf8.tex, and now a dvi is produced which has Japanese text in it. > > The same for the JIS.tex from the latex-cjk-japanese package. Ah, great to hear that. Which package installer did you use? Because latex-cjk-japanese-wadalab is recommended by latex-cjk-japanese. And if you used "aptitude", it would normally select the font package as well. > It is a bit confusing that the error which occurs when a font is not > installed is a parse error, "Undefined control sequence." - I would > have thought that fonts would not affect actual LaTeX parsing. You're right that the Type1 fonts are not considered when LaTeX compiles the .tex font: they are only used when you actually view the DVI file or when you convert it to PS or PDF. However, TeX needs to calculate the amount of space that each glyph needs, so it consults the .tfm (TeX Font Metric) files in /usr/share/texmf/fonts/tfm/wadalab/. Hence the parsing error. I know it isn't too helpful for us, CJK users, but I'm no TeXpert (yet ;). > There is a remaining problem, which is that I can't convert either of > the dvi files to ps or pdf successfully - all of the Japanese > characters are blank. Am I correct in imagining that the problem is > again one of fonts? If so, what should I install? Most interesting. That shouldn't happen. Could you give me an output of the error? Or the last lines of missfonts.log, if it exists? Did something go wrong during the installation of latex-cjk-japanese-wadalab? I've got one theory, but I'm not confident that it would actually work: Remove or move away the Cyberbit Type1 and TFM fonts and the .map file (basically undoing the installation from README.Debian), and run texhash, update-updmap and updmap-sys as root. Now recompile the .tex file and view the DVI. Now run dvips or dvipdfmx. Please show me the error message if it fails. > By the way, it might be nice to have a Debian package which depends on > everything necessary to get full functionality from latex-cjk. Hard > drives are big enough nowadays that I imagine many users won't mind > the extra space taken up by fonts for languages which they don't > intend to use. It is only a suggestion. There is already such a virtual package called "latex-cjk-all", which will install all the latex-cjk-* fonts. Since the font packages are only recommended, latex-cjk-all will also only recommend these fonts. Best regards Danai SAE-HAN 韓達耐 -- 題目:《活水亭觀書有感》 作者:朱熹（１１３０－１２００） 半畝方塘一鑒開，天光云影共徘徊。 問渠那得清如許，為有源頭活水來。
Bug#406701: fails on example file CJKutf8.tex
Hello Danai,
Thank you for your quick response.
I have tried installing latex-cjk-japanese-wadalab (I didn't know it
had to be installed) and removing everything but the Japanese from
CJKutf8.tex, and now a dvi is produced which has Japanese text in it.
The same for the JIS.tex from the latex-cjk-japanese package.
It is a bit confusing that the error which occurs when a font is not
installed is a parse error, "Undefined control sequence." - I would
have thought that fonts would not affect actual LaTeX parsing.
There is a remaining problem, which is that I can't convert either of
the dvi files to ps or pdf successfully - all of the Japanese
characters are blank. Am I correct in imagining that the problem is
again one of fonts? If so, what should I install?
By the way, it might be nice to have a Debian package which depends on
everything necessary to get full functionality from latex-cjk. Hard
drives are big enough nowadays that I imagine many users won't mind
the extra space taken up by fonts for languages which they don't
intend to use. It is only a suggestion.
Many thanks,
Frederik
On Sat, Jan 13, 2007 at 04:50:08AM +0100, Danai SAE-HAN wrote:
>
> Hi!
>
> From: Frederik Eaton <[EMAIL PROTECTED]>
>
> > (/usr/share/texmf/tex/latex/CJK/UTF8/c70mj.fd)kpathsea: Running mktextfm
> > uwmjc7
> > /usr/share/texmf/web2c/mktexnam: Could not map typeface abbreviation wm
> > for uwmjc7.
>
> This explains it all. Korean in UTF-8 doesn't work yet.
> Reason is that I need to iron out a few possible problems.
> The fonts are provided by the HLaTeX package, but need to be converted
> to Unicode, and not everything goes smoothly there.
>
> I intend to solve this issue in March or April, when I hope to get
> more time.
>
> If you really really need Korean support in UTF-8 encoded files, I
> could give you my own Makefile to create the fonts and install them in
> /usr/local/share/texmf/.
>
> If you don't need Korean support now, you can just comment these few
> lines. All the rest should work, even without the Cyberbit fonts.
> As long as you use the "CJKutf8" package, you don't need Cyberbit at
> all as long as you have other Unicode fonts for each script, id est
> one for Traditional Chinese, one for Simplified Chinese, one for
> Japanese, another for Russian, etc. These fonts should be defined in
> .fd "font definition" files in /usr/share/texmf/tex/latex/CJK/UTF8/.
>
> IOW, you can use CJKutf8 along with latex-cjk-japanese-wadalab in
> order to get Latin scripts (=T1) and Japanese working together
> nicely.
>
> As far as JIS is concerned, only use [dnp]{JIS} and not {JIS}. The
> reason here is that only DNP fonts are packaged on Debian (these are
> the beautiful Type1 Wadalab fonts). If you would just use {JIS}, CJK
> will try to find ugly HBF bitmap fonts, for which I haven't had the
> time yet to package (and for me it's got a lower priority ATM).
>
> So if you could try the JIS.tex example file that comes with
> latex-cjk-japanese? The three font styles are: min, goth and maru
> (I will put all three in the examples file in a next release).
>
>
> Cheers
>
>
>
> Danai SAE-HAN
> 韓達耐
>
> --
> 題目:《登快閣》
> 作者:黃庭堅（１０４５－１１０５）
>
> 痴兒了卻公家事，快閣東西倚晚晴。
> 落木千山天遠大，澄江一道月分明。
> 朱弦已為佳人絕，青眼聊因美酒橫。
> 萬里歸船弄長笛，此心吾與白鷗盟。
>
--
http://ofb.net/~frederik/
Bug#406701: fails on example file CJKutf8.tex
Hi!
From: Frederik Eaton <[EMAIL PROTECTED]>
> (/usr/share/texmf/tex/latex/CJK/UTF8/c70mj.fd)kpathsea: Running mktextfm
> uwmjc7
> /usr/share/texmf/web2c/mktexnam: Could not map typeface abbreviation wm for
> uwmjc7.
This explains it all. Korean in UTF-8 doesn't work yet.
Reason is that I need to iron out a few possible problems.
The fonts are provided by the HLaTeX package, but need to be converted
to Unicode, and not everything goes smoothly there.
I intend to solve this issue in March or April, when I hope to get
more time.
If you really really need Korean support in UTF-8 encoded files, I
could give you my own Makefile to create the fonts and install them in
/usr/local/share/texmf/.
If you don't need Korean support now, you can just comment these few
lines. All the rest should work, even without the Cyberbit fonts.
As long as you use the "CJKutf8" package, you don't need Cyberbit at
all as long as you have other Unicode fonts for each script, id est
one for Traditional Chinese, one for Simplified Chinese, one for
Japanese, another for Russian, etc. These fonts should be defined in
.fd "font definition" files in /usr/share/texmf/tex/latex/CJK/UTF8/.
IOW, you can use CJKutf8 along with latex-cjk-japanese-wadalab in
order to get Latin scripts (=T1) and Japanese working together
nicely.
As far as JIS is concerned, only use [dnp]{JIS} and not {JIS}. The
reason here is that only DNP fonts are packaged on Debian (these are
the beautiful Type1 Wadalab fonts). If you would just use {JIS}, CJK
will try to find ugly HBF bitmap fonts, for which I haven't had the
time yet to package (and for me it's got a lower priority ATM).
So if you could try the JIS.tex example file that comes with
latex-cjk-japanese? The three font styles are: min, goth and maru
(I will put all three in the examples file in a next release).
Cheers
Danai SAE-HAN
韓達耐
--
題目:《登快閣》
作者:黃庭堅（１０４５－１１０５）
痴兒了卻公家事，快閣東西倚晚晴。
落木千山天遠大，澄江一道月分明。
朱弦已為佳人絕，青眼聊因美酒橫。
萬里歸船弄長笛，此心吾與白鷗盟。
Bug#406701: fails on example file CJKutf8.tex
Package: latex-cjk-common Version: 4.7.0+cvs20061019-2 Severity: normal I get an error when I try to compile CJKutf8.tex, JIS,tex, and also when I create a file according to the instructions in /usr/share/doc/latex-cjk-common/japanese/japanese.txt.gz (these are the only things I've tried). I've followed the instructions in /usr/share/doc/latex-cjk-common/README.Debian.gz for installing the Cyberbit fonts, but I think the error is not related to that. An example of the text of the error is below. The error is on a line with Korean text in this case. I would really like to be able to use this package! It seems like so much work has been put into it ... I hope that I am doing something wrong. Thank you, Frederik $ latex CJKutf8.tex This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) entering extended mode (./CJKutf8.tex LaTeX2e <2003/12/01> Babel and hyphenation patterns for american, french, german, ngerman, b ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur kish, ukrainian, nohyphenation, pinyin, loaded. (/usr/share/texmf-tetex/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/share/texmf-tetex/tex/latex/base/size12.clo)) (/usr/share/texmf/tex/latex/cm-super/type1ec.sty (/usr/share/texmf-tetex/tex/latex/base/t1cmr.fd)) (/usr/share/texmf-tetex/tex/latex/base/fontenc.sty (/usr/share/texmf-tetex/tex/latex/base/t1enc.def)) (/usr/share/texmf/tex/latex/CJK/CJKutf8.sty (/usr/share/texmf-tetex/tex/latex/oberdiek/ifpdf.sty) (/usr/share/texmf-tetex/tex/latex/base/inputenc.sty (/usr/share/texmf-tetex/tex/latex/base/utf8.def (/usr/share/texmf-tetex/tex/latex/base/t1enc.dfu) (/usr/share/texmf-tetex/tex/latex/base/ot1enc.dfu) (/usr/share/texmf-tetex/tex/latex/base/omsenc.dfu))) (/usr/share/texmf/tex/latex/CJK/CJK.sty (/usr/share/texmf/tex/latex/CJK/mule/MULEenc.sty) (/usr/share/texmf/tex/latex/CJK/CJK.enc)) (/usr/share/texmf-tetex/tex/latex/base/fontenc.sty)) (/usr/share/texmf-tetex/tex/generic/babel/babel.sty (/usr/share/texmf-tetex/tex/generic/babel/germanb.ldf (/usr/share/texmf-tetex/tex/generic/babel/babel.def)) (/usr/share/texmf-tetex/tex/generic/babel/russianb.ldf (/usr/share/texmf-tetex/tex/latex/cyrillic/t2aenc.def (/usr/share/texmf-tetex/tex/latex/base/t2aenc.dfu))) (/usr/share/texmf-tetex/tex/latex/vietnam/vietnam.ldf Loading definitions for the Vietnamese font encoding (/usr/share/texmf-tetex/tex/latex/vietnam/t5enc.def) (/usr/share/texmf-tetex/tex/latex/vietnam/vncaps.tex)) (/usr/share/texmf-tetex/tex/generic/babel/english.ldf)) (/usr/share/texmf/tex/latex/CJK/ruby.sty) (/usr/share/texmf/tex/latex/CJK/CJKulem.sty (/usr/share/texmf-tetex/tex/latex/ulem/ulem.sty)) (./CJKutf8.aux) (/usr/share/texmf-tetex/tex/latex/cyrillic/t2acmr.fd) (/usr/share/texmf-tetex/tex/latex/vietnam/t5cmr.fd) (/usr/share/texmf/tex/latex/CJK/UTF8/UTF8.bdg) (/usr/share/texmf/tex/latex/CJK/UTF8/UTF8.enc) (/usr/share/texmf/tex/latex/CJK/UTF8/UTF8.chr) (/usr/share/texmf/tex/latex/CJK/UTF8/c70mj.fd)kpathsea: Running mktextfm uwmjc7 /usr/share/texmf/web2c/mktexnam: Could not map typeface abbreviation wm for uwmjc7. /usr/share/texmf/web2c/mktexnam: Need to update /usr/share/texmf-tetex/fonts/map/fontname/special.map? mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input uwmjc7 This is METAFONT, Version 2.71828 (Web2C 7.5.4) kpathsea: Running mktexmf uwmjc7 ! I can't find file `uwmjc7'. <*> ...:=ljfour; mag:=1; nonstopmode; input uwmjc7 Please type another input file name ! Emergency stop. <*> ...:=ljfour; mag:=1; nonstopmode; input uwmjc7 Transcript written on mfput.log. grep: uwmjc7.log: No such file or directory mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input uwmjc7' failed to make uwmjc7.tfm. kpathsea: Appending font creation commands to missfont.log. ! Font C70/mj/m/n/12/c7=uwmjc7 at 12.0pt not loadable: Metric (TFM) file not fo und. relax l.49 이 FAQ 은 자주 반복되는 질문과 그에 대한 대답을 간... ? -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages latex-cjk-common depends on: ii tetex-base3.0-18 Basic library files of teTeX ii tetex-bin 3.0-16 The teTeX binary files Versions of packages latex-cjk-common recommends: ii freetype1-tools 1.4pre.20050518-0.5 Bundled tests, demos and tools for -- no debconf information
