mirror of
https://github.com/lipis/flag-icons.git
synced 2026-04-26 09:25:50 +03:00
[GH-ISSUE #303] SVG Syntax for bo.svg and fj.svg causes problem when parsing it with Apache Batik #189
Labels
No labels
3rd-party
3rd-party
bug
code
documentation
enhancement
fixed-in-master
flag-request
help needed
missing-flag
missing-flag
pull-request
wrong-flag
wrong-flag
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/flag-icons#189
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cnsgithub on GitHub (Sep 21, 2016).
Original GitHub issue: https://github.com/lipis/flag-icons/issues/303
Hi, i don't know if i should post it here or at batik, but since it happens only with 2 files, maybe something with the svg syntax of those two files is wrong (or non-standard)
specified on the element - may be a problem of 'id'
As for 1. https://developer.mozilla.org/en-US/docs/Web/SVG/Element/use
The 2. has some strange tag: clip-path="url(#c)"
Kind regards
@lipis commented on GitHub (Sep 21, 2016):
Can you check if they are better now?!
@cnsgithub commented on GitHub (Sep 22, 2016):
The Bolivia flag still has the error (same xlink) but the Fiji flag passed.
@lipis commented on GitHub (Sep 22, 2016):
@cnsgithub that is very strange.. because there are no references to xlink or href or anything in those files:
@cnsgithub commented on GitHub (Sep 23, 2016):
probably <use tag requires xlink (see the mozilla link above) ?
@lipis commented on GitHub (Sep 27, 2016):
Well not sure what to do.. if you find a solution to the "problem" let us know.. until then it looks good from my side..
@cnsgithub commented on GitHub (Sep 27, 2016):
What i did to fix it: Removed those two tags completely. Didn't see a difference on the flag itself.
@hulufei commented on GitHub (Oct 28, 2016):
@lipis Can you publish 2.6.0 to npm please, seems the issue solved, but npm package haven't update, thx
@lipis commented on GitHub (Oct 31, 2016):
@hulufei Published 2.8.0 :)