Lines: 24
References: <535FB8BC.2040409@nag.co.uk> <536078C4.5040103@googlemail.com>     
            <5360BAB2.4040600@nag.co.uk> <5360E19D.3020105@googlemail.com>
            <5360EEDE.2000306@nag.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
User-Agent: 40tude_Dialog/2.0.15.41de
Message-ID:  <19ge9u2gc02te.dlg@nililand.de>
Date:         Wed, 30 Apr 2014 14:59:04 +0200
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: Ulrike Fischer <news3@NILILAND.DE>
Subject: Re: preview of latex2e 2014 release
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

Am Wed, 30 Apr 2014 13:38:54 +0100 schrieb David Carlisle:

> yes agreed although rather than inputenc try to guess that the font 
> encoding isn't going to work it would probably be better if fontenc
> warned if it was on xe/latex with utf8 input encoding that it can't load 
> unicode fonts.

That's not a good idea. At first fontspec loads fontenc too, and so
you would get warnings even if the document (correctly) uses
fontspec. 

At second there are cases (e.g. chessfonts) where fontenc is needed
and useful even with xelatex or lualatex. 

fontenc could check 
- if it has been loaded after fontspec (that means \f@encoding is
EU1 or EU2). Normally this is not intended. 
- if at begin document \f@encoding is EU1 or EU2 and issue a warning
if not.
 

-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/