On 22.11.2010, at 17:04, Albrecht Schlosser wrote: > The only important point I can see is that the user's application should > not crash (not even with a controlled assert()), if s/he uses standard > FLTK functions. However, I don't know if we can achieve this...
Yes, you are right. I am afraid that there is still quite some work to do for all kinds of text management... . > I'm thinking of test/editor: can/should it check the text buffer after > reading a file? Sometimes you don't know a file's encoding before > you open it, and what about the file chooser's preview? Could it > crash a user's program if s/he looks at a file in CP-1252 encoding? > > How much can we do about this? We can not check and guess the format of all files. But we must ensure that loading and saving a text file without editing it should always create exactly the same file again (no hidden conversions), and that none of the widgets crashes if there is an unsupported UTF8 sequence. Matthias _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
