From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: entity substitution
Date: Tue, 03 Apr 2018 16:38:59 +0200 [thread overview]
Message-ID: <5AC39203.7070101@gmail.com> (raw)
In-Reply-To: <49B56DF6-5715-4EE0-974F-3D8FB048C138@ziggo.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2038 bytes --]
ConTeXt has a list of predefined entities like & which can be used
without the use of \xmlsetentity.
Wolfgang
> dr. Hans van der Meer <mailto:havdmeer@ziggo.nl>
> 3. April 2018 um 16:22
> Does ConText always process DOCTYPE definitions? Because in the next
> example the defined XXX entity is substituted in one case but not in
> the other.
>
> In a directory I have the following files:
>
> doctype.tex =
> \startxmlsetups demo:setups
> \xmlsetsetup{#1}{root}{demo:*}
> \stopxmlsetups
> \xmlregistersetup{demo}{demo:setups}
> \startxmlsetups demo:root
> \xmlflush{#1}
> \stopxmlsetups
> \startbuffer[demo]
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE Entities [<!ENTITY XXX "My xxx definition">]>
> <root>
> See &XXX; for &XXX;.
> </root>
> \stopbuffer
> \starttext
> \xmlprocessbuffer{demo}{demo}{}
> \stoptext
>
> Produces as output a subtituted entity
>
>
> But
>
> doctype-public.tex =
> \startxmlsetups demo:setups
> \xmlsetsetup{#1}{root}{demo:*}
> \stopxmlsetups
> \xmlregistersetup{demo}{demo:setups}
> \startxmlsetups demo:root
> \xmlflush{#1}
> \stopxmlsetups
> \startbuffer[demo]
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE Entities PUBLIC "namen.dtd" "file://namen.dtd"><root>
> See &XXX; for &XXX;.
> </root>
> \stopbuffer
> \starttext
> \xmlprocessbuffer{demo}{demo}{}
> \stoptext
>
> namen.dtd =
> <!ENTITY XXX "This is my XXX definition">
>
> The last two do not output a substituted entity. /Why is this not
> working? What I am doing wrong?/
>
>
>
> dr. Hans van der Meer
>
>
> ___________________________________________________________________________________
> 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://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
[-- Attachment #1.2.1: Type: text/html, Size: 13026 bytes --]
[-- Attachment #1.2.2: image.jpg --]
[-- Type: image/jpeg, Size: 5245 bytes --]
[-- Attachment #1.2.3: image.jpg --]
[-- Type: image/jpeg, Size: 3350 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2018-04-03 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 14:22 dr. Hans van der Meer
2018-04-03 14:38 ` Wolfgang Schuster [this message]
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=5AC39203.7070101@gmail.com \
--to=schuster.wolfgang@gmail.com \
--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).