|
From: | Per Bothner |
Subject: | Re: unicode box-drawing characters |
Date: | Fri, 30 Sep 2016 09:34:14 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 |
On 09/29/2016 11:56 PM, Gavin Smith wrote:
On 28 September 2016 at 20:40, Per Bothner <address@hidden> wrote:For me pdf output has relatively low priority (and dvi output has zero priority), but it would be nice to have the correct output. I could use png images of the output but that is obviously less desirable (more hassle with lots of small image files, doesn't scale (zoom) as well, takes more space, and text can't be selected). Using @iftex to use an image only in the tex case, but that's even more of a hassle and management problem.I agree. Another idea is not to use the box-drawing characters for the sample output (I assume there is some option to Kawa not to use them).
The box-drawing characters is what makes for readable output of arrays - which is especially desirable in documentation. They are used by mc and work fine with emacs and every terminal emulator I've tried so far, As an experiment I tried by-passing tex entirely: texinfo -> docbook -> fo ->pdf The box-drawing characters make it through to the .fo file, but the fop processor (fo -> pdf) didn't find a font with the box characters, at least not with default options. Presumably fixable. There are also some styling flaws, presumably also fixable. I also tried the ebook-convert tool which is associated with the Calibre tool and project. It handled the box characters just fine, but there were other problems. I just found this earlier discussion: https://lists.gnu.org/archive/html/help-texinfo/2013-01/msg00001.html -- --Per Bothner address@hidden http://per.bothner.com/
[Prev in Thread] | Current Thread | [Next in Thread] |