[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: languages and tags
Hello Achim and List, given one possible solution to take the whole EDIFACT Data Dictionary I think it would be a very painfull job to translate all the Segment, Element and Code Entries into Memonic english. Some automated jobs (first three words of the official EDIFACT description for example) wont produce very good tag Names in all parts of the system. Therefore I think coded elements are the much better solution here.. after all we are talking about data processing not printing. It is quite easy to store the Full Text Name of every Element in an attribute and use it in a XSL Stylesheet for Visualisation. This means: generic XSL+language selector coded-XML-EDI-Message + DTD-with-fixed-attributes) ---> HTML with localized output Greetings Bernd > -----Original Message----- > From: Achim Gasch [mailto:agasch@saios.com] > Sent: Thursday, March 09, 2000 10:26 AM > To: Matti.Vasara@fingrid.fi; ebXML-Architecture@lists.oasis-open.org > Subject: Re: languages and tags > > > Matti, > > I have also made experiences in multilingual environments for > years and I > completely agree to what you say. Using a 'language' for > describing semantic > relationships between semantic entities has no need for a > NATURAL language, > english would more be used as an semi-artificial > metalanguage, just because it's > te most common one on the global level > > regards > > Achim > > ------------------------------------------------------------------ > Achim Gasch - SAIOS SA > mailto:agasch@saios.com / http://www.saios.com > Tel: + 352 40 55 40 415 / Fax: + 352 40 55 40 6180 > 90-A Rue de Strasbourg, L-2560, Luxembourg > ------------------------------------------------------------------
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC