Changes between Version 3 and Version 4 of MultilingualMetadata


Ignore:
Timestamp:
Dec 4, 2008, 3:05:34 AM (15 years ago)
Author:
Fxp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MultilingualMetadata

    v3 v4  
    6161}}}
    6262
     63
     64
    6365SchemaLoader should be able to register complexType which are extension based on a PropertyType (and not only a Type). For example :
    6466{{{
    … …  
    7375}}}
    7476
     77
    7578For title which is a gco:CharacterString_PropertyType, xsi:type could be :
    7679 * gco:CharacterString_PropertyType
    … …  
    7881Then if an xsi:type="gmd:PT_FreeText_PropertyType" the element is edited in multilingual mode.
    7982
    80 
    81 Via schema_suggestion, the editor will define if one element should be « suggested » as multilingual or not and which languages to suggest.
    82 {{{
    83 <field name="gmd:title">
    84 <suggest name="xsi:type" value="gmd:PT_FreeText_PropertyType">
    85   <lang value= « eng »/>
    86   <lang value= « fra »/>
    87   <lang value= « deu »/>
    88   <lang value= « ita »/>
    89 </suggest>
    90 </field>
    91 
    92 }}}
    93 
    94 
    95 Then the editor will suggest multilingual editing interface.
     83In the editor any gco:CharacterString could be multilingual. The gco:CharacterString is in default language, the other PT_FreeText elements has to use a locale declared in the metadata document.
    9684
    9785==== GUI ====
    … …  
    9987A list of all available languages is proposed to the user next to all gco:CharacterString elements.
    10088
    101 Label (?)* : _input_________________  [Language selection list]
     89Label (?)* : _input_field_____  [Language selection list]
    10290
     91The editor can switch to another language using the selection list and could add a new translation.
    10392
    10493