search

google-code-export / flies

Automatically exported from code.google.com/p/flies
GNU Lesser General Public License v2.1
2 stars 0 forks source link

Externalize all Strings within the JSF UI #103

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
The Seam/JSF-based UI is not yet i18n'ized. This task involves externalizing 
all messages using the standard Seam i18n approach.

Original issue reported on code.google.com by asgeirf on 24 May 2010 at 12:50

GoogleCodeExporter commented 9 years ago

Original comment by Caius.Chance on 10 Jun 2010 at 12:05

GoogleCodeExporter commented 9 years ago

Original comment by Caius.Chance on 10 Jun 2010 at 12:05

GoogleCodeExporter commented 9 years ago 
I have externalized all strings from .xhtml files to messages.properties file.

messages.properties file is the fallback properties file for all languages. The 
strings were from general messages and buttons.

The key of the translation in .xhtml and .properties should be same and without 
space chars to link up properly.

Original comment by Caius.Chance on 24 Jun 2010 at 3:55

GoogleCodeExporter commented 9 years ago 
As with #102, I want to see either a pseudo-localized flies, or a real 
translation in order to test and ensure we don't have any english strings left 
in the UI.

Original comment by asgeirf on 28 Jun 2010 at 4:05

GoogleCodeExporter commented 9 years ago 
There is only non-locale-suffixed .properties files in repo now. The 
*_qc.properties testing files are generated during compile. There are maven 
scripts need for some file copying/moving to be automated.

There are pseudo-localized files generated with l10n:pseudo plugin 
http://mojo.codehaus.org/l10n-maven-plugin/pseudo-mojo.html, they are located 
in target/classes/** which are available for testing.

Original comment by Caius.Chance on 1 Jul 2010 at 5:40

GoogleCodeExporter commented 9 years ago 
I changed match pattern and output directory of pseudo translation plugin, 
removed set-property of en as locale, and ignored generated *_qc.properties 
files in src/main/resources/.

Original comment by Caius.Chance on 2 Jul 2010 at 1:00