From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: XML
Date: Thu, 9 Oct 2008 09:50:54 +0200 [thread overview]
Message-ID: <115224fb0810090050x4b827f8ej9c75bcc724222a7b@mail.gmail.com> (raw)
In-Reply-To: <200810072214.52895.johannes_graumann@web.de>
On Wed, Oct 8, 2008 at 12:14 AM, <johannes_graumann@web.de> wrote:
> Hello,
>
> The family is gone for the week, so I have time to play ...
>
> What I'm doing is the following(using the attached files):
> context --ctx=t-openoffice BoldOnlyContent.xml
> Which works nicely.
>
> I'd like to make this work like so:
> context --ctx=t-openoffice VersuchBoldOnly.odt
> but whether I change the respective line in t-openoffice.tex to
> \xmlprocess{main}{zip://*/content.xml}{}
> or
> \xmlprocess{main}{*/content.xml}{}
> - no luck ... how to do this?
\xmlprocess{main}{zip:///\inputfilename.odt?name=content.xml}{}
or
\usezipfile[\inputfilename.odt]
\xmlprocess{main}{*/content.xml}{}
> Hans let me know how to parse xml styles on the fly, but I fail to generalize
> this further. When uncommenting the line
> \xmlval{fo:font-style}{\xmlatt{#1}{font-style}}{}
> in t-openoffice.tex this doesn't work as expected:
> context --ctx=t-openoffice BoldAndItalicContent.xml
> Any hints on how to fix this?
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}
> I have asked related questions in the past, but have now a bit of time to
> investigate further ...
Regards,
Wolfgang
___________________________________________________________________________________
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 7:50 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 ` Wolfgang Schuster [this message]
2008-10-09 18:13 ` XML Johannes Graumann
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=115224fb0810090050x4b827f8ej9c75bcc724222a7b@mail.gmail.com \
--to=schuster.wolfgang@googlemail.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).