ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Procházka Lukáš Ing. - Pontex s. r. o." <LPr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: File.export to File.html
Date: Fri, 15 Jul 2011 11:08:21 +0200	[thread overview]
Message-ID: <op.vynkz7n4tpjj8f@lpr> (raw)
In-Reply-To: <CAG5iGsDb=eOMwnUwe7QmnwYoLdDz+s__Qrj_fjgF4jGSDHSkzA@mail.gmail.com>

... Perfect, thanks!

(c:\ConTeXt\tex\texmf-context\tex\context\base\export-example.*)

I didn't know this example; creating .(x)htm(l) in such way is really easy!

Best regards,

Lukas


On Fri, 15 Jul 2011 10:36:32 +0200, luigi scarso <luigi.scarso@gmail.com> wrote:

> 2011/7/15 Procházka Lukáš Ing. - Pontex s. r. o. <LPr@pontex.cz>:
>> Hello,
>>
>> the following question may relate to XML processing rather to Context.
>>
>> But someone may have needed to solve the problem.
>>
>> Lets have a File.export which was generated by Context with
>> "\setupbackend[export=yes,xhtml=yes,css=yes]".
>>
>> Such a XML output file uses tags like:
>>
>> <section>
>> <sectionnumber>
>> <sectiontitle>
>> <sectioncontent>
>> <itemgroup>
>> <item>
>> ...
>>
>> Has anyone solved conversion of such a file to an [arbitrary] .(x)html?
>>
>> I have only slight knowledge about XML transformations - the task is just
>> about converting the Context XML to XHTML - and I would be hardly able to
>> write a XSLT from scratch.
>>
>> Moreover, I don't have personal experience with any XML processor/converter.
>>
>> It wouldn't be so important how the resulting .html would be "perfect"; the
>> main goal is to convert Context File.export to File.html with working
>> hyperlinks to view it in a web page viewer.
>>
>> Could anyone describe his experience?
>>
>> - Processor, support file(s) (XSLT?); any demos of such support files (their
>> "minimals") or "complex solutions" would be welcome; whatever working
>> solution.
>>
>> I'm WinXP (32b) user, so demos for Windows are preferred but any hints are
>> welcome.
> The context way is to demand the css files about the meaning of the tags .
> If you search in the ml (or grep the code) you will find an example of
> this; see also
> example-export.css in the minimals.
>


-- 
Ing. Lukáš Procházka [mailto:LPr@pontex.cz]
Pontex s. r. o.      [mailto:pontex@pontex.cz] [http://www.pontex.cz]
Bezová 1658
147 14 Praha 4

Tel: +420 244 062 238
Fax: +420 244 461 038

___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2011-07-15  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15  8:29 Procházka Lukáš Ing. - Pontex s. r. o.
2011-07-15  8:36 ` luigi scarso
2011-07-15  9:08   ` Procházka Lukáš Ing. - Pontex s. r. o. [this message]

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=op.vynkz7n4tpjj8f@lpr \
    --to=lpr@pontex.cz \
    --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).