| 00:01 | <Hixie> | gsnedders: i don't suppose there's any chance of getting anolis 1.2 any time soon? :-) |
| 10:57 | <gsnedders> | Hixie: It would appear not |
| 10:57 | <gsnedders> | Hixie: I have a computing project to do in the next week, and an English dissertation to do in the next three |
| 12:25 | <gsnedders> | hsivonen: You around? |
| 14:11 | <gsnedders> | BibTeX doesn't map to ISO 690 nicely |
| 14:16 | <Philip`> | BibTeX is older than ISO 690, so blame ISO :-) |
| 14:16 | <gsnedders> | Peh. :P |
| 14:17 | <gsnedders> | BibTeX is also pretty near impossible to parse |
| 14:17 | <Philip`> | It's just a load of key/value pairs - how hard can it be? |
| 14:18 | <gsnedders> | @Preamble, the availability of LaTeX commands, the fact that complete parse errors just restart parsing at the next @… |
| 14:19 | <gsnedders> | Also @String adds some complexity |
| 21:30 | <ByRon21> | Hi All |
| 21:30 | <zcorpan_> | heycam: ByRon21 |
| 21:30 | <zcorpan_> | oops |
| 21:31 | <zcorpan_> | ByRon21: hey |
| 21:31 | <ByRon21> | :) |
| 21:31 | <ByRon21> | no problem |
| 21:31 | <ByRon21> | can we ask any question here |
| 21:31 | <zcorpan_> | sure |
| 21:31 | <ByRon21> | i am learning Something |
| 21:31 | <ByRon21> | And then i found myself here |
| 21:32 | <zcorpan_> | what was the Something? |
| 21:32 | <ByRon21> | Clickjacking |
| 21:32 | <zcorpan_> | ah |
| 21:32 | <ByRon21> | or Camjacking |
| 21:32 | <ByRon21> | Did u watch Jeremiah's Video? |
| 21:33 | <zcorpan_> | no |
| 21:33 | <ByRon21> | ok |
| 21:35 | <zcorpan_> | so what was your question? |
| 21:35 | <ByRon21> | For Example |
| 21:36 | <ByRon21> | i have One Swf |
| 21:36 | <ByRon21> | Mic.swf |
| 21:36 | <ByRon21> | it is asking To Enable Mic or not |
| 21:38 | <ByRon21> | if He click Enable How can it possible to record Sound? |
| 21:38 | <ByRon21> | is it possible |
| 22:24 | <zcorpan_> | Hixie: is it intentional to not mark up the whole of "must not" and "should not"? why are "required", "recommended" and "optional" not marked up? |
| 22:30 | zcorpan_ | disables font-variant in his user style sheet |
| 22:32 | <Hixie> | i was just experimenting with the style |
| 22:33 | <Hixie> | i'm not keeping it |
| 22:33 | <zcorpan_> | ok |
| 22:34 | <zcorpan_> | maybe the sentence regarding rfc2119 should comment out more keywords that are used in the spec but intended to be non-normative |
| 22:36 | <Hixie> | are any of them not used? |
| 22:37 | <Hixie> | other than shall? |
| 22:37 | <jcranmer> | zcorpan_: the reader MAY construe the following words to have unspecified meanings |
| 22:37 | <zcorpan_> | they are used, but don't seem to be intended as normative |
| 22:38 | <Hixie> | if they are used in inappropriate ways, please let me know |
| 22:38 | <Hixie> | they are intended to all be used per 2119 |
| 22:38 | <jcranmer> | RFC 2119 must be the most-cited RFC |
| 22:38 | <Hixie> | i should probably fix the use of optional a bit |
| 22:39 | <jcranmer> | sorry, RFC 2119 MUST be the most-cited RFC :-) |
| 22:39 | <Hixie> | but even optional seems correct to me |
| 22:40 | <zcorpan_> | Hixie: do you consider it a mistake if a keyword is used in a comment? |
| 22:40 | <zcorpan_> | er |
| 22:40 | <zcorpan_> | note |
| 22:42 | <annevk5> | it's a mistake |
| 22:42 | <annevk5> | notes are non-normative |
| 22:44 | <zcorpan_> | Hixie: i find it easier to follow requirements if only the keywords must, must not, should, should not and may are used, and the other keywords carry no normative weight... but maybe it's just me |
| 23:36 | <zcorpan_> | Hixie: added exception 23 |
| 23:36 | <Hixie> | thanks |
| 23:37 | <Hixie> | zcorpan_: yeah i should probably only use must/should/may. and yeah, in notes would be an error. |