summaryrefslogtreecommitdiff
path: root/macros
diff options
context:
space:
mode:
Diffstat (limited to 'macros')
-rw-r--r--macros/latex/contrib/authoraftertitle/README.md12
-rw-r--r--macros/latex/contrib/authoraftertitle/authoraftertitle.pdfbin121340 -> 113957 bytes
-rw-r--r--macros/latex/contrib/authoraftertitle/authoraftertitle.sty7
-rw-r--r--macros/latex/contrib/authoraftertitle/authoraftertitle.tex6
-rw-r--r--macros/latex/contrib/caption/README2
-rw-r--r--macros/latex/contrib/caption/caption3.dtx74
-rw-r--r--macros/latex/contrib/derivative/README.md2
-rw-r--r--macros/latex/contrib/derivative/derivative.pdfbin184454 -> 185397 bytes
-rw-r--r--macros/latex/contrib/derivative/derivative.sty8
-rw-r--r--macros/latex/contrib/derivative/derivative.tex29
-rw-r--r--macros/luatex/generic/luaxml/README2
-rw-r--r--macros/luatex/generic/luaxml/luaxml-domobject.lua7
-rw-r--r--macros/luatex/generic/luaxml/luaxml-namedentities.lua3
-rw-r--r--macros/luatex/generic/luaxml/luaxml.pdfbin98710 -> 99665 bytes
-rw-r--r--macros/luatex/generic/luaxml/luaxml.tex18
-rw-r--r--macros/xetex/latex/xepersian-hm/INSTALL.txt2
-rw-r--r--macros/xetex/latex/xepersian-hm/xepersian-hm-doc.ltx6
-rw-r--r--macros/xetex/latex/xepersian-hm/xepersian-hm-doc.pdfbin268013 -> 267978 bytes
-rw-r--r--macros/xetex/latex/xepersian-hm/xepersian-hm.dtx22
-rw-r--r--macros/xetex/latex/xepersian-hm/xepersian-hm.pdfbin59687 -> 59544 bytes
20 files changed, 136 insertions, 64 deletions
diff --git a/macros/latex/contrib/authoraftertitle/README.md b/macros/latex/contrib/authoraftertitle/README.md
new file mode 100644
index 0000000000..6155e5c2fe
--- /dev/null
+++ b/macros/latex/contrib/authoraftertitle/README.md
@@ -0,0 +1,12 @@
+# authoraftertitle
+
+This very simple package provides a simple way of having the autor, title and date availble after the titlepage.
+
+## Usage
+
+Use `\MyAuthor`, `\MyTitle` and `\MyData` as on the title page in your document, even after the titlepage.
+The original definitions of \verb+\author+, \verb+\title+ and \verb+\date+ can be accessed using \verb+\Originalauthor+, \verb+\Originaltitle+ and \verb+\Originaldate+.
+
+
+## Author
+Matthias Bilger <matthias@bilger.info>
diff --git a/macros/latex/contrib/authoraftertitle/authoraftertitle.pdf b/macros/latex/contrib/authoraftertitle/authoraftertitle.pdf
index f01f8669a4..9888fa0fd0 100644
--- a/macros/latex/contrib/authoraftertitle/authoraftertitle.pdf
+++ b/macros/latex/contrib/authoraftertitle/authoraftertitle.pdf
Binary files differ
diff --git a/macros/latex/contrib/authoraftertitle/authoraftertitle.sty b/macros/latex/contrib/authoraftertitle/authoraftertitle.sty
index 47b87a27f6..96618a0660 100644
--- a/macros/latex/contrib/authoraftertitle/authoraftertitle.sty
+++ b/macros/latex/contrib/authoraftertitle/authoraftertitle.sty
@@ -1,8 +1,11 @@
% Author Matthias Bilger
-% License: This package is released to the Public Domain
+% Version 1.0
+% License:
+% This work by Matthias Bilger is licensed under CC0 1.0.
+% To view a copy of this license, visit https://creativecommons.org/publicdomain/zero/1.0
\NeedsTeXFormat{LaTeX2e}
-\ProvidesPackage{authoraftertitle}[2006/10/14 v0.9 package for Author after Titlepage]
+\ProvidesPackage{authoraftertitle}[2020/07/20 v1.0 package for Author after Titlepage]
%Author
\newcommand\Originalauthor{}
\let\Originalauthor\author
diff --git a/macros/latex/contrib/authoraftertitle/authoraftertitle.tex b/macros/latex/contrib/authoraftertitle/authoraftertitle.tex
index 0c2296f814..e2ec4de009 100644
--- a/macros/latex/contrib/authoraftertitle/authoraftertitle.tex
+++ b/macros/latex/contrib/authoraftertitle/authoraftertitle.tex
@@ -1,10 +1,12 @@
+% This work by Matthias Bilger is licensed under CC0 1.0.
+% To view a copy of this license, visit https://creativecommons.org/publicdomain/zero/1.0
\documentclass[pagesize=auto]{scrartcl}
\addtokomafont{title}{\rmfamily}
-\title{The \textsf{authoraftertitle} package\thanks{This manual corresponds to \textsf{authoraftertitle.sty} v0.9, dated~2006/10/14.}}
+\title{The \textsf{authoraftertitle} package\thanks{This manual corresponds to \textsf{authoraftertitle.sty} v1.0, dated~2020/07/20.}}
\author{Matthias Bilger}
-\date{2006/10/14}
+\date{2020/07/20}
\begin{document}
diff --git a/macros/latex/contrib/caption/README b/macros/latex/contrib/caption/README
index 080116df65..721eab665a 100644
--- a/macros/latex/contrib/caption/README
+++ b/macros/latex/contrib/caption/README
@@ -1,7 +1,7 @@
==========================================================================
The `caption' package bundle
-Release 2020-07-19
+Release 2020-07-20
Copyright (C) 1994-2020 Axel Sommerfeldt (axel.sommerfeldt@f-m.fm)
License: LPPL = LaTeX Project Public Licence
diff --git a/macros/latex/contrib/caption/caption3.dtx b/macros/latex/contrib/caption/caption3.dtx
index 031c84fa67..8edc856461 100644
--- a/macros/latex/contrib/caption/caption3.dtx
+++ b/macros/latex/contrib/caption/caption3.dtx
@@ -28,7 +28,7 @@
% caption-deu.tex, caption-eng.tex, caption-rus.tex.
%
% \fi
-% \CheckSum{3585}
+% \CheckSum{3606}
%
% \iffalse
%<*driver>
@@ -191,7 +191,7 @@
%
% \begin{macrocode}
\NeedsTeXFormat{LaTeX2e}[1994/12/01]
-\ProvidesPackage{caption3}[2020/07/19 v1.12a caption3 kernel (AR)]
+\ProvidesPackage{caption3}[2020/07/20 v1.12b caption3 kernel (AR)]
% \end{macrocode}
%
% \section{Workaround for bug in package \package{arabtex}}
@@ -742,14 +742,15 @@
% \begin{macrocode}
\newcommand*\@captionsetup[1]{%
\captionsetup@startrue#1\captionsetup@starfalse
- \@ifnextchar[\caption@setup@options\caption@setup}
+ \@ifnextchar[%]
+ \caption@setup@options\caption@setup}
% \end{macrocode}
% \begin{macrocode}
\newcommand*\caption@setup{\caption@setkeys{caption}}
% \end{macrocode}
% \begin{macrocode}
\def\caption@setup@options[#1]{%
- \@ifnextchar[%
+ \@ifnextchar[%]
{\caption@stepthecounter
\caption@withoptargs{\@expandtwoargs
\caption@setup@options@i{#1}{@\caption@thecounter}}}%
@@ -3635,6 +3636,7 @@
% \changes{v1.8}{2018/05/16}{Redefinition of \cs{acused} added}
% \changes{v1.8}{2018/05/26}{Definition method changed so it can be pre-defined by other packages}
% \changes{v1.8}{2018/05/27}{Redefinition of \cs{hypertarget} added}
+% \changes{v1.12b}{2020/07/20}{Special adaption to \class{beamer} added}
% |\caption@prepareslc|\par
% Re-define anything which would disturb the single-line-check.
% \begin{macrocode}
@@ -3643,16 +3645,32 @@
\let\label\caption@gobble
\let\hypertarget\@gobbletwo
% \end{macrocode}
+% We re-define \cs{footnote} so
+% \begin{enumerate}
+% \item The footnote counter will not be increased twice (but still the correct footnote mark will be used within the single-line-check)
+% \item The footnote text will not be evaluated twice
+% \end{enumerate}
% \begin{macrocode}
- \let\caption@endnotemark@ORI\endnotemark
+ \let\caption@footnote@ORI\footnote
+ \def\footnote{\caption@withoptargs\caption@footnote}%
+ \let\caption@footnotemark@ORI\footnotemark
+ \def\footnotemark{\caption@withoptargs\caption@footnotemark}%
+ \let\caption@footnotetext@ORI\@footnotetext
+ \let\@footnotetext\caption@gobble
+% \end{macrocode}
+% Same for \cs{endnote}
+% \begin{macrocode}
+ \let\caption@endnote@ORI\endnote
\def\endnote{\caption@withoptargs\caption@endnote}%
+ \let\caption@endnotemark@ORI\endnotemark
\def\endnotemark{\caption@withoptargs\caption@endnotemark}%
+ \let\caption@endnotetext@ORI\@endnotetext
\let\@endnotetext\caption@gobble
% \end{macrocode}
% \begin{macrocode}
\let\pagenote\caption@gobble
% \end{macrocode}
-% Adaption to the \package{acronym} package.\par
+% Adaption to the \package{acronym} package\par
% See also \url{https://tex.stackexchange.com/questions/428788}
% \begin{macrocode}
\let\acused\@gobble
@@ -3671,43 +3689,50 @@
% \begin{macrocode}
}
% \end{macrocode}
-%
-% The following patch of \cs{footnote} assumes that the optional arguments of
-% \cs{footnote} and \cs{footnotemark} match. Since this is not the case in
-% \class{beamer} based documents, and since \class{beamer} extents the
-% syntax of \cs{footnote} in a way we don't support, we don't apply the patch there.
-% \begin{macrocode}
-\caption@ifclassloaded{beamer}{}{%
- \g@addto@macro\caption@prepareslc{%
- \let\caption@footnote@ORI\footnote
- \def\footnote{\caption@withoptargs\caption@footnote}%
- \let\caption@footnotemark@ORI\footnotemark
- \def\footnotemark{\caption@withoptargs\caption@footnotemark}%
- \let\caption@footnotetext@ORI\@footnotetext
- \let\@footnotetext\caption@gobble}}
-% \end{macrocode}
% \begin{macrocode}
\newcommand\caption@footnote[2]{%
\caption@footnotemark{#1}}
+% \end{macrocode}
+% \begin{macrocode}
\newcommand\caption@footnotemark[1]{%
\begingroup
\let\stepcounter\caption@l@stepcounter
- \caption@footnotemark@ORI#1%
+ \caption@footnotemark@ORI#1\relax
\endgroup}
% \end{macrocode}
% \begin{macrocode}
\newcommand\caption@endnote[2]{%
\caption@endnotemark{#1}}
+% \end{macrocode}
+% \begin{macrocode}
\newcommand\caption@endnotemark[1]{%
\begingroup
\let\stepcounter\caption@l@stepcounter
- \caption@endnotemark@ORI#1
+ \caption@endnotemark@ORI#1\relax
\endgroup}
% \end{macrocode}
% \begin{macrocode}
\newcommand*\caption@l@stepcounter[1]{%
\advance\csname c@#1\endcsname\@ne\relax}
% \end{macrocode}
+% The patch above assumes that the optional arguments of \cs{footnote} and
+% \cs{footnotemark} match. Since this is not the case in \class{beamer} based documents,
+% and since \class{beamer} extents the syntax of \cs{footnote} in a special way,
+% we need a special patch here.\par
+% \emph{Note:} For this patch we assume that \cs{footnote} will always end with the usage of
+% \cs{beamer@footnotetext}. (Unfortunately \cs{footnote} is defined too monolithic
+% in \class{beamer} to offer a less dirty patch.)
+% \begin{macrocode}
+\caption@ifclassloaded{beamer}{%
+ \g@addto@macro\caption@prepareslc{%
+ \def\footnote{%
+ \begingroup
+ \let\stepcounter\caption@l@stepcounter
+ \renewcommand<>\beamer@framefootnotetext[1]{%
+ \endgroup}%
+ \let\@footnotetext\beamer@framefootnotetext
+ \caption@footnote@ORI}}}{}
+% \end{macrocode}
% \end{macro}
%
% \begin{macro}{\caption@applyfont}
@@ -4113,7 +4138,8 @@
% |\caption@For|\marg{elt-list}\marg{code with \#1}\\
% |\caption@For*|\marg{elt-list}\marg{code with \#1}
% \begin{macrocode}
-\newcommand*\caption@For{\caption@withoptargs\caption@@For}
+\newcommand*\caption@For{%
+ \caption@withoptargs\caption@@For}
%\@onlypreamble\caption@For
% \end{macrocode}
% \begin{macrocode}
diff --git a/macros/latex/contrib/derivative/README.md b/macros/latex/contrib/derivative/README.md
index 308e79be32..8d35e94523 100644
--- a/macros/latex/contrib/derivative/README.md
+++ b/macros/latex/contrib/derivative/README.md
@@ -1,4 +1,4 @@
-## README for derivative package v0.97 dated 2019-02-03
+## README for derivative package v0.98 dated 2020-07-20
The package provides a set of commands `\NewOdvVariant`, `\NewPdvVariant` etc. that can be used to define a variant of a derivative. The package have already defined several derivatives:
diff --git a/macros/latex/contrib/derivative/derivative.pdf b/macros/latex/contrib/derivative/derivative.pdf
index dae8b7dede..1298760f22 100644
--- a/macros/latex/contrib/derivative/derivative.pdf
+++ b/macros/latex/contrib/derivative/derivative.pdf
Binary files differ
diff --git a/macros/latex/contrib/derivative/derivative.sty b/macros/latex/contrib/derivative/derivative.sty
index d410254931..a30dad465f 100644
--- a/macros/latex/contrib/derivative/derivative.sty
+++ b/macros/latex/contrib/derivative/derivative.sty
@@ -16,7 +16,7 @@
\NeedsTeXFormat{LaTeX2e}
\RequirePackage{xparse}[2018/05/09]
-\ProvidesExplPackage{derivative}{2020/02/03}{0.97}{Nice and easy derivatives}
+\ProvidesExplPackage{derivative}{2020/07/20}{0.98}{Nice and easy derivatives}
%%%%% Useful conditionals %%%%%
@@ -451,7 +451,8 @@
% dv , new/delare/renew/provide , macro , inf
\cs_new_protected:Npn \deriv_d_define:nnnn #1 #2 #3 #4
{
- \use:c { #2 DocumentCommand }{#3}{ s o m t/ m !e{\sb^} }
+ \exp_args:Nnnx
+ \use:c { #2 DocumentCommand }{#3}{ s o m t/ m !e{\char_generate:nn {`_}{8}^} }
{
\group_begin:
\exp_args:Nnc \bool_xor:nnTF {##4} { l__deriv_#1_switch_slash_bool }
@@ -484,7 +485,8 @@
% dv , new/delare/renew/provide , macro , inf
\cs_new_protected:Npn \deriv_p_define:nnnn #1 #2 #3 #4
{
- \use:c { #2 DocumentCommand }{#3}{ s o o m t/ m !e{\sb^} }
+ \exp_args:Nnnx
+ \use:c { #2 DocumentCommand }{#3}{ s o o m t/ m !e{\char_generate:nn {`_}{8}^} }
{
\group_begin:
\exp_args:Nnc \bool_xor:nnTF {##5} { l__deriv_#1_switch_slash_bool }
diff --git a/macros/latex/contrib/derivative/derivative.tex b/macros/latex/contrib/derivative/derivative.tex
index 30eaab1bee..ef36ef2fe9 100644
--- a/macros/latex/contrib/derivative/derivative.tex
+++ b/macros/latex/contrib/derivative/derivative.tex
@@ -1082,8 +1082,8 @@
\Titel{The \pakkenavn{} package}
\Forfatter{Simon Jensen}
\Email{sjelatex@gmail.com}
-\Dato{2019/02/03}
-\Version{0.97}
+\Dato{2020/07/20}
+\Version{0.98}
\RequirePackage{derivative}[\dato]
\derivset{all}[scale-auto = mleftmright]
@@ -2063,14 +2063,14 @@
\item The sorting by \val{abs} separates the terms by their absolute value, where the terms are ordered in a descending manner according to their absolute value. Using the option \keyval{sort-abs-reverse}{true}, then the terms are ordered in an ascending manner instead.
\end{itemize}
- When using the option \keyval{sort-method}{\{...\}}, the number of algorithms determines the number of layers e.g. \keyval{sort-method}{sign,symbol} is a sorting method with two layers, where the algorithms \val{sign} and \val{symbol} are applied in layer \num{1} and layer \num{2}, respectively. It should be understood as that the \val{sign} algorithm splits the terms into two groups, one with positive terms and one with negative terms. Then the \val{symbol} algorithm will order the terms within each groups according to the terms symbolic length. The mixed order is then formed by combining these two groups such that the positive terms comes first.
+ When using the option \keyval{sort-method}{\{...\}}, the number of algorithms determines the number of layers e.g. \keyval{sort-method}{\{sign,symbol\}} is a sorting method with two layers, where the algorithms \val{sign} and \val{symbol} are applied in layer \num{1} and layer \num{2}, respectively. It should be understood as that the \val{sign} algorithm splits the terms into two groups, one with positive terms and one with negative terms. Then the \val{symbol} algorithm will order the terms within each groups according to the terms symbolic length. The mixed order is then formed by combining these two groups such that the positive terms comes first.
The next subsubsection is dedicated to give some examples of how the algorithms in this package sorts the mixed order.
\subsubsection{Examples}
The examples are constructed of a partial derivative with the comma separated list of orders given by \texttt{[3a-3hh-2b, 4c+4gg+2ff, -5d-5ee]} and a close up view of the mixed order. Square brackets are used to indicate grouping of terms and the text below a group refers to the algorithm applied. Here the words positive and negative, long and short, and big and low refers to the \val{sign}, \val{symbol}, and \val{abs} algorithms, respectively. A row of square brackets represents a layer.
- The packages default sorting method is \keyval{sort-method}{sign,symbol,abs}, which is used below. The \val{sign} algorithm separate the positive and negative terms in the first layer. While in the second layer, the terms are separated by symbol length etc.
+ The packages default sorting method is \keyval{sort-method}{\{sign,symbol,abs\}}, which is used below. The \val{sign} algorithm separate the positive and negative terms in the first layer. While in the second layer, the terms are separated by symbol length etc.
\begin{equation*}
\derivset{\pdv}[sort-method = {sign,symbol,abs}]
\pdv[3a-3hh-2b, 4c+4gg+2ff, -5d-5ee]{f}{x,y,z}
@@ -2097,7 +2097,7 @@
}{short}
}{negative}
\end{equation*}
- as expected. Interchanging \val{sign} and \val{symbol} algorithms from the previous example i.e \keyval{sort-method}{symbol, sign, abs}, then the \val{symbol} \cal{sign} algorithms are now applied in the first and second layer, respectively. The result is shown below
+ as expected. Interchanging \val{sign} and \val{symbol} algorithms from the previous example i.e \keyval{sort-method}{\{symbol,sign,abs\}}, then the \val{symbol} \cal{sign} algorithms are now applied in the first and second layer, respectively. The result is shown below
\begin{equation*}
\derivset{\pdv}[sort-method = {symbol,sign,abs}]
\pdv[3a-3hh-2b, 4c+4gg+2ff, -5d-5ee]{f}{x,y,z}
@@ -2126,7 +2126,7 @@
\end{equation*}
where a clear difference is seen between the above two examples.
- The above two examples used 3-layer sorting methods but as mentioned earlier, the sorting method can also be constructed with one and two algorithms i.e. 1-layer and 2-layer sorting methods. A sorting method with two layers could be constructed as \keyval{sort-method}{sign,symbol} and with it, the terms are ordered by sign and then symbolic length. In this case, there is not a third layer. Instead, the terms \enquote{appear randomly} according to their absolute value as shown below
+ The above two examples used 3-layer sorting methods but as mentioned earlier, the sorting method can also be constructed with one and two algorithms i.e. 1-layer and 2-layer sorting methods. A sorting method with two layers could be constructed as \keyval{sort-method}{\{sign,symbol\}} and with it, the terms are ordered by sign and then symbolic length. In this case, there is not a third layer. Instead, the terms \enquote{appear randomly} according to their absolute value as shown below
\begin{equation*}
\derivset{\pdv}[sort-method = {sign,symbol}]
\pdv[3a-3hh-2b, 4c+4gg+2ff, -5d-5ee]{f}{x,y,z}
@@ -2223,7 +2223,7 @@
\clearpage
\section{To do}\label{sec:todo}
- Entries marked with \cmark{} will be implemented in a future release specified in the entry. Entries marked with \xmark{} will not be implemented.
+ Entries marked with \cmark{} will be implemented in a future release. Entries marked with \xmark{} will not be implemented.
\subsection{Future implementation}
The list describes what \emph{will be added} to the package in a later release.
@@ -2247,10 +2247,10 @@
%
\item Such an option should not be possible to be set with \macro[index=false]{\derivset} or in the definition of a new derivative (or maybe if one really needs a lot of higher order derivative).
\end{itemize}
- \answer{\cmark}{I truly believe this is the right way forward and is coming in the next release. More features can easily be added in a key-value style. The order argument will be replaced with a key-value argument and a order key introduced; \texttt{ord=\meta{order}}.}
+ \answer{\cmark}{I truly believe this is the right way forward and is coming in version 1.0. More features can easily be added in a key-value style. The order argument will be replaced with a key-value argument and a order key introduced; \texttt{ord=\meta{order}}.}
%
\item With the above consideration, than it would only be natural to remove the mixed order and then have an option \keyval[index=false]{mixed-order}{\marg{mixed-order}}. Likewise, it should not be possible to be set with \macro[index=false]{\derivset} or in the definition of a new derivative. \label{consid:RemoveMixedOrder} \\
- \answer{\cmark}{The mixed order argument will be removed due to the introduction of a key-value argument as mentioned above in the next release. The mixed order can be set with the knew key \texttt{m-ord=\meta{mixed-order}}.}
+ \answer{\cmark}{The mixed order argument will be removed due to the introduction of a key-value argument as mentioned above in version 1.0. The mixed order can be set with the knew key \texttt{m-ord=\meta{mixed-order}}.}
%
\item Currently \macro[index=false]{\derivset}'s optional argument \oarg{key=val}, when not given, sets the derivatives options to the package default settings. This should probably be changed to the options set in the definition of the derivative. \label{consid:DerivsetOptional} \\
\answer{\cmark}{I believe this would a nice change for the future, but I do not have the time to make the implementation for the next release.}
@@ -2263,13 +2263,13 @@
\answer{\cmark}{This have already been changed in version 0.95, since it is an unnecessary constraint.}
%
\item Should I add the option to \key[index=false]{sort-numerical}, so that it is treated as a symbolic term instead of a numerical term? \label{consid:sort_numerical}
- \\ \answer{\cmark}{Yes. Yes I should. This feature will be added in the next release.}
+ \\ \answer{\cmark}{Yes. Yes I should. This feature will be added in version 1.0.}
%
\item Should I add a sorting algorithm that order the terms according to their number (including sign)? \label{consid:sort_number}
- \\ \answer{\cmark}{Yes. Yes I should. This feature will be added in the next release.}
+ \\ \answer{\cmark}{Yes. Yes I should. This feature will be added in version 1.0.}
%
\item I am considering making the optional argument of \macro[index=false]{\slashfrac} into a \oarg{key=value} argument with something like \keyval[index=false]{scale}{\marg{scaling}}. \label{consid:slashfrac_opt} \\
- \answer{\cmark}{I want an key-value implementation like this in the future, but it will not be added it the next release.}
+ \answer{\cmark}{I want an key-value implementation like this in the future, but it will not be added it version 1.0.}
%
\item Should the default scaling for \macro[index=false]{\slashfrac} be \val{auto} or \val{none}? Or should it be possible to set it with something like \cs{slashfracset}\oarg{key=value}? \label{consid:slashfrac_def_scale} \\
\answer{\xmark}{The package default should be \val{auto}, but it will be possible to change it, when the key-value is implemented or \macro[index=false]{\slashfrac}.}
@@ -2316,8 +2316,13 @@
\begin{change}[version = 0.96, date = 2019-12-22, beta = true]
\item Fixed the double superscript issue for higher order derivative when the variable contained a superscript.
\end{change}
+ \smallskip
\begin{change}[version = 0.97, date = 2020-02-03, beta = true]
\item Fixed the argument specifier of {\small\verb|\__deriv_scale_big:nnnn|} when it was used (it was used with \texttt{:nnnm}).
\end{change}
+ \smallskip
+ \begin{change}[version = 0.98, date = 2020-07-20, beta = true]
+ \item Fixed a bug concerning the subscript argument due to recent changes to the \pkg{xparse} package dated 2020-05-14 (the fix works with earlier versions of xparse as well).
+ \end{change}
\end{changelog}
\end{document} \ No newline at end of file
diff --git a/macros/luatex/generic/luaxml/README b/macros/luatex/generic/luaxml/README
index 897968a391..ab8a407dd0 100644
--- a/macros/luatex/generic/luaxml/README
+++ b/macros/luatex/generic/luaxml/README
@@ -28,7 +28,7 @@ Author
------
Michal Hoftich
Email: michal.h21@gmail.com
-Version: 0.1l, 2019-09-16
+Version: v0.1m, 2020-07-19
Original authors: Paul Chakravarti and Manoel Campos (http://manoelcampos.com)
diff --git a/macros/luatex/generic/luaxml/luaxml-domobject.lua b/macros/luatex/generic/luaxml/luaxml-domobject.lua
index 413947b5d4..6d299d4157 100644
--- a/macros/luatex/generic/luaxml/luaxml-domobject.lua
+++ b/macros/luatex/generic/luaxml/luaxml-domobject.lua
@@ -115,7 +115,12 @@ local function serialize_dom(parser, current,level, output)
attributes["_text"] = nil
elseif xtype == "DECL" and name =="xml" then
-- the xml declaration attributes must be in a correct order
- insert("<?xml version='%s' encoding='%s' ?>", attributes.version, attributes.encoding)
+ local encoding = attributes.encoding or "utf-8"
+ insert("<?xml version='%s' encoding='%s' ?>", attributes.version, encoding)
+ return output
+ elseif xtype == "CDATA" then
+ -- return content unescaped
+ insert(string.format("<![CDATA[%s]]>", text_content))
return output
end
diff --git a/macros/luatex/generic/luaxml/luaxml-namedentities.lua b/macros/luatex/generic/luaxml/luaxml-namedentities.lua
index dbbed79ce0..9a26f448f6 100644
--- a/macros/luatex/generic/luaxml/luaxml-namedentities.lua
+++ b/macros/luatex/generic/luaxml/luaxml-namedentities.lua
@@ -1,3 +1,4 @@
+local utf8 = require "utf8"
return {
["Subset"]="⋐",
["Chi"]="Χ",
@@ -39,7 +40,7 @@ return {
["nsqsube"]="⋢",
["Nacute"]="Ń",
["mcomma"]="⨩",
-["ApplyFunction"]="⁡",
+["ApplyFunction"]=utf8.char(8289),
["rfisht"]="⥽",
["phmmat"]="ℳ",
["rarrw"]="↝",
diff --git a/macros/luatex/generic/luaxml/luaxml.pdf b/macros/luatex/generic/luaxml/luaxml.pdf
index 6b53c44891..86aa928593 100644
--- a/macros/luatex/generic/luaxml/luaxml.pdf
+++ b/macros/luatex/generic/luaxml/luaxml.pdf
Binary files differ
diff --git a/macros/luatex/generic/luaxml/luaxml.tex b/macros/luatex/generic/luaxml/luaxml.tex
index 3b451fdb63..d641b91aad 100644
--- a/macros/luatex/generic/luaxml/luaxml.tex
+++ b/macros/luatex/generic/luaxml/luaxml.tex
@@ -7,7 +7,7 @@
\usepackage{framed}
% Version is defined in the makefile, use default values when compiled directly
\ifdefined\version\else
-\def\version{0.1l}
+\def\version{v0.1m}
\let\gitdate\date
\fi
\newcommand\modulename[1]{\subsection{#1}\label{sec:#1}}
@@ -99,6 +99,22 @@ end
\end{luacode*}
\end{framed}
+\subsection{Void elements}
+
+The \verb|DOM_Object.parse| function tries to support the HTML void elements,
+such as \verb|<img>| or \verb|<hr>|. They cannot have closing tags, a parse
+error occurs when the closing tags are used.
+
+It is possible to define a different set of void elements using the second parameter
+for \verb|DOM_Object.parse|:
+
+\begin{verbatim}
+obj = dom.parse(document, {custom_void = true})
+\end{verbatim}
+
+An empty table will disable all void elements. This setting is recommended for common |xml| documents.
+
+
\subsection{Node selection methods}
There are some other methods for element retrieving.
diff --git a/macros/xetex/latex/xepersian-hm/INSTALL.txt b/macros/xetex/latex/xepersian-hm/INSTALL.txt
index 6c4c2415e9..c1c5b9e4bb 100644
--- a/macros/xetex/latex/xepersian-hm/INSTALL.txt
+++ b/macros/xetex/latex/xepersian-hm/INSTALL.txt
@@ -1,7 +1,7 @@
xepersian-hm -- INSTALL
======================
- Source: xepersian-hm.dtx (2020-06-04 v1.0b)
+ Source: xepersian-hm.dtx (2020-07-20 v1.0c)
Author: Hossein Movahhedian
Info: filecontents + macro + verbatim
License: LPPL 1.3c
diff --git a/macros/xetex/latex/xepersian-hm/xepersian-hm-doc.ltx b/macros/xetex/latex/xepersian-hm/xepersian-hm-doc.ltx
index e2c64b3073..24a168dfc5 100644
--- a/macros/xetex/latex/xepersian-hm/xepersian-hm-doc.ltx
+++ b/macros/xetex/latex/xepersian-hm/xepersian-hm-doc.ltx
@@ -27,7 +27,7 @@
}
}
-\date{Released \quad 2020-06-04 \quad v1.0b}
+\date{Released \quad 2020-07-20 \quad v1.0c}
\let\tmpthepage\thepage
\renewcommand{\thepage}{\lr{\Large\textbf\tmpthepage}}
@@ -257,10 +257,10 @@ The options available in \textsf{xepersian-hm} are:
For example: \mbox{\texttt{'kashidastretch=titr'}} is equivalent to\linebreak
\mbox{\texttt{'kashidastretch=0.12 em plus 0.5 em'}}
- \item \texttt{ligature}: \\
+ \item \texttt{ligatures}: \\
which fixes the disturbance of ligatures caused by activation of kashida in
\textsf{xepersian}. You may strictly specify the value of this option.
- For example \texttt{'ligature=dlig'} or you may use the default value.
+ For example \texttt{'ligatures=dlig'} or you may use the default value.
The available values are:
\begin{longtable}{ll}
diff --git a/macros/xetex/latex/xepersian-hm/xepersian-hm-doc.pdf b/macros/xetex/latex/xepersian-hm/xepersian-hm-doc.pdf
index 5c0adbb357..67ab527464 100644
--- a/macros/xetex/latex/xepersian-hm/xepersian-hm-doc.pdf
+++ b/macros/xetex/latex/xepersian-hm/xepersian-hm-doc.pdf
Binary files differ
diff --git a/macros/xetex/latex/xepersian-hm/xepersian-hm.dtx b/macros/xetex/latex/xepersian-hm/xepersian-hm.dtx
index 8628fb08cc..6a74a05107 100644
--- a/macros/xetex/latex/xepersian-hm/xepersian-hm.dtx
+++ b/macros/xetex/latex/xepersian-hm/xepersian-hm.dtx
@@ -67,7 +67,7 @@ make time to fix.
% }^^A
% }
%
-% \date{Released \quad 2020-06-04 \quad v1.0b}
+% \date{Released \quad 2020-07-20 \quad v1.0c}
%
% \maketitle
%
@@ -96,7 +96,7 @@ make time to fix.
\RequirePackage{zref-savepos}[2020-03-03]
\RequirePackage{xepersian}
\ExplSyntaxOn
-\ProvidesExplPackage {xepersian-hm} {2020-06-04} {1.0b} { Fixes~issues~in~xepersian~package }
+\ProvidesExplPackage {xepersian-hm} {2020-07-20} {1.0c} { Fixes~issues~in~xepersian~package }
\box_new:N \l_xephm_ksh_box
@@ -195,15 +195,15 @@ make time to fix.
\tl_set:Nn \l_xephm_lig_rlig_tl { rlig } % Required Ligatures
\tl_set:Nn \l_xephm_lig_default_tl { default }
-\clist_set:Nn \l_xephm_lig_aalt_clist { { } } % Access All Alternatives
-\clist_set:Nn \l_xephm_lig_ccmp_clist { { } } % Glyph Composition/Decomposition
+\clist_set:Nn \l_xephm_lig_aalt_clist { } % Access All Alternatives
+\clist_set:Nn \l_xephm_lig_ccmp_clist { } % Glyph Composition/Decomposition
\clist_set:Nn \l_xephm_lig_dlig_clist { FDF2 = الله , FDF3 = اکبر , FDFB = جلجلاله } % Discretionary Ligatures
-\clist_set:Nn \l_xephm_lig_fina_clist { { } } % Final (Terminal) Forms
-\clist_set:Nn \l_xephm_lig_init_clist { { } } % Initial Forms
-\clist_set:Nn \l_xephm_lig_locl_clist { { } } % Localized Forms
-\clist_set:Nn \l_xephm_lig_medi_clist { { } } % Medial Forms
-\clist_set:Nn \l_xephm_lig_rlig_clist { { } } % Required Ligatures
-\clist_set:Nn \l_xephm_lig_default_clist { { } }
+\clist_set:Nn \l_xephm_lig_fina_clist { } % Final (Terminal) Forms
+\clist_set:Nn \l_xephm_lig_init_clist { } % Initial Forms
+\clist_set:Nn \l_xephm_lig_locl_clist { } % Localized Forms
+\clist_set:Nn \l_xephm_lig_medi_clist { } % Medial Forms
+\clist_set:Nn \l_xephm_lig_rlig_clist { } % Required Ligatures
+\clist_set:Nn \l_xephm_lig_default_clist { }
\clist_set:Nn \l_xephm_lig_names_clist
{
@@ -385,7 +385,7 @@ make time to fix.
% \begin{macrocode}
%<*kashida-xepersian-hm-def>
\ExplSyntaxOn
-\ProvidesExplFile {kashida-xepersian-hm.def} {2020-06-04} {1.0b} { Fixes~implementation~of~Kashida~in~xepersian~package }
+\ProvidesExplFile {kashida-xepersian-hm.def} {2020-07-20} {1.0c} { Fixes~implementation~of~Kashida~in~xepersian~package }
\newXeTeXintercharclass \c_xephm_d_charclass % dual-joiner class
\newXeTeXintercharclass \c_xephm_l_charclass % lam
diff --git a/macros/xetex/latex/xepersian-hm/xepersian-hm.pdf b/macros/xetex/latex/xepersian-hm/xepersian-hm.pdf
index 60f34fde89..5dc5c070b8 100644
--- a/macros/xetex/latex/xepersian-hm/xepersian-hm.pdf
+++ b/macros/xetex/latex/xepersian-hm/xepersian-hm.pdf
Binary files differ