https://bugs.documentfoundation.org/show_bug.cgi?id=143095
--- Comment #25 from Eyal Rozenberg <[email protected]> --- (In reply to Callegar from comment #24) > I understand that there is disagreement on whether the issue can be > addressed, because even if there is a solution path, following it would > take a significant amount of resources Actually, it should really not be a big deal to solve this problem 90% of the way. A heuristic could be applied ex-post-facto, i.e. after import, to consider possible split-ups of phrases like "LiberationSerif" or "DavidCLMNormal"; to see whether any of them match an actual font family; and to prefer the split-up form if the original form is not a known font family. This could in principle get some cases wrong (maybe there are font families FooBold and Foo with a Bold variant for example) - but the errors will be minor relative to the majority of cases. A more fundamental solution may require a lot of work. > IMHO, providing the ability to read PDFs and convert them to an editable odg > format Don't forget the ODT format... > Currently, the biggest annoyances with PDF are: etc. etv. I think a "prioritizing list" of annoyances belongs on the tracker/meta-bug page of PDF import and export filters. I mean, I'm not saying you're wrong, or that this issue is the most important one regarding PDFs (it isn't); but - this is the page for a single issue, not for everything else, even if our discussion has veered off track :-) -- You are receiving this mail because: You are the assignee for the bug.
