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.
Is this correct component for netbeans plugin projects - if not please change to correct one. create netbeans plugin projects and then go to project browser and click on various menu items see these words not coming from localized bundle files (or even in a bundle) - what is the name of the jar file(s) associated with this functionality ? Build, Clean and Build, Run, Debug, etc on the menu of the project itself Important Files, Module Manifest, Build Script, Project Metadata, Netbeans Platform Config, Per user Netbeans Platform Config in output window like when building the project - Deleting directory, Created dir, Enabled modules, Generating info for auto update no public pkgs dialog - "It is not yet configured to export any pkgs to other modules" project properties - display display category words - Database,etc project props - libraries - add module - add module dependency popup - names of the modules - are these translatable ? also their descriptions -- where is this info supposed to come from ? project props - versioning - add new friend dialog "Friend Module to be Added ......" Since this is new module I am guessing other missing msgs/labels in explorer and elsewhere -and related to the other sub projects of this functionality - please use string checking script or other ways to make sure all msgs/labels are in bundle files and found from localized bundle ? BTW, where is info on how to create the other projects and file-> new related to this like library wrapper and others ? PS module manifest in editor does not show mbyte properly - is that a restriction of java manifest handling or can that be viewed as bug on this - I can file it separately.
Will internationalize all normal text strings. Output window messages will not be localized. Manifests accept only UTF-8 encoding. No user-visible text should ever be entered in a manifest, though it is conceivable you could have non-ASCII text in case you were adventurous enough to make e.g. a ModuleInstall subclass using a non-ASCII class or package name. If your system is set to use UTF-8 as the platform default encoding, which is always a good idea, then the editor will display such content in manifests correctly; otherwise, sorry but no.
Should be done. Other apisupport developers, please make sure you are looking for I18N violations in any new code you add before feature freeze.
verified 5.0fcs + pseudo(ja)