From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: luatex feature question/request
Date: Fri, 04 Apr 2008 11:08:05 +0200 [thread overview]
Message-ID: <47F5EFF5.9040109@wxs.nl> (raw)
In-Reply-To: <5c2c86e70804040158o712ab1ben88b69b0d794109cc@mail.gmail.com>
Olivier Guéry wrote:
> On Fri, Apr 4, 2008 at 10:52 AM, Taco Hoekwater <taco@elvenkind.com> wrote:
>>
>> luigi scarso wrote:
>> >> There actually is a way to modify the input lines just before they
>> >> are parsed by luatex, but that is really only suitable for converting
>> >> 8-bit encodings to utf-8. (I was going to post an example abusing
>> >> that method, but there are way many things that can go wrong, so I
>> >> changed my mind)
>> > Post it anyway.
>> > We are all adults.
>>
>> If you say so ...
>>
>> % engine=luatex
>>
>> \startluacode
>> function add_ties (line) return line:gsub(' ','~') end
>> \stopluacode
>
> Hello, new to this list, I see this first message. Is it a solution
> for my request (http://wiki.contextgarden.net/Feature_Requests) about
> french typography ?
\setcharacterspacing [frenchpunctuation]
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-04-04 9:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 5:09 Marcin Borkowski
2008-04-04 7:50 ` Hans Hagen
2008-04-04 8:33 ` Taco Hoekwater
2008-04-04 8:38 ` luigi scarso
2008-04-04 8:52 ` Taco Hoekwater
2008-04-04 8:58 ` Olivier Guéry
2008-04-04 9:08 ` Hans Hagen [this message]
2008-04-04 11:02 ` Olivier Guéry
2008-04-04 11:15 ` Wolfgang Schuster
2008-04-04 12:26 ` Olivier Guéry
2008-04-04 12:55 ` Peter Münster
2008-04-04 13:15 ` Olivier Guéry
2008-04-04 15:15 ` Peter Münster
2008-04-04 20:23 ` Olivier Guéry
2008-04-04 12:26 ` Hans Hagen
2008-04-04 13:09 ` Olivier Guéry
2008-04-15 19:18 ` Hans Hagen
2008-04-15 19:54 ` Olivier Guéry
2008-04-16 0:40 ` Arthur Reutenauer
2008-04-16 8:50 ` Hans Hagen
2008-04-16 10:19 ` Olivier Guéry
2008-04-16 12:46 ` Peter Münster
2008-04-16 14:20 ` Hans Hagen
2008-04-04 10:16 ` Peter Münster
2008-04-04 9:19 ` luigi scarso
2008-04-04 19:26 ` Peter Münster
2008-04-04 19:48 ` Aditya Mahajan
2008-04-04 20:03 ` Peter Münster
2008-04-04 20:07 ` Hans Hagen
2008-04-04 20:20 ` Taco Hoekwater
2008-04-04 9:57 ` Marcin Borkowski
2008-07-04 10:54 Marcin Borkowski
2008-07-04 14:23 ` Idris Samawi Hamid ادريس سماوي حامد
2008-07-04 15:01 ` Olivier
2008-07-04 17:38 ` Idris Samawi Hamid ادريس سماوي حامد
2008-07-04 20:34 ` Hans Hagen
2008-07-04 20:39 ` Hans Hagen
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=47F5EFF5.9040109@wxs.nl \
--to=pragma@wxs.nl \
--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).