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 - support multibyte in project name and path | ||
---|---|---|---|
Product: | javafx | Reporter: | Ken Frank <kfrank> |
Component: | Unsupported | Assignee: | Anton Chechel <manowar> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | kaa, masaki |
Priority: | P2 | Keywords: | I18N |
Version: | 6.x | ||
Hardware: | Sun | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Attachments: |
image
image |
Description
Ken Frank
2008-10-23 19:17:21 UTC
Created attachment 72556 [details]
image
Created attachment 72557 [details]
image
Build system > Adam Project name affects many part, it is used for folder name, build artifacts are derived from the name, many descriptors are referencing the name in various encodings and various ways of escaping, it is used in URLs as well as in MIDP. Is is a very complex task to assure correct functionality of multibytes in the whole JavaFX buildsystem. I am changing this bug to a new enhancement for the future releases. Multibyte support in project name was never supported for JavaFX projects. Adam, thanks for clarifying. I think this makes sense as enhancement since as far as I know, mbyte is ok for java itself and nb java projects, to have in project names, paths, etc. But I don't know if fx itself allows this at command line/non nb usage ie if a fx file can have non ascii in file name or path. If yes, then enhancement is ok; if not, then issue could be closed, since if fx not support it, fx plugin would not either. ken.frank@sun.com I think this issue can be closed as wontfix, I don't think using multibyte in such fields is common. But please add error messages and do not allow when user is trying to input multibytes in project name and project path on New Project and New File wizard. Ruby project is doing such checks - refer bug 99058. Cleaning bugzilla categories .... JavaFX 1.3 is no longer supported. |