https://bugs.documentfoundation.org/show_bug.cgi?id=160848
Bernard Moreton <bernard.more...@gmx.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Bernard Moreton <bernard.more...@gmx.co.uk> ---
Thank you, Julien.
On testing today, I get different results from yesterday - but then I was
calling my script yesterday from a 4GL application, which I'm not today.
The problem yesterday seemed to be lined to a redundant '}' at the end of the
rtf, following the RTF end-of-document closure. Taking that out seemed
yesterday to remove the unwanted output, consistently.
I'll simplify the LO call for convert-to, leaving out the --headless and
--outdir, which seemed necessary to have in some years ago, but which don't
seem to do anything significant for my purposes now; and instead of calling my
script, make three separate BASH calls from my 4GL app.
And all this to check on exactly how many lines a variable message will take up
on a document, so's to keep everything on a single page
(write the lines to a temporary RTF with the appropriate typeface and
formatting convert to PDF;
call pdftotext -layout -nopgbrk;
count the lines (wc -l);
then add the appropriate number of blank lines to the main document in the $GL
app, to get the layout correct).
What I do notice today in the course of testing is that if I remove the RTF
end-of-document closing brace (}), then "convert-to pdf" outputs "Error: source
file could not be loaded" - but returns an exit code of 0 !
--
You are receiving this mail because:
You are the assignee for the bug.
