Using unicode for e.g. double struck letters would be really useful, but not obvious that it's allowed under the RFC 7997 rules.
", "time": "2023-07-25T22:09:19Z"}, {"author": "Phillip Hallam-Baker", "text": "Well people can try using mathematical symbols in specs but the current ietf tooling doesn't support it.
", "time": "2023-07-25T22:09:38Z"}, {"author": "Daniel Gillmor", "text": "The IETF tooling does indeed support it. It works in HTML and PDF.
", "time": "2023-07-25T22:11:14Z"}, {"author": "Daniel Gillmor", "text": "And, you can produce .txt formats that use unicode, encoded in UTF-8. We need to just accept it and do it.
", "time": "2023-07-25T22:11:50Z"}, {"author": "Thom Wiggers", "text": "(aside from notation etc, it would also be nice to those of us who do not have ASCII names)
", "time": "2023-07-25T22:12:35Z"}, {"author": "Jonathan Hoyland", "text": "Yeah, the .txt versions of things weirdly seem to work for names, but not for generic text in the document.
Math typesetting has its own issues. We need to go to that wg for this
", "time": "2023-07-25T22:12:41Z"}, {"author": "Daniel Gillmor", "text": "it also works for text in the document: https://www.ietf.org/archive/id/draft-ietf-lamps-e2e-mail-guidance-10.txt contains \u21a7 and \u21e9 and unicode BOX DRAWINGS with no problems.
", "time": "2023-07-25T22:13:26Z"}, {"author": "Jonathan Hoyland", "text": "Weird, I guess I need to update my local tools then?
", "time": "2023-07-25T22:13:58Z"}, {"author": "Daniel Gillmor", "text": "I agree that more complex math typesetting (the stuff you'd want to use TeX for) just won't work in .txt
", "time": "2023-07-25T22:14:06Z"}, {"author": "Phillip Hallam-Baker", "text": "The current tooling supports some unicode pages but not others and does not document what is supported. Thus one of my drafts says: As the Russian proverb goes: ???????, ?? ????????:
", "time": "2023-07-25T22:15:46Z"}, {"author": "Daniel Gillmor", "text": "@Phillip Hallam-Baker can you point me to the source for the draft in question? i'd like to be able to replicate the problem.
", "time": "2023-07-25T22:16:22Z"}, {"author": "Phillip Hallam-Baker", "text": "@dan https://www.ietf.org/archive/id/draft-hallambaker-mesh-architecture-19.html
", "time": "2023-07-25T22:17:12Z"}, {"author": "Phillip Hallam-Baker", "text": "just replace with xml...
", "time": "2023-07-25T22:17:19Z"}, {"author": "Phillip Hallam-Baker", "text": "Oh and they also damage the xml
", "time": "2023-07-25T22:18:52Z"}, {"author": "Jonathan Hoyland", "text": "@Phillip Hallam-Baker The PDF version of that looks broken too.
", "time": "2023-07-25T22:20:30Z"}, {"author": "Phillip Hallam-Baker", "text": "Now I remember getting the xml rejected.
", "time": "2023-07-25T22:22:19Z"}, {"author": "Phillip Hallam-Baker", "text": "The tooling might have changed after Henryk stoped being responsible
", "time": "2023-07-25T22:22:40Z"}, {"author": "Daniel Gillmor", "text": "speaking of \"trust, but verify\": https://datatracker.ietf.org/doc/draft-dkg-rfcediting-non-ascii-ietf-tooling/ it works fine.
", "time": "2023-07-25T22:23:00Z"}, {"author": "Phillip Hallam-Baker", "text": "Will check the original
", "time": "2023-07-25T22:23:01Z"}, {"author": "Kris Kwiatkowski", "text": "I'm happy to review LMS RFC also
", "time": "2023-07-25T22:29:02Z"}, {"author": "Kris Kwiatkowski", "text": "*draft...
", "time": "2023-07-25T22:29:30Z"}, {"author": "Phillip Hallam-Baker", "text": "OK, the draft now comes up with a warning if the
", "time": "2023-07-25T22:30:52Z"}, {"author": "Phillip Hallam-Baker", "text": "cyrilic is in
", "time": "2023-07-25T22:30:57Z"}, {"author": "Phillip Hallam-Baker", "text": "used to be an error
", "time": "2023-07-25T22:31:01Z"}, {"author": "Daniel Gillmor", "text": "good. it works, and the warning is just that people who don't understand UTF-8 won't be able to understand the text/plain form of the document. That is a fine warning to ignore, in 2023. So, no more FUD about how we can't use unicode, please! Just forge ahead.
", "time": "2023-07-25T22:32:16Z"}, {"author": "Daniel Gillmor", "text": "especially for documents whose target audience is other specification writers. If an author of a cutting-edge specification doesn't have tooling to read UTF-8, something is seriously wrong.
", "time": "2023-07-25T22:37:59Z"}, {"author": "Phillip Hallam-Baker", "text": "DKG, preaching to the choir there. I would happily kill the plaintext RFCs entirely
", "time": "2023-07-25T22:38:40Z"}, {"author": "Phillip Hallam-Baker", "text": "The plaintext versions of my drafts lack the diagrams.
", "time": "2023-07-25T22:39:37Z"}, {"author": "Daniel Gillmor", "text": "might want to look at the aasvg tooling that MT is maintaining.
", "time": "2023-07-25T22:40:28Z"}, {"author": "Daniel Gillmor", "text": "He's pretty open to suggestions if you have a use case that isn't well-supported.
", "time": "2023-07-25T22:40:50Z"}, {"author": "Phillip Hallam-Baker", "text": "I am waiting to see what the RFC Interest group decides on SVG before changing.
", "time": "2023-07-25T22:41:30Z"}, {"author": "Phillip Hallam-Baker", "text": "Using GOATIFY right now
", "time": "2023-07-25T22:41:51Z"}, {"author": "Nicola Tuveri", "text": "Phillip Hallam-Baker said:
\n\n\nUsing GOATIFY right now
\n
can you point to a URL for GOATIFY?
", "time": "2023-07-25T22:44:55Z"}, {"author": "Martin Thomson", "text": "aasvg is what I recommend to people (not because I built it): https://github.com/martinthomson/aasvg (which I see that dkg already mentioned)
", "time": "2023-07-25T22:45:46Z"}, {"author": "Phillip Hallam-Baker", "text": "@nicola https://github.com/bep/goat
", "time": "2023-07-25T22:46:16Z"}, {"author": "Phillip Hallam-Baker", "text": "But I have some edits to pass the stupid RFC restrictions
", "time": "2023-07-25T22:46:34Z"}, {"author": "Phillip Hallam-Baker", "text": "I will check out Martin's because I had to make some changes to the GOAT output
", "time": "2023-07-25T22:47:55Z"}, {"author": "Nicola Tuveri", "text": "Do you have suggestions on tooling to author new ASCII diagrams?
", "time": "2023-07-25T22:49:07Z"}, {"author": "Randy Bush", "text": "protocol
\nand, on mac, MonoDraw
if you don't mind using a webapp, https://asciiflow.com/ isn't bad (you can also run it locally)
", "time": "2023-07-25T22:49:59Z"}, {"author": "Daniel Gillmor", "text": "(developed at https://github.com/lewish/asciiflow )
", "time": "2023-07-25T22:50:17Z"}, {"author": "Nicola Tuveri", "text": "Randy Bush said:
\n\n\n\n
protocol
\nand, on mac, MonoDraw
A URL for protocol?
https://github.com/luismartingarcia/protocol
", "time": "2023-07-25T22:51:35Z"}, {"author": "Daniel Gillmor", "text": "it's only good for a very specific subset of diagrams
", "time": "2023-07-25T22:52:03Z"}, {"author": "Randy Bush", "text": "packet porn
", "time": "2023-07-25T22:52:15Z"}, {"author": "Daniel Gillmor", "text": "@Nicola Tuveri see also https://textik.com/ (https://github.com/astashov/tixi)
", "time": "2023-07-25T22:56:11Z"}, {"author": "Phillip Hallam-Baker", "text": "@Nicola, like an intern?
", "time": "2023-07-25T23:02:28Z"}, {"author": "Martin Thomson", "text": "(deleted)
", "time": "2023-07-25T23:09:12Z"}, {"author": "Phillip Hallam-Baker", "text": "@Martin, are you arguing against gratuitous use of cryptography?
", "time": "2023-07-25T23:13:01Z"}, {"author": "Martin Thomson", "text": "@Phillip Hallam-Baker that too :)
", "time": "2023-07-25T23:14:19Z"}, {"author": "Phillip Hallam-Baker", "text": "@martin, spoilsport
", "time": "2023-07-25T23:14:42Z"}, {"author": "Frank Denis", "text": "I'm here for AEGIS !
", "time": "2023-07-25T23:27:27Z"}]