On 11/14/23, Michał Kruszewski via wrote:
> What is more, when the user types .PDFHREF, there is no warning or error.
It's longstanding roff practice to silently ignore undefined macro calls.
$ echo .TOTAL-GARBAGE-KJSFHUWER | groff
$
But you can enable warnings for this. As Deri suggests, you
On Tuesday, 14 November 2023 09:12:55 GMT Michał Kruszewski via wrote:
> There is one thing about PDF macros I struggle to understand, namely the
> case sensitivity.
>
> Example:
> .PDFPIC is uppercase
> .pdfhref is lowercase
>
> What is more, when the user types .PDFHREF, there is no warning or
> Can we create documents that have chapters, sections,
> that are in separate files? How can we do this?
Use the method you already described that works: source the files
directly from the main document, not from within a macro.
> Now if I run this main file using
> (cat main.tr | groff -p -
Hello,
Is it possible to move the .so command to a macro. For instance let's say I
have a macro
.de source
.so \\$1
..
and call it like so: .source complex1.roff.
It seems like the soelim is getting the .so in the source macro. If I put
the macro in the main complex.roff file it says that it ca
There is one thing about PDF macros I struggle to understand, namely the case
sensitivity.
Example:
.PDFPIC is uppercase
.pdfhref is lowercase
What is more, when the user types .PDFHREF, there is no warning or error.
The link is simply missing in the generated pdf output.
Why are some PDF macro
