Angel, I found the real problem, I think.
1) If you are using UTF-8 characters, be sure to save any text files with
UTF-8 encoding specified. This places a special 3-byte code at the front of
the file that identifies it as UTF-8. This is critical.
2) If you are using UTF-8 characters in your .JS files or HTML, be sure to
specify in your <head> block:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Nothing else should be necessary. The problem was that Jmol was not
recognizing the Binary Order Mark at the beginning of files. This was a
bug. Jmol reads UTF-8 text natively, but was not considering the BOM \uFEFF
at the beginning of the file (or anywhere else, for that matter).
I've fixed that in Jmol 12.2.18 and 12.3.18 and will check in my changes
later this morning.
no need for -D switches.
Bob
Robert M. Hanson
Professor of Chemistry
St. Olaf College
1520 St. Olaf Ave.
Northfield, MN 55057
http://www.stolaf.edu/people/hansonr
phone: 507-786-3107
If nature does not answer first what we want,
it is better to take what answer we get.
-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
