when you make an extension you can add in the description.xml file license, display-name, extension-description for different languages. example <extension-description> <src xlink:href="description/component_en.txt" lang="en" /> <src xlink:href="description/component_es.txt" lang="es" /> </extension-description> that's fine and you have language support in the LibO extension manager. but it's not possible to define that the content (color palette, gallery, ...) should be selected depend on the language. The reason is that the path for the content is stored in config.xcu file and there is no lang="" tag available.
example config.xcu file ======================= <?xml version="1.0" encoding="UTF-8"?> <oor:items xmlns:oor="http://openoffice.org/2001/registry"> <item oor:path="/org.openoffice.Office.Paths/Paths/Palette/InternalPaths"> <node oor:name="%origin%/palettes" oor:op="fuse"/> </item> </oor:items>
example config.xcu file with language support ============================================= <?xml version="1.0" encoding="UTF-8"?> <oor:items xmlns:oor="http://openoffice.org/2001/registry"> <item oor:path="/org.openoffice.Office.Paths/Paths/Palette/InternalPaths"> <node oor:name="%origin%/palettes/colors_en.soc" oor:op="fuse" lang="en"/> <node oor:name="%origin%/palettes/colors_es.soc" oor:op="fuse" lang="es"/> </item> </oor:items>
@Heiko, as an extension expert, what's your opinion here?
As an _advocate_ of extensions, I could live with this limitation. Don't see a clear use case for l10n. And ultimately it's possible to ship different extensions.
(In reply to Heiko Tietze from comment #4) > As an _advocate_ of extensions, I could live with this limitation. Don't see > a clear use case for l10n. And ultimately it's possible to ship different > extensions. ok, but why we have than l10n support for the extension manager? the stuff in the extension manager is "only" informativ. The content of the extension (eg. the gallery elements, whatever, ...) is more usefull to have translated. On the other side, which extension developer is interested in translate there stuff in all languages.
Hello Andreas, Heiko, What's the status of this issue? It has been in UNCONFIRMED for a while, what should we do with it ?
As there is a GSOC Student for extensions stuff this would be a good bug for the UI part of the GSOC project.
(In reply to andreas_k from comment #7) > As there is a GSOC Student for extensions stuff this would be a good bug for > the UI part of the GSOC project. Hi Andreas, Heiko, any update on this ?
(In reply to Xisco Faulí from comment #8) > any update on this ? Nope, and I doubt it will be done. You can provide multiple extensions alternatively to the proposed packing of everything into one file. Having different configurations or directories is not feasible. And localization is possible out of the box, see https://wiki.openoffice.org/wiki/Extensions_best_practices#GUI_Localization