ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: typeseting XML
Date: Fri, 18 May 2001 16:10:22 +0200	[thread overview]
Message-ID: <3.0.6.32.20010518161022.019277e0@server-1> (raw)
In-Reply-To: <Pine.BSF.3.96.1010515225104.2197B-100000@vertigo.fme.vutbr .cz>

At 01:54 AM 5/17/01 +0200, Petr Ferdus wrote:
>Hi,
>how could be typeset backslash character parsed from XML stream?

<...>bla \bla bla<...> should work ok

>I tryed:
>
>\defineXMLsingular [backslash]  {$\backslash$}
>
>having in XML doc an  empty element <backslash/>, with no success (no
>error either, it was just silently discarded). 

\defineXMLsingular [backslash] {\tex{}} 

i still need to add named chars for backslash and so. 

>Also, would it be possible to have # char in the name of XML entity? Like:
>
>\defineXMLentity [#937] {$\Omega$} %instead of
>\defineXMLentity [937] {$\Omega$} 
>
>because it seems to be rather conforming to naming convention of entities
>based on unicode position  of its glyph (&#937; in this case).

that's being worked on [for that taco and i need to have the math unicode
part finished]

Hans
-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


       reply	other threads:[~2001-05-18 14:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.BSF.3.96.1010515225104.2197B-100000@vertigo.fme.vutbr .cz>
2001-05-18 14:10 ` Hans Hagen [this message]
2001-05-18 16:15   ` Petr Ferdus
     [not found]   ` <Pine.BSF.3.96.1010518180453.16005F-100000@vertigo.fme.vutb r.cz>
2001-05-18 16:53     ` Hans Hagen
     [not found] <3.0.6.32.20010525212835.0127d390@server-1>
     [not found] ` <Pine.BSF.3.96.1010529101027.14223A-100000@vertigo.fme.vutb r.cz>
2001-05-29  9:45   ` Hans Hagen
2001-05-29 14:05     ` Petr Ferdus
2001-05-30 15:01     ` Petr Ferdus
     [not found]     ` <Pine.BSF.3.96.1010529153914.15436A-101000@vertigo.fme.vutb r.cz>
2001-05-30 15:09       ` Hans Hagen
2001-05-30 20:12         ` Petr Ferdus
2001-06-14 23:07         ` Petr Ferdus
     [not found]         ` <Pine.BSF.3.96.1010615004606.12697C-100000@vertigo.fme.vutb r.cz>
2001-06-15  8:09           ` Hans Hagen
     [not found]     ` <Pine.BSF.3.96.1010530154343.20742A-101000@vertigo.fme.vutb r.cz>
2001-05-31  9:12       ` Hans Hagen
2001-06-01  8:03         ` Petr Ferdus
     [not found]         ` <Pine.BSF.3.96.1010601083337.29526A-100000@vertigo.fme.vutb r.cz>
2001-06-04  9:55           ` Hans Hagen
2001-06-06  4:47             ` Petr Ferdus
2001-05-16 23:54 Petr Ferdus
2002-02-03 19:51 ` Johannes Hüsing
2002-02-05  8:26   ` Hans Hagen
2002-02-05 13:20     ` Taco Hoekwater
2002-02-05 13:57       ` Hans Hagen
2002-02-05 21:40       ` Johannes Hüsing

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=3.0.6.32.20010518161022.019277e0@server-1 \
    --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).