https://bugs.documentfoundation.org/show_bug.cgi?id=96872
--- Comment #29 from V Stuart Foote <[email protected]> --- (In reply to Vincent Lefevre from comment #28) > There is the same issue with the unoconv converter, which uses the standard > LibreOffice API (in the Python language, with the Python-UNO bridge). > Assuming that the API doesn't provide the font substitution information, I'm > wondering whether a new bug is needed or this should be discussed in this > bug. This issue is just about UX of LibreOffice's UI feedback details on font substitution. While there are "plumbing" issues to be tackled for instrumenting needed font substitution details to be shown in the UI, here we are only covering the UI. Issues of providing those details via API support, i.e. support of LibreOffices internal CLI 'convert' command, or for external projects like "unoconv" or its replacement "unoserver"/"unoconvert"--should be filed as new BZ issues. -- You are receiving this mail because: You are the assignee for the bug.
