| Summary: | TVT3.1 #101 - Non externalized strings in Externalize Strings panel | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | David W Hare <dwhare> | ||||
| Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> | ||||
| Status: | CLOSED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | camle | ||||
| Version: | 3.1 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
David W Hare
Created attachment 19188 [details]
Hungarian screenshot
This string is correctly externalized. File: org.eclipse.jdt.ui/core refactoring/ org/eclipse/jdt/internal/corext/refactoring/nls/NLSMessages.properties Key: NLSRefactoring.no_strings Q: Is it OK to close such bugs or is there some other component (or owner) to investigate why the key is not translated? It appears that b/c of the 'NLS' in the filename, this was somehow removed from the script that sends to the files for translation. So it was probably never translated. Thank you It was the directory 'nls'. All files in a directory named "nls" are removed. This is fixed and these files will be sent for translation. Closing... |