RE: [widgets] i18n proposals document

Hi Marcos,

My fault: I completely missed the exchange you mentioned.

The comment is quite relevant if there is only one config.xml. But obviously your response should have clarified that for us. I should have caught your question and make a comment back then.

My personal opinion: while having single file like config.xml with multiple translations is not as good as separate files, it is not a show-stopper either. Localization is possible in both cases, and that is the most important part.

Kind regards,
-yves



> Although we allowed multiple config.xml files in the current published
> WD, we made the decision to move to a single config.xml file based on
> feedback received from i18n core as part of their LC review comments [1]:
> 
> [[
> "2. Section 7.4 (Widget) The various language bearing elements such as
> <name>, <description>, etc. are of the zero-or-one type. However, it is
> typically better to allow any number of these elements to occur,
> provided that none share the same xml:lang. This allows for localization
> (which is part of the point in allowing xml:lang on the element)."
> ]]
> 
> In [2], I responded to the above by saying:
> [[
> "We followed "Best Practice 12: Working with multilingual documents" in
> Best Practices for XML Internationalization, where it says we
> should have different documents for this kind of localization (to
> achieve what you propose, we allow multiple configuration documents in
> a widget).
> 
>    Does i18n core recommend we drop allowing multiple configuration
> documents and use xml:lang in multiple elements in the manner
> suggested above? We have built a lot infrastructure around the current
> model in the spec, so if it's all the same we would prefer to keep it."
> ]]
> 
> We didn't receive a reply from i18n; so, after further consideration, we
> decided to go with having a single config.xml file and rely on xml:lang
> to differentiate between localized and unlocalized content.

Received on Friday, 17 April 2009 14:54:35 UTC