lkpfour.blogg.se

Sabon lt std history
Sabon lt std history




sabon lt std history

We are getting font character "Glyphs replacing other characters"Ĭharacters that have been causing the issues. I have been having an issue with Indesign and PDF files ist file out as well as clearing the system font caches. We are placing a font folder for the jobs into the application>Indesign cs5 > fonts folderīefore we load the fonts to this location we clear the.

sabon lt std history

We are not using any font managment tools at present. This bug has wasted plenty of money so far. Even with the presence of a corrupted font cache, I could not get CS3 to have the same problem. I would like Adobe to analyze this and discover what the difference was between CS3 and CS5 that caused this error to occur. We are a printing company and we are loading client's collected fonts all the time, and so we will have lots of opportunity for corrupted font caches. This is a problem that I don't think most users will run into, as they tend to have one set of fonts they have purchased, loaded, and use commonly. If you turn off ligatures, the problem goes away, but so do the good ligatures. Open the PDF on the website and check out the sticky notes in it.Įverywhere the letters eh and ek occur, ID CS5 replaces them automatically with either a strange symbol or an "fi" ligature. We have not been able to repeat it on the same machine with a corrupt font with InDesign CS3. We can only get this to occur in InDesign CS5 on Macintosh, on a machine with a corrupt font cache. Has anyone seen this problem or know what causes it? What preventative measures can be done to keep it from occurring other that manually turning off ligatures on all text in all InDesign jobs? If you aren't looking for it, you will not notice that it has changed. You load up the fonts, you open the InDesign file, and the pairs have changed themselves since the last time it was opened. This problem is particularly insidious in that there is no warning for it. Turn off the automatic ligatures, and the problem goes away. Thus, if I type "seek behind", you would get "sefi b>ind". In the document I have currently, the pairs ek and eh convert to the ligature glyph fi and the > symbol. Once you turn automatic ligatures off, the pairs go back to the way they are supposed to be (but, all your good ligatures go away as well). If automatic ligatures are turned on (and they are invariably), certain letter pairs will swap out with single glyphs as if they are ligatures despite the fact that they should not be ligatures. We've had two InDesign CS5 jobs develop this strange problem in the past month. We have ran into a type problem that we would like to know if others have had and if there is a preventative solution for. I work at a printing company and we do prepress on InDesign CS5 print jobs.






Sabon lt std history