3 files in lualibs: add comment characters

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

3 files changed, 159 insertions, 159 deletions

diff --git a/Master/texmf-dist/tex/luatex/lualibs/lualibs-basic.lua b/Master/texmf-dist/tex/luatex/lualibs/lualibs-basic.lua
index 630f2cce588..25b2cec3ba1 100644
--- a/Master/texmf-dist/tex/luatex/lualibs/lualibs-basic.lua
+++ b/Master/texmf-dist/tex/luatex/lualibs/lualibs-basic.lua
@@ -16,59 +16,59 @@
 --  
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-  By default, \identifier{lualibs} will not load the libraries individually.
-  Instead, it includes two \emphasis{merged packages} that have been compiled
-  from the original files.
-  This is achieved by means of \identifier{mtx-package}, a script for bundling
-  \LUA code shipped with \CONTEXT.
-  This concatenates the code of several \LUA files into a single file that is
-  both easier to distribute and loading (marginally) faster.
-  \identifier{mtx-package} ensures that the code from each file gets its
-  own closure and strips newlines and comments, resulting in a smaller payload.
-  Another package that relies on it heavily is the font loader as contained in
-  \identifier{luaotfload} and \identifier{luatex-fonts}.
-
-  If \CONTEXT is installed on the system, the merge files can be created
-  by running:
-
-  \begin{quote}\begin{verbatim}
-    mtxrun --script package --merge lualibs-basic.lua
-    mtxrun --script package --merge lualibs-extended.lua
-  \end{verbatim}\end{quote}
-
-  \noindent
-  Of course there is a make target for that:
-
-  \begin{quote}\begin{verbatim}
-    make merge
-  \end{verbatim}\end{quote}
-  \noindent
-  will take care of assembling the packages from the files distributed with
-  \identifier{lualibs}.
-
-  For this to work, the syntax of the \LUA file needs to be well-formed:
-  files that should be merged must be included via a function
-  \verb|loadmodule()|.
-  It doesn’t matter if the function actually does something; a dummy will
-  suffice.
-  Also, the argument to \verb|loadmodule()| must be wrapped in parentheses.
-  This rule is quite convenient, actually, since it allows excluding files
-  from the merge while still using \verb|loadmodule()| consistently.
-
-  \begin{quote}\begin{verbatim}
-    ...
-    loadmodule("my-lua-file.lua") -- <= will be merged
-    loadmodule('my-2nd-file.lua') -- <= will be merged
-    loadmodule "my-3rd-file.lua"  -- <= will be ignored
-    ...
-  \end{verbatim}\end{quote}
-
-  Note that there is one exception to the packaging:
-  \fileent{lualibs-util-jsn.lua} cannot be successfully packaged because
-  it follows a different coding convention, returning a \LUA table on exit.
-  Therefore, the file is loaded separately as part of the \identifier{extended}
-  set like any other \LUA module.
-
+-- By default, \identifier{lualibs} will not load the libraries individually.
+-- Instead, it includes two \emphasis{merged packages} that have been compiled
+-- from the original files.
+-- This is achieved by means of \identifier{mtx-package}, a script for bundling
+-- \LUA code shipped with \CONTEXT.
+-- This concatenates the code of several \LUA files into a single file that is
+-- both easier to distribute and loading (marginally) faster.
+-- \identifier{mtx-package} ensures that the code from each file gets its
+-- own closure and strips newlines and comments, resulting in a smaller payload.
+-- Another package that relies on it heavily is the font loader as contained in
+-- \identifier{luaotfload} and \identifier{luatex-fonts}.
+--
+-- If \CONTEXT is installed on the system, the merge files can be created
+-- by running:
+--
+-- \begin{quote}\begin{verbatim}
+--   mtxrun --script package --merge lualibs-basic.lua
+--   mtxrun --script package --merge lualibs-extended.lua
+-- \end{verbatim}\end{quote}
+--
+-- \noindent
+-- Of course there is a make target for that:
+--
+-- \begin{quote}\begin{verbatim}
+--   make merge
+-- \end{verbatim}\end{quote}
+-- \noindent
+-- will take care of assembling the packages from the files distributed with
+-- \identifier{lualibs}.
+--
+-- For this to work, the syntax of the \LUA file needs to be well-formed:
+-- files that should be merged must be included via a function
+-- \verb|loadmodule()|.
+-- It doesn’t matter if the function actually does something; a dummy will
+-- suffice.
+-- Also, the argument to \verb|loadmodule()| must be wrapped in parentheses.
+-- This rule is quite convenient, actually, since it allows excluding files
+-- from the merge while still using \verb|loadmodule()| consistently.
+--
+-- \begin{quote}\begin{verbatim}
+--   ...
+--   loadmodule("my-lua-file.lua") -- <= will be merged
+--   loadmodule('my-2nd-file.lua') -- <= will be merged
+--   loadmodule "my-3rd-file.lua"  -- <= will be ignored
+--   ...
+-- \end{verbatim}\end{quote}
+--
+-- Note that there is one exception to the packaging:
+-- \fileent{lualibs-util-jsn.lua} cannot be successfully packaged because
+-- it follows a different coding convention, returning a \LUA table on exit.
+-- Therefore, the file is loaded separately as part of the \identifier{extended}
+-- set like any other \LUA module.
+--
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/Master/texmf-dist/tex/luatex/lualibs/lualibs-extended.lua b/Master/texmf-dist/tex/luatex/lualibs/lualibs-extended.lua
index db1eef60720..91020868fc8 100644
--- a/Master/texmf-dist/tex/luatex/lualibs/lualibs-extended.lua
+++ b/Master/texmf-dist/tex/luatex/lualibs/lualibs-extended.lua
@@ -16,59 +16,59 @@
 --  
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-  By default, \identifier{lualibs} will not load the libraries individually.
-  Instead, it includes two \emphasis{merged packages} that have been compiled
-  from the original files.
-  This is achieved by means of \identifier{mtx-package}, a script for bundling
-  \LUA code shipped with \CONTEXT.
-  This concatenates the code of several \LUA files into a single file that is
-  both easier to distribute and loading (marginally) faster.
-  \identifier{mtx-package} ensures that the code from each file gets its
-  own closure and strips newlines and comments, resulting in a smaller payload.
-  Another package that relies on it heavily is the font loader as contained in
-  \identifier{luaotfload} and \identifier{luatex-fonts}.
-
-  If \CONTEXT is installed on the system, the merge files can be created
-  by running:
-
-  \begin{quote}\begin{verbatim}
-    mtxrun --script package --merge lualibs-basic.lua
-    mtxrun --script package --merge lualibs-extended.lua
-  \end{verbatim}\end{quote}
-
-  \noindent
-  Of course there is a make target for that:
-
-  \begin{quote}\begin{verbatim}
-    make merge
-  \end{verbatim}\end{quote}
-  \noindent
-  will take care of assembling the packages from the files distributed with
-  \identifier{lualibs}.
-
-  For this to work, the syntax of the \LUA file needs to be well-formed:
-  files that should be merged must be included via a function
-  \verb|loadmodule()|.
-  It doesn’t matter if the function actually does something; a dummy will
-  suffice.
-  Also, the argument to \verb|loadmodule()| must be wrapped in parentheses.
-  This rule is quite convenient, actually, since it allows excluding files
-  from the merge while still using \verb|loadmodule()| consistently.
-
-  \begin{quote}\begin{verbatim}
-    ...
-    loadmodule("my-lua-file.lua") -- <= will be merged
-    loadmodule('my-2nd-file.lua') -- <= will be merged
-    loadmodule "my-3rd-file.lua"  -- <= will be ignored
-    ...
-  \end{verbatim}\end{quote}
-
-  Note that there is one exception to the packaging:
-  \fileent{lualibs-util-jsn.lua} cannot be successfully packaged because
-  it follows a different coding convention, returning a \LUA table on exit.
-  Therefore, the file is loaded separately as part of the \identifier{extended}
-  set like any other \LUA module.
-
+-- By default, \identifier{lualibs} will not load the libraries individually.
+-- Instead, it includes two \emphasis{merged packages} that have been compiled
+-- from the original files.
+-- This is achieved by means of \identifier{mtx-package}, a script for bundling
+-- \LUA code shipped with \CONTEXT.
+-- This concatenates the code of several \LUA files into a single file that is
+-- both easier to distribute and loading (marginally) faster.
+-- \identifier{mtx-package} ensures that the code from each file gets its
+-- own closure and strips newlines and comments, resulting in a smaller payload.
+-- Another package that relies on it heavily is the font loader as contained in
+-- \identifier{luaotfload} and \identifier{luatex-fonts}.
+--
+-- If \CONTEXT is installed on the system, the merge files can be created
+-- by running:
+--
+-- \begin{quote}\begin{verbatim}
+--   mtxrun --script package --merge lualibs-basic.lua
+--   mtxrun --script package --merge lualibs-extended.lua
+-- \end{verbatim}\end{quote}
+--
+-- \noindent
+-- Of course there is a make target for that:
+--
+-- \begin{quote}\begin{verbatim}
+--   make merge
+-- \end{verbatim}\end{quote}
+-- \noindent
+-- will take care of assembling the packages from the files distributed with
+-- \identifier{lualibs}.
+--
+-- For this to work, the syntax of the \LUA file needs to be well-formed:
+-- files that should be merged must be included via a function
+-- \verb|loadmodule()|.
+-- It doesn’t matter if the function actually does something; a dummy will
+-- suffice.
+-- Also, the argument to \verb|loadmodule()| must be wrapped in parentheses.
+-- This rule is quite convenient, actually, since it allows excluding files
+-- from the merge while still using \verb|loadmodule()| consistently.
+--
+-- \begin{quote}\begin{verbatim}
+--  ...
+--   loadmodule("my-lua-file.lua") -- <= will be merged
+--   loadmodule('my-2nd-file.lua') -- <= will be merged
+--   loadmodule "my-3rd-file.lua"-- -- <= will be ignored
+--   ...
+-- \end{verbatim}\end{quote}
+--
+-- Note that there is one exception to the packaging:
+-- \fileent{lualibs-util-jsn.lua} cannot be successfully packaged because
+-- it follows a different coding convention, returning a \LUA table on exit.
+-- Therefore, the file is loaded separately as part of the \identifier{extended}
+-- set like any other \LUA module.
+--
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/Master/texmf-dist/tex/luatex/lualibs/lualibs.lua b/Master/texmf-dist/tex/luatex/lualibs/lualibs.lua
index 74eafba6878..c6f4d8a3963 100644
--- a/Master/texmf-dist/tex/luatex/lualibs/lualibs.lua
+++ b/Master/texmf-dist/tex/luatex/lualibs/lualibs.lua
@@ -16,59 +16,59 @@
 --  
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-  By default, \identifier{lualibs} will not load the libraries individually.
-  Instead, it includes two \emphasis{merged packages} that have been compiled
-  from the original files.
-  This is achieved by means of \identifier{mtx-package}, a script for bundling
-  \LUA code shipped with \CONTEXT.
-  This concatenates the code of several \LUA files into a single file that is
-  both easier to distribute and loading (marginally) faster.
-  \identifier{mtx-package} ensures that the code from each file gets its
-  own closure and strips newlines and comments, resulting in a smaller payload.
-  Another package that relies on it heavily is the font loader as contained in
-  \identifier{luaotfload} and \identifier{luatex-fonts}.
-
-  If \CONTEXT is installed on the system, the merge files can be created
-  by running:
-
-  \begin{quote}\begin{verbatim}
-    mtxrun --script package --merge lualibs-basic.lua
-    mtxrun --script package --merge lualibs-extended.lua
-  \end{verbatim}\end{quote}
-
-  \noindent
-  Of course there is a make target for that:
-
-  \begin{quote}\begin{verbatim}
-    make merge
-  \end{verbatim}\end{quote}
-  \noindent
-  will take care of assembling the packages from the files distributed with
-  \identifier{lualibs}.
-
-  For this to work, the syntax of the \LUA file needs to be well-formed:
-  files that should be merged must be included via a function
-  \verb|loadmodule()|.
-  It doesn’t matter if the function actually does something; a dummy will
-  suffice.
-  Also, the argument to \verb|loadmodule()| must be wrapped in parentheses.
-  This rule is quite convenient, actually, since it allows excluding files
-  from the merge while still using \verb|loadmodule()| consistently.
-
-  \begin{quote}\begin{verbatim}
-    ...
-    loadmodule("my-lua-file.lua") -- <= will be merged
-    loadmodule('my-2nd-file.lua') -- <= will be merged
-    loadmodule "my-3rd-file.lua"  -- <= will be ignored
-    ...
-  \end{verbatim}\end{quote}
-
-  Note that there is one exception to the packaging:
-  \fileent{lualibs-util-jsn.lua} cannot be successfully packaged because
-  it follows a different coding convention, returning a \LUA table on exit.
-  Therefore, the file is loaded separately as part of the \identifier{extended}
-  set like any other \LUA module.
-
+--  By default, \identifier{lualibs} will not load the libraries individually.
+--  Instead, it includes two \emphasis{merged packages} that have been compiled
+--  from the original files.
+--  This is achieved by means of \identifier{mtx-package}, a script for bundling
+--  \LUA code shipped with \CONTEXT.
+--  This concatenates the code of several \LUA files into a single file that is
+--  both easier to distribute and loading (marginally) faster.
+--  \identifier{mtx-package} ensures that the code from each file gets its
+--  own closure and strips newlines and comments, resulting in a smaller payload.
+--  Another package that relies on it heavily is the font loader as contained in
+--  \identifier{luaotfload} and \identifier{luatex-fonts}.
+--
+--  If \CONTEXT is installed on the system, the merge files can be created
+--  by running:
+--
+--  \begin{quote}\begin{verbatim}
+--    mtxrun --script package --merge lualibs-basic.lua
+--    mtxrun --script package --merge lualibs-extended.lua
+--  \end{verbatim}\end{quote}
+--
+--  \noindent
+--  Of course there is a make target for that:
+--
+--  \begin{quote}\begin{verbatim}
+--    make merge
+--  \end{verbatim}\end{quote}
+--  \noindent
+--  will take care of assembling the packages from the files distributed with
+--  \identifier{lualibs}.
+--
+--  For this to work, the syntax of the \LUA file needs to be well-formed:
+--  files that should be merged must be included via a function
+--  \verb|loadmodule()|.
+--  It doesn’t matter if the function actually does something; a dummy will
+--  suffice.
+--  Also, the argument to \verb|loadmodule()| must be wrapped in parentheses.
+--  This rule is quite convenient, actually, since it allows excluding files
+--  from the merge while still using \verb|loadmodule()| consistently.
+--
+--  \begin{quote}\begin{verbatim}
+--    ...
+--    loadmodule("my-lua-file.lua") -- <= will be merged
+--    loadmodule('my-2nd-file.lua') -- <= will be merged
+--    loadmodule "my-3rd-file.lua"  -- <= will be ignored
+--    ...
+--  \end{verbatim}\end{quote}
+--
+--  Note that there is one exception to the packaging:
+--  \fileent{lualibs-util-jsn.lua} cannot be successfully packaged because
+--  it follows a different coding convention, returning a \LUA table on exit.
+--  Therefore, the file is loaded separately as part of the \identifier{extended}
+--  set like any other \LUA module.
+--
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 lualibs = lualibs or { }