<html><head></head><body>Hi all,<br>agreed fully. It will be good to cover for this directly if budget allows, otherwise we can seek additional funds.<br>Cheers.<br><br><div class="gmail_quote">On 15 August 2019 12:41:35 EEST, Marco Bernasocchi <marco@qgis.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi Nyall, <br><br>On 15.08.19 05:44, Nyall Dawson wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Before I send this -- would I be overstepping if I add a few optional<br>items of things we've identified as significant limitations in the Qt<br>SVG handling (which directly affect QGIS), but don't directly related<br>to existing bugs (because we can't expose the functionality which<br>relies on this)?<br></blockquote>please add them, it is good to know what kind of costs would be<br>involved. nobody says QGIS _has_ then to cover the costs, but we would<br>know wat it woud require do get the ball rolling (and we could tell that<br>to users).<br><br>><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> One concrete example would be Qt's lack of respect for svg/qpainter<br> fill/stroke order.<br><br> Nyall<br></blockquote><br>cheers<br>Marco<br></pre></blockquote></div><br>-- <br>Sorry for being short</body></html>