nicefilelist (31oct12)

git-svn-id: svn://tug.org/texlive/trunk@28141 c570f23f-e606-0410-a88d-b1316a301751

2 files changed, 74 insertions, 26 deletions

diff --git a/Master/texmf-dist/tex/latex/nicefilelist/nicefilelist.RLS b/Master/texmf-dist/tex/latex/nicefilelist/nicefilelist.RLS
index 8b607c243c4..a6c36907693 100644
--- a/Master/texmf-dist/tex/latex/nicefilelist/nicefilelist.RLS
+++ b/Master/texmf-dist/tex/latex/nicefilelist/nicefilelist.RLS
@@ -1,4 +1,5 @@
 \ProvidesFile{nicefilelist.RLS}     %% RELEASE INFO
+   [{2012/10/30 r0.7 v0.7 [wrap] option}]
    [{2012/10/11 r0.6 v0.6 \string\MaxBaseEmptyList*}]
     [2012/10/01 r0.5 v0.5 \string\MaxBaseEmptyList]
     [{2012/05/20 r0.4 v0.4 Kabelschacht + [r] }]
diff --git a/Master/texmf-dist/tex/latex/nicefilelist/nicefilelist.sty b/Master/texmf-dist/tex/latex/nicefilelist/nicefilelist.sty
index 5e1a6787cd5..2ee4194c1cd 100644
--- a/Master/texmf-dist/tex/latex/nicefilelist/nicefilelist.sty
+++ b/Master/texmf-dist/tex/latex/nicefilelist/nicefilelist.sty
@@ -1,7 +1,6 @@
 \NeedsTeXFormat{LaTeX2e}[1994/12/01]
-\ProvidesPackage{nicefilelist}[2012/10/03 v0.6
+\ProvidesPackage{nicefilelist}[2012/10/30 v0.7
                                more file list alignment (UL)]
-
 %% Copyright (C) 2012 Uwe Lueck,
 %% http://www.contact-ednotes.sty.de.vu
 %% -- author-maintained in the sense of LPPL below --
@@ -17,11 +16,14 @@
 %%
 %%   http://www.contact-ednotes.sty.de.vu
 %%
-%% === Alignment Settings ===
+%% === Alignment Settings        ===
 %% \label{sec:templates}
 %% We use the \ctanpkgref{monofill} package for alignment of plain text:
-\RequirePackage{monofill}
+\RequirePackage{monofill}[2012/10/29]
 %% See its documentation for details.
+%% %% <- added 2012/10/29 ->
+%% The `[wrap]' option provided by 'nicefilelist' v0.7 requires 
+%% 'monofill' v0.2 as of 2012-10-29.
 %%
 %% We support three alignment ``fields" according to the terminology of \pkg{monofill}. 
 %% Their ids are |f-base| for base filenames, |f-ext| for filename extensions, 
@@ -46,8 +48,8 @@
 \newcommand*{\NFLspaceII} { \space}
 \newcommand*{\NFLspaceIII}{ }
 %% 
-%% === Failure Displays ===
-%% \label{sec:failure}
+%% === Failure Displays          ===
+%% \label{sec:fail}                 %% was failure 2012/10/29
 %% |\NFLnodate| is displayed in place of a file date if it seems 
 %% not to be given (configurable):
 \newcommand*{\NFLnodate}{ -- \space-- --}
@@ -61,23 +63,9 @@
 %% \cs{Provides.\empty..} command:
 \newcommand*{\NFLnotfound}{ * NOT FOUND *}
 %% 
-%% === Safe Tests ===
-%% \label{sec:safe}
-%% For fairly safe tests, we brief{}ly use an exotic version of `Q'
-%% (similarly to \ctanpkgref{ifmptarg}):
-\catcode`\Q=7 \let\NFL@criterion=Q \catcode`\Q=11
-%% %% 2012/03/27:
-%% It appears to me that expandable tests like the ones employed here 
-%% never are perfectly safe; you only can say that it is safe with a 
-%% source meeting certain conditions. \ctanpkgref{fifinddo} originally 
-%% was made for ``plain text," to be read from files without assigning 
-%% \TeX's special category codes. \emph{Here} we assume that the source 
-%% (text in \cs{Provides.\empty..} arguments) will never contain such a 
-%% ``funny `Q'".
-%%
-%% === Package Option `[r]' ===
+%% === Package Options           ===
 %% \label{sec:opt}
-%% v0.4 offers package option `[r]' that allows strings with `r' 
+%% v0.4 offers package option |[r]| that allows strings with `r' %% |...| 2012/10/30
 %% in place of `v', for ``release." `\NFL@v@digit''s definition
 %% therefore depends ... we use |\@listfiles| for a ``message" 
 %% there. For the original restricted functionality, it expands 
@@ -93,11 +81,64 @@
         \noexpand\NFL@false}%
   }%
 }
