> > In which case, loading the text into an Fl_Text_* widget might be an
> > option (it handles larger text files) or make a subclass of
> > Fl_Multi_Browser that only holds a "visible" subset of the 
> full file,
> > and reload it dynamically as the user scrolls - possible 
> but a bit of a
> > hassle to do...
> 
> Displaying plain ascii using the FL_Text_* widgets is known to work,

Good point from Duncan there... I was only thinking in fltk-1.1 mode,
following the OP's post, so assumed it would only be ASCII text. Which
ought to work...


> but please be aware that there are some issues with certain non-ascii
> characters (CP1252 0x80-0x9f) and line-wrapping involving Chinese/CJK
> characters in UTF-8 that are currently being investigated.

And we haven't even touched on the Indic or Semitic scripts yet... We
know we have problems with CJK texts, but it does more or less work,
much of the time.
If we start looking at Semitic scripts, maybe Hebrew or Arabic, then we
need to render text that is predominantly RtoL but with some bi-dir
handling, and variable pitch, and tricky vowel handling and...
Then the Indic scripts... Well, we are going to need some help with
that...




SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 
3EL
A company registered in England & Wales.  Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to