- From: tomerm via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Feb 2016 11:18:13 +0000
- To: public-i18n-archive@w3.org
EBCDIC isn't a single code page (as a matter of fact Unicode also can refer to UTF-8 / UTF-16 code pages). Many of EBCDIC code pages are mentioned at: https://www-01.ibm.com/software/globalization/ccsid/ccsid_registered.html In my previous comment I referred to - EBCDIC Hebrew (cp-424) - https://www-01.ibm.com/software/globalization/ccsid/ccsid424.html and also here: http://www.tachyonsoft.com/cp00424.htm - EBCDIC Arabic (cp-420) - https://www-01.ibm.com/software/globalization/ccsid/ccsid420.html and also here: http://www.tachyonsoft.com/cp00420.htm Both Arabic and Hebrew EBCDIC (cp-424 and cp-420) are visual. The visual nature stems from correlation between storage and display on green screens (old ones: https://en.wikipedia.org/wiki/IBM_3270 or screen emulators - modern software which mimic old screens via desktop app such as IBM HOD - http://www-03.ibm.com/software/products/en/rationalhostondemand or non IBM such as ERICOM - http://www.ericom.com/tn3270.asp ). In modern operating systems (i.e. Windows, Android etc.), text stored in the buffer in the chronological order (the same order in which it was typed), undergoes reordering (performed by UBA [Unicode Bidi Algorithm] compliant Bidi engine) before it is rendered on the screen. As opposed to modern operating systems, on legacy systems (i.e. green screens) there is no any transformation which text undergoes before it is rendered. Namely it is rendered exactly like it appears in the storage. -- GitHub Notification of comment by tomerm Please view or discuss this issue at https://github.com/w3c/charmod-norm/issues/80#issuecomment-187128394 using your GitHub account
Received on Monday, 22 February 2016 11:18:15 UTC