On Sun, Dec 19, 2021 at 01:31:54PM +0900, Akira Yokosawa wrote:
> On Fri, 17 Dec 2021 09:23:15 -0800, Paul E. McKenney wrote:
> > On Fri, Dec 17, 2021 at 11:14:50PM +0900, Akira Yokosawa wrote:
> >> RCUspacetime.svg and RCUusecases.svg are not properly rendered
> >> in a browser.
> >>
> >> By reverse converting from properly-rendered PDF, we are lucky to
> >> obtain browser-compatible SVGs of these figures.
> >>
> >> Steps of reverse conversion (example for defer/RCUusecases.svg):
> >>
> >> 1. Generate a properly rendered PDF with fixsvgfonts.sh applied:
> >>
> >> make defer/RCUusecases.pdf
> >>
> >> 2. Confirm the PDF looks OK.
> >> 3. Export as plain-SVG from PDF (Inkscape >= 1.0):
> >>
> >> inkscape -l -o defer/RCUusecases.svg defer/RCUusecases.pdf
> >>
> >> ,or with Inkscape < 1.0:
> >>
> >> inkscape -l defer/RCUusecases.svg defer/RCUusecases.pdf
> >>
> >> 4. Confirm the plain-SVG looks OK in a browser.
> >> 5. Confirm that the plain-SVG can be edited by Inkscape.
> >>
> >> Note: Plain-SVG is a SVG format where Inkscape-specific attributes
> >> and UI settings are removed. It is meant for portability across
> >> different SVG editors.
> >>
> >> Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
> >
> > Queued and pushed, thank you!
> >
> >> ---
> >> Hi Paul,
> >>
> >> You might want to call this "Inkscape black magic!".
> >> But it works as far as these two figures are concerned.
> >>
> >> It's up to you whether or not taking this.
> >> At least this change reduces their sizes almost by half.
> >
> > Even better!
> >
> >> Note that simply saving a problematic SVG as a plain-SVG by
> >> Inkscape, exported SVG is still not compatible with browsers.
> >
> > Ouch!!!
> >
> >> As a matter of fact, texts in RCUusecases.svg at current master can
> >> not be edited in Inkscape 1.1.1 in my test even after upgrouping
> >> texts. For example, font size can not be changed.
> >>
> >> After the reverse conversion to plain-SVG, their font sizes become
> >> changeable.
> >
> > And editing is significantly less cranky, so thank you again!
>
> Well, changing font sizes might be possible, but the result is not
> what you would expect.
>
> When Inkscape imports PDF, texts are divided into words and
> each letter in a word has explicit x-position specified.
> All spaces are lost along the way.
>
> This means when you increase font size or change font style,
> position of each letter does not change, resulting in bad looking
> texts.
>
> So I'm beginning to think that this patch should be reverted
> despite the browser incompatibility.
>
> I'll see further for the way to make these SVGs both editable
> and browser compatible, maybe after the upcoming release of
> perfbook.
It looks fine as is, so agreed, browser compatibility is not at all
urgent. If someone gets annoyed by it in the short term, we can always
ask them for help, right? ;-)
> Sorry for making noise by proposing the crude approach of
> PDF -> SVG conversion.
Not a problem, no need to apologize! It does appear that inkscape
version compatibility is a bit more challenging than one might hope.
> List of commits to be reverted:
> 89115b70dc0f ("defer: Update RCUusecases.svg grouping")
> 305b778abcb8 ("defer: Simplify SVG files for compatibility with browsers")
Done!
What I did was to download the inkscape v1.1 .AppImage, mark it
executable, and place it in my bin directory.
Convenient! Though .AppImage files will of course turn into just as
ugly a security hole as the old self-extracting .EXE files. Can't have
everything! ;-)
And in theory, it is no safer to download an RPP or DEB and install
it than it is to download an executable...
Thanx, Paul
> Thanks, Akira
> --
> >
> > I adjusted grouping and fixed a pre-existing alignment issue.
> > The resulting .svg rendered fine in Chrome, so here is hoping!
> >
> > Thanx, Paul
> >
> >> Thanks, Akira
>
