Re: Fonts

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

sev-engel wrote:


There is a known problem with certain video cards that can cause this problem. It's particularly prevalent on certain NVidea cards, particularly the GeForce 9100. This also explains why you're having different results on different pc's. The problem affects Type 1 fonts and Type 1 flavor Open Type fonts such as all of Adobe's OTF fonts.

There was a very long thread on this topic in some font or typography forum late last year or early this year, but right now I can't find it :(

Here is one solution that has worked:

===============================================================
Good news. Nvidia has identified the problem and provided a fix. The way it was explained to me, Windows expects the device driver to be a certain size (maximum). In this case, the nvidia driver is slightly larger than expected. A simply registry entry will resolve the issue in WinXP (the issue doesn't occur in Vista).

To resolve the problem, do the following:

Open the registry editor (regedit)

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Add a new REG_DWORD entry called SessionImageSize with a value (decimal) of 20

Reboot

====================================================================


It's also always a good idea to have the latest drivers for your video card - from either your pc manufacturer or, preferably the video card maker.


Thanks for that hint towards the printingfonts discussion group, I was not aware of it and will cross-post this message.






As to your questions: All fonts that would not become installed were .otf type fonts (actually give aways from Adobe upon registration of CS3). They include the GaramondPremierPro and the HypatiaSansPro families. Installation was tried via Start>System>Fonts (I am translating this here from German and hope that you get an idea of what I mean since I do not remember the precise English denominations). In the fonts directory you have the option to "install new fonts". Upon doing so, I get an error message like "file damaged" - which clearly is not the case since exactly these files behave well on my other xpsp3 pc. Upon double clicking the font file directly, "working fonts" show up in a window just to indicate how they look, but the "damaged" fonts are then said to be an invalid font file. Now I wonder what that "invalidity" is due to, since, as I mentioned, these very same font files do well on other pc's. I should like to mention that I obtained new font files from Adobe ( assuming that their use might be restricted somehow), but to absolutely no avail: They behave exactly as the "older" ones (and are identical, binary wise). "Character" wrote:


sev-engel wrote:


With a brand new installed xpsp3/office 2007 I cannot install some fonts with the following error messages depending on whether I install them via font managament or just double click the font file:

...this font cannot get installed. It may be damaged. Request a new file at your suppliers.

This file is not a valid font file.

Now, these very same files DO install on another xpsp3/office 2007 pc, they can't be damaged hence, right? Also I did obtain new files from the manufacturer but the error message remains the same.

Thanks for your help.

Siggi Engelbrecht

A better forum for this question would be
microsoft.public.word.printingfonts

Whether here or there, please give some additional information:
Specifically,
What kind of fonts are they (.ttf, .pfb/.pfm, .otf or other)
A couple of names of the fonts and their vendors.
Exactly how are you installing them? XP has no built-in font management - are you using a third-party font manager or installing via control panel/fonts/file/install new font or just dragging the font files into C:/windows/fonts?

- Character

.

Relevant Pages