- From: Michael Cooper <cooper@w3.org>
- Date: Tue, 26 Feb 2013 09:35:56 -0500
- To: Robin Berjon <robin@w3.org>
- CC: Karl Dubost <karl@la-grange.net>, "spec-prod@w3.org" <spec-prod@w3.org>
- Message-ID: <512CC84C.9020005@w3.org>
Robin Berjon wrote: > For (1) there's Michael's objection that he likes to post-edit in an > XML editor. I'd love to hear about what kind of post-editing we're > talking about because the point is sort of that there shouldn't be any ;) There can be any number of reasons to need to post-edit the result of automatic generation. A couple that I've had to deal with recently on a repeated basis: 1. Respec outputs some weird attributes like 0="" which cause the document not to validate and that weren't present in the source document, so I have to remove those. 2. Respec puts a paragraph with public comment instructions in the Status section that is not compatible with our process. I always have to remove that; the correct instructions are in the custom paragraphs I add to the status. 3. There are times I prefer to tweak aspects of the output like the heading number format, or sometimes the TOC should go to a deeper level for some sections than others (in particular, appendices usually don't need the depth in the TOC that mainline sections do). I don't expect it will be possible to predict and provide configuration options for every scenario like this. We should just always expect there there might be a need to edit the output. Michael -- Michael Cooper Web Accessibility Specialist World Wide Web Consortium, Web Accessibility Initiative E-mail cooper@w3.org <mailto:cooper@w3.org> Information Page <http://www.w3.org/People/cooper/>
Received on Tuesday, 26 February 2013 14:39:11 UTC