Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
References: <20170731.162337.688577912214660894.wl@gnu.org>
Message-ID:  <A7E10047-826F-42DA-917E-483286207F0B@wspr.io>
Date:         Tue, 1 Aug 2017 00:15:07 +0930
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 <will@WSPR.IO>
Subject: Re: \usepackage problem with LaTeX 3
To:           LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <20170731.162337.688577912214660894.wl@gnu.org>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Content-Transfer-Encoding: 8bit
Status: R

Hi Werner,

The first thing you can do is to ask the fontspec person to update the package :)
But of course you have a broader point:

> On 31 Jul 2017, at 11:53 pm, Werner LEMBERG <wl@GNU.ORG> wrote:
> 
> To satisfy the LPPL I thought the right solution is to copy
> `fontspec.sty' to `fontspec-patched.sty', then applying the following
> change:

In fact, requiring a change to the filename is no longer written explicitly into the LPPL.
(Long story, don’t ever ask Frank how many emails it involved.)

You would be well within your rights to add something like the following to the top of your patched version of fontspec.sty:

    \typeout{This is Werner Lemberg’s altered copy of fontspec vX.X.}

The most important thing is that the altered code is clearly differentiated to the user as being altered from its original.

* * *

A possible alternative to your problem would be to trick LaTeX into thinking that you had already loaded fontspec.sty.
This would be done with something like:

    \expandafter\def\csname ver@fontspec.sty\endcsname{}

(Look into memoir.cls’s \EmulatedPackage code for more details.)

* * *

Hope this helps,
Will