You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2005/08/13 10:49:54 UTC

[jira] Created: (FOR-628) I18n Management

I18n Management
---------------

         Key: FOR-628
         URL: http://issues.apache.org/jira/browse/FOR-628
     Project: Forrest
        Type: Improvement
  Components: Other  
    Versions: 0.8-dev    
    Reporter: Gavin


There is a problem with the current I18N support for content. At present
it is the responsability of the plugin designer to ensure their plugins
are I18N compliant. At present none of them are and so only XDocs
rendered in HTML will work in an I18N site.

Cheche and I (Ross) looked at this. What we wanted to do was make it the
responsabillity of core to manage the I18N stuff. We think we may have a
solution using locationmaps, but it reqruies a little work on the
Locationmap code. Basically, instead of using the I18N generator from
Cocoon to resolve the source we would use the locationmap to resolve the
correct source file.

More on this including candidate code examples from the following link.

This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :-

http://issues.apache.org/jira/browse/FOR-618 "Create issues for items discussed at Apachecon"


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (FOR-628) I18n Management

Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-628?page=all ]

Ross Gardler updated FOR-628:
-----------------------------

    Priority: Minor  (was: Major)

> I18n Management
> ---------------
>
>          Key: FOR-628
>          URL: http://issues.apache.org/jira/browse/FOR-628
>      Project: Forrest
>         Type: Improvement
>   Components: Other
>     Versions: 0.8-dev
>     Reporter: Gavin
>     Priority: Minor

>
> There is a problem with the current I18N support for content. At present
> it is the responsability of the plugin designer to ensure their plugins
> are I18N compliant. At present none of them are and so only XDocs
> rendered in HTML will work in an I18N site.
> Cheche and I (Ross) looked at this. What we wanted to do was make it the
> responsabillity of core to manage the I18N stuff. We think we may have a
> solution using locationmaps, but it reqruies a little work on the
> Locationmap code. Basically, instead of using the I18N generator from
> Cocoon to resolve the source we would use the locationmap to resolve the
> correct source file.
> More on this including candidate code examples from the following link.
> This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :-
> http://issues.apache.org/jira/browse/FOR-618 "Create issues for items discussed at Apachecon"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (FOR-628) resolve the i18n sources using locationmap

Posted by "David Crossley (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-628?page=all ]

David Crossley updated FOR-628:
-------------------------------

    Summary: resolve the i18n sources using locationmap  (was: I18n Management)

> resolve the i18n sources using locationmap
> ------------------------------------------
>
>          Key: FOR-628
>          URL: http://issues.apache.org/jira/browse/FOR-628
>      Project: Forrest
>         Type: Improvement
>   Components: Other
>     Versions: 0.8-dev
>     Reporter: Gavin
>     Priority: Minor

>
> There is a problem with the current I18N support for content. At present
> it is the responsability of the plugin designer to ensure their plugins
> are I18N compliant. At present none of them are and so only XDocs
> rendered in HTML will work in an I18N site.
> Cheche and I (Ross) looked at this. What we wanted to do was make it the
> responsabillity of core to manage the I18N stuff. We think we may have a
> solution using locationmaps, but it reqruies a little work on the
> Locationmap code. Basically, instead of using the I18N generator from
> Cocoon to resolve the source we would use the locationmap to resolve the
> correct source file.
> More on this including candidate code examples from the following link.
> This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :-
> http://issues.apache.org/jira/browse/FOR-618 "Create issues for items discussed at Apachecon"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (FOR-628) resolve the i18n sources using locationmap

Posted by "David Crossley (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/FOR-628?page=all ]

David Crossley updated FOR-628:
-------------------------------

    Component: Internationalisation (i18n)
               Locationmap
                   (was: Other)

> resolve the i18n sources using locationmap
> ------------------------------------------
>
>          Key: FOR-628
>          URL: http://issues.apache.org/jira/browse/FOR-628
>      Project: Forrest
>         Type: Improvement
>   Components: Internationalisation (i18n), Locationmap
>     Versions: 0.8-dev
>     Reporter: Gavin
>     Priority: Minor

>
> There is a problem with the current I18N support for content. At present
> it is the responsability of the plugin designer to ensure their plugins
> are I18N compliant. At present none of them are and so only XDocs
> rendered in HTML will work in an I18N site.
> Cheche and I (Ross) looked at this. What we wanted to do was make it the
> responsabillity of core to manage the I18N stuff. We think we may have a
> solution using locationmaps, but it reqruies a little work on the
> Locationmap code. Basically, instead of using the I18N generator from
> Cocoon to resolve the source we would use the locationmap to resolve the
> correct source file.
> More on this including candidate code examples from the following link.
> This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :-
> http://issues.apache.org/jira/browse/FOR-618 "Create issues for items discussed at Apachecon"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira