Re: [Inkscape-devel] [Inkscape-user] PostScript fonts print as Courier when Inkscape exports to EPS
Niall,
I am not the Latex expert. I am using Ubuntu and/or Sarge do.
Could you provide me some small document inserting the eps and the command how to start Latex I will investigate in this.
btw. You probably know PostScript does not support Unicode thats why Inkscape creates own "Subfonts" for each font before using in the document. This is the reason for the "-ISOLatin1" in the font name. The second PostScript issue is that it does not handle font names containing spaces. There have to be brackets around.
There will be no easy patch in the next future and you will be save if you convert fonts to strokes before. I will have an eye on that.
HTH,
Adib.
Niall Mansfield schrieb:
Adib,
Thanks for your message.
which Version of the Helvetica font do you use on your PC? I have found several versions from Adobe, Apple or some which stated "Converted from ... by ALLTYPE". Also there are .ttf and .otf
Good question.
I assumed that I was using PostScript fonts, but that may not be true -- your question forced me to look, and try and understand these things (which I don't pretend to do on Windows).
However:
all the fonts displayed in the Inkscape dialogs are TrueType.
but not all TrueType fonts are visible in Inkscape. (e.g. WingDings and WebDings) but about 95% of the TT fonts are visisble. The TT fonts are all .ttf extension. When I look at a sample of Helvetica Condensed, it says the foundry is Agfa Monotype Corporation.
no PostScript fonts are visible in Inkscape (even tho' they are visible in MS-Word, and other programs, and can be selected, displayed on screen, and printed ,without any problem). All our printers are PostScript.
Only other point that might be relevant (but I doubt it) is that I am copying all the .EPS files from the XP box to a Linux m/c where I am using them within LaTeX.
Regards, Niall
Adib Taraben wrote:
The second PostScript issue is that it does not handle font names containing spaces.
IIUC, the PostScript font name of a Type1 font does not have spaces.
See: "FontName" in the AFM file. If this name has spaces, the font is broken.
The same should be true of PostScript font names extracted from TrueType font files.
Where are the font names with spaces coming from?
James Richard Tyrer schrieb:
Adib Taraben wrote:
The second PostScript issue is that it does not handle font names containing spaces.
IIUC, the PostScript font name of a Type1 font does not have spaces.
See: "FontName" in the AFM file. If this name has spaces, the font is broken.
The same should be true of PostScript font names extracted from TrueType font files.
Where are the font names with spaces coming from?
This refers to the bug: 1668259 Win32 font problem using helvetica on PS output When printing e.g. "Helvetica Condensed" or under Windows "Times Roman".
Actually there are different implementations of helvetica in windows (ttf and otf) and I am not certain which implementation gives that font name.
However gv reads the files with no prob.
HTH, Adib.
participants (2)
-
Adib Taraben
-
James Richard Tyrer