LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Tue, 14 Feb 2006 19:09:13 +0100
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=us-ascii
From: Frank Mittelbach <[log in to unmask]>
Parts/Attachments: text/plain (35 lines)

 > . The files `report.cls', `size10.clo', `size11.clo', and `size12.clo'
 >   from the last LaTeX release identify themselves as
 >     2004/02/16 v1.4f
 >   while the new version uses
 >     2005/09/16 v1.4f
 >   I suggest to increase the version number to, say, 1.4g.

the convention we follow (normally at least) is as follows:

 - version number and date changes where there is any code change
 - but in case of documentation change we only change the date

so in other words the date reflects the state of the documentation while the
version reflects the state of the code (ie what appears to be in the file
after docstrip)

whether that is wise, would require public stating ... I don't know, but the
rational is: if you tell me you run 1.4f then i know that codewise you are
good even if you may not have the dtx that has additional info

 > . For the creation of encguide.pdf I would be glad to see all
 >   available fonts in the PDF document -- more than have been used in
 >   the PDF file from the beta test bundle.

which fonts do you miss?