In a message dated 1/4/02 11:50:50 AM Eastern Standard Time, [EMAIL PROTECTED] writes:
> Remy, > > Excellent. I wish you much success with this in 2002. We can all learn > from > each other here. > > Some thoughts my side is that some of what you need may already be > covered off by the tri-lingual work done for BSR - Alain is the contact > there. > > Alain Chapdaniel > [EMAIL PROTECTED] > ACTIMUM > http://www.actimum.com > > Also - the ebXML UID mechanism can provide the linkage between > the various translations - see http://www.catxml.org for examples > of how to include these into your schema. > > Bon chance, > > Merci, DW. > ================================================================ > Message text written by R�my Marchand > > > I do not know this NESPOLE and will learn what it is and if and how we can > benefit from their efforts. > > We means the EFNET program, an acronym which means European Footwear > Network. > > In EFNET we do not see translation in different languages as so difficult > to organise. > > Our work produces standard XML Schemas. > When we have these schemas, it is possible to translate in each language > the terms used in the schemas and the tags also since they are needed in > human interfaces. > > Translation of the standard XML Schemas is a task which has to be performed > in each country be the national EFNET expert. > > When this is obtained you can compose a message in spanish and the receiver > will read it in german. Example An UK Order will become Une "Commande" . > > We start contacting EAN national organisations to see what they are doing > concerning translation of EAN-UCC Schemas. EAN France has translated these > Schemas. EFNET wants to work with EAN. > > What English speaking people do not understand frequently is that in a > warehouse in Germany or in the Netherlands, the workers who will take an > order in charge for its fulfillment, he or she do not speak another > language than their own. > > e-Commerce has to reach lower level of responsibilities in trading > companies and at this level not all people speak english. > > Regards< > > David, The fellows remarks on translations: EDI did all that. An Invoice for goods is known in all the languages and covered by a symbol. An "additional charge" ditto. Etc. etc. etc.. A parallel table of language_-_version (LV) to symbol(tag) w/sequential_ID_native _key used w/one/any LV value at an "outer" level (yes, indentation would be the correct view) obviates all such language translation problems as soon as the table is populated w/indexed parallel candidate language entries, ... bc. the rest of the tables are ((UN)EDI) and are in substantial usage world wide, aren't they? Is the "wheel" getting it's due from the "inventors"? Point being, so much is done and in place, sholders of giants available to stand upon and see so further. In particular, I requote from above: "terms used in the schemas " --->"and the tags also since they are needed in human interfaces"<--- (EDI!!! the "comonality", of busness "thingies", not just of documents, civil code (Law, LOTS!), International Trade authorities/clients/users (as is, - NOW -, for a long time; precedents that WILL be sought, noticed and used by LAWers and the body-comfortable-with-all-that-EDI-stuff, tho, w/o even knowing so, etc.). Have so few perused (wow! what a SIC thought; "per used", AND saved a keystroke, a " ") the EDI "tables" in it's specs. docs.? They're cool. Regards, Jim Cunningham P.S. Would decreasing logrithmic to time based pricing of spec. body publications cause them to expereience not only sufficient funding, but also greater impact (value over time for the funds spent)? "Adoptive participation" is surely the greatest of those funds, over time and surely "spent". ------ XML/edi Group Discussion List ------ Homepage = http://www.XMLedi-Group.org Unsubscribe = send email to: [EMAIL PROTECTED] Leave the subject and body of the message blank Questions/requests: [EMAIL PROTECTED] To receive only one message per day (digest format) send the following message to [EMAIL PROTECTED], (leave the subject line blank) digest xmledi-group your-email-address To join the XML/edi Group complete the form located at: http://www.xmledi-group.org/xmledigroup/mail1.htm
