<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Ale, <br>
</p>
<p>thanks lot for this work.</p>
<p>If I understand correctly, the path to circumvent html
vectorisation through intermediate pdf might work but brings a
one-man library in the loop and a fragile dependency to the pdf
format. <br>
</p>
<p>Even if the previous experience let us pessimistic about the
possibility of a Qt's upstream work, I would explore this
possibility in any case.</p>
<p>Because Qt needs to know downstream projects need it. </p>
<p>Because fixing upstream is always more efficient. </p>
<p>Because it is not expensive to ask KDAB and ask Qt's project. <br>
</p>
<p>Because smart workarounds are fragile and in the end a
Velociraptor appears from the bushes and eats you alive. <br>
</p>
<p>Is there any other major blocker ? <br>
</p>
<p>Regards</p>
<p>Régis<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 12/12/2023 14:15, Alessandro Pasotti
via QGIS-PSC wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAL5Q672_P5PS2-12qJQX5oGTshpwzuZjFBo1f3tjMqkE7obQbA@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">Hi,
as you probably know during the developers meeting in s-Hertogenbosch
it was decided to allocate a budget for developers that wanted to
dedicate some time to remove the blockers that prevented QGIS to be
eventually migrated to QT6.
I volunteered to coordinate the effort and organized a few meetings to
track the advancement of the efforts.
The good news is that thanks to the efforts and the brilliant work of
the participants we now have made significant steps towards the goal.
Here are the last QT6 meeting minutes:
<a class="moz-txt-link-freetext" href="https://docs.google.com/document/d/1D9X3pMXJgB1pIs2sFX5O22-TJEmLYuA4ujYis7EGXpE">https://docs.google.com/document/d/1D9X3pMXJgB1pIs2sFX5O22-TJEmLYuA4ujYis7EGXpE</a>
Kind regards.
</pre>
</blockquote>
<div id="grammalecte_menu_main_button_shadow_host"
style="width: 0px; height: 0px;"></div>
</body>
</html>