Well, I am not familiar with git or github and don't know by mind how to do a Pull Request. But I can try to improve the unicode.html (I guess it is generated from https://github.com/fltk/fltk/blob/master/documentation/src/unicode.dox

1. I would delete all the Unicode/UCS history and explanations what Unicode and UTF-8 was/is, because that is written already in better form elsewhere. So let's strictly focus on "Unicode in FLTK" (especially where FLTK does not – yet or never – support this-and-that Unicode feature). Maybe we later might describe the bare minimum what a FLTK user must know about Unicode to use it properly in FLTK.

For that I'd like to know what is meant with [OksiD] in the documentation? It looks like a link or reference, but it is not.

2. All these "wide character" functions looks weird to me. I've heart that on MS Windows they are (or was?) quite common. Same for "Multibyte" character sets. Still necessary or old crap that should be removed quickly? Maybe a Windows programmer can tell us more.

3. I don't know whether it is a good idea to double the whole POSIX filesystem API in a "unicode-aware variant". We have C++, there is std::filesystem since 6 years now, a fallback to boost::filesystem is acceptable for pre-C++14 compilers, I think.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.