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.

As I mentioned before, there were two different attempts to introduce UTF-8 into FLTK, which is why there are two different flavours and naming schemes for the UTF-8 routines described in the documentation in unicode.dox.

The [FLTK2] tag in unicode.dox refers to Bill Spitzak's attempt to rewrite the original 1.0 code to create an FLTK-2 release to address design flaws, which included adding UTF-8 support, but FLTK2 never really caught on.

The [OksiD] tag refers to a later attempt by two users, OksiD and rokan, to add / retrofit UTF-8 into the original FLTK1, but why they chose a slightly different approach with different function names is now lost in the mists of time.

The idea was that the code would be refactored to produce a single more coherent interface, but it never happened.

See also "Article #825: What are the versions of FLTK?" at https://www.fltk.org/articles.php?L825

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