From: Hans Hagen <pragma@wxs.nl>
Subject: Re: XML and title page rule
Date: Tue, 28 Mar 2006 18:40:13 +0200 [thread overview]
Message-ID: <442966ED.4000007@wxs.nl> (raw)
In-Reply-To: <e0bn9e$dql$1@sea.gmane.org>
Jano Kula wrote:
> Hi,
>
>
>> <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?
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-03-28 16:40 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 [this message]
2006-03-28 17:38 ` Jano Kula
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=442966ED.4000007@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).