I just realized that feature request should be posted here (not in a PS of a bug report). So here's again my feature request: please have MacTex produce PDF as output.
I do not think that PDF can be imported with a sufficient quality by LibO for texmaths right now.
Up to LibO 5.4 the PDF import filter used to insert PDF images was "translating" the PDF into LibO native format, but in the process many objects were getting misplaced and fonts were substituted.
Since 5.4, LibO uses pdfium for inserting PDF images. In principle, this renders PDF perfectly. However, there are still issues such as the mishandling of transparency.
However, as soon as this last minor nuisance with PDF import is fixed, I think that Wolfang's idea to provide also PDF (in addition to SVG and PNG) as a format for inserting the latex equations could be quite useful. Clearly, TeXMaths should allow PDF only from LibO 5.4.something on.
A great advantage would be saving the dvisvgm step and allowing more tex engines to be used (xelatex and lualatex).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think that the day when LibO has fully working PDF support via its pdfium filters, having TeXMaths support also PDF images in addition to PNG and SVG could have some advantages.
Doing Xelatex/Lualatex/Pdflatex -> PDF -> import PDF in LibO would skip one step wrt the current flow Latex -> DVI -> dvisvgm -> SVG -> import SVG in LibO. This could make TeXMaths faster (more so, because the PDF import via pdfium should itself be faster than the SVG import).
Managing PDF would allow working with those Latex engines that do not support (or do not support with full features) DVI. For instance, Xelatex or Lualatex enable unicode math and a much more flexible selection of fonts than the standard Latex engine, but only with PDF output.
However, the new PDF import filters in LibO 6.0.x are still too immature for anything like that. The PDF filters will probably be completed only in 6.1.x or 6.2.x.
Last edit: Sergio Callegari 2018-05-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do not think that PDF can be imported with a sufficient quality by LibO for texmaths right now.
Up to LibO 5.4 the PDF import filter used to insert PDF images was "translating" the PDF into LibO native format, but in the process many objects were getting misplaced and fonts were substituted.
Since 5.4, LibO uses pdfium for inserting PDF images. In principle, this renders PDF perfectly. However, there are still issues such as the mishandling of transparency.
However, as soon as this last minor nuisance with PDF import is fixed, I think that Wolfang's idea to provide also PDF (in addition to SVG and PNG) as a format for inserting the latex equations could be quite useful. Clearly, TeXMaths should allow PDF only from LibO 5.4.something on.
A great advantage would be saving the dvisvgm step and allowing more tex engines to be used (xelatex and lualatex).
I don't see the point of having a PDF output? Could you clarify your wish?
I think that the day when LibO has fully working PDF support via its pdfium filters, having TeXMaths support also PDF images in addition to PNG and SVG could have some advantages.
Doing Xelatex/Lualatex/Pdflatex -> PDF -> import PDF in LibO would skip one step wrt the current flow Latex -> DVI -> dvisvgm -> SVG -> import SVG in LibO. This could make TeXMaths faster (more so, because the PDF import via pdfium should itself be faster than the SVG import).
Managing PDF would allow working with those Latex engines that do not support (or do not support with full features) DVI. For instance, Xelatex or Lualatex enable unicode math and a much more flexible selection of fonts than the standard Latex engine, but only with PDF output.
However, the new PDF import filters in LibO 6.0.x are still too immature for anything like that. The PDF filters will probably be completed only in 6.1.x or 6.2.x.
Last edit: Sergio Callegari 2018-05-08
OK, I see. Thanks for the explanation. So, let's wait for the new pdfimport fllters...