From: Johannes Graumann <johannes_graumann@web.de>
To: ntg-context@ntg.nl
Subject: Re: XML
Date: Thu, 9 Oct 2008 18:13:00 +0000 (UTC) [thread overview]
Message-ID: <loom.20081009T180040-706@post.gmane.org> (raw)
In-Reply-To: <115224fb0810090050x4b827f8ej9c75bcc724222a7b@mail.gmail.com>
Wolfgang Schuster <schuster.wolfgang <at> googlemail.com> writes:
> \xmlprocess{main}{zip:///\inputfilename.odt?name=content.xml}{}
>
> or
>
> \usezipfile[\inputfilename.odt]
> \xmlprocess{main}{*/content.xml}{}
Thank you very much - very nice!
> You could use this for the start but it behavious a little bit weird.
>
> \unprotect
>
> \def\switchfontstyle
> {\ifx\fontalternative\c!tf \it \else
> \ifx\fontalternative\c!bf \bi \else
> \it \fi\fi}
>
> \protect
>
> \xmlmapvalue {fo:font-style} {italic} {\switchfontstyle}
Hmm ... if I understand this correctly this is aimed at dealing with nested
bold/italic attributes?
While I'm certainly going to fall over this rather soon, I think the issue here
is that the following excerpt, where "T1" and "T2" correspond to bold and italic
definitions further up, is misinterpreted such that the opening "text:span" of
the "T1" section is taken for the beginning of the "T2" section instead and "T2"
is accordingly applied to the whole construct ...
<text:p text:style-name="Standard">
Versuch
<text:span text:style-name="T1">
Bold Versuch
</text:span>
<text:span text:style-name="T2">
Italic Versuch
</text:span>
</text:p>
Where in Hans' snippet below might that be fixable?
\startxmlsetups office
\xmlsetsetup{main}{text:p|text:span}{*}
\stopxmlsetups
xmlregistersetup{office}
\startxmlsetups text:p
\xmlflush{#1}\par
\stopxmlsetups
\startxmlsetups text:span
\bgroup
\xmlfilter{main}{office:automatic-styles/style:style/style:text-properties
/command(do:style:text-properties)}
\xmlflush{#1}
\egroup
\stopxmlsetups
Thanks for any further hints,
Joh
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-10-09 18:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 22:14 XML johannes_graumann
2008-10-08 6:34 ` XML luigi scarso
2008-10-08 8:02 ` XML Johannes Graumann
2008-10-08 8:11 ` XML luigi scarso
2008-10-09 7:50 ` XML Wolfgang Schuster
2008-10-09 18:13 ` Johannes Graumann [this message]
2008-10-14 7:24 ` XML Wolfgang Schuster
2008-10-16 8:24 ` XML Johannes Graumann
2008-10-18 7:28 ` XML olivier Turlier
2008-10-19 13:25 ` XML Johannes Graumann
2008-10-16 8:27 ` XML Johannes Graumann
2008-10-19 20:38 ` XML Johannes Graumann
2008-10-22 6:50 ` XML Wolfgang Schuster
2008-10-22 14:56 ` XML Johannes Graumann
2008-10-22 21:04 ` XML Johannes Graumann
2008-10-22 21:30 ` XML Hans Hagen
2008-10-26 14:05 ` XML Johannes Graumann
2008-10-27 10:42 ` XML Wolfgang Schuster
2008-10-27 20:16 ` XML Johannes Graumann
2008-10-29 7:09 ` XML Wolfgang Schuster
-- strict thread matches above, loose matches on Subject: below --
2005-09-22 6:29 XML Jessica Holle
2005-09-22 6:39 ` XML Henning Hraban Ramm
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=loom.20081009T180040-706@post.gmane.org \
--to=johannes_graumann@web.de \
--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).