From: Christopher G D Tipper <chris.tipper@gmail.com>
Subject: Re: indenting in XML environment
Date: Sun, 15 Jan 2006 12:54:26 +0000 [thread overview]
Message-ID: <A5E179C4-AEAC-42D8-96B5-A4B2FC56271A@gmail.com> (raw)
In-Reply-To: <43C9849B.70909@elvenkind.com>
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
Hi Taco,
I've found the miscreant. In my stylesheet I have
\def\eDroppedCaps
{\DroppedCaps
{} {ptmr8r}
{2.2\baselineskip} {2pt} {\baselineskip} {2}}
and in my XML I have:
\defineXMLcommand [dropped-caps] \eDroppedCaps
and for some reason this screws up all paragraph indenting. Has this
changed recently, because it used to work?
Christopher
[-- Attachment #2: xml-indenting.tex --]
[-- Type: application/octet-stream, Size: 701 bytes --]
\def\eDroppedCaps\r {\DroppedCaps\r {} {ptmr8r}\r {2.2\baselineskip} {2pt} {\baselineskip} {2}}
\defineXMLenvironment[body]
{\bgroup
\startcolumns[rule=on,n=2,tolerance=strict]
%\startcolumnset[twocolumns]
\rm\setupwhitespace[none]
\setupindenting[small,yes]
\noindentation
}
{\stopcolumns
%\stopcolumnset
\egroup}
\defineXMLenvironment [document] {} {}
\defineXMLcommand[p] {\par}
\defineXMLcommand[tex] \TeX\
\defineXMLcommand [dropped-caps] \eDroppedCaps
\starttext
\processXMLfilegrouped {knuth.xml}\r\stoptext
[-- Attachment #3: knuth.xml --]
[-- Type: text/xml, Size: 1121 bytes --]
<document>
<body>
<p><dropped-caps />Thus, I came to the conclusion that the designer of a new
system must not only be the implementer and first
large-scale user; the designer should also write the first
user manual.
</p>
<p>The separation of any of these four components would have
hurt <tex/> significantly. If I had not participated fully in
all these activities, literally hundreds of improvements
would never have been made, because I would never have
thought of them or perceived why they were important.
</p>
<p>But a system cannot be successful if it is too strongly
influenced by a single person. Once the initial design is
complete and fairly robust, the real test begins as people
with many different viewpoints undertake their own
experiments.
</p>
</body>
</document>
[-- Attachment #4: Type: text/plain, Size: 722 bytes --]
On 14 Jan 2006, at 23:09, Taco Hoekwater wrote:
> I've created a test file with this appended to your definition:
>
> \defineXMLenvironment[p]{}{\par}
> \starttext
> \startXMLdata
> <body>
> <p>text</p>
> <p>text</p>
> <p>text</p>
> </body>
> \stopXMLdata
> \stoptext
>
> And it nicely indents the second and third paragraph.
>
> I would use
> \noindentation }
> instead of
> {\noindening} }
> but both possibilities work out fine here.
--------------------------------o00o--------------------------------
“Since light travels faster than sound, isn’t that why
some people appear bright until you hear them speak”
— Steve Wright
[-- Attachment #5: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-01-15 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 16:03 Christopher G D Tipper
2006-01-14 23:09 ` Taco Hoekwater
2006-01-15 12:54 ` Christopher G D Tipper [this message]
2006-01-15 18:07 ` Hans Hagen
2006-01-16 11:09 ` Taco Hoekwater
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=A5E179C4-AEAC-42D8-96B5-A4B2FC56271A@gmail.com \
--to=chris.tipper@gmail.com \
--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).