http://bugzilla.suse.com/show_bug.cgi?id=897284 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ulrich.deiters@uni-koeln.de Flags| |needinfo?(ulrich.deiters@un | |i-koeln.de) --- Comment #21 from Johannes Meixner <jsmeix@suse.com> --- Perhaps I found a possible workaround to avoid the font mess: The basic idea behind is to make the EPS so that it does no longer need any font (also not any standard PostScript font). Ghostscript can be used to re-create a PostScript or EPS file from scratch in such a way which means all text will be drawn by emitting the glyph description directly into the page stream every time a glyph is used. For most fonts this will result in paths, for bitmap fonts it will result in bitmaps. Note that the output will be larger, slower to process, the text rendering will be less consistent and, particularly at lower resolution, of poorer quality. See the somewhat related mail thread about "pswrite and NOPLATFONTS" on the gs-devel@ghostscript.com mailing list - but I am really not an expert in this area so that I could misunderstand something. I use Ghostscript version 9.15 (from the openSUSE build service development project "Printing") and for me it worked by using the epswrite device without any parameters: # gs -sDEVICE=epswrite -dBATCH -dNOPAUSE \ -sOutputFile=diagram.epswrite.eps diagram.eps When I exchange in doc.ps the included diagram.eps by my new diagram.epswrite.eps and save the result in doc.with_diagram.epswrite_eps.ps then # gs -r75 doc.with_diagram.epswrite_eps.ps shows the Greek DELTA character. Ulrich Deiters, perhaps you can make your EPS files in a similar way to avoid any kind of font mess. Note that depending on the Ghostscript version it may vary if -sDEVICE=epswrite and/or -sDEVICE=eps2write produce output that does no longer need any font - you may have to use further parameters to enforce that kind of output. Ulrich Deiters, could you try it out and provide feedback whether or not it is a usable workaround for you? -- You are receiving this mail because: You are on the CC list for the bug.