Glenn Linderman

For a 2 row 1 column layout, it is a bit disconcerting, and not at all helpful to have a vertical dotted line in the middle of the page. Having a horizontal dotted line showing where the fold could be would be far more helpful.

My booklet (intended for print distribution) has one URL in it, in plain text in the original PDF. IT seems that PDFBooklet detected the URL, converted it to a clickable link, but in the process wiped out some of the text of the link, and included some of the text on the next line as part of the link, and wiped out part of that line too. I didn't quickly find a way to turn off that behaviour. Because in included part of the next line, the link didn't even work when clicked, and of course, the presentation...

For a 2 row 1 column layout, it is a bit disconcerting, and not at all helpful to have a vertical dotted line in the middle of the page. Having a horizontal dotted line showing where the fold could be would be far more helpful.

Is there any way to drag-n-drop a file into the file picker? Or to past a complete path name into it? I have deep and wide directory structures, and navigating by scrolling to find a particular file takes lots of scrolls and clicks.

As requested per email (that must not have come via the ticket system), here is a command: expander3.py balderdash.txt And attached file. I had moved on from pyexpander as mentioned above, and thought that any Chinese character would reproduce the problem, but maybe it has to be the right one, or in the right context, but I still recalled which line I'd eventually tracked this down to, and was able to recreate it by pasting that line into the attached text file.

As requested per email (that must not have come via the ticket system), here is a command: expander3.py balderdash.txt And attached file. I had moved one from pyexpander as mentioned above, and thought that any Chinese character would reproduce the problem, but maybe it has to be the right one, or in the right context, but I still recalled which line I'd eventually tracked this down to, and was able to recreate it by pasting that line into the attached text file.

Well, due to the difficulty of finding bugs, because the reports don't tell which macro is failing (in all cases), and the unknown character encoding used that caused this problem, and the limitation of having to have balanced () within macro invocations, I decided to write my own. Trying to use yours gave me some good ideas, some from your documented features, and some from the undocumented issues I encountered and listed. I've got everything working now, so no need to fix this bug except for other...

stdout was redirected to a file. I'm just experimenting with pyexpander... it looks nice, but it was hard to determine where some errors occurred... I had to "bisect" search the file to discover where the problem was. I guess incremental development of macros is necessary so errors would be isolated to recent changes. But this one, while it points right to the error character, gives no clue as to how to fix it.