US7ASCII is the 'base' character set. It misses
many many characters. Avoid at all costs unless you are dealing with a
system that has to deal with many distributed legacy
systems.
Western ISO 15 used to be the best character set to
use.
UTF8
or AL32UTF8 is the way to go as this contains all the characters you need.
It also "legally" includes the euro sign
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Potts
Sent: 13 January 2005 22:47
To: U.S. Metric Association
Subject: [USMA:31916] RE: good reason to go metricJim:The degree sign arrived intact.Others, please note that Jim is using ISO-8859-1 (also known as Western European ISO and ISO Latin-1) as his encoding scheme, as do I. Consistency has its benefits.Note that ISO-8859-1 has given me the least trouble of all the encoding schemes I've tried. I gave up on ASCII (which Microsoft redundantly calls US ASCII) a long time ago. Latin-9 (ISO-8859-9) created anomalies, and the UTF-8 implementation of Unicode drastically reduces font choices (because those who produce the fonts haven't got around to providing full UTF-encoded versions for more than a small number of them).Bill Potts, CMS
Roseville, CA
http://metric1.org [SI Navigator]-----Original Message-----I just about choked when I saw this specification for the thermal conductivity of a hi-temp epoxy in a press release (ECN magazine, January 2005, page 46):
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Jim Elwell
Sent: Thursday, January 13, 2005 13:48
To: U.S. Metric Association
Subject: [USMA:31915] good reason to go metric24 BTU/in/ft2/hr/�F
(Hope that degree sign comes out right)
Of course, it should really be W/m•K.
JimJim Elwell, CAMS
Electrical Engineer
Industrial manufacturing manager
Salt Lake City, Utah, USA
www.qsicorp.com
