<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - form exported as pdf does not embed all required fonts"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=50879#c40">Comment # 40</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - form exported as pdf does not embed all required fonts"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=50879">bug 50879</a>
from <span class="vcard"><a class="email" href="mailto:thb@libreoffice.org" title="Thorsten Behrens (CIB) <thb@libreoffice.org>"> <span class="fn">Thorsten Behrens (CIB)</span></a>
</span></b>
<pre>I wonder how much of this is a bug, vs. a user experience deficiency.
Technically, LibreOffice _could_ embed the entire font, for those that don't
prohibit that in the font flags (N.B. most Windows fonts do _not_ permit that).
The drawback is a significant increase in PDF size, especially for short 1-2
page forms (fonts with good unicode coverage are easily 2-10MB in size).
For fonts where LibreOffice cannot embed more than a subset, several options
come to mind:
* leave things as they are, and perhaps issue a warning during export
(suggesting users to pick one of the 12 standard PDF fonts)
* try to be smart & embed a subset that matches the language selected at the
text at hand
* always fallback to Helvetia (or something) for PDF forms</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>