<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:adam.m.fontenot+docfo@gmail.com" title="adam.m.fontenot+docfo@gmail.com">adam.m.fontenot+docfo@gmail.com</a>
</span> changed
<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Enabling pair kerning breaks rendering of many common fonts"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=142940">bug 142940</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>WONTFIX
</td>
<td>---
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>RESOLVED
</td>
<td>REOPENED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Enabling pair kerning breaks rendering of many common fonts"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=142940#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Enabling pair kerning breaks rendering of many common fonts"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=142940">bug 142940</a>
from <span class="vcard"><a class="email" href="mailto:adam.m.fontenot+docfo@gmail.com" title="adam.m.fontenot+docfo@gmail.com">adam.m.fontenot+docfo@gmail.com</a>
</span></b>
<pre>(In reply to László Németh from <a href="show_bug.cgi?id=142940#c9">comment #9</a>)
<span class="quote">> Pair kerning is for high quality typesetting. It's a de facto standard in
> document editing, not only in desktop publishing.</span >
Thanks for your comment. I was surprised to see a commit reverting this so
quickly and in fact I was going to raise the issue of rendering to PDF myself.
Indeed, I'm worried that a naive solution that simply changes the default would
break high quality PDF rendering. (This hadn't yet occurred to me when I made
the suggestion.)
<span class="quote">> As a workaround for the reported problem, enable "View PDF after export", so
> clicking on the PDF export icon, you can see the result with subpixel-based
> rendering, too.</span >
Yes, this is exactly the workaround I've been using when writing anything in
LibreOffice for years now. Write a few paragraphs without proofreading them,
export to PDF, then read back the PDF. That's the only way to avoid a miserable
experience trying to edit/read a document in LibreOffice at the moment.
Although I'm sure you're aware of this, I want to be clear that the status quo
is very bad. A huge number of LibreOffice users have complained about its font
rendering over the last few years, and so I was surprised to learn that there's
seemingly no active effort to fix the complete lack of subpixel positioning for
glyphs in the editor.
---
As I said above, I do agree that simply disabling the pair kerning default
isn't acceptable because of high quality printing and PDF output. But I still
don't think this should be a WONTFIX - there's another alternative. Leave pair
kerning enabled but only apply the setting to output that actually *can* be
meaningfully kerned - i.e. only the contexts which support accurate subpixel
positioning.
So you will continue to get the high quality desktop publishing output, while
the LibreOffice editor component which handles font rendering will silently
ignore the setting when rendering text (for example, in the Writer window).
Alternatively, I request that a separate setting be added to disable pair
kerning *only* in the editor components while leaving it enabled for desktop
publishing cases.
I'd also point out that if casual users discover that having pair kerning
enabled makes their documents look worse, they will simply disable it, heavily
reducing the quality of their published documents. Writer is a WYSIWYG editor
after all!
---
I'm reopening the bug so that the proposal above can be discussed. I apologize
if reopening a closed bug is against etiquette on this issue tracker - this is
my first issue opened here.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>