LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Thu, 11 Mar 2010 23:04:30 +0100
Content-Disposition:
inline
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
MIME-Version:
1.0
Message-ID:
In-Reply-To:
<20100311212544.GA4583@khaled-laptop>
Content-Type:
text/plain; charset=us-ascii
From:
Heiko Oberdiek <[log in to unmask]>
Parts/Attachments:
text/plain (26 lines)
On Thu, Mar 11, 2010 at 11:25:44PM +0200, Khaled Hosny wrote:

> On Thu, Mar 11, 2010 at 09:24:06PM +0100, Heiko Oberdiek wrote:
> > On Thu, Mar 11, 2010 at 10:12:25PM +0200, Khaled Hosny wrote:
> > 
> > > What about the approach we used in etex.src; redefining \patterns and
> > > \hyphenation to use corresponding lua functions, so we don't need to
> > > duplicate hyphenation files and, AFAIU, solves the catcode issue.
> > 
> > \patterns is not read by Lua but by TeX, thus the catcode
> > problem remains.
> 
> I don't claim that I understand anything, but do we have some example
> for the likes of me to see the problem?

* verbatim mode
* babel shorthands
* other active characters
* ...

At format generation the catcodes are known, the pattern files
are written for that case. Later the catcodes can be anything.

Yours sincerely
  Heiko <[log in to unmask]>

ATOM RSS1 RSS2