81–90 of 136 posts
Does anyone like the way they've done the dotted zero? I've always disliked it personally. If they offered a slashed version I would definitely try it out.
Keep stuff out of the middle of my zeros, please.
The circle surrounding nothing wonderfully symbolizes a subtle concept.
Drop a dot in hole and now what are you symbolizing? A nice golf shot? When you put a slash across it are you warning me away?
No, no. I prefer my voids empty, thanks very much.
No, still cannot compete with consolas, sorry!
For those feeling adventurous: Input[1] is a proportional font made for coding. It's also highly customizable. [1]: http://input.fontbureau.com
Too bad it doesn't include programmer ligatures, I've been looking for a proportional font that included those (I tried hacking them in myself but couldn't figure out the font hacking tool chain).
Earlier quoted context omitted.
> All sorts of problems installing this on OSX Like what? Installed it with absolutely no problem at all in both Sierra and High Sierra (GM) -- and never had issues installing it in my older Mac OSes (or any other font -- some fonts created by amateurs --free .ttf varieties-- have broken metrics/config and you're warned about it sometimes. Other than that, absolutely zero issues). > to be fair, the process for instal…
UPDATE (& TL;DR & Introduction!): Killing Font Book between operations avoids all sorts of errors and weird display issues you'll get if you try to install multiple font files in a single 'session'. Open Font Book from fresh, locate font files in Finder, drag them into it and you'll do everything in one operation, and it will even update to show you what's happened! > Like what? Errors about duplicate fonts. Several…
Oh, I rarely happened to need to install multiple files in the same Font Book "session". At best 4-5 files for the different fonts of the same family (X bold, X italic, etc) -- might be why I'm not seeing those issues.
>Having to open four separate font files, then click a button each time to actually install them seems like a pretty tortuous process
Having been there in 1997-200x era Linux, where you had to manually edit config files and jump through hoops to register fonts (and they wouldn't even work across all desktop environments and toolkits) I really don't see the issue...
That said, you can just drag and drop multiple font files into Font Book if I'm not mistaken. In fact, you could just drop them into your Fonts folder and they should work too -- no clicking required -- don't know if Apple removed that, used to work at least in Snow Leopard days.
Can we please stop polluting the global namespace with names like "Hack"?
Earlier quoted context omitted.
That doesn't even make sense. What if there is a font named Hack and a language (which, FWIK, exists as well)? In fact if it's "extremely common" then already there's no such concern. Now it just has N+1 uses. Would it hurt anyone to use context to know which of the two is talked about?
> What if there is a font named Hack and a language Then one gets confused between them. Next month a story on HN will be titled "New version of Hack released". That's confusing. > (which, FWIK, exists as well)? Yes I know. That doesn't weaken my point! > Would it hurt anyone to use context to know which of the two is talked about? Of course. Every time one has to spend effort additionally clarifying one's meaning (o…
For 1 split second. Every year or so. And only if there's no other context in the title (e.g. www.facebook.com).
>Of course. Every time one has to spend effort additionally clarifying one's meaning (or worse, someone else's meaning)causes a bit of "hurt".
It also exercises the brain for the broader world, where things are not always humanly managed and/or cleanly designed, and only need the least possible effort.
Can we please stop polluting the global namespace with names like "Hack"?
Earlier quoted context omitted.
UPDATE (& TL;DR & Introduction!): Killing Font Book between operations avoids all sorts of errors and weird display issues you'll get if you try to install multiple font files in a single 'session'. Open Font Book from fresh, locate font files in Finder, drag them into it and you'll do everything in one operation, and it will even update to show you what's happened! > Like what? Errors about duplicate fonts. Several…
> UPDATE (& TL;DR & Introduction!): Killing Font Book between operations avoids all sorts of errors and weird display issues you'll get if you try to install multiple font files in a single 'session'. Open Font Book from fresh, locate font files in Finder, drag them into it and you'll do everything in one operation, and it will even update to show you what's happened! Oh, I rarely happened to need to install multiple…
That was exactly the case in this instance :)
> Having been there in ...
Sure, I don't think I've ever had a great experience installing fonts on any platform, but I hold Apple to a higher standard.
> That said, you can just drag and drop ...
I know, I said that in my update that you quoted! :-)