(1) Drag copy all the symbols you need from a single symbol libray file (2) Edit>Clone>Unlink Clone (3) Ungroup (4) File>Clean Up Document (5) Save file (6) Repeat this for each single symbol library file you need symbols from (7) *** At this point I suggest unsetting the fill and stroke of each object. This will allow you to change fill and stroke after they are converted to a symbol *** (Not necessary) (8) Convert the objects to symbols.
From there - you can simply drag copy the symbols from the current document or duplicate them.
It looks like a fix is being expedited, and might make it into v1.4.
In the meantime, I'd use the above workaround.
Keep in mind this needs to be done within each document that you are using symbols from existing/external libraries. Symbols you create within a document will be fine, but could be overwritten by symbols from external collections.
Tyler - I believe it will be in 1.4.1. Crossing fingers for 1.4
100% correct about the diagnostic.
I never came across this issue years ago when symbols were introduced because out of habit I always "unclone" them when bringing them in. Then bring more in from other files and unclone those.
Came agross this issue recently when I was trying to create a master catalog of my symbols (800+ now). After about the 3rd or 4th file I started having problems. Searched gitlab for a bug report. Sure enough there was a bug report.
Good news though (lol). I completly redid my entire library to take advantage of the unset fill and stroke feature. I didn't know symbols had that capability. That will make my workflow more efficient and "end" documents a lot smaller. Smaller because before I always "uncloned" them but never converted them back.
Once the bug is fixed, I will release my new kit.
Now if I can get the alpha sort back inside the symbol dialog. For some reason they removed alpha sort in the symbol dialog but kept it in document resourse symbol tab. (LOL)
I just noticed a few new things about "unset" symbols and symbols in general:
(1) Unset symbols that are drag/copied from the symbol dialog, you can change fill, stroke, and pattern. Even apply filters. However you will still have to "unclone" the copied symbol if you wish to use gradients. Correct me if I am wrong but isn't gradients considered a style? Hopefully future versions of Inkscape will allow gradients on drag/copied symbols without having to "unclone" it.
(2) Unset symbols of an open path will not show in the symbols dialog. Not sure if that is a bug or simply not an implemented feature yet. Hopefully future versions of Inkscape will allow this.
(3) If you copy/paste a symbol from one document to another - it is not longer a symbol. However, if you import a Inkscape document that has symbols into another document, the symbols are correctly imported. Not sure what to make of that.
1) It seems I can apply gradients to symbols dragged-in from the dialog.
2) Open paths can have a fill, so I expect you mean a path having only a stroke... Unset strokes typically do not display with any width, whether paths, clones or symbols; but stroke styles can be applied to symbols that have an unset stroke.
3) This is also expected behavior... copying a clone to another document unlinks the clone - it does not bring over the parent, so similarly a copied/pasted symbol will be unlinked. However, importing an SVG document also brings in the any used defs like gradients, markers and symbol parents.
I suppose there's an argument to be made that symbols should be able to be copy/pasted between documents like paths with gradients and/or markers, which also have associated defs.
Tyler "3) This is also expected behavior... copying a clone to another document unlinks the clone - it does not bring over the parent, so similarly a copied/pasted symbol will be unlinked. However, importing an SVG document also brings in the any used defs like gradients, markers and symbol parents." "I suppose there's an argument to be made that symbols should be able to be copy/pasted between documents like paths with gradients and/or markers, which also have associated defs. "
I was testing out you last comment and sure enough that is correct. When copying an object from one document with a mesh and/or filter into another document , it correctly copies it with mesh and/or filter. In the defs - for example it will give it an id of "filter7"
Copy it again and another def is created with "filter7-1". Copy it again and the def will have a random dash number.
What I am getting at - is that when copying symbols, it should be the same concept since a clone/symbol is actually defined in the defs element. The copied path will point to the def.
I am guessing that feature simply was not implemented for symbols yet. Symbols for Inkscape sort of came late to the ball game (v0.92 ???)
Beyond the Basics Symbol libraries - bug work around
Inkscape.org
Serious symbol bug issue in Inkscape. I suspect all versions that have symbol capabilities.
https://gitlab.com/inkscape/inkscape/-/issues/4781#
(1) Drag copy all the symbols you need from a single symbol libray file
(2) Edit>Clone>Unlink Clone
(3) Ungroup
(4) File>Clean Up Document
(5) Save file
(6) Repeat this for each single symbol library file you need symbols from
(7) *** At this point I suggest unsetting the fill and stroke of each object. This will allow you to change fill and stroke after they are converted to a symbol *** (Not necessary)
(8) Convert the objects to symbols.
From there - you can simply drag copy the symbols from the current document or duplicate them.
It looks like a fix is being expedited, and might make it into v1.4.
In the meantime, I'd use the above workaround.
Keep in mind this needs to be done within each document that you are using symbols from existing/external libraries. Symbols you create within a document will be fine, but could be overwritten by symbols from external collections.
Tyler - I believe it will be in 1.4.1. Crossing fingers for 1.4
100% correct about the diagnostic.
I never came across this issue years ago when symbols were introduced because out of habit I always "unclone" them when bringing them in. Then bring more in from other files and unclone those.
Came agross this issue recently when I was trying to create a master catalog of my symbols (800+ now). After about the 3rd or 4th file I started having problems. Searched gitlab for a bug report. Sure enough there was a bug report.
Good news though (lol). I completly redid my entire library to take advantage of the unset fill and stroke feature. I didn't know symbols had that capability. That will make my workflow more efficient and "end" documents a lot smaller. Smaller because before I always "uncloned" them but never converted them back.
Once the bug is fixed, I will release my new kit.
Now if I can get the alpha sort back inside the symbol dialog. For some reason they removed alpha sort in the symbol dialog but kept it in document resourse symbol tab. (LOL)
I just noticed a few new things about "unset" symbols and symbols in general:
(1) Unset symbols that are drag/copied from the symbol dialog, you can change fill, stroke, and pattern. Even apply filters. However you will still have to "unclone" the copied symbol if you wish to use gradients. Correct me if I am wrong but isn't gradients considered a style? Hopefully future versions of Inkscape will allow gradients on drag/copied symbols without having to "unclone" it.
(2) Unset symbols of an open path will not show in the symbols dialog. Not sure if that is a bug or simply not an implemented feature yet. Hopefully future versions of Inkscape will allow this.
(3) If you copy/paste a symbol from one document to another - it is not longer a symbol. However, if you import a Inkscape document that has symbols into another document, the symbols are correctly imported. Not sure what to make of that.
Hmmm....
1) It seems I can apply gradients to symbols dragged-in from the dialog.
2) Open paths can have a fill, so I expect you mean a path having only a stroke... Unset strokes typically do not display with any width, whether paths, clones or symbols; but stroke styles can be applied to symbols that have an unset stroke.
3) This is also expected behavior... copying a clone to another document unlinks the clone - it does not bring over the parent, so similarly a copied/pasted symbol will be unlinked. However, importing an SVG document also brings in the any used defs like gradients, markers and symbol parents.
I suppose there's an argument to be made that symbols should be able to be copy/pasted between documents like paths with gradients and/or markers, which also have associated defs.
(1) OMG - having a senile moment on gradients. When I was testing this - the gradient start/stop was set to black from previous use. LOL Ok - good!
(2) Yes - just unset stroked lines unfilled. A closed path with unset fill and stroke goes black. I was expecting the same logic with lines.
(3) Yes, I was expecting the same behavior. I did learn that importing is easier and solves the issue.
Wish I discovered the unset fill/stroke symbols feature 2 years ago. Helps to read documentation huh?
Tyler
"3) This is also expected behavior... copying a clone to another document unlinks the clone - it does not bring over the parent, so similarly a copied/pasted symbol will be unlinked. However, importing an SVG document also brings in the any used defs like gradients, markers and symbol parents."
"I suppose there's an argument to be made that symbols should be able to be copy/pasted between documents like paths with gradients and/or markers, which also have associated defs. "
I was testing out you last comment and sure enough that is correct. When copying an object from one document with a mesh and/or filter into another document , it correctly copies it with mesh and/or filter. In the defs - for example it will give it an id of "filter7"
Copy it again and another def is created with "filter7-1". Copy it again and the def will have a random dash number.
What I am getting at - is that when copying symbols, it should be the same concept since a clone/symbol is actually defined in the defs element. The copied path will point to the def.
I am guessing that feature simply was not implemented for symbols yet. Symbols for Inkscape sort of came late to the ball game (v0.92 ???)
Maybe one day?
Sounds like a good feature request...
Done