Closed Bug 280656 Opened 20 years ago Closed 20 years ago

Remove UTF-8 BOMs from source files

Categories

(SeaMonkey :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: smontagu, Assigned: smontagu)

Details

Attachments

(1 file)

UTF-8 BOMs (EF BB BF) at the beginning of source files are not good. Among other
problems they prevent LXR from indexing files. Example:
http://lxr.mozilla.org/seamonkey/find?string=bug41262 finds all files from
bug41262-1.html to bug41262-6.html, except for bug41262-2.html.
Attached patch Remove the BOMsSplinter Review
Attachment #173077 - Flags: superreview?(brendan)
Attachment #173077 - Flags: review?(jshin1987)
Comment on attachment 173077 [details] [diff] [review]
Remove the BOMs

r=jshin
Perhaps, we have to document very clearly that UTF-8 BOM is not welcome in the
tree. (Windows users are prone to commit this mistake.)  In addition, an
automatic 'sanitizer' would be handy (how? hacking cvs server running at
cvs.mozilla.org or ...)
Attachment #173077 - Flags: review?(jshin1987) → review+
Comment on attachment 173077 [details] [diff] [review]
Remove the BOMs

rs=me on any such future changes.

/be
Attachment #173077 - Flags: superreview?(brendan) → superreview+
Thanks for reviews, fix checked in.

(In reply to comment #2)
> Perhaps, we have to document very clearly that UTF-8 BOM is not welcome in the
> tree. (Windows users are prone to commit this mistake.)

We should certainly something like "don't save source files as UTF-8 from
Windows Notepad" to the docs at http://www.mozilla.org/hacking/

Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
For those who may come to this bug in the future: bug 280789 was filed for the
documentation. 
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: