hnonline.blogg.se

1. MY GOOGLE CHROME FOR MAC GETS WEIRD MAC OS X
2. MY GOOGLE CHROME FOR MAC GETS WEIRD SERIES
3. MY GOOGLE CHROME FOR MAC GETS WEIRD WINDOWS

MY GOOGLE CHROME FOR MAC GETS WEIRD MAC OS X

Geek ramblings posted here come without guarantees of correctness, but I offer good karma to those who read them.ĪctionScript AS3 As3Crypto Benchmarks Bug Cages Cassandra Chrome client library configure connection pool Demos distributed database domain name Encryption evaluate Flash Flex Flex Styles Font Embedding Fonts Google code Guava hadoop HBase hbase vs cassandra Indexing Install Java Library Locking Mac OS X marketing mutator NOSQL OS X PayPal Pelops performance recurring payments Red5 rolling upgrade RSA selector seo Transactions Ubuntu upgrade ZooKeeper RSS My team seeks out the broad sunny uplands of open source, rich internet applications and Web scale computing. I'm just another hacker entrepreneur based in London (a JAHEBIL, pronounced gerbil. All other applications I know of have no problem with this. Font managers don’t break any rules: they’ve been part of the Mac scene for many many years. It seems to me as if requiring *Windows* system fonts to be handled in a special way on a different platform is simply laziness on the part of the developer. We should at least have a checkbox in Chrome’s Prefs that allows us to use a font manager and warns us of the (negligible) risks if we do.

I’m not compromising my workflow for a browser.

MY GOOGLE CHROME FOR MAC GETS WEIRD WINDOWS

Over a period of years I’ve discovered that the way for a simple life is to let the font manager (Suitcase Fusion in my case) handle everything.Īs a result, I’m afraid, if Google can’t be bothered to support a very common and standard method of handling fonts on the Macintosh because of some nebulous “security model” (is this really true? it sounds absurd) then I can, frankly, stick with Firefox – much as I like Chrome on Windows a great deal. and in my experience the way to give yourself problems in a range of design and publishing applications is not to have a font manager. By the sound of it, they’re *Windows* system fonts.Īs a designer, I work with a vast number of fonts. I don’t know that I would call these “System Fonts” on a Macintosh.

Deactivate any copies of Web fonts such as Arial, Tahoma and Georgia (these fonts should already exist in your system fonts anyway). Unfortunately however, Chrome’s security model does not allow it to access and load font files outside of the system fonts folder.įix: Carefully go through the fonts in your font manager.

If the manager activates a Web font that is also a “system” font, such as Arial or Tahoma, when Chrome Beta requests the font from the system it will be directed to the managed copy.

MY GOOGLE CHROME FOR MAC GETS WEIRD SERIES

When this happens, text in the fonts in question are represented by a series of A’s.Ĭause: You have a font manager installed, such as Suitcase Fusion, which maintains fonts outside of the Mac OS X fonts folder. That is, except for some people on Mac OS X, because in some configurations Chrome screws up the display of certain fonts. It rocks so much, that once you use it for a while, any other browser becomes unbearable (I won’t go into the design decisions that make it so much better, but please take it on trust and try using this browser for a while, searching via the address bar, adding extensions etc, if you are not already). Just about everyone in the Web/tech industry now has worked out that Chrome rocks.