Activity
From 04/14/2011 to 05/13/2011
05/13/2011
-
04:19 pm I18n 2.4 released
- The I18n team is pleased to announce the *i18n-2.4* release!
Nuiton i18n tools
Documentation of the project can be ... -
04:11 pm Revision 1932: [maven-release-plugin] prepare for next development iteration
-
04:11 pm Revision 1931: [maven-release-plugin] copy for tag i18n-2.4
-
04:11 pm Revision 1930: [maven-release-plugin] prepare release i18n-2.4
-
12:04 pm Revision 1929: add file headers + svn properties
-
11:59 am Revision 1928: add package info (need more documentation inside them...)
- format everything + fix some javadocs
introduce format package to push to I18nMessageFormatter -
11:17 am Revision 1927: fix it
05/12/2011
-
11:38 pm Evolution #1513 (Résolu): Bundle mojo can have distinct encoding to read and write properties files
-
11:37 pm Evolution #1512 (Résolu): Depreciates the tapestry-bundle mojo
-
10:48 am Revision 1926: Bad imports configuration
-
10:40 am Revision 1925: doc improvement
05/11/2011
-
05:46 pm Revision 1924: update docs
-
05:46 pm Revision 1923: fix inheritance...
-
04:51 pm Revision 1922: clean api
-
04:48 pm Revision 1921: clean javadoc and it
05/10/2011
-
12:16 am Revision 1920: Evolution #1516: Updates to m-helper-p 1.3
-
12:15 am Evolution #1516 (Résolu): Updates to m-helper-p 1.3
- Required to have last version of *SortedProperties*
-
10:41 pm Evolution #1507 (Résolu): Introduce BundleFormatConverter to allow format conversion with bundle ...
-
10:40 pm Evolution #1515 (Résolu): Add AvailableConverterMojo for BundlerFormatConverter
-
10:39 pm Revision 1919: #1515 : Add AvailableConverterMojo for BundlerFormatConverter
-
10:36 pm Revision 1918: Rename converter and remove previous commented implementation
-
10:28 pm Evolution #1515 (Résolu): Add AvailableConverterMojo for BundlerFormatConverter
- Usage :
@mvn i18n:available-converters@
Useful to display all BundlerFormatConverter found by plexus -
10:16 pm Revision 1917: Evolution #1513: Bundle mojo can have distinct encoding to read and write properti...
-
10:16 pm Evolution #1513 (Résolu): Bundle mojo can have distinct encoding to read and write properties files
- By default the *encoding* parameter is used, but you can defined a *bundleInputEncoding* (resp. *bundleOutputEncoding...
-
10:11 pm Revision 1916: Evolution #1512: Depreciates the tapestry-bundle mojo
-
10:09 pm Evolution #1512 (Résolu): Depreciates the tapestry-bundle mojo
- This goal offers nothing more than the bundle one...
-
08:37 pm Evolution #1507 (Assigné): Introduce BundleFormatConverter to allow format conversion with bundle...
-
03:52 pm Revision 1915: Improve format case, MessageFormat must format all messages even there is no args
-
03:44 pm Revision 1914: useless last ;
-
01:16 pm Revision 1913: add file header
- add svn properties
-
01:15 pm Revision 1912: improve converter from String.format to MessageFormat
-
12:35 pm Revision 1911: rename eits to introduce their id + add link to its in README files
- add svn properties
add file license header -
12:32 pm Revision 1910: use mavenpom plugin version properties
05/09/2011
-
11:51 pm Revision 1909: Use plexus to expose BundlerFormatConverter as component
-
11:50 pm Revision 1908: Improve javadoc
-
08:47 pm Revision 1907: add svn:keywords
-
01:33 pm Revision 1906: Resolve issue with ' escape
05/06/2011
-
02:53 pm Anomalie #1509 (Résolu): Locale is not used during String.format
- Could be useful for dates.
-
02:51 pm Revision 1905: #1507 : Introduce BundleFormatConverter to apply conversion with bundle goal. Basi...
-
02:49 pm Revision 1904: #1499 : Add I18nFormatter interface to format message with args. I18nFormat enum p...
-
02:47 pm Evolution #1499 (Résolu): Support other format than String.format (I18nFormatter)
-
02:44 pm Evolution #1507 (Résolu): Introduce BundleFormatConverter to allow format conversion with bundle ...
- This will allow for example a conversion between String.format syntax and MessageFormat one.
An basic implementati...
05/04/2011
-
09:30 pm Revision 1903: #1505 : UTF-8 is default encoding. Only one parameter in maven plugin is sufficien...
-
09:26 pm Evolution #1505 (Résolu): I18n properties file are managed with UTF-8 encoding by default
- Before encoding was Properties default one (iso-8859-1 or us-ascii). Now the default has been set to UTF-8 to allow p...
-
05:40 pm Revision 1902: Use DEFAULT_ENCODING constant
-
02:30 pm Revision 1901: Update documentation (only french for the moment)
-
02:11 pm Evolution #1498 (Résolu): Support other encoding than default one for runtime Api
-
02:09 pm Revision 1900: #1498 : Add Charset encoding in I18nInitializer used for I18nLanguage to load prop...
05/03/2011
-
01:13 am Evolution #1499 (Résolu): Support other format than String.format (I18nFormatter)
I18n could have an *I18nFormatter* to use on each translation with args.
Default I18nFormatter will be with Stri...-
01:09 am Evolution #1498 (Résolu): Support other encoding than default one for runtime Api
- Needed if plugin encoding is not the default one (utf-8)
New parameter will be added to I18nInitializer -
01:05 am Anomalie #1494: Plugin encoding parameter is not properly managed
- r1898
-
01:03 am Anomalie #1494 (Résolu): Plugin encoding parameter is not properly managed
-
01:00 am Revision 1899: missing modules change version to 2.4-SNAPSHOT
-
12:36 am Revision 1898: #1494 : Introduce srcEncoding and outEncoding in maven plugin. Change implementati...
-
12:29 am Revision 1897: #1495 : Add methods to use specific encoding with File. The one from instance is r...
-
11:45 am Anomalie #1496 (Nouveau): ClassPathI18nInitializer not working on windows
- In our application, foolowing code is used :...
-
11:40 am Revision 1896: Wrong copied code
04/30/2011
-
05:54 pm Anomalie #1494 (Résolu): Plugin encoding parameter is not properly managed
- Even if encoding is set to UTF-8, resulting properties file will stay in default ISO-8859-1 format. With JDK1.6 it's ...
Also available in: Atom