[JBoss JIRA] Created: (JBIDE-2972) Move translatable .properties files from src/ into resources/text/
2:29 a.m.
Move translatable .properties files from src/ into resources/text/
------------------------------------------------------------------
Key: JBIDE-2972
URL: https://jira.jboss.org/jira/browse/JBIDE-2972
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup
Reporter: Sean Flanigan
See http://lists.jboss.org/pipermail/jbosstools-dev/2008-October/002268.html for
background, particularly item number 4. If all translatable resources are kept in
standard locations, the localization build can be simplified and more reliable.
In JBoss Tools, I have identified translatable .properties in the
following directories under various ${plugin} dirs:
src/main
src
jbosscore
jbossui
templates
template-src
One example is the file
/org.jboss.ide.eclipse.archives.core/src/main/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
but there are similar files in every project.
Rather than create a similar jira for each and every project, I'd be happy to do the
work myself, with a little help (I haven't done much work with Eclipse plugins):
Could someone please confirm what needs be changed to move this file into
/org.jboss.ide.eclipse.archives.core/resources/text/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
and still be available on the classpath for Eclipse and PDE Build and anywhere else
important.
At the moment, I can think of these changes:
1. add another classpathentry in Eclipse's .classpath (through Eclipse's Java
Build Path screen)
2. edit sources.archivescore.jar in build.properties (through Eclipse's Build
Configuration editor)
Is that all that is needed?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:46 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2972) Move translatable .properties files from src/ into resources/text/
[
https://jira.jboss.org/jira/browse/JBIDE-2972?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-2972:
---------------------------------------
Fix Version/s: 3.0.0.cr1
3.0.0.GA
hmm - that might work; would also be a good way of explicit stating which resources that
actually needs/want translation.
The files that I could definitly see this done for are the Eclipse resource properties;
i.e. those who have a .properties and .java pair.
i.e. Messages.java/Messages.properties.
Where it gets harder is for the root properties files which is used by the
plugin.xml/feature.xml parts.
But they are always named plugin.properties so that might just be another standard
name....
Following that thought wouldn't it be just as simple for you to say that the default
translations you need is
/plugin.properties and **/Messages.properties ?
That still won't cover the templates/xmodel which is a different beast.
I would think getting the Eclipse resource bundle file/class called the same (and only
have one per plugin) would be a better first step?
Move translatable .properties files from src/ into resources/text/
------------------------------------------------------------------
Key: JBIDE-2972
URL: https://jira.jboss.org/jira/browse/JBIDE-2972
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup
Reporter: Sean Flanigan
Fix For: 3.0.0.cr1, 3.0.0.GA
See http://lists.jboss.org/pipermail/jbosstools-dev/2008-October/002268.html for
background, particularly item number 4. If all translatable resources are kept in
standard locations, the localization build can be simplified and more reliable.
In JBoss Tools, I have identified translatable .properties in the
following directories under various ${plugin} dirs:
src/main
src
jbosscore
jbossui
templates
template-src
One example is the file
/org.jboss.ide.eclipse.archives.core/src/main/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
but there are similar files in every project.
Rather than create a similar jira for each and every project, I'd be happy to do the
work myself, with a little help (I haven't done much work with Eclipse plugins):
Could someone please confirm what needs be changed to move this file into
/org.jboss.ide.eclipse.archives.core/resources/text/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
and still be available on the classpath for Eclipse and PDE Build and anywhere else
important.
At the moment, I can think of these changes:
1. add another classpathentry in Eclipse's .classpath (through Eclipse's Java
Build Path screen)
2. edit sources.archivescore.jar in build.properties (through Eclipse's Build
Configuration editor)
Is that all that is needed?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:37 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2972) Move translatable .properties files from src/ into resources/text/
[
https://jira.jboss.org/jira/browse/JBIDE-2972?page=com.atlassian.jira.plu...
]
Sean Flanigan commented on JBIDE-2972:
--------------------------------------
Yes, apparently I need to include $plugin/plugin.properties and perhaps
$feature/feature.properties, probably by their exact names. That's fine.
(Ignoring xmodel too...)
As for the runtime classpath .properties files (*Messages.properties,
ArchivesCoreMessages.properties, etc), I'm fine with renaming them all to
Messages.properties. I just thought it would be easier to move them to new directories,
but keep the same names. No code change that way.
But I don't mind either way. Just so long as it's easy to write an ant filespec
which picks up the translatable .properties files, and nothing else.
Move translatable .properties files from src/ into resources/text/
------------------------------------------------------------------
Key: JBIDE-2972
URL: https://jira.jboss.org/jira/browse/JBIDE-2972
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup
Reporter: Sean Flanigan
Fix For: 3.0.0.cr1, 3.0.0.GA
See http://lists.jboss.org/pipermail/jbosstools-dev/2008-October/002268.html for
background, particularly item number 4. If all translatable resources are kept in
standard locations, the localization build can be simplified and more reliable.
In JBoss Tools, I have identified translatable .properties in the
following directories under various ${plugin} dirs:
src/main
src
jbosscore
jbossui
templates
template-src
One example is the file
/org.jboss.ide.eclipse.archives.core/src/main/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
but there are similar files in every project.
Rather than create a similar jira for each and every project, I'd be happy to do the
work myself, with a little help (I haven't done much work with Eclipse plugins):
Could someone please confirm what needs be changed to move this file into
/org.jboss.ide.eclipse.archives.core/resources/text/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
and still be available on the classpath for Eclipse and PDE Build and anywhere else
important.
At the moment, I can think of these changes:
1. add another classpathentry in Eclipse's .classpath (through Eclipse's Java
Build Path screen)
2. edit sources.archivescore.jar in build.properties (through Eclipse's Build
Configuration editor)
Is that all that is needed?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:16 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2972) Move translatable .properties files from src/ into resources/text/
[
https://jira.jboss.org/jira/browse/JBIDE-2972?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-2972:
--------------------------------------------
Sean - is this still relevant to fix or are you all clear ?
Move translatable .properties files from src/ into resources/text/
------------------------------------------------------------------
Key: JBIDE-2972
URL: https://jira.jboss.org/jira/browse/JBIDE-2972
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup
Reporter: Sean Flanigan
Fix For: 3.0.0.CR2
See http://lists.jboss.org/pipermail/jbosstools-dev/2008-October/002268.html for
background, particularly item number 4. If all translatable resources are kept in
standard locations, the localization build can be simplified and more reliable.
In JBoss Tools, I have identified translatable .properties in the
following directories under various ${plugin} dirs:
src/main
src
jbosscore
jbossui
templates
template-src
One example is the file
/org.jboss.ide.eclipse.archives.core/src/main/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
but there are similar files in every project.
Rather than create a similar jira for each and every project, I'd be happy to do the
work myself, with a little help (I haven't done much work with Eclipse plugins):
Could someone please confirm what needs be changed to move this file into
/org.jboss.ide.eclipse.archives.core/resources/text/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
and still be available on the classpath for Eclipse and PDE Build and anywhere else
important.
At the moment, I can think of these changes:
1. add another classpathentry in Eclipse's .classpath (through Eclipse's Java
Build Path screen)
2. edit sources.archivescore.jar in build.properties (through Eclipse's Build
Configuration editor)
Is that all that is needed?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:08 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2972) Move translatable .properties files from src/ into resources/text/
[
https://jira.jboss.org/jira/browse/JBIDE-2972?page=com.atlassian.jira.plu...
]
Sean Flanigan commented on JBIDE-2972:
--------------------------------------
It's still relevant, but I have a workaround. This file contains the wildcards I have
defined to pick up .properties files:
http://anonsvn.jboss.org/repos/jbosstools/trunk/i18n/prop2potincludes.txt (reproduced
here):
*/plugins/*/plugin.properties
*/plugins/*/src/**/*.properties
*/plugins/*/jbosscore/**/*.properties
*/plugins/*/jbossui/**/*.properties
*/plugins/*/resources/**/*.properties
*/plugins/*/template-src/**/*.properties
Naturally, I would prefer the list was shorter, and not so ad hoc. (But plugin.properties
is fine, by the way.) I'm just concerned about the hodge-podge of
*Messages.properties files, under src/, jbosscore/, resources/, etc.
Also, I haven't got any feedback from the translators yet, but I suspect some of the
included properties files may contain not translatable text but configuration values. So
it would still be better if we could keep them in separate directories so that I can
easily exclude config files.
Move translatable .properties files from src/ into resources/text/
------------------------------------------------------------------
Key: JBIDE-2972
URL: https://jira.jboss.org/jira/browse/JBIDE-2972
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup
Reporter: Sean Flanigan
Fix For: 3.0.0.CR2
See http://lists.jboss.org/pipermail/jbosstools-dev/2008-October/002268.html for
background, particularly item number 4. If all translatable resources are kept in
standard locations, the localization build can be simplified and more reliable.
In JBoss Tools, I have identified translatable .properties in the
following directories under various ${plugin} dirs:
src/main
src
jbosscore
jbossui
templates
template-src
One example is the file
/org.jboss.ide.eclipse.archives.core/src/main/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
but there are similar files in every project.
Rather than create a similar jira for each and every project, I'd be happy to do the
work myself, with a little help (I haven't done much work with Eclipse plugins):
Could someone please confirm what needs be changed to move this file into
/org.jboss.ide.eclipse.archives.core/resources/text/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
and still be available on the classpath for Eclipse and PDE Build and anywhere else
important.
At the moment, I can think of these changes:
1. add another classpathentry in Eclipse's .classpath (through Eclipse's Java
Build Path screen)
2. edit sources.archivescore.jar in build.properties (through Eclipse's Build
Configuration editor)
Is that all that is needed?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:23 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-2972) Move translatable .properties files from src/ into resources/text/
[
https://jira.jboss.org/jira/browse/JBIDE-2972?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-2972:
---------------------------------------
Fix Version/s: 3.0.0.GA
(was: 3.0.0.CR2)
Move translatable .properties files from src/ into resources/text/
------------------------------------------------------------------
Key: JBIDE-2972
URL: https://jira.jboss.org/jira/browse/JBIDE-2972
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup
Reporter: Sean Flanigan
Fix For: 3.0.0.GA
See http://lists.jboss.org/pipermail/jbosstools-dev/2008-October/002268.html for
background, particularly item number 4. If all translatable resources are kept in
standard locations, the localization build can be simplified and more reliable.
In JBoss Tools, I have identified translatable .properties in the
following directories under various ${plugin} dirs:
src/main
src
jbosscore
jbossui
templates
template-src
One example is the file
/org.jboss.ide.eclipse.archives.core/src/main/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
but there are similar files in every project.
Rather than create a similar jira for each and every project, I'd be happy to do the
work myself, with a little help (I haven't done much work with Eclipse plugins):
Could someone please confirm what needs be changed to move this file into
/org.jboss.ide.eclipse.archives.core/resources/text/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
and still be available on the classpath for Eclipse and PDE Build and anywhere else
important.
At the moment, I can think of these changes:
1. add another classpathentry in Eclipse's .classpath (through Eclipse's Java
Build Path screen)
2. edit sources.archivescore.jar in build.properties (through Eclipse's Build
Configuration editor)
Is that all that is needed?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:54 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-2972) Move translatable .properties files from src/ into resources/text/
[
https://jira.jboss.org/jira/browse/JBIDE-2972?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen resolved JBIDE-2972.
----------------------------------------
Resolution: Rejected
as far as I understood the last mail about i18n we won't need nor want to do this.
reopen if i misunderstood.
Move translatable .properties files from src/ into resources/text/
------------------------------------------------------------------
Key: JBIDE-2972
URL: https://jira.jboss.org/jira/browse/JBIDE-2972
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup
Reporter: Sean Flanigan
Fix For: 3.0.0.GA
See http://lists.jboss.org/pipermail/jbosstools-dev/2008-October/002268.html for
background, particularly item number 4. If all translatable resources are kept in
standard locations, the localization build can be simplified and more reliable.
In JBoss Tools, I have identified translatable .properties in the
following directories under various ${plugin} dirs:
src/main
src
jbosscore
jbossui
templates
template-src
One example is the file
/org.jboss.ide.eclipse.archives.core/src/main/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
but there are similar files in every project.
Rather than create a similar jira for each and every project, I'd be happy to do the
work myself, with a little help (I haven't done much work with Eclipse plugins):
Could someone please confirm what needs be changed to move this file into
/org.jboss.ide.eclipse.archives.core/resources/text/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
and still be available on the classpath for Eclipse and PDE Build and anywhere else
important.
At the moment, I can think of these changes:
1. add another classpathentry in Eclipse's .classpath (through Eclipse's Java
Build Path screen)
2. edit sources.archivescore.jar in build.properties (through Eclipse's Build
Configuration editor)
Is that all that is needed?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:33 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-2972) Move translatable .properties files from src/ into resources/text/
[
https://jira.jboss.org/jira/browse/JBIDE-2972?page=com.atlassian.jira.plu...
]
Sean Flanigan commented on JBIDE-2972:
--------------------------------------
My recent mailing list messages were about simplifying the build by avoiding the need for
langpack generation, and eliminating filetype conversions from the build. There will
still be a need to convert .properties <-> .po, but it will become the problem of
the L10n/i18n teams/projects. So the problem does still exist.
To avoid overwhelming translators with garbage, it's still very important to
distinguish configuration-type .properties files from translatable .properties files. We
can (a) keep them in separate directories (and design our wildcards to pick up just the
translatables), or (b) mark .properties files with NON-TRANSLATABLE comments. See
http://wiki.eclipse.org/Eclipse_Globalization_Guidelines#Non-translatable...
. The Ant-Gettext converters know how to skip NON-TRANSLATABLE messages/files.
However, the number of non-translatable .properties is probably small, so I think the best
solution is (b). That way we don't have to change any sourcepaths or buildfiles, we
just have to add comments to a small number of files. If the number of non-translatable
.properties turns out to be too big, or adding the NON-TRANSLATABLE comments becomes
impractical/undesirable, we might want to revisit this.
Move translatable .properties files from src/ into resources/text/
------------------------------------------------------------------
Key: JBIDE-2972
URL: https://jira.jboss.org/jira/browse/JBIDE-2972
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup
Reporter: Sean Flanigan
Fix For: 3.0.0.GA
See http://lists.jboss.org/pipermail/jbosstools-dev/2008-October/002268.html for
background, particularly item number 4. If all translatable resources are kept in
standard locations, the localization build can be simplified and more reliable.
In JBoss Tools, I have identified translatable .properties in the
following directories under various ${plugin} dirs:
src/main
src
jbosscore
jbossui
templates
template-src
One example is the file
/org.jboss.ide.eclipse.archives.core/src/main/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
but there are similar files in every project.
Rather than create a similar jira for each and every project, I'd be happy to do the
work myself, with a little help (I haven't done much work with Eclipse plugins):
Could someone please confirm what needs be changed to move this file into
/org.jboss.ide.eclipse.archives.core/resources/text/org/jboss/ide/eclipse/archives/core/ArchivesCoreMessages.properties
and still be available on the classpath for Eclipse and PDE Build and anywhere else
important.
At the moment, I can think of these changes:
1. add another classpathentry in Eclipse's .classpath (through Eclipse's Java
Build Path screen)
2. edit sources.archivescore.jar in build.properties (through Eclipse's Build
Configuration editor)
Is that all that is needed?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6247
days inactive
6374
days old
jbosstools-issues@lists.jboss.org
7 comments
2 participants
participants (2)
-
Max Rydahl Andersen (JIRA) -
Sean Flanigan (JIRA)