> From: Paul Norman [mailto:penor...@mac.com] > Sent: Saturday, January 11, 2014 9:19 PM > To: t...@openstreetmap.org; talk-ja@openstreetmap.org; talk- > k...@openstreetmap.org > Subject: [OSM-talk] CJK fallback fonts - testing needed > > Right now the main OpenStreetMap.org stylesheet uses Unifont as a > fallback font to render Chinese, Japanese and Korean (CJK) characters, > as well as any other characters not present in the DejaVu font. Unifont > is mainly designed to support all characters, and is not designed to > look good. > > I'm looking at Droid Sans Fallback, a free font developed for Android, > and evaluating if it would be a better fallback font than Unifont. > Because I don't read Chinese, Japanese or Korean, I could use help. > > I have prepared a demo at http://tile.paulnorman.ca/demo/fonts.html with > three layers: conventional OSM.org, tiles without any fallback font, and > tiles using Droid Fallback as a fallback font. > > What I would like is for people to look at the difference between the > conventional OSM.org and Droid Fallback tiles and see which is easier to > read for the CJK glyphs. The tiles without any fallback font can be used > to find areas where DejaVu doesn't have glyphs and the fallback font is > being used.
I've gathered various feedback and comments > The fonts are too small Andy wants to increase the font size, but this is a separate issue. Currently the smallest font-size is 8pt, so even if everything gets bumped up 2pt, that's still 10pt. Rendering POIs on a webmap means you need small fonts to get everything in. > The hinting and anti-aliasing of the characters is bad It's not clear if this comment is about it being bad, or it being worth with Droid Fallback than with Unifont. The first is not relevant for what I'm looking at right now, but the second would be a concern. > Missing glyphs It is intentional that I am missing glyphs on the test rendering, as I don't want Unifont used at all while testing. > Different fonts are needed for labels based on their language, even when > the characters are the same in two labels This is a complicated one. Frankly, as long as people are using tags like name=近畿 (Kinki Region) instead of putting the name of the feature as it is on the ground (e.g. name=近畿), the chances of being able to do this are about zero. If it was tagged consistently, you could maybe detect that name is the same as name:xx, know that you're in the xx language, and adjust fonts accordingly. This would be some time off, and definitely out of scope for what I'm doing right now. > smaller pieces of kanji are easier to read with droid sans > droid font looks better for Hangul Good feedback to hear _______________________________________________ Talk-ja mailing list Talk-ja@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ja
