Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Diaeresis/Trema above Capital Umlauts ÄÖÜ are too high #69

Closed
plgruener opened this issue Jul 26, 2015 · 19 comments
Closed

Diaeresis/Trema above Capital Umlauts ÄÖÜ are too high #69

plgruener opened this issue Jul 26, 2015 · 19 comments
Assignees

Comments

@plgruener
Copy link
Contributor

The Trema (two dots) above the Umlaute ÄÖÜÏËŸ (capital) are too high, so that they are towering into the previous line.
Tested with Monoid downloaded from your website yesterday (LineHeight M, Normal Font, Ligatures off) under Ubuntu/Linux in Atom and GVim (and in Konsole) with lineheight=1.

As one can clearly see in the screenshot, the dots seem to be cut off in the middle by line-highlighting, and clashing with the lower j,g,p,q etc.

Using the XL-Lineheight font seems to "fix" this issue, but then the other Characters are too far apart.

monoid-umlaute-fail

@larsenwork
Copy link
Owner

It is actually by design - I used to have capitals with diacritics squeezed vertically but looked weird - especially in all caps text. Not sure how to "solve" this. I've lowered them a bit.
screen shot 2015-07-26 at 19 53 56

@jozsefk9
Copy link

I like the extra large space between lines. Could be matter of taste.

J. K.

N9005

On Jul 26, 2015, Andreas Larsen notifications@github.com wrote:

It is actually by design - I used to have capitals with diacritics
squeezed vertically but looked weird - especially in all caps text. Not
sure how to "solve" this. I've lowered them a bit.
screen shot 2015-07-26 at 19 53 56


Reply to this email directly or view it on GitHub:
#69 (comment)

@plgruener
Copy link
Contributor Author

BTW, same issue with all other accents (eg È,É,Ŝ,Ĉ, …)
I assumed it's a design„flaw“ – you want the caps as big as possible, then there's no space above…don't know if there's an elegant solution.
Problem is, in some sizes/editors I don't see the diacritics at all, so cannot tell the difference between A and Ä.
Sure, large line spacing resolves that issue, but that's against the compact design principle.

@larsenwork
Copy link
Owner

@plgruener Not a "flaw" but by design.

Added it to this poll though: http://goo.gl/forms/TlxGLPkH2e

"Solutions"

  1. You can make the diacritics smaller. Would make it impossible to tell e.g. Ȅ and Ë apart.
  2. Reduce the space between the diacritic and the base character. Would also make it harder to tell them apart + looks weird
  3. Make the capitals with diacritics shorter - i.e. squeeze them vertically. Looks strange but works.

What I originally did was the last "solution" but it looked really odd. Option B in the poll are in between what I originally made and what monoid currently has - i.e. squeezed but not that much.

@plgruener
Copy link
Contributor Author

I agree, solution 3 sounds like the way to go. I think it's acceptable for a monospaced font to have a little odd-looking diacritics (they are only used sparingly in sourcecode, if at all). The version in the poll doesn't even look too strange to me (couldn't test it on small sizes though). Maybe you can later also offer that as an alternate version.

((Yeah, by „flaw“ (not the right word) I meant other font's do avoid that problem by not having such line-filling characters (correct me if I'm wrong, definitely not a font-expert^^), but you took an interesting design-decision. ))

Anyways, keep up the good work, Monoid looks very promising :D

@plgruener
Copy link
Contributor Author

I've played a litte with some other accents, and the Ǎ (A with caron) seems a bit off… it's a straight A (not the normal slightly curved one) and is much too wide (see screenshot). I don't think that's intended?
monoid-a-caron

@larsenwork
Copy link
Owner

Cheers. Ǎ isn't in the font (yet) - thought it wasn't really used? Otherwise add it to #12

@plgruener
Copy link
Contributor Author

Oh, I don't know if it's used, I just hit my dead-keys and the A ;D

@larsenwork
Copy link
Owner

I agree, solution 3 sounds like the way to go. I think it's acceptable for a monospaced font to have a little odd-looking diacritics (they are only used sparingly in sourcecode, if at all). The version in the poll doesn't even look too strange to me (couldn't test it on small sizes though). Maybe you can later also offer that as an alternate version.

Diacritics are used a lot in source code though so sparingly will never be an argument but I'll add the squeezed ones as a download options to regular soon.
Try searching for a common word using diacritics here on github and you'll be surprised.

@plgruener
Copy link
Contributor Author

Similar issue: the bottom curly quotes „ ‚ are too low, their curly part is in the line beneath.
monoid-curly-quotes-fail
(grey part in screenshot delimits line)

The upper curly quotes seem to be fine, however.

@larsenwork
Copy link
Owner

@plgruener good catch - they should have been elevated like the comma

@plgruener
Copy link
Contributor Author

Also, could you add a little dot at their „big end“ (to distinguish better from the straight quotes), or would that make them too undistinctive from the comma?

@larsenwork
Copy link
Owner

I think being able to distinguish them from straight quotes is more important than distinguishing single low quote from comma so I'll go with option "big end" 😉

@larsenwork
Copy link
Owner

@plgruener try this: https://dl.dropboxusercontent.com/u/3019777/Monoid-Regular.ttf

Note that I've changed the UPM so optimum font-size it's now 16px or 12pt depending on your OS. (The actual font-size is unchanged)

@plgruener
Copy link
Contributor Author

Curly quotes look great now, good job 👍
(Now waiting for the lowered diacritics ;)

@larsenwork
Copy link
Owner

En route to 0.55 so closing this

@larsenwork
Copy link
Owner

are currently available as ss14 - will be hardcoded once #94 is solved

@plgruener
Copy link
Contributor Author

Thanks. But what does ss14 mean?

@larsenwork
Copy link
Owner

Stylistic set number 14 - can be used via css (so e.g. atom editor), adobe programs (photoshop etc), apple programs (text edit etc)...but not in basic code editors

https://developer.mozilla.org/en-US/docs/Web/CSS/font-feature-settings
http://arstype.tumblr.com/post/24539110952/accessing-opentype-features-in-apples-own-applications

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants