On 2002-11-30, Henrique Peron wrote: > Obviously, we cannot define the same CCSID (Coded Character Set IDentifier, > a.k.a. CPxxxx codepage number) for two different codepages. > > My proposal: > > In order to preserve the standard codepages, I would like to name those > codepages as follows: > > cp1254 (Standard) ==> cp1254 > cp1254e (Azeri) ==> cp2254 > cp1251 (Standard) ==> cp1251 > cp1251k (Kazakh) ==> cp2251 > > After a lot of research on the web, I've found no cp225x codepages, so > it seems that there would be no conflicts.
Hm, while I like your idea to assign new codepage IDs to codepages without offical ID, and the 02xxx codepage range is in fact still free also in my own CODEPAGE.LST (which is a superset of CDRA level 2 and various other standards - although, as we've seen, not completely up to date in regard to the latest ID assignments), it seems you have missed some parts of my 2002-11-22 post under the subject "Re: Codepage IDs"... In there I explained, that it is not a good idea to assign new codepage IDs on your own behalf: | According to IBM's Character Data Representation Architecture | (CDRA level 2) there are two special areas within the 16-bit | Code Page ID space for variations of existing Code Pages and user | or OEM definable Code Pages. This is exactly the way to go until | IBM would assign an offical ID for a new Code Page. Everything | else undermines the system, which I think, is a bad idea, even | though there are quite a large number of Code Pages which have | been assigned without first checking with IBM and there are | still many Code Pages not having official Code Page IDs, yet. And some of them /do/ conflict in very painful ways now. A bit later I wrote: | The range E000h..EFFFh is used for varitions of existing Code Pages, | and if possible should be assigned so that the LSBs are still | matching the parent Code Page. That's why NECPINW.CPI also supported | the new variant of Code Page 850 with Euro sign under ID 58194 | (CP 850 = 0352h, CP 58194 = E352h). So, while this is up to the user/OEM/etc, variants of codepages 1251 and 1254 should get E000h added, so that 1251=04E3h and 1254=04E6h become E4E3h=58595 and E4E6h=58598 respectively. Would there be more than one variant, you could, for example, add another 0400h, so that the 2nd variant of 1251 would get added E400h resulting in codepage 59619, and so on. Note, that these IDs are not unambiguous, as without central coordination different people could assign different variants to these IDs, but that doesn't harm the CDRA standard as these ranges are explicitly reserved for such extensions, so being unambiguous in there is allowed (although not preferred) by definitionem, while it is not allowed in the other ranges (it still happens, though, because many people do not know of CDRA). I also wrote: | | The IBM CDRA level 2 standard reserves Code Page IDs FF00h..FFFEh | | for user definable "private use" assignments. | | This means, Code Pages in the FF00h..FFFEh (or better FFFDh) range may | vary completely from user to user, device to device, and/or manufacturer | to manufacturer. So, switching to them via CHCP does not necessary | create reasonable results depending on circumstances. Switching to | them via MODE dev: CODEPAGE SELECT=nnnnn will still work fine, as | you can select different Code Pages for different devices then. Once IBM decides to officially include the new codepage in their registry (in CDRA or related projects), you can switch over to the new IDs and fade out the temporary ID. AT least this is how I interpret the CDRA standard. Greetings, Matthias -- <mailto:[EMAIL PROTECTED]>; <mailto:[EMAIL PROTECTED]> http://www.uni-bonn.de/~uzs180/mpdokeng.html; http://mpaul.drdos.org "Programs are poems for computers." ---------- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
