<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - qt5: exported PDf file misses embedded fonts with vcl=qt5" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125234#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - qt5: exported PDf file misses embedded fonts with vcl=qt5" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125234">bug 125234</a> from <a class="email" href="mailto:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> Jan-Marek Glogowski</a> <pre>So we talked about "this" on ESC today, and I'll just quote the minutes here: * Just a reminder regarding kde5 plugin in still (Jan-Marek) + the qt5 plugin is currently not using cairo and it’s font handling is not really existing. + if we keep kde5, should we switch qt5 to cairo too, so that people have the same “quality”? + we get bug reports for qt5, even if its never automatically selected, like <a class="bz_bug_link bz_status_NEW " title="NEW - qt5: exported PDf file misses embedded fonts with vcl=qt5" href="show_bug.cgi?id=125234">https://bugs.documentfoundation.org/show_bug.cgi?id=125234</a> + Is that considered a problem for anyone or “if it hurts, don’t do it” ? + what do you prefer ? (Michael) + not sure – user has to select it themselves (Jmux) + happy to get bug reports, but reply to bugs is not helpful. + if switch to cairo automatically – has same quality / fixes + if this comes to still – and people non-automatically select it + years ago Kendy made effort to switch VCL from inside the app (Heiko) + at beginning of coding process – not clear that’s there. + easy to switch from one to the other to cope with issues. + talking wrt. Still – but won’t happen here (Jmux) + any downside to qt5 + cairo ? (Xisco) + not sure if there is any downside (Jmux) + plus is that Qt5 would be usable for users. + any objections to using Cairo for Qt5 ? (Michael) + can we make it more obvious it’s experimental? (Thorsten) + not accommodating random users who did odd things they found on the net. + if there is a plan to improve that over time. + fine – how can we make this experimental ? (Jmux) + for help/about can write Qt5Experimental + had similar thing in the past for gtk3 (Miklos) + just ignore it unless its experimental. + i.e. bail out the vcl plug if not experimental mode is on officecfg::Office::Common::Misc::ExperimentalMode::get() + any objections to making it experimental ? => will make it experimental. So you'll still be able to use it, but have to enable experimental. If some LxQt person is interested in some auto-loading, this can be revised to my original suggestion. FWIW the gtk3_kde5 plugin is "now" also forcefully linked to KIO to prevent bug 124598, even if the library just uses the file picker through an external helper program (like Firefox does).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>