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
stem even as patch was sent
before two years, but Czech keyboard is available in X via setxkbmap
which is fine for me. As it's UTF-8 including files I'm doing that
from gtk+ vim as no other tool from base support UTF-8.
>
>> So again, the complaint was that there was mojibake g
ers.
I think that complaint, as pointed out, is bogus. Only broken
browsers are broken.
> +Csikó - Foal. - Photo: Adam Tomkó @flickr (CC)
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 pres
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
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
hat it means adding escapes *everywhere*. Can you
>imagine writing http://www.openbsd.org/cs/ in anything but native UTF-8?
>At some point we have to pick an encoding and stick with it.
>
>> So again, the complaint was that there was mojibake gibberish in
>> Ingo's presentatio
On Sun, Jul 1, 2012 at 12:30 PM, Anthony J. Bentley
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 ac
ent regardless of declared character encoding.
The disadvantage is that it means adding escapes *everywhere*. Can you
imagine writing http://www.openbsd.org/cs/ in anything but native UTF-8?
At some point we have to pick an encoding and stick with it.
So again, the complaint was that there was mo
g pure ASCII plus HTML escapes in a page is that it
displays the correct content regardless of declared character encoding.
The disadvantage is that it means adding escapes *everywhere*. Can you
imagine writing http://www.openbsd.org/cs/ in anything but native UTF-8?
At some point we have to pick an e
e
parameter, and people had all kinds of responses, mostly suggesting
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
10 matches
Mail list logo
