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.
Product Version: NetBeans IDE Dev (Build 200808240201) Java: 1.6.0_06; Java HotSpot(TM) Client VM 10.0-b22 I'm running in Japanese locale, using a pseudo localized Netbeans with font size 16 option. 1. Create Java App 2. Create JUnit test using wizard 3. Test the app JUnit test results window contains a message not from pseudo localized bundle file: No Runnable methods. See image.
Created attachment 68550 [details] image
Don't think it's P2 and actually this message is a part of exception I guess. Marian, Am I right ?
Yes, it is a message from the exception. It comes from the JUnit library (http://www.junit.org/), which is used for running JUnit tests. The JUnit library is not internationalized so all messages coming from it are in English.
we don't know where the message is from; we file in good faith that its from nb and as such a p2; but if its not from nb, wouldn't you just close it rather than state its a p3 ? like any issue filed in good faith that is not really an issue, the issue is evaluated and closed if not an issue. We accept the evaluations for sure in these cases. (unless you are saying that even if its not from nb, you want to have it be translatable and capture it and have a wrapper module or something that would allow it to be translated as part of nb translation - then can understand that it could be p3) but otherwise, if its not from nb, wouldn't you just close it vs comment about p2 or p3 ??? ken.frank@sun.com
Is it possible to enable i18n support there?
What do you mean by "to enable i18n support there"? Do you mean "to make the JUnit library internationalized"? If so, then the answer is: Yes, it can be internationalized. Just that it is up to developers of the library to make the job. Maybe you meant "to internationalize the messages coming from the library in NetBeans IDE": If so, then the answer is: Yes, it is doable, too. Just that it would make the NetBeans code more complex and still it would not be 100% reliable - reliability of the internationalization would depend on the source code of the JUnit library.
andrey, just to clarify a bit more - I think Marian is correct, that it could be done but it could be complex and since junit itself is not translated. In other such issues, developers have evaluated if the messages in question would be important to have translatable by nb translations - if not then issue is just closed as wontfix and we accept that. in other cases developers have said, yes, we want to have these msgs translatable and they create wrapper modules and intercept the messages from non nb jars or some other process - so that nb own bundle files can have such messages. from overall view of translation one could say that the more translatable the better, but in practice due to various non nb modules not being translated, then it means that those msgs will just be in english, unless nb dev evaluation decides that they should be translated and will implement special process, and then they leave issue open for future release implementation. another way to look at this might be to request junit providers to have the messages translated - for some ext modules in ide, they are translated for some locales and some are not - and request/issue could be filed with junit about it. ken.frank@sun.com
I do not think that translating messages coming from the JUnit library is so important that it would require additional translation on the IDE side - marking as WONTFIX. Feel free to reopen this issue if you do not agree.
I meant "to make the JUnit library internationalized". Thanks for the clarification. I agree with WONTFIX resolution.