Droid Sans Mono (the Apache-licensed monotype typeface used on Android devices) is a great font, but it has one big disadvantage: the zero is indistinguishable from the O. There is a slashed and a dotted version on http://cosmix.org/software/ (same license). I think a good solution would be to add two USE flags, one 'slashed' and one 'dotted' to the ebuild, and, if active, replace the file '/usr/share/fonts/droid/DroidSansMono.ttf' with DroidSansMono{Slashed|Dotted}.ttf from the website above. Additionally one of those USE flags could be active by default (I'd prefer 'dotted'). Reproducible: Always Steps to Reproduce: 1. Install media-fonts/droid 2. Use the font Droid Sans Mono and type a 0 (zero) and an O Actual Results: Observe that they are indistinguishable Expected Results: Being able to distinguish 0 and O
The fonts from http://cosmix.org/software/ would have to be hosted on Gentoo servers, automatically fetching from the website is not allowed by the site owner.
Where does it say that automatic fetching isn't allowed? I couldn't find that part.
(In reply to comment #2) > Where does it say that automatic fetching isn't allowed? I couldn't find that > part. > I have been told so by the site owner. Maybe it's negotiable ;)
Bumped to -r1 with two new USE flags: slashed and dotted. There's no default but if both are on then slashed takes precedence. Thanks a lot for reporting :)
(In reply to comment #4) > Bumped to -r1 with two new USE flags: slashed and dotted. There's no default > but if both are on then slashed takes precedence. Thanks a lot for reporting :) That sounds perfect :) Though I don't know what I am doing wrong - after syncing today I get [ebuild U ] media-fonts/droid-112_p1-r1 [112_p1] USE="X" 2,870 kB [0] and I can't see new USE flags there.
(In reply to comment #5) > Though I don't know what I am doing wrong - after syncing today I get > > [ebuild U ] media-fonts/droid-112_p1-r1 [112_p1] USE="X" 2,870 kB [0] > > and I can't see new USE flags there. > I realized after committing that the slashed and dotted fonts have a different name than the regular sans mono font, and so I removed the USE flags and the ebuild now installs all variants. Sorry for not saying anything :)
(In reply to comment #6) > I realized after committing that the slashed and dotted fonts have a different > name than the regular sans mono font, and so I removed the USE flags and the > ebuild now installs all variants. Sorry for not saying anything :) Oh, ok. My original idea was, that only the version chosen by the user (via USE flag) gets actually installed, since it's unlikely that anyone wants the same monotype font with just a difference in how the 0 looks like on his machine. Like so: USE="" -> DroidSansMono.ttf gets installed as is USE="dotted" -> DroidSansMonoDotted.ttf gets installed as DroidSansMono.ttf USE="slashed" -> DroidSansMonoSlashed.ttf gets installed as DroidSansMono.ttf (in all the above USE flag constellations, only one Droid Sans Mono will get installed) USE="dotted slashed" -> Like now - all three versions get installed. And now that I think about it, maybe the USE flags should better be called "dottedzero" and "slashedzero" for better clarity.
