@FakeUnicode I know, but where is it discouraged in the *standard* itself? +@ericlaw @filedescriptor
-
-
Replying to @mathias
@mathias@FakeUnicode@filedescriptor It isn't. But it's also fair to say that the UTF8 BOM is uncommon in web responses.2 replies 0 retweets 0 likes -
Replying to @ericlaw
@ericlaw@mathias@filedescriptor Per 8.0 specs, the "common/important" uses are themselves disappearing slowly.pic.twitter.com/jfUsQZ9NB4
1 reply 0 retweets 0 likes -
Replying to @FakeUnicode
@ericlaw@mathias@filedescriptor Which is easy to interpret as "This is a dirty hack. Why use it if you don't need to?"1 reply 0 retweets 0 likes -
Replying to @FakeUnicode
@FakeUnicode I dislike BOM as much as the next guy but saying the standard “discourages” it seems incorrect IMHO +@ericlaw@filedescriptor2 replies 0 retweets 0 likes -
Replying to @mathias
@mathias@FakeUnicode@ericlaw Unicode 5.0.0 ch2.6 Encoding Schemes: [..] Use of a BOM is neither required nor recommended for UTF-82 replies 0 retweets 1 like -
Replying to @filedescriptor
@filedescriptor Not recommended is different from “discouraged” or “recommended against”. +@FakeUnicode@ericlaw1 reply 0 retweets 0 likes -
Replying to @mathias
@mathias@FakeUnicode@ericlaw I think you are right - the wordings are not very precise on my side and happy to make changes :)1 reply 0 retweets 0 likes -
Replying to @filedescriptor
@filedescriptor How about just “BOM is not really an issue since it is rarely used” instead? +@FakeUnicode@ericlaw1 reply 0 retweets 0 likes -
@filedescriptor xoxo @0x6D6172696F & @mathias #ruhrsecpic.twitter.com/9h9h9U9aZP
-
-
Replying to @filedescriptor
@filedescriptor@mathias @0x6D6172696F Time for expose ? ;)0 replies 0 retweets 0 likes
End of conversation
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.
