cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32690] - [i18n] extending the I18nTransformer
Date Tue, 14 Dec 2004 11:38:44 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32690>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32690





------- Additional Comments From vgritsenko@apache.org  2004-12-14 12:38 -------
Christoph,

Just so that you know where I18nTransformer is (or supposed to be, or can be)
moving...

I18nT should have most of catalogue handling code removed, and should not have
any catalogue configuration information beside simply specifying the ID of
catalogue set it wants to work with:
  <catalogue-set name="foo"/>

Real configuration of the catalogues should happen within i18n bundle component,
probably as:
  <i18n-bundles logger="core.i18n-bundles">
    <catalogue-set name="messages">
      <catalogue id="messages" name="messages"
                 location="context://samples/i18n/translations"/>
      <catalogue id="menu" name="menu"
                 location="context://samples/i18n/translations"/>
      <catalogue id="tiered" name="messages">
        <location>context://samples/i18n/translations/tiered</location>
        <location>context://samples/i18n/translations</location>
      </catalogue>
    </catalogue-set>
    <catalogue-set name="foo">
      ...
    </catalogue-set>
  </i18n-bundles>

This way, catalogue handling part and actual catalogue usage are nicely
separated into two independent components (and you can easily overide one of
them without touching another)

Relevant link to archive:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107426274218350


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Mime
View raw message