I'm not sure if this forum has been abandoned or not, but I've just uploaded two monospaced font files that work well in cke, and are easier to read than Courier or Lucida Console: DejaVuSansMono.ttf and DejaVuSansMonoBold.ttf. For better visibility, you may want to try the bold version, but for best results, make both available to cke. Otherwise the font change dialogue doesn't seem to work properly.
The font and cursor will be aligned perfectly in sizes 9 and 10, but using other sizes leads to misalignment.
> I'm not sure if this forum has been abandoned or not, but I've just
> uploaded two monospaced font files that work well in cke, and are
> easier to read than Courier or Lucida Console: DejaVuSansMono.ttf and
> DejaVuSansMonoBold.ttf. For better visibility, you may want to try
> the bold version, but for best results, make both available to cke.
> Otherwise the font change dialogue doesn't seem to work properly.
> The font and cursor will be aligned perfectly in sizes 9 and 10, but
> using other sizes leads to misalignment.
> forum is not abandoned, just it seems that not much is going on. Where
> are the fonts? Cant find them.
> On Mar 11, 10:28 pm, Gerry Busch <gerryb.mob...@gmail.com> wrote:
> > I'm not sure if this forum has been abandoned or not, but I've just
> > uploaded two monospaced font files that work well in cke, and are
> > easier to read than Courier or Lucida Console: DejaVuSansMono.ttf and
> > DejaVuSansMonoBold.ttf. For better visibility, you may want to try
> > the bold version, but for best results, make both available to cke.
> > Otherwise the font change dialogue doesn't seem to work properly.
> > The font and cursor will be aligned perfectly in sizes 9 and 10, but
> > using other sizes leads to misalignment.
It uses TrueType fonts exclusively, Beverly, but recognizes only the fixed-pitch (monospaced) fonts. Even some of those can be problematic, as cke's cursor gets misaligned with many of them; it winds up on top of or between characters, resulting in errors when backspacing or deleting, among other things.
There are usually only one or two sizes for each font face that work properly. On my VGA device, size 9 or 10, except for Courier New, which only works correctly with 8.5 and 11.5.
It uses TrueType fonts exclusively, Beverly, but recognizes only the
fixed-pitch (monospaced) fonts. Even some of those can be
problematic, as cke's cursor gets misaligned with many of them; it
winds up on top of or between characters, resulting in errors when
backspacing or deleting, among other things.
There are usually only one or two sizes for each font face that work
properly. On my VGA device, size 9 or 10, except for Courier New,
which only works correctly with 8.5 and 11.5.
> It uses TrueType fonts exclusively, Beverly, but recognizes only the
> fixed-pitch (monospaced) fonts. Even some of those can be
> problematic, as cke's cursor gets misaligned with many of them; it
> winds up on top of or between characters, resulting in errors when
> backspacing or deleting, among other things.
> There are usually only one or two sizes for each font face that work
> properly. On my VGA device, size 9 or 10, except for Courier New,
> which only works correctly with 8.5 and 11.5.
dragg wrote:
> That’s strange. It has to be some VGA problem with cursor. On my QVGA
> screen all fonts work good in all sizes.
Yes, you're absolutely right! My device uses VGA, and I suspected all
along that cke might not be supporting it properly. A few minutes ago
I downloaded Hou Ming's Force High Resolution utility and applied it
to cke. It improved the font rendering dramatically, and now my fonts
work in all sizes. It also made the horizontal margins a bit
narrower; they had been limiting the text area before, and causing
more text wrap than necessary .
Of course, now the boxes in some of the dialogues have shrunk. For
instance, the search and replace input panel displays microscopic
fonts in very narrow input fields. At the top of the file dialogue
screens, the drop-down list for file types now overlaps the box
immediately below it containing the selected file name. Oh well,
nothing's perfect. ;-)
Gerry
---
"The digital camera at the motor vehicle office can see into my past.
It takes my picture, and shows me my grandfather." ... GB
The problem with all this kind of stuff is that is really dificult to
write code for so many different types of hardware, there is too much
diversity in PDA's and the system calls are very poor and poorly
documented, so you have to do all by yourself. I detected the issue
with the fonts not displaying properly a long time ago but then
somehow it disappeared and I was never able to reproduce it later.
I take note of all those problems and will try to address them if I'm
able some day to retake the cke project.
Thanks for your response and all your efforts with cke, Esteban. The VGA work-around I discovered today has made it possible for me to use cke as my default text editor, even with the resulting tiny font in the search and replace dialogue -- I just paste in my query instead of typing it in. ;-)
cke has already proven itself indispensable for editing HTML. It's what I've been using for the files on my personal website.
By the way, I'm running v. 0.22, and have edited cke.opt manually to force it to save in ANSI by default, instead of in UTF-8.
> The problem with all this kind of stuff is that is really dificult to
> write code for so many different types of hardware, there is too much
> diversity in PDA's and the system calls are very poor and poorly
> documented, so you have to do all by yourself. I detected the issue
> with the fonts not displaying properly a long time ago but then
> somehow it disappeared and I was never able to reproduce it later.
> I take note of all those problems and will try to address them if I'm
> able some day to retake the cke project.
