Inkscape should do the auto-conversion to keep the artwork as it was (especially because the software can). The artwork or rendering shouldn't be broken. The users shouldn't be prompted with a dialog with jargon. I hope this type of blog-post will shake the mindset a bit, and make developers more serious about compatibility. Downgrading my local install to 0.91, blacklisting 0.92 SVG files on the renderfarm and advising all 40 translators to not update to 0.92 is a short-term fix and not a pleasant one.Ī graphical difference with Meld between a Inkscape 0.91 SVG on left, and a 0.92 on right. This version will hit all the GNU/Linux distros, Windows and Mac users will download this new version from the official website and problems with SVG files will hit Pepper&Carrot. So, first, let accept it: 0.92 is a released version. I hate when I have to admit that using open-source is actually a production handicap in this type of scenario. I don't want to lose all the previous revisions of SVG file on Pepper&Carrot either! And what if I even do it will Inkscape tell me I have to do it again with Inkscape 0.93? This type of development decision, relying on 'users must fix it themselves' must stop. I can't spend the rest of the month to convert over 10,000 files manually one by one and push them to Git.
So: "Set 'viewbox'" or "Scale elements" ? More work for the users Screenshot of the new dialog for all SVG before Inkscape 0.92. Read it, let me know if you can choose an option: Also, now a dialog box will pop-up when you open a previous Inkscape SVG to choose between two obscure choice.
On all the reports, an external Inkscape extension is suggested to fix your previous SVG files one by one. I found over 5 duplicates bug-reports ticket about it (even during the testing period) and nowhere can I read that this issue was considered as a serious, high-priority, release bug. I wasted hours to investigate how this type of major issue could land into a major release. 10,804 files! No answers or professional solutions The line-height breaks every speech-bubbles in 0.92 it affects hundreds of pages in 40 languages and also all previous revisions on git. How can I invest my time and that of my contributors on Pepper&Carrot if this type of thing happens with the tools I'm using? Should I be blamed as an artist for the tools I'm using? For. Should 10K artwork not be interpreted correctly anymore after an update? In short the new Inkscape 0.92 can't read SVG made with previous Inkscape versions without breaking them visually.įor a professional like me using Free/Libre Open-Sources Software, it means: if a client, a publisher, a contributor or a translator tries to open today one of the 10,804 available source SVG files on Pepper&Carrot with the new Inkscape 0.92, he'll get rendering issues with text and will blame my competences as a professional for either making bad work or using unreliable tools.
0 kommentar(er)
