[NTG-context] Purpose of backend (export=yes)

Vladimir Lomov lomov.vl at gmail.com
Mon Nov 8 15:52:41 CET 2010


Hi.

(I'm reading this ML but rarely ask questions.)

I try to understand the purpose of 'setupbackend'.

Consider the following three examples:

----------------------------------------------------------------------

<example name="ex1.tex">
\setupbackend[export=yes]

\starttext

This is simple example. No font switching, no math.

\stoptext
</example>

----------------------------------------------------------------------

<example name="ex2.tex">
\setupbackend[export=yes]

\starttext

This is second example.
This time we try to use font switching mechanism:
This is normal, but this \bold{one is bold}. Normal again.

\stoptext
</example>

----------------------------------------------------------------------

<example name="ex3.tex">
\setupbackend[export=yes]

\starttext

This is third example with 'backend' 'export=yes'. Now we try simple math:

This is inline formula $E=mc^{2}$.

This is display formula
\startformula
  E=mc^{2}
\stopformula

\stoptext
</example>

----------------------------------------------------------------------

I compiled them with context (mkIV, context minimal) and got
ex{1,2,3}.export. I thought that I get not only the document content but
also its logical structure (for example some markup for font switching).

Is it true that 'backend' only output document content not its logic
strcuture? Does it work with math? The third example gives for math only
not letters.

I attached the resulted export files.

P.S. Then I saw the announce about 'backend' & 'export=yes' I thought
that context would be good tool for notes. I imagine that I could wrote
a text file and make from it either pdf (for printing/screening) or html
(for screening) or may be convert xml (using existing tools and
methods) to other formats (rtf/odt/xhtml) that would contain math,
images, tables. But seems that I was wrong or this will be in future
of the backend?

---
WBR, Vladimir Lomov


-- 
If you make people think they're thinking, they'll love you; but if you
really make them think they'll hate you.
-------------- next part --------------
<?xml version='1.0' standalone='yes' ?>

<!-- input filename   : ex1               -->
<!-- processing date  : Mon Nov  8 22:44:56 2010 -->
<!-- context version  : 2010.11.03 19:42  -->
<!-- exporter version : 0.10              -->

<document language='en' file='ex1' date='Mon Nov  8 22:44:56 2010' context='2010.11.03 19:42' version='0.10'>
This is simple example. No font switching, no math.
</document>
-------------- next part --------------
<?xml version='1.0' standalone='yes' ?>

<!-- input filename   : ex2               -->
<!-- processing date  : Mon Nov  8 22:45:03 2010 -->
<!-- context version  : 2010.11.03 19:42  -->
<!-- exporter version : 0.10              -->

<document language='en' file='ex2' date='Mon Nov  8 22:45:03 2010' context='2010.11.03 19:42' version='0.10'>
This is second example. This time we try to use font switching mechanism: This is normal, but this one is bold. Normal again.
</document>
-------------- next part --------------
<?xml version='1.0' standalone='yes' ?>

<!-- input filename   : ex3               -->
<!-- processing date  : Mon Nov  8 22:45:09 2010 -->
<!-- context version  : 2010.11.03 19:42  -->
<!-- exporter version : 0.10              -->

<document language='en' file='ex3' date='Mon Nov  8 22:45:09 2010' context='2010.11.03 19:42' version='0.10'>
This is third example with 'backend' 'export=yes'. Now we try simple math:
  <break/>
 This is inline formula 
  <math>
    <mrow>
      <mi>?</mi>
      <mo>=</mo>
      <mi>?</mi>
      <msup>
        <mi>?</mi>
        <mn>2</mn>
      </msup>
    </mrow>
  </math>


More information about the ntg-context mailing list