You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "Allen Gilliland (JIRA)" <no...@atlassian.com> on 2007/07/10 21:33:30 UTC
[Roller-JIRA] Created: (ROL-1473) Resource bundles need to be
separated into multiple files
Resource bundles need to be separated into multiple files
---------------------------------------------------------
Key: ROL-1473
URL: http://opensource.atlassian.com/projects/roller/browse/ROL-1473
Project: Roller
Issue Type: Sub-task
Affects Versions: 4.0
Reporter: Allen Gilliland
Assignee: Roller Unassigned
In order to effectively simplify the management of the resource bundles we should break things down into various files. At the very least I think it makes sense to separate out the parts of the resource bundles into these files ...
1. email messages. a file for all messages which go into emails.
2. weblog rendering messages. this would be all messages used by weblogs during rendering in templates and macros. this is the bundle that the MessageModel would use.
3. authoring/admin UI messages. the majority of the messages which are used by all the authoring/admin pages. struts2 allows us the option of putting these in package.properties files on the classpath, but if we don't like that idea then we can just do a single resource bundle for all UI messaging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/roller/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Roller-JIRA] Commented: (ROL-1473) Resource bundles need to be
separated into multiple files
Posted by "David Johnson (JIRA)" <no...@atlassian.com>.
[ http://opensource.atlassian.com/projects/roller/browse/ROL-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_13855 ]
David Johnson commented on ROL-1473:
------------------------------------
We need to make it as easy as possible for folks to contribute translations. Eliminating unused keys makes things easier. Having a single file makes things easy too. Perhaps having 3-4 targeted separate files could make it even easier, and I think you've got a good breakdown there, but I'm strongly opposed to having a separate file per Java source package as some suggest.
> Resource bundles need to be separated into multiple files
> ---------------------------------------------------------
>
> Key: ROL-1473
> URL: http://opensource.atlassian.com/projects/roller/browse/ROL-1473
> Project: Roller
> Issue Type: Sub-task
> Affects Versions: 4.0
> Reporter: Allen Gilliland
> Assignee: Roller Unassigned
>
> In order to effectively simplify the management of the resource bundles we should break things down into various files. At the very least I think it makes sense to separate out the parts of the resource bundles into these files ...
> 1. email messages. a file for all messages which go into emails.
> 2. weblog rendering messages. this would be all messages used by weblogs during rendering in templates and macros. this is the bundle that the MessageModel would use.
> 3. authoring/admin UI messages. the majority of the messages which are used by all the authoring/admin pages. struts2 allows us the option of putting these in package.properties files on the classpath, but if we don't like that idea then we can just do a single resource bundle for all UI messaging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/roller/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Roller-JIRA] Commented: (ROL-1473) Resource bundles need to be
separated into multiple files
Posted by "Allen Gilliland (JIRA)" <no...@atlassian.com>.
[ http://opensource.atlassian.com/projects/roller/browse/ROL-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_13856 ]
Allen Gilliland commented on ROL-1473:
--------------------------------------
I agree, I want to make it easy for people to submit translations as well. Having files per java package may be overkill and I am also weary of doing it because the files would be the same name in each package which would even further confuse things.
I like the idea of separating them out a little bit though, like I mentioned above. In particular, the one I feel most strongly about is separating out the keys which are used in weblog rendering. The reason is because this seems like the one that Roller users would be most likely to want to extend so that they could add in support for a language that Roller doesn't support out of the box. For example, if you wanted to blog in arabic then you would want to provide a translation of this file so that everything on your blog shows up in arabic, and separating this out into its own file will make that easier for users to do.
> Resource bundles need to be separated into multiple files
> ---------------------------------------------------------
>
> Key: ROL-1473
> URL: http://opensource.atlassian.com/projects/roller/browse/ROL-1473
> Project: Roller
> Issue Type: Sub-task
> Affects Versions: 4.0
> Reporter: Allen Gilliland
> Assignee: Roller Unassigned
>
> In order to effectively simplify the management of the resource bundles we should break things down into various files. At the very least I think it makes sense to separate out the parts of the resource bundles into these files ...
> 1. email messages. a file for all messages which go into emails.
> 2. weblog rendering messages. this would be all messages used by weblogs during rendering in templates and macros. this is the bundle that the MessageModel would use.
> 3. authoring/admin UI messages. the majority of the messages which are used by all the authoring/admin pages. struts2 allows us the option of putting these in package.properties files on the classpath, but if we don't like that idea then we can just do a single resource bundle for all UI messaging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/roller/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira