Font problems - update

it seems that Xft and freetype need patching for some people, maybe having to do with using an LCD. i found the patches on David Chester's page:
http://www.cs.mcgill.ca/~dchest/xfthack/
i haven't got it perfect yet, but you can perhaps start to see the difference here:
http://datadump.homelinux.com/fontcomp/dchester.html
on the left is before the patching, on the right, after. keep in mind that even though it might not seem like a major change, on an LCD it makes all the difference. :shock:
after i applied the first patch, the other one complained about it already being patched, so i left that out for now (edit: d'oh, i just noticed the two patches are for different freetype versions - so much for scanning. the version i applied was the cvs version, and apparently that still mainly works for up to 2.1.9). i also made some other hacks to Xfree before recompiling, but i lost the webpage URL and will have to locate that again.
this is with freetype 2.1.9 and XFree86 4.4, btw. at first X wouldn't compile, but during one iteration i forgot to remove xorg and compiled XFree right over it. that time it worked!
i'm also having some "side-effects," like the italic text in web pages is bolded (try to read slashdot, ugh ), and the characters with alt underlines (F in File, etc.) in some apps like gnome are weird courier-like fonts. other than that, it's a big improvement.
next i am going to test the whole process again on my test partition. maybe it's not even freetype that's doing it, but the recompile of X with those hacks, or both. hopefully i can get it tweaked 100 percent and get rid of the anomalies. i'm wondering, though, can these tweaks eventually be applied to the arch version of freetype2/X for those of us with LCDs? or maybe set up parallel versions in a test repository or something? it really would make life a lot easier! the X hack was only a matter of adding two or three lines to a subdirectory file -- i'll try to find that again and post it. but i'm just afraid of what's going to happen when things start upgrading and we're left with the crappy fonts again.

I think I'm wrong about this?
Apparently, Symbol-like characters have to be entered via the Character Palette, and not via Format > Font > Show Fonts.
I've managed to avoid knowing this all along, because my use of such symbols has been copy and paste from MathType into maths presentations.
Sweet understanding at last!

Similar Messages

  • Pdf fonts problem in 10.6.7 - resolved in 10.6.8 combo update?

    The pdf fonts problem in 10.6.7 forced me to go through the long uninstall process after a couple days stressing over what the problem was -- it was Adobe tech support that finally informed me what the problem was. Is the problem fixed in the 10.6.8 combo update?  Since I got no replies when I asked this question a different way yesterday, can anyone say (for helpful answer points) whether Apple would be inclined to answer this question if I just call them up (i.e., without existing AppleCare)?   Any other suggestions for getting official support on this question?   As it stands, I fear updating at all, and could be stuck with 10.6.6 for a long time.

    The combo should fix your problem.  As always have a back-up in case you have to revert.
    The Font update came out to fix the problem in 10.6.7
    http://support.apple.com/kb/DL1377
    It should be rolled into the Combo-Update:
    http://support.apple.com/kb/DL1399

  • [Solved] Strange font problem - after update.

    Hello guys,
    encountered a strange small font problem on sites with code wrappers like stackoverflow/blogs/jsfiddle. After update. took a look at my font setup all looks good.
    I've also checked the settings for gtk2/3 and no problems there.
    INFO:
    Google-Chrome-Beta. [same thing]
    Firefox [same thing]
    /etc/vconsole.conf ->
    KEYMAP=sv-latin1
    FONT=ter-112n
    .gtkrc-2.0->
    gtk-theme-name="Clearlooks"
    gtk-icon-theme-name="Faience"
    gtk-font-name="Tewi 9"
    gtk-cursor-theme-name="Adwaita"
    gtk-cursor-theme-size=0
    gtk-toolbar-style=GTK_TOOLBAR_BOTH
    gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
    gtk-button-images=1
    gtk-menu-images=1
    gtk-enable-event-sounds=0
    gtk-enable-input-feedback-sounds=0
    gtk-xft-antialias=1
    gtk-xft-hinting=1
    gtk-xft-hintstyle="hintfull"
    gtk-xft-rgba="none"
    /gtk-3.0/settings.ini->
    gtk-theme-name=Clearlooks
    gtk-icon-theme-name=Faience
    gtk-font-name=Tewi 9
    Any ideas on this problem would be greatfully appreciated.
    http://imgur.com/MD7yPI2
    Mod note: removed huge image -- WorMzy
    Last edited by Learning (2015-05-22 21:55:07)

    Update:
    Tried reinstalling, change the fonts, remove all font clear the cache.
    change, look up the settings, looked up size, tried monitor dpi.
    checked all the config files for anything remotely related to this problem.
    Had a quick look at the bug tracker for google-chrome-beta as well no reported
    font problems as far as i can find.
    Update2:
    Tried adding custom.css to the browser not even that worked.
    update3: [SOLVED]
    So i solved the problem.
    The problem was a faulty font that was stuck and used in the pre somehow.
    Removed and added another to the list and somehow that worked.
    recommendations - if anyone has this problem in the future.
    open firefox and look in the font tab what is used. and remove that
    or try to install a fixed one. that should work.
    -Nothing has yielded any working results.
    So any ideas at this point would be most appreciated.
    Thanks,
    -L
    Last edited by Learning (2015-05-22 21:59:14)

  • Strange font problem after kernel update

    Hi,
    I recently did a pacman -Su system update which told me there was one new package available which was the kernel. I let it install and when i rebooted my fonts had kind of 'degraded' in kde. They're still usable but they now look like they haven't been rendered properly because of a dpi problem. However, xdpyinfo tells me my screen's at 92x96 dpi and i have all the 100 and 75 dpi fonts installed so i don't understand how this would happen. i even tried reinstalling the nvidia drivers in case it was the kernel module which needed rebuilding.
    I never had this problem updating before although i have known pacman to remove things it shouldn't in the past so could it have deleted something??
    Hope someone can shed some light on this for me
    Dan

    I solved that by resetting the parameter ram, as explained here: http://docs.info.apple.com/article.html?artnum=2238

  • Updated to 10.6.4 and now a Photoshop font problem.

    I just updated to 10.6.4 and opened a file I was using with Photoshop CS4. Now I get the message "some text layers may need to be updated before they can be used for vector based output" which tells me that a font I was using has problems (turned off? corrupted?).
    If I allow it to update, will it change the font?
    I cannot click on the text to see what font I was using because it requires that I update it.
    What do I do now?

    So I think my problem is sort of a non-problem. Updating to 10.6.4 caused my font setting to change, most likely turning on some that were duplicates. This caused Photoshop to change what font it used for the layout and gave me the 'warning'. Allowing the fonts to update did not change the look of the Photoshop document.
    The one part I do not understand is that since MSOffice seems to load fonts in a folder that houses the applications, rather than in the user font folder, is there anyway to rectify this and load the MS fonts in the user font folder? Using the Font Book to resolve duplicates causes problems with the MSOffice programs. If I can move those fonts to the user library font folder, will that resolve the problem?
    It is also interesting that even though the MSOffice fonts are loaded in a folder with the MS applications, those fonts are available to other applications such as Photoshop that are not part of the MSOffice group.
    Note that I am having this problem only because I have two copies of MSOffice, X and 2004. If I trashed one version of them, my problem would go away. I keep the two different versions because of compatibility issues and because I have problems with Entourage 2004.

  • Glitches in address fill-ins with nicknames; default font problem; plus other glitches in Thunderbird 31.3.0 and 31.4.0; can I roll back to an earlier version?

    I am unhappy with the recent upgrade to Thunderbird 31.3.0 and now 31.4.0. My bottom line question is whether I can roll back to the previous version, which was working well for me.
    The problems I have encountered include:
    1. I used to be able to enter a single letter in many cases in the address field, and the autocomplete would fill in the entry that I always use with that single letter. That function has been lost, as has auto fill-in based on the nicknames I have entered in my Address Book. I see there is another thread on this problem (https://support.mozilla.org/en-US/questions/1036962), but no satisfactory answer so far. Entering a single letter now pulls up completely unrelated address entries that may not even have that letter as part of the name, address or nickname for that unrelated address. I have created new nicknames to try to adapt to this problem, but even these new nicknames no longer work with the 31.4.0 upgrade yesterday, forcing me to create yet more complex and hard-to-remember nicknames to pull up my frequent addressees. This is all very frustrating to me, as I depend on speed and ease when creating messages.
    2. Also, I used to be able to enter a single letter in the address field and then use the mouse to click on the "To:" symbol to the left of the next address line to change the next entry to "Cc:"; doing so would then cause the complete address to fill in in the "To:" address field, and make the next field ready for an entry. That no longer works. If I use that technique, the shortcut that I entered in the first field gets included along with the address (if I'm lucky enough to have the address itself selected now, given the problems I've mentioned above). I now have to press "Enter" in order to get the address in the first field to "take" correctly, and then have to click on the "To:" symbol for the next line as a separate action. Just another inconvenience with the new version.
    3. While still on the subject of addresses, personally I see no reason why the address and subject fields should now be colored blue by default rather than appearing as blank, white fields. I far prefer the old look. And I suspect that changing from the blue color to a nice, clean, white field takes time and computer resources that slow things down.
    4. The default font (Times in my case) no longer "takes" when replying to or forwarding messages. I've checked Tools/Options/Composition, and Times is still shown as my default font. However, when I start to type (in a reply with the original message quoted or in a forwarded message), the result is "Variable Width". In order to get Times, I need to highlight the block of text after typing, including the lead-in to the quoted message or the header of the forwarded message, and select "Times" when "(mixed)" shows up. This is a big pain; I often forget to do so and end up having to edit the Unsent Message (which I check before sending) as New and correct the font.
    5. A minor problem: I rely on the reminder to attach a message which shows up when an "attachment-related" word is entered in the body of the message. It has been a wonderful feature of Thunderbird that has prevented me on many occasions from sending off messages without the attachments. However, in the new versions, even if I have indeed added the attachment, a pop-up comes up on sending the message saying there has been no attachment and asking if I want to add one. It's easy enough to just click "No", but it's yet one more unnecessary and distracting step that this new version is requiring of the user.
    I'm really sad to see these various changes/glitches. I love Thunderbird and it bothers me deeply to find myself mired in so many new problems that slow down my work. I would be grateful for any suggestions and advice, and, particularly, for any information as whether I can roll back to the version prior to 31.3.0 that was working well for me.

    Thank you, Zenos. I tried rolling back to v31.2.0, since I had not encountered problems prior to December. However, that didn't help. So I followed your valuable suggestion to revert to v24.6; that seems to have done the trick.
    I would like to mark this problem as "Solved" -- the rollback seems to have worked. However, since my original post was a complex mix of things, before I do that, should I post the individual problem sets that I had noted (address fields/nicknames problems -- numbers 1-3; default font problem -- number 4; attachment reminder problem -- number 5) as separate issues which have not been solved?
    Do you know if these various issues are being worked on? I'm glad to have the temporary fix of rolling back to an earlier version, but I'd like to get back on the current update schedule at some point if and when these problems have been corrected.
    Thank you again!

  • 10.6.8 combo & 10.6.7 pdf fonts problem

    Does the 10.6.8 update combo correct the pdf fonts problem that was inherent to 10.6.7?  After a couple days of stress I had to do the lengthy 10.6.7 uninstall process in order to refine my doctoral dissertation.  This has made me gun-shy & fearful of updates.  Is it safe to update now?

    The combo should fix your problem.  As always have a back-up in case you have to revert.
    The Font update came out to fix the problem in 10.6.7
    http://support.apple.com/kb/DL1377
    It should be rolled into the Combo-Update:
    http://support.apple.com/kb/DL1399

  • HT1338 Font Problems with Snow Leopard

    I'm having font problems after updating to Snow Leopard.  It seems to have problems with spacing the fonts properly and reading some fonts properly in Page and Keynote.  Any suggestions of how to fix it?

    Dear Kurt,
    in bigger companies thinks come slow :-)  Actually we are switching from 10.4.11 with Quark 6.52 and FontReserve to 10.6.8 with Adobe CS5 and FontBook.
    And as you may guess we're running directly into the HelveticaNeue problem.
    We cleaned up the system fonts so that only the absolutly needed are in /Sys/Lib/Fonts/ and all other fonts (from MacOS and our own) are in /Lib/Fonts/ where they are in folders for better handling.
    The number of additional fonts were radically stripped down to the REALLY needed (about 70 fonts with their families).
    We removed the protected fonts and replaced Helvetica, HelveticaNeue, Times, Symbol and ZapfDingbats with PS Type1 fonts.
    Our goal was to have no font conflicts to keep our users save. In addition we put fonts in predefinded collections to switch them on/off with an AppleScript that picks the collection name.
    And from here it went fancy: The Apple apps are working fine but external app like Adobe CS5 and MS Office only see the fonts in /Sys/Lib/Fonts/.
    When we put the HelveticaNeue.dfont back (no matter if it's in the system or at ~/Lib/Fonts/) the other apps also get all installed fonts. We found out that this works even if the HelveticaNeue.dfont is deactivated.
    Unfortunately this brings up two problems:
    The HelveticaNeue.dfont can't be put to a font collection without taking the corresponding font from the Type1 font with it, so it's more difficult to handle with the AppleScript (we have to pick the exact single name).
    The second is that if something goes wrong and all fonts are switched to active we have a font conflict and the possibility that the dfont is used in documents.
    I think I have read all (ok, many :-) of your posts about the Helvetica problem in 10.6 as well as your really great document about font handling in OS X.
    But I wasn't able to get it to work.
    Do you have the one big hint for me???
    Thanks and best regards...      Udo

  • Font problems after 10.6.7

    I'm getting lots of strange behaviour relating to fonts since updating to 10.6.7. This is all in things that used to work perfectly.
    PostScript output causes errors in Distiller (problems in font definitions); and manipulating PDF objects can cause embedded fonts to become .... unembedded.
    As I understand it, there were lots of security fixes to font handling in the update, but it seems to have caused loads of trouble.
    The developers for an app I use, Imposition Wizard, have confirmed that things aren't working as they are supposed to and have filed bug reports with Apple.
    However, as I do a lot of work with PostScript and PDFs, I will have to reinstall the OS to 10.6.6.

    it's impossible to know how my particular combination of hardware and software (Finale music notation; Distiller; Imposition Wizard) is going to react in the absence of other people doing exactly the same thing.
    You don't need other people's experience for this, just an extra drive with a partition where you can install an upgrade and test your requirements before moving to it permanently. Lots of people who cannot afford to have OS update problems work this way. Superduper has a "sandbox" feature which makes this really easy.
    I always think that if you're going to reinstall the OS, best do it fresh rather than a clone that may already have some cruft on it.
    Perhaps. The main value of the clone is that you can keep working without losing the time required to reinstall, which could be important for a particular user on a particular day.

  • How to uninstall Snow Leopard? major font problems in iWork, iLife

    All iWork and iLife apps have shocking font problems... so much so that I need to uninstall Snow Leopard and wait for Apple to sort it out. Does anyone know the best way? And how is it possible that these problems are occurring with Apple's inhouse software? Other stuff seems to be working OK so far for the most part. For a bit more detail on my problems, including sample images:
    http://bit.ly/309G0o

    Snow lizard cost me $27.000.00 in unusable fonts. We installed snow lizards (what I'm calling it now) and lost 934 fonts. Say 40 were bad fonts and 896 were type 1 postscript. When I explained to the tech person how big this was to the print community, he had no clue. - I'm still waiting to hear back. I have a case number but now I read from another post they knew Snow Lizard would do this. At 30.00 per font that is almost $27,000 to replace what they thought wasn't important. But in the print world of design this is huge. Every layout and ad that needs an update - which take a few minutes is a whole rework. They have no clue what business a mac computer is in or they don't see us as important.
    I did find if I load those fonts or the font missing into the InDesign font folder I can get the old ad to make it to pdf. But photoshop and illustrator, I'm screwed. And if I didn't outline the type in illustrator - it's gone. I asked the tech guy if I can go back, and undo this slimy lizard and he said probably not if we do backups. We do backups every hour - this is the print business. I feel forsaken. I've been with apple for so many years.

  • Font problem when converting to pdf

    I have been struggling with this for a long time! When I export to pdf for some reason the fonts become really mangled. I use several fonts but it is especially baskerville 12 that looks really bad. I have searched and searched but can't figure out why it comes out like that?
    If anyone can be of help it will be much appreciated!

    I have the same issue. From what I found online it originated sometime during this update (http://indesignsecrets.com/mac-os-x-10-6-7-update-causes-font-problems—but-proba bly-not-in-indesign.php)? I am running OSX Lion but it seems the issue was inherited...
    My situation is using Pages with Baskerville font. It appears wonky in Adobe Reader but as expected in Preview.
    Found a temporary fix at http://forums.adobe.com/message/4320355#4319047 . It would be nice for this to be included in an upcoming patch.
    Message was edited by: _juan_

  • Japanese font problem fixed.

    The Japanese font problem was fixed in the recent update. The Kaku Gothic font now shows in the correct font-weight.
    Only Kaku Std which is a fat font is still a bit fat, but that's how it is.
    http://web.me.com/heli1/Test/Experiment.html
    (the first three danger signs have been fixed)

    where exactly u r using the japenese charecters??
    r u using inthe Java programme or r u using in html page.

  • Font Problems in Keynote

    Hi all
    Having some big Font problems using keynote since the last Snow Leopard update some month ago Mac OS X 10.6.7 (10J869) .
    I tried to install the Latest Font Update package as well but nothing.....
    The problem is the Myriad Pro Bold font (Apple use Myriad Pro almost everywhere).
    The other Myriads work just fine.
    I have also checked the Font Book and the Font is NOT duplicated.
    Have done some 50+ presentation in Keynote all with this Font.
    It looks like this
    Thanks for your time and help

    Yes I have...nothing happens. The font is myriad pro bold, all other myriads works. The thing is that I have used that in almost every slide in some 50 presentations, i.e hundreds or perhaps thousends of slides and in keynote you can not change them all et once. On my both iMacs works just fine but I cant install the uptades just in case, and who carry around an iMac for every presentation

  • Dictionary Font problem - E52

    hey pals,
    i've updated built-in dictionary with additional language Hindi but font is not getting displayed , instead it shows just boxes. Any ideas why it happens.......and any solution??
    bought the phone in singapore and using in India.
    Also how to get regional font support for my phone e52??  plz help!!!
    Thanks in Advance,
    himbin

    Hi...
    Troubleshooting help here >  Font problems and management in OS X

  • There was a problem updating InDesign CC For more information see the specific error below.  Update Failed Download error.  Press Retry to try again or contact customer support.(49)

    Posted the entire text from the error window, when trying to update, using the normal NON-TECHIE way to update any and all Adobe CC products, via the Creative Cloud updater installed when Adobe Creative Cloud subscription was purchased when first offered.
    The following occurs, ad nauseam:
    There was a problem updating InDesign CC
    For more information see the specific error below.
    Update Failed
    Download error.  Press Retry to try again or contact customer support.(49)
    Here's the crux of my frustration:
    (1) Customer Service is NOT contact-able, to receive LIVE help.
    (2) There is NO way for me to mitigate this "Download error", being a student learning InDesign, and NOT in any way capable of tweaking folders/files here and there.
    Therefore, the real question:
    Given that a significant number of subscribers are having the above referenced issue with attempting to download the current update for InDesign, WHAT ARE WE SUPPOSED TO DO, in order to get our contractually paid-for updates to our legally and contractually paid-for Adobe software, specifically in my case, InDesgin's current update?
    Please, NO TECHNICAL mumbo-jumbo which most likely will cause the overwhelming majority of users, like me, to seriously corrupt their computer files, but rather an honest, straightforward "what to do" from real CS/Engineers working for Adobe, as to how to FIX this issue, period.
    ===========================================================
    UPDATE:
    Here is a way in which I think I was able to "update" my InDesign CC application:
    (1) Sign-In to your Adobe Account
    https://www.adobe.com/
    (2) Click on the MENU icon
    (3) Click on the product InDesign icon
    Your browser should display the page for Adobe InDesign CC
    https://www.adobe.com/products/indesign.html?promoid=KLXLU
    (4) Click on the Download icon,
    Your browser should now display the page to download InDesign,
    https://creative.adobe.com/products/download/indesign
    (5) a Pop-Up window should open, and display:
      Launch Application
      This link needs to be opened with an application.
    with the first option to select being the CreativeCloud(URIHandler)
    (5) Select this application and click OK.
    What happened when I followed steps (1) thorugh (5) is that:
    (a) InDesign CC(2014) was installed,
    (b) InDesign CC, updated, and then
    (c) InDesign CC(2014), also updated.
    Why this all worked, is a mystery to me.
    Looks like a separate, "new" version of InDesign, InDesign CC(2014), was installed, the existing "old" InDesign was updated, and then the newly installed Indesign CC(2014) was further updated.
    A BIT MORE, when I launched my InDesign CC app, and checked to see if there were Updates Available, there in fact was an Adobe InDesign CC 64 bit (9.2.2) update.
    I clicked on UPDATE and my "old" InDesign CC app was "successfully updated."
    FURTHER INFO:  I may have neglected to list some important info ... OS:  Windows 8.1 Pro with Media Center, 64-bit
    Confused, I am able to launch BOTH of these apps, and hopefully I may use one of these versions of the InDesign CC app, to do some InDesign work.
    Will keep y'all posted!
    Message was edited by: Richard Yapkowitz, about an hour after I first posted this issue.

    Jackdan error 49 indicates the installer was unable to access a critical file or directory.  You can find additional details at Error downloading Creative Cloud applications - http://helpx.adobe.com/creative-cloud/kb/error-downloading-cc-apps.html.

Maybe you are looking for