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.
this applies to javascript, groovy, php also since also have ct_ keys in some bundle files. most lines are obvious - should not be translated, since code snippets or other things but some lines it might not be clear - thus for each bundle file in ruby, php, javascript, groovy that have ct_ sections, could a #NOI18N comment be placed telling not to translate that section ? (and is there some alias or way to reach those developers without needing separate issue in those other areas ?)
I can't speak for Groovy and PHP, but for Ruby and JavaScript there ct_ entries refer to Code Templates, these are the display names, and should therefore be translated if appropriate. However, they often refer to code snippets by including part of the code snippet and you probably don't want to translate it - though in some cases you may want to. For example: ct_forv=for (var v in o) { } The above isn't valid code - it's "pseudocode" showing that this code template will insert a for block with a variable v and then a codeblock { }. Perhaps there are better ways to translate this using more local words in other languages. Certainly if the descriptions aren't going to be localized, we might as well remove them from the bundle lookup and just hardcode the strings into the codetemplates.xml file, where the code snippet is already hardcoded. (These display names are shown in code completion for example, when the prefix in the editor matches the prefix of the code template contents (not name). I'm not sure how to resolve this issue - mark it as fixed, or not a bug, or if something else is necessary. Again, the intent was that these entries could be localized.
Moving from ruby/GSF to editor/CSL. Step one: assign to myself ;-)
Step 2: trying to make the owner not myself but the owner of the subcomponent.
Looks like we're going to keep the status quo.