Talk:Extension Manager:Localized Addon Text
I guess to bundle the localized information into one bucket is a good idea, and not to go for having the localized information in each element.
Regarding the example, I'd be thankful to use short locale codes here right away. I'd personally put the language into an attribute, that doesn't change the graph, but is looking more descriptive:
<em:localized> <Description em:locale="es-ES"> <em:name>Tab Sidebar</em:name> <em:description>Muestra una vista previa de sus pestañas en su panel lateral.</em:description> </Description> </em:localized> <em:localized> <Description em:locale="nl"> <em:name>Tab Sidebar</em:name> <em:description>Laat voorbeeldweergaven van uw tabbladen in de zijbalk zien.</em:description> </Description> </em:localized>
Regarding the additional properties: Are those required? Like, are we picking up that information often enough at enough places? If so, that's OK with me. From an RDF POV, I'd prefer to not put those arcs into a new vocabulary, though. So I'd rather use http://www.mozilla.org/2004/em-rdf#language?code= for that. Or something of that kind. That looks like a good URL to me, at least.
In the case of where localizable information is missing for one language, we should fall back to the default. It's an interesting question what default would be, do you intend to require the non-em:localized dataset? For Fx3-only extensions, the extension author may not intend to create that.
--Pike 08:14, 29 May 2007 (PDT)
On the additional properties you might be right, possibly an added complication at this stage. It's certainly implementable without and then after some profiling if they turn out to be needed then they could be added in then.
As for the default dataset, yes I was thinking of the non-em:localized set. It's a possibility to have say an em:localized em:locale="default" or something similar, but thinking of the case where an add-on is for Firefox 2 and 3 using that would require putting the default data into both the em:localized and in the non-em:localized place which is somewhat redundant. And of course we have to continue to support the data where Firefox 2 reads it from. So I think regardless of whether this is implemented with em:locale="default" we should still always fall back to the old-style data at some stage.
--User:Mossop 09:15, 29 May 2007 (PDT)