User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0)
            Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
References: <201503252123.t2PLN4Z2031134@freefriends.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Message-ID:  <55132CBA.10203@morningstar2.co.uk>
Date:         Wed, 25 Mar 2015 21:46:34 +0000
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: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: latex and unicode-letters
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <201503252123.t2PLN4Z2031134@freefriends.org>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On 25/03/2015 21:23, Karl Berry wrote:
>     saying words to the effect 'You better have a matching set of files'.
> 
> I agree.  And my point is that a user cannot know if the files are in
> fact "matching" unless you specify actual information about the files
> used to build.  A random version string like "7.0.0" is not enough to
> technically verify.  A checksum (ideal), a file size (good enough in
> practice), something that is specific to the actual content is needed.
> Otherwise it's just a guess.

Worth bearing in mind that only a small group of people need to actually
generate the processed data file (currently me). However, I will look at
this. I'd rather go with an automated solution if possible, so will
examine \pdfmdfivesum and/or Lua-based file size grabbing rather than
hand-editing if at all possible.

> Regarding the name: I like unicode-letters.def.

OK, that change is easy.

Depending on the time taken to do the file sums, this may take a little
while. I'll mail the list once it is done and there is a DropBox
snapshot showing it.

Joseph