Hi, For those who were not at the ctx conference (where it was demonstrated) .. there is a new feature. When you say: \setupbackeds[export=yes] You will also get a file called <jobname>.export which represents the document in xml format. You can postprocess such an export to for instance html. It's still somewhat experimental but also fun. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hi Hans, Thanks for giving the information to those unlucky people who were not at the ConTeXt conference: Since I am interested in the feature you mention, I just tried with the latest beta you uploaded today, but the command \setupbackeds[export=yes] is unknown. Maybe there is a typo in what you said: could you please give a hint? Many thanks in advance: OK On 22 sept. 2010, at 12:45, Hans Hagen wrote:
Hi,
For those who were not at the ctx conference (where it was demonstrated) .. there is a new feature. When you say:
\setupbackeds[export=yes]
You will also get a file called <jobname>.export which represents the document in xml format. You can postprocess such an export to for instance html. It's still somewhat experimental but also fun.
Hans
----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl ----------------------------------------------------------------- ___________________________________________________________________________________ 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 ___________________________________________________________________________________
Otared Kavian wrote:
Hi Hans,
Thanks for giving the information to those unlucky people who were not at the ConTeXt conference: Since I am interested in the feature you mention, I just tried with the latest beta you uploaded today, but the command \setupbackeds[export=yes] is unknown. Maybe there is a typo in what you said: could you please give a hint? Try \setupbackends.
Many thanks in advance: OK
On 22-9-2010 2:18, Otared Kavian wrote:
On 22 sept. 2010, at 14:06, Yury G. Kudryashov wrote:
[…] Try \setupbackends.
Thanks Yuri for your attention, but this suggestion doesn't work: I get
error on line 3 in file test-export.tex: Undefined control sequence ...
\setupbackends[export=yes]
there is only one backend ... \setupbackend [export=yes] and this command is only available in post tex live 2010 versions (with export only being supported with versions uploaded during and after the conference) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Minimal example (given at the workshop): \setupbackend [export=yes] \starttext \startchapter [title=First chapter] \startparagraph \input ward \stopparagraph \stopchapter \stoptext On Wednesday 22 September 2010 14:18:18 Otared Kavian wrote:
On 22 sept. 2010, at 14:06, Yury G. Kudryashov wrote:
[…]
Try \setupbackends.
Thanks Yuri for your attention, but this suggestion doesn't work: I get
error on line 3 in file test-export.tex: Undefined control sequence ...
\setupbackends[export=yes]
Best regards: OK ___________________________________________________________________________ ________ 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 ___________________________________________________________________________ ________
-- Alan Braslau CEA DSM-IRAMIS-SPEC CNRS URA 2464 Orme des Merisiers 91191 Gif-sur-Yvette cedex FRANCE tel: +33 1 69 08 73 15 fax: +33 1 69 08 87 86 mailto:alan.braslau@cea.fr http://www-dna2009.cea.fr/ .''`. : :' : `. `'` `-
On Wednesday 22 September 2010 14:29:08 Andreas Harder wrote:
Am 22.09.2010 um 14:25 schrieb Alan BRASLAU:
\setupbackend [export=yes]
\starttext
\startchapter [title=First chapter]
\startparagraph
\input ward
\stopparagraph
\stopchapter
\stoptext
Results in "Undefined control sequence. \setupbackend" (newest beta; OS X) …
Greeting Andreas
Works here - latest beta - linux x86_64 (see attached) Alan
Am 2010-09-22 um 14:29 schrieb Andreas Harder:
Am 22.09.2010 um 14:25 schrieb Alan BRASLAU: Results in "Undefined control sequence. \setupbackend" (newest beta; OS X) …
Works for me on OSX-Intel. You didn't try texexec (MkII), did you? Greetlings from Lake Constance! Hraban --- http://www.fiee.net/texnique/ http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer)
On 22/09/10 06:45, Hans Hagen wrote:
\setupbackeds[export=yes]
You will also get a file called <jobname>.export which represents the document in xml format. You can postprocess such an export to for instance html. It's still somewhat experimental but also fun.
Hi Hans, Thanks! this is a useful step in the direction of ctx2odt support. Are you planning to provide (basic) (x)html export too? (I'm thinking about this workflow: write in ctx -> make pdf/make html -> open html in OpenOffice -> save as odt/doc.) Jelle
On 23-9-2010 3:55, Jelle Huisman wrote:
On 22/09/10 06:45, Hans Hagen wrote:
\setupbackeds[export=yes]
You will also get a file called <jobname>.export which represents the document in xml format. You can postprocess such an export to for instance html. It's still somewhat experimental but also fun.
Hi Hans,
Thanks! this is a useful step in the direction of ctx2odt support. Are you planning to provide (basic) (x)html export too? (I'm thinking about this workflow: write in ctx -> make pdf/make html -> open html in OpenOffice -> save as odt/doc.)
As xhtml is just xml converted to other tags, I suppose that at some day there will be additional converters. I would only come up with one in the perspective of a project as I have no need for it. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Thu, 23 Sep 2010, Hans Hagen wrote:
On 23-9-2010 3:55, Jelle Huisman wrote:
On 22/09/10 06:45, Hans Hagen wrote:
\setupbackeds[export=yes]
You will also get a file called <jobname>.export which represents the document in xml format. You can postprocess such an export to for instance html. It's still somewhat experimental but also fun.
Hi Hans,
Thanks! this is a useful step in the direction of ctx2odt support. Are you planning to provide (basic) (x)html export too? (I'm thinking about this workflow: write in ctx -> make pdf/make html -> open html in OpenOffice -> save as odt/doc.)
As xhtml is just xml converted to other tags, I suppose that at some day there will be additional converters. I would only come up with one in the perspective of a project as I have no need for it.
There cannot be a universal one-to-one mapping between context generate xml and xhtml. For example, in a book, I may want \chapter to map to <h1> while in an article, I may want \section to map to <h1>. Nonetheless, having a specialized xml to xhtml converter should not be too difficult (using the verbose XSLT transformations). Targetting html5 is another option. On the otherhand, a ConTeXt module that can read context generated xml will be nice... then the context xml can be the target input form for an automated tool trying to generate context source. Aditya
On 23-9-2010 5:01, Aditya Mahajan wrote:
On Thu, 23 Sep 2010, Hans Hagen wrote:
On 23-9-2010 3:55, Jelle Huisman wrote:
On 22/09/10 06:45, Hans Hagen wrote:
\setupbackeds[export=yes]
You will also get a file called <jobname>.export which represents the document in xml format. You can postprocess such an export to for instance html. It's still somewhat experimental but also fun.
Hi Hans,
Thanks! this is a useful step in the direction of ctx2odt support. Are you planning to provide (basic) (x)html export too? (I'm thinking about this workflow: write in ctx -> make pdf/make html -> open html in OpenOffice -> save as odt/doc.)
As xhtml is just xml converted to other tags, I suppose that at some day there will be additional converters. I would only come up with one in the perspective of a project as I have no need for it.
There cannot be a universal one-to-one mapping between context generate xml and xhtml. For example, in a book, I may want \chapter to map to <h1> while in an article, I may want \section to map to <h1>. Nonetheless, having a specialized xml to xhtml converter should not be too difficult (using the verbose XSLT transformations). Targetting html5 is another option.
indeed
On the otherhand, a ConTeXt module that can read context generated xml will be nice... then the context xml can be the target input form for an automated tool trying to generate context source.
it's on my list to make such a roundtrip style Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 23/09/10 11:12, Hans Hagen wrote:
As xhtml is just xml converted to other tags, I suppose that at some day there will be additional converters. I would only come up with one in the perspective of a project as I have no need for it.
There cannot be a universal one-to-one mapping between context generate xml and xhtml. For example, in a book, I may want \chapter to map to <h1> while in an article, I may want \section to map to <h1>. Nonetheless, having a specialized xml to xhtml converter should not be too difficult (using the verbose XSLT transformations). Targetting html5 is another option.
indeed
Sounds like it's time to learn some xslt ;-) Jelle
Am 23.09.2010 um 17:12 schrieb Hans Hagen:
On 23-9-2010 5:01, Aditya Mahajan wrote:
On Thu, 23 Sep 2010, Hans Hagen wrote:
On 23-9-2010 3:55, Jelle Huisman wrote:
On 22/09/10 06:45, Hans Hagen wrote:
\setupbackeds[export=yes]
You will also get a file called <jobname>.export which represents the document in xml format. You can postprocess such an export to for instance html. It's still somewhat experimental but also fun.
Hi Hans,
Thanks! this is a useful step in the direction of ctx2odt support. Are you planning to provide (basic) (x)html export too? (I'm thinking about this workflow: write in ctx -> make pdf/make html -> open html in OpenOffice -> save as odt/doc.)
As xhtml is just xml converted to other tags, I suppose that at some day there will be additional converters. I would only come up with one in the perspective of a project as I have no need for it.
There cannot be a universal one-to-one mapping between context generate xml and xhtml. For example, in a book, I may want \chapter to map to <h1> while in an article, I may want \section to map to <h1>. Nonetheless, having a specialized xml to xhtml converter should not be too difficult (using the verbose XSLT transformations). Targetting html5 is another option.
indeed
On the otherhand, a ConTeXt module that can read context generated xml will be nice... then the context xml can be the target input form for an automated tool trying to generate context source.
it's on my list to make such a roundtrip style
=:o) st.
participants (9)
-
Aditya Mahajan -
Alan BRASLAU -
Andreas Harder -
Hans Hagen -
Henning Hraban Ramm -
Jelle Huisman -
Otared Kavian -
Steffen Wolfrum -
Yury G. Kudryashov