ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: My Way: Unicode Symbols
Date: Mon, 05 Jan 2004 21:12:16 +0100	[thread overview]
Message-ID: <6.0.1.1.2.20040105205934.01dc7890@server-1> (raw)
In-Reply-To: <20040105142328.13433@smtp.btinternet.com>

Hi Adam,

When reading your my way i noticed a few things:

(1) sometimes too wide verbatim xml lines can better be handled as follows:

\starttext

\showXMLwrd[oeps]

\startbuffer
<text>
   <example>
     test <oeps/> test
   </example>
</text>
\stopbuffer

\showXMLbuffer

\stoptext

There is also an inline variant:

test test test test test \showXMLtext {<text> <example> test <oeps/> test
</example> </text>} test test test test

and of course a \showXMLfile{name.xml}

The advantage of this method is that too wide lines are handled better i.e. 
they are properly indented

(2) When formatting an ascii text (i.e. the input source), instead of

  test \test{test[test] test{test}} test

one can say:

  test \test {test [test] test {test}} test

which wraps nicer. So, one may have a space after a \command, and between 
{one} {two} arguments (few
exceptions) etc.

(3) instead of \input symb-uni you can use \usesymbols[uni]

(4) I've just added \startxtyping and \startxxtyping to the style

\definetyping[xtyping] [style=\ttx]
\definetyping[xxtyping][style=\ttxx]

Hans




Hans

  parent reply	other threads:[~2004-01-05 20:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 17:59 unicode and out-of-box usability Adam Lindsay
2004-01-03 22:38 ` Hans Hagen
2004-01-05 13:43   ` Adam Lindsay
2004-01-05 14:23   ` My Way: Unicode Symbols Adam Lindsay
2004-01-05 19:20     ` Adam Lindsay
2004-01-05 20:12     ` Hans Hagen [this message]
2004-01-06 12:22       ` Adam Lindsay
2004-01-06 14:01         ` Hans Hagen
2004-01-07 15:26           ` Adam Lindsay
2004-01-11 11:30       ` Adam Lindsay

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=6.0.1.1.2.20040105205934.01dc7890@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).