× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



IBM did not create all of the various EBCDIC code pages in isolation. The
code pages were designed by various work/study groups. Within each group
were representatives of IBM, government bodies associated with the
specific language, and other interested parties.

Politics, in the 60s and still today, have a lot to do with how standards
are defined. Unicode for instance has been strongly influenced by government
requirements. Standards don't become "real" standards if nations refuse to
use/allow them...

On Fri, Jan 22, 2010 at 10:26 AM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

Does anybody know why it is that IBM came up with a whole bunch of
EBCDIC codepages that are really just permutations of the same characters?

I mean, I can understand Turkish having its own codepage, given that it
has a few extra letters not appearing in any of the regular European
codepages, and I can understand languages that don't use the Roman
alphabet at all having their own codepages, but . . .

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.