bionking.blogg.se

• #DWARF FORTRESS TILESET COMIC SANS CODE#

> If you don’t believe me, try it for 10 or 15 years.Įvery time a programmer tells me this, and I ask around, I find that the population is split. If you want to go all Marie Kondo on your toolchain (like Chuck Moore has been doing for decades), that's neat, but that doesn't sound like what he's advocating here. Again, if perfection is your threshold for use, you're going to have to throw out half your editor. Every IDE "find text" feature finds useless results, occasionally, from lack of context, too. Every syntax-highlighter I've ever used, for any language more complex than a Lisp, has been wrong, occasionally. If the quality of visual uniqueness is important, better stick to printable ASCII.Ģ. There's lots of codepoints that I can't visually distinguish from one another, even when printed without ligatures. By this reasoning, Unicode contradicts itself. I've never used ligatures like this, and I have no horse in this race, but I don't find these arguments compelling.ġ. Ironically, the article says "well-intentioned amateur ligaturists are adding dozens of new & strange ligatures." and uses what appears a "° DEGREE SIGN U+00B0" that looks like a link to a footnote to denote external links.

#DWARF FORTRESS TILESET COMIC SANS CODE#

So, what's the beef with ligatures? I don't know :) And yes, I've been using Fira Code for several years now. Properly spaced numbers? Properly spaced and aligned punctuation? Contextually correct punctuation? Yes, please, more! Computers have all but destroyed typography, and it's a good thing some of it is coming back. These will never be easy to type in their original form (unless you have APL's custom keyboard), so why not present them as such?ģ. Programming languages have been long stuck in ASCII-land trying to emulate symbols commonly used in other areas such as mathematics: -> and => are arrows, = and = are equality and congruence, >= and =< are greater than/less than or equal to, and the list goes on. It's exactly the font's job to provide any glyphs or ligatures it wants on top of provided characters.Ģ. That said, however, the article fails to provide a compelling argument against ligatures.ġ. Unfortunately, there's no good way to have a font have sets of ligatures per. Rather, they are substitutions in the tradition of APL or vim conceal mode - to get mathematical notation with a standard keyboard.įira Code's main problem is that it tries to be a font for all programming languages which results in some weird behaviours here and there.

I always assumed there were similar subtle rules in English.Īs to the "ligatures" in programming fonts - I would not call them such, problem solved. Historically, this is the reason sometimes ss and sometimes ß is used. There are actually words where this resolves an ambiguity, I think. At least in German, they should never cross a word boundary in composite words, for example Kaufleute (merchants) is Kauf-leute (buy-people), so you would not use a "fl" ligature. Maybe this is different in English typography - I'm a bit more proficient in German - but ligatures do have semantic meaning. In that case, ligature substitution that ignores context doesn’t change the meaning. An fi ligature always means f followed by i. > When we’re using a serifed text font in ordinary body text, we don’t have the same considerations. Usually, the author is spot-on with his recommendations and I really enjoy reading his website.