Need help getting path tags to not be invalid

[Excalibur Z]

I am currently working on trying to get a website I am working on to be checked by Nokogiri through html-proofer. However, when I run Nokogiri via html-proofer, whenever I have a path tag in the website I get the following error message "Tag path invalid". I am unsure if this is due to improper coding of the path tag or website, or a problem with Nokogiri.

I am using Jekyll for the website, and I have put it in a Github repository here: https://github.com/Infinite-Dango-Studios/Infinite-Dango-Studios.github.io . The website is online at the following url: https://infinite-dango-studios.github.io/

The path tags that I am using in the website are all found in the following files:

• https://github.com/Infinite-Dango-Studios/Infinite-Dango-Studios.github.io/blob/master/_includes/header.html
• https://github.com/Infinite-Dango-Studios/Infinite-Dango-Studios.github.io/blob/master/_includes/footer.html

I am trying to use the following command to compile the website with Jekyll and run it through html-proofer and Nokogiri:

jekyll build && htmlproof ./_site --check-favicon --verbose --check-html

Does anyone know what the issue is, and can anyone help me fix it?

[Mike Dalessio]

Hi,

Thanks for asking this question. Can you help us reproduce it, by providing working code? That would help someone see what you're seeing and perhaps be able to diagnose the issue.

--
You received this message because you are subscribed to the Google Groups "nokogiri-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nokogiri-tal...@googlegroups.com.
To post to this group, send email to nokogi...@googlegroups.com.
Visit this group at http://groups.google.com/group/nokogiri-talk.
For more options, visit https://groups.google.com/d/optout.

[Excalibur Zero]

I have posted a copy of the "_site" directory that was generated by Jekyll onto MediaFire here:

http://www.mediafire.com/download/019n72v0w4mrieq/_site.zip

[Excalibur Zero]

After doing a bit of testing I was able to stop the error message from occurring by instead using the path tags in svg image files, and then calling the svg files using img tags.