Eliot
On 08.06.2025 07:35, Brian E Carpenter wrote:
I have to say that I completely disagree. This should be done, by the RPC, and hosted at authors.ietf.org. It should categorically not be in a policy document.Regards Brian Carpenter On 08-Jun-25 17:07, Eliot Lear wrote:I agree that we need something to demonstrate the dos and do nots, and some pointers to tools that can be used. I am not sure that needs to be in the RFC, but it certainly should be an informational reference. This is especially the case with SVG which has been quite difficult for authors to deliver into an RFC.Eliot On 07.06.2025 23:19, Rob Sayre wrote:Hi,Shouldn't the document have several example SVGs? I'm not opposed to this plan, but I found myself wondering how some extremely basic features would work in an RFC, especially given varying output formats. The document itself should demonstrate the variations.I even wondered about simple things like what the value of "viewBox" should be. But, if it's easy, we should probably drop in 5 or 10.thanks, Rob
OpenPGP_0x87B66B46D9D27A33.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- rswg mailing list -- [email protected] To unsubscribe send an email to [email protected]
