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 67340 - [50cat] I18N - encoding directives are ignored for CSS files
Summary: [50cat] I18N - encoding directives are ignored for CSS files
Status: NEW
Alias: None
Product: web
Classification: Unclassified
Component: CSS Visual Tools (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Jan Stola
Keywords: I18N
: 67341 (view as bug list)
Depends on:
Blocks: 67341 97848
  Show dependency tree
Reported: 2005-10-22 10:07 UTC by vbrabant
Modified: 2014-10-06 13:27 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 vbrabant 2005-10-22 10:07:12 UTC
[ BUILD # : 200510131922 ]
[ JDK VERSION : 1.5.0_05 ]

When I edit a CSS file, his encoding directive is ignored.

The first line of a CSS file can contain the following directive:

@charset "iso-8859-1";

But I see no difference when I am saving a CSS file that use iso-8859-1 or utf-8 encoding.

I will also create another issue for DIFF module !!!
Comment 1 Martin Roskanin 2005-11-08 14:43:46 UTC
similarly as issue #67341 this is xml/css issue
Comment 2 Marek Fukala 2005-11-14 13:34:13 UTC
I will try to implement an CSS encoding parser in the next release.
Comment 3 Marek Fukala 2007-07-11 12:48:18 UTC
Making this issue as defect and closing issue #67341 which is in fact a duplicate.
Comment 4 Marek Fukala 2007-07-11 12:48:30 UTC
*** Issue 67341 has been marked as a duplicate of this issue. ***
Comment 5 Ken Frank 2007-07-11 15:06:54 UTC
since we now have project encoding property and also some encoding handling
for some file types, should this happen for css files ?
If so I can file a separate issue.  (since I think this one is about encoding directives not being
used by ide when saving the file)

For example, jsp and html files encoding directives will be seeded with that of the global
project encoding when created or else that of the fallback locale (encoding of the locale user is
in).  (there is similar issue for xml files).

for existing css files or if encoding of the file is changed by user, I need to get clear on what the
new spec is related to feq on these as to assumption of encoding of such files and will add to the issue.

--> let me  know if separate issue should be created.
Comment 6 Marek Fukala 2007-07-11 15:25:34 UTC
I consider this issue to be about the same problems which you reported to html and jsp, so we at least need:

1) take into account the @charset in the document when loading/saving the file in editor, if there isn't any use FEQ to
get the encoding.

2) put proper @charset when creating from template

Comment 7 Marek Fukala 2007-10-12 18:08:48 UTC
This never worked, marking as enhancement.