- From: Carl W. Brown <cbrown@xnetinc.com>
- Date: Thu, 30 Aug 2001 12:59:24 -0700
- To: <David_Possin@i2.com>, "Kremena Gotcheva" <infom@bcci.bg>
- Cc: <www-international@w3.org>
- Message-ID: <FNEHIHOMIIDPDCIFEJEGKELMCIAA.cbrown@xnetinc.com>
David, Part of the problem is categorizing the data you need. For example you categorize gender for English and German. To be complete you might want to consider that girls in German are neuter(I don't know of other languages that do this) . Tokenizing addresses for say US, Russian and Japanese addresses is not a simple task. Besides a letter for say Venezuela to me would be: Carl W. Brown X.Net, Inc. 3452 Shangri-La Rd. Lafayette, CA 94549 EE.UU.A International mail requires hybrid addresses. Not an easy task. Carl -----Original Message----- From: www-international-request@w3.org [mailto:www-international-request@w3.org]On Behalf Of David_Possin@i2.com Sent: Thursday, August 30, 2001 12:32 PM To: Kremena Gotcheva Cc: www-international@w3.org Subject: Re: International standards for various forms of profile data I will be doing what I can for en_US and de_DE, these being my 2 native locales. Currently I am just collecting whatever data I can find in the areas I listed below. I plan to design a definitive requirement for our March SW release by mid-December, that should give me enough time for a good research and compilation of data. I do plan to host the results on a web site when they are finished, notifying the members of this list of its presence. I might even design it so that members can update the tables for their locale online. The tables will look like this: table lang_table data_id data_type locale data_std data_long data_short data_description 0001 gender en_US male male m male gender de_DE männl. männlich m männliches Geschlecht 0002 gender en_US female female f female gender de_DE weibl. weiblich w weibliches Geschlecht Not all fields might be required for each instance, but so far I was able to store all locale specific information in this format. Thanks for your cooperation, Kremena - Dave "Kremena Gotcheva" <infom@bcci.bg> 08/30/01 01:08 PM To: <David_Possin@i2.com> cc: Subject: Re: International standards for various forms of profile data OK, I can do my best as far as Bulgarian is concerned but please share the results, e.g. publishing on this mailing list or in a personal mailing. I am also working on a project that is likely to involve a lot of i18n. How soon do you need the data? Can you mail me a 'dummy' list of all details you have so far found out you need, to give me something to think on? Much success, Kremena Gotcheva Bulgarian Chamber of Commerce an Industry ----- Original Message ----- From: David_Possin@i2.com To: Hello everybody, I am currently working the i18n/l10n requirements for creating and maintaining company and person profile data for our ecommerce framework. Due to the large diversity of our customers we want to offer standard base data for international support in all supported languages. This was originally done by our customer in their respective local offices, but the magnitude is getting overwhelming and our support staff cannot keep up with their requests. I am looking for resources for specific profile data information in as many languages/locales/cultures/regions as possible, preferably backed up by national standards organizations. Here are the major areas I have started to research: a.. Common Honorifics, Salutations, Titles; their placement rules and correct usage (regular expressions) b.. Gender and Marriage Status specifications (some countries do not allow divorces, but may allow the term separated or legally separated) c.. Surnames and Additions (like Henry III or the Third) d.. Usage of Maiden Names and other genealogical information (I remember Spanish heritage listing as a nightmare: uuuu y vvvv y wwww y xxxxx and so on) e.. Religions and Sub-Groups (like Protestant, Lutheran or Reformed) f.. Legal business identifications (like in Germany: AG, KG, GmbH, GmbH & Co. KG, etc.) There are probably dozens more parts of information that should be used to be complete, there are probably additional fields that don't even apply to a Western culture. I would appreciate getting as much info as I can, I will compile a list and send it out to the group once it looks like I have all. I am especially interested in native standards in the respective languages Thanking all in advance, David Possin International QA Engineer (i18n & l10n) i2 Technologies - Austin g.. h..
Received on Thursday, 30 August 2001 15:59:40 UTC