-------- Message transféré -------- De: Albert Graham <agraham at g-b dot net> > > Hi Nicolas, > > I installed this fonts a week or so ago and have found one major problem > which has caused my no end of problems. > > The number 0 is too similar to the number 8 (0808080808) the reason for > this is there is a slash going thru the 0 making it look the same (to > me). this in tern has caused me not to spot lots of typos, e.g. > 192.160.0.1 should have been 192.168.0.1, but on my screen I could > hardly tell the difference until up really close! > > I use a rather large font size (14 pt) so I assume these type of typos > are harder to spot with small font sizes. > > Did you spot the typo in the subject line ? > > Any comments ?
Created attachment 6226 [details] Screenshot -------- Message transféré -------- De: Albert Graham <agraham at g-b dot net> > Nicolas Mailhot wrote: > >> Can you provide a screenshot? > >> > >> > > No problem. > > http://g-b.net/kconsole.png > > The focal point is the IP address, in this case a non-routable 192.168.12.4 > > [root@agraham /]# ping 192.160.12.4 > PING 192.160.12.4 (192.160.12.4) 56(84) bytes of data. > > Then after a while I stick my nose to the screen and realize I've made a > typo :)
Viewing the screenshot I can easily distinguish between 0 and 8. I am not sure if something else related to the monitor that is not visible in the screenshot causes a problem. I tried to reproduce in GNOME Terminal by disabling smoothing or hinting. I could not reproduce the type of dot you can see inside the zero. In the screenshot, it looks similar to a thin horizontal bar, which is displaced (a bit higher and to the left). In the screenshot it looks that no smoothing has been enabled in KDE. I am wondering if the reporter could try out with GNOME terminal (gnome-terminal), if it is installed. Another issue that one could take into account is the subpixel order; on my TFT screen, underscores (=thin horizontal bar) show in different colours depending on the value of the subpixel order.
Le Mar 18 juillet 2006 11:15, Paul Howarth a écrit : > I do actually. My eyesight isn't great, but I'm using it at home and at > work (hence two different monitors) and this is the only issue I have > with DejaVu, which I generally like, having used it for a week or so.
(In reply to comment #3) > Le Mar 18 juillet 2006 11:15, Paul Howarth a écrit : > > > I do actually. My eyesight isn't great, but I'm using it at home and at > > work (hence two different monitors) and this is the only issue I have > > with DejaVu, which I generally like, having used it for a week or so. I think it's my eyesight really. If I magnify the text (with a magnifying glass, not by changing any setting) then I can easily tell the difference between 0 and 8. It just means I'll need to use bigger font sizes than I currently use, though for most purposes I can get by with the smaller font. With the old default FC5 font, I had similar difficulties distinguishing between 0 and O, though I don't think that was as big a problem. Paul.
Created attachment 6253 [details] image from gnome-termonal De: "Albert Graham" <agraham at g-b dot net> Hi Nicolas, I really don't want to sign up for this bugzilla, I'm just too busy (as you are), but they did request this image from gnome-termonal, so if you could post that via your account. http://www.g-b.net/gnome-termonal-under-KDE.png Also, It seems that everybody disagrees with my argument on this matter, so I'm no longer following this thread, instead I'm going to buy a 24in LCD braille screen, so next time I'm confused, I can just feel the for that nasty little dot. Thanks. Albert.
De: "Steven Stern" <subscribed-lists at sterndata dot com> A couple of first impressions: I like the dot in the zero, but it looks odd in that it's not centered. I had some other fonts with a centered zero that, to my eye, looked better.
The dot is perfectly centered when using the interpreter -- at least when the figureheight is odd or large enough that it is more than one pixel tall. That screenshot looks like it is auto-hinted: the stems are not snapped to whole pixels and the dot is a three pixel diameter disc rather than one pixel. So, to the OP: recompile freetype with -DTT_CONFIG_OPTION_BYTECODE_INTERPRETER in CFLAGS and you'll find it much easier to read.
cleaning up
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.