![]() In the file the flowPara has a font size of 48px: Inkscape 0.91 is incorrectly recalculating the line spacing for each 'flowPara' element inside the 'flowRoot'. So in this case, the line spacing should be 16px (12px * 1.25). The source of the problem you are having is that in 0.91 the 'line-height' property is set to a % value:Īccording to CSS, the line spacing for a % line-height value is calculated once and then applied to all inner elements (which don't have their own 'line-height' value). No problem if quick fix follows Now I need to know if it is something planned for 0.92.1 or downloaded one of your files. Mistakes and error in design can be done. No problem if quick fix follows Now I need to know if it is something planned for 0.92.1 or 0.92.2? Inkscape 0.92 is able detect old legacy files, why not 'not prompting' user and just apply the smartest converting solution to preserve the rendering accross 0.91 to 0.92 ? If the extension does it, why not doing it auto-magically by default? I can't spend the next week to convert over 10000 files manually. ![]() The dialog poping at startup in 0.92 and proposal of an external extension to fix SVG text file by file is not a solution. As I can't use 0.92 -for sure- on my production now, I'm forced to downgrade to 0.91 and I'll force all my collaborator to not use 0.92. I can't rely my professional tools with this type of choices. This is highly unprofessional for a major release, and it put my project, Pepper&Carrot, in an unsecure area. Should I be blamed as an artist for the tools I'm using? For using FLOSS? Should my artworks be not interpreted correctly after an update?. If a client tries to open my sources with 0.92 he'll be prompted with dialog proposing obscure choices, and will get rendering issue with texts anyway and will blame my competences as a designer, not the software. Problem: Inkscape 0.92 can't read them without affecting them visually. I'm rendering this 10K of SVGs with command-line. I have the responsability of 10804 SVG files created with Inkscape, prior or with 0.91, spread over 20 repositories, contributed by 40 translators. This webcomic is open-source and I use Inkscape for the speechbubbles, the translation system and the renderfarm. Hi, I have a webcomic called Pepper&Carrot. These steps also work for your test case when done manually (using the options on the text tool controls bar). ![]() Internally, the extension basically applies the same steps you likely read about based on the bug description (setting line height explicitly for all inner text elements, and setting it to 0 for the outer text, which defines the CSS "strut" value). In your test case, the outer style of the two text objects differs, and thus the result for the re-adjusted text on the left will still show a slight difference in the baseline spacing compared to the text on the right (the extension does not copy style properties from random other text objects it only shuffles the style properties per text object). The proposed extension (for 0.92.1) can help with many basic cases where multi-line text in legacy documents renders differently in Inkscape 0.92. 92#Known_ Issuesīug #1655483 “Inkscape 0.92 line space problem with text of Inkscape 0.91”īug #1655412 “Space between base lines misbehavior”īug #1652006 “Line spacing differs between 0.91 an 0.92b4”īug #1644299 “text and image not displaying in 0.92pre3”īug #1642133 “Inkscape shows text with ridiculously wide line spacing”īug #1617692 “Spacing Between Baselines Messed Up 0.92 15081”īug #1556400 “line height all equal in development version”īug #1652340 “Extension for 0.92.x to fix line spacing in legacy documents” Changes wrt line spacing in Inkscape 0.92 are described here:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |