The attached file is the result of converting an original SVG, that uses the commercial "Cubiculum" font as text, into <path>'s. Obviously, the result is a file that's rather a lot bigger, so I decided to convert all individual letters into (0,0) based <path>'s and use <use> to reduce the size of the file. This works, but there are two issues:
1) For six letters, all of them the first on a line, it doesn't, the use of <use> results in garbage, and for that reason I've commented them out in the attached. The question is, why does it not work?
2) Why do I have to use "xlink:href"? All browsers (Palemoon, Firefox, and even IE) accept just "href", yet edit the SVG in an text editor, and delete the "xlink:"'s and Inkscape completely looses the text? Again, why?
Because xlink:href is correct for SVG 1.1 and href is not, browsers are cheating and pre-empting svg 2.0 hrefs. There's an issue for allowing Inkscape to support both. It's odd that this has only this year become a problem for users though.
Having looked at your clones, those two paths are messed up. Did you chop the original path up into bits? It's something to do with the starting node if that's the case. You can use Inkscape to break apart a path and Inkscape 1.0 will even turn Text to Path into a group of paths rather than a single path to make this easier.
The href/xlink:href is definitely something that needs attention, in fact this is the first time I'm encountering problems with them. All of my SVG's only use stand-alone "href", and what's more they were all created using an older version of Inkscape (pre 0.92.4) and I'm pretty sure that they worked there. For what it's worth, I've now tried some older ones, and they (now?) show the same problem, lots of parts are missing in Inkscape that show correctly in every browser. (But GIMP (2.8.22) also messes them up...)
...those two paths are messed up....
Which two? There are three first letters (all capitals, D, N, and S) that are all wrong.
I'll do another conversion of "Object to Path" with the original, and compare the resulting paths. All editing was done with Notepad++ and I would consider it very unlikely that I messed up three paths.
OK, I've now minified the SVG. It contains two copies of the path-ified text, one as-is, one using a <defs>'ed path shifted to (0,0). Second copy has manually shifted down 300(px), and the second, using the <use> again screws up. Now tell me that I've still something wrong, or that this is indeed (or seems to be) a bug.
Beginners' Questions Use of <use>
Inkscape.org
The attached file is the result of converting an original SVG, that uses the commercial "Cubiculum" font as text, into <path>'s. Obviously, the result is a file that's rather a lot bigger, so I decided to convert all individual letters into (0,0) based <path>'s and use <use> to reduce the size of the file. This works, but there are two issues:
1) For six letters, all of them the first on a line, it doesn't, the use of <use> results in garbage, and for that reason I've commented them out in the attached. The question is, why does it not work?
2) Why do I have to use "xlink:href"? All browsers (Palemoon, Firefox, and even IE) accept just "href", yet edit the SVG in an text editor, and delete the "xlink:"'s and Inkscape completely looses the text? Again, why?
Because xlink:href is correct for SVG 1.1 and href is not, browsers are cheating and pre-empting svg 2.0 hrefs. There's an issue for allowing Inkscape to support both. It's odd that this has only this year become a problem for users though.
Having looked at your clones, those two paths are messed up. Did you chop the original path up into bits? It's something to do with the starting node if that's the case. You can use Inkscape to break apart a path and Inkscape 1.0 will even turn Text to Path into a group of paths rather than a single path to make this easier.
The href/xlink:href is definitely something that needs attention, in fact this is the first time I'm encountering problems with them. All of my SVG's only use stand-alone "href", and what's more they were all created using an older version of Inkscape (pre 0.92.4) and I'm pretty sure that they worked there. For what it's worth, I've now tried some older ones, and they (now?) show the same problem, lots of parts are missing in Inkscape that show correctly in every browser. (But GIMP (2.8.22) also messes them up...)
Which two? There are three first letters (all capitals, D, N, and S) that are all wrong.
I'll do another conversion of "Object to Path" with the original, and compare the resulting paths. All editing was done with Notepad++ and I would consider it very unlikely that I messed up three paths.
OK, I've now minified the SVG. It contains two copies of the path-ified text, one as-is, one using a <defs>'ed path shifted to (0,0). Second copy has manually shifted down 300(px), and the second, using the <use> again screws up. Now tell me that I've still something wrong, or that this is indeed (or seems to be) a bug.