Hi Elias,
I talked about the exact same topic today with Frank Schepp. We thought of rule like this:
- have only one file (messages.properties) per bundle / project
- put it in a package named<bundle-id>.nls
So org.eclipse.riena.core would have a package org.eclipse.riena.core.nls with a messages.properties with all text entries for that bundle.
Does that sound like a good idea to everyone ?
christian
Am 04.03.2010 um 19:03 schrieb Elias Volanakis:
Here's something I would like to discuss:
What is the best location for messages.properties / Messages.java
files. The options could be:
- having a dedicated messages.properties per package
- or having a dedicated messages.properties per bundle (ideally with
some naming scheme)
The reason for mentioning this is that moving the .properties file to
another package breaks existing translation fragments. From the POV of
somebody who has an existing translation the location of that file (as
well as the key names that are already in it) should be considered
API.
Looking forward to your input,
Elias.
--
Elias Volanakis | Technical Lead | http://eclipsesource.com
elias@xxxxxxxxxxxxxxxxx | +1 503 929 5537 | @evolanakis
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: 069 / 27 22 18 0
fax: 069 / 27 22 18 22
web: www.compeople.de
Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
Ust-Ident.-Nr: DE207665352
-------------------------------------------------------------
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
