IMHO I'm experiencing the most weird behaviour for "{outfilesuffix}" …
I am using included files, which themself include other files (think of it as document configuration, setting standards, …).
e.g.
:myLink: some-relative-path/file.adoc
:myXref: pass:n[xref:{myLink}#myAnchor[my xref text]]
So … when I do such includes and preparing (pass:n) xref in one of the includes the generator plugin looses the knowledge of "{outfilesuffix}" when using the "{myXref}" in some top document (generates an anchor alike "file:///C:/data/file#myAnchor").
But … when I use something like "suffix: {outfilesuffix}" near top of page of an included file with attributes alike those above, the generator plugin keeps/gets back its knowledge of "{outfilesuffix}" when using the "{myXref}" in some top document (generates an anchor alike "file:///C:/data/file
.html#myAnchor" or ".pdf" if using PDF output).
Already tried ":getOutfilesuffix: {outfilesuffix}" to no avail … only a visible text "does the trick".
Please see also attached files
mwe-0.adoc and
mwe-1.adoc.
The included xref is at bottom of page mwe-0, the "outfilesuffix switch" on top of mwe-1 source.
Bug? Using it wrong? …?
Thanks and Regards
Peter