02:29
MikeSmith
is suprised nobody mentioned "divitis" during this meeting of the minds, nor "tag abuse"
02:29
<MikeSmith>
Hixie: you use tmux? or just screen?
02:29
<MikeSmith>
I started using tmux and it seems real nice
02:31
<MikeSmith>
can display 🍺 and all other higher unicode while screen can't
02:32
<MikeSmith>
(as long as the glyphs are around of course)
02:32
<Hixie>
screen
02:32
<zewt>
my irc client can't display that, so i'll just assume it's PILE OF POO
02:32
<Hixie>
i've only recently gotten to a world that's beyond ASCII, so...
02:33
<zewt>
(well, it does display it as a single missing character, so it's probably just a font thing)
02:34
<MikeSmith>
zewt: it's U+1F37A BEER MUG
02:37
<MikeSmith>
Hixie: tmux is definitely worth a try. The only problem I ran into with it so far is not really a problem at all but it's that it uses C-b as its prefix key instead of C-a screen thing but my fingers are so trained to the screen C-a that when I want to go back to the beginning of a line I still keep hitting "C-a a" instead of just C-a (and so I get an extra "a" at the beginning of the line that I think have to backspace over)
02:37
<Hixie>
i configure screen to use C-p. I use C-a to go to the start of the line.
02:38
<zewt>
MikeSmith: if you can't even reconfigure that, that would DQ it for me :P
02:38
<MikeSmith>
Hixie: yeah I probably should have done it that way from the beginning so that my fingers didn't end up having C-a burned into memory
02:39
<zewt>
mostly screen is "good enough" that i haven't really bothered trying other things
02:39
<MikeSmith>
zewt: nah you can reconfigure it in tmux too
02:39
<Hixie>
is tmux the one that uses UDP?
02:39
<MikeSmith>
Hixie: dunno if it does or not
02:40
<Hixie>
there's some alternative to screen that uses UDP and predictive magic and local echo to make it seem to have radically lower latency
02:40
<zewt>
ew
02:40
<MikeSmith>
zewt: yeah screen is great. Honestly the only reason I switched was because of the unicode thing
02:40
<Hixie>
so i figure i'm good with screen until i can switch to that
02:40
<zewt>
i'd expect that if there was enough latency to need it, any mispredictions would be worse than the gain
02:40
<MikeSmith>
Hixie: maybe you're thinking of mosh? (alternative to ssh)
02:41
<MikeSmith>
at least that sounds like what mosh does
02:41
<Hixie>
ah yeah, maybe that's it
02:41
<MikeSmith>
yeah
02:41
<MikeSmith>
well I started using mosh recently and it's really great actually
02:42
<MikeSmith>
the other thing about mosh is is that even if your wifi connection drops in and out or your IP address changes, the mosh session just persists
02:42
<MikeSmith>
crappy hotel wifi or whatever
02:42
<zewt>
that's nice i guess, though i wish the ip changing thing could be fixed infrastructurally
02:42
<MikeSmith>
zewt: yeah
02:42
<zewt>
it's excessively lame that all of my connections drop when I unplug my laptop from ethernet
02:43
<zewt>
(and then there's a period of laptop going "huh what wait up I'm confused")
02:44
<zewt>
most of my terminals are in windows with putty, and I just have them all have a startup command of "screen -rd", so I just connect and it goes
02:44
<zewt>
though I need to figure out how to say "connect if there's already a screen running, otherwise start a new one"
02:44
<MikeSmith>
yeah if you have mosh sessions and you unplug that won't happen. At some point mosh will say, "No response for server for NN seconds." where the NN keeps increasing until it gets some network connection behind the session again
02:45
<zewt>
exponential fallback -1
02:45
<Hixie>
i have ssh set up to autostart in terminal, and my .bash_profile autostarts screen, so reconnecting for me is just a matter of restarting terminal
02:45
<zewt>
(yeah you didn't say exponential I know heh)
02:45
<Hixie>
but i really should move to mosh at some point
02:46
<zewt>
(but generally increasing fallback makes sense if you're talking to a big central server, not so much for terminals where you're usually talking to a small personal server with no thundering herd problem to worry about)
02:46
<MikeSmith>
the only downside I've run into with mosh is (surprise) a unicode issue -- but it's not due to a problem in mosh, it's due to a problem with OS X using some old libc instead of glibc
02:46
<zewt>
heh one of the big things osx needs: gnu tools
02:47
<zewt>
drives me crazy when I type "ls /foo", then hit up and add "ls /foo -l"
02:47
<MikeSmith>
yeah
02:47
<zewt>
and osx looks at me funny, instead of just working
02:48
<MikeSmith>
I just used the g* versions of everything on osx, installed from port (e.g., greadlink, gdate)
02:49
<MikeSmith>
anyway, the osx unicode issue causes mosh client on osx to not display U+1F37A, etc., as expected
02:49
<zewt>
guess I've never hit anything to make me care about non-BMP unicode
02:49
<MikeSmith>
https://github.com/keithw/mosh/issues/478 and https://github.com/Homebrew/homebrew/issues/26370 have the details
02:49
<zewt>
other than in principle (utf-16 needs to die)
02:50
<MikeSmith>
yeah for me it's more the principle I guess
02:51
<zewt>
utf-16 is fantastic because: it combines the downsides of UCS-4 (non-byte encoding so it's completely incompatible with multibyte encodings), *and* the downsides of UTF-8 (compared to UTF-32, eg. no random access by index)
02:51
<zewt>
worst of both worlds. thanks for that
02:52
<zewt>
(not that the latter is a big downside ... it's just the *only* benefit of raw UCS-4, really)
04:49
<MikeSmith>
heads-up: some time later today I'm going to break all URLs under http://dev.w3.org/csswg/ again
04:50
<MikeSmith>
we are flipping the DNS over on the host those are getting rewritten to, and I'll need to change a rewrite directive to point to a different port on that host
04:50
<MikeSmith>
but I can't do that until after the DNS if flipped
04:59
SamB
thinks it's remarkable how many of the WHATWG logos are bad visual puns ...
05:27
<Domenic_>
<3 the WHATWG logos
05:27
<Domenic_>
My favorite is encoding
05:27
<Hixie>
i must admit to not understanding the xhr one
05:28
<Domenic_>
yeah... apparently from http://en.wikipedia.org/wiki/AFC_Ajax
05:30
<Hixie>
aah
05:30
<zewt>
i can't say that i've ever consciously noticed that a whatwg logo of any sort exists
05:30
<Hixie>
it's, like, plastered all over the site
05:30
<zewt>
i probably just tune logos out without noticing it
06:24
<SamB>
Domenic_: yes, encoding is great but I had a nice delayed groan with the XHR one when I finally figured out who the guy in the picture had to be :-)
06:27
<SamB>
had no idea there was a football team involved though
06:30
<SamB>
so, is "our" usage of this Ajax based on the "right to parody", or?
06:33
<TabAtkins>
MikeSmith: The URL breakage is temporary, right?
06:33
<MikeSmith>
TabAtkins: yeah
06:33
<TabAtkins>
All right, no problem then. ^_^
06:33
<MikeSmith>
actually right now I'm trying to set it up so there will not even be any temporary breakage
06:34
<SamB>
huh, why am I surprised that google is so confident as to the identity of this greek dude in logo-xhr.png that it fills in the words "ajax amsterdam logo" in the search box when I search by that image?
06:51
<MikeSmith>
TabAtkins: OK I think I've got the ports and apache config set up the right way now and we'll be flipping the DNS soon
06:51
<MikeSmith>
but it'll take a few hours to propogate
06:51
<MikeSmith>
so I reckon you'll be asleep by then
06:51
<TabAtkins>
yeah
06:51
<MikeSmith>
but when you get online tomorrow if you find any problems lemme know
06:52
SamB
isn't sure why we the logo for the URL standard is based on a colon ...
07:02
<SamB>
oh, right ...
07:02
SamB
remembers that a lot of URL schemes don't do anything special with /
10:05
<mathiasbynens>
hsivonen: your feedback on https://codereview.chromium.org/183893021 (see comments) would be appreciated
10:35
<jgraham>
Philip`_: For informational purposes, is your old OCaml implementation of the HTML tokenizer/parser around?
12:29
<MikeSmith>
jgraham: about the wptserve code change we need for w3c-test.org (option to not restrict access to localhost), you want me to write a PR or have you been working on it already?
12:32
<jgraham>
MikeSmith: I haven't worked on it yet
12:32
<jgraham>
MikeSmith: So feel free
12:33
<MikeSmith>
ok I will
12:37
<MikeSmith>
jgraham: btw how we get the github remote w-p-t repo "resources" submodule updated to the latest upstream testharness.js?
12:37
<jgraham>
Thanks
12:38
<MikeSmith>
to include, e.g., the change from foolip_ that removed the media/ subdir
12:38
<jgraham>
MikeSmith: cd resources; git pull; cd ..; git add resources; git commit -m "Update to latest testharness.js"; git push
12:38
<jgraham>
Or something
12:39
<MikeSmith>
ok
12:39
<MikeSmith>
so I'll go ahead and push that, thanks
12:43
<odinho>
It's probably detached HEAD, so you ofc need to make sure you are standing on the correct commit (e.g. by checkout out origin/master)
12:43
<jgraham>
Oh, that could be the case yeah
12:45
<MikeSmith>
indeed yeah
12:45
<MikeSmith>
had to checkout master first
12:45
<MikeSmith>
anyway, done now
12:47
<odinho>
(working daily with submodules at Opera, watching new people screw up the the same things many times, has some benefits :) )
12:49
jgraham
takes responsibility for suggesting using git pull rather than git fetch
12:49
<odinho>
:]
12:49
<odinho>
(if suggesting git pull, I always write as git pull --ff-only)
12:49
<Ms2ger>
Boo, submodules
12:49
<MikeSmith>
I just use "git pull -r" any time I see "git pull"
12:50
<MikeSmith>
except for critic review branches
12:50
<Ms2ger>
I just use a pull.sh I wrote a long time ago
12:50
<MikeSmith>
yeah crazy assed submodule voodoo
12:52
<MikeSmith>
anyway I don't like merge
12:53
<MikeSmith>
if a rebase messes up I just get an error message and then after that I run rebase --abort
12:54
<MikeSmith>
I don't know of any merge --abort and even if there was one I won't use it because why would you since you can always just use rebase
12:55
<MikeSmith>
hmm odinho is there some config setting that will cause "--ff-only" to always be used with merge?
12:56
<MikeSmith>
nm
12:56
MikeSmith
finds ff = no
12:56
<odinho>
:)
12:57
<davve`>
But you want 'git config merge.ff only', right?
12:58
<MikeSmith>
davve`: yeah
12:58
<MikeSmith>
--global
12:59
<MikeSmith>
fking git
12:59
<MikeSmith>
they need to make this stuff way more complicated
12:59
<MikeSmith>
it's all just too clear and easy right now
13:01
<jgraham>
MikeSmith: It might be worse. It might be mercurial.
13:01
<jgraham>
:)
13:02
Ms2ger
whacks jgraham
13:04
<jgraham>
Yes, trying to use bookmarks makes me want to resort to violence too
13:04
<MikeSmith>
jgraham: Ms2ger is whacking you so that you'll sustain a head injury so that your IQ will decrease and you'll then become a mercurial advocate
13:05
<Ms2ger>
MikeSmith, I'd better not try to decrease yours any further ;)
13:05
<MikeSmith>
hehah
13:05
<MikeSmith>
that's probably not possible
13:06
<Ms2ger>
Well, you never know
13:06
<Ms2ger>
Might hit an underflow :)
13:06
<MikeSmith>
hah
13:13
<hsivonen>
mathiasbynens: I sent some feedback.
14:46
<mathiasbynens>
hsivonen: much appreciated
15:07
<MikeSmith>
hsivonen: OK with you if I go ahead and change vnu build.py to pull from github instead of bitbucket? (after syncing up the github repos to the latest bitbucket sources)
15:07
<hsivonen>
MikeSmith: OK.
15:08
<MikeSmith>
hsivonen: thanks
15:09
<MikeSmith>
how about jing-trang? I have a mirror of that at github too already. OK to use that? (so we can eliminate the svn dependency) Or would you rather we keep pulling from the upstream svn repo for that?
15:13
<MikeSmith>
hsivonen: ↑
15:16
<hsivonen>
MikeSmith: let's pull from github
15:16
<hsivonen>
MikeSmith: what happens with the htmlparser repo?
15:18
<MikeSmith>
hsivonen: I have a github mirror of that too
15:18
<MikeSmith>
and I'll just manually update that by pulling from the mozilla hg repo
15:18
<MikeSmith>
and pushing to the github repo
15:19
<MikeSmith>
whenever there are changes
15:19
<MikeSmith>
if that's OK for you
15:19
<MikeSmith>
alternatively we can keep pulling from the upstream hg repo directly fo that
16:32
<Ms2ger>
Postel tarpit (n.) - A system that has tried so hard to accept all possible input that any change becomes backwards-incompatible
16:32
<Ms2ger>
Aka "the Web"
17:58
<SimonSapin>
MikeSmith: http://dev.w3.org/csswg seems stuck in January
17:59
<jgraham>
The CSS WG are now officially stuck in the past?
18:00
<SimonSapin>
well, https://dvcs.w3.org/hg/csswg/ is fine
18:00
<ltilve>
hi
18:00
<ltilve>
I have been doing a patch related with <select> elements not dispatching input events
18:00
<ltilve>
http://code.google.com/p/chromium/issues/detail?id=349472
18:01
<Ms2ger>
SimonSapin, I saw something come by about that breaking due to dns changes
18:02
<ltilve>
I guess that the comments here https://www.w3.org/Bugs/Public/show_bug.cgi?id=22467 are still valid, aren't they?
18:03
<ltilve>
(I ended at the link to http://www.whatwg.org/specs/web-forms/current-work/#the-change from the equivalent WK bug https://bugs.webkit.org/show_bug.cgi?id=117526)
18:06
<MikeSmith>
SimonSapin: it's probably related to the fact I moved the rewrite for http://dev.w3.org/csswg to a different host today
18:06
<Ms2ger>
ltilve, whoa whoa whoa
18:06
<Ms2ger>
ltilve, please scroll to the top of http://www.whatwg.org/specs/web-forms/current-work/#the-change
18:07
<SimonSapin>
MikeSmith: is the mercurial push hook still syncing to the old host?
18:07
<MikeSmith>
SimonSapin: is contents of http://dev.w3.org/csswg same as http://128.30.54.131/csswg/ ?
18:07
<MikeSmith>
SimonSapin: maybe
18:07
<MikeSmith>
dunno
18:07
<MikeSmith>
I'll look
18:08
<Ms2ger>
ltilve, and if you want a serious answer to a bug, you should file it in the whatwg component, not the html wg one
18:08
<MikeSmith>
SimonSapin: but frankly I really rather not have to keep dealing with this rewrite
18:09
<Ms2ger>
Hixie, can you make the banner on http://www.whatwg.org/specs/web-forms/current-work/#the-change position:fixed?
18:11
<SimonSapin>
MikeSmith: they’re not the same for me, http://128.30.54.131/csswg/ is fine
18:11
<MikeSmith>
SimonSapin: yeah it seems I have to re-setup some useless crap on the new host just for the csswg case
18:12
<MikeSmith>
this is nuts really
18:12
<SimonSapin>
Is 128.30.54.131 the old host?
18:12
<MikeSmith>
yeah
18:13
<SimonSapin>
how do other things work?
18:13
<MikeSmith>
I want Peter to figure out some alternative that doesn't involve me
18:13
<MikeSmith>
other things work by not using mercurial
18:13
<MikeSmith>
and by not rewriting URLs from dev.w3.org to w3c-test.org
18:14
<ltilve>
thanks Ms2ger, I hadn't scrolled top :p
18:14
<Ms2ger>
ltilve, it's clearly not huge enough :)
18:14
<ltilve>
"anchors happen"
18:15
<paxcoder>
hola
18:15
<ltilve>
it was big indeed :)
18:16
<MikeSmith>
SimonSapin: I'll e-mail Peter. I have zero enthusiasm for spending any more time dealing with this than the hours I've wasted on it already in the past at his request
18:16
<MikeSmith>
you guys really need to find something sane
18:17
<MikeSmith>
instead of this convoluted way
18:17
<MikeSmith>
it's all totally unnecessary, this stuff that Peter has set up
18:18
<MikeSmith>
or rather that Peter talked me through setting up for him
18:18
<MikeSmith>
"Make sure to cut the *green* wire, not the red one"
18:19
<jgraham>
Ms2ger: Obviously the whole page should be display:none except that warning until you click a button marked "I am only reading this out of historical interest and will not use the document for any purpose related to implementing web browsers or authoring web content"
18:19
<MikeSmith>
SimonSapin: sorry I broke it but http://128.30.54.131/csswg/ should have the latest until I can figure out something else
18:19
<Ms2ger>
jgraham, can I leave the warning out?
18:21
<SimonSapin>
thanks MikeSmith. Apparently Peter’s plan is to have dev.csswg.org/csswg proxy to drafts.csswg.org. Does that sound more sane?
18:21
<MikeSmith>
SimonSapin: yes
18:21
<MikeSmith>
please
18:22
<MikeSmith>
he can make that change himself at http://dev.w3.org/cvsweb/csswg/.htaccess?rev=1.21
18:22
<MikeSmith>
as far as I know
18:31
<MikeSmith>
SimonSapin: OK I just e-mailed Peter about it directly as well
18:32
<MikeSmith>
SimonSapin: again, sorry
18:32
<SimonSapin>
no problem, thanks
18:32
<MikeSmith>
SimonSapin: thanks for the heads-up about it and sorry for ranting
18:33
<SimonSapin>
to be fair the little I know about the old setup does sound, hum, hairy
19:14
<Hixie>
Ms2ger: done
19:14
<Hixie>
does any browser support 'filter: grayscale()' yet? i want to desaturate the images at the same time
19:15
<Hixie>
but i can't work out how to do it short of lots of prefixed properties and some svg
19:15
<Hixie>
which seems a bit excessive
19:15
<Ms2ger>
Thanks
19:16
<jgraham>
Hixie: The text doesn't seem to be gray anymore
19:16
<Hixie>
oops
19:17
<Hixie>
try again
19:17
<Hixie>
(what browser?)
19:17
<krit_>
MikeSmith: the link to CSS Compositing is broken http://dev.w3.org/fxtf/compositing-1/
19:17
<krit_>
MikeSmith: gives me {"error": {"message": "", "code": 404}}
19:17
<jgraham>
Hixie: Firefox
19:17
<jgraham>
Hixie: Now the warning is gray :)
19:18
<Hixie>
already fixed that
19:18
<Ms2ger>
krit_, you should join #css on w3 :)
19:18
<Hixie>
i was a bit overzealous with my filters
19:19
<Hixie>
(the text not being gray was because firefox supports scoped="", nice!)
19:19
<krit_>
Ms2ger: just searched a channel with MikeSmith. This was the first I found :P
19:19
<jgraham>
Hixie: Works now
19:19
<Ms2ger>
http://dev.w3.org/csswg/css2/ is rumoured to work
19:19
SamB
thought filters WERE an SVG thing
19:20
<Ms2ger>
Only took 15 years
19:20
<krit_>
Ms2ger: that is a different repository, but the FX rep works in general as well
19:20
SamB
wonders how crazy allowing SVG filters on everything would be ...
19:20
<krit_>
SamB: we are just that crazy and do that!
19:20
<SamB>
(without actually having to use that foreignOjbect thing)
19:20
<krit_>
SamB: you can try kind of in WebKit/Blink and soon in Firefox
19:21
<krit_>
SamB: sorry, it works in Firefox, the filter functions will work in FF soon
19:21
<SamB>
it certainly seems a lot less crazy than NIHing a filter language of similar expressiveness in CSS, yes
19:24
<SamB>
hmm, I probably asked about this before, but where is the "shadow DOM" idea from XBL being worked on? MDN is still linking to a long-abandoned "XBL 2" effort ...
19:29
<Hixie>
ok i've gone and added the same position:fixed warning and gray styling to all the snapshots of wf2 and wa1/html5 that we have
19:29
<TabAtkins>
Ooooh, grayscaling obsolete stuff sounds awesome.
19:29
TabAtkins
goes to update Bikeshed's obsoleting styles.
19:29
<MikeSmith>
krit_: talk to fantasai or Peter or Bert
19:30
SamB
wonders how hard Sepia would be
19:30
<Domenic_>
Hixie: sample link, out of curiosity?
19:30
<krit_>
SamB: filter: sepia(0.5)
19:30
<MikeSmith>
krit_: fantasi updated the dev.w3.org/csswg rewrite to point to http://drafts.csswg.org
19:30
<MikeSmith>
http://dev.w3.org/cvsweb/csswg/.htaccess?rev=1.23
19:30
<SamB>
krit_: okay now that is just cheating
19:31
<Hixie>
Domenic_: http://www.whatwg.org/specs/web-apps/2009-10-27/multipage/content-models.html#interactive-content-0 or http://www.whatwg.org/specs/web-forms/2005-09-01/
19:31
<MikeSmith>
krit_: so if
19:31
<Domenic_>
Hixie: nice
19:31
<krit_>
MikeSmith: hm, the FX repository is not maintained by you anymore?
19:31
SamB
was expecting the need for, like, color('sepia')*monochrome or so ...
19:32
<Hixie>
this is some svg filter i found on stackoverflow, mostly
19:32
<Hixie>
seems css filters are still not quite there
19:32
<MikeSmith>
krit_: ah FX. fantasai needs to update the rewrite for that one too I guess
19:33
<krit_>
Hixie: well, if you use filters, you should use -webkit-filter: grayscale() for webkit/blink and filter: url(#svgFilter) for Firefox... no way to filter HTML elements in IE
19:33
<MikeSmith>
krit_: and no I have nothing to do with the FX repo or any of this tuff any more. I have exited the business
19:33
<krit_>
Hixie: for performance reason mainly
19:34
<Hixie>
krit_: right, like i said, css filters aren't really there yet :-)
19:34
<Hixie>
krit_: i mean, what i _want_ is "filter: grayscale and sepia" or something
19:34
<krit_>
Hixie: got you
19:35
<SimonSapin>
".obsolete { border: double thick red ! important;" that should be in ALL CAPS, to give it more weight
19:36
<Hixie>
heh
19:37
<Hixie>
wtf, the 'filter' property affects the z-index?
19:37
<Hixie>
what kind of crap is this
19:37
<Domenic_>
everything affects z-index
19:37
<Domenic_>
z-index is a landmine waiting to destroy you and eat your soul
19:37
Hixie
adds some z-index values to the position:fixed element
19:37
<Domenic_>
(by "everything" i mean "random features")
19:39
<SamB>
okay I am confused by this bullet in the FAQ: "* Bug fixing: when bugs are found in the spec or implementations, they have to be maintained"
19:40
<SamB>
if this is actually talking about maintaining the bugs themselves, then I think that needs more explanation of the reason for it
19:40
<SamB>
otherwise, I could probably reword it for you ...
19:40
<Ms2ger>
they = the spec or implementations
19:41
<Hixie>
source?
19:41
<SamB>
oh, I guess they = features
19:42
SamB
grumbles about the missing "copy link to this anchor" command in browsers ...
19:42
<Hixie>
oh, from the faq
19:42
<SamB>
Hixie: http://wiki.whatwg.org/wiki/FAQ#Where.27s_the_harm_in_adding.E2.80.94
19:43
<Hixie>
updated
19:46
<Philip`_>
jgraham: It is
19:47
<Ms2ger>
Philip`_, where?
19:47
<Philip`_>
Ms2ger: That's a harder question :-(
19:48
<Philip`_>
jgraham: I think http://canvex.lazyilluminati.com/svn/tokeniser/ may be the latest version
19:49
<Philip`_>
("latest" being over 5 years ago)
19:51
<SamB>
hmm, it never occurred to me to wonder how the w3c got w3.org before ...
19:52
<SamB>
but I just typed "www.3.org" and now I do
19:53
<Hixie>
as opposed to what?
19:56
<SamB>
I guess they got in before there were rules and/or squatters
20:03
<Domenic_>
I am making an argument to corporate peoples that ASCII is not enough for names. Any reasonably-famous people I can cite with non-ASCII characters in their names? /cc mathiasbynens
20:03
<Ms2ger>
Er...
20:03
<Ms2ger>
All of China?
20:04
<Domenic_>
that helps i suppose.
20:06
<SimonSapin>
Domenic_: famous to whom?
20:06
<Domenic_>
SimonSapin: either "everybody" or "developers" sounds good.
20:07
<Hixie>
Domenic_: Влади́мир Пу́тин is pretty famous
20:07
<SimonSapin>
http://people.opera.com/howcome/ maybe?
20:08
<Hixie>
Domenic_: 毛泽东 was also pretty famous
20:08
<Domenic_>
SimonSapin: yup that was my first example actually :)
20:08
<Domenic_>
Hixie: yeah, but I kind of feel like their argument would be "he should just type Mao Zedong"
20:09
<Hixie>
Ἰησοῦς, also known as ישוע, is also pretty famous
20:09
<Domenic_>
heh
20:10
<Hixie>
Domenic_: well, if people are willing to just randomly rename people for the sake of their database, you're not going to convince them...
20:10
<Ms2ger>
Domenic_, what's next, won't allow numbers in names?
20:11
<Domenic_>
Ms2ger: somewhat ironically, the current regex is: ^[-A-Za-z0-9.,' ]{0,64}$
20:12
<Hixie>
and the artist formerly known as "the artist formerly known as Prince" used to have a name that even Unicode can't describe
20:12
<Hixie>
afk, lunch
20:12
<SimonSapin>
Domenic_: http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ sounds relevant
20:12
<Domenic_>
SimonSapin: yup, was going to close with that...
20:15
<SimonSapin>
although not to take it too seriously
20:15
<SimonSapin>
restricting names handled in software to all of Unicode sounds reasonable
20:44
<TabAtkins>
Domenic_: Fucking most of Europe?
20:45
<TabAtkins>
áéóåöç etc
20:45
<TabAtkins>
Not to mention things like the Turkish i situation.
21:09
<mathiasbynens>
Domenic_: https://jonaswesterlund.se/invalid-form-validation.html may also be of reference
21:14
<mathiasbynens>
Domenic_: more ‘famous’ (to us) people with non-ASCII names: Geir Ivarsøy, Faruk Ateş, Юрий Зайцев (aka. kangax), Cãtãlin Mariş, etc.
21:14
<Domenic_>
mathiasbynens: good stuff, thanks
21:14
<TabAtkins>
Tantek Çelik
21:14
<mathiasbynens>
Domenic_: fun fact: Sindre Sørhus changed his name to Sindre Sorhus because of this
21:14
<Ms2ger>
Eh, tantek :)
21:15
<TabAtkins>
(And that i is a turkish lowercase dotted i, not an ASCII dotted i.)
21:15
<Domenic_>
mathiasbynens: oh wow did not know
21:15
<mathiasbynens>
like, legally. pretty sad story
21:15
<Domenic_>
TabAtkins: oh wow, he must have a bad time with that i.
21:15
<TabAtkins>
Domenic_: Heh, yeah. I suppose most people with Turkish names learn to live with it.
21:16
<TabAtkins>
And accept that, when uppercased, their name will look wrong.
21:16
<Hixie>
the turkish lowercase dotted i actualy is the ASCII dotted i
21:16
<TabAtkins>
As it's actually written in HTML when he does so, it's a turkish undotted i with a combining dot.
21:16
<Hixie>
it's just that the ASCII dotted i has different capitalisation rules (and the I different lowercasing rules) in the turkish locale.
21:16
<TabAtkins>
So it uppercases correctly.
21:17
<Hixie>
yeah, but that's a hack
21:17
<TabAtkins>
A hack that actually works, though.
21:17
<Hixie>
the character is correctly the ASCII "i".
21:17
<Hixie>
it's a good example of why this stuff is hard, though :-)
21:17
<TabAtkins>
I cant' understand how the Turkish i's got folded into ASCII when so many other scripts have identical letters separated.
21:17
<TabAtkins>
Yay Unicode.
21:17
<Hixie>
yeah, beats me
21:18
<Ms2ger>
TabAtkins, hey, cjk ;)
21:18
<TabAtkins>
Indeed.
21:18
<Hixie>
that too
21:28
<jgraham>
Interestingly I noticed that in the winter olympics, all the on-screen information was ascii-only even though that clearly wasn't sufficient
21:29
<jgraham>
So they did things like transliterate Swedish ö to o
21:29
<jgraham>
Which is just wrong
21:31
<jgraham>
Philip`: Thanks
21:31
<Hixie>
anyone know what http://zzyzwicz.w3.org/resources.whatwg.org/ is about?
21:31
<gsnedders>
jgraham: I presume they just had a generic codepoint to ASCII codepoint mapping.
21:32
<jgraham>
gsnedders: Well it's hard to know what they did
21:32
<jgraham>
I think it's somewhat reasonable that British people wouldn't deal with non-latin characters
21:33
<Ms2ger>
Hixie, I think someone scraping w3c-test?
21:33
<Ms2ger>
Oh, w3.org
21:33
<Ms2ger>
MikeSmith?
21:36
<Hixie>
anyone here know anything about ruders.org?
21:36
<gsnedders>
jgraham: Okay, so it was a Vizrt system (somewhat unsurprisingly, they're who everyone use for OSD), and they're based in Bergen, so I'd be surprised if it was really ASCII-only
21:37
<jgraham>
gsnedders: The backend might not have been
21:37
<jgraham>
But I'm prety sure what we saw was
21:38
<gsnedders>
Yeah, indeed. But the OSD certainly should've supported it.
21:38
<gsnedders>
Where the data was coming from is a separate matter again.
21:38
<gsnedders>
As is data entry.
21:38
tantek
scrolls up
21:38
<gsnedders>
I wouldn't be at all surprised if it was in data entry where it all went wrong :)
21:38
<jgraham>
I think it was probably intentional
21:39
<jgraham>
I don't know *why*
21:39
<tantek>
Hixie is correct about the dotted lowercase i
21:39
tantek
goes back to #ab in irc.w3.org
21:40
<gsnedders>
is dotted lowercase i in NFC?
21:40
<TabAtkins>
Man, turning ö to o is just *super* wrong. The accepted ASCII mapping is to "oe".
21:40
<gsnedders>
TabAtkins: For some languages.
21:40
<TabAtkins>
Hm, I guess so. Definitely for german.
21:40
<jgraham>
I guess it could have been to oe, but that's just as wrong for Swedish
21:40
<TabAtkins>
and I think Björn is Nordic?
21:41
<jgraham>
Yeah, in German it seems to be acceptable to replace umlauts with es
21:42
<gsnedders>
jgraham: Well, it's how you do it *if you have to do it*.
21:42
<gsnedders>
jgraham: So in a sense it's /less/ wrong
21:42
<gsnedders>
TabAtkins: But in French you certainly just drop the diacritic
21:43
<jgraham>
I'm pretty sure I remember foolip saying that he wouldn't transliterate ä to ae
21:44
<jgraham>
(but I might be wrong)
21:47
<TabAtkins>
gsnedders: Yeah, I know about dropping the diacritic when it's just a grave accent.
21:49
<gsnedders>
TabAtkins: It applies for all diacritics in French, not just graves.
21:49
<TabAtkins>
Ah, kk.
21:49
<TabAtkins>
Yeah, that makes sense, François to Francois, etc.
21:49
<gsnedders>
Again, locale dependent.
21:50
<gsnedders>
jgraham: Certainly å to aa is relatively common, though far more recent addition to alphabet.
21:51
<gsnedders>
(Which is kinda odd. Seems to have gone from á -> aa -> å)
21:53
<TabAtkins>
I thought å went to "ow".
21:54
<gsnedders>
It's a long a
21:54
<gsnedders>
(acute is used in Old Norse as a length marker, hence á)
21:55
<gsnedders>
There again, I find it horrific placing vowels in the vowel space. :)
21:55
<TabAtkins>
Then explain "howcome", smarty-pants.
21:55
<TabAtkins>
^_^
21:56
TabAtkins
is aware of what it sounds like, and how "howcome" is a joke.
21:56
<gsnedders>
It's amusingly close, though :)
21:57
<gsnedders>
Esp. giving linking phenomena softening the "ow"
21:57
<gsnedders>
Oh god, I just looking up all the various terms for various phonetic linking phenomena.
21:58
gsnedders
goes back to avoiding phonetics
22:05
<Hixie>
(i dunno about hte languages y'all are talking about, but in norwegian, the letters with diacritics are actually just different letters, so replacing them with other letters wouldn't make sense, as i understand it)
22:08
<jgraham>
Hixie: Yeah, Swedish is the same
22:08
<jgraham>
German less so aiui
22:08
<Hixie>
yeah
22:09
<SimonSapin>
Dropping accents in French is not uncommon, but still wrong
22:09
<SimonSapin>
it can be ambiguous
22:12
<Hixie>
MikeSmith: you around?
23:35
<Hixie>
Michael Dyck rocks
23:35
<Hixie>
SamB: not sure what i should do with https://www.w3.org/Bugs/Public/show_bug.cgi?id=24893
23:36
<TabAtkins>
Hixie: Who's Michael Dyck?
23:37
<Hixie>
dunno but he files a ton of bugs on typos and stuff
23:37
<SamB>
Hixie: hmm, well, am I correct that what Matthew Raymond gave you was a 256x256 raster (presumably in PNG format)?
23:38
<Hixie>
i think so? not sure.
23:38
<Hixie>
i couldn't actually track down the original e-mail.
23:38
<Hixie>
i found lots of e-mails around it.
23:38
<Hixie>
but not the actual one.
23:38
<Hixie>
:-/
23:38
<SamB>
yeah, it looked like there were one or two images that were missing from the list archives
23:38
<SamB>
er. s/images/emails/
23:39
<Hixie>
i couldn't even find them in my own private mail archives
23:39
<SamB>
anyway, from the sound of things he wasn't even using his own question mark
23:41
<smaug____>
Hixie: by any chance, do you recall spec changes affecting https://bugzilla.mozilla.org/show_bug.cgi?id=951887
23:43
<SamB>
so now I'm wondering if there's some way I can find out what font the question mark might be from ...
23:43
<SamB>
Hixie: oh, and that still leaves the .js files without copyright/license headers