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

--- Comment #5 from [email protected] <[email protected]> ---
(In reply to Dieter from comment #4)
> Thank you for further explanations. Please try to explain in some short
> steps. I try to rephrase your comment 2
> 
> 1. Make sure, that Font Awesome 6 Free Solid is installed
> 2. Open an document in LO 25.2
> 3. Open special character dialog (Omega icon in toolbar), insert the for
> external links
> 4. Save and close
> 5. Reopen in LO 25.8
> 
> Actual result
> Font of icon changed to Min Sans and therefore Icon changed to a cross
> 
> Expected result
> Same font and same icon as in LO 25.2
> 
> Are these steps correct? If not, please provide a correct set of steps.
> 
> I could only test with LO 25.8 and culdn't see a problem after saving and
> reopening

Hello, thanks for replying, you got it right, a document saved in LO 25.2 and
later re-opened in it displays the symbols from FA (Font Awesome) correctly in
the document, but when re-opened in 25.8 they're forced to show with the Min
Sans font, thus displaying as a cross inside a square like it's invalid.

Adding to that, the symbols seem to (primarily) break in links, which I'd like
to add also show broken in a table of contents too (they didn't break there
before), though for it, I'm using the symbols on only two headings on my
personal documents.

I have an example screenshot (of which I censored most of the headings' text
just to show the icons): https://ibb.co/wZVKq35j - this shows the icons
displaying on a PDF exported on LO 25.2, seen on Pale Moon's PDF.js add-on
where the navigation sidebar lists the headings and shows the icons in their
emoji equivalent (in these cases a thumbs up and thumbs down).

Meanwhile, the issue with the em dash seems to have been fixed, could be wrong,
but I feel like we can perhaps ignore it and focus on the icons, since it
displays with Linux Libertine G font now, at least on my current set-up.

A portable build might help so you can use LO 25.2 alongside 25.8.

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

Reply via email to