Hi Alanna, other RFC editors--

I just wanted to note that
https://github.com/ietf-tools/xml2rfc/pull/1261 has been merged into
xml2rfc's main branch, though it is not part of any formal release yet
(3.29.0 is the latest release, which does not yet include the patch in
question).

If a version of xml2rfc is released including this change, then the
transformation to all BOX DRAWING characters should be sufficient to
fix the misalignment problems we were seeing with the MIME tree
renderings in the PDF variant of RFC-to-be 9787.

I'll be sending you a message latter today following up about RFC-to-be
9788, which has *not* yet had the all-BOX-DRAWING change applied to it.

Again, if y'all think that is the right thing to do for 9788, i can
follow up with such a change there too.  Just let me know!

Regards,

     --dkg

On Wed 2025-07-02 15:30:27 -0700, Alanna Paloma wrote:
> Hi DKG,
>
> Apologies for the delay. Your suggestion to update xml2rfc is being actively 
> considered.
>
> Please hold off on updating the artwork in RFC-to-be 9788 until a decision 
> has been made.
>
> Thank you,
> RFC Editor/ap
>
>> On Jul 2, 2025, at 2:57 PM, Daniel Kahn Gillmor <d...@fifthhorseman.net> 
>> wrote:
>> 
>> On Fri 2025-06-27 22:19:31 -0400, Daniel Kahn Gillmor wrote:
>>> I propose replacing ↧ and ⇩ with symbols from the BOX DRAWINGS range
>>> instead.
>>> 
>>> The attached proposed XML file makes this substitution for the MIME tree
>>> diagrams.  It will still render as misaligned, however, as long as the
>>> fix [0] is not applied to xml2rfc.
>>> 
>>> If you think this is reasonable, let me know and i can try to make a
>>> comparable revision for RFC 9788.
>> 
>> So far i've only heard back from Bernie about this change to the
>> codepoints used in the "ascii-art" MIME diagrams (and he approves).
>> Doing the same work for RFC-to-be 9788 is more substantial (because of
>> all the test vectors) but i'm inclined to go ahead and do it anyway in
>> the hopes that there will be no objections.
>> 
>> If anyone is inclined to contest this change, please let me know so i
>> don't waste my time fixing up the other draft!
>> 
>> And, if the RFC editor approves, i encourage you to update the xml
>> published at https://www.rfc-editor.org/authors/rfc9787.xml too.
>> 
>> Thanks,
>> 
>>          --dkg
-- 
auth48archive mailing list -- auth48archive@rfc-editor.org
To unsubscribe send an email to auth48archive-le...@rfc-editor.org

Reply via email to