DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2505 Version: 1.3-current Someone might have to explain this patch to me in simple words that I can understand, but I don't understand what it is doing, really. In particular, there is "runtime" code to check the "sizeof(wchar_t)" and do the Right Thing - but of course "sizeof(wchar_t)" will be a constant on any given host so there's a reasonable chance (indeed we need to hope!) that the compiler will optimise away the redundant options on each host leaving just the one option (probably the FcChar32 option on linux, for example...) So... how is that better? I'm missing something important here, obviously... In the previous code, we just used the XFT UTF8 rendering directly, so I assume the intent of this patch is that we "clean" the nominally-UTF8 text into a parsed and "error-corrected" wchar_t string, and then render that - is that what is being done here? Link: http://www.fltk.org/str.php?L2505 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
