From: George R. <gr...@us...> - 2001-07-31 18:48:15
|
I know it wasn't what you meant, but it was an alternate suggestion. It may not be a good one, but it was a suggestion. The version number that I was refering to was the ICU version number, not the Unicode version number. George Rhoten IBM Globalization Center of Competency/ICU Cupertino, CA, USA Sent by: icu...@dw... To: "'ic...@os...'" <ic...@dw...> cc: Subject: RE: ICU 1.8 and Unicode 2.1 > Well you could have two data sets at once. It would just require two > versions of ICU running at once. It's kind of relateded to > the library > versioning discussion that we have been having lately. You > could try to > make the normal ICU 1.8.1 and make your custom ICU version. > The one that > needs a restriction to a certain version of Unicode has the > nonstandard > version. That's not what I mean by "two data sets at once". That's what I mean by "building 1.8 with Unicode 2.1 data". > It would just be one of those annoying hacks that few people > would want to > try such a thing. After all, the main ICU source code may > eventually use > the exact same version number as your custom ICU does. It > may be worth > looking into. I am not sure I understand what you mean by "After all, the main ICU source code may eventually use the exact same version number as your custom ICU does" but I am pretty sure that as long as Microsoft Windows is stuck on Unicode 2.1 there will be a need to build ICU with "older" data. On Unix, I'd go with a new Autoconf option --with-unidata-dir=some-place and then I could have a data/unidata-2.1 along data/unidata. That would address building ICU with either version of UnicodeData.txt by making it pretty simple (providing the build finds the data it needs there). If I do that, what would be a good way to mirror this on Windows? If you think nobody else will want to have ICU manipulate the same set of Unicode characters as Windows, then I can just dump one UnicodeData.txt on top of another and hopw for the best (what will happen with collation for example?). YA _______________________________________________ icu mailing list ic...@os... http://oss.software.ibm.com/developerworks/opensource/mailman/listinfo/icu |