DITAA SVG output & Fop

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

DITAA SVG output & Fop

metro
I am using asciidoctor-diagram and generate SVG output for a DITAA drawing.

The SVG rendering in Fop fails in 'createFontFace' and the the offending part of the SVG seems to be:
  <style type="text/css">@font-face {  font-family: sans-serif;}</style>
Removing this part makes Fop work.

Does anyone else see this problem?

Is there a way for asciidoctor-diagram to not define this style?

Thanks,

MT
--
Reply | Threaded
Open this post in threaded view
|

Re: DITAA SVG output & Fop

mojavelinux
Administrator
I'm pretty sure it is DITAA that's adding the <style> tag, not Asciidoctor Diagram. Asciidoctor Diagram merely delegates to DITAA. You could file an issue with asciidoctor-diagram to consider cleaning this tag if a certain compliance setting is set. Or you could see if DITAA would consider not emitting it.

It's really fop that's in the wrong here since technically that is a valid SVG.

Best Regards,

-Dan

On Sun, Jul 26, 2020 at 1:28 AM metro [via Asciidoctor :: Discussion] <[hidden email]> wrote:
I am using asciidoctor-diagram and generate SVG output for a DITAA drawing.

The SVG rendering in Fop fails in 'createFontFace' and the the offending part of the SVG seems to be:
  <style type="text/css">@font-face {  font-family: sans-serif;}</style>
Removing this part makes Fop work.

Does anyone else see this problem?

Is there a way for asciidoctor-diagram to not define this style?

Thanks,

MT
--


If you reply to this email, your message will be added to the discussion below:
https://discuss.asciidoctor.org/DITAA-SVG-output-Fop-tp8111.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML


--
Dan Allen (he, him, his) | @mojavelinux | https://twitter.com/mojavelinux