On 6/22/08, Andreas Hartmann <[EMAIL PROTECTED]> wrote: > Wolfgang Jeltsch schrieb: > > I don't understand this. I thought by creating a file cmsui_de.xml in my > > publication, I create a separate catalogue and the fallback mechanism would > > choose this cmsui_de.xml file instead of the one of the default publication. > > Unfortunately the (aggregate-)fallback:// mechanism can't be applied to > i18n, at least not without serious performance degradation. The i18n > transformer uses a single (global) URI to reference the catalogue, and the > first result of the request to this URI is cached. So, the first requested > publication would win, and all subsequently requested publications would use > the same i18n messages. > > You'd have to switch off caching (which will make the application really > slow) or declare a dedicated transformer for each publication. > > A possible solution would be an enhanced i18n transformer which > * builds the catalogue URI dynamically based on the current publication > * maintains a set of catalogues (one per publication) > * caches all these catalogues > > What do the others think? > -- Andreas
We can (and probably did) discuss this on the Dev ML. My goal is for the XMLSerializer to translate using Publication/Module-specific i18n catalogues without changing undefined elements, then the HTML Serializer finishes transforming all i18n elements with the "untranslated" message if necessary. This eliminates the need for developers to remember to call the I18nTransformer (and likely upset people believing serialization is not a transformation) while storing i18n catalogues with their functions. The i18n catalogue cache will contain separate entries for every Module in every Publication plus the global Modules. No global catalogue will exist -- (almost) everything will belong to a Module including all i18n configuration since i18n translation is useless without some text to translate. The publication title can be overridden in a publication-specific module's catalogue. For the OP: Just edit page2xhtml.xsl to change the <td id="publication-title"> section to display what you want. Use i18n elements named with your publication-id if needed e.g. "mypub-publication-title". solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
