ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ulrike Fischer <news2@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: Partly OT: some luatex questions
Date: Thu, 14 Aug 2008 14:25:44 +0200	[thread overview]
Message-ID: <tf1k4z72n4as.dlg@nililand.de> (raw)
In-Reply-To: <48A3E8C1.6050409@wxs.nl>

Am Thu, 14 Aug 2008 10:11:45 +0200 schrieb Hans Hagen:


>>> In all cases (also if I try dvi-output) the lines glue together. The
>>> attachment text-lua is the pdf of the latex try.
> 
> you can make a plain format operating in the same 'space' as context with
> 
>    luatools --make plain

I tried plain only for testing purposes. My goal is to be able to use
LaTeX. Also I don't have a "context space": As non-Miktex-files I use
currently only the executables luatex, mktexlsr (and kpswhich) and a
texmf.cnf-file. 


> eventually i will make a plain variant (probably a bit more more plain 
> than plain) with basic open type support (for other formats you might 
> need to add --compile to the make call)

If you mean a complete plainTeX-format: I at least don't need it much
;-) 

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. 

 


-- 
Ulrike Fischer 

___________________________________________________________________________________
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 12:25 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 [this message]
2008-08-14 14:27           ` Hans Hagen
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=tf1k4z72n4as.dlg@nililand.de \
    --to=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).