Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Ghostscript/VFlib not finding font
- To: tlug@example.com
- Subject: Re: tlug: Ghostscript/VFlib not finding font
- From: Matt Gushee <matt@example.com>
- Date: Wed, 10 Feb 1999 13:16:56 +0900
- Content-Type: text/plain; charset=US-ASCII
- In-Reply-To: <19990210125206.B17878@example.com>
- References: <199902090736.QAA10439@example.com><19990209185414F.andy@example.com><19990210125206.B17878@example.com><14017.1054.140148.773849@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
Frank Bennett writes: > On Tue, Feb 09, 1999 at 06:54:14PM +0900, Andrew S. Howell wrote: > > > Your postscript should have some setfont postscript operators that are > > trying to select some Japanese font. Your mission, should you decide > > to accept it, is to dive head first into the postscript and figure out > > what fonts its looking for. > > This info is contained in kconfig.ps, in the VFlib or kanji subdirectory > of your ghostscript data directory, whereever that happens to be located. > > The entry looks like this: > > /Ryumin-Light 4300000 (min) VFlibkanji > /GothicBBB-Medium 4300200 (goth) VFlibkanji > > "min" and "goth" are the alias names it will look for. So you just leave > this alone, and edit the entries in vfontcap. The problem is that > your system might be looking for vfontcap in lots of different locations. No, finding vfontcap isn't the problem. But the values of 'min' and 'goth' are. Anyway, it's good to know about 'kconfig.ps'. I knew it was there, but hadn't seriously looked at it and didn't know if it was the right file to edit. > But pointing VFlib at the Wadalab fonts worked, according to Matt? I'm afraid that was a misleading statement on my part. What actually happened was that VFlib stopped complaining about the 'min' font *when it wasn't needed* -- e.g., for English documents. Pointing it at the Wadalab fonts does *not* work, I found ... at least, not the way I did it. I later got previewing to work with a TrueType Mincho & Gothic -- but I haven't managed to print with those yet. Stephen J. Turnbull writes: > I beleive that VFlib is supposed to handle _all_ fonts in a unified > way. Yes, I think version 3 handles all fonts. Version 2 handles only a limited set of Japanese fonts ... and as I review the docs again, it appears that doesn't include Type 1 fonts (and yes, I tried to build Ghostscript against version 3, but the interface seems to be completely incompatible). So maybe what I need to do is to prevent GS from calling VFlib when Wadalab Type 1 fonts are called for ... would kconfig.ps be the place to do that? Or maybe substitute the TrueType versions? Cheers, Matt Gushee Oshamanbe, Hokkaido ------------------------------------------------------------------- Next Technical Meeting: February 13 (Sat), 12:30 place: Temple Univ. ** presentation: XEmacs, by Steven Baur and Martin Buchholz Next Nomikai: March 19 (Fri), 19:30 Tengu TokyoEkiMae 03-3275-3691 ------------------------------------------------------------------- more info: http://tlug.linux.or.jp Sponsor: PHT
- Follow-Ups:
- Re: tlug: Ghostscript/VFlib not finding font
- From: Frank Bennett <bennett@example.com>
- References:
- Re: tlug: Ghostscript/VFlib not finding font
- From: Matt Gushee <matt@example.com>
- Re: tlug: Ghostscript/VFlib not finding font
- From: "Andrew S. Howell" <andy@example.com>
- Re: tlug: Ghostscript/VFlib not finding font
- From: Frank Bennett <bennett@example.com>
- Re: tlug: Ghostscript/VFlib not finding font
- From: "Stephen J. Turnbull" <turnbull@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: Ghostscript/VFlib not finding font
- Next by Date: Re: tlug: Ghostscript/VFlib not finding font
- Prev by thread: Re: tlug: Ghostscript/VFlib not finding font
- Next by thread: Re: tlug: Ghostscript/VFlib not finding font
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links