On 11 May 2011, at 16:07, Albrecht Schlosser wrote: > On 11.05.2011 16:36, Leonid wrote: >>> Then you should be using fltk 1.3 it is compatible with 1.1 but supports >>> UTF8= >>> for i18n. Fltk2 is too different from 1.1 to allow simple porting of fluid >>> f= >>> iles. >> >> I'm sorry! >> FLTK-1.3 too doesn't want to collect the same file, only errors others >> gives out. > >
> The following is a guess only, but maybe... > > If your fluid file contains text in an extended character set and you > want to read it with FLTK 1.3, then it *must* be encoded in UTF-8. This > means that you can't simply take your FLTK 1.1 fluid file with (e.g.) > chinese or latin-1 characters in whatever-codepage that might have been > used with FLTK 1 (IIRC). Oh yes, that's a good guess! I suspect the OP's files may be encoded in some Cyrillic codepage, rather than UTF8, so that might well come into play here. Conversion from some random codepage to UTF8 ought to be straightforward though, lots of text editors will do it for you, or iconv, or... _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
