|
|
Unix command files, UTF-8, and the byte order mark
I didn't even get but a few sentences into this hint before I realized what the outcome would be. I've found, as others have here, that UTF-8 with BOM is just asking for trouble. I think BareBones should remove that option from BBEdit and TextWrangler! The no-BOM option seems to work great, and is well read across many apps that accept UTF-8.
Unix command files, UTF-8, and the byte order mark
Err, no. Don't eliminate useful features. Barebones just needs to extend that features, so that if you save an HTML file, it uses the fancy encoding. But if you save a shell script, it saves it in a format appropriate to that filetype.
Unix command files, UTF-8, and the byte order mark
Or if you open a HTML file with no BOM, it could scan for the <meta> header specifying the encoding. Likewise, if it opens XML, it could interpret the encoding attribute. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.10 seconds |
|