ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: TeX in \xmlsetentity and DTDs in DOCTYPEs
Date: Mon, 18 Jan 2016 22:19:29 +0100	[thread overview]
Message-ID: <569D56E1.2010101@wxs.nl> (raw)
In-Reply-To: <CAA36g0WBp1_zA=1iUFfqYoprT4mePXM8SdJGdA3yX=9hbfvAPw@mail.gmail.com>

On 1/18/2016 9:56 PM, Kate F wrote:
> On 18 January 2016 at 20:07, Hans Hagen <pragma@wxs.nl> wrote:
>> On 1/18/2016 2:30 PM, Thomas A. Schmitz wrote:
>>>
>>> On 01/17/2016 07:24 PM, Hans Hagen wrote:
>>>>
>>>> it should work in the in beta now
>>>
>>>
>>> Hi Hans,
>>>
>>> now I have a problem :-) What should take precedence if an entity is
>>
>>
>> so you have an example ?
>>
>>> both defined in the dtd and as a \xmltexentity? The way I see it, the
>>> latter: e.g., in the DTD, I might declare something for use in a browser
>>> but require a different solution when typesetting with ConTeXt. The
>>> latest and greatest now takes my DTD definitions instead of the
>>> \xmltexentities, which did not happen before. Is that an unwanted side
>>> effect or the new default?
>>
>>
>> we probably have to make it configureable
>
> I don't think it's necessary to have the precedence configurable - I
> think it would make sense to have \xmltexentity always take
> precedence.

all is configureable because there's always someone who wants it different

> The usual case would be that there are no user-specified \xmltexentity
> definitions present at all, and the document's DTD entities would be
> used (by the feature you just added).
>
> So if somebody does have their own \xmltexentity specified, it's
> because they want that to be used instead. That would allow a user to
> do something specific for ConTeXt processing, but I don't have a good
> example for that. Personally I hope I can delete all my \xmltexentity
> calls now.

of course that assumes that you don't need to revert to tex for 
rendering them

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-01-18 21:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 17:21 Kate F
2016-01-15 17:34 ` Thomas A. Schmitz
2016-01-15 17:58   ` Kate F
2016-01-15 20:20     ` Thomas A. Schmitz
2016-01-16  0:33       ` Hans Hagen
2016-01-16 15:55         ` Kate F
2016-01-17 18:24           ` Hans Hagen
2016-01-18 13:30             ` Thomas A. Schmitz
2016-01-18 16:13               ` Kate F
2016-01-18 16:22               ` Kate F
2016-01-18 19:13                 ` Hans Hagen
2016-01-18 20:49                   ` Kate F
2016-01-18 21:16                     ` Hans Hagen
2016-01-19  2:16                       ` Kate F
2016-01-19  2:39                         ` Kate F
2016-01-18 20:07               ` Hans Hagen
2016-01-18 20:56                 ` Kate F
2016-01-18 21:19                   ` Hans Hagen [this message]
2016-01-18 21:26               ` Hans Hagen
2016-01-18 21:45                 ` Thomas A. Schmitz
2016-01-19  8:19                   ` Hans Hagen

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=569D56E1.2010101@wxs.nl \
    --to=pragma@wxs.nl \
    --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).