Hi Ian,
ropers wrote on Sun, Jul 01, 2012 at 05:23:07PM +0200:
(Not sure who of you best to talk to;
Regarding conference presentations, the author.
All conference presentations are different and
don't usually follow the www.openbsd.org site style,
if such a thing even exists.
Andres Perera
that there was a much, much bigger problem than merely minor mojibake
gobbledygook in Ingo's presentation.
So I've now just gone through ALL the presentations on
http://www.openbsd.org/papers/ , and I've determined that the problem
is much, much smaller than it's cracked up to be in the misc thread
was that there was mojibake gibberish in
Ingo's presentation, because the character encoding isn't specified
but defaults to UTF-8 in modern browsers, while the page is actually
iso-8859-1 encoded.
Actually, modern browsers do not default to a particular encoding (in
fact, this violates the HTML standard
with it.
So again, the complaint was that there was mojibake gibberish in
Ingo's presentation, because the character encoding isn't specified
but defaults to UTF-8 in modern browsers, while the page is actually
iso-8859-1 encoded.
Actually, modern browsers do not default to a particular encoding (in
fact
On Sun, Jul 1, 2012 at 12:30 PM, Anthony J. Bentley
anthonyjbent...@gmail.com wrote:
So again, the complaint was that there was mojibake gibberish in
Ingo's presentation, because the character encoding isn't specified
but defaults to UTF-8 in modern browsers, while the page is actually
iso
with it.
So again, the complaint was that there was mojibake gibberish in
Ingo's presentation, because the character encoding isn't specified
but defaults to UTF-8 in modern browsers, while the page is actually
iso-8859-1 encoded.
Actually, modern browsers do not default to a particular encoding
Dave Anderson writes:
So, in summary, the options are:
Use HTML escapes everywhere. IMO, highly impractical.
Use any encoding you wish, and set a meta tag when appropriate. This is
basically what we have now. (The front pages of /, /de/, /fr/ all use
ISO-8859-1; /cs/ uses UTF-8; /lt/ uses
On Sun, 1 Jul 2012, Anthony J. Bentley wrote:
Dave Anderson writes:
So, in summary, the options are:
Use HTML escapes everywhere. IMO, highly impractical.
Use any encoding you wish, and set a meta tag when appropriate. This is
basically what we have now. (The front pages of /, /de/, /fr/
out, is bogus. Only broken
browsers are broken.
+pCsikoacute; - Foal. - Photo: Adam Tomkoacute; @flickr (CC)/p
gods, no. html entities are the last thing I want to see.
So again, the complaint was that there was mojibake gibberish in
Ingo's presentation, because the character encoding isn't
support UTF-8.
So again, the complaint was that there was mojibake gibberish in
Ingo's presentation, because the character encoding isn't specified
but defaults to UTF-8 in modern browsers, while the page is actually
iso-8859-1 encoded.
Actually, modern browsers do not default
10 matches
Mail list logo
