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.
There are some strings in Netbeans 7.2 t13y analysis, which are regarded as DNT strings by our tool. please help to confirm if they are translatable or not, if they are translatable, please change their format to initial caps. This is string is in a format that is treated as Read-Only by our tool. Please confirm that it should stay in English, or change the format to prevent this string from being read-only. It is physically impossible for us to translate it in its current format : netbeans/websvccommon/websvc-saas-ui/websvc-saas-ui/org/netbeans/modules/websvc/saas/ui/wizards/Bundle.properties LBL_Browse_1 <LBL_Browse> LBL_ProxySettings_1 <LBL_ProxySettings> LBL_WsdlSource_1 <LBL_WsdlSource> LBL_WsdlSourceFilesystem_1 <LBL_WsdlSourceFilesystem> LBL_WsdlUrl_1 <LBL_WsdlUrl>
I don't see labels with postfix "_1". Mentioned labels look good and I don't see any problem with their translation. There are just mnemonic mark "&" and word REST which should not be translated. Any other strings could be translated. Please point exact issue in the mentioned strings that is the problem for translation if any.
The label with postfix "_1" is the strings' ItemID, and the strings in "<>" without the postfix are issued strings, such as LBL_Browse and so on. These strings are picked up by our tool from the resource files and they are with underscore and in the format that is treated as Read-Only by our tool. Please confirm that it should stay in English, or change the format to prevent this string from being read-only. It is physically impossible for us to translate it in its current format.
(In reply to comment #2) > The label with postfix "_1" is the strings' ItemID, and the strings in "<>" > without the postfix are issued strings, such as LBL_Browse and so on. > > These strings are picked up by our tool from the resource files and they are > with underscore and in the format that is treated as Read-Only by our tool. > Please confirm that it should stay in English, or change the format to prevent > this string from being read-only. It is physically impossible for us to > translate it in its current format. I don't know how the tool you mentioned works. So please don't refer to the tool. It has no sense. >Please confirm that it should stay in English No , I confirm that they could be translated to other languages. >or change the format to prevent > this string from being read-only. It is physically impossible for us to > translate it in its current format. I can't do this because I don't know what is exactly the problem. Once again: please don't refer to the tool. Please point to me WHAT IS EXACTLY IS INCORRECT. I don't see any problem to translate mentioned labels: what does mean "read-only" ?
Can you help to double confirm those postfixes(_Browse,_ProxySettings,_WsdlSourceFilesystem,_WsdlUrl) need to be localized in all languages (even the ones that do not use Latin characters), for example: Give them an example: _Output it can be translated to target languages to: _Kimenet. But we have to know: 1. is there a restriction to languages with Latin characters not to use special characters like accented ones 2. what should Asian languages do, shall they also translate "output", and the same for Greek, Russian, Arabic, Hebrew 3. is there a space limit, how many characters the target can occupy 4. is it a must to connect the string with the underscore? Hyphen can be allowed or not? Thank you.
(In reply to comment #4) > Can you help to double confirm those > postfixes(_Browse,_ProxySettings,_WsdlSourceFilesystem,_WsdlUrl) need to be > localized in all languages (even the ones that do not use Latin characters), > for example: > Give them an example: > _Output > it can be translated to target languages to: > _Kimenet. > > But we have to know: > > 1. is there a restriction to languages with Latin characters not to use special > characters like accented ones > 2. what should Asian languages do, shall they also translate "output", and the > same for Greek, Russian, Arabic, Hebrew > 3. is there a space limit, how many characters the target can occupy > 4. is it a must to connect the string with the underscore? Hyphen can be > allowed or not? > Thank you. Do you care about translation of "LBL_Browse" , "LBL_WsdlUrl" , ... strings as is ? These strings are keys. They shouldn't be translated. I didn't understand your question before because I thought you asking about their values. Once again : all mentioned string are KEYS. They are identifiers. That's the essence of property file : some_key=some_value. some_key is identifier and shouldn't be localized. some_value is string that should be localized.
(In reply to comment #5) > (In reply to comment #4) > > Can you help to double confirm those > > postfixes(_Browse,_ProxySettings,_WsdlSourceFilesystem,_WsdlUrl) need to be > > localized in all languages (even the ones that do not use Latin characters), > > for example: > > Give them an example: > > _Output > > it can be translated to target languages to: > > _Kimenet. > > > > But we have to know: > > > > 1. is there a restriction to languages with Latin characters not to use special > > characters like accented ones > > 2. what should Asian languages do, shall they also translate "output", and the > > same for Greek, Russian, Arabic, Hebrew > > 3. is there a space limit, how many characters the target can occupy > > 4. is it a must to connect the string with the underscore? Hyphen can be > > allowed or not? > > Thank you. > Do you care about translation of "LBL_Browse" , "LBL_WsdlUrl" , ... > strings as is ? > These strings are keys. They shouldn't be translated. I didn't understand your > question before because I thought you asking about their values. > Once again : all mentioned string are KEYS. They are identifiers. > That's the essence of property file : some_key=some_value. > some_key is identifier and shouldn't be localized. > some_value is string that should be localized. Yes, I am caring about these five strings' translation. LBL_Browse LBL_ProxySettings LBL_WsdlSource LBL_WsdlSourceFilesystem LBL_WsdlUrl Now that they are not translatable, the bug can be closed, because our tool will mark them as Read-only strings.(Read-only means they cannot be translated by our tool.)