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 - Encoding handling | ||
---|---|---|---|
Product: | web | Reporter: | _ pkuzel <pkuzel> |
Component: | HTML Editor | Assignee: | _ rkubacki <rkubacki> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | Keywords: | I18N |
Priority: | P4 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | 18651 | ||
Bug Blocks: |
Description
_ pkuzel
2001-12-13 10:45:49 UTC
Does it make sense to parse HTML in order to get your encoding? I would say that it is an advanced feature and there is not big demand for it. Ask your question Japanese users. This is typical I18N issue. Set target milestone to TBDo Consistent use of the I18N keyword. Should be implemented by Jarda Tulach some time ago. |