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.

Bug 139484 - I18N - no encoding value in project properties of grails project
Summary: I18N - no encoding value in project properties of grails project
Status: NEW
Alias: None
Product: groovy
Classification: Unclassified
Component: Grails (show other bugs)
Version: 6.x
Hardware: Sun All
: P2 blocker (vote)
Assignee: martin_adamek
Keywords: I18N, RELNOTE
: 148739 161219 (view as bug list)
Depends on:
Reported: 2008-07-09 20:37 UTC by Ken Frank
Modified: 2011-12-30 18:13 UTC (History)
2 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Ken Frank 2008-07-09 20:37:28 UTC
most nb project types have a project encoding value and the feq api is implemented;
I don't see such a value in grails project properties (rails projects do have one).

Also, if feq for grails or related groovy classes/scripts need implementing
besides about project encoding property, can that be done ?
Comment 1 martin_adamek 2008-07-30 12:23:38 UTC
In Grails projects there is hardcoded UTF-8 encoding always returned from FEQ. Is that ok, or do we really need project properties for that?
Comment 2 Ken Frank 2008-07-30 16:17:53 UTC

I thought feq is supposed to return current view of project encoding, not hardcoded
to utf-8 only - or is this hardcoding what grails project does ?

if so, I think, like for other projects, including rails project, it needs
to use feq that returns current view of project encoding, which might not be utf8.

Comment 3 Ken Frank 2008-09-29 18:56:43 UTC
to clarify, IMO this needs to be fixed both to
provide project properties encoding value
and also to follow feq in general,
just as is done for other nb project types.
Comment 4 martin_adamek 2008-09-30 15:11:35 UTC
UTF-8 is default for Grails. It can be tweaked for specific files in Config.groovy, but that's out of scope for 6.5 and default is recommended by Grails 
developers anyway. Changing to enhancement, would be nice to have read/write model + UI for Config.groovy.
Comment 5 martin_adamek 2008-09-30 15:13:46 UTC
*** Issue 148739 has been marked as a duplicate of this issue. ***
Comment 6 Ken Frank 2008-09-30 16:57:25 UTC

should we have some rel note or faq for users to emphasize about it and 
to tell them that any files in another encoding need to be changed
to utf-8 encoding ?

the good news for this is that default project encoding for nb is utf-8
and that grails project feq is hardcoded to utf-8 but users who run
in another locale for which utf-8 is not default encoding might
need to change some files (this is true for windows since it does not
have a regional setting in which utf-8 is the default encoding)
Comment 7 martin_adamek 2008-10-02 09:36:11 UTC
Yes, that's probably a good idea.
Comment 8 Ken Frank 2008-10-02 15:55:58 UTC
added relnote keyword based on Martin's comment.
Comment 9 Martin Janicek 2011-12-30 18:13:17 UTC
*** Bug 161219 has been marked as a duplicate of this bug. ***