| 15:00 | gsnedders | wonders if he needs any other features for 1.0 of the spec-gen |
| 15:12 | <Lachy> | gsnedders, I already did add the mathml entities to that chart |
| 15:13 | gsnedders | claims blindness |
| 15:13 | <gsnedders> | Well, of course, you refer to the entities by their numbers. Duh. |
| 17:42 | <gsnedders> | String replacements are expensive. Really expensive. |
| 17:43 | <gsnedders> | When done on something the size of HTML 5, at least, looking at every text node, comment, PI, and attribute value in the document. |
| 17:48 | <Philip`> | Doing replacements on all those strings, or just doing matches on them all? |
| 17:49 | <gsnedders> | Well, doing basic string matches on them all, then if they match that doing a regex replacement |
| 17:52 | <gsnedders> | The subs are like half the time taken to process HTML 5 |
| 17:52 | <gsnedders> | They're a bit more expensive than xref |
| 17:52 | <gsnedders> | Basic advice: TOCs rule. They're cheap. |
| 20:31 | gsnedders | stabs lxml |
| 20:32 | <jgraham> | ? |
| 20:32 | <gsnedders> | Store text in a sane way! |
| 20:32 | <jgraham> | define sane |
| 20:33 | <gsnedders> | Not using the whole tail thing :_ |
| 20:33 | <gsnedders> | * :P |
| 20:34 | <jgraham> | define sane :) |
| 20:35 | <gsnedders> | Text nodes, like DOM are sae. |
| 20:35 | <gsnedders> | *sane |
| 20:35 | <jgraham> | No |
| 20:37 | <gsnedders> | They're saner than what lxml does, at lesat. |
| 20:37 | <gsnedders> | *least |
| 20:37 | gsnedders | can't type |
| 20:38 | <gsnedders> | XPath is nice too. |
| 20:38 | <gsnedders> | //text()[contains(normalize-space(translate(., 'AEILNORSTV', 'aeilnorstv')), 'latest version') or contains(., 'http://www.w3.org/TR/';)] |
| 20:50 | <Dashiva> | gsnedders: You already showed us that one :P |
| 20:50 | <gsnedders> | Dashiva: Shhh! |
| 21:51 | <gsnedders> | Conclusion of a friend of mine from school: "You're too crazy" |
| 21:51 | <gsnedders> | (where the second person refers to me) |
| 21:52 | <krijnh> | Mine mostly refers to 'me' :) |
| 21:54 | <gsnedders> | krijnh: Yes, but it didn't mean the conclusion referred to me, just that it was his conclusion |
| 23:08 | <jgraham> | gsnedders: To elaborate on my brief point earlier, text-as-nodes doesn't make for a nice api because they always get in the way when trying to do sensible tree navigation type things where you only really want elements, so you end up having to define a whole seperate API for tree navigation (ElementTraversal) |
| 23:09 | <jgraham> | But I guess you realised that was my point |
| 23:09 | <gsnedders> | jgraham: Yeah, they have obvious flaws, but I think in a lot of ways nicer. |
| 23:10 | <jgraham> | Well .text isn't too bad, it's the weird .tail thing in elementtree that sucks |
| 23:10 | <gsnedders> | yeah |
| 23:10 | <gsnedders> | But there's no way around that with the .text |
| 23:11 | <jgraham> | Not an obvious one at least |
| 23:27 | <jgraham> | Lachy: I think a character reference that told authors how to include any character, not just those with named references, would be nice, especially as there are problems using named references |
| 23:28 | <jgraham> | s/reference/pallete/ maybe |
| 23:28 | <webben> | could just link to ishida's converter |
| 23:28 | <webben> | http://rishida.net/scripts/uniview/conversion.php |
| 23:28 | <webben> | as step 1 |
| 23:30 | <Philip`> | There should be a thing where you can draw the shape you want using your mouse and it'll search for the matching character |
| 23:35 | <webben> | sounds like a use-case for a direct-drawing API ;) |
| 23:35 | <jgraham> | webben: That's way more complex than I had in mind. I basically want a way to search for characters with "alpha" in their name or description and get a glyph and an idea of how to include them in my html document |
| 23:36 | <jgraham> | Philip`: That would be awesome |
| 23:36 | <webben> | http://rishida.net/scripts/pickers/ worth a look too |