From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Thangalin <thangalin@gmail.com>
Subject: Re: SVG comments, transparency, and extended font styles
Date: Sat, 3 Apr 2021 20:25:31 +0200 [thread overview]
Message-ID: <d1630193-fa2c-f553-8185-aa0776033826@xs4all.nl> (raw)
In-Reply-To: <CAANrE7pdYLt2hE+OJNV2VzMcAA6KizaOyGHPTaNTmiK-bV-zbg@mail.gmail.com>
On 4/3/2021 8:10 PM, Thangalin wrote:
> Issues encountered with version 2021.03.31 18:04.
>
> 1. Comments in SVG
>
> % SOF
> \startbuffer[svg]
> <svg viewBox="0 0 100 100" xmlns="http://www.w3.org/2000/svg
> <http://www.w3.org/2000/svg>">
> <!-- Hello --><g><circle cx="50" cy="50" r="20"/></g></svg>
> \stopbuffer
>
> \starttext
> \placefigure{}{\includesvgbuffer[svg][conversion=mp]}
> \stoptext
> % EOF
>
> Expected: Black circle, no border, comment lines ignored.
> Actual: Empty square.
>
> 2. Transparent stroke
>
> % SOF
> \startbuffer[svg]
> <svg xmlns="http://www.w3.org/2000/svg <http://www.w3.org/2000/svg>"
> version="1.1">
> <polygon fill="#eeffff" stroke="transparent" points="500,10 500,0 0,0
> 0,10" />
> </svg>
> \stopbuffer
>
> \starttext
> \placefigure{}{\includesvgbuffer[svg][conversion=mp]}
> \stoptext
> % EOF
>
> Expected: Light cyan rectangle, no border (it's transparent).
> Actual: Light cyan rectangle with visible border.
i'll check it .. if I forget, remind me.
> 3. Inkscape font specification
>
> We discussed this previously: Inkscape extends the SVG specification
> with a custom style class ("-inkscape-font-specification") that allows
> its users to refine font styles.
>
> % SOF
> \startbuffer[svg]
> <svg xmlns="http://www.w3.org/2000/svg <http://www.w3.org/2000/svg>"
> viewBox="0 0 154.6 19.3" width="155" height="19"><text x="-6.7"
> y="-2.3"><tspan x="-1.9" y="15"
> style="-inkscape-font-specification:'Roboto,
> Ultra-Light';font-family:Roboto;font-size:20px;font-weight:200">Roboto
> Ultra-Light</tspan></text></svg>
> \stopbuffer
>
> \starttext
> \placefigure{}{\includesvgbuffer[svg][conversion=mp]}
> \stoptext
> % EOF
>
> Expected: "Roboto Ultra-Light" appears in Roboto Ultra-Light font.
> Actual: Empty square.
>
> Supporting this via MetaPost would help maintain backwards compatibility
> (with ConTeXt invoking Inkscape).
Hm, one should export the 'simple' SVG from inkscape, not the bloated
stuff. This is a bit like Adobe illustrator and its AI files: tons of
crap needed for an editor but not really an 'eps' file for which there
is a normal export. Once we decide to support all the weirdness there is
no end. It's like the browser css madness.
Now, with regards to remapping fonts, doing that at the tex end should
work ok (maybe some extra helper for svg to make it easier).
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-04-03 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 18:10 Thangalin
2021-04-03 18:25 ` Hans Hagen [this message]
2021-04-03 19:46 ` Thangalin
2021-04-03 21:15 ` Hans Hagen
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=d1630193-fa2c-f553-8185-aa0776033826@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=thangalin@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).