Red Hat Bugzilla – Bug 838345
Latex2RTF needs a correct GS_FONTPATH environment variable to convert .tex files with pslatex package
Last modified: 2012-08-01 19:38:24 EDT
Created attachment 596894 [details]
Description of problem:
When you try to convert a .tex file that includes the pslatex package and has equations into a .rtf file using latex2rtf and -M12, you will have errors in the equations conversion because GS_FONTPATH is not set correctly.
pslatex package (http://ctan.org/pkg/pslatex) makes LaTeX use the standard PostScript fonts, like Times. The -M12 in latex2rtf convert inline and displayed equations to .png. Thus, if a .tex file has equations and pslatex packages, then the conversion of such equations into .png file will fail with "invalid font" errors, because the default ghostscript fonts path in Fedora are not set (GS_FONTPATH environment variable).
Version-Release number of selected component (if applicable):
I'm using latex2rtf 2.2.0 (Fedora 17)
I could reproduce this bug every time I try to convert a .tex that has equations and pslatex package into a .rtf using latex2rtf with -M12.
Steps to Reproduce:
1. Create a .tex file with inline and displayed equations and pslatex package (or download test.tex attached)
2. Compile with pdflatex (everything should work fine)
3. Try to convert to a .rtf file using latex -M12 -D300 <NAME>.tex
You will see errors about 'invalid font' (see attached error log for the conversion of test.tex).
The conversion should work correctly.
The problem is gone if you use the command:
GS_FONTPATH=/usr/share/fonts/default/Type1/ latex2rtf -M12 -D300 <NAME>.tex
Created attachment 596895 [details]
Error output when GS_FONTPATH is not set
Created attachment 596896 [details]
.rtf file generated when GS_FONTPATH is not set
Created attachment 596897 [details]
.rtf file generated when GS_FONTPATH is set
It turns out that the problem was with infinality patches in fontconfig. It was blocking Type1 fonts because it does not render well. When I remove this block, everything works. Thus, it isn't a Fedora issue. Sorry for that.
This bug can be closed.