ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Otared Kavian <otared@gmail.com>
Subject: Re: export
Date: Wed, 22 Sep 2010 14:22:59 +0200	[thread overview]
Message-ID: <4C99F523.9040408@wxs.nl> (raw)
In-Reply-To: <8303474C-099C-432A-A095-7FD16597A84A@gmail.com>

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
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2010-09-22 12:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 10:45 export Hans Hagen
2010-09-22 11:56 ` export Otared Kavian
2010-09-22 12:06   ` export Yury G. Kudryashov
2010-09-22 12:18     ` export Otared Kavian
2010-09-22 12:22       ` Hans Hagen [this message]
2010-09-22 12:25       ` export Alan BRASLAU
2010-09-22 12:29         ` export Andreas Harder
2010-09-22 12:36           ` export Alan BRASLAU
2010-09-22 21:47           ` export Henning Hraban Ramm
2010-09-23 13:55 ` export Jelle Huisman
2010-09-23 14:40   ` export Hans Hagen
2010-09-23 15:01     ` export Aditya Mahajan
2010-09-23 15:12       ` export Hans Hagen
2010-09-23 15:41         ` export Jelle Huisman
2010-09-23 19:30         ` export Steffen Wolfrum
     [not found] <mailman.240.1285157191.4222.ntg-context@ntg.nl>
2010-09-22 23:26 ` export Vyatcheslav Yatskovsky
2010-09-23  6:05   ` export Henning Hraban Ramm
     [not found] <mailman.263.1285229118.4222.ntg-context@ntg.nl>
2010-09-23 13:00 ` export Vyatcheslav Yatskovsky
2010-09-23 13:15   ` export Cedric Mauclair
2010-09-23 17:17     ` export Peter Münster
     [not found] <mailman.269.1285249774.4222.ntg-context@ntg.nl>
2010-09-25 15:45 ` export Vyatcheslav Yatskovsky

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=4C99F523.9040408@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=otared@gmail.com \
    /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).