|
From: Tom Liotta >And right here is where Rob's issue probably would become first visible. What he will see will be the >characters according to the character set defined for him in that session on that device. This has no necessary >relationship to a character set defined for a remote customer or partner at a different location on a different >system. Without transmitting appropriate CCSID or code page/character set, he has no way to influence what >someone else sees. Sorry for jumping into this a bit late, but the above is (no surprise) absolutely right. The broken bar (x'6A' in CCSID 37) is not in the base 7-bit ASCII character set, and so moves around based on what ASCII code page the viewer is using. If the target is 1252 (Windows Latin 1) or 819 (ISO 8859 Latin 1) a x'A6' is needed to display the broken bar; but if you're in 437 (PC USA) or 850 (PC Multilingual) that same x'A6' would give you a feminine ordinal indicator (what looks like a superscripted lowercase underlined a). And other country specific code pages would give still other characters for x'A6'.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
