You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Jeanne Waldman (JIRA)" <de...@myfaces.apache.org> on 2007/10/19 20:56:50 UTC
[jira] Resolved: (TRINIDAD-776) add 'translatable' meta-data to all
the component properties that are translatable
[ https://issues.apache.org/jira/browse/TRINIDAD-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeanne Waldman resolved TRINIDAD-776.
-------------------------------------
Resolution: Fixed
Completed: At revision: 586575
on trunk
Changed about 20 xml files in trinidad-build\src\main\resources\META-INF\maven-faces-plugin\components\trinidad
I checked that my changes were ok by comparing the generated faces-config.xml file after the change and before the change.
> add 'translatable' meta-data to all the component properties that are translatable
> ----------------------------------------------------------------------------------
>
> Key: TRINIDAD-776
> URL: https://issues.apache.org/jira/browse/TRINIDAD-776
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Reporter: Jeanne Waldman
> Assignee: Jeanne Waldman
> Priority: Minor
>
> add 'translatable' meta-data to all the component properties that are translatable.
> JDeveloper is going to help a user know when a property is translatable based on the meta-data.
> Adding <property-metadata>
> <mfp:translatable>true</mfp:translatable>
> to the component's XML file will allow this to happen.
> Properties that are translatable are shortDesc, label, text, textAndAccessKey, leadingHeader, etc..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.