This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Character Set used in v2 messages"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 3: | Line 3: | ||
UTF-8 is the defacto standard encoding for v2 messages in Northern America, in Europe it's ISO 8859-1 (Latin-1). UTF-8 is the commonly used encoding for UNICODE. Note that UNICODE is an example of a character set, it is not a character encoding. Use "UNICODE UTF-8" in MSH.18 and | UTF-8 is the defacto standard encoding for v2 messages in Northern America, in Europe it's ISO 8859-1 (Latin-1). UTF-8 is the commonly used encoding for UNICODE. Note that UNICODE is an example of a character set, it is not a character encoding. Use "UNICODE UTF-8" in MSH.18 and | ||
you're all set. | you're all set. | ||
| + | |||
| + | See [http://www.unicode.org/unicode/faq/utf_bom.html UNICODE FAQ] for details aof UNICODE and its encodings (UTF-8, UTF-16, UTF-32) | ||
== Hints == | == Hints == | ||
*Try to avoid using operating system specific character pages (e.g. Windows cp1252, Mac code pages, EBCDIC variations) | *Try to avoid using operating system specific character pages (e.g. Windows cp1252, Mac code pages, EBCDIC variations) | ||
Revision as of 19:45, 12 June 2006
HL7 doesn't have its own character set. It has a mechanism for escaping multibyte characters, this is mainly/only used by systems that would otherwise mangle a multibyte character (e.g. lots of US 7-bit ASCII systems)..
UTF-8 is the defacto standard encoding for v2 messages in Northern America, in Europe it's ISO 8859-1 (Latin-1). UTF-8 is the commonly used encoding for UNICODE. Note that UNICODE is an example of a character set, it is not a character encoding. Use "UNICODE UTF-8" in MSH.18 and you're all set.
See UNICODE FAQ for details aof UNICODE and its encodings (UTF-8, UTF-16, UTF-32)
Hints
- Try to avoid using operating system specific character pages (e.g. Windows cp1252, Mac code pages, EBCDIC variations)