Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
0.8
-
None
-
None
Description
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"
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"