DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17127>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17127 [PATCH] I18nTransformer support for multiple catalogues Summary: [PATCH] I18nTransformer support for multiple catalogues Product: Cocoon 2 Version: Current CVS Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: sitemap components AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] This patch extends the I18nTransformer with support for multiple catalogues, as discussed on cocoon-dev in the thread http://marc.theaimsgroup.com/?t=104505932200002&r=1&w=2 Since the "old" configuration style is still supported, users shouldn't be affected by these changes. One thing I added that was not in the original discussion is the possibility to use input modules in catalogue name and catalogue location, e.g. <catalogue id="messages" name="messages" location="{defaults:skin}/translations"/> would use a skin-dependent message bundle. The name and location are re-evaluated on each use of the i18n-transformer, so it is possible to use request-dependent information in there. Next to that, I also fixed what appeared to me as a bug (and was different in behaviour from Cocoon 2.0x): if i18n:text is used inside an i18n:translate element, the content of the i18n:text element was not used as key for translation. The user was required to always use an i18n:key attribute (but only when i18n:text was used inside i18n:translate). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
