From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ConTeXt users <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: extra lines in PDF annotations
Date: Mon, 13 Mar 2023 16:06:44 +0100 [thread overview]
Message-ID: <b370a7a2-6a00-8f24-6a46-3ef7ff60898d@gmx.es> (raw)
Dear list,
using current latest from 2023.03.10 12:18, I have this XML sample:
<pre>
<element/>
</pre>
And the following environment:
\setupinteraction[state=start]
\startxmlsetups xml:text
\xmlsetsetup{\xmldocument}
{pre}
{xml:copy:html}
\stopxmlsetups
\xmlregistersetup{xml:text}
\startxmlsetups xml:copy:html
\xmltobuffer{#1}{.}{text}
\comment[location=inmargin,buffer=text]{}
\attachment[method=hidden, name=attach.xml, buffer=text]
\null
\stopxmlsetups
If I save the XML file with Windows EOL chars (CR LF), I get extra blank
lines in the PDF annotation.
Everything is fine, if XML has Unix line endings (LF char).
Attachment contains the proper line ending in each case.
Could anyone confirm what appears to be a tricky issue?
Many thanks for your help,
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2023-03-13 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 15:06 Pablo Rodriguez via ntg-context [this message]
2023-03-13 15:22 ` Pablo Rodriguez via ntg-context
2023-03-13 21:32 ` Hans Hagen via ntg-context
2023-03-14 15:27 ` Pablo Rodriguez via ntg-context
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b370a7a2-6a00-8f24-6a46-3ef7ff60898d@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).