[
https://issues.apache.org/jira/browse/FELIX-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834747#action_12834747
]
Felix Meschberger commented on FELIX-1988:
------------------------------------------
Re: i18n questions:
The reason why I used "full strings" as the translation strings is, that we use
these in our internal I18N functionality.
Benefits
* The keys are readily usable as the actual value if a translation would be
missing
* No translation needed for the default (english) language
* No "cryptic" strings for missing translations
* Easy translation, since the key can directly be seen as the original to
translate
Problems
* Escaping needed if strings contain spaces etc.
* Missing translations may escape review since they are just regular texts
* Tools don't support this approach
* Hard to adapt if original language strings must be fixed
Weighing the pros and cons, I think it is probably better to go with the keys
as you propose.
For this reason, I have applied your resource file patch as provided.
> Integrate jQuery UI integration into the Web Console Trunk
> ----------------------------------------------------------
>
> Key: FELIX-1988
> URL: https://issues.apache.org/jira/browse/FELIX-1988
> Project: Felix
> Issue Type: Task
> Components: Web Console
> Affects Versions: webconsole-2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: webconsole-3.0.0
>
> Attachments: 2.use-utility-methods.patch, 3.javadoc-public-api.patch,
> 4.webconsole_src_main_resources_res_lib.zip, 5.main_template.patch,
> 6.vmstat.patch, abstr-simple-web-console2.patch, src.zip
>
>
> Valentin Valchev has implemented jQuery UI support in the web console. This
> issue is to keep track of this migration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
