References: <11ECEE9E-C040-44DF-9D1F-97281D9128ED@gmail.com>
            <49C8B459.5050201@telecom-bretagne.eu>
            <49C8C80B.3020504@elzevir.fr> <86eiwncer9.fsf@lola.quinscape.zz>
            <49C8D015.1070205@elzevir.fr>
            <49C8D320.3070400@telecom-bretagne.eu> <49C8D715.7020805@elzevir.fr>
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Mime-Version: 1.0 (iPhone Mail 5H11)
Content-Transfer-Encoding: 8bit
Message-ID:  <510AF2B3-466E-4362-BCEF-E53F4D0974BF@gmail.com>
Date:         Tue, 24 Mar 2009 23:40:19 +1030
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Will Robertson <wspr81@GMAIL.COM>
Subject: Re: inputenc for XeTeX and LuaTeX
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <49C8D715.7020805@elzevir.fr>
Precedence: list
Status: R

Hi all,

Don't forget that for utf8 encoded documents, the luatex and xetex  
inputenc packages do *not* mess around with active characters or  
whatever -- they prevent the legacy inputenc from doing so in the  
first place.

However, given any reservations I'd be happy enough with adapting  
inputenc to simply abort with an error if it's loaded with the new  
engines.

More comments requested, I possible.

Will

(Sent from my phone.)

On 24/03/2009, at 23:20, Manuel Pégourié-Gonnard <mpg@ELZEVIR.FR>  
wrote:

> Elie Roux a écrit :
>> In the future LuaTeX will probably replace pdfTeX, so inputenc will  
>> load
>> luainputenc. The question is not really to decide if it's good or  
>> not,
>
> Hmm...
>
>> it's to decide when we will do it. And I still can't really see why  
>> we
>> should wait three more years...
>>
> I don't mean waiting for three years. I just mean waiting enough to  
> be able to
> tidy up problems. Probably one year will be enough. Be a few months  
> (current
> time of luainputenc development/testing, iirc) are probably not  
> enough.
>
>> Just to repeat myself: (lua)inputenc is not optional in most cases,  
>> so
>> the user will have to load luainputenc. This means that people  
>> working
>> with LuaLaTeX will have to change their documents in 2012, replacing
>> luainputenc by inputenc...
>
> And that's perfectly ok if they need so, because you know you  
> possibly have to
> change a few names sometimes when you're using something under  
> developement.
> (And it doesn't mean only LuaTeX: I sometimes have to change my  
> documents in
> order to make them compile with a newer version of Koma-script, and  
> I accept
> that. If I don't want to have to worry about it, I use only the  
> standard
> classes, and I'm happy I have this choice too.)
>
> Anyway, I see no reason why luainputenc should stop working with  
> this name if it
> is later available as inputenc. A package can perfectly have  
> multiple names.
>
>> I know it's not 100% stable so users must
>> know what they're doing, but it still seems more annoying than the
>> miracle solution for stability...
>
> Well, it seems we disagree on what the future will be. In my future,  
> I want to
> be able to compile utf-8 encoded sources using Unicode fonts without  
> loading
> some sort of inputenc and making a bunch af character actives.
>
> Manuel.