Font problem

Christina Thiele cthiele at ccs.carleton.ca
Mon Sep 8 10:49:41 CEST 2003


Herbert Gintis writes:
>
> --=====================_1025082062==_.ALT
> Content-Type: text/plain; charset="us-ascii"; format=flowed
>
> I've used Y & Y successfully and without problem since 1999, but now I have
> one.

Which fonts had you purchased when you bought the v.2.2 upgrade? The
CM fonts (which would include lcircle) have to be purchased ... so if
you don't have a folder on your v.2.2 installation CD for the CM
fonts, then you'll need to contact the Y&Y office via
admin at yandy.com.  Or install them with your older CD ... I don't know
if the files will have changed all that much -- or even at all. My
lcircle fonts seem to mainly have a 9/24/98 date ...

But let's assume you did purchase the CM fonts ... There are two parts
to any font installation -- making the PS fonts available to both
Windows (for display) and to one's printer, and then making sure there
are matching .tfm files for TeX to use.

So, to check if all the font files for lcircle* has been installed, do
a search on lcircle*.* in the c: folder (that is, NOT just in
c:\yandy, which is where the TeX-specific .tfm files will be) BUT ALSO
up higher, to include c:\windows\fonts, which is where PS-specific
.pfb and .pfm files reside.

If you don't find lcircle* files in both places, then the font's not
been fully installed.

If you go to your CD, you should find a whole bunch of lcircle*.* font
files, all in the folder d:\LatxFont, including the .pfb and .pfm
files, which are needed for screen and printer.

So, as indicated on p.5 of the manual (which I've gotten used to
re-`reading' as c:\winnt for NT machines, and c:\windows for
Win2000/XP), `install the font' from the CD. I say `install the font'
because installation actually means that ALL the various files that a
given `font' needs are put into their proper place. We get so misled,
thinking one font = one file -- and that's just not the case.

Now, if I read pages 3 and 5 correctly, this means that, via Explorer
or My Computer, you open a list of all folders and files (make sure
`Details' is activated, under the `View' menu, so you can see the file
extensions, which you MUST be able to distinguish), click on the red-a
icons (lcircle*.pfb) on the CD, and then drag 'em over to the folder
c:\windows\fonts, I believe it's called.

> I also found out about this support group and how to access it. So far so
> good...

We try ;-))

> My problem: I use Windows XP.

We also find this a `problem' with the documentation, the bulk of
which dates from when Win2000/Pro (or XP as it now seems to be called)
were just being introduced. The documentation was still giving primacy
to Win95/98/NT, and then Win2000/XP materials were added in after. So
it's a pain in the *** for everyone who's upgraded to the newer OSs.

> A set of files I have compiled many times started giving me 50 or so error
> messages of the following form:
> GetTeXMetrics Failed at byte 148. Can't find font lcircle10 (0).
> Font Name: lcircle10 REGULAR (Windows offers 'lcircle10'). Can't get
> TexMetrics at byte 148.
> This appears to be in response to the following TeX code:
> \begin{picture}(83.00,70.00)
> \put(20.18,38.35){\circle*{1.20}}
> When I use Window's character map, lcircle10 comes up fine.
> The file prints fine, also, but the screen version is screwed up.

The Technical Addendum has a section on font file formats (section
2.2), which lists the various file extentions and what they contains
(p.4). On p.5, I find this:

   PFB and PFM files are required for viewing in DVIWindo, and both
   are required for printing from DVIWindo using a Windows Postscript
   driver. DVIPSONE, on the other hand, requires only the PFB files.

I believe that when one installs the .pfb file via the drag-and-drop
method for Win2000/XP (and via ATM for the older OSs), that the .pfm
file then automatically is plopped (= installed) into its proper
folder as well on the machine.

So that's it for the PS-specific files. Now to check that the
corresponding TeX-specific .tfm file(s) are in place down in the
c:\yandy tree. If they're there, then you should be able to run your
files again.

> The suggestions in the readme.txt for dviwindo (whose existence was kindly
> supplied to me by Chrstina Thiele) are not relevant for XP. Win.ini has no
> fonts listed, atm.ini does not exist, and there are only a few idiotic .fot
> files on my hard drive. Page 5 of the Y and Y little manual are equally
> irrelevant. There is no c:\winnt folder.

Yeah ... I know. My impression is that that section wasn't properly
revised for Win2000 -- where it says the \fonts folder `under \winnt',
that should read `under `window'. I noticed this difference back in
February or March, I think it was, when I was helping someone else and
found `c:\windows\fonts' in their dviwindo.ini file instead of
`c:\winnt\fonts'. As I said, I've now gotten used to mentally
replacing `winnt' references to `windows' whenever a Win2000/XP query
comes up ... Make the correction in your documentation, if you'd like,
to remind you of the right location on your machine.

> I vaguely recall something special about lcircle---that it used to be part
> of LaTeX and then was dropped. But I have no idea what this refers to.
> The only thing I did to my computer that could possibly be relevant to this
> problem was to install Scientific Word, and then uninstall it about two
> weeks later.

Normally, that shouldn't affect things but ... well ... we'll find
out, eh? ;-)

You know ... even if you do find all the right files, why don't you
just go ahead and re-install them, just to make sure that perhaps the
places where font registration is set up get the right info.

And another thing -- even though p.5 is writing about NT (last
para. in section 2.2), see if you have this `setupttf.exe' file around
(either on the machine or on the CD) and see if you can run it. It's
been known to help unkink mangled font info.

> The larger problem seems to be that there are no general directions for
> handling font problems in XP.

Agreed! See above for explanation of lack of XP-specific help.

> Help with this problem would be appreciated.

Fortunately, there are quite a few XP users on this list so if the
above still does not resolve your problem, then perhaps someone else
will spot the specific error. But it does seem to me that your error
message is saying that there are font files that can't be found, so
surely we should be able to locate where all files normally reside,
and then get 'em in there, via the proper installation procedures.

Oh, one more suggestion: take a CM font that's not causing any problem
(say, cmmi*), and locate all its font files in c: -- if they're all
there and you have no problems with screen display, then that's a
model to follow for your lcircle* font.

> Best,

And to you. It's hard to debug via e-mail but at least it's someone
else to talk to ;-)

Now, if none of the above helps you, then maybe the best is to ask you
to post a short sample .tex file, along with _your_ .log file, so we
can see what the input/output are from your machine. Then if someone
else takes your source file, they can compare their .log file with
yours to see where things differ. But we aren't there yet ...

Good luck with this round ;-)

> Herb Gintis
>
> ...

Ch.





More information about the yandytex mailing list