To clarify:
(1) Josh's solution has worked, and so I don't think we need to worry
about my suggestion. It works because the HTML entities with which he
has replaced all accented and other non-ASCII characters are treated the
same way regardless of the encoding of the page.
(2) The reason the page was not working for some people in the first
place was because the HTML page (essentially a plain text file) was
encoded in ISO Latin-1 (aka ISO 8859-1), but that this was not indicated
in the file header in a way that all browsers could understand. (There
was a <meta> tag in the HTML header, but I think it also needed an
encoding statement *above* the <html> tag. Most browsers will default to
Unicode if they aren't told explicitly what encoding to use, so this was
causing errors.
(3) The best solution to this problem would have been to (a) change the
encoding of the page to Unicode so browsers would read the characters
correctly (this would also allow the inclusion of Greek and other
non-Latin characters in the page in the future); or (b) put an encoding
decl on the top line of the file. Preferably both, use Unicode and
declare it explicitly.
However, Josh's solution works, as noted, so let's not confuse the issue
by trying to change anything else. (Until the first Greek or Russian
publication needs to be included in the CList...)
Best,
G
Arzt-Grabner, Peter a écrit :
Josh,
your solution works great on Safari, Fire Fox, and Mozilla as well.
Those are the browsers I tried on my Macintosh.
I am not familiar with all the technical details, so I cannot tell
anything about Gabriel´s recommendation.
Thank you very much for the great work you are doing with the checklist.
Peter
--
Dr Gabriel BODARD
(Epigrapher & Digital Classicist)
Centre for Computing in the Humanities
King's College London
26-29 Drury Lane
London WC2B 5RL
Email: [EMAIL PROTECTED]
Tel: +44 (0)20 7848 1388
Fax: +44 (0)20 7848 2980
http://www.digitalclassicist.org/
http://www.currentepigraphy.org/
