I've built a new font! Thoughts and feedback on my approach very welcome.

all 20 comments

sorted by: hot top controversial new old
[–] 15 points 3 years ago* (1 child)

Very cool! That did not look easy to do.

  • source
  • hideshow 2 child comments
  • [–] 10 points 3 years ago* (1 child)

    Fantastic project! And thanks for the heads up about the 17th century Dutch fonts - I might consider that for the printed version of my thesis that will probably rot away in the university library anyway. Might as well make it interesting looking.

    My favourite project of this kind is TT2020, which takes typewriter imitation to the next level by including irregularities within the font itself. Each (common) glyph has several versions, making the outcome look much more genuine and allowing for the occasional badly printed glyph without making the same error repeat itself to infinity.

    It's a bit overkill maybe, but it would absolutely lend itself well to Shakespearian scripts. :)

  • source
  • hideshow 2 child comments
  • [–] 5 points 3 years ago* (1 child)

    This is so cool! Not just the font but the whole process and study. Please feel free to cross-post to Typography & fonts.

  • source
  • hideshow 2 child comments
  • [–] 4 points 3 years ago

    This is very cool. I'm looking forward to seeing the progress!

  • source
  • [–] 3 points 3 years ago (3 children)

    Do modern day fonts even support automatic ligatures? How does that work? Or are there Unicode symbols for them?

  • source
  • hideshow 6 child comments
  • [–] 4 points 3 years ago*

    Yes, they do. Part of the OpenType standard are the so called “OpenType features” which (amongst other things) allow for contextual alternates, i.e. different kinds of ligatures, and for stylistic alternates, e.g. a slashed zero, a single-storey ɑ, etc. All of these different glyphs are encoded in the font and can be enabled when typesetting using different selectors. This website shows them off.

    Some ligatures, like “ffl”, are a separate character in Unicode. Some were added because they can be considered a different character in languages other than English. Some (like “ffl”) were added because of legacy reasons; “no more will be encoded in any circumstances”.

  • source
  • parent
  • [–] 2 points 3 years ago (1 child)

    Oh, I love everything about this project so much! It looks lovely!

    It also looks mighty useful for making handouts for TTRPG campaigns ahaha.

    Was the letter-recognition Python codeblock of your own making?

  • source
  • hideshow 2 child comments
  • [–] 1 point 3 years ago (1 child)

    You've really retained the slightly blotted look of the print. Great work!

  • source
  • hideshow 2 child comments
  • [–] 1 point 3 years ago (1 child)
  • [–] [S] 2 points 3 years ago (1 child)

    Cheers! I'm hoping to add some more letters and tidy up the rest when I have more time.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 years ago (1 child)

    This is such a great project! I can see how there’s a little room for clean-up on that long S. Plus the comma-looking apostrophe 😵‍💫. Although maybe that’s how that punctuation mark acted back then?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 years ago

    Oooh, I'm excited to try this out! But later, 'cause I'm just on mobile, and kbin doesn't have a save function yet lol.

  • source