UpdateCenterPolicy

Internationalization requirements and localization policy for Netbeans Stable Auto Update Center

All of the requirements in this section must be met for modules going to the stable update center that will be translated. See next section for which modules will be translated.


The uc modules to be translated for the stable update center are those that fall into all of the below classifications:

whose code resides in NetBeans repository

and that is built as part of regular NetBeans stable update center modules that is built by and maintained by Build Engineering

that have messages and labels to be seen by user (some stable uc modules from NetBeans repository are not needed to be translated, and the providing team indicates that in their UC application)


Requirements


* I18N implementation must be complete related to: messages coming from locale specific bundle files, for encoding handling and all other i18n areas. See Additional information section below.

  • ( For modules going to the Beta Update Center, i18n implementation and testing should be complete for i18n areas like encoding handling and time and date but do not yet have to be complete for message handling.)

* I18N testing must be complete including module UI testing to make sure that messages do come from localized bundle files in localized jars. (you don't need real translated messages or jars to do this testing)

* P1/P2 i18n bugs must be fixed.

* The translatable files for the module must be in the netbeans stable uc l10n kit AND NetBeans Build Engineering needs to know that the localized nbms for this module need to be setup to be built - contact NetBeans Build Engineering for details and see the howto guidelines

The providing team for the modules whose translatable files will be in stable uc l10n kit must get the kit and verify their part of it is correct - that all needed files are there and that there are no unneeded files.


========================================================

Additional i18n implementation information


In order for the module code and UI to be i18n ready make sure that:


  • * Bundle.properties or Javahelp HTML files are the only file types that should have translatable material.



  • * Do not hard code format of time and date


  • * Handle encoding properly; take into account that users might use different encodings as well as input and use multibyte or other non ASCII characters in file names, contents and other data. Follow the NetBeansProject and FileEncoding Query api.


  • * Use ampersand (&) character to mark mnemonic key, for example: MAIN_WINDOW.MENU_FILE = &File


  • * Use NOI18N/#NOI18N keyword to mark strings in your code/bundle file that don't need localization, for example:if (protocol.equals("file")) { // NOI18N
  • mark any lines in Bundle.properties files that should not be translated with a
#NOI18N comment line before the key/value line.


==========================================================


Localization

Content published on NetBeans Auto Update Center complies with the following localization rules:

  • Currently there are 4 language versions of NetBeans Stable Auto Update Center: English, Japanese, Chinese and Portuguese




  • As mentioned in i18n section above, the uc modules to be translated are those that fall into all of the below classifications:
  • * whose code resides in NetBeans repository


  • * that are built as part of regular NetBeans stable update center modules that is built by and maintained by Build Engineering


  • * that have messages and labels to be seen by user (some stable uc modules from NetBeans repository are not needed to be translated, and the providing team indicates that in their UC application)



  • NetBeans community is welcome to help with localization of stable modules created by NetBeans community
  • If module is not localized, its English version is published on localized Auto Update Center
  • Once module gets localized, the localized version replaces the English one
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo