|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #56448] Backslashes in text objects break postscript export |
Date: | Thu, 6 Jun 2019 11:30:28 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko |
Update of bug #56448 (project octave): Status: None => Confirmed Operating System: Microsoft Windows => Any Summary: Back slashes in text objects break postscript export => Backslashes in text objects break postscript export _______________________________________________________ Follow-up Comment #1: Confirmed. A very simple example to reproduce is clf; ht = text (0.5, 0.5, "This is a backslash (\\)."); print -dpsc2 bslash.ps This is not specific to Windows; I reproduced it on Linux using the code above. The "interpreter" property is also a red herring as either "none" or "tex" have the same issue. I believe this is going to be a problem with the gl2ps library. We may be forced in Octave to work around it by filtering the output of gl2ps before we pass it to Ghostscript. As a workaround for now you can go through svg and pdf formats which do work. On a Linux machine which has the pdf2ps converter this sequence works print -svgconvert bslash.pdf system ("pdf2ps bslash.pdf") (file #47046) _______________________________________________________ Additional Item Attachment: File name: tst_bslash.m Size:0 KB <https://savannah.gnu.org/file/tst_bslash.m?file_id=47046> _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?56448> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |