-
Notifications
You must be signed in to change notification settings - Fork 699
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.
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
Remade diagrams #147
Remade diagrams #147
Conversation
I'm bringing this in from my `diagrams-test` branch.
From diagrams.net, I'd originally exported at 200% zoom, to roughly match the original jpgs. Looking at the markdown page, these seemed gigantic, essentially taking up a printed page. The new versions are exported at 100% zoom.
Oops, I brought the images but not the markdown from `diagrams-test` branch. Fixed.
Adding id attributes - e.g. `#fig-03-01` before figures.
To do: * some renaming to less terse, more greppable filenames (diagram, not u) * exporting PNG and SVG files * deleting redundant attempts
Skipping figure 17.7 for now - lost in browser crash?
Filling gaps: 6.1, 6.2, 16.2, 17.7
I'm willing to try going forward for this. We should test on multiple browser/OS combinations. Thank you for the effort. |
Note: Fig 17.5 still needs work. |
Re: 17.5 - Turning some images into markdown tables is still a WIP branch - see #136. It might have stalled. I realized I have a Raspberry Pi, with only the basic Ubuntu fonts installed. I'm going to skim the diagrams there. |
On the Linux machine, the diagrams are perfectly legible and in place. (Everything looks odd at 500% zoom.) 18.05 had inconsistent fonts, but in all, it looks good! |
I puttered around on draw.io / diagrams.net . I think they're an improvement, but perhaps not the final word. I included svg (vector) and png files.
The text in svg might be an issue - embedding fonts (which might be the default?) or turning the letters into lines and curves could fix that. Those would be a matter of re-exporting with different settings, after verifying the fix. I ... dunno. Maybe roll forward with this until it breaks somewhere?
Some background in #139 .