samsonite801
Member
The monospace font bug that was in Kangerade 5.0.9 hasn't been fixed in Lithium Mod. The issue is that the DroidSansMono.ttf font file isn't a monospace (fixed-width) font, so Terminal Emulator, ConnectBot and other terminal-like programs that need a monospace font are messed up--they render the terminal winodow incorrectly. For example, allinone isn't lined up in nice neat columns. I tried to fix it this time by using allinone and selecting:
3 Change Fonts
22 Stock (original)
but that didn't fix the problem.
I'm going to repeat the post I made before which was apparently in the wrong, older Kangerade 4.0.7 thread instead of the Kangerade 5.0.9 thread I had intended to post this in:
Thanks jrummy for a great ROM. I have one small problem that I managed to fix. The Terminal Emulator as well as ConnectBot appear to be using a non-monospaced (non-fixed-width) font. This causes the cursor position as shown to not line up with its actual position where it should be. It also causes full-screen console apps to display incorrectly, since the text on each line doesn't line up with the other lines. E.g. "ls -l" output isn't lined up in nice even columns. I looked into this and discovered that the /system/fonts/DroidSansMono.ttf wasn't a monospaced font. I copied the DroidSansMono.ttf file from the Android SDK (platforms/android-8/data/fonts/DroidSansMono.ttf) onto the sdcard and from there to /system/fonts, and this fixed the issue in both the Terminal Emulator as well as ConnectBot.
su
mountsys
cd /system/fonts
cp DroidSansMono.ttf DroidSansMono.ttf.bak
cp /sdcard/DroidSansMono.ttf DroidSansMono.ttf
cd /
unmountsys
exit
I noticed that all the fonts in /system/fonts/ are dated from 2008. Maybe they should be updated to the newest ones? Or are these custom fonts? Either way it would be appreciated if you could fix the Mono one to actually be monospace. Thanks!
Hey, nice find!
Would you have any idea if it's a font issue that always seems to cause poor behavior in these text entry boxes like for example now as I'm typing messages into any forum from my Droid? The problem is so annoying, and had always done it on every ROM I've tried and even on 3 different Droids I've used, but like for example, right now as I type (doesn't matter what browser I use), but as I'm typing, the text entry box when zoomed-in with software keyboard on, or hardware keyboard on, doesn't matter, but the text entry box is too big, and Android always tries to auto-scroll it left-to-right, and it never does it right. When I scroll it manually to see what the the heck I'm typing in, then when I type another character in, it MOST ANNOYINGLY always scrolls so I can no longer see the text, and just as fast as I try to scroll so I can see it again, then if I even try to move the cursor or type so much as a single letter it ALWAYS auto-scrolls out of view. This BUG, is so bad that it almost seems as if they designed it to try to pi$$ you off because even after it will always scroll to the left so that you can never see what your typing, then when you get to the end of the line and hit carriage return, then it starts auto-scrolling to the right so you can never see what you're typing ever.
I'm typing this on my Droid as we speak and so I'm getting annoyed by this bug as I write this now. It's always bothered me but just accepted it as 'normal'.
Does anybody else have this problem? Is it just me who can never see what they type?
I wish what I could do is just zoom the whole text-entry box out so it is exactly as wide as whichever screen I'm using (portrait or landscape). Then it wouldn't ever scroll at all. So if I do zoom it how I want, then the keyboard looses focus, so I click in the text-entry box again and it auto-zooms in WAY too far again and can't auto-scroll left-to-right again in that same way, so you can never track your cursor. It is major buggy and unintuitive, and I'm always embarrassed to let any iPhone owner try out my Android in case they discover this major annoyance with text entry.
Hopefully somebody knows what I'm talking about. Maybe it's just a font problem, or maybe (I'm hoping) it's just a simple case of PEBKAC.