continuing (pdf) font frustrations
continuing (pdf) font frustrations
am 08.10.2004 19:09:58 von James Miller
Sorry to beat a dead horse over these font problems, but it's really
bothering me and interfering with my work. I've posted on this before,
but the issue remains unresolved. Previously I complained about a couple
of apps as having some font problems: browsers (Mozilla and Opera) and pdf
viewers (Xpdf and GV). Well, I need to reduce the field in this post:
all X apps display fonts just fine so far as I can tell - except for the
pdf viewers. My problem now focuses on an inability to view certain pdf
files. What I mean by "inability to view" is that the program opens a
file, but where text should be in the file there is nothing - just
white/blank space. That's what Xpdf does. GV does the same, but at least
gives an error message. I cannot really say what precipitated this
problem: it could be some chmod-ing I did in some font directories
recently, could be the result of switching to an apt-get dist-upgrade
system administration policy I recently adopted for this Debian Sid system
(had been selectively upgrading apps previously) - I just can't say with
any certainty. This surely won't help you help me, but I just have to be
up front about that. With dist-upgrade'ing I've gotten dialogues about
defoma and pango and other font programs/options that I do not understand,
so I blindly choose. I suppose changing one of those options from the way
I initially set up the system could be utlimately at the root of the
problem. But the problem is here and needs to be resolved. As means to
addressing the problem, I've tried the following: ckecking font files and
dirs for proper permissions setting (they seem to be fine), uninstalling
and reinstalling Xpdf (and related progs), GV and reinstalled gsfonts.
These measures did not help: the problem of blank pdf's or blank portions
persists. I need to mention that not all pdf documents are affected: some
show the text as normal. But others do not. Also relevant: ps2pdf no
longer works, but exits with error messages. Here is the error message I
get from GV:
---------------------------------------------------------
Error: /invalidfontESP Ghostscript 7.07.1: Unrecoverable error, exit
code 1
in findfont
Operand stack:
--dict:8/8(L)-- F12 1 --dict:8/8(L)-- --dict:8/8(L)--
--dict:10/10(L)-- Helvetica-Narrow Font Helvetica-Narrow 487763
Helvetica-Narrow --nostringval-- Helvetica-Narrow
NimbusSanL-ReguCond (NimbusSanL-ReguCond) NimbusSanL-ReguCond
(NimbusSanL-ReguCond) NimbusSanL-ReguCond
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1
3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval--
--nostringval-- --nostringval-- 2 %stopped_push --nostringval--
--nostringval-- --nostringval-- --nostringval-- %array_continue
--nostringval-- false 1 %stopped_push --nostringval--
%loop_continue --nostringval-- --nostringval-- --nostringval--
--nostringval-- 7 9 %oparray_pop 8 9 %oparray_pop
--nostringval-- --nostringval-- --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 11 10 %oparray_pop
--nostringval-- --nostringval-- --nostringval-- 5 -1 1
--nostringval-- %for_neg_int_continue --nostringval--
--nostringval--
Dictionary stack:
--dict:1055/1417(ro)(G)-- --dict:0/20(G)-- --dict:73/200(L)--
--dict:97/127(ro)(G)-- --dict:229/230(ro)(G)-- --dict:20/24(L)--
--dict:4/6(L)-- --dict:20/31(L)-- --dict:10/13(L)--
--dict:17/17(ro)(G)-- --dict:1055/1417(ro)(G)--
Current allocation mode is local
Last OS error: 2
------------------------------------------------------------ --
From ps2pdf, I get the following error:
------------------------------------------------------------ -
Error: /invalidfont in findfont
Operand stack:
HeadFont Helvetica Font Helvetica 362928 Helvetica
--nostringval-- Courier NimbusMonL-Regu (NimbusMonL-Regu)
NimbusMonL-Regu (NimbusMonL-Regu) NimbusMonL-Regu
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3
%oparray_pop 1 3 %oparray_pop .runexec2 --nostringval--
--nostringval-- --nostringval-- 2 %stopped_push --nostringval--
--nostringval-- 2 3 %oparray_pop 3 3 %oparray_pop
--nostringval-- --nostringval-- --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 6 4 %oparray_pop
--nostringval-- --nostringval-- --nostringval-- 5 -1 1
--nostringval-- %for_neg_int_continue --nostringval--
--nostringval--
Dictionary stack:
--dict:1055/1417(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)--
--dict:17/17(ro)(G)-- --dict:1055/1417(ro)(G)--
Current allocation mode is local
Last OS error: 2
Current file position is 6259
------------------------------------------------------------ --
The beginning of each - "Error: /invalidfont in findfont" - seems relevant
to me. Doesn't this mean that, since it can't find or use one or more
fonts, that the program is aborting? What can I do to check that these
fonts are present and are fine? I can use Helvetica and Courier under
OOo, for example. Nimbus does not show up as an option there, though.
In Abiword nimbus fonts of various sorts show up in the font selection
menu, but trying to select one of them for use causes the program to crash
(summarily disappear from the screen). Maybe this is where the problem
lies? Please, any ideas on addressing or resolving this problem will be
appreciated.
Thanks for any input on this.
James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Re: continuing (pdf) font frustrations
am 08.10.2004 20:05:59 von Ray Olszewski
At 12:09 PM 10/8/2004 -0500, James Miller wrote:
>Sorry to beat a dead horse over these font problems, but it's really
>bothering me and interfering with my work. I've posted on this before,
>but the issue remains unresolved. Previously I complained about a couple
>of apps as having some font problems: browsers (Mozilla and Opera) and pdf
>viewers (Xpdf and GV). Well, I need to reduce the field in this post:
>all X apps display fonts just fine so far as I can tell - except for the
>pdf viewers. My problem now focuses on an inability to view certain pdf
>files. What I mean by "inability to view" is that the program opens a
>file, but where text should be in the file there is nothing - just
>white/blank space. That's what Xpdf does. GV does the same, but at least
>gives an error message.
OK, James. Fair enough. But let's then try to pin things down a bit more.
For now, let's stay with xpdf for tests.
1. Just to eliminate possible rookie error ... do you know that the
"certain" .pdf files are themselves good? Can you read them on Windows
using Acrobat, or could you previously read it on this system? You've
almost surely checked this, but your problem has gotten so messy that I
don't want to skip past even "obvious" questions. (If you have a small one,
consider sending it to me off-list, and I'll make sure I can display it here.)
2. How have you been starting xpdf? Try starting it through an xterm, so
you can either see or redirect STDOUT and STDERR ... see if xpdf is telling
you anything about the problem that way.
3. Check for a dependency problem. The easiest way is to remove, then
install the package, that is ...
apt-get remove xpdf
apt-get install xpdf
From what you wrote below, it appears you already tried his. Oh well.
4. Is there anything that systematically distinguishes the "certain" .pdf
files that have problem from others that, presumably, do not? Might you be
missing some specific font that they need, for example? The gv output you
wrote below seems to suggest this, in that the error comes from "findfont".
(I don't use gs here, so I'm not familiar with the form of its error
output, leving me to guess that
"Helvetica Font Helvetica 362928 Helvetica" *might* be the missing
font. See what "fc-list" tells you.
5. Or there might be some lost "mapping" between a font you do have and
Helvetica. (I say this because I don't have a Helvetica on my system
either, and I can't find a .deb that provides a true Helvetica.) Check that
you have tthe full Nimbus font set, for example (that appears to be what
xpdf and gs want to use for Helvetica):
waverly:/proc# fc-list |grep Nimbus |grep Sans
Nimbus Sans L:style=Regular Italic
Nimbus Sans L Condensed:style=Regular
Nimbus Sans L:style=Bold
Nimbus Sans L Condensed:style=Regular Italic
Nimbus Sans L:style=Regular
Nimbus Sans L:style=Bold Italic
Nimbus Sans L Condensed:style=Bold
Nimbus Sans L Condensed:style=Bold Italic
Also make sure you have the deforma symlinks to these fonts present:
waverly:/proc# find / -name *imbus*
/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-ReguItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusMonL-Bold.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldCond.pfb
/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-MediItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-Medi.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-Regu.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-Bold.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguCond.pfb
/var/lib/defoma/fontconfig.d/N/NimbusMonL-BoldObli.pfb
/var/lib/defoma/fontconfig.d/N/NimbusMonL-ReguObli.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguCondItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldCondItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-Regu.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusMonL-Regu.pfb
(These are all symlinks to various actual fonts
in /usr/share/fonts/type1/gsfonts/ )
6. With respect to defoma and its kin, did you ever "blindly choose"
something other than the recommended default? Debian is not really idiot
proof, but its default choices are pretty good.
> I cannot really say what precipitated this
>problem: it could be some chmod-ing I did in some font directories
>recently, could be the result of switching to an apt-get dist-upgrade
>system administration policy I recently adopted for this Debian Sid system
>(had been selectively upgrading apps previously) - I just can't say with
>any certainty. This surely won't help you help me, but I just have to be
>up front about that. With dist-upgrade'ing I've gotten dialogues about
>defoma and pango and other font programs/options that I do not understand,
>so I blindly choose. I suppose changing one of those options from the way
>I initially set up the system could be utlimately at the root of the
>problem. But the problem is here and needs to be resolved. As means to
>addressing the problem, I've tried the following: ckecking font files and
>dirs for proper permissions setting (they seem to be fine), uninstalling
>and reinstalling Xpdf (and related progs), GV and reinstalled gsfonts.
>These measures did not help: the problem of blank pdf's or blank portions
>persists. I need to mention that not all pdf documents are affected: some
>show the text as normal. But others do not. Also relevant: ps2pdf no
>longer works, but exits with error messages. Here is the error message I
>get from GV:
>
>---------------------------------------------------------
> Error: /invalidfontESP Ghostscript 7.07.1: Unrecoverable error, exit
>code 1
> in findfont
>Operand stack:
> --dict:8/8(L)-- F12 1 --dict:8/8(L)-- --dict:8/8(L)--
>--dict:10/10(L)-- Helvetica-Narrow Font Helvetica-Narrow 487763
>Helvetica-Narrow --nostringval-- Helvetica-Narrow
>NimbusSanL-ReguCond (NimbusSanL-ReguCond) NimbusSanL-ReguCond
>(NimbusSanL-ReguCond) NimbusSanL-ReguCond
>Execution stack:
> %interp_exit .runexec2 --nostringval-- --nostringval--
>--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
>--nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1
>3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval--
>--nostringval-- --nostringval-- 2 %stopped_push --nostringval--
>--nostringval-- --nostringval-- --nostringval-- %array_continue
>--nostringval-- false 1 %stopped_push --nostringval--
>%loop_continue --nostringval-- --nostringval-- --nostringval--
>--nostringval-- 7 9 %oparray_pop 8 9 %oparray_pop
>--nostringval-- --nostringval-- --nostringval-- --nostringval--
>--nostringval-- false 1 %stopped_push 11 10 %oparray_pop
>--nostringval-- --nostringval-- --nostringval-- 5 -1 1
>--nostringval-- %for_neg_int_continue --nostringval--
>--nostringval--
>Dictionary stack:
> --dict:1055/1417(ro)(G)-- --dict:0/20(G)-- --dict:73/200(L)--
>--dict:97/127(ro)(G)-- --dict:229/230(ro)(G)-- --dict:20/24(L)--
>--dict:4/6(L)-- --dict:20/31(L)-- --dict:10/13(L)--
>--dict:17/17(ro)(G)-- --dict:1055/1417(ro)(G)--
>Current allocation mode is local
>Last OS error: 2
>----------------------------------------------------------- ---
>
> >From ps2pdf, I get the following error:
>
>----------------------------------------------------------- --
>Error: /invalidfont in findfont
>Operand stack:
> HeadFont Helvetica Font Helvetica 362928 Helvetica
>--nostringval-- Courier NimbusMonL-Regu (NimbusMonL-Regu)
>NimbusMonL-Regu (NimbusMonL-Regu) NimbusMonL-Regu
>Execution stack:
> %interp_exit .runexec2 --nostringval-- --nostringval--
>--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
>--nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3
>%oparray_pop 1 3 %oparray_pop .runexec2 --nostringval--
>--nostringval-- --nostringval-- 2 %stopped_push --nostringval--
>--nostringval-- 2 3 %oparray_pop 3 3 %oparray_pop
>--nostringval-- --nostringval-- --nostringval-- --nostringval--
>--nostringval-- false 1 %stopped_push 6 4 %oparray_pop
>--nostringval-- --nostringval-- --nostringval-- 5 -1 1
>--nostringval-- %for_neg_int_continue --nostringval--
>--nostringval--
>Dictionary stack:
> --dict:1055/1417(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)--
>--dict:17/17(ro)(G)-- --dict:1055/1417(ro)(G)--
>Current allocation mode is local
>Last OS error: 2
>Current file position is 6259
>----------------------------------------------------------- ---
>
>The beginning of each - "Error: /invalidfont in findfont" - seems relevant
>to me. Doesn't this mean that, since it can't find or use one or more
>fonts, that the program is aborting? What can I do to check that these
>fonts are present and are fine? I can use Helvetica and Courier under
>OOo, for example. Nimbus does not show up as an option there, though.
>In Abiword nimbus fonts of various sorts show up in the font selection
>menu, but trying to select one of them for use causes the program to crash
>(summarily disappear from the screen). Maybe this is where the problem
>lies? Please, any ideas on addressing or resolving this problem will be
>appreciated.
>
>Thanks for any input on this.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Re: continuing (pdf) font frustrations
am 08.10.2004 21:12:46 von James Miller
On Fri, 8 Oct 2004, Ray Olszewski wrote:
Thanks for your response, Ray.
> 1. Just to eliminate possible rookie error ... do you know that the
> "certain" .pdf files are themselves good? Can you read them on Windows
> using Acrobat, or could you previously read it on this system? You've
> almost surely checked this, but your problem has gotten so messy that I
> don't want to skip past even "obvious" questions. (If you have a small one,
> consider sending it to me off-list, and I'll make sure I can display it here.)
The files (the text within them) were previously readable, whereas now
only the graphics portions of them are visible. I've selected two for
testing: one is a webpage I printed to file (.ps) then used ps2pdf to
convert to a pdf. The other is a city bus map I downloaded that was
created eslewhere: neither show any text where they used to - only blank
space around or within the graphics. I've just checked them using
Acroread under Win (VMware install of Win 98) and they both display
normally there: all text appears and is legible. On Debian, I get only
graphics but no text. I'll send you the smaller of the two offlist (the
webpage I printed to .ps file, then converted to pdf) so you can check it
as well: the other one is fairly large - nearly 1 MB.
> 2. How have you been starting xpdf? Try starting it through an xterm, so
> you can either see or redirect STDOUT and STDERR ... see if xpdf is telling
> you anything about the problem that way.
Been starting it via the menu Debian gives. When I start it from an xterm
and open a problematic file, I get the following in STDOUT (in the
terminal, right?):
me@mycomputer:~$ xpdf
Error: Couldn't create a font for 'Times-Roman'
Error: Couldn't create a font for 'Times-Roman'
Error: Couldn't create a font for 'Times-Roman'
Error: Couldn't create a font for 'Times-Roman'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica-Bold'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica-Bold'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica-Bold'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Times-Bold'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Times-Bold'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
Error: Couldn't create a font for 'Helvetica'
> 3. Check for a dependency problem. The easiest way is to remove, then
> install the package, that is ...
>
> apt-get remove xpdf
> apt-get install xpdf
>
> From what you wrote below, it appears you already tried his. Oh well.
Yep, tried that. Except I'm using Synaptic now, so I did it through the
gui.
> 4. Is there anything that systematically distinguishes the "certain" .pdf
> files that have problem from others that, presumably, do not? Might you be
> missing some specific font that they need, for example? The gv output you
> wrote below seems to suggest this, in that the error comes from "findfont".
> (I don't use gs here, so I'm not familiar with the form of its error
> output, leving me to guess that
> "Helvetica Font Helvetica 362928 Helvetica" *might* be the missing
> font. See what "fc-list" tells you.
I'm guessing it's a missing font problem, yes. I don't see Helvetica in
the list fc-list produces, and "fc-list |grep Helvetica" does not return
any results. Could that be the problem? Helvetica is definitely
available and useable in OpenOffice.org, but I don't see it listed in
Abiword's font menu.
> 5. Or there might be some lost "mapping" between a font you do have and
> Helvetica. (I say this because I don't have a Helvetica on my system
> either, and I can't find a .deb that provides a true Helvetica.) Check that
> you have tthe full Nimbus font set, for example (that appears to be what
> xpdf and gs want to use for Helvetica):
>
> waverly:/proc# fc-list |grep Nimbus |grep Sans
> Nimbus Sans L:style=Regular Italic
> Nimbus Sans L Condensed:style=Regular
> Nimbus Sans L:style=Bold
> Nimbus Sans L Condensed:style=Regular Italic
> Nimbus Sans L:style=Regular
> Nimbus Sans L:style=Bold Italic
> Nimbus Sans L Condensed:style=Bold
> Nimbus Sans L Condensed:style=Bold Italic
I get
Nimbus Sans L:style=Regular Italic
Nimbus Sans L:style=Bold
Nimbus Sans L:style=Regular
Nimbus Sans L:style=Bold Condensed
Nimbus Sans L:style=Bold Italic
Nimbus Sans L:style=Regular Condensed Italic
Nimbus Sans L:style=Regular Condensed
Nimbus Sans L:style=Bold Condensed Italic
> Also make sure you have the deforma symlinks to these fonts present:
>
> waverly:/proc# find / -name *imbus*
> /var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-ReguItal.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusMonL-Bold.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldCond.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-MediItal.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-Medi.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusSanL-Regu.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldItal.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusSanL-Bold.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguCond.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusMonL-BoldObli.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusMonL-ReguObli.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguCondItal.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldCondItal.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-Regu.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguItal.pfb
> /var/lib/defoma/fontconfig.d/N/NimbusMonL-Regu.pfb
>
> (These are all symlinks to various actual fonts
> in /usr/share/fonts/type1/gsfonts/ )
Here's what I get doing "find / -name *Nimbus*":
/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-ReguItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusMonL-Bold.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldCond.pfb
/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-MediItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-Medi.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-Regu.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguCond.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-Bold.pfb
/var/lib/defoma/fontconfig.d/N/NimbusMonL-BoldObli.pfb
/var/lib/defoma/fontconfig.d/N/NimbusMonL-ReguObli.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguCondItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldCondItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-Regu.pfb
/var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguItal.pfb
/var/lib/defoma/fontconfig.d/N/NimbusMonL-Regu.pfb
> 6. With respect to defoma and its kin, did you ever "blindly choose"
> something other than the recommended default? Debian is not really idiot
> proof, but its default choices are pretty good.
It's quite possible. My policy is to accept the defaults, but sometimes I
think: "what the heck, why not try an alternative? Maybe I'll learn
something" (all this time the good angel on my right shoulder is saying
"you'll hose your system, bub. Be wise, and stick with convetion") But
again I understand so poorly what Defoma and Pango are and do that it
wasn't really a conscious decision, so I have no clear recollection.
Sorry - I know that doesn't help.
Again, thanks.
James
(Rest of previous content deleted)
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Re: continuing (pdf) font frustrations
am 08.10.2004 23:55:12 von Ray Olszewski
The added info you provide below, along with my quick check of the file you
sent to me offlist, all says you are right that you have a font problem.
And I am probably right that it is specific to Helvetica (or almost
specific to it ... the errors you list below indicate a bit of a problem
with Times Roman as well).
OK. Now what? I already made a few guesses, but they proved (by your
responses) to be off the mark.
1. The required font files *are* present on your system.
2. The required deforma symlinks *are* present on your system.
So, the rest of the steps ...
3. Are the fonts all mode 644? (The actual fonts
in /usr/share/fonts/type1/gsfonts/, not the symlinks). Probably; you said
you checked that already. And if other apps workm, that too indicates the
problem is specific to the PDF font corrspondences.
4. Is the file /etc/defoma/hints/gsfonts.hints present? It provides defoma
with the information that Helvetica is an "Alias" for the Nimbus fonts.
5. From looking over the man pages for defoma, I'd guess that it is worth
trying this:
defoma-font reregister-all /etc/defoma/hints/gsfonts.hints
(I didn't actually try this here, since I don't like to muck with a stable,
working system just to see what happens.) Try reading the man pages for
defoma and defoma-fonts yourself, though, before you decide if you want to
try this.
At 02:12 PM 10/8/2004 -0500, James Miller wrote:
>On Fri, 8 Oct 2004, Ray Olszewski wrote:
>
>Thanks for your response, Ray.
>
> > 1. Just to eliminate possible rookie error ... do you know that the
> > "certain" .pdf files are themselves good? Can you read them on Windows
> > using Acrobat, or could you previously read it on this system? You've
> > almost surely checked this, but your problem has gotten so messy that I
> > don't want to skip past even "obvious" questions. (If you have a small one,
> > consider sending it to me off-list, and I'll make sure I can display it
> here.)
>
>The files (the text within them) were previously readable, whereas now
>only the graphics portions of them are visible. I've selected two for
>testing: one is a webpage I printed to file (.ps) then used ps2pdf to
>convert to a pdf. The other is a city bus map I downloaded that was
>created eslewhere: neither show any text where they used to - only blank
>space around or within the graphics. I've just checked them using
>Acroread under Win (VMware install of Win 98) and they both display
>normally there: all text appears and is legible. On Debian, I get only
>graphics but no text. I'll send you the smaller of the two offlist (the
>webpage I printed to .ps file, then converted to pdf) so you can check it
>as well: the other one is fairly large - nearly 1 MB.
>
> > 2. How have you been starting xpdf? Try starting it through an xterm, so
> > you can either see or redirect STDOUT and STDERR ... see if xpdf is telling
> > you anything about the problem that way.
>
>Been starting it via the menu Debian gives. When I start it from an xterm
>and open a problematic file, I get the following in STDOUT (in the
>terminal, right?):
>
>me@mycomputer:~$ xpdf
>Error: Couldn't create a font for 'Times-Roman'
>Error: Couldn't create a font for 'Times-Roman'
>Error: Couldn't create a font for 'Times-Roman'
>Error: Couldn't create a font for 'Times-Roman'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica-Bold'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica-Bold'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica-Bold'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Times-Bold'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Times-Bold'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>Error: Couldn't create a font for 'Helvetica'
>
>
> > 3. Check for a dependency problem. The easiest way is to remove, then
> > install the package, that is ...
> >
> > apt-get remove xpdf
> > apt-get install xpdf
> >
> > From what you wrote below, it appears you already tried his. Oh well.
>
>Yep, tried that. Except I'm using Synaptic now, so I did it through the
>gui.
>
> > 4. Is there anything that systematically distinguishes the "certain" .pdf
> > files that have problem from others that, presumably, do not? Might you be
> > missing some specific font that they need, for example? The gv output you
> > wrote below seems to suggest this, in that the error comes from "findfont".
> > (I don't use gs here, so I'm not familiar with the form of its error
> > output, leving me to guess that
> > "Helvetica Font Helvetica 362928 Helvetica" *might* be the missing
> > font. See what "fc-list" tells you.
>
>I'm guessing it's a missing font problem, yes. I don't see Helvetica in
>the list fc-list produces, and "fc-list |grep Helvetica" does not return
>any results. Could that be the problem? Helvetica is definitely
>available and useable in OpenOffice.org, but I don't see it listed in
>Abiword's font menu.
>
> > 5. Or there might be some lost "mapping" between a font you do have and
> > Helvetica. (I say this because I don't have a Helvetica on my system
> > either, and I can't find a .deb that provides a true Helvetica.) Check that
> > you have tthe full Nimbus font set, for example (that appears to be what
> > xpdf and gs want to use for Helvetica):
> >
> > waverly:/proc# fc-list |grep Nimbus |grep Sans
> > Nimbus Sans L:style=Regular Italic
> > Nimbus Sans L Condensed:style=Regular
> > Nimbus Sans L:style=Bold
> > Nimbus Sans L Condensed:style=Regular Italic
> > Nimbus Sans L:style=Regular
> > Nimbus Sans L:style=Bold Italic
> > Nimbus Sans L Condensed:style=Bold
> > Nimbus Sans L Condensed:style=Bold Italic
>
>I get
>
>Nimbus Sans L:style=Regular Italic
>Nimbus Sans L:style=Bold
>Nimbus Sans L:style=Regular
>Nimbus Sans L:style=Bold Condensed
>Nimbus Sans L:style=Bold Italic
>Nimbus Sans L:style=Regular Condensed Italic
>Nimbus Sans L:style=Regular Condensed
>Nimbus Sans L:style=Bold Condensed Italic
>
> > Also make sure you have the deforma symlinks to these fonts present:
> >
> > waverly:/proc# find / -name *imbus*
> > /var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-ReguItal.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusMonL-Bold.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldCond.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-MediItal.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-Medi.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusSanL-Regu.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldItal.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusSanL-Bold.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguCond.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusMonL-BoldObli.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusMonL-ReguObli.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguCondItal.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldCondItal.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-Regu.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguItal.pfb
> > /var/lib/defoma/fontconfig.d/N/NimbusMonL-Regu.pfb
> >
> > (These are all symlinks to various actual fonts
> > in /usr/share/fonts/type1/gsfonts/ )
>
>Here's what I get doing "find / -name *Nimbus*":
>
>/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-ReguItal.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusMonL-Bold.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldCond.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-MediItal.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-Medi.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldItal.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusSanL-Regu.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguCond.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusSanL-Bold.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusMonL-BoldObli.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusMonL-ReguObli.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguCondItal.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusSanL-BoldCondItal.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusRomNo9L-Regu.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusSanL-ReguItal.pfb
>/var/lib/defoma/fontconfig.d/N/NimbusMonL-Regu.pfb
>
> > 6. With respect to defoma and its kin, did you ever "blindly choose"
> > something other than the recommended default? Debian is not really idiot
> > proof, but its default choices are pretty good.
>
>It's quite possible. My policy is to accept the defaults, but sometimes I
>think: "what the heck, why not try an alternative? Maybe I'll learn
>something" (all this time the good angel on my right shoulder is saying
>"you'll hose your system, bub. Be wise, and stick with convetion") But
>again I understand so poorly what Defoma and Pango are and do that it
>wasn't really a conscious decision, so I have no clear recollection.
>Sorry - I know that doesn't help.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Re: continuing (pdf) font frustrations
am 09.10.2004 00:45:52 von James Miller
On Fri, 8 Oct 2004, Ray Olszewski wrote:
> 3. Are the fonts all mode 644? (The actual fonts
> in /usr/share/fonts/type1/gsfonts/, not the symlinks). Probably; you said
> you checked that already. And if other apps workm, that too indicates the
> problem is specific to the PDF font corrspondences.
Ray, you're a genius. Or I'm an idiot. Or maybe a little of both.
Rechecking modes on those fonts in gsfonts (which were all 644, btw) got
me thinking about checking permissions on the gsfonts directory in which
they're located. I think I mentioned previously about having mistakenly
changed permissions on those font directories and having to go back and
repair that. Well, looks like I missed this one :(. Chalk up another one
for blatant newbie error. After changing the mode of that directory back
to what it should be (from 644 to 755), my pdf's are once again displaying
as normal in Xpdf. Thanks so much for sticking through this, Ray.
Without your help it would've taken alot longer to figure this out (if I
hadn't just finally broken down and done a reinstall). As Hal would say
Appreciate! James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs