From: Jano Kula <jano.kula@tiscali.cz>
Subject: Re: XML and title page rule
Date: Tue, 28 Mar 2006 19:38:04 +0200 [thread overview]
Message-ID: <e0bs9t$3kd$1@sea.gmane.org> (raw)
In-Reply-To: <442966ED.4000007@wxs.nl>
>>> <title>Something &emdash; or <i>Something else</i></title>
>>>
>> can somebody explain to a complete newbie why entity &emdash; isn't
>> expanded out of the box?
>>
>> (I use texexec -pdf document.tex for processing.)
>>
>>
> did you define the entity?
Thanks.
No I expected the example to be a minimal example, where everything else
should work. And & entity did work (yes, I know it has a special
meaning in XML, so it is probably predefined).
Jano
next prev parent reply other threads:[~2006-03-28 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 4:36 Johannes Graumann
2006-03-24 9:12 ` Hans Hagen
2006-03-24 18:04 ` Johannes Graumann
2006-03-28 16:12 ` Jano Kula
2006-03-28 16:40 ` Hans Hagen
2006-03-28 17:38 ` Jano Kula [this message]
2006-03-29 14:15 ` documents to (print and) read Geert Stappers
2006-03-30 8:38 ` Taco Hoekwater
2006-04-03 17:43 ` Jano Kula
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='e0bs9t$3kd$1@sea.gmane.org' \
--to=jano.kula@tiscali.cz \
--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).