[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2972) Move translatable .properties files from src/ into resources/text/

[Sean Flanigan (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12454596#action_12454596 ] 

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_Message_Strings .  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