/irc-logs / w3c / #html-wg / 2009-03-28 / end

Options:

  1. # Session Start: Sat Mar 28 00:00:00 2009
  2. # Session Ident: #html-wg
  3. # [00:00] <Dashiva> hypertext cg?
  4. # [00:05] * Quits: maddiin (mc@87.185.206.149) (Quit: maddiin)
  5. # [00:05] <anne> Dashiva, Hypertext Coordination Group
  6. # [00:07] <Dashiva> I heard about them. What do they actually do?
  7. # [00:12] <anne> Chairs and Team contacts of the WGs within the Interaction Domain have a bi-weekly private call on stuff.
  8. # [00:14] <Dashiva> So they're the guys in charge of making sure e.g. HTML and SVG get along?
  9. # [00:16] <Hixie> technically that group isn't actually in charge of anything, but the chairs are responsible for making sure their groups get along with other groups, so it is a meeting that includes the people in charge of that, yes
  10. # [00:17] <anne> They can also publish a so-called W3C Coordination Group Note, e.g. http://www.w3.org/TR/2006/NOTE-backplane-20061116/
  11. # [00:17] <pimpbot> Title: Rich Web Application Backplane (at www.w3.org)
  12. # [00:38] <shepazu> huh, dunno why HCG shouldn't be public... it's not like anything secret gets discussed, we just all give summaries of what's going on in the different WGs, talk about places where coordination should happen, or common goals like testing
  13. # [01:03] * Quits: Shunsuke (Shunsuke@219.94.192.74) (Client exited)
  14. # [01:08] * Quits: Sander (svl@86.87.68.167) (Quit: And back he spurred like a madman, shrieking a curse to the sky.)
  15. # [01:15] * Joins: Shunsuke (Shunsuke@219.94.192.74)
  16. # [02:16] * Quits: tH (Rob@77.86.107.105) (Quit: ChatZilla 0.9.84-rdmsoft [XULRunner 1.9.0.1/2008072406])
  17. # [08:43] * Joins: maddiin (mc@87.185.249.95)
  18. # [09:43] * Quits: gavin_ (gavin@99.226.207.11) (Ping timeout)
  19. # [09:44] * Joins: gavin_ (gavin@99.226.207.11)
  20. # [10:25] <jgraham> shepazu: You should ell that to the secret W3C cabal :)
  21. # [10:25] <jgraham> *tell
  22. # [11:10] * Joins: ROBOd (robod@89.122.216.38)
  23. # [11:54] * Quits: xover (xover@193.157.66.22) (Ping timeout)
  24. # [12:07] <anne> Reading http://esw.w3.org/topic/IETF_HTML5_Meeting_March_2009 again I wonder if anyone actually tested Atom clients. E.g. I have a hard time believing they'd implement NFC handling for non-Unicode encoded Atom feeds.
  25. # [12:07] <pimpbot> Title: IETF HTML5 Meeting March 2009 - ESW Wiki (at esw.w3.org)
  26. # [12:08] <anne> That is, if they normalize URLs per the IRI specification when the document encoding is not a Unicode encoding.
  27. # [12:09] <anne> I also wonder if they cannot cope with spaces and other characters not officially allowed.
  28. # [12:23] * Joins: Sander (svl@86.87.68.167)
  29. # [12:25] * Joins: myakura (myakura@122.29.116.63)
  30. # [12:34] * Joins: tH (Rob@77.86.107.105)
  31. # [12:41] <pimpbot> planet: Shrinking HTML5 some more <http://annevankesteren.nl/2009/03/more-shrinking-html5>
  32. # [13:08] * Joins: xover (xover@193.157.66.22)
  33. # [13:22] <gsnedders> What's a byte/encoding pair that converts to non-NFC Unicode?
  34. # [13:29] <anne> U+0041 U+0300 would be one I suppose
  35. # [13:30] <anne> U+00C0 is the same in NFC
  36. # [13:32] <anne> maybe U+0300 should be U+0340, I can't quite tell the difference :)
  37. # [13:33] <anne> simpler is U+0041 U+0308 vs U+00C4
  38. # [13:35] <gsnedders> anne: But you need something that converts to those two characters from another encoding
  39. # [13:36] <anne> gsnedders, character references
  40. # [13:36] <gsnedders> (Because this is for IRIs, and if it is stored as a Unicode encoding no normalization is done)
  41. # [13:36] <gsnedders> Hm, I guess that would work
  42. # [13:54] * Philip learns from http://twitter.com/diveintomark that identi.ca uses application/xhtml+xml
  43. # [13:54] <pimpbot> Title: Mark Pilgrim (diveintomark) on Twitter (at twitter.com)
  44. # [13:55] <Philip> hence http://identi.ca/search/people?q=%ef%bf%bf
  45. # [13:55] <pimpbot> Title: People search - Identi.ca (at identi.ca)
  46. # [13:55] <Philip> (Oddly they seem to serve text/html to Opera?)
  47. # [13:57] <anne> And to Firefox?
  48. # [13:58] <anne> Maybe it's just the backend?
  49. # [13:58] <anne> Or maybe just to WebKit then...
  50. # [13:58] <Philip> Oh
  51. # [13:59] <Philip> They serve application/xhtml+xml to Firefox 2, but text/html to firefox 3
  52. # [14:00] <anne> heh, and Firefox 3 is the one with incremental rendering for XHTML
  53. # [15:59] * Quits: tH (Rob@77.86.107.105) (Quit: ChatZilla 0.9.84-rdmsoft [XULRunner 1.9.0.1/2008072406])
  54. # [18:05] * Quits: shepazu (schepers@128.30.52.30) (Ping timeout)
  55. # [18:17] * Joins: shepazu (schepers@128.30.52.30)
  56. # [18:19] * Quits: shepazu (schepers@128.30.52.30) (Client exited)
  57. # [18:20] * Joins: shepazu (schepers@128.30.52.30)
  58. # [18:30] * Quits: shepazu (schepers@128.30.52.30) (Ping timeout)
  59. # [18:49] * Quits: myakura (myakura@122.29.116.63) (Quit: Leaving...)
  60. # [19:23] * Joins: shepazu (schepers@128.30.52.30)
  61. # [20:15] * Joins: tlr (tlr@128.30.52.30)
  62. # Session Close: Sun Mar 29 00:00:00 2009

The end :)