Live data from Hacker News

Routed Gothic Font

webonastick.com

51–60 of 60 posts

Re: Routed Gothic Font

#51
post #37

> "I created this font by purchasing a Leroy Lettering set, using Inkscape to trace the scanned letterforms of one of its templates, and some FontForge Python scripting." How does this work from a copyright/legal perspective?

Guess why so many Helvetica impersonations/clones exist:

The thing is called "tracing" and quite common.

The actual code (which means the ttf/otf) is protected under copyright. The shape of a letter isn't and can't be by any form of IP.

So: You're not allowed to redistribute the font file but creating your own font which just happens to look alike is perfectly fine.

Re: Routed Gothic Font

#52
post #49

Earlier quoted context omitted.

DIN standards are local derivatives of ISO standards. There are few widely used "Technical lettering" [0] standards: «ISO 3098»(EU/International), «ASME Y14.5» (US) and «GOST 2.304» (ex-USSR). There are few FLOSS fonts which cover «ISO 3098» [1,2,3], «ASME Y14.5» [3,4,5] and «GOST 2.304» [6,7,8] technical lettering standards. [0] https://en.wikipedia.org/wiki/Technical_lettering [1] https://github.com/hikikomori82/os…

Seems like ISO 3098 is significantly newer than DIN 6776, so it's the ISO standard that's derivative of the DIN one.

Well, you are partially right, because most of "DIN" standards already replaced by "ISO".

But there are still many "DIN" standards that now replaced by "DIN EN ISO", e.g. German (local) version of «ISO 3098» (which replace «DIN 6776») is «DIN EN ISO 3098».[0]

[0] en.wikipedia.org/wiki/List_of_DIN_standards#DIN_6000_to_DIN_6999

Re: Routed Gothic Font

#53
This is pretty much the same as Comic Sans, except Comic Sans is a bit more curvy and fun. Routed Gothic is what Comic Sans should have been.

Re: Routed Gothic Font

#54
post #44

For a newer font in this vein, I'd look at B612, a font designed in cooperation with Airbus specifically for visibility inside cockpits: https://github.com/polarsys/b612/blob/master/docs/B612-Leafl...

I'm also quite surprised that the symbols for "O" (capital O) and "0" (zero) are very similar, even in the monospace version of B612.

Cyphar, two years ago you posted:

"Well, there is a port of glibc to UEFI, so one could very easily "boot into Emacs". Strangely I've not seen anyone do this."

Can you hook me up with that link :) Cheers.

Re: Routed Gothic Font

#57
post #51
post #37

> "I created this font by purchasing a Leroy Lettering set, using Inkscape to trace the scanned letterforms of one of its templates, and some FontForge Python scripting." How does this work from a copyright/legal perspective?

Guess why so many Helvetica impersonations/clones exist: The thing is called "tracing" and quite common. The actual code (which means the ttf/otf) is protected under copyright. The shape of a letter isn't and can't be by any form of IP. So: You're not allowed to redistribute the font file but creating your own font which just happens to look alike is perfectly fine.

Thanks.

So, a given "specification" (how a font looks to the human eye) can have many different "implementations" (ie. TTF files). The specific "implementations" themselves can be copyrighted, but somehow not the "specifications"?

If so... assume one TTF file which is copyrighted, pay-per-use license. Assume another TTF file, which is open-source, free to use and redistribute. The files both implement the "Helvetica" specification, rendering the same letters to the human eye. How "different" must the free implementation be from the paid one, for it to not be considered an infringement?

Re: Routed Gothic Font

#58
post #44

Earlier quoted context omitted.

I'm also quite surprised that the symbols for "O" (capital O) and "0" (zero) are very similar, even in the monospace version of B612.

Cyphar, two years ago you posted: "Well, there is a port of glibc to UEFI, so one could very easily "boot into Emacs". Strangely I've not seen anyone do this." Can you hook me up with that link :) Cheers.

Very off-topic but hilarious.

Back to topic: inability to distinguish O and 0 seems pretty terrifying for avionics. Related, I love SF Mono, but it's so hard to read 0000080 in small fonts (try it).

Re: Routed Gothic Font

#59

Earlier quoted context omitted.

Cyphar, two years ago you posted: "Well, there is a port of glibc to UEFI, so one could very easily "boot into Emacs". Strangely I've not seen anyone do this." Can you hook me up with that link :) Cheers.

Very off-topic but hilarious. Back to topic: inability to distinguish O and 0 seems pretty terrifying for avionics. Related, I love SF Mono, but it's so hard to read 0000080 in small fonts (try it).

Yeah, very off topic, terribly sorry. My brain won't let me write 0's without strikethrough anymore.

Re: Routed Gothic Font

#60
post #51

Earlier quoted context omitted.

Guess why so many Helvetica impersonations/clones exist: The thing is called "tracing" and quite common. The actual code (which means the ttf/otf) is protected under copyright. The shape of a letter isn't and can't be by any form of IP. So: You're not allowed to redistribute the font file but creating your own font which just happens to look alike is perfectly fine.

Thanks. So, a given "specification" (how a font looks to the human eye) can have many different "implementations" (ie. TTF files). The specific "implementations" themselves can be copyrighted, but somehow not the "specifications"? If so... assume one TTF file which is copyrighted, pay-per-use license. Assume another TTF file, which is open-source, free to use and redistribute. The files both implement the "Helvetica"…

Since the shapes afaik can't be copyrighted: Your selfdrawn font has totally the right to look the same.

They probably won't however, since you might be able to copy the shape, but for being displayed on screen you need a process called "hinting". That is the term for making pixels out of the shapes. Professional fonts are hinted by hand, making it look neat even in small sizes. There is auto-hinting, but it only gets you so far.

Post reply on HN