Discussion:
valgrind log entry hyphenation related?
corvid
2012-12-01 03:23:07 UTC
Permalink
http://starurchin.org/dillo/valgrind/5eaf94da6ca698708497c27cd3d3a50730f6f9f5.html
Sebastian Geerken
2012-12-14 11:33:58 UTC
Permalink
Post by corvid
http://starurchin.org/dillo/valgrind/5eaf94da6ca698708497c27cd3d3a50730f6f9f5.html
I hope this is fixed now.

Somehow, fl_utf8fwd has got problems, especially with strings, which
are not 0-terminated. OTOH, I agreed with Johannes some time ago that
the UTF-8 related methods should not be part dw::core::Platform, since
UTF-8 handling is not platform dependant.

For fl_utf8fwd (or, Platform::nextGlyph, respectively), there is a
replacement, lout::unicode::nextUtf8Char. Anything else could be
completed after the release (unless there are severe problems). Parts
of Fltk can be copied: the respective code is in the public domain.

Sebastian
corvid
2012-12-14 17:31:47 UTC
Permalink
Post by Sebastian Geerken
Somehow, fl_utf8fwd has got problems, especially with strings, which
are not 0-terminated. OTOH, I agreed with Johannes some time ago that
the UTF-8 related methods should not be part dw::core::Platform, since
UTF-8 handling is not platform dependant.
For fl_utf8fwd (or, Platform::nextGlyph, respectively), there is a
replacement, lout::unicode::nextUtf8Char. Anything else could be
completed after the release (unless there are severe problems). Parts
of Fltk can be copied: the respective code is in the public domain.
Which bits are in the public domain?

Loading...