ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "luigi.scarso" <luigi.scarso@logosrl.it>
Subject: Re: Python,swig and pdftex ?
Date: Mon, 28 Feb 2005 07:49:46 +0100	[thread overview]
Message-ID: <4222BF0A.5080504@logosrl.it> (raw)
In-Reply-To: <4220577F.50205@zscout.de>


[-- Attachment #1.1: Type: text/plain, Size: 771 bytes --]

Janko Hauser wrote:

>luigi.scarso schrieb:
>  
>
>>I'm try do make something useful with Python and pdftex using swig.
>>Any suggestions ?
>>
>>    
>>
>Have you looked at pytex? It does nothing with pdftex, but I do not know
>what do you want to actually do.
>
>__Janko
>
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
>
>  
>
I have found
http://www.metatex.org

that seem to be a good starting point.
I would like to explore the possibility to embed a pyhton interpreter 
into pdftex,and use it into ConTeXt ("python inside context");
another wish is some python modules to do some typesetting jobs using
ConTexT ("context inside python"); maybe swig can be help.

luigi

[-- Attachment #1.2: Type: text/html, Size: 1433 bytes --]

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

      reply	other threads:[~2005-02-28  6:49 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 12:29 lettrine.sty, but not LaTeX Gerben Wierda
2005-02-25 13:41 ` Taco Hoekwater
2005-02-25 17:51   ` Peter Münster
2005-02-25 18:46     ` Taco Hoekwater
2005-02-25 19:19       ` Mats Broberg
2005-02-25 20:16         ` Hans Hagen
2005-02-25 21:04           ` Taco Hoekwater
2005-02-25 22:00             ` VnPenguin
2005-02-25 22:28               ` Taco Hoekwater
2005-02-25 22:52                 ` David Wooten
2005-02-26 10:23                   ` Taco Hoekwater
2005-02-26 13:10                     ` Gerben Wierda
2005-02-26 16:26                       ` Taco Hoekwater
2005-02-26 17:08                         ` lack of hyphenation Ciro A. Soto
2005-02-26 17:34                           ` Taco Hoekwater
2005-02-26 20:06                             ` Ciro A. Soto
2005-02-26 21:32                               ` 4UP with no table of content - bug? Ciro A. Soto
2005-02-27 11:48                                 ` h h extern
2005-02-26 21:50                               ` lack of hyphenation Taco Hoekwater
2005-02-26 22:26                                 ` Patrick Gundlach
2005-02-27  7:45                                   ` Ciro A. Soto
2005-02-27  9:57                                     ` Taco Hoekwater
2005-02-27 11:35                             ` h h extern
2005-03-19 17:40                               ` Patrick Gundlach
2005-02-26 17:34                           ` Mats Broberg
2005-02-27 11:21                           ` h h extern
2005-02-27 11:33                             ` Patrick Gundlach
2005-02-27 11:40                               ` Taco Hoekwater
2005-02-27 19:55                                 ` h h extern
2005-02-28 19:54                             ` Mats Broberg
2005-02-28 20:08                               ` Mikael Persson
2005-02-28 20:40                                 ` Mats Broberg
2005-02-28 20:37                               ` h h extern
2005-03-02 19:05                                 ` Mats Broberg
2005-03-03  7:19                                   ` Hans Hagen
2005-02-27 13:13                           ` Mats Broberg
2005-02-26 17:22                         ` lettrine.sty, but not LaTeX Peter Münster
2005-02-27 11:01                           ` packaging of extra modules Taco Hoekwater
2005-02-27 18:21                         ` lettrine.sty, but not LaTeX h h extern
2005-02-27 11:06                     ` h h extern
2005-02-27 14:29                       ` Taco Hoekwater
2005-02-27 15:59                         ` Mats Broberg
2005-02-28  9:34                           ` Taco Hoekwater
2005-03-01 19:33                             ` VnPenguin
2005-03-01 19:41                             ` VnPenguin
2005-03-01 20:02                               ` Taco Hoekwater
2005-03-01 22:37                               ` Ciro A. Soto
2005-03-01 23:03                                 ` Mats Broberg
2005-03-01 23:44                                 ` VnPenguin
2005-03-02 19:08                                   ` Mats Broberg
2005-03-02 19:50                                     ` Willi Egger
2005-03-02 20:34                                     ` Hans Hagen
2005-03-02 23:42                                       ` Ciro A. Soto
2005-03-03  7:09                                         ` Hans Hagen
2005-03-10 20:04                                           ` Gerben Wierda
2005-03-10 20:11                                             ` Gerben Wierda
2005-03-02 19:06                             ` Mats Broberg
2005-02-27 10:13             ` h h extern
2005-02-27 10:51               ` Taco Hoekwater
2005-02-27 10:51               ` Mats Broberg
2005-02-27 11:02                 ` Adam Lindsay
2005-02-25 15:29 ` Python,swig and pdftex ? luigi.scarso
2005-02-26 11:03   ` Janko Hauser
2005-02-28  6:49     ` luigi.scarso [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=4222BF0A.5080504@logosrl.it \
    --to=luigi.scarso@logosrl.it \
    --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).