Dear Ian, > Is there a list of what functionalities this particular patch adds? > > Also, the other patches you have posted - do they need to be applied in > a particular order? > > These patches seem to be mainly linux oriented - have you had a chance > to test on other platforms? Are there any known issues? How has the > testing gone, generally?
My patches are independent of each other. I have not had any issues using these patches together. The Xft and iconv patches are geared towards Linux, and I do not have the opportunity to test on other platforms. However since conditional compilation is used (ie: USE_XFT and HAVE_LIBC_ICONV macros), the new code should have no effect on other platforms. It would be great if others could verify this assumption. Below is a summary of the patches I've posted so far: fltk-1.3-u8wrapper (under STR #1903): This patch enforces the use of UTF-8 wrapper functions to ease future porting. All filename-related system calls (fopen, access, getenv, chdir, system) are changed to their equivalent UTF-8 wrapper function. fltk-1.3-xft (under STR #1903): This patch allows a Unicode string to be drawn with an Xft font set (poor man's Pango). fltk-1.3-iconv.patch (under STR #2148): This patch makes use of libc's iconv() to convert between UTF-8 and other encodings, instead of placing the conversion table inside libfltk. External iconv() implementations are not considered for such use. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
