Josh,
In my opinion the correct solution is to save this HTML file as UTF-8
and then declare it as such in the HTML. This should solve the problem
with some browsers not knowing what encoding to use.
(For what it's worth, your current solution seems to work, however.)
G
Josh Sosin a écrit :
Colleagues:
IT staff here recommended that I convert all special characters in
the files to HTML entities (as the solution that should accommodate
most users most easily). I have done this for the 'papyri' section of
the Clist. Before I make these changes to all files will the
community please take a quick look at clist_papyri.html:
HERE, in this *temporary location: http://www.duke.edu/~jds15/
clist_papyri.html
If all is well, please let me know and I shall make the changes
globally. If not, I shall see whether another solution is to be found.
Thank you,
josh
-- -- --
Associate Professor, Classical Studies, Duke University
Director of Undergraduate Studies
Associate Editor, Greek, Roman and Byzantine Studies
Co-Director, Duke Data Bank of Documentary Papyri
www.duke.edu/~jds15
--
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/
