ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Andreas Schneider" <aksdb@gmx.de>
To: ntg-context@ntg.nl
Subject: Sanitize &quot; in XML/XHTML documents
Date: Tue, 2 Feb 2016 11:32:41 +0100	[thread overview]
Message-ID: <trinity-0ca165d5-93e0-49e2-81d7-c56386684e89-1454409161605@3capp-gmx-bs53> (raw)

Hi,

I hope I don't just overlook some plain obvious solution, but a longer search in the Wiki and the mailing list (and the context source) didn't come up with anything too useful ....

Anyway: is there any mechanism that I can use to "fix" quotations while typesetting XML documents?
Pandoc produces &quot;some text&quot;. In TeX I would usually use \quotation{some text} to have proper, language dependent quotes.

I tried to intercept &quot; using \xmltexentity{quot}{...} but apparently the internal replacement takes precedence here. Otherwise I would have tried to build some small state machine which remembers if it is currently inside a quotation of not.

My next try would be to somehow intercept the XML stream (or flush) using lua and replace " ... " inline. However that all seems quite hacky.

So, does ConTeXt currently offer anything I can piggyback to get quotations set properly? :-)

Best regards,
Andreas
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2016-02-02 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 10:32 Andreas Schneider [this message]
2016-02-02 11:14 ` Hans Hagen
2016-02-02 12:44   ` Andreas Schneider
2016-02-02 12:19 ` massifr
2016-02-02 12:49   ` Andreas Schneider

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=trinity-0ca165d5-93e0-49e2-81d7-c56386684e89-1454409161605@3capp-gmx-bs53 \
    --to=aksdb@gmx.de \
    --cc=ntg-context@ntg.nl \
    /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).