----- Original Message ----- From: "Peter Saint-Andre" <stpeter@xxxxxxxxxx> To: "Marc Petit-Huguenin" <petithug@xxxxxxx> Cc: "Yaron Sheffer" <yaronf.ietf@xxxxxxxxx>; <ietf@xxxxxxxx> Sent: Friday, May 03, 2013 12:13 AM > > On 5/2/13 4:03 PM, Marc Petit-Huguenin wrote: > > On 05/02/2013 02:40 PM, Yaron Sheffer wrote: > > An alternative would be to have the RFC-editor doing copyediting of > > I-Ds for a fee. Depending on the cost, I would use such service > > for my I-Ds. That would be good for everybody: I would spend less > > time trying to make my text legible and more making the protocol > > described in it better. And because the document would have been > > copy-edited by the same people that will publish the RFC, that's > > less work at the end. > > Instead of imposing even more work on the RFC Editor team, I suggest > that you find someone in the WG, in your company, in the IETF > community (etc.) to help with the language issues. I did this recently > with a document in one of the WGs where I'm active and it worked quite > well (especially if the document is under source control and you can > just send a patch). Ah, there's the rub. I have done this on a number of occasions for a variety of people and editing the text file of an I-D is almost trivial compared to then incorporating the amendments, some agreed, some debated, some rejected, into the XML, in doing so introducing the need for further amendments (problem generates change generates problem generates ... the cycle beloved of all software developers). We really do need a tool, the like of which I was using 40 years ago when writing code, that allows patches to be applied independently and temporarily to see what it then looks like and if agreed that it looks good, incorporating them permanently into the source (XML). Ideally such a tool would reverse engineer the amended text into XML patches as well - text is so much easier to work with than XML (or any other markup language). Tom Petch > Peter > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.19 (Darwin) > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBAgAGBQJRgvMHAAoJEOoGpJErxa2p1WkP/Ao11JgbfdPk1+r5psycC4yW > hc9qCTZeJEuXHHEG5mFLXyuEugkL1LKDjH7TAHql3o28iRYi1P+0LnR4l4Eg27u8 > Rfk8TrQ3pE0EHOiMhtX9b1G718iyQAR6bxjBJhR0Sc6f5Y2x4drqZQd4xwHggNCz > uKp58+mrEizUBM3V6+JtCJAQj/mOv3HVbbSij8yWWYvJzuOP1nJ+rqEaI/0lBct5 > rkWrefJogtxRHIrwALKmV+BYV99MyDzmm4kwZj+rDzqy/epq77FkqvZUms9EkLZW > HYLWE9RL/onV+XOLbjkSIvjqjCgKdaS1FpMH6zqYidNN491bLAQacyI0QS9d6dGw > 9AbDMf1uTxWcfWyB4LrwFFVyA8ZVCWO+1d5up+LSRgfGR/u0WhbyiaJqN0JKy10t > 0yJ30+4rwsYjtzsOWy1Zggn8bD4uXXdyjbw8X6Ze69A8ChBlIqticIf4mEd12qSO > E6k8SqtsoX17QmEU8oa7RwNaIbQ59txVju0NHEDlYreBKdHeRrki1SuK5+VrOJAg > yTqzNkpJskgwFukSfLBiX446c4luXkQ4XoSWT3NdkqxIq2ikpXh3WU2p0WgDTM+G > EreYmGTQXP9YV2Ieb+nMsj1pNbD0gB5a8CpXWLe859IIu2ga1uCcxo99LqPymNJB > hmkU2s1OJ2xuR1/d5Anx > =JEpp > -----END PGP SIGNATURE----- >