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.
Summary: | I18N - pasting multibyte into diagram does not show correct multibyte | ||
---|---|---|---|
Product: | uml | Reporter: | Ken Frank <kfrank> |
Component: | General Diagram | Assignee: | issues@uml <issues> |
Status: | NEW --- | ||
Severity: | blocker | CC: | sunlit, tspiva |
Priority: | P2 | Keywords: | I18N |
Version: | 5.x | ||
Hardware: | Sun | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Attachments: |
image
image |
Description
Ken Frank
2006-06-19 22:20:03 UTC
Created attachment 31178 [details]
image
Created attachment 31180 [details]
image
This seems like a very important kind of functionality - to be able to use these areas of diagram to add or change names of or attributes or operations - a basic functionality - that is, if this happened in english locale, wouldn't it be fixed for entpack for sure ? if so, why not for users who input multibyte ? ken.frank@sun.com Targeted in the drawing area redesign. REstoring the original priority and using the NB 6.0 waiver process. Diagram area bugs waived for 6.0 will also be waived for 6.1. I'm able to paste multibyte chinese characters properly in NB 6.5 builds. I'm on Windows Vista though. I18N support is targeted for 6.5M2. From peters comments, does this mean that the issue is can no longer be reproduced? development team , please confirm via unit testing first that it works ok now, then resolve it if so, then it will undergo verification as usual. ken.frank@sun.com What are the unit test that you want run? as to unit test, I'm don't know details of what each team does in this regard, what I meant was to do whatever developers do when an issue has been fixed or investigated that its not an issue anymore due to some new coding or implementation; then issues are put in resolved state if ok, then qe can verify. from my experience working with other uml developers and issues, this has happened in past about other issues. ken.frank@sun.com as to unit test, I'm don't know details of what each team does in this regard, what I meant was to do whatever developers do when an issue has been fixed or investigated that its not an issue anymore due to some new coding or implementation; then issues are put in resolved state if ok, then qe can verify. from my experience working with other uml developers and issues, this has happened in past about other issues. ken.frank@sun.com |