|
|
As mentioned in the fltk.coredev thread on a roadmap for 1.4.0,
we could really use some help with reviewing the Unicode/UTF-8
docs because the two original contributors rokan and oksid are no
longer active here.
I didn't know enough when I updated the dox to resolve the issues
so please feel free to apply your knowledge to improve the docs at
https://www.fltk.org/doc-1.4/unicode.html and the unicode stuff at
https://www.fltk.org/doc-1.4/todo.html
There's a big difference between being able to add an accented
character to a string, and dealing with higher level issues of case
comparison, non-latin scripts, etc.
To remain Fast and Light, where should FLTK draw the line?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
[ Direct Link to Message ] | |
|
| |