You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2014/06/08 15:06:01 UTC
[jira] [Resolved] (ROL-1434) lots of UI messaging needs to be
converted to i18n keys in resource bundles
[ https://issues.apache.org/jira/browse/ROL-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Mazza resolved ROL-1434.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.1
Assignee: Glen Mazza (was: Roller Unassigned)
Fixed, added additional keys in except for messages for rare/unexplained system errors where an English string would be more helpful in googling for help.
> lots of UI messaging needs to be converted to i18n keys in resource bundles
> ---------------------------------------------------------------------------
>
> Key: ROL-1434
> URL: https://issues.apache.org/jira/browse/ROL-1434
> Project: Apache Roller
> Issue Type: Task
> Components: User Interface - General
> Reporter: Allen Gilliland
> Assignee: Glen Mazza
> Fix For: 5.1
>
>
> As part of the struts2 migration a large amount of work was done to prevent our UI code from blindly throwing exceptions which are unhandled and provide no valuable response back to users. In a wide variety of places throughout the struts2 code there are message strings which are returned which aren't i18n keys coming from the resource bundles.
> Most of these places should be marked in the code via the comment ... // TODO: i18n
> The work here is just to go through the code, find these places, and convert raw strings into i18n keys in the resource bundles.
> NOTE: this same situation applies for all the struts2 validation files which currently list i18n keys which may not exist in the resource bundles and need to be added as well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)