6 Replies Latest reply on Apr 23, 2003 8:17 PM by Noel Rocher

    internationalize

    Hu Yen-Chuan Newbie

      It good to find Nuke on JBoss.
      I am very interest in internationalizing Nuke on JBoss to Traditional-Chinese.
      How could I do it?

        • 1. mssql-xa-service vs mssql-service
          Noel Rocher Apprentice

          If I want to write a stateless session bean which transacts between two MSSQL datasources, I know I should use an XA transaction. Do I have to deploy a datasource configuring mssql-xa-service or is there a way to use XA transactions with mssql-service?

          Thanks.

          • 2. Re: internationalize
            Viet Master

            support is already in there, though I did not test it yet.

            per component, there is a set of resource bundles and if the component is well done, all the messages should be taken there.

            the resource bundle is chosen with a Locale.

            how do you think the Locale should be defined ? so far it's done by : HttpServletRequest, request.getLocale()

            should it be done with a nukes defined property global to the site + a user defined override ?

            julien

            • 3. Re: internationalize
              Noel Rocher Apprentice

              Hi,

              My idea for internationalization is that all modules should be able to provide their own messages without reusing those of other modules (using prefixes). We surely have to define a default language that should be provided by default and where missing translated message can be found.

              The advantage is that each module is really idependant.
              The disavantage is that some messages can be present several times.

              Independance is a stronger criteria.

              Maybe core messages can be an exception, but not sure because of modifications on core that will compromise a module.

              BUT THERE IS STILL A PROBLEM :
              Our tables are not design to support translated names. For example, a FAQ Category have only one name attribute.

              What I propose is : providing a common mecanism (module)
              that will provide Names translation services. Thus, a table that where the name needs to be translated will use that translation block to add translated names (optional) and, depending on tha request's Local, each getName will present the correct language one (default to the table name).

              Is that sound reasonable ?

              Noel

              • 4. Re: internationalize
                Viet Master

                > Hi,
                >
                > My idea for internationalization is that all modules
                > should be able to provide their own messages without
                > reusing those of other modules (using prefixes).

                I agree

                We
                > surely have to define a default language that should
                > be provided by default and where missing translated
                > message can be found.
                >

                I agree

                > The advantage is that each module is really
                > idependant.

                yes

                > The disavantage is that some messages can be present
                > several times.
                >

                yes also, so since core module is always present, these messages should be there. makes sense ?

                > Independance is a stronger criteria.
                >
                > Maybe core messages can be an exception, but not sure
                > because of modifications on core that will compromise
                > a module.
                >
                > BUT THERE IS STILL A PROBLEM :
                > Our tables are not design to support translated
                > names. For example, a FAQ Category have only one name
                > attribute.

                arghh...... you're doing faq module :-)
                same for html module which could contain several versions of the page.

                one workaround :

                you can use ${ns:key} in faq module as labels
                and add an independant module that does nothing but providing translated names.

                >
                > What I propose is : providing a common mecanism
                > (module)
                > that will provide Names translation services. Thus, a
                > table that where the name needs to be translated will
                > use that translation block to add translated names
                > (optional) and, depending on tha request's Local,
                > each getName will present the correct language one
                > (default to the table name).
                >

                yes, look at my previous statement. you put in DB something like :

                ${translation:xxx}

                and the translation module attach itself as a KeyHandler, one method to define :

                String forKey(String key) { blah blah }

                then on getApi().addKeyHandler("translation", this) during start() phase of lifecycle.

                when nukes renders it, it will trigger forKey method when ${translation:xxx} is encountered and ask your module the value it wants to provide for that name.

                I can add method on Api to give back the Locale according to either : current user definition or request definition (provided by HTTP headers)

                does that fill your requirement ?

                > Is that sound reasonable ?
                >

                yes

                > Noel

                julien

                • 5. Re: internationalize
                  Hu Yen-Chuan Newbie

                  A Stupid question: Is it possible to download (and Test) Nuke on JBoss?

                  I am very interenting in Nuke-like CMS, like PostNuke,XOOPS.

                  I found JNuke, but it isn't works now.

                  • 6. Re: internationalize
                    Viet Master

                    you have to get it from CVS and follow instructions carrefully :

                    http://www.jboss.org/index.html?module=html&op=userdisplay&id=developers/projects/nukes/index

                    we will do a release in the coming weeks

                    julien