+%% v0.7 offers package option |[wrap]| for automatical wrapping within %% |...| 2012/10/30
+%% the "captions" column, based on Will Robertson's and Kevin Godby's 
+%% \ctanpkgref{hardwrap} package. The difference between this option 
+%% and the functionality without is controlled by the macro 
+%% `\NFL@filerow'. 
+%% %% 2012/10/30:
+%% \emph{Without} it expands to `\typeout'
+\newcommand*{\NFL@filerow}{\typeout}
+%% ---`\let' does'nt work with 'myfilist''s redefinition of 
+%% `\typeout'.
+%% \emph{With} `[wrap]', `\NFL@filerow' applies 'hardwrap''s 
+%% `\HardWrap':
+\DeclareOption{wrap}{%
+  \renewcommand*{\NFL@filerow}[1]{%
+    \HardWrap\typeout\hw@maxprintline\relax{^^J%
+      \MFrightinfield\space{f-base} %
+      \MFleftinfield \space{f-ext}%
+      \NFLspaceI\@spaces\space\@spaces\space \NFLspaceII
+      \MFrightinfield\space{f-version}\NFLspaceIII}{%
+      #1}}%
+%% Alignment of filenames with 'hardwrap' seems to need
+  \renewcommand*{\MFfillelement}{\MFotherspace}
+%% from \ctanpkgref{monospace} v0.2.
+}
+%% The display width is controlled by 'hardwrap''s counter 
+%% `\hw@maxprintline'. Unless 'hardwrap' finds something special, 
+%% its content is 79, corresponding to a display width of 
+%% 80 characters (I believe---counting the leftmost character 
+%%  as \qtd{0}, as editors like to do). You can choose a different 
+%% content value <max-char-col> by 'hardwrap''s
+%% \[|\setmaxprintline{<max-char-col>}|\]
 \ProcessOptions
+%% The next `\ifx' is to check whether `[wrap]' has been demanded 
+%% and 'hardwrap' is needed:
+\ifx\NFL@filerow\typeout \else
+  \RequirePackage{hardwrap}
+\fi
 %% 
+%% === Safe Tests                === %% below options 2012/10/29
+%% \label{sec:safe}
+%% For fairly safe tests, we brief{}ly use an exotic version of `Q'
+%% (similarly to \ctanpkgref{ifmptarg} and \ctanpkgref{url}):
+\catcode`\Q=7 \let\NFL@criterion=Q \catcode`\Q=11
+%% %% 2012/03/27:
+%% It appears to me that expandable tests like the ones employed here 
+%% never are perfectly safe; you only can say that it is safe with a 
+%% source meeting certain conditions. \ctanpkgref{fifinddo} originally 
+%% was made for ``plain text," to be read from files without assigning 
+%% \TeX's special category codes. \emph{Here} we assume that the source 
+%% (text in \cs{Provides.\empty..} arguments) will never contain such a 
+%% ``funny `Q'".
+%%
 %% === Redefining \cs{listfiles} ===
 %% Similarly to original \LaTeX, |\listfiles| carries almost everything 
-%% that is needed for the file list only:
+%% that is needed for the file list only. 2012-10-29: little point 
+%% in this, perhaps, in that the package should be loaded when 
+%% running `\listfiles' is intended---TODO. Or maybe it is loaded 
+%% \emph{just in case?}
 \renewcommand*{\listfiles}{%
   \let\listfiles\relax
 %% ---this clears memory. Now \LaTeX\ doesn't collect file names for 
@@ -127,7 +168,7 @@
        \edef\@tempa{\filename@area\filename@base}%
 %% Actually I would like to be able to do even the filename parsing 
 %% expandably---for all systems, `texsys.cfg'!?? TODO
-       \typeout{%
+       \NFL@filerow{%
 %% Now all parsing and checking must be expandable.
          \NFL@make@macro@arg\MFrightinfield\@tempa      {f-base}.%
          \NFL@make@macro@arg\MFleftinfield \filename@ext{f-ext}%
@@ -262,7 +303,7 @@
                    {\NFL@place@version{##1}\NFLspaceIII##2}%
                    {\NFLnoversion@\NFLspaceIII##1 ##2}}%
 }
-%% === Shorthand for 'myfilist' ===
+%% === Shorthand for 'myfilist'  ===
 %% \[|\MaxBaseEmptyList{<longest-name>}[<read-again-files>]|\]
 %% (v0.5) or 
 %% \[|\MaxBaseEmptyList*[<read-again-files>]|\]
@@ -275,7 +316,7 @@
 %% So |\maxBaseEmptyList| is like former `\MaxBaseEmptyList'
 %% without expecting a star---available to users.
 %%
-%% === Leaving the Package File ===
+%% === Leaving the Package File  ===
 \endinput
 %%
 %% === VERSION HISTORY ===
@@ -306,3 +347,9 @@ v0.4   2012/05/20   option [r]
 v0.5   2012/09/30   \MaxBaseEmptyList
 v0.6   2012/10/03   \MaxBaseEmptyLists first arg. only optional
        2012/10/11   ... bad with 2nd opt. arg., *
+v0.7   2012/10/13   "updating" date in \Provides...!
+       2012/10/28   \HardWrap first try 
+       2012/10/29   \HardWrap newline material -> [wrap]
+                    sec:test below sec:opt, mentioning `url'
+       2012/10/30   correcting \NFL@filerow without wrapping, 
+                    doc.: |...| in sec:opt