On Tue, Apr 22, 2025 at 1:15 PM Jean Mahoney <[email protected]> wrote:
> Hi Carsten, > > On 4/22/25 12:21 PM, Carsten Bormann wrote: > > On 2025-04-21, at 22:54, Jean Mahoney <[email protected]> > wrote: > >> > >> > >> o Once the authors have approved the copy edits, we convert > >> the file to RFCXML and make formatting updates. > > > > Hi Jean, > > > > Just out of curiosity: > > Why is “formatting updates” considered to be the realm of XML (while > content, understandably, is markdown)? > > (Maybe I don’t understand “formatting updates”.) > > [JM] This is based on feedback we have received from authors where they > want to see the content edited first in the markdown and then the > formatting (e.g., updates to list formats, table layouts) can happen in > the XML file. > > I think it would be helpful for the authors, though, for the RPC to make > the formatting updates in the markdown (e.g., changing a bulleted list > to a definition list) after the copy edits so that the authors can keep > their markdown aligned, then the RPC creates the RFCXML file at the end > of the process. FWIW, I would call this specific example a copy-edit, and argue that it should go in the first pass, and I definitely agree it should go in the markdown. Obviously, these lines are going to be a bit blurry, but I think if we can agree on the general concept, we'll be in a much better place. -Ekr There would still be a few formatting updates to make in > the RFCXML file: adding displayreference if needed, boilerplate updates, > etc. > > Best regards, > Jean > > > > > Grüße, Carsten > > > > _______________________________________________ > rfc-interest mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ rfc-interest mailing list -- [email protected] To unsubscribe send an email to [email protected]
