- From: Helder Magalhães <helder.magalhaes@gmail.com>
- Date: Sun, 7 Feb 2010 00:24:12 +0000
- To: Jeff Schiller <codedread@gmail.com>
- Cc: SVG IG List <public-svg-ig@w3.org>
Hi everyone, [...] > I'm really trying to get a sense as to how a review process can proceed, > ideally I'd like to give reviewers the possibility of making changes themselves > in the HTML doc and then sending a diff (patch) to the editor/owner (whoever that will > be). > > My CVS is a little rusty, but I did do a cvs diff and took a look at > what my changes show: > > Here's an example: [...diff snippet...] > As can be seen, for small paragraphs, it is quite easy to review in > plain text the suggested change. On the other hand for large > paragraphs (like the first one in my snipped diff), it is quite hard). To be honest, I never liked diff much: the format is pretty hard to parse visually, or maybe I'm just not used to. When I started to handle unified diff (diff -u), which is the format typically used in SVN-based repositories, I found that format much more user-friendly. Just my 2 cents... ;-) > Also, I believe the W3C must have some tools for splitting/combining > the document into multi-page/single-page documents. I'd like to offer > both for viewing (but have the source split into multiple chapters for > reviewing and editing). Yeah, I guess recall seeing such scripts in the specs. section. I'm not sure if we can use them, but breaking the book seems almost a requirement to start-up a successful reviewing process. I also recall Amaya has got a feature (make book [1]) which is pretty much what's intended. I'm just not sure if the editor will be able to handle the markup without messing it up or freaking out with the (currently) huge amount of content. Even if we don't use it, the idea [1] seems nice and can perhaps be used as inspiration...? > Thanks, > Jeff Cheers, Helder [1] http://www.w3.org/Amaya/User/doc/MakeBook.html#Assembling
Received on Sunday, 7 February 2010 00:25:04 UTC