generation of gnu/java/locale/*.uni
I'm looking at updating java.lang.Character to JDK 1.4 specs (and Unicode 3.0). Does anyone know what programs generated gnu/java/locale/*.uni? I ask because I need to add more information to each character to cover the new DIRECTIONALITY category designations. If the generation program is not currently in the distribution, I'll write up a quick Java program and add it to Classpath. -- This signature intentionally left boring. Eric Blake [EMAIL PROTECTED] BYU student, free software programmer ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: generation of gnu/java/locale/*.uni
Eric Blake <[EMAIL PROTECTED]> writes: > I'm looking at updating java.lang.Character to JDK 1.4 specs (and > Unicode 3.0). Does anyone know what programs generated > gnu/java/locale/*.uni? I ask because I need to add more information to > each character to cover the new DIRECTIONALITY category designations. > > If the generation program is not currently in the distribution, I'll > write up a quick Java program and add it to Classpath. doc/unicode/unicode-muncher.pl Brian -- Brian Jones <[EMAIL PROTECTED]> ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: generation of gnu/java/locale/*.uni
Brian Jones wrote: > > doc/unicode/unicode-muncher.pl Thanks. Should I try to update Classpath to Unicode 3.2.0 (currently in beta, expected to be final next month), 3.1.1 (the current stable state), or 3.0 (the version mentioned in the 1.4 javadoc of java.lang.Character)? JLS 3.1 states "The Java platform will track the Unicode specification as it evolves. The precise version of Unicode used by a given release is specified in the documentation of the class Character." I think the choice is between documenting that we are using the latest definition 3.2.0, or else sticking with 3.0.0 to match the behavior of Sun, but want to know what others think. -- This signature intentionally left boring. Eric Blake [EMAIL PROTECTED] BYU student, free software programmer ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: generation of gnu/java/locale/*.uni
Eric Blake <[EMAIL PROTECTED]> writes: > Brian Jones wrote: > > > > doc/unicode/unicode-muncher.pl > > Thanks. Should I try to update Classpath to Unicode 3.2.0 (currently in > beta, expected to be final next month), 3.1.1 (the current stable > state), or 3.0 (the version mentioned in the 1.4 javadoc of > java.lang.Character)? > > JLS 3.1 states "The Java platform will track the Unicode specification > as it evolves. The precise version of Unicode used by a given release is > specified in the documentation of the class Character." I think the > choice is between documenting that we are using the latest definition > 3.2.0, or else sticking with 3.0.0 to match the behavior of Sun, but > want to know what others think. As I recall Unicode now requires more bits than a Java 'char' allows. I don't know that helps at all? I don't really know what Sun's solution is. It looks like we did update to unicode data 3.0, but I know our implementation fails many Mauve tests related to Character. Brian -- Brian Jones <[EMAIL PROTECTED]> ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
