This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
in this file, ergonomics/ide-ergonomics/ide-ergonomics/org/netbeans/modules/ide/ergonomics/cnd/Bundle.properties Line 90: Key "Templates/testFiles" has already appeared at line(s) 53. Non-unique keys are likely to increase translation costs due to over-translating.
Who told you to translate org/netbeans/modules/ide/ergonomics/cnd/Bundle.properties? It is a generated file, not in the sources and should not be translated.
Jaroslav, I am Jessica's manager. This file is included in the fileset that was sent to WPTG for translation. If a file is not to be translated, it must not be included in the drop that we receive for translation. This is not our error. Please fix this at your end.
How do I exclude the file from WPTG fileset?
(In reply to comment #3) > How do I exclude the file from WPTG fileset? If you confirm ergonomics/ide-ergonomics/ide-ergonomics/org/netbeans/modules/ide/ergonomics/cnd/Bundle.properties is non-translatable file, please directly move it out from wptg fileset.
Tonda told me that Masaki is the best one to know how to remove the file from the localized list. Here is the list of properties file in ide.ergonomics module that are not generated: $ cd ide.ergonomics $ find src | grep Bundle.properties src/org/netbeans/modules/ide/ergonomics/newproject/Bundle.properties src/org/netbeans/modules/ide/ergonomics/Bundle.properties src/org/netbeans/modules/ide/ergonomics/fod/Bundle.properties These has to be translated. All other files are auto generated during build.
Hi Jaroslav, I understand localized jar file is simply generated by gathering localized .properties. So for example, org/netbeans/modules/ide/ergonomics/cnd/Bundle_ja.properties is not generated automatically in localized build process. This is the reason why we're translating all .properties files in org-netbeans-modules-ide-ergonomics.jar. Let's just avoid duplicated keys here. Is it possible to avoid duplicated keys at build process? If not, I will try to exclude them at making translation drop from l10n-kit.
I see what I can do. On the other hand a single duplicated key is nothing compared to the fact that the team is translating whole file which has been already translated elsewhere.
ergonomics#ac985d00dd18