-
Notifications
You must be signed in to change notification settings - Fork 15
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
Simple seqdiag generates invalid SVG XML #21
Comments
From Takeshi KOMIYA on 2012-04-18 02:02:31+00:00 Fix #21; add default fontpaths to debian/wheezy → <> |
From Takeshi KOMIYA on 2012-04-18 02:08:17+00:00 I added new paths to ipagp.ttf and more new truetype fonts (vl-gothic). If you have any more good ideas for detecting truetype fonts, suggest it for me :-) |
From Miguel García on 2017-06-11 08:30:55+00:00 This may be a problem within sphinxcontrib-seqdiag, because testing it with seqdiag only it doesn't happen. The test:
The result:
Anyways, validating it against https://validator.w3.org/check, it says there are two errors, attached as image. |
With
blockdiag_html_image_format = 'SVG'
, I added a simple seqdiag to my RST file:This generates the following invalid SVG XML:
Note the invalid SVG tag has two
xmlns
attributes, one of them invalid:xmlns="http://www.w3.org/2000/svg" xmlns="xmlns"
.This results in errors on the page and an SVG that doesn't display.
For various architectural reasons, PNG isn't an option for us, so this is blocking our ability to use seqdiag.
Versions:
Pygments==2.2.0
Sphinx==1.4.9
blockdiag==1.5.3
seqdiag==0.9.5
sphinxcontrib-seqdiag==0.8.5
sphinxcontrib-blockdiag==1.5.5
The text was updated successfully, but these errors were encountered: