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

Rendering name with very close characters, hard to read #1335

Closed
jase88 opened this issue Feb 25, 2015 · 9 comments · Fixed by #2349
Closed

Rendering name with very close characters, hard to read #1335

jase88 opened this issue Feb 25, 2015 · 9 comments · Fixed by #2349

Comments

@jase88
Copy link

jase88 commented Feb 25, 2015

Hello,

The characters of natural=water are very close so that you can not differentiate between "rn" or "m".
example Kernersee

see live at http://osm.org/go/0MEnwKXYl

This seems to affect also other objects like streets, see
http://www.openstreetmap.org/#map=18/51.54463/6.84936

This is of course also depending on the zoom level. Hopefully this can be improved.

Thanks in advance!

@polarbearing
Copy link
Contributor

I assume you mean you can not differentiate between them?
The typographic term is kerning, is that adjustable in carto?
https://en.wikipedia.org/wiki/Kerning

@HolgerJeromin
Copy link
Contributor

iirc kerning is about top-heavy chars with next char is bottom-heavy. This is the case between "Ke" but not between "rn".

@matthijsmelissen
Copy link
Collaborator

Is this an issue already present in the font (DejaVu Sans Oblique)? This is how it looks in OpenOffice:

screenshot

Upstream reports can be done here: https://bugs.freedesktop.org/

@matkoniecz matkoniecz added this to the Bugs and improvements milestone Feb 25, 2015
@daganzdaanda
Copy link

The "rn" combination is actually used in textbooks to show that sans-serifs are a bit less "stable" than serifs when it comes to close spacing.
Kerning is usually coded into a font, and optimized for a normal reading size (e.g. 9 or 10pt). Smaller sizes may not work as well. Also, at a small size the hinting and anti-aliasing on a screen interfere with what you get. And some programs just ignore the kerning tables.

Here, the outline / halo fuses in some places, and makes the letters look even closer than they are.
I'd just increase the letter-spacing (tracking) for all the letters a bit, maybe 2px.

Optionally, we could space all the letters evenly over the whole lake (if that's possible).

@matthijsmelissen
Copy link
Collaborator

I'd just increase the letter-spacing (tracking) for all the letters a bit, maybe 2px.

This is possible, but would look bad for Arabic, see here.

@matthijsmelissen
Copy link
Collaborator

Other example in OpenOffice:
screenshot from 2015-03-02 15 41 02

@matthijsmelissen
Copy link
Collaborator

Reported upstream, let's see what they think.

https://bugs.freedesktop.org/show_bug.cgi?id=89393

@fkv1
Copy link

fkv1 commented Jan 25, 2016

Also, at a small size the hinting and anti-aliasing on a screen interfere with what you get.

Anti-aliasing should be turned off for every kind of text altogether. It makes the text blur without delivering any real benefit. Additional examples at #2028.

@matthijsmelissen
Copy link
Collaborator

This might be fixed in Mapnik3 as well.

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

Successfully merging a pull request may close this issue.

7 participants