ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: news2@nililand.de,  mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Partly OT: some luatex questions
Date: Thu, 14 Aug 2008 16:27:28 +0200	[thread overview]
Message-ID: <48A440D0.8000608@wxs.nl> (raw)
In-Reply-To: <tf1k4z72n4as.dlg@nililand.de>

Ulrike Fischer wrote:

> But what would be really fine were extracts of the context code: E.g. a
> bundle of self contained lua-code and tex-code that leds to an extended
> \font command (or a \font command with extended syntax similar to xetex)
> with opentype/ttf-support. If such a primitive were present it would be
> probably quite easy to write the LaTeX support e.g. by adapting
> fontspec. Or a bundle which can be used to convert other input encodings
> to utf8. Or a bundle of the code which sets catcodes and lccode etc. 

wel, if there is some kind of plain mode, then using that other macro 
packages is possible too, but it has no high priority; first most of the 
font stuff needs to be in place, then i start working on a more layered 
context setup (so that one can use components for other purposes)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-08-14 14:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 14:50 Ulrike Fischer
2008-08-13 21:07 ` Arthur Reutenauer
2008-08-14  7:48   ` Ulrike Fischer
2008-08-14  7:58     ` Wolfgang Schuster
2008-08-14  8:11       ` Hans Hagen
2008-08-14 12:25         ` Ulrike Fischer
2008-08-14 14:27           ` Hans Hagen [this message]
2008-08-14  9:07       ` Ulrike Fischer
2008-08-14  9:44         ` Wolfgang Schuster
2008-08-14 11:53           ` Ulrike Fischer
2008-08-14 13:49             ` Arthur Reutenauer
2008-08-14 14:28               ` Ulrike Fischer
2008-08-14 20:08                 ` Hans Hagen
2008-08-14 21:24                   ` Intraword spacing proof of concept Charles P. Schaum
2008-08-15  7:49                     ` Hans Hagen
2008-08-15 15:50                       ` Charles P. Schaum
2008-08-15 17:40                         ` AUCTeX issues not necessarily ConTeXt-related Charles P. Schaum
2008-08-15 20:53                           ` Peter Münster

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=48A440D0.8000608@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=news2@nililand.de \
    --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).