From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: Re: ConTeXt, XML en-dash
Date: Wed, 30 Nov 2005 09:16:22 +0100 [thread overview]
Message-ID: <438D5FD6.70409@wxs.nl> (raw)
In-Reply-To: <dmil88$7ep$1@sea.gmane.org>
Johannes Graumann wrote:
>Hans Hagen wrote:
>
>
>
>>>Gee ... Tacos fix (see thread) worked just fine ... when would I need
>>>this?
>>>
>>>
>>>
>>taco's fix deals with entities; the other method is meant for direct
>>input (say three -'s in the input stream)
>>
>>
>>
>I see. I was hoping to find some way of mapping my (custom) XML eventually
>somehow into ooffice as well (any pointers on how one might create a style
>sheet for that are HIGHLY appreciated) and think the entity method is
>therefore more future proof for me.
>
>
definitely, but when you deal with third part (utf-8 encoded) xml, you
can expect anything (a dozen of different dashes to start with -)
Hans
prev parent reply other threads:[~2005-11-30 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 2:04 Johannes Graumann
2005-11-29 7:08 ` Taco Hoekwater
2005-11-29 19:46 ` Johannes Graumann
2005-11-29 9:15 ` Hans Hagen
2005-11-29 19:59 ` Johannes Graumann
2005-11-29 21:14 ` Hans Hagen
2005-11-29 22:37 ` Johannes Graumann
2005-11-30 8:16 ` Hans Hagen [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=438D5FD6.70409@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).