| 00:02 | <Hixie> | TabAtkins: you still want cssElementMap right? |
| 00:07 | <Hixie> | TabAtkins: you still want cssElementMap right? |
| 00:10 | <Hixie> | i love, in "Detecting and Resolving Circular Relationships", that in the prose it confidently states "These relationships can be easily and reliably detected and resolved" but in the issue marker below that it says "Someone else needs to review this and make sure that I'm not missing any cycles" |
| 00:10 | <Hixie> | (http://dev.w3.org/csswg/css3-images/#element-reference) |
| 00:31 | <TabAtkins> | Hixie: Yes, I do. |
| 00:31 | <Hixie> | k |
| 00:32 | <TabAtkins> | Hixie: The issue will disappear in time, leaving only my confident declaration. |
| 00:32 | <Hixie> | any chance i could get you to change "represents" in "represents a paint source" to "provides"? |
| 00:33 | <Hixie> | "represents" has a defined meaning in the html spec so it is a little confusing in some of these sentences |
| 00:33 | <TabAtkins> | Sure. |
| 00:33 | <Hixie> | awesome |
| 00:35 | <TabAtkins> | done |
| 00:35 | <Hixie> | csselementmap isn't in the w3c copy of html, should "provides a paint source" be? |
| 00:35 | <Hixie> | or should i add csselementmap too? |
| 00:35 | <Hixie> | (i don't recall why it's not included) |
| 00:35 | <TabAtkins> | Yes. The intention currently is that a display:none <img> provides a paint source. |
| 00:35 | <TabAtkins> | And sure, since it's not exposing any API or anything, might as well. |
| 00:36 | Hixie | is confused by the two most recent lines from TabAtkins |
| 00:36 | <Hixie> | come again? |
| 00:37 | <TabAtkins> | The clause that invokes paint sources in the Image Values spec is applicable to more than just things assigned to the csselementmap. |
| 00:37 | <TabAtkins> | Since "provides a paint source" isn't an API detail (like csselementmap is), it shouldn't arouse any complaints if it's put in the spec. |
| 00:38 | <Hixie> | ah, ok. so you're saying paint source in w3c, csselementmap not |
| 00:38 | <Hixie> | ok |
| 00:38 | <Hixie> | sounds good, that's what i had done |
| 00:38 | <TabAtkins> | I don't care if you put csselementmap in. I'm just saying that paint source is totally fine. |
| 00:39 | <Hixie> | ok done: http://html5.org/tools/web-apps-tracker?from=6519&to=6520 |
| 00:40 | <TabAtkins> | Looks good. |
| 01:08 | <Hixie> | AryehGregor: see the widget where you pick people to share with in G+ for a use case of contenteditable="" that might be worth bearing in mind |
| 01:09 | <Hixie> | AryehGregor: also re http://www.w3.org/Bugs/Public/show_bug.cgi?id=12834#c10 -- it's not my scripts, i just use a bugzilla query of open bugs, so closed bugs don't get matched by the query :-) |
| 01:09 | <Hixie> | that's why i don't see comments on closed bugs |
| 08:54 | <nlogax> | Hixie: are you there? |
| 14:02 | <krijn> | Ms2ger: back, sorry! :) |
| 14:03 | <krijn> | My mom was showing somebody how fuses work. |
| 14:03 | <krijn> | She really shouldn't |
| 14:24 | <Ms2ger> | Heh |
| 15:06 | <jgraham> | Ms2ger: Technically that part of the spec is a SHOULD |
| 15:06 | <jgraham> | I'm not sure if we ever come to a conclusion about testing SHOULDs |
| 15:06 | <zcorpan> | annevk: wonder how many you've managed to confuse on events |
| 15:07 | <Ms2ger> | That's a bug in the spec I should file, then |
| 15:10 | <jgraham> | Ms2ger: I suppose one should argue that the spec should allow you to open a text/plain document in an external editor if you like |
| 15:12 | <annevk> | zcorpan, per matjas the fault is HTML4: http://www.w3.org/TR/html4/interact/scripts.html#h-18.2.3 |
| 15:14 | <realityking> | I'm looking for a HTML5 parser for php and the only thing that looks promising so far is html5lib |
| 15:14 | <realityking> | but the php port hasn't been updated for 2 years |
| 15:15 | <realityking> | anyone know how mature it is or if there's a better alternative? |
| 15:16 | <annevk> | I haven't seen anything |
| 15:19 | <jgraham> | realityking: I don't really know anything about the PHP port, sorry. It won't have changed to match the current spec perfectly |
| 15:19 | <jgraham> | It might be slow depending on what your needs are |
| 15:19 | <zcorpan> | annevk: woah |
| 15:53 | <Ms2ger`> | annevk, I know... That's why I don't see us running XHR tests any time soon |
| 16:33 | <realityking> | jgraham, annevk: thanks for the info |
| 16:40 | <dglazkov> | good morning, Whatwg! |
| 16:41 | <dglazkov> | and evening, Ms2ger` |
| 16:41 | <Ms2ger`> | Good afternoon, dglazkov |
| 16:41 | <dglazkov> | doh |
| 16:42 | <Ms2ger`> | And may this day bless you and your family, to quote Philip` |
| 16:42 | <dglazkov> | and fruit in the pants, to qoute jgraham |
| 16:46 | <annevk> | :) |
| 18:06 | <gsnedders> | realityking: the PHP parser doesn't perfectly match the current spec, but should work reasonably well on not-overly long documents (parts of PHP's DOM impl have O(n^2) perf, so it hurts) |
| 18:06 | <realityking> | gsnedders: usage would be to parse articles to a DOM in a CMS so certain attributes/elements can be filtered on save |
| 18:06 | <realityking> | so documents shouldn't be too long |
| 18:06 | <realityking> | but I am slightly worried about it not perfectly matching the spec |
| 18:06 | <realityking> | I wish the PHP devs would just get a proper parser into the core... |
| 18:06 | <realityking> | thanks for your help tough |
| 18:06 | <gsnedders> | realityking: Basically, when there were major changes to the spec a couple of years ago, I spent what seemed like an eternity making the tedious changes to the Python version, and never had the motivation to make them in PHP too. Especially seeming I ended up never using it in the end. |
| 18:06 | <gsnedders> | (around script parsing, that was) |
| 18:07 | <realityking> | btw, is there any open source c library available for html5 parsing? |
| 18:08 | <gsnedders> | takkaria wrote one a few years back. No idea if it is maintained. |
| 18:08 | <Ms2ger`> | There will be a C++ one once hsivonen gets around to packaging his |
| 18:08 | <Ms2ger`> | Maybe even in this decade |
| 18:08 | <realityking> | :) |
| 18:09 | <Hixie> | foolip: previously, cues that were found to have been missed when the browser next checked for cues were just dropped on the floor |
| 18:09 | <Hixie> | foolip: i fixed that |
| 18:11 | <gsnedders> | Ms2ger`: You're hopeful. :) |
| 18:12 | <Ms2ger`> | One needs to be in this business... There's so little hope for the platform itself already ;) |
| 18:21 | <Ms2ger`> | gsnedders, so I hear you're good at that :) |
| 18:22 | <gsnedders> | Ms2ger`: Don't believe *her*. She lies, or so I'm told. But there again, testing *is* the future… |
| 18:29 | <Hixie> | i love the copyright notice on http://dev.w3.org/2011/webrtc/editor/webrtc.html |
| 18:29 | <Hixie> | it's the most explicit statement of hypocrisy i've ever seen the w3c make |
| 18:30 | <Ms2ger`> | Wow, that must be quite a thing |
| 18:30 | Ms2ger` | checks |
| 18:30 | <Ms2ger`> | >.< |
| 18:30 | <Hixie> | (amusingly, all the changes i could find are actually edits that made the spec worse) |
| 18:31 | <Ms2ger`> | Following a long tradition of copyrighting junk, then |
| 18:32 | <AryehGregor> | karlcow, I'm not clear on who exactly has influence on the decision here, or who's going to make it, so I thought I'd reply to be on the safe side. How exactly will a decision get made, and who has a say here? Is there anyone in particular I have to convince or can ignore? |
| 18:33 | <AryehGregor> | Hixie, which widget where you pick people to share with? |
| 18:33 | <AryehGregor> | Hixie, and okay. |
| 18:34 | <Hixie> | when you do a post, the one where you pick the circles |
| 18:34 | <karlcow> | I'm trying to not focus on who but what are the requirements and then see what we can propose to achieve these requirements. |
| 18:36 | <karlcow> | liam could have had a real proposal by saying we need to identify keywords, code, etc. I do not think the grammar of HTML whatever version is a guarantee, but the documentation of classname on HTML is a lot more for the purpose of the spec is what is needed. At the same time it was never really required in the past. |
| 18:36 | <karlcow> | so it's why the argument is a bit MOOT |
| 18:37 | <karlcow> | too much talk, not enough how-do-we-do-it |
| 18:47 | <AryehGregor> | Hixie, which part is contenteditable? I don't see it. |
| 18:47 | <AryehGregor> | (too much div soup!) |
| 18:47 | <Hixie> | oh i don't know if it's actually implemented as contenteditable (though i can't see how else it could be sanely done) |
| 18:47 | <AryehGregor> | I don't see any part that looks editable. |
| 18:48 | <Hixie> | i just mean the concept of a control that contains both editable text or immutable "chips" |
| 18:48 | <Hixie> | let me get you a screenshot |
| 18:48 | <AryehGregor> | Which part of the text is editable? |
| 18:48 | <AryehGregor> | Oh, I see. |
| 18:48 | <AryehGregor> | Right. |
| 18:48 | <AryehGregor> | It's an input, actually. |
| 18:49 | <AryehGregor> | They somehow cleverly make it not look like one. |
| 18:49 | <AryehGregor> | But the non-editable stuff is actually not part of the editable area at all, it's just sitting next to it. |
| 18:49 | <AryehGregor> | Still, this is what <span contenteditable=false> is for, yea.h |
| 18:49 | <AryehGregor> | yeah. |
| 18:49 | <AryehGregor> | Although that's a huge PITA to spec/implement correctly, it adds corner cases to *everything*. |
| 18:50 | <Hixie> | crap gotta go. bbiab with screenshots. |
| 19:56 | <AryehGregor> | Hmm. When I customize my sync preferences in Chrome and hit OK, it waits for a long time with a little spinner thing. I wonder whether it's frozen or actually doing something. |
| 20:09 | <annevk> | Hixie, seems to be within their right |
| 20:12 | <AryehGregor> | Hixie, yeah, I don't see anything wrong with that copyright notice. |
| 20:12 | <AryehGregor> | They're reproducing the original notice and making the copyright status clear. |
| 20:48 | timeless | ponders |
| 20:49 | <timeless> | is there an easy way to find out which version of a document @w3 is the one for a given TR? |
| 20:49 | <timeless> | or LC or whatever |
| 20:50 | <Ms2ger`> | Mm? |
| 20:50 | <timeless> | http://dev.w3.org/cvsweb/2006/webapi/WebIDL/Overview.xml?r1=1.353;f=h#rev1.353 |
| 20:50 | <timeless> | i've decided to compare 1.339 to tip |
| 20:50 | <timeless> | but i'm not sure if that's the right choice |
| 20:51 | <Ms2ger`> | No way to do that in general, but 339 sounds right |
| 20:52 | <karlcow> | timeless: do you mean which revision number has been published into TR/ space? |
| 20:52 | <timeless> | karlcow: i'm pretty sure if i did, i wouldn't need to ask :) |
| 20:52 | <karlcow> | hey? |
| 20:53 | <timeless> | oh |
| 20:53 | <timeless> | yes, sorry, i misread your question |
| 20:53 | <karlcow> | :) |
| 20:53 | <timeless> | yes, that's what i'm trying to get |
| 20:53 | timeless | misread `mean` as `know` |
| 20:53 | timeless | has no idea how |
| 20:53 | <karlcow> | no idea if it's tracked, but that could be useful indeed for future version. |
| 20:54 | <karlcow> | there could be even a link of the diff between the tip and the published rev number |
| 20:56 | <timeless> | Ms2ger`: interface screwy { attribute DOMString getter; }; |
| 20:56 | <timeless> | there's no harm in that, right? |
| 20:57 | <Ms2ger`> | In what? |
| 20:57 | <timeless> | that attribute name |
| 20:57 | <jgraham> | Don't think so |
| 20:57 | <Ms2ger`> | You probably need _getter |
| 20:58 | timeless | will have to give it as input to the spec and see what comes out |
| 20:59 | <timeless> | btw, how was the earthquake (to whomever it may concern) |
| 20:59 | <nimbu> | it was a GOOD ONE |
| 20:59 | nimbu | lives on the west coast |
| 20:59 | <timeless> | nimbu: `the only good earthquake is one too far away from me to be noticed`? :) |
| 20:59 | <aho> | so, spilt your coffee? :) |
| 21:00 | <nimbu> | timeless: exactly |
| 21:01 | <timeless> | … |
| 21:01 | <timeless> | ... |
| 21:01 | timeless | ponders |
| 21:01 | <timeless> | Ms2ger / jgraham : ... / … |
| 21:02 | <timeless> | + <pre class='syntax'><i>return-type</i> <i>identifier</i>([<em>extended-attributes</em>] <i>type</i> <i>identifier</i>, [<em>extended-attributes</em>] <i>type</i> <i>identifier</i>, …);</pre> |
| 21:02 | <timeless> | + <pre class='syntax'><i>return-type</i> <i>identifier</i>(<i>type</i><em>...</em> <i>identifier</i>); |
| 21:02 | <timeless> | +<i>return-type</i> <i>identifier</i>(<i>type</i> <i>identifier</i>, <i>type</i><em>...</em> <i>identifier</i>);</pre> |
| 21:02 | timeless | ponders |
| 21:03 | <timeless> | i guess the last two lines are actually focused on the ellipsis |
| 21:03 | <jgraham> | I think I was wrong |
| 21:03 | <jgraham> | But I haven't quite proved it yet |
| 21:30 | <timeless> | oh |
| 21:30 | <timeless> | interface in {}; |
| 21:30 | <timeless> | is that likely to cause pain for people? :) |
| 21:31 | <timeless> | .. probably not, i guess |
| 21:45 | <dglazkov> | posted some stuff to read for y'all: http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0975.html |
| 21:47 | <timeless> | * { visibility: hidden; } code, .syntax { visibility: visible !important; } |
| 21:47 | <timeless> | is a good way to proofread stuff :) |
| 21:48 | <timeless> | code, code > *, .syntax, .syntax > * { visibility: visible !important; } |
| 21:48 | <timeless> | works better :( |
| 21:52 | <TabAtkins> | Hehe. |
| 21:56 | <timeless> | well, both proved what i needed, but the latter showed me more stuff to review :( |
| 21:56 | <timeless> | http://pastebin.mozilla.org/1308553 |
| 21:56 | <timeless> | TabAtkins: any guesses how i got that? |
| 21:57 | <TabAtkins> | A regex that looks for "an [aeiou]"? |
| 21:57 | <TabAtkins> | Or I guess the other way round. |
| 21:57 | <timeless> | `can i` |
| 21:58 | <timeless> | i did it the old fashioned way, for each (letter not in aeiou) find ` an {letter}` |
| 21:58 | <timeless> | (using firefox) |
| 21:58 | <TabAtkins> | Bah. Use a regex text editor. That would have been slightly easier. ^_^ |
| 21:58 | <TabAtkins> | /an [^aeiou]/ |
| 21:59 | <timeless> | TabAtkins: those fail on ` an <b>car</b>` |
| 21:59 | <TabAtkins> | Get one that understands HTML as well. |
| 21:59 | <TabAtkins> | (I don't know if one exists.) |
| 21:59 | timeless | chuckles |
| 21:59 | <timeless> | emacs might count |
| 21:59 | <timeless> | word probably does count |
| 21:59 | <timeless> | but one wouldn't typically call either a text editor |
| 21:59 | <timeless> | the former is an operating system |
| 21:59 | <timeless> | the latter is a word processor |
| 22:00 | <TabAtkins> | Alternately: copypasta from the browser to a text file, *then* search. Markup is lost. |
| 22:00 | timeless | nods |
| 22:01 | timeless | will actually ask Word what it thinks of the document |
| 22:01 | <timeless> | (word tends to do a good job of drawing green squiglies) |
| 22:03 | <Philip`> | /an (<[^>]*>)*[^b-df-hj-nptv-z]/ ? |
| 22:03 | <timeless> | Philip`: that fails `can i` :) |
| 22:03 | <Philip`> | /\ban (<[^>]*>)*[^b-df-hj-nptv-z]/ ? |
| 22:04 | <timeless> | that might work |
| 22:04 | timeless | thinks it's more trouble than it's worth |
| 22:05 | <timeless> | does that fail ` an <em><a>foo` ? |
| 22:05 | <timeless> | oh, you have another * there |
| 22:05 | <timeless> | it might fail ` an <em> <a> foo` :) |
| 22:05 | <Philip`> | Only weirdos would write markup like that :-p |
| 22:06 | <timeless> | also, that probably fails any case of <a foo="bar>fp"> |
| 22:06 | <timeless> | and yes, the author in question *does* use unencoded >'s |
| 22:07 | <TabAtkins> | Unencoded > is the best. Much eaiser to read. |
| 22:07 | <timeless> | s/eais/eas/ |
| 22:07 | <timeless> | s/eais/easi/ |
| 22:08 | <TabAtkins> | eaiesr |
| 22:08 | <timeless> | (it's hard to correct what i can't see..) |
| 22:08 | <Philip`> | /\ban (<[^>]*>)*(?!html|http|href|hgroup|rt|rp|li|xml|svg|hour)[b-df-hj-np-tv-z]/i |
| 22:09 | <Philip`> | That's less broken and has less false positives |
| 22:09 | <Philip`> | and finds a few errors in the HTML5 spec |
| 22:09 | <timeless> | <em>an ... |
| 22:09 | <timeless> | otoh |
| 22:09 | <timeless> | if it finds errors in the html5 spec, then it's a win! |
| 22:10 | <Philip`> | /\ban/ matches "<em>an" |
| 22:11 | <timeless> | yeah |
| 22:11 | <timeless> | but technically you don't want to |
| 22:11 | <timeless> | c<em>an |
| 22:11 | <timeless> | not sure when you'd hit that, but.. |
| 22:11 | <Philip`> | "<dt>An <code>hr</code> element</dt>" |
| 22:11 | <Philip`> | Only weirdos use markup in the middle of words :-p |
| 22:11 | <timeless> | wanna do a search in html5 for that? :) |
| 22:11 | <Hixie> | annevk, AryehGregor: nothing legally wrong with it. It's just hypocritical is all. |
| 22:13 | <timeless> | code, code > *, .syntax, .syntax > *, .idlstring, .esstring, .grammar { visibility: hidden !important; } * { visibility: default; } |
| 22:13 | <timeless> | do a search for `"` |
| 22:13 | <Philip`> | Lots of <var>index</var>th and <code>Document</code>s etc |
| 22:13 | <timeless> | :) |
| 22:13 | <Philip`> | but anyway, false positives don't hurt much :-) |
| 22:13 | timeless | is trying to decide if any of these `"`s should be tagged somehow |
| 22:14 | <timeless> | depends how long your document is :) |
| 22:14 | <timeless> | a colleague passed around a screen shot of a dialog from MS Word |
| 22:14 | <timeless> | the dialog was Word's "I give up, there are too many errors in this spec" |
| 22:14 | <Philip`> | HTML5 is pretty long, and my earlier regexp only finds 44 matches |
| 22:14 | <timeless> | one conclusion: spec isn't written by native speakers |
| 22:14 | <timeless> | alternate: spec is too long |
| 22:15 | <Hixie> | AryehGregor: do you have a mac? another example of contenteditable is the native date format editor (http://junkyard.damowmow.com/494) |
| 22:15 | <Philip`> | which was few enough that I gave up adding exceptions to the list |
| 22:15 | <timeless> | ok :) |
| 22:15 | <timeless> | Hixie: i remember that widget |
| 22:17 | <Philip`> | Hixie: Do you want bug reports of phrases like "an hostile" and "an platform array object" and "an global" and "an published" and "an JavaScript" and "an SYNTAX_ERROR"? |
| 22:17 | <Hixie> | sure |
| 22:17 | <Hixie> | one bug for all ideally |
| 22:17 | <Philip`> | and "an VideoTrackList" |
| 22:18 | <Hixie> | if you could just paste the actual markup in the bug that would be ideal |
| 22:18 | <Hixie> | so i can just search for that |
| 22:18 | <Hixie> | but if you don't have it that's fine |
| 22:18 | <timeless> | code, code > *, .syntax, .syntax > *, .idlstring, .idlvalue, .esstring, .grammar, .sym { visibility: hidden !important; } * { visibility: default; } |
| 22:18 | <timeless> | ended up working for my purposes |
| 22:18 | <Philip`> | I can paste the regexp :-) |
| 22:19 | <timeless> | heh |
| 22:19 | <Hixie> | if it's a regexp against the markup that would be perfect |
| 22:19 | <Hixie> | i can just stick it in my build script |
| 22:19 | <Hixie> | to catch future errors |
| 22:19 | <timeless> | woohoo, automation! |
| 22:20 | <Hixie> | anyone know if there's a way to renumber a screen in screen(1)? |
| 22:20 | <timeless> | http://brainscraps.wikidot.com/screnum |
| 22:20 | <timeless> | in short, `yes` |
| 22:21 | timeless | opts not to decode the code |
| 22:22 | <Hixie> | yeah that code is weird |
| 22:22 | <timeless> | regexps are much saner than shell |
| 22:22 | <Hixie> | seems to involve nested screen sessions |
| 22:22 | <timeless> | screen -l = list screens more or less iirc |
| 22:23 | <timeless> | screen -x = attach and share a screen session in case it's already attached (don't disconnect the currently attached clients) |
| 22:23 | <Hixie> | aha, ^A : number <n> |
| 22:23 | <timeless> | but yeah, it does do stuff in a screen session |
| 22:24 | <timeless> | i suspect that's to avoid damaging your console or something |
| 22:24 | <timeless> | or poisoning the session with your dimensions or who knows |
| 22:24 | <Hixie> | nice |
| 22:24 | <Hixie> | it works |
| 22:24 | <Hixie> | ^A :number 2 |
| 22:24 | <Hixie> | swaps the current window with window #2 |
| 22:25 | <hober> | nice |
| 22:26 | <timeless> | heycam: is there a rule you use for <foo attrib="bar"> v. <foo attrib='bar'> ? |
| 22:26 | <heycam> | timeless, in the source? no, just depends on my mood. |
| 22:26 | <timeless> | ok :) |
| 22:26 | <heycam> | most single quotes though I think? |
| 22:26 | <timeless> | i believe so |
| 22:27 | <heycam> | I would not accept a patch that made them consistent :) |
| 22:27 | <timeless> | i think you've reached the point where it wouldn't cost much to standardize on '' |
| 22:27 | <timeless> | not? |
| 22:27 | <timeless> | that's ok, i haven't sent patches anywhere in a while :) |
| 22:27 | <TabAtkins> | My rule is to use " when my hands are on home row, and ' when a hand is on the arrows and it would be inconvenient to hit shift. |
| 22:27 | <Philip`> | http://www.w3.org/Bugs/Public/show_bug.cgi?id=13879 - I think that's enough exceptions |
| 22:28 | Hixie | hopes that regexp is in a format grep accepts... |
| 22:28 | <Hixie> | let's see... |
| 22:28 | <timeless> | heh |
| 22:28 | <timeless> | w/ Hixie ?! ? |
| 22:28 | <Philip`> | 'ack' accepts it |
| 22:29 | <Philip`> | I expect anything non-Perl would be unhappy with (?!...) |
| 22:29 | <timeless> | grr, this irc client catches ctrl-tab as tab as tab-complete |
| 22:29 | <Philip`> | I suppose one problem is this doesn't cope with newlines after "an" |
| 22:30 | <timeless> | s/ /\s/; s!/i!/im! ? |
| 22:30 | <timeless> | or something like that, maybe sprinkle in a + and perhaps escape the backslash.. |
| 22:31 | <Philip`> | Then you need a grep-like tool that doesn't process line-by-line, but does print enough context for you to find each match |
| 22:32 | <timeless> | w/ perl you could print $. or something (there's a line accumulator floating around, i can't remember if that's it) |
| 22:32 | <timeless> | actually, that might not do the right thing |
| 22:32 | timeless | ponders |
| 22:32 | <timeless> | but yeah, it gets painful |
| 22:32 | <timeless> | you can capture (.{200}) before and after and print them :) |
| 22:33 | <Hixie> | can you see what's wrong with this other than the newline thing you mentioned?: |
| 22:33 | <Hixie> | perl -ne 'print "$.: $_" if /\ban(<[^>]*>)*(?!(http|https|href|hgroup|rt|rp|li|xml|svg|hour|hr|xhtml|xslt|xbl|nntp|m[ions]|mtext|merror|h[1-6]|xmlns|xpath|s|x|sgml|huang|srgb|rsa)\b|html)[b-df-hj-np-tv-z]/i' source | perl -lpe 'print "\nPossible article problems:" if $. == 1' |
| 22:33 | <Hixie> | i'm getting way too many false positives |
| 22:33 | <Hixie> | e.g. it matches:10: ! - element, attribute, content model, and interface indexes |
| 22:33 | <Philip`> | You need at least a space or a \s+ after the "an" |
| 22:33 | <Hixie> | oh oops |
| 22:33 | <Hixie> | copy pasta |
| 22:33 | <timeless> | yeah, blame your web browser :) |
| 22:33 | <Hixie> | that's better |
| 22:34 | <Hixie> | awesome |
| 22:34 | <Hixie> | thanks |
| 22:34 | <Hixie> | i added it to my build script |
| 22:35 | <Hixie> | will fix errors later, i'm in the middle of an edit |
| 22:35 | <timeless> | what does it say that i correctly remembered $. -- i don't use it, and haven't touched perl in months? |
| 22:35 | timeless | sighs |
| 22:35 | <Hixie> | i use $. quite often |
| 22:36 | <timeless> | i suspect the last time i did was on my text to html/atom script |
| 22:36 | <Hixie> | Philip`: if you figure out a way to make this work for multiline stuff while still being a short script let me know, i could use such magic in other efforts |
| 22:36 | <timeless> | which was probably a couple of years ago |
| 22:36 | <Philip`> | I'm assuming everyone pronounces HTML as "aitch tee em ell", not as "hotmeal" or similar |
| 22:36 | jgraham | is very suspicious of regexps to prase phonetics using the rule "all vowels plus some listed exceptions" |
| 22:36 | <timeless> | Hixie: are you on a memory constrained system? |
| 22:37 | <jgraham> | *parse |
| 22:37 | <timeless> | if not, you could go the mxr line counting approach |
| 22:37 | jgraham | assumes Hixie doesn't have an infinte amount of ticker tape |
| 22:37 | <timeless> | and capture your context and replace all line feeds up to it and then count that replacement |
| 22:37 | <Hixie> | timeless: yes, but more importantly i can write the script as a multiline one without help, i just can't work out a way to do a one-liner to do this :-) |
| 22:37 | <Hixie> | if i had infinite ram i'd just do the regexps against the whole file |
| 22:38 | <timeless> | i can imagine a way that cheats a bit |
| 22:38 | <timeless> | takes the file, and each time it encounters an<tags>{linebreak} it swaps the {linebreak} and an<tags> |
| 22:39 | <timeless> | and then applies the rule to that resulting stream |
| 22:39 | <Hixie> | there are many trivial ways to do it if you can write more than one line of code :-P |
| 22:39 | <Hixie> | the point is that this is currently a -ne perl one-liner |
| 22:40 | <timeless> | oh, you have access to variables in -ne |
| 22:40 | <timeless> | you can easily do: |
| 22:40 | <Philip`> | perl -le '@_=<>; for $i (0..$#_) { $_="$_[$i]$_[$i+1]"; print "$i: $_" if /\ban\s+etcetcetc/im }' source |
| 22:40 | <timeless> | $_ = $a.$_ if $a; $a = "an" if s/an$//; |
| 22:40 | <Philip`> | (Surely not the best way but it seems to work) |
| 22:41 | <timeless> | grr, don't forget to clear $a in that first if :) |
| 22:41 | <Hixie> | lordy |
| 22:41 | <Hixie> | you guys give perl a bad name :-P |
| 22:44 | <Philip`> | One of my variables had an alphanumeric name - it could have been worse |
| 22:44 | <timeless> | heh |
| 22:45 | <timeless> | > The following changes were made since the previous Windows cumulative time zone update: |
| 22:45 | <Philip`> | perl -le '@_=<>; for $i (0..$#_) { $_="$_[$i]$_[$i+1]"; print "$i: $_" if --$| and /\ban\s+etcetcetc/im }' source |
| 22:45 | <timeless> | > Turkey Standard Time: A new Windows time zone was created: Turkey Standard Time. The display name is "(UTC+2:00) Istanbul." The government of Turkey has decided to change the 2011 DST schedule. It will start on Monday March 28 instead of Sunday March 27. "Istanbul" was removed from the display name of the "(UTC+2:00) Athens, Bucharest, Istanbul" time zone. |
| 22:45 | <Philip`> | That'll stop it reporting each line twice |
| 22:46 | <Philip`> | Oh, but I suppose it'll break if 'an' is at the end of a second line, so ignore that |
| 22:46 | <timeless> | > Egypt Standard Time [Display Name "(UTC+2:00) Cairo"]: The government of Egypt has canceled daylight saving time. |
| 22:46 | timeless | chuckles |
| 22:47 | <timeless> | ooh, Newfoundland is -3:30 |
| 22:48 | <timeless> | i didn't know i could get a half hour time zone w/o leaving this hemisphere |
| 22:52 | <timeless> | oh |
| 22:52 | <timeless> | Philip`: ? |
| 22:52 | <timeless> | can you ensure that `an [ImplicitThis]` is properly handled? :) |
| 22:53 | <timeless> | (or is that too Web IDL specific?) |
| 22:58 | <timeless> | ok, i'm done reviewing the diff |
| 22:58 | <timeless> | there's a dancing in the dark movie tonight |
| 22:58 | timeless | should figure out dinner, probably skip dancing, |
| 23:03 | <timeless> | heycam: ? |
| 23:03 | <timeless> | http://dev.w3.org/2006/webapi/WebIDL/#idl-special-operations |
| 23:04 | <timeless> | Special operations are declared by using one or more special keywords keywords in an operation declaration. |
| 23:04 | <timeless> | MS Word objects to `keywords keywords` |
| 23:11 | <shepazu> | annevk: I don't understand matter's #ffs … any explanation? |
| 23:12 | <timeless> | awww |
| 23:12 | <timeless> | Word crashed |
| 23:12 | <timeless> | heycam: it's all your fault! |
| 23:13 | <timeless> | [4.2.20.3] |
| 23:20 | <TabAtkins> | shepazu: Do you not understand #ff at all, or just mattur's ones? |
| 23:20 | <TabAtkins> | shepazu: Oh wait, I see. Never mind. |
| 23:20 | <TabAtkins> | That's a "for fucks sake", I assume. |
| 23:21 | <TabAtkins> | So, I dunno. |
| 23:21 | <shepazu> | like, I would use that when I think someone said something extremely stupid |
| 23:21 | <shepazu> | so, maybe he thought my statement was really dumb… :) |
| 23:21 | <shepazu> | oh, well |
| 23:21 | <nimbu> | shepazu: no i think he sez DO IT ALREADY |
| 23:21 | <nimbu> | clearly annevk can explain himself |
| 23:22 | <nimbu> | #ffs |
| 23:22 | <shepazu> | yeah, I reckon that's one interpretation |
| 23:23 | shepazu | will probably get some tsk-tsks for saying that... |
| 23:25 | <heycam> | timeless, thanks fixed (locally) |
| 23:25 | astearns | just accidentally created a #ffs channel clicking on shepazu's comment above |
| 23:26 | <shepazu> | astearns, what a stupid mis take! #ffs |
| 23:26 | <shepazu> | see, that's how you use #ffs :) |
| 23:26 | <astearns> | it was blue, I had to click... |
| 23:49 | <mattur> | shepazu: I agree with your comment, and meant DO IT ALREADY |
| 23:49 | <shepazu> | mattur: ok |
| 23:50 | <shepazu> | mattur: to be fair, I don't think there's any great rush, it will happen eventually (I'd guess sooner rather than later) |
| 23:51 | <shepazu> | I can actually see both sides of the topic |
| 23:53 | <Hixie> | for registerProtocolHandler() and registerContentHandler(), can anyone think of any states the browser could be in beyond these?: |
| 23:53 | <Hixie> | http://junkyard.damowmow.com/495 |
| 23:59 | <mattur> | shepazu: sooner would be good :) |
| 23:59 | <shepazu> | mattur: agreed |