On Wed, 18 Feb 2009, Lorenzo Fiorini wrote:

Hi,

> > Are there restrictions I can't see?
> Maybe I found the problem.
> If I replace XWC_DEFAULT_FONT_ENCODING   "iso10646-1" with "*-1" I get
> many fonts working.

Yes though this are not unicode fonts so not in all countries it's an
option.
Looks that we have missing HB_GTI_* action for setting code encoding
which is kept in szFontEncoding GTXWC structure member. It should be
reactivated.
I also think that we should give direct access to use X11 font selection
instead of keeping the current code which tries to use some meta
multiplatfrom layer. I do not think we ever will be able to agree common
for different platfrom font description and translation rules to native
representation. Number of Windows only features in GTWVT is growing up
so I think we can add few ones for GTXWC. It will make *nix users life
much easier, f.e. sth like:

   REQUEST HB_GT_XWC_DEFAULT
   proc main()
      local cFont
      hb_gtInfo( HB_GTI_FONTSEL, cFont := xFontSel() )
      alert( "What do you think about it???;;" + cFont )
   return

   function xfontsel()
      local hProcess, hStdOut, cFontSel, n
      hProcess := hb_processOpen( "xfontsel -print",, @hStdOut )
      if hProcess != -1
         cFontSel := space( 256 )
         n := fread( hStdOut, @cFontSel, len( cFontSel ) )
         cFontSel := left( cFontSel, n )
         hb_processClose( hProcess )
         fclose( hStdOut )
      endif
   return cFontSel

> Not all are usable but at least there are choices.

If you install unicode fonts then you will also have more choice.
With HB_GTI_FONTSEL you will be able to chose any existing font.

best regards,
Przemek
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to