- From: Martin J. Duerst <duerst@w3.org>
- Date: Tue, 21 Mar 2000 08:23:03 +0900
- To: Markus Scherer <markus.scherer@jtcsv.com>, charsets@innosoft.com
This is probably a difficult one. - We don't really want it to be used too much, but the IANA policy for registrations (as far as I have heard from people I consider relevant in this respect) currently tends towards 'register if somebody uses it, even if we think it shouldn't be used'. - Strictly formally speaking, the thing fits the definition for 'charset', but it's really rather far away from the average case. So I would say: Register, but with as big a warning as possible. Regards, Martin. At 00/03/20 10:49 -0800, Markus Scherer wrote: >Hello, > >I just subscribed to this list a few days ago and did not see any traffic >that would have shown me the table manners. >My job is with IBM in a team that produces Unicode- and I18N-related >libraries for Java and C/C++. > >Proposal: I would like to register an encoding as follows with the IANA >list at >http://www.isi.edu/in-notes/iana/assignments/character-sets : > > >Name: SCSU >MIBenum: 107 ?? >Source: A Standard Compression Scheme for Unicode, Unicode Technical >Report #6, http://www.unicode.org/unicode/reports/tr6/ >Alias: [none] > > >This is a character encoding scheme for Unicode. Algorithmic >transformation of Unicode text to and from SCSU is fairly >simple and can yield a similar code point:byte count ratio as legacy >encodings. It is stateful. US-ASCII and ISO-8859-1 text >that does not contain control codes other than NUL, TAB, CR, LF is also >correct SCSU text. SCSU uses all byte values. > > >I am looking forward to get feedback from you and hope to advance this >towards a registration. > > >Thanks, > >markus
Received on Monday, 20 March 2000 22:04:09 UTC