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 - rhtml needs default meta charset tag | ||
---|---|---|---|
Product: | ruby | Reporter: | Ken Frank <kfrank> |
Component: | RHTML | Assignee: | Torbjorn Norbye <tor> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | jf4jbug, pjiricka |
Priority: | P3 | Keywords: | I18N |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Ken Frank
2007-06-13 19:26:58 UTC
Reassigning this issue to newly created 'ruby' component. 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? 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 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 based on tor's comments, should this one be closed ? ken.frank@sun.com Agreed - closing. |