Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/4.77 [ja/[Vine,RedHat]] (X11; U; Linux 2.4.2-2 i686) When dvips converts a TeX DVI file including Japanese, core dumped. Reproducible: Always Steps to Reproduce: 1.The file, foo.tex includes Japanese text. 2.platex foo.tex 3.dvips -o foo.ps foo.dvi Actual Results: dvips: Font rml not found, using cmr10 instead. Segmentation fault(core dumped) rml must be defined in the file, /usr/share/texmf/dvips/config/psfonts.map.
Please attach the file you are using so that I can test out a fix. Thanks.
Please see the patch file, teTeX-1.0-japanese-psfonts.patch, in tetex-1.0.7-15.src.rpm.
What about it? It is already applied. Please attach a tex file that I can use to reproduce the problem locally.
The file, psfonts.map, does not include lines of japanese.map. If we add the lines to psfonts.map, dvips works. \documentstyle{jarticle} \begin{document} Japanese F|K\8l \end{document}
If we run the command, /usr/share/texmf/dvips/config/updmap, the file, psfonts.map, is updated and the lines of the file, japanese.man, are included.
Please use the 'create a new attachment' link to attach the file you are using, since I can't reproduce the problem with that above fragment. I'd like to test a fixed package. Thanks.
Created attachment 17806 [details] LaTeX file including japanese text
This should be fixed in 1.0.7-17. Thanks!
Please confirm whether 1.0.7-17 makes things better or worse.
1.0.7-19 has reverted the change that caused updmap to be run during the build stage. I'm going to close this bug as WORKSFORME since I can't reproduce the original problem you were having. If you have more information you can tell me, please reopen this bug report. Thanks.
I still consider this a bug, and the "fix" in 1.0.7-19 only masks the real problem. In my case, I would like to use type1 fonts in preference of metafont, so I edit the appropriate section of /usr/share/texmf/dvips/config/updmap to say: ########################################################################### # Set to true to use postscript type1 versions for fonts with existing # metafont versions. ########################################################################### # type1_default=false type1_default=true and rerun updmap. I now have a non-functioning dvips. tetex-1.0.7-14 (as distributed with rh7.1) did not have this problem. Undoing the following patch (which supposedly fixes bug 32134, though bugzilla won't let me see it) in the SRPM fixes this: teTeX-1.0-japanese-psfonts-fix.patch IMO, The long-term fix should involve being able to fix japanese fonts in a way that doesn't break other things (like dvips).
The trouble is that if you undo that patch, pdftex complains because those psfonts.map don't have enough words on the line any more. :-( Yes, the correct solution would involve a psfonts.map that you could run updmap on and still have everything work. I don't know what the correct solution is though at this point. I _am_ deeply suspicious of the teTeX-1.0-japanese-psfonts-fix.patch patch, but I don't know what it should look like instead.
I rebuild tetex without the jap-psfonts-fix.patch and all my problems are gone: dvips works, updmap works, pdflatex works, pdftex works ok except for a few warnings: Warning: pdftex (file pdftex.map): invalid line in map file: `gbm GothicBBB-Med ium-H^^J' Warning: pdftex (file pdftex.map): invalid line in map file: `gbmv GothicBBB-Me dium-V^^J' Warning: pdftex (file pdftex.map): invalid line in map file: `rml Ryumin-Light- H^^J' Warning: pdftex (file pdftex.map): invalid line in map file: `rmlv Ryumin-Light -V^^J' (Is this what you were talking about?) Otherwise, I'm still of the opinion that the jap-psfonts-fix.patch in question is broke and should not be included. Of course, until a better patch comes along, it's your call to decide which bug is more important to fix: this one or bug #32134.
This should be fixed by 1.0.7-27. We have two dvips binaries now: dvips (normal) and pdvips (ptex-enabled).