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 - provide global option to change project encoding | ||
---|---|---|---|
Product: | projects | Reporter: | Ken Frank <kfrank> |
Component: | Generic Infrastructure | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | Keywords: | I18N |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | Sun | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Ken Frank
2008-06-17 18:17:38 UTC
Are you suggesting that the global project encoding is to be used for creation of all new projects? Sounds good, however we don't have a project category in Tools/Options right now. I'm not sure global project encoding fixes the problem though. it will only help users to identify the solution in an easier way than the current workaround you described. to answer the questions: Are you suggesting that the global project encoding is to be used for creation of all new projects? Sounds good, however we don't have a project category in Tools/Options right now. answer - yes that is the suggestion since it seems more cleaner than the current way (what I described I don't think is a workaround;its the way it needs to be done if one wanted a project without any previous files that had a different encoding and thus those previous/original files would need their encoding changed somehow once the project encoding was changed (ide does not do this nor have tools for this though there is a dev module at uc that does it, but that seems like a lot of work for user to do in this case. I'm not sure global project encoding fixes the problem though. it will only help users to identify the solution in an easier way than the current workaround you described. answer - I was not clear enough in summary or description - what I meant to say is that a user who wants a new project in an encoding other than the current global encoding value, needs to go thru the steps I mentioned. If there was an option, they would not need to go thru those steps, they would just change the option, then create a new project and it (and subsequent projects) would be in that encoding from the beginning until they changed that option again. ken.frank@sun.com Change of default owner. If you import files from elsewhere, simply set the project's encoding to the encoding of those files after you create it. If you want to retroactively change the encoding of a set of files already on disk (generally these would be versioned), you can use native2ascii + ascii2native to do so. |