From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH -perfbook] defer: Retouch SVG files for browser compatibility (2nd attempt)
Date: Sat, 1 Jan 2022 08:48:34 +0900 [thread overview]
Message-ID: <6525231c-a11f-0085-4b28-bbcd8701ab3a@gmail.com> (raw)
In-Reply-To: <20211231173756.GG4109570@paulmck-ThinkPad-P17-Gen-1>
On Fri, 31 Dec 2021 09:37:56 -0800, Paul E. McKenney wrote:
> On Fri, Dec 31, 2021 at 11:29:21AM +0900, Akira Yokosawa wrote:
>> In <text> elements which are misplaced when viewed in a browser,
>> there are "transform" directives of the form:
>>
>> transform="scale(-1)"
>>
>> (indicating rotation of 180 degrees), and attributes of:
>>
>> writing-mode:tb-rl
>>
>> (top to bottom, right to left: Normally used in vertical text in
>> Asian languages. "lr-tb" is the normal choice in English.)
>>
>> By manually removing those transform directives and replacing
>> "tb-rl" with "lr-tb" by a text editor; then ungrouping, rotating,
>> and moving those text elements by Inkscape 1.1.1; browser-compatible
>> SVGs have been obtained.
>>
>> Regrouping of edited text elements have been done as a final stage.
>
> Looks good, thank you! Queued, and will push soon.
>
> I grouped the "Delete-Only List" box, which might well have been
> ungrouped to start with.
Ah, I missed that one.
> This also serves as a test of Inkskcape> v1.1 modifying a drawing produced by Inkscape v1.1.1. ;-)
Nice!
>
>> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
>> ---
>> Hi Paul,
>>
>> I've not figured out what operations corrupted those text elements in
>> RCUspacetime.svg.
>> So take this fix as a "happens to work" kind of thing.
>>
>> Do you have any clue as to why those text elements have 180 degree
>> rotation and vertical writing mode?
>
> My best guess is that in the process of copying old figures to make
> new figures, I took some 90-degree rotated text and rotated it back.
> That -should- result in zero-degree rotation, but if the two verions
> of Inkscape used different pivot point for rotation, it would not have
> been possible to simply cancel the rotations, at least without quite a
> bit more math than I would expect to be applied.
I'm still wondering where that "tb-rl" mode come from.
>
>> I guess you copied such a text element to RCUusecases.svg and edited
>> and copied it in Inkscape. So I suspect RCUusecases.svg was corrupted
>> from the very beginning.
>
> That is my guess.
>
>> After this update, you should be able to edit both SVGs by Inkscape
>> as you'd like, I suppose.
>
> Looks good at the moment, but I am curious as to what your version
> of Inkscape thinks. ;-)
Will see when you push your grouping.
>
> And Happy New Year!!!
Happy New Year!
Thanks, Akira
>
> Thanx, Paul
>
>> Thanks, Akira
>> --
>> defer/RCUspacetime.svg | 88 +++--
>> defer/RCUusecases.svg | 707 ++++++++++++++++++++---------------------
>> 2 files changed, 378 insertions(+), 417 deletions(-)
>>
[...]
prev parent reply other threads:[~2021-12-31 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 2:29 [PATCH -perfbook] defer: Retouch SVG files for browser compatibility (2nd attempt) Akira Yokosawa
2021-12-31 17:37 ` Paul E. McKenney
2021-12-31 23:48 ` Akira Yokosawa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6525231c-a11f-0085-4b28-bbcd8701ab3a@gmail.com \
--to=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.