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 106560 - I18N - rhtml needs default meta charset tag
Summary: I18N - rhtml needs default meta charset tag
Status: RESOLVED INVALID
Alias: None
Product: ruby
Classification: Unclassified
Component: RHTML (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Torbjorn Norbye
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2007-06-13 19:26 UTC by Ken Frank
Modified: 2008-02-27 14:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Frank 2007-06-13 19:26:58 UTC 
to be consistent with files like web apps html file, jsp and xml files,
can rhtml have a default meta charset tag, with utf-8 being the charset ?

it helps users to have this and know about it.

(am assuming this kind of html file can have such a tag - if not please close issue)

PS - for other projects with the new project encoding/feq, it seems the spec is that the tag in a
jsp/html/xml file overrides what is set for project encoding, and that would apply to
design time/in editor, besides the expected behavior for runtime.
Tomas Zezula can provide more information on that.
Comment 1 Jiri Kovalsky 2007-07-03 13:58:52 UTC 
Reassigning this issue to newly created 'ruby' component.
Comment 2 Torbjorn Norbye 2007-07-12 17:03:45 UTC 
I'm not sure that's a good idea. There's another bug filed against the RHTML template which states that RHTML files are typically NOT corresponding to whole 
pages - a page is assembled from multiple rhtml files - so there should NOT be body-tags etc. in the RHTML file. 

And in looking at some big Rails projects, only one of the RHTML files (in app/views/layouts) contains a charset - none of the (hundreds of) other RHTML files 
refer to a charset.

I had planned to fix the other issue (stating that the RHTML template is "wrong") by making the template reflect exactly what the Rails code generator puts 
into an RHTML file by default - some simple text stating that this is a view file and where it can be found.

What do you think?
Comment 3 Ken Frank 2007-07-12 17:50:35 UTC 
I agree; we should  follow the same ways as other ruby/rails processes and files.

And as long as the overall project encoding and/or the encoding set in other ruby/rails project files that can set
encoding -- 
is used by the rhtml file, then the encoding handling will be taken care of.

ken.frank@sun.com
Comment 4 Ken Frank 2007-08-06 17:17:02 UTC 
if rhtml will have charset tag, it should come from the feq query, not seeded with utf-8 as I mentioned
before.

ken.frank@sun.com
Comment 5 Ken Frank 2007-10-03 18:24:12 UTC 
based on tor's comments, should this one be closed ?

ken.frank@sun.com
Comment 6 Petr Jiricka 2008-02-27 14:36:38 UTC 
Agreed - closing.