https://bugs.documentfoundation.org/show_bug.cgi?id=158588

--- Comment #21 from Tomaz Vajngerl <[email protected]> ---
(In reply to Heiko Tietze from comment #19)
> That's my point.
> 
> Since the flag is set on the document, you should automatically store the
> used fonts in later editions if used. No need to plan ahead.

Well, this is not the only use case. What if I create a template document and
there is actually no real content, so most styles would be set as unused and
most fonts not embedded. I don't think we can assume the reason for embedding
the fonts is just so the shared document is only read or lightly edited. The
option that is less likely to cause issues is the one that should be the
default IMHO. Any other option should be made consciously by the user.

> Btw, what happens if I uncheck the option? Become fonts that were previously
> embedded purged? 

Well "save" action always creates a document from scratch so there is nothing
purged, so the fonts would just not be embedded. The document and fonts
currently open would still be there.

> If not, how about switching the whole functionality into a
> one-click interaction, some command that embeds the fonts (and another to
> remove) thinking of it as a final step in processing. And if someone else
> runs the same command again new fonts would be added, but only if manually
> initiated.

Font embedding is implemented in the filter - you have no idea which fonts have
previously been embedded and which fonts haven't.

Not sure what issue you want to solve with this..

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to