Community
Participate
Eclipse IDE
Our usage of the templates extension point specifies include files and their translatable properties - we should use $nl$ in the path to the properties file in order to enable translations.
fyi, i just opened bug 103345 which points out using $nl$ does not work for .properties files.
This has been marked as must fix for translation sign off. Translated JDT templates cannot be displayed. Please change severity to major and add "TVT 3.1 - TCT 478" to the summary. Thanks.
I've already fixed in the R3_1_maintenance branch and it will be in the next M-build. IMPORTANT NOTE TO THE TRANSLATORS: the translation files are not treated as resource bundles and hence the file name has to be left as (at least until bug 103345 has been fixed) is i.e. do not add the locale to the name. The translated files must be in the 'nl' directory i.e. if a <plugin> defines a template translations file in its plugin.xml like: ... translations=$nl$/<plugin-relative path to file> ... then the translations must go into: <plugin's nl fragment>\nl\<locale>\templates\<plugin-relative path to file>
start verifying...
Verified in M20050831-1200 + ZRH plugins from R3_1_maintenance that file /nl/geek/templates/default-templates.properties is picked up in a fragment with the "geek" locale. Added "TVT 3.1 - TCT 478" to summary as requested in comment 2.