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 > > <tex.pro><texps.pro>. <cmbx12.pfb><dmjkb.pfb><dmjkf.pfb><dmjhira.pfb> > > <dmjkj.pfb><dmjka.pfb><dmjkg.pfb><dmjkd.pfb><dmjkl.pfb><dmjki.pfb><dmjkk.pfb> > 1> <dmjke.pfb><dmjsy.pfb><dmjkata.pfb><cmr12.pfb>[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 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/ . OK, I've subscribed to the list. Thanks to you as well! Frederik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
