Home » railML newsgroups » railML.infrastructure » Infrastructure semantics
Language-sensitive names [message #252 is a reply to message #249] Thu, 12 May 2011 11:15 Go to previous messageGo to previous message
Susanne Wunsch railML is currently offline  Susanne Wunsch railML
Messages: 0
Registered: January 2020
coordination(at)railmlorg (Vasco Paul Kolmorgen) writes:

Hello Tuomas (and others interested in this thread),

>> Are the translations only supported in OCP (in additionalName)?
>> Is there possibility to define language code for OCP's default name?
>
> We added a ticket in our SVN (http://trac2.assembla.com/railML/ticket/121)
> and will integrate additional names and language codes on short notice in
> RailML's version 2.1.

I commited this change according to mentioned ticket.

All elements with id/code/name/description will include the optional
xml:lang attribute for defining the defaults language code.

All theses elements offer the optional element "additionalName" for
defining further names/descriptions with its language codes.

Current ocp element "ocp/propOther/additionalName" is marked
"deprecated" for better using above mentioned structure starting with
railML 2.1.

Is there any need for attribute "type" in "additionalName"? Or is there
any other attribute which is needed in addition to the now provided
ones.

Please, checkout/download current development version and check, if it
works for your needs.

Thank you for revising and improving railML.

Kind regard...
Susanne

--
Susanne Wunsch
Schema Coordinator: railML.common
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Change of infrastructure coordinator
Next Topic: "default" attribute raises implementation problems
Goto Forum:
  


Current Time: Mon Apr 29 11:51:59 CEST 2024