Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Text output for Model 33 ASR teletypes #65

Open
cabo opened this issue Jul 7, 2023 · 2 comments
Open

Text output for Model 33 ASR teletypes #65

cabo opened this issue Jul 7, 2023 · 2 comments

Comments

@cabo
Copy link

cabo commented Jul 7, 2023

When writing RFCs, we are limited to 69 columns (72 columns in an emergency) for plaintext output (SVG for HTML and PDF are unrestricted).

I can easily squash 4 columns by removing the indentation for the diagram:

cri-reference:
    ╭──────────────────────────────────────>───────────────────────────────────────╮
    │                                                                              │
    │                               ╭─────────────────────>─────────────────────╮  │
    │                               │                                           │  │
    │                               │          ╭──────────────>──────────────╮  │  │
    │                               │          │                             │  │  │
    │                               │          │           ╭──────>───────╮  │  │  │
    │                               │          │           │              │  │  │  │
│├──╯──╮── scheme ── authority ──╭──╯── path ──╯── query ──╯── fragment ──╰──╰──╰──╰──┤│
       │                         │
       ╰──────── discard ────────╯

The ideal way to handle this would be to be able to give a column limit to rrtext/rrutf8 and let kgt figure it out...

A simple space-saving flag (e.g., remove spaces around scheme, authority..., making │├── and ──┤│ vertical) would already help.
@katef
Copy link
Owner

katef commented Jul 7, 2023

Aha. I actually want this feature for responsive HTML output too. It'd be the same mechanism; target a particular width (and in the case of HTML, render out for various widths and select between them with a media query).

I did some coding for this, I have WIP stuff that I haven't finished off and pushed upstream.

@cabo
Copy link
Author

cabo commented Jul 8, 2023

Looking forward to seeing some of this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cabo @katef