On Thu, 30 Sep 2010 22:33:33 +0200 Jirka Kosek <[email protected]> wrote:
> This was never suggested way how to customize localization. You > shouldn't copy existing localization, just override existing one as is > described at: > > http://www.sagehill.net/docbookxsl/CustomGentext.html > > In short local.l10n.xml has to point to XML structure like: > > <l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0";> > <l:l10n language="xxx"> > ... localization customizations go there ... > </l:10n> > </l:i18n> > > By copying current l10n.xml you have broken this expected structure as > there are no directky nested localization customization instead only > href attribute is pointing to localization data for one language. This > allows lazy loading implementation. However this approach is used only > for default localization data, all customization has to use same > mechanism as before. I see, there should be only one file to rule them all. But, I must confess, that modular structure, imitating the stock directories/files, was very appealing. -- Costin STROIE Informatics Consultant BitDefender ------------------------------ Email: [email protected] Phone: +40 212 063 470 ------------------------------ www.bitdefender.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
