On Thu, Jan 24, 2002 at 08:48:50AM +0300, Alexander Kotelnikov wrote:
> Hello
> 
> After all changes I made there are still two troubles:

Does this means that you can display in the good way strings
encoded in UTF8 ??

> 1. in small window indicating window size/position on resize/move
> test is displayed too high, with UTF locale I see only some bottom
> pixels of it.
> 2. FvwmPager hurts x font server. I have 5 labeled desktops, and if I
> correctly understood the code FvwmPager loads all fonts to draw on
> desks images separately. So it makes many requests to X for a font and
> sometimes something breaks and I do not see labels at all. Same, but
> less frequent happens to balloons.
> 3. everything works just ok it I use MiniIcons in FvwmPager, but if I
> do not, but set SmallFont then I can get the same trouble as with
> labels or balloons, but sometimes names of the windows can disappear
> one by one (then BadDrawble error is printed into stderr). And I just
> noted, sometime these window names are located in corresponding window
> image as text in move/resize indication window: I see only the bottom
> of a name.
> 
> One technical thing to do is to substitute XCreateFontSet with
> GetFontSetOrFixed in modules.
>

Yes, I think that GetFontSetOrFixed/GetFontOrFixed should be used evreywhere.
In a perfect wolrd we should have a libs files FText.{c,h} with F* functions
with the following correspondance:

  GetFontSetOrFixed or GetFontOrFixed  <-> FGetFontOrFixed
  XmbTextEscapement or XTextWidth <-> FTextWidth
  XmbDrawString or XDrawString <-> FDrawString
  ... etc ...

Basically, almost no I18N_MB ifdef should appear in fvwm codes (but
in the FText.{c,h} files). Also the arguments of the F* functions
should be carfully chosen  to allows "text extension" as using Xft
text rendering.

This is in my TODO list, but not in the first position at all. So, if
you want to do it your are welcome.

Olivier

--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to