[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#351333: cid-x.map is almost empty



Hi,

I've sent to the wrong mail address, resending.

> > > You've broken some default font-maps which were provided by dvipdfmx. Put them back.
> > 
> > dvipdfmx package does not contain any font file. Configurations for other
> > package must be contained to that package. Otherwise, dvipdfmx have to
> > depend on that package. Most of people don't want to install every packages
> > that uses dvipdfmx.
> 
> That wasn't the case with the previous dvipdfmx version.  The fonts
> are provided by the ptex-base packages, they are not add-ons. You'll
> either need to patch ptex-base packages for dvipdfmx, or dvipdfmx to
> add its own support for ptex basic fonts.
> 
> I'm cc'ing debian-tetex-maint for some input.
> 
> 
> I've checked, tetex-base, and it provides map files in 
> 	/usr/share/texmf-tetex/fonts/map/
> and has files under
> 	/etc/texmf/updmap.d/
> 
> Probably ptex-base should provide map files somewhere,
> so that it can be used by dvipdfmx.
> 
> updmap manpage tells me 
> 
>    updmap is a utility that creates font configuration files for
> dvips(1), pdftex(1), xdvi(1), ps2pk(1), gsftopk(1), dvipdfm(1) and
> (soon) dvipdfmx(1).
> 
> whatever that means, it's probably not yet supported.

After some looking around, probably the map files found in 
	/var/lib/texmf/fonts/map/dvipdfm/updmap/dvipdfm_*.map
are the ones that dvipdfmx should be using.

Considering that, the next thing to do will be to dump the required 
map files so that updmap will pick them up.

/etc/texmf/dvipdfm/dvipdfmx.cfg currently has:
f dvipdfm.map
f cid-x.map


which probably loads /var/lib/texmf/fonts/map/dvipdfm/updmap/dvipdfm.map, 
which on my system is symbolic link to 
/var/lib/texmf/fonts/map/dvipdfm/updmap/dvipdfm_ndl.map


With a strace of dvipdfmx run, I can verify that it's actually reading that file:

access("/etc/texmf/fonts/map/dvipdfm.map", R_OK) = -1 ENOENT (No such file or directory)
access("/etc/texmf/fonts/map/dvips/dvipdfm.map", R_OK) = -1 ENOENT (No such file or directory)
access("/etc/texmf/fonts/map/dvips/context/dvipdfm.map", R_OK) = -1 ENOENT (No such file or directory)
access("/var/lib/texmf/fonts/map/dvipdfm/updmap/dvipdfm.map", R_OK) = 0
stat("/var/lib/texmf/fonts/map/dvipdfm/updmap/dvipdfm.map", {st_mode=S_IFREG|0644, st_size=20198, ...}) = 0
open("/var/lib/texmf/fonts/map/dvipdfm/updmap/dvipdfm.map", O_RDONLY) = 4


The interesting entries that disappeared since Debian sarge system are:

$ grep -v ^$ /var/cache/pbuilder/build/18413/etc/texmf/dvipdfm/cid-x.map | grep -v ^%
omrml  UniJIS-UCS2-H Ryumin-Light
omgbm  UniJIS-UCS2-H GothicBBB-Medium
rml  H Ryumin-Light
gbm  H GothicBBB-Medium
rmlv V Ryumin-Light
gbmv V GothicBBB-Medium
bsmi@Big5@ ETen-B5-H bsmi00lp
bsmis@Big5@ ETen-B5-H bsmi00lp -s .167
bkai@Big5@ ETen-B5-H bkai00mp
bkais@Big5@ ETen-B5-H bkai00mp -s .167
bsmir@Big5@  ETen-B5-V  bsmi00lp
bsmirs@Big5@  ETen-B5-V  bsmi00lp -s .167
bkair@Big5@  ETen-B5-V  bkai00mp
bkairs@Big5@  ETen-B5-V  bkai00mp -s .167
bsmiv@Big5@  ETen-B5-V  bsmi00lp
bsmivs@Big5@  ETen-B5-V  bsmi00lp -s .167
bkaiv@Big5@  ETen-B5-V  bkai00mp
bkaivs@Big5@  ETen-B5-V  bkai00mp -s .167
gbsn@EUC@   GB-EUC-H   gbsn00lp
gbsns@EUC@  GB-EUC-H   gbsn00lp -s .167
gkai@EUC@   GB-EUC-H   gkai00mp
gkais@EUC@  GB-EUC-H   gkai00mp -s .167
gbsnr@EUC@  GB-EUC-V   gbsn00lp
gbsnrs@EUC@  GB-EUC-V   gbsn00lp -s .167
gkair@EUC@  GB-EUC-V   gkai00mp
gkairs@EUC@  GB-EUC-V   gkai00mp -s .167
gbsnv@EUC@  GB-EUC-V   gbsn00lp
gbsnvs@EUC@  GB-EUC-V   gbsn00lp -s .167
gkaiv@EUC@  GB-EUC-V   gkai00mp
gkaivs@EUC@  GB-EUC-V   gkai00mp -s .167


They probably need to be restored to somewhere updmap picks up.

The question is, am I on the right track?


regards,
	junich
-- 
dancer@{debian.org,netfort.gr.jp}   Debian Project



Reply to: