You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "James Song (JIRA)" <be...@incubator.apache.org> on 2005/02/03 20:12:24 UTC

[jira] Created: (BEEHIVE-239) control packaging: I18N support for control description/displaynames

control packaging: I18N support for control description/displaynames
--------------------------------------------------------------------

         Key: BEEHIVE-239
         URL: http://issues.apache.org/jira/browse/BEEHIVE-239
     Project: Beehive
        Type: New Feature
  Components: Controls  
    Versions: V1Beta    
    Reporter: James Song
 Assigned to: Kyle Marvin 
     Fix For: V1Beta


This is reminder of task44:Localization strategy for user visible strings.

Currently, displayName and description of FeatureInfo are hard coded on control interface.

Needs a mechanism to save them into .properties files. 

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Resolved: (BEEHIVE-239) control packaging: I18N support for control description/displaynames

Posted by "Kyle Marvin (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-239?page=history ]
     
Kyle Marvin resolved BEEHIVE-239:
---------------------------------

     Assign To: James Song  (was: Kyle Marvin)
    Resolution: Fixed

Resolved by svn 155053:

Added support for localization of strings specified via BeanInfo (org.apache.beehive.controls.api.packaging.*) annotations.  A string annotation value can have the form "%<resource-specifier>%" and the value will be pulled from a resource bundle.  The <resource-specifier> string is a base resource bundle name (which will be customized based upon the default locale) concatenated with a resource name inside the bundle, seperated by '.'.   Generated BeanInfo classes will dynamically pull the string value from the resource bundle, enabling BeanInfo attributes (name, displayName, shortDescription, etc) to be customized for different locales.  The beaninfo test in the Controls checkin test set inc
ludes a sample usage.


> control packaging: I18N support for control description/displaynames
> --------------------------------------------------------------------
>
>          Key: BEEHIVE-239
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-239
>      Project: Beehive
>         Type: New Feature
>   Components: Controls
>     Versions: V1Beta
>     Reporter: James Song
>     Assignee: James Song
>      Fix For: V1Beta

>
> This is reminder of task44:Localization strategy for user visible strings.
> Currently, displayName and description of FeatureInfo are hard coded on control interface.
> Needs a mechanism to save them into .properties files. 

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Closed: (BEEHIVE-239) control packaging: I18N support for control description/displaynames

Posted by "James Song (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-239?page=all ]
     
James Song closed BEEHIVE-239:
------------------------------


The test for this has been running and passing.

> control packaging: I18N support for control description/displaynames
> --------------------------------------------------------------------
>
>          Key: BEEHIVE-239
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-239
>      Project: Beehive
>         Type: New Feature
>   Components: Controls
>     Versions: V1Beta
>     Reporter: James Song
>     Assignee: James Song
>      Fix For: V1Beta

>
> This is reminder of task44:Localization strategy for user visible strings.
> Currently, displayName and description of FeatureInfo are hard coded on control interface.
> Needs a mechanism to save them into .properties files. 

-- 
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