[OS X] Renders incorrectly during Font Book installation and Sublime Text editor; MS Word is OK #54
Comments
|
@cwotta Just saw that on 10.9; what version of OS X are you using? |
|
I'm also encountering the issue for both OTF and TTF installs where the font is incorrectly displayed during install on OS X 10.9.5. |
|
Yep, OS X 10.9.5! |
|
Also seeing this on OS X 10.9.5 |
|
Those are the Armenian glyphs that are displayed. They are included in the set. 1. Do you mind right clicking on the Hack font group in FontBook and choosing If you don't get all greens let me know
2. Have any of you customized your keyboard character mapping? |
|
I'm getting all greens inside FontBook, no customized character mapping for me. |
|
Also getting all greens. No customized character mappings. |
|
Same as above: all greens, no customized character mappings! |
|
Well then we have the default solution. You are all Armenian. Issue closed. |
|
;) Sorry all, I really have no idea what is going on if the files passed validation. Let me check into any reports of similar issues on OS X for other typefaces. Can you use it in any non-ST editors aside from Word? |
|
I just gave it a shot in WebStorm, Android Studio and Atom. No luck in WebStorm but Atom and Android Studio appear to work OK. Doesn't even get listed in WebStorm. Also appears to work in the OS X terminal alright. Also, not Armenian, neither is my machine ;) |
|
Haha good solution! It works correctly in TextWrangler and TextMate (and TextEdit, but I'm not sure that one's particularly helpful). |
|
Perhaps a font caching issue on OS X? Maybe try a reboot if you did a number of install + remove + install sequences with the same font files. |
|
Font seems to work fine in iTerm once installed. I did not perform any additional install/uninstall actions with the font file (otf or tff), this was on the first install. Font caching could definitely be an issue, I haven't rebooted in a few days. |
|
Seems surprising to me that it'd be this prevalent were this merely a caching issue... |
|
Seeing the same issue. |
|
Seeing the same issue in OS X 10.8 Mountain Lion as well: |
|
What's odd is if you install it, it appears to display/validates/functions fine, it even previews properly in QuickLook.
I've also purged my font cache via |
|
Will you please give these new builds a try (v2.012)? I've updated the name tables and adjusted the font names based upon what is currently recommended for cross-platform support. Let's see if this addresses this issue. Download Links |
|
I'm sorry to report this, but the new fonts you provided are still showing up as cryptic glyphs, when opened in Font Book (before and after installing). I tested in OS X 10.8.5 and OS X 10.9.5. Screenshots:
|
|
OK thanks for letting me know. It was a long shot for this issue but figured we should give it a shot. Will continue working on it. |
|
Nothing that I did should have changed these behaviors, but there is a new test build available (v2.014) if you'd like to give this a try to see if we happen to change something that made this go away. Available in #111 |
|
Alas, same issue with OS X 10.8.5 and OS X 10.9.5 using Hack 2.014. Screenies: |
|
@jhuckaby Ok, thanks. There wasn't a change that should have led to a solution here but I wanted to confirm that there was not a problem in the metrics that led to display issues. It did install and display ok on your OS X version despite the FontBook issues? |
|
No problem, happy to help! Yup, the font installs just fine, and looks great after installing. Apparently this bug only affects the FontBook preview window before installing. Screenshot after install: |
|
OK, thanks. That is good to hear. If anyone has issues with use of the font after they encounter these Font Book install issues, please let me know. |
|
@chrissimpkins just tested again on 10.9.5. The Quick Look previews and installs just fine as @jhuckaby mentions, it's just the pre-install screen in Font Book the face appears in odd characters. On later OS X versions (Yosemite for instance) it renders OK in the pre-install screen. My guess (wild-ass guess) is that this could have nothing to do with your font, and everything to do with an edge case inside the 10.9 releases. |
|
@qbunt Yeah, I am developing this on 10.10.5 and have never noticed this over numerous install / uninstall cycles. I looked for some information on changes in Font Book with these new releases, but there aren't many details in the Apple documentation. I suspect that it has something to do with the Unicode range support settings in the font builds, but I don't know how to modify it so that you see the appropriate character set during the install. Incidentally, are all of you using older OS X releases or are these testing platforms? |
|
I run 10.10.5 on my main machine. I keep 10.8.5 and 10.9.5 around for testing purposes :) |
|
10.9.5 is my main (only, at this point...) machine. Don't go crazy trying to fix this for my sake; I'm sure I'll be off of 10.9.5 at some point! Thanks for your work so far! |
|
No worries! Just trying to understand the scope of this issue. I can't find data on what proportion of users are still on older versions of OS X. |
|
Not sure how accurate this is, but it might be close enough to say "Yeah, not going to waste my time on 10.9" ;) https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0 |
|
I work for a digital ad company (I know, sorry), and we analyze all incoming browser user agents which contain the OS X version. Here is some data pulled our view logs yesterday (Sept 20, 2015):
|
|
Yeah, that is a bit surprising. I think it's primarily because Mavericks is so stable now, and that Yosemite didn't really add anything Earth-shattering. All my friends at work are still running Mavericks, and when asked why they didn't upgrade, the most common answer was "Why upgrade? What I have works just fine.". Also, no one could list a single feature added in Yosemite either (besides the new flat-shaded look). Funny :) |
Seems like reason enough to me. |
|
Yeah I've gotta admit, I'm running 10.9.5 on my work machine not by choice, but by dependency. Minor iOS development annoyances aside, there's not a lot of motivation to upgrade, even for free. Thanks for looking into this @chrissimpkins, digging your work. |
|
I second that -- I'm really digging Hack. Thanks a bunch @chrissimpkins :) |
|
It's been a lot of fun and the developer response has been great. All of these new changes are the result of issue reports. Will be interesting to see where it leads. I have a large number of things to address yet and lots of new ideas. Keep an eye on the changelog if you continue to use it. |
|
Just for reference, The font previews, installs, and works/renders just fine (for me) in OS X 10.11 El Capitan and Sublime Text 3 (build 3083). 👍 |
|
@Smolations thank you!! |
|
Also works fine for me, same setup as @Smolations. Thanks for this font! |
|
@alanmcginnis great! |
Both OTF and TTF versions seem to render correctly in:
...But do not work correctly in:
I saw the previous issue about rendering in JetBrains editors, but Sublime Text isn't one of them.
The text was updated successfully, but these errors were encountered: