imacarthur wrote:
> Here's an odd thing: I was actually reading the docs (!) for Fl_Input
> and I note that, on this Mac using Safari, the "Character Composition
> Table" does not display the composed characters correctly.
>
> This is true for the fltk-1.1.10 and fltk-1.3.x docs.
>
> Now, what makes this *odd* is that the old fltk-1.0.10 docs *do* display
> the characters correctly.
>
> In the absence of any actual evidence, I am guessing that this is
> because the old docs have a charset line:
>
> META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
>
> Whereas the newer docs do not - I guess that in that case Safari is just
> guessing that they are UTF-8 and messing things up a bit?
>
> Just a thought...
... but appears to be mostly correct ;-)
- old 1.0.10 (online) docs contain a charset statement: okay
- 1.1.10 (normal) online docs don't have it (bad), and adding it makes
them appear okay.
- 1.1.10 online docs *with comments* have "charset=utf-8" (worse),
because they are embedded in the normal FLTK header and (comment) trailer.
- 1.3.0 docs are generated by doxyggen and contain "charset=UTF-8", but
this is currently our worst case, because the input (FL/Fl_Input.H) is
parsed as UTF-8, although it is encoded in ISO-8859-1
Possible solutions:
I wouldn't care much about FLTK 1.1. However, it would be easy to add
"charset=iso-8859-1" to this single file, but then we have the problem
again with the docs with comments. IMHO the only possible solution would
be to add "charset=UTF-8" and convert the compose character table (and
more examples in this file and maybe even more files) to UTF-8.
For FLTK 1.3 we're saying explicitly in Doxyfile:
INPUT_ENCODING = UTF-8
Either we change this to
INPUT_ENCODING = ISO-8859-1
(and edit all docs in ISO-8859-1, where necessary), or we must convert
all files with non-ASCII characters to UTF-8.
The fastest solution would be to change INPUT_ENCODING to ISO-8859-1
(and I'm not keen on having UTF-8 characters in my non-UTF-8-aware
editor (nedit) as well), but I remember that Matt added some UTF-8 text
to some source file(s). However, I don't remember which one, and if this
was for documentation or comments only.
Other opinions?
Albrecht
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
