I noticed this on April 28 and Tweeted about it, tagging the New Zealand Labour Party at the time. It still hasn’t been fixed as of today. That’s supposedly Commercial Type’s Stag Bold Italic in the headline, but someone has slanted the italic. Is this a signal that Labour leans to the right more than it’s letting on? Did someone say 1984?
Still, Stag is a far more inspired, and typographically appropriate, choice than the Futura used by our present government’s political party, after years of Gill Sans. Interestingly, I seem to recall the Labour of Bill Rowling having Futura Italic in its logotype. If only modern-day Labour could get its italic displaying correctly.
Good typography wins votes. I should know.
Other than for the landline, Iâve never bought a phone before. Each cellphone has come as a result of a company plan or a loyalty gift from the telco, but when my Huawei Ascend Y200 began needing resets several times a dayâIâve had computer experts tell me this is the phone, or the SD card (like any endeavour, itâs hard to find agreement; this is like saying that the problem with an axe lies with the handle or the blade)âI decided to replace it. Plus, having built websites for clients it seemed only fair to have a device on which I could test them on an OS newer than Android 2.3, and after a few days I have to say the Meizu M2 Note has been worth every penny. (The Xiaomi Redmi Note 2 was on the shortlist but the Meizu performed better in online tests, e.g. this one.)
You can find the specs on this device elsewhere, in reviews written by people far more au fait with cellular technology than me, but a few things about arriving in the mid-2010s with such a gadget struck me as worth mentioning.
First, I opted for a blue one. Theyâre usually cheaper. Since I have a case for it, I donât have to put up with the colour on the back anyway, so why not save a few bucks if the guts are the same?
Secondly, itâs astonishing to think in five inches I have the same number of pixels as I do in 23 inches on my monitor.
Thirdly, cellular battery technology has come a heck of a long way. (Down side: you canât replace it in this device.)
But hereâs an absolutely wonderful bonus I never expected: itâs Google-free. Yes, the Flyme OS is built on Googleâs Android 5.1.1, but the beauty of buying a phone from a country where Google is persona non grata is that Iâm not stuck with all the crap I had on the Telstra Clear-supplied Huawei. No Google Plus, Google Play Store, Gmail, Google Maps and all the other stuff I had to switch off constantly. I could have had the phone rooted but it never was a big enough priority, even with my dislike of the big G.
I donât know how much ultimately gets back to Google through simply using its OS, but Iâve managed to keep away from signing in to any of their services. In this post-Snowden era, I regard that as a good thing.
The phone booted up for the first time and gave me English as an option (as the seller indicated), so the deviceâs OS is all in the language Iâm most fluent in. However, itâs not that weird for me to have Chinese lettering around, so the apps that stayed in the Chinese language are comprehensible enough to me. There is an app store that isnât run by Google, at which all the apps are availableâInstagram, Dolphin Browser, Opera Mini, plus some of the other admin tools I use. Nothing has shown up in my Google Dashboard. The store is in Chinese, but if you recognize the icon you should be all right, and the apps work in the language youâve set your OS to.
The China-only apps arenât hard to dispose of, and the first ones to go were Netease, Dianping (I donât even use an Anglo dining review app, so why would I need a China-only one?), Amap (again, it only works in China, and it can be easily reinstalled through Autonavi and its folded paper icon), and 116114, an app from a Chinese telco. Weibo I donât mind keeping, since I already have an account, and I can see some utility to retaining Alipay, the painting app, and a few others.
And having a Google-free existence means I now have Here Maps, the email is set up with my Zoho âboxes, and 1Weather replaces the default which only gives Chinese cities.
What is remarkable is that the Chinese-designed default apps are better looking than the western counterparts, which is not something you hear very often. The opposite was regularly the case. A UI tipping-point could have happened.
I also checked the 2G, 3G and 4G frequencies against Vodafone New Zealand’s to ensure compatibilityâthere are at least two different M2 Notes on the market, so caveat emptor. Vodafone also recommends installing only one SIM, which suits me fine, as the other slot is occupied by a 64 Gbyte micro-SD card.
The new Flyme-based-on-Android keyboard isnât particularly good though, and I lose having a full set of smart quotes, a proper apostrophe, and en and em dashes, but far more obscure Latin-2 glyphs are accessible. Iâm not sure what the logic is behind this.
I had an issue getting the Swift keyboard to install, but Iâve opted for Swype, which, curiously, like the stock keyboard, is missing common characters. Want to type a g with a breve for ErdoÄan? Or a d with a caron? Easy. An en dash? Impossible.
This retrograde step doesnât serve me and there are a few options in Swype. First, I had to add the Russian keyboard, which does give an em dash, alongside the English one, though I havenât located a source of en dashes yet. Secondly, after copying and pasting in a proper apostrophe from a document, I proceeded to type in words to commit them to my personal Swype dictionary: itâs, heâd, sheâll, wonât, etc. This technique has worked, and while itâs not 100 per cent perfect as thereâll be words I missed, itâs better than nowt.
I see users have been complaining about the omissions online for three years, and if nothing has been done by now, I doubt Swypeâs developers are in a rush to sort it.
Swypeâs multilingual keyboards are easy to switch between, work well, but I havenât tried my Kiwi accent on the Dragon-powered speech recognition software within.
Going from a 3Â·2 Mpixel camera to a 13 Mpixel one has been what I expected, and finally I get a phone with a forward-facing camera for the first time since the mid-2000s (before selfies became de rigueur). Itâs worth reminding oneself that a 13 Mpixel camera means files over 5 Mbyte are commonplace, and thatâs too big for Twitter. Iâm also going to have to expect to need more storage space offline, as I always back up my files.
I havenât found a way to get SMSs off yet (suggestions are welcome), unlike the Huawei, but transferring other files (e.g. photos and music) is easier. Whereas the Huawei needed to have USB sharing switched on, the Meizu doesnât care, and you can treat it as a hard drive when connected to your PC without doing anything. That, too, has made life far easier.
Iâve been able to upgrade the OS without issue, and Microsoft (and sometimes Apple) would do well to learn from this.
It leaves the name, Meizu (é æ), which in Cantonese at least isnât the most pleasant when translatedâletâs say itâs all a bit Goblin King. Which may be appropriate this week.
Iâm not one who ever gets a device for imageâs sake, and I demand that they are practical. So far, the Meizu hasnât let me down with its eight cores, 16 Gbyte ROM and 4G capability, all for considerably less than a similarly equipped cellphone that wears an Apple logo. And itâs nice to know that this side of Apple, one can have a Google-free device.
Star Wars is in my feed in a big way. To get up to speed on the film series, I had to start with the memorable theme by John Williams.
Thanks, Bill and Paul.
And who better to describe the plot than someone else in the science-fiction world, Doctor Who?
Seriously though, I hope all friends who are big Star Wars fans enjoy Episode VII. It seems to be getting positive reviews, partly because it appeals to our sense of nostalgia. It hasn’t blown anyone away in the same manner as the 1977 original, but then Disney would be very foolhardy to stray for this sequel. If you are building a brand that was at its height 30 years ago, nostalgia isn’t a bad toolâjust ask the team that came up with the 1994 Ford Mustang. J. J. Abramsâthe creator of Felicity and What about Brian?, plus some other thingsâhas apparently been a genius at getting just enough from the past.
One item that is from Star Warsâ past is the opening title, or the crawl. I’ll be interested to learn if they’ve managed to re-create the typography of the original: they were unable to provide perfect matches for Episodes I through III because of the changes in technology and cuts of the typefaces that made it into the digital era. The main News Gothic type is far heavier in these later films. ITC Franklin Gothic was used for ‘A long time ago âŠ’ for I to III; this, too, was originally News Gothic, but re-releases have brought all six films into line to use the later graphic.
However, it could be argued that even between Episodes V and VI there were changes: News Gothic Extra Condensed in caps for the subtitle for The Empire Strikes Back, switching to Univers for Return of the Jedi. (It seems even the most highly ranked fan wiki missed this.) And, of course, there was no equivalent in the original Star Warsâ’A New Hope’ was added in 1981.
Here’s how it looked in 1977:
And if you really wish to compare them, here are all six overlaid on each other:
I wasn’t a huge fan in the 1970s: sci-fi was not my thing, and I only saw Star Wars for the first time in the 1980s on video cassette, but I did have a maths set, complete with Artoo Detoo eraser (I learned my multiplication table from a Star Wars-themed sheet) and the Return of the Jedi book of the film. But even for this casual viewer and appreciator, enough of that opening sunk in for me to know that things weren’t quite right for The Phantom Menace in 1999. I hope, for those typographically observant fans, that The Force Awakens gets things back on track.
Cortana gives completely the wrong address for me. I wonder if the resident of 39A Aparima Avenue is getting identified as the home of a lot of Windows 10 users.
Thereâs not an awful lot that Cortana can tell you. Most enquiries wind up on Bing, and sheâs only really good for the weather and exchange rates (as I have discovered so far). There are a few fun questions you can throw at her, asking if sheâs better than Siri, or whether if sheâs met Bill Gates, but generally, but weâre far from Knight Rider or replicant technology here. A New Zealand accent presents no problems. One thing she gets very wrong is my location, which is allegedly 39A Aparima Avenue in Miramar. Iâm not sure how she arrived at that address, as I donât live there and I donât believe I know the person who does.
Itâs not too unpleasant to look at although the mobile-specific features can get a bit annoying. The menus feel too large overall, because itâs all designed from a mobile-first standpoint, while the biggest gripe from me comes with the typography.
Microsoft has ruined ClearType here in its attempt to make something for mobile first, and most type looks very poor on screen. Fortunately, a Japanese website still hosts the MacType plug-in, which brings the font display closer to what we experience on Mac OS X. It even goes beyond what we were used to in Windows 7, which had been Microsoftâs best use of its ClearType technology to date.
After installing MacType, ITC Legacy Serif looks far more like it does in print.
You can alter the fonts through the Registry Editor, and I set about getting rid of Arial as always. Windows 10 doesnât like you removing a system font, so the trick is to replace it with something else called Arial, then remove the original from HKLM\Software\Microsoft\Windows NT\CurrentVersion\Fonts.
Windows 10 removes your ability to change the icon and menu fonts, and they now have to be changed in the registry, too, at HKCU\Control Panel\Desktop\WindowMetrics, and very carefully.
After tinkering with those, the display began looking like what I was familiar with, otherwise there was a bit too much Segoe on screen.
There have so far been no program incompatibilities. As upgrades go, it hasnât been too bad, and I havenât been stuck here forever downloading updates. Apple still gets higher marks for its OS upgrade processes (when they work) but given how much data I have on my main Windows machine, and how different each PC is, Microsoft has done a good job. Iâm glad the system waited till now, and delivered me a relatively bug-free transition. Software upgrading is one area where I don’t mind not being first.
During the six hours wasted with Ubuntu today (13 would no longer upgrade, so I removed it and decided to start afresh with 14âbig mistake, since it would not let me use the same hard drive), I had to open up my five-year-old Windows Vista laptop and upgrade my Firefox. After all, what were the odds that Mozilla would cock up its flagship browser on two OSs? After all, it’s fine on Mac OS X and Linux.
As it turns out, pretty high. Just as in Windows 7, Firefox for Windows Vista displays no text. And unlike Windows 7, which was solved by switching on hardware acceleration, Windows Vista proved a bit of a bugger to fix.
During the months where I was trouble-shooting, and after my last post, one of the more knowledgeable Mozilla volunteers admitted that there is a fault with the Cairo rendering engine in Firefox: ‘This means that (at least in your case) the issue is most likely specific to the cairo drawing backend. Good to know, thanks.’
It is still definitely related to the 2011 bug I filed where PostScript Type 1 fonts were incompatible with Firefox due to something breaking that time.
Firefox for Windows Vista’s bug, as far as I can make out, is down to Type 1 fonts being incompatible with the browser, even though they are compatible with nearly everything else on the OS. This is slightly different from the Windows 7 fault, as I still have PostScript Type 1 fonts on that computer, but Firefox simply ignores those when specified in a stylesheet in favour of what it can load under hardware acceleration (usually the default).
Despite my updating some of the system fonts that were particular to my Vista set-up to OpenType (which Firefox might have trouble with sometimes, too), that did not fix it. Firefox requires you to delete fonts off your system.
On some websites, including Facebook, Helvetica is specified before Arial in stylesheets. If your Helvetica (not Neue Helvetica) is PostScript Type 1âand it probably would be on a Windows machineâFirefox will detect it, and return blank spaces.
This is still a daft state of affairs with Cairo. Here’s how (to my very basic layman’s mind, and obviously to the minds of everyone at Adobe and a bunch of other places) how a program should deal with fonts:
* Is it installed on the system? Yes.
* Use it.
Firefox seems to adopt this approach:
* Is it installed on the system? Yes.
* Let’s ignore the ones our programmers dislike in favour of the ones our programmers like, which would only be certain TrueType fonts, and to heck with the people who have licensed other fonts and installed them in good faith. Let’s punish anyone who decided to carry over older software. Let’s also fail selected OpenType fonts such as the italics in Source Sans Pro for no apparent reason. [PS.: If the first font family is incompatible, let’s display nothing. On a stylesheet, if one does not work, we won’t load the second one, but we will try to load the system font even if that is incompatible, too.]
When it comes to stylesheets, neither OS makes much sense. Normally a program would go through each font specified, and display in the first one available. I don’t understand the rationale but Firefox will skip the ones in the stylesheet even when installed, even when compatible, and opt for system fonts or those specified as defaults in the program.
All of this is counter-intuitive, and if it weren’t for what must be my OCD, I’d never have found out, and have given up to use another browser.
Not that IE11 is much good:
After months of avoiding the latest Mozilla Firefox because it would display no text, installing, removing, and reinstalling an older version of Waterfox just so I could do some work, and experimenting over the last day with Cyberfox, which included editing fonts, looking at GFX settings, editing the registry, and doing an awful lot of research, I have now fixed the problem of having no text in these browsers.
As I discovered years ago, the trick is to do the exact opposite of what the experts suggest.
When trying to set up the office network in the mid-2000s, the only way I could get it going was to do the exact opposite of expert advice, by making sure the speed on every device did not match.
Tonight, the solution was as simple as pie. Almost every piece of advice I had received when reporting this issue was: turn off hardware acceleration. It was already turned off, so, logically, I kept looking at other things. It got to the point where I was advised by Loic, one of the helpful guys on the Mozilla forums who had hitherto walked me through possible solutions, ‘As you are able to reproduce it, could you use the tool mozregression to find a possible regression range, it will help to narrow the underlying regression.’
Software people think I am a lot smarter than I really am, and I had to admit to the writer that I am a layman and I had no idea what he was talking about.
The correct solution, if you want Firefox, Waterfox and Cyberfox to display text where there was none, is to turn on hardware acceleration.
You can imagine my feeling right now: a sense of satisfaction knowing that I am running the latest, most secure browser and that I overcame this rather serious bug, with the usual disappointment in realizing that I trusted again in expert advice that wasted time for a lot of people, including those kind developers on the Mozilla forums, and Alex, the guy behind Waterfox, who were trying to find a solution for me. I simply do not know enough about computers and software beyond what I have to do to make a living.
The concluding remark from one of the guys, Nicolas, on the Mozilla thread was, ‘This means that (at least in your case) the issue is most likely specific to the cairo drawing backend. Good to know, thanks.’
I hope documenting this bug has helped someone out there. Merry Christmas!
Rather than repeat the story in new words, here is a draft of the post that was sent to Cyberfox’s support forum.
The short story: Cyberfox no longer displays text as of this morning after working well for its first evening yesterday after installation for the first time. Glyphs that are not from a @font-face linked font will not show, so if a page is calling fonts from the system, the browser displays blank text. Nothing happened overnight. I switched the machine off, and when I switched it on again, Cyberfox exhibits this behaviour.
The long story: in 2011, Firefox had a bug which meant there was no backward compatibility with PostScript Type 1 fonts (https://bugzilla.mozilla.org/show_bug.cgi?id=628091). This is very similar to that except the text areas are blank, rather than filled with squares or hex codes.
About two Firefox versions ago (I am guessing v. 32), the browser stopped showing text. I switched to Waterfox, which lasted one more version before it, too, stopped showing text. I downloaded Cyberfox last night and was truly pleased that here was a Firefox-based browser that actually worked. Text displayed as normal, and these were my Type 1, TrueType and OpenType fonts. To top it off, Cyberfoxâs rasterizer and the way it handled sub-pixel rendering was superior to that of the other two browsers (see my blog post at http://jackyan.com/blog/2014/12/switching-to-cyberfox-after-waterfox-and-firefox-stopped-displaying-text/ for two screen shots of the type). Naturally, I was over the moon and made Cyberfox my default.
Just to be on the safe side, I turned off hardware acceleration as when I posted the above bug to Mozilla Support, I was told that that could be a culprit. I made no change to OMTC.
Today, as mentioned, Cyberfox has become just another Firefox where no text is displayed. But the really weird thing is that the typography, for the type that does show, is identical to Firefox and Cyberfox: the superior rendering is gone.
Also, Iâve since altered the font family I use as a default for Windows displays to OpenType (I work in fonts), so there should no longer be an backward-incompatibility issue. Nvidia updated one of its drivers today, so I let that happen, and confirmed that all my drivers are up to date.
Reinstallation (while keeping profile data) actually fixes everything: the type is back, rasterized more sharply,
I was using Australis as the theme but have since gone back to classic.
Iâd be grateful for any light you can shed on this as Iâm keen to stay within the Firefox 64-bit family. Whatever makes Cyberfox display better than the other two immediately after installation (though not after a reboot) solves this major problem of no type appearing.
The different rendering method is the fix. The questions are: why does Cyberfox render type differently if it’s Mozilla Firefox-based? And why does rebooting my computer change this setting?
Since the Firefox for Windows updates in November, I’ve had a big problem with the Mozilla browser, and the Waterfox 64-bit version based on it: they won’t display text. I had to downgrade to Waterfox 32.0.3 for the last month or so, but it’s begun crashing more and more regularly (from once a day to thrice todayâI visit largely the same sites, so why does software “decay” like this?).
On the latest incarnations of Firefox and Waterfox, linked fonts work, but the majority of system fonts vanished from the browser. And, for once, I’m not alone, if Bugzilla is any indication. It is probably related to a bug I filed in 2011.
I’ve had some very helpful people attend to the bug reportâit’s great when you get into Bugzilla where the programming experts resideâbut sadly, a lot of the fixes require words. And, unfortunately, those are the things that no longer displayed in Firefox, not even in safe mode.
As many of you know, there’s no way I’d switch to Chrome (a.k.a. the ‘Aw, snap!’ browser) due to its frequent crashes on my set-up, and its memory hogging. There’s also that Google thing.
After some searching tonight, I came across Cyberfox. It’s not a Firefox alternative that comes up very often. Pale Moon is the one that a lot of people recommend, but I have become accustomed to Firefox’s Chrome-like minimalism, and wanted something that had a Firefox open-source back end to accompany it. Cyberfox, which lets you choose your UI, has the familiar Firefox Australis built in.
I made the switch. And all is well. Cyberfox forces you to make a new profile, something that Waterfox does not, but there isn’t much of an issue importing bookmarks (you have to surf to the directory where they are stored, and import the JSON file), and, of course, you have to get all your plug-ins and do all your opt-outs again. It also took me a while to program in my cookie blocks. But the important thing is: it displays text.
You’d think that was a pretty fundamental feature for a web browser.
The text rendering is different, and probably better. I’ve always preferred the way text is rendered on a Macintosh, so for Cyberfox to get a bit nearer that for some fonts is very positive. It took me by surprise, and my initial instinct was that the display was worse; on review, Firefox displayed EB Garamond, for example, in a slightly bitmapped fashion; Cyberfox’s antialiasing and subpixel rendering are better.
Firefox and Waterfox on Windows 7
Cyberfox on Windows 7
Here’s where the above text is from.
Gone is the support for the old PostScript Type 1 fonts (yes, I still have some installed) but that’s not a big deal when almost everything is TrueType and OpenType these days.
The fact Cyberfox works means one of two things: (a) Cyberfox handles typography differently; or (b) as Cyberfox forces us to have a new profile, then there is something in the old profiles that caused Firefox to display no text. That’s beyond my knowledge as a user, but, for now, my problems seem to be solvedâat least until someone breaks another feature in the future!
PS.: That lasted all of a few hours. On rebooting, Cyberfox does exactly the same thing. All my text has vanished, and the rendering of the type has changed to what Firefox and Waterfox do. No changes to the settings were made while the computer was turned off, since, well, that would be impossible. Whomever said computers were logical devices?
Of yesterday’s options, (a) is actually correctâbut how do we get these browsers behaving the way they did in that situation? In addition, the PostScript Type 1 fonts that the browser was trying to access have since been replaced.