[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #62884] "-svgconvert" print option causes inco
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #62884] "-svgconvert" print option causes incorrectly colored Latex output |
Date: |
Fri, 12 Aug 2022 11:38:00 -0400 (EDT) |
Follow-up Comment #3, bug #62884 (project octave):
The documentation for the "-svgconvert" option to print says
'-svgconvert'
When using the '-painters' renderer, this enables a different
backend toolchain with enhanced characteristics:
Font handling:
For interpreters "none" and "tex", the actual font is
embedded in the output file which allows for printing
arbitrary characters and fonts in all vector formats.
Strings using the "latex" interpreter, are rendered using
path objects. This looks good but note that textual info
(font, characters...) are lost.
So, there are changes to strings which use the "latex" interpreter (conversion
to path objects) which might be influencing things.
I think the fastest workaround right now is to print to svg and then use
another program such as Inkscape or your own test.py to convert svg to pdf.
I added @Pantxo to the CC list for this report since he did the most to write
octave-svgconvert and maybe knows how to fix this quickly.
As a work
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62884>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/