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 ?
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?
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.
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.
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.
*** Issue 148739 has been marked as a duplicate of this issue. ***
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)
Yes, that's probably a good idea.
added relnote keyword based on Martin's comment.
*** Bug 161219 has been marked as a duplicate of this bug. ***