what to do with the end caps not aligning

[argyleink]

some people think it's glaringly bad, some dont notice, some will never see it at the tiny size they'll usually see it, other's might print it on a poster and be appalled. a couple questions:

• if we solve it, then we cant just point to the Dinish font
• if we solve it, how will we distribute the glyphs/shapes

[romainmenke]

Upstream issue? Maybe the Dinish font creators are open to making such changes?

Edit: could also be a fork, it is open source :)

[mxdvl]

While visual adjustments make sense for a font, which is visually adjusted to work best at typical reading sizes, for a word mark that is often drawn at large “display” sizes, following a more rigorously geometric solution may be preferable.

Obviously in this case the canonical version would be the SVG and distributed that way.

[chriskirknielsen]

Agreeing with @mxdvl here — this was the one thing that bothered me using Dinish that I had to fix (though it is only following in the footsteps of original DIN fonts 😄).

While I think it's very cool to be able to recreate this in CSS with very little code, it does also mean it might look a little different based on the browser (font metrics are not always consistent across browsers) or if the fontr fails to load, and as such, two things come to mind:

• it's okay to recreate the logo with the font as-is; it's a detail that can be ignored if you want to play around with it.
• a "source of truth" SVG version would make sense: it is a logo after all, and as such I expect it to be used a lot more as SVG (or PNG) than an embedded HTML/CSS block of code, which means that the typeface changes can be baked into that "true" logo.

Providing SVG versions means that folks who would like to style it still can do so with CSS, meaning you could add, for example, the version number with a live piece of text using Dinish, but with an "imposed" set of paths for the CSS letters. Anyways I'm basically just repeating Max's point here!

If keeping it as editable text is essential, then I like the idea proposed by @romainmenke — it would be fairly easy to add either an alternate glyph, or a ligature, to correct this issue, but of course, that would require the proper CSS to be enabled so you still get the problem with very basic styling, so the fork might be the way to go in this case?