texlive[58457] branches/branch2020.0/Master: lebhart (16mar21)

commits+karl at tug.org commits+karl at tug.org
Tue Mar 16 23:17:11 CET 2021


Revision: 58457
          http://tug.org/svn/texlive?view=revision&revision=58457
Author:   karl
Date:     2021-03-16 23:17:11 +0100 (Tue, 16 Mar 2021)
Log Message:
-----------
lebhart (16mar21) (branch)

Added Paths:
-----------
    branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/
    branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/LICENSE
    branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/README.md
    branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-cn.pdf
    branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-cn.tex
    branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-en.pdf
    branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-en.tex
    branches/branch2020.0/Master/texmf-dist/tex/latex/lebhart/
    branches/branch2020.0/Master/texmf-dist/tex/latex/lebhart/lebhart.cls
    branches/branch2020.0/Master/tlpkg/tlpsrc/lebhart.tlpsrc

Added: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/LICENSE
===================================================================
--- branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/LICENSE	                        (rev 0)
+++ branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/LICENSE	2021-03-16 22:17:11 UTC (rev 58457)
@@ -0,0 +1,416 @@
+The LaTeX Project Public License
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
+
+LPPL Version 1.3c  2008-05-04
+
+Copyright 1999 2002-2008 LaTeX3 Project
+    Everyone is allowed to distribute verbatim copies of this
+    license document, but modification of it is not allowed.
+
+
+PREAMBLE
+========
+
+The LaTeX Project Public License (LPPL) is the primary license under
+which the LaTeX kernel and the base LaTeX packages are distributed.
+
+You may use this license for any work of which you hold the copyright
+and which you wish to distribute.  This license may be particularly
+suitable if your work is TeX-related (such as a LaTeX package), but 
+it is written in such a way that you can use it even if your work is 
+unrelated to TeX.
+
+The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
+below, gives instructions, examples, and recommendations for authors
+who are considering distributing their works under this license.
+
+This license gives conditions under which a work may be distributed
+and modified, as well as conditions under which modified versions of
+that work may be distributed.
+
+We, the LaTeX3 Project, believe that the conditions below give you
+the freedom to make and distribute modified versions of your work
+that conform with whatever technical specifications you wish while
+maintaining the availability, integrity, and reliability of
+that work.  If you do not see how to achieve your goal while
+meeting these conditions, then read the document `cfgguide.tex'
+and `modguide.tex' in the base LaTeX distribution for suggestions.
+
+
+DEFINITIONS
+===========
+
+In this license document the following terms are used:
+
+   `Work'
+    Any work being distributed under this License.
+    
+   `Derived Work'
+    Any work that under any applicable law is derived from the Work.
+
+   `Modification' 
+    Any procedure that produces a Derived Work under any applicable
+    law -- for example, the production of a file containing an
+    original file associated with the Work or a significant portion of
+    such a file, either verbatim or with modifications and/or
+    translated into another language.
+
+   `Modify'
+    To apply any procedure that produces a Derived Work under any
+    applicable law.
+    
+   `Distribution'
+    Making copies of the Work available from one person to another, in
+    whole or in part.  Distribution includes (but is not limited to)
+    making any electronic components of the Work accessible by
+    file transfer protocols such as FTP or HTTP or by shared file
+    systems such as Sun's Network File System (NFS).
+
+   `Compiled Work'
+    A version of the Work that has been processed into a form where it
+    is directly usable on a computer system.  This processing may
+    include using installation facilities provided by the Work,
+    transformations of the Work, copying of components of the Work, or
+    other activities.  Note that modification of any installation
+    facilities provided by the Work constitutes modification of the Work.
+
+   `Current Maintainer'
+    A person or persons nominated as such within the Work.  If there is
+    no such explicit nomination then it is the `Copyright Holder' under
+    any applicable law.
+
+   `Base Interpreter' 
+    A program or process that is normally needed for running or
+    interpreting a part or the whole of the Work.    
+
+    A Base Interpreter may depend on external components but these
+    are not considered part of the Base Interpreter provided that each
+    external component clearly identifies itself whenever it is used
+    interactively.  Unless explicitly specified when applying the
+    license to the Work, the only applicable Base Interpreter is a
+    `LaTeX-Format' or in the case of files belonging to the 
+    `LaTeX-format' a program implementing the `TeX language'.
+
+
+
+CONDITIONS ON DISTRIBUTION AND MODIFICATION
+===========================================
+
+1.  Activities other than distribution and/or modification of the Work
+are not covered by this license; they are outside its scope.  In
+particular, the act of running the Work is not restricted and no
+requirements are made concerning any offers of support for the Work.
+
+2.  You may distribute a complete, unmodified copy of the Work as you
+received it.  Distribution of only part of the Work is considered
+modification of the Work, and no right to distribute such a Derived
+Work may be assumed under the terms of this clause.
+
+3.  You may distribute a Compiled Work that has been generated from a
+complete, unmodified copy of the Work as distributed under Clause 2
+above, as long as that Compiled Work is distributed in such a way that
+the recipients may install the Compiled Work on their system exactly
+as it would have been installed if they generated a Compiled Work
+directly from the Work.
+
+4.  If you are the Current Maintainer of the Work, you may, without
+restriction, modify the Work, thus creating a Derived Work.  You may
+also distribute the Derived Work without restriction, including
+Compiled Works generated from the Derived Work.  Derived Works
+distributed in this manner by the Current Maintainer are considered to
+be updated versions of the Work.
+
+5.  If you are not the Current Maintainer of the Work, you may modify
+your copy of the Work, thus creating a Derived Work based on the Work,
+and compile this Derived Work, thus creating a Compiled Work based on
+the Derived Work.
+
+6.  If you are not the Current Maintainer of the Work, you may
+distribute a Derived Work provided the following conditions are met
+for every component of the Work unless that component clearly states
+in the copyright notice that it is exempt from that condition.  Only
+the Current Maintainer is allowed to add such statements of exemption 
+to a component of the Work. 
+
+  a. If a component of this Derived Work can be a direct replacement
+     for a component of the Work when that component is used with the
+     Base Interpreter, then, wherever this component of the Work
+     identifies itself to the user when used interactively with that
+     Base Interpreter, the replacement component of this Derived Work
+     clearly and unambiguously identifies itself as a modified version
+     of this component to the user when used interactively with that
+     Base Interpreter.
+     
+  b. Every component of the Derived Work contains prominent notices
+     detailing the nature of the changes to that component, or a
+     prominent reference to another file that is distributed as part
+     of the Derived Work and that contains a complete and accurate log
+     of the changes.
+  
+  c. No information in the Derived Work implies that any persons,
+     including (but not limited to) the authors of the original version
+     of the Work, provide any support, including (but not limited to)
+     the reporting and handling of errors, to recipients of the
+     Derived Work unless those persons have stated explicitly that
+     they do provide such support for the Derived Work.
+
+  d. You distribute at least one of the following with the Derived Work:
+
+       1. A complete, unmodified copy of the Work; 
+          if your distribution of a modified component is made by
+          offering access to copy the modified component from a
+          designated place, then offering equivalent access to copy
+          the Work from the same or some similar place meets this
+          condition, even though third parties are not compelled to
+          copy the Work along with the modified component;
+
+       2. Information that is sufficient to obtain a complete,
+          unmodified copy of the Work.
+
+7.  If you are not the Current Maintainer of the Work, you may
+distribute a Compiled Work generated from a Derived Work, as long as
+the Derived Work is distributed to all recipients of the Compiled
+Work, and as long as the conditions of Clause 6, above, are met with
+regard to the Derived Work.
+
+8.  The conditions above are not intended to prohibit, and hence do not
+apply to, the modification, by any method, of any component so that it
+becomes identical to an updated version of that component of the Work as
+it is distributed by the Current Maintainer under Clause 4, above.
+
+9.  Distribution of the Work or any Derived Work in an alternative
+format, where the Work or that Derived Work (in whole or in part) is
+then produced by applying some process to that format, does not relax or
+nullify any sections of this license as they pertain to the results of
+applying that process.
+     
+10. a. A Derived Work may be distributed under a different license
+       provided that license itself honors the conditions listed in
+       Clause 6 above, in regard to the Work, though it does not have
+       to honor the rest of the conditions in this license.
+      
+    b. If a Derived Work is distributed under a different license, that
+       Derived Work must provide sufficient documentation as part of
+       itself to allow each recipient of that Derived Work to honor the 
+       restrictions in Clause 6 above, concerning changes from the Work.
+
+11. This license places no restrictions on works that are unrelated to
+the Work, nor does this license place any restrictions on aggregating
+such works with the Work by any means.
+
+12.  Nothing in this license is intended to, or may be used to, prevent
+complete compliance by all parties with all applicable laws.
+
+
+NO WARRANTY
+===========
+
+There is no warranty for the Work.  Except when otherwise stated in
+writing, the Copyright Holder provides the Work `as is', without
+warranty of any kind, either expressed or implied, including, but not
+limited to, the implied warranties of merchantability and fitness for a
+particular purpose.  The entire risk as to the quality and performance
+of the Work is with you.  Should the Work prove defective, you assume
+the cost of all necessary servicing, repair, or correction.
+
+In no event unless required by applicable law or agreed to in writing
+will The Copyright Holder, or any author named in the components of the
+Work, or any other party who may distribute and/or modify the Work as
+permitted above, be liable to you for damages, including any general,
+special, incidental or consequential damages arising out of any use of
+the Work or out of inability to use the Work (including, but not limited
+to, loss of data, data being rendered inaccurate, or losses sustained by
+anyone as a result of any failure of the Work to operate with any other
+programs), even if the Copyright Holder or said author or said other
+party has been advised of the possibility of such damages.
+
+
+MAINTENANCE OF THE WORK
+=======================
+
+The Work has the status `author-maintained' if the Copyright Holder
+explicitly and prominently states near the primary copyright notice in
+the Work that the Work can only be maintained by the Copyright Holder
+or simply that it is `author-maintained'.
+
+The Work has the status `maintained' if there is a Current Maintainer
+who has indicated in the Work that they are willing to receive error
+reports for the Work (for example, by supplying a valid e-mail
+address). It is not required for the Current Maintainer to acknowledge
+or act upon these error reports.
+
+The Work changes from status `maintained' to `unmaintained' if there
+is no Current Maintainer, or the person stated to be Current
+Maintainer of the work cannot be reached through the indicated means
+of communication for a period of six months, and there are no other
+significant signs of active maintenance.
+
+You can become the Current Maintainer of the Work by agreement with
+any existing Current Maintainer to take over this role.
+
+If the Work is unmaintained, you can become the Current Maintainer of
+the Work through the following steps:
+
+ 1.  Make a reasonable attempt to trace the Current Maintainer (and
+     the Copyright Holder, if the two differ) through the means of
+     an Internet or similar search.
+
+ 2.  If this search is successful, then enquire whether the Work
+     is still maintained.
+
+  a. If it is being maintained, then ask the Current Maintainer
+     to update their communication data within one month.
+     
+  b. If the search is unsuccessful or no action to resume active
+     maintenance is taken by the Current Maintainer, then announce
+     within the pertinent community your intention to take over
+     maintenance.  (If the Work is a LaTeX work, this could be
+     done, for example, by posting to comp.text.tex.)
+
+ 3a. If the Current Maintainer is reachable and agrees to pass
+     maintenance of the Work to you, then this takes effect
+     immediately upon announcement.
+     
+  b. If the Current Maintainer is not reachable and the Copyright
+     Holder agrees that maintenance of the Work be passed to you,
+     then this takes effect immediately upon announcement.  
+    
+ 4.  If you make an `intention announcement' as described in 2b. above
+     and after three months your intention is challenged neither by
+     the Current Maintainer nor by the Copyright Holder nor by other
+     people, then you may arrange for the Work to be changed so as
+     to name you as the (new) Current Maintainer.
+     
+ 5.  If the previously unreachable Current Maintainer becomes
+     reachable once more within three months of a change completed
+     under the terms of 3b) or 4), then that Current Maintainer must
+     become or remain the Current Maintainer upon request provided
+     they then update their communication data within one month.
+
+A change in the Current Maintainer does not, of itself, alter the fact
+that the Work is distributed under the LPPL license.
+
+If you become the Current Maintainer of the Work, you should
+immediately provide, within the Work, a prominent and unambiguous
+statement of your status as Current Maintainer.  You should also
+announce your new status to the same pertinent community as
+in 2b) above.
+
+
+WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE
+======================================================
+
+This section contains important instructions, examples, and
+recommendations for authors who are considering distributing their
+works under this license.  These authors are addressed as `you' in
+this section.
+
+Choosing This License or Another License
+----------------------------------------
+
+If for any part of your work you want or need to use *distribution*
+conditions that differ significantly from those in this license, then
+do not refer to this license anywhere in your work but, instead,
+distribute your work under a different license.  You may use the text
+of this license as a model for your own license, but your license
+should not refer to the LPPL or otherwise give the impression that
+your work is distributed under the LPPL.
+
+The document `modguide.tex' in the base LaTeX distribution explains
+the motivation behind the conditions of this license.  It explains,
+for example, why distributing LaTeX under the GNU General Public
+License (GPL) was considered inappropriate.  Even if your work is
+unrelated to LaTeX, the discussion in `modguide.tex' may still be
+relevant, and authors intending to distribute their works under any
+license are encouraged to read it.
+
+A Recommendation on Modification Without Distribution
+-----------------------------------------------------
+
+It is wise never to modify a component of the Work, even for your own
+personal use, without also meeting the above conditions for
+distributing the modified component.  While you might intend that such
+modifications will never be distributed, often this will happen by
+accident -- you may forget that you have modified that component; or
+it may not occur to you when allowing others to access the modified
+version that you are thus distributing it and violating the conditions
+of this license in ways that could have legal implications and, worse,
+cause problems for the community.  It is therefore usually in your
+best interest to keep your copy of the Work identical with the public
+one.  Many works provide ways to control the behavior of that work
+without altering any of its licensed components.
+
+How to Use This License
+-----------------------
+
+To use this license, place in each of the components of your work both
+an explicit copyright notice including your name and the year the work
+was authored and/or last substantially modified.  Include also a
+statement that the distribution and/or modification of that
+component is constrained by the conditions in this license.
+
+Here is an example of such a notice and statement:
+
+  %% pig.dtx
+  %% Copyright 2005 M. Y. Name
+  %
+  % This work may be distributed and/or modified under the
+  % conditions of the LaTeX Project Public License, either version 1.3
+  % of this license or (at your option) any later version.
+  % The latest version of this license is in
+  %   http://www.latex-project.org/lppl.txt
+  % and version 1.3 or later is part of all distributions of LaTeX
+  % version 2005/12/01 or later.
+  %
+  % This work has the LPPL maintenance status `maintained'.
+  % 
+  % The Current Maintainer of this work is M. Y. Name.
+  %
+  % This work consists of the files pig.dtx and pig.ins
+  % and the derived file pig.sty.
+
+Given such a notice and statement in a file, the conditions
+given in this license document would apply, with the `Work' referring
+to the three files `pig.dtx', `pig.ins', and `pig.sty' (the last being
+generated from `pig.dtx' using `pig.ins'), the `Base Interpreter'
+referring to any `LaTeX-Format', and both `Copyright Holder' and
+`Current Maintainer' referring to the person `M. Y. Name'.
+
+If you do not want the Maintenance section of LPPL to apply to your
+Work, change `maintained' above into `author-maintained'.  
+However, we recommend that you use `maintained', as the Maintenance
+section was added in order to ensure that your Work remains useful to
+the community even when you can no longer maintain and support it
+yourself.
+
+Derived Works That Are Not Replacements
+---------------------------------------
+
+Several clauses of the LPPL specify means to provide reliability and
+stability for the user community. They therefore concern themselves
+with the case that a Derived Work is intended to be used as a
+(compatible or incompatible) replacement of the original Work. If
+this is not the case (e.g., if a few lines of code are reused for a
+completely different task), then clauses 6b and 6d shall not apply.
+
+
+Important Recommendations
+-------------------------
+
+ Defining What Constitutes the Work
+
+   The LPPL requires that distributions of the Work contain all the
+   files of the Work.  It is therefore important that you provide a
+   way for the licensee to determine which files constitute the Work.
+   This could, for example, be achieved by explicitly listing all the
+   files of the Work near the copyright notice of each file or by
+   using a line such as:
+
+    % This work consists of all files listed in manifest.txt.
+   
+   in that place.  In the absence of an unequivocal list it might be
+   impossible for the licensee to determine what is considered by you
+   to comprise the Work and, in such a case, the licensee would be
+   entitled to make reasonable conjectures as to which files comprise
+   the Work.
+

Added: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/README.md
===================================================================
--- branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/README.md	                        (rev 0)
+++ branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/README.md	2021-03-16 22:17:11 UTC (rev 58457)
@@ -0,0 +1,16 @@
+<!-- Copyright (C) 2021 by Jinwen XU -->
+
+# `lebhart` : write you articles in a colorful way
+
+`lebhart` is a LaTeX class for typesetting articles, which has a colorful
+design.
+
+Currently, it has native support to English, French and Chinese typesetting. And
+it may compile with either XeLaTeX or LuaLaTeX.
+
+This is part of the colorist class series.
+
+# License
+
+This work is released under the LaTeX Project Public License, v1.3c or later.
+


Property changes on: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/README.md
___________________________________________________________________
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-cn.pdf
===================================================================
(Binary files differ)

Index: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-cn.pdf
===================================================================
--- branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-cn.pdf	2021-03-16 22:17:01 UTC (rev 58456)
+++ branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-cn.pdf	2021-03-16 22:17:11 UTC (rev 58457)

Property changes on: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-cn.pdf
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/pdf
\ No newline at end of property
Added: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-cn.tex
===================================================================
--- branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-cn.tex	                        (rev 0)
+++ branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-cn.tex	2021-03-16 22:17:11 UTC (rev 58457)
@@ -0,0 +1,257 @@
+%! TEX program = xelatex
+\PassOptionsToPackage{dvipsnames}{xcolor}
+\documentclass{lebhart}
+
+\UseLanguage{Chinese}
+
+%%================================
+%% TeX logo 与 网址
+%%================================
+\usepackage{hologo}
+\usepackage{url}
+
+%%================================
+%% 排版代码
+%%================================
+\usepackage{listings}
+\definecolor{lightergray}{gray}{0.99}
+\lstset{language=[LaTeX]TeX,
+    keywordstyle=\color{RoyalBlue},
+    basicstyle=\ttfamily,
+    commentstyle=\color{ForestGreen}\ttfamily,
+    stringstyle=\rmfamily,
+    showstringspaces=false,
+    breaklines=true,
+    frame=lines,
+    backgroundcolor=\color{lightergray},
+    flexiblecolumns=true,
+    escapeinside={(*}{*)},
+    % numbers=left,
+    numberstyle=\scriptsize, stepnumber=1, numbersep=5pt,
+    firstnumber=last,
+} 
+\providecommand{\meta}[1]{$\langle${\normalfont\itshape#1}$\rangle$}
+\lstset{morekeywords=%
+    {CreateTheorem,proofideanameCN,cref,dnf,needgraph,UseLanguage,
+    linenumbers,nolinenumbers,subsection,maketitle
+    }
+}
+\lstnewenvironment{code}% 
+{\setkeys{lst}{columns=fullflexible,keepspaces=true}}{}
+
+\providecommand{\colorist}{\textsf{colorist}}
+\providecommand{\colorart}{\textsf{colorart}}
+\providecommand{\colorbook}{\textsf{colorbook}}
+\providecommand{\lebhart}{\textsf{lebhart}}
+\providecommand{\beaulivre}{\textsf{beaulivre}}
+
+%%================================
+%% 正文
+%%================================
+\begin{document}
+
+\title{\lebhart{},以多彩的方式排版你的文章\thanks{对应版本. \texttt{\lebhart{} 2021/03/15}}}
+\author{锦文}
+\date{2021年3月,北京}
+
+\maketitle
+
+\begin{abstract}
+    \lebhart{}是\colorist{}文档类系列的成员之一,整个系列包含用于排版文章的\colorart{}、\lebhart{}以及用于排版书的\colorbook{}、\beaulivre{}。我设计这一系列的初衷是为了撰写草稿与笔记,使之多彩而不缭乱。
+
+    其中,\lebhart{}与\beaulivre{}支持英文、法文、中文三种语言,并且同一篇文档中三种语言可以很好地协调。由于采用了自定义字体,需要采用 \hologo{XeLaTeX} 或 \hologo{LuaLaTeX} 进行编译。
+    
+    这篇说明文档是用\lebhart{}排版的,你可以把它看作一份简短的说明与演示。
+\end{abstract}
+
+\begin{tcolorbox}[enhanced jigsaw,pad at break*=1mm,breakable,colback=yellow!25!paper,boxrule=0pt,frame hidden]
+    由于\colorist{}主体是从\textsf{minimalist}系列修改而来的,因而一些页面元素还未完全重新设计,特别是目录、part和chapter的样式。这些内容会在将来逐渐加入。
+\end{tcolorbox}
+
+\tableofcontents
+
+\section{关于文档类的名称与选项}
+
+\lebhart{}取自于德文的lebhaft (活泼),并取了artikel (文章)的前三个字母组合而成。
+
+\beaulivre{}取自于法文的beau (美丽),以及livre (书),由二者组合而成。
+
+\medskip
+你可以使用选项 \verb|fast| 来启用快速但略微粗糙的样式,主要区别是:
+\begin{itemize}
+    \item 使用较为简单的数学字体设置;
+    \item 不使用hyperref;
+    \item 所有tcolorbox使用draft模式;
+    \item 使用polyglossia而不是babel来支持多语言。(使用polyglossia编译速度会略有提高,但目前对于中文的兼容不太完善,在它更加稳定后,将会考虑全面切换到polyglossia)
+\end{itemize}
+
+在文章的撰写阶段,建议使用 \verb|fast| 选项以加快编译速度,改善写作时的流畅程度。在最后,可以把 \verb|fast| 标记去除,从而得到正式的版本。
+
+\section{一些使用说明}
+
+\subsection{定理,以及引用}
+
+定义、定理等环境已经被预定义,可以直接使用,例如:
+\begin{code}
+  \begin{definition}[奇异物品] \label{def: strange} ...
+\end{code}
+将会生成
+\begin{definition}[奇异物品]\label{def: strange}
+    这是奇异物品的定义。
+\end{definition}
+
+\begin{definition}[另一个定义]
+    不同的定义会自动粘结在一起,中间不会有空隙。
+\end{definition}
+
+引用时,可以直接使用智能引用 \lstinline|\cref{标签名称}|,例如:\lstinline|\cref{def: strange}| 会显示为:\cref{def: strange}。
+
+\bigskip
+下面是定理类环境的其他几种样式:
+
+\begin{theorem}
+    Theorem style: theorem, proposition, lemma, corollary
+\end{theorem}
+
+\begin{proof}
+    Proof style
+\end{proof}
+
+\begin{remark}
+    Remark style
+\end{remark}
+
+\begin{conjecture}
+    Conjecture style
+\end{conjecture}
+
+\begin{example*}
+    Example style: example, fact
+\end{example*}
+
+\begin{problem}
+    Problem style
+\end{problem}
+
+\subsection{定义新的定理型环境}
+
+首先定义这个环境在所用语言下的名称 \lstinline|\(name of environment)(language name)|,其中 \\\lstinline|(language name)| 是 \lstinline|EN|、\lstinline|FR|、\lstinline|CN| 等,然后用下面四种方式之一定义这一环境:
+\begin{itemize}
+    \item \lstinline|\CreateTheorem*{(name of environment)}|
+    \item \lstinline|\CreateTheorem{(name of environment)}[(numbered like)]|
+    \item \lstinline|\CreateTheorem{(name of environment)}<(numbered within)>|
+    \item \lstinline|\CreateTheorem{(name of environment)}|
+\end{itemize}
+
+\def\proofideanameCN{思路}
+\CreateTheorem*{proofidea}
+
+例如,
+
+\begin{code}
+  \def\proofideanameCN{思路}
+  \CreateTheorem*{proofidea}
+\end{code}
+可以定义不编号的环境 \lstinline|proofidea|,它支持在中文环境中使用,效果如下所示:
+
+\begin{proofidea}
+    ...
+\end{proofidea}
+
+\subsection{未完成标记}
+
+你可以通过 \lstinline|\dnf| 来标记尚未完成的部分。例如:
+\begin{itemize}
+    \item \lstinline|\dnf|: \quad \dnf
+    \item \lstinline|\dnf<还需加入…>|: \quad \dnf<还需加入…>
+\end{itemize}
+
+类似的,还有 \lstinline|\needgraph| :
+\begin{itemize}
+    \item \lstinline|\needgraph|: \needgraph
+    \item \lstinline|\needgraph<关于…>|: \needgraph<关于…>
+\end{itemize}
+
+\subsection{语言设置}
+可以随时使用 \lstinline|\UseLanguage{语言名称}| 更改语言,语言名称包括Chinese、English、French(首字母大小写随意,例如chinese亦可)。这样,各种指令和环境的效果也会随之变动。
+
+例如,使用 \lstinline|\UseLanguage{English}| 后,定理与未完成标记会显示为:
+
+\UseLanguage{English}
+\begin{theorem}[Useless]\label{thm}
+    Some theorem in English. \dnf
+\end{theorem}
+
+引用时,定理的名称总是与定理所在区域的语言匹配,例如,开头的定义在现在的英文模式下依然显示为中文:\cref{def: strange} 和 \cref{thm}。
+
+\UseLanguage{Chinese}
+
+\subsection{关于字体}
+\lebhart{}与\beaulivre{}使用Palatino Linotype作为英文字体,方正悠宋、悠黑简体作为中文字体,并部分使用了Neo Euler作为数学字体:
+\begin{itemize}
+    \item English main font. \textsf{English sans serif font}.
+    \item 中文主要字体,\textsf{中文无衬线字体}
+    \item 数学示例: \( \alpha, \beta, \gamma, \delta, 1,2,3,4, a,b,c,d \), \[\mathrm{li}(x)\coloneqq \int_2^{\infty} \frac{1}{\log t}\,\mathrm{d}t \]
+\end{itemize}
+
+其中,Neo Euler可以在 \url{https://github.com/khaledhosny/euler-otf} 下载。
+
+其他字体不是免费字体,需要自行购买使用(你可以在方正字库网站查询详细资料:\url{https://www.foundertype.com})。
+
+在没有安装相应的字体时,将采用TeX Live中自带的字体来代替,效果可能会有所折扣。
+
+\section{文档示例}
+
+\singlespacing
+
+\begin{minipage}{0.45\textwidth}
+\begin{code}
+%! TEX program = xelatex
+\documentclass[fast]{lebhart}
+
+\linenumbers
+\UseLanguage{French}
+
+\begin{document}
+
+\title{Titre}
+\author{Nom}
+\date{03 / 2021, Lieu}
+
+\maketitle
+
+%% Texte ici
+
+\end{document}
+\end{code}
+\end{minipage}
+%
+\hfill
+%
+\begin{minipage}{0.45\textwidth}
+\begin{code}
+%! TEX program = xelatex
+\documentclass[fast]{lebhart}
+
+\linenumbers
+\UseLanguage{Chinese}
+
+\begin{document}
+
+\title{标题}
+\author{姓名}
+\date{2021年3月,地点}
+
+\maketitle
+
+%% 正文部分
+
+\end{document}
+\end{code}
+\end{minipage}
+\par
+
+\bigskip
+(\lstinline|\UseLanguage| 既可以放在导言中,也可以放在正文部分,并且可以按照需要反复使用)
+
+\end{document}


Property changes on: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-cn.tex
___________________________________________________________________
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-en.pdf
===================================================================
(Binary files differ)

Index: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-en.pdf
===================================================================
--- branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-en.pdf	2021-03-16 22:17:01 UTC (rev 58456)
+++ branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-en.pdf	2021-03-16 22:17:11 UTC (rev 58457)

Property changes on: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-en.pdf
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/pdf
\ No newline at end of property
Added: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-en.tex
===================================================================
--- branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-en.tex	                        (rev 0)
+++ branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-en.tex	2021-03-16 22:17:11 UTC (rev 58457)
@@ -0,0 +1,251 @@
+%! TEX program = xelatex
+\PassOptionsToPackage{dvipsnames}{xcolor}
+\documentclass{lebhart}
+
+%%================================
+%% TeX logo and URL
+%%================================
+\usepackage{hologo}
+\usepackage{url}
+
+%%================================
+%% For typestting code
+%%================================
+\usepackage{listings}
+\definecolor{lightergray}{gray}{0.99}
+\lstset{language=[LaTeX]TeX,
+    keywordstyle=\color{RoyalBlue},
+    basicstyle=\ttfamily,
+    commentstyle=\color{ForestGreen}\ttfamily,
+    stringstyle=\rmfamily,
+    showstringspaces=false,
+    breaklines=true,
+    frame=lines,
+    backgroundcolor=\color{lightergray},
+    flexiblecolumns=true,
+    escapeinside={(*}{*)},
+    % numbers=left,
+    numberstyle=\scriptsize, stepnumber=1, numbersep=5pt,
+    firstnumber=last,
+} 
+\providecommand{\meta}[1]{$\langle${\normalfont\itshape#1}$\rangle$}
+\lstset{morekeywords=%
+    {CreateTheorem,proofideanameEN,cref,dnf,needgraph,UseLanguage,
+    linenumbers,nolinenumbers,subsection,maketitle
+    }
+}
+\lstnewenvironment{code}% 
+{\setkeys{lst}{columns=fullflexible,keepspaces=true}}{}
+
+\providecommand{\colorist}{\textsf{colorist}}
+\providecommand{\colorart}{\textsf{colorart}}
+\providecommand{\colorbook}{\textsf{colorbook}}
+\providecommand{\lebhart}{\textsf{lebhart}}
+\providecommand{\beaulivre}{\textsf{beaulivre}}
+
+%%================================
+%% Main text
+%%================================
+\begin{document}
+
+\title{\lebhart{}, write your articles in a colorful way\thanks{Corresponding to: \texttt{\lebhart{} 2021/03/15}}}
+\author{Jinwen}
+\date{March 2021, Beijing}
+
+\maketitle
+
+\begin{abstract}
+    \lebhart{} is a member of the \colorist{} class series. The entire collection includes \colorart{} and \lebhart{} for typesetting articles and \colorbook{} and \beaulivre{} for typesetting books. My original intention in designing this series was to write drafts and notes that look colorful yet not dazzling.
+
+    Among them, \lebhart{} and \beaulivre{} support three languages: English, French, and Chinese, and these three languages can be switched seamlessly in a single document. Due to the usage of custom fonts, they need to be compiled with \hologo{XeLaTeX} or \hologo{LuaLaTeX}.
+    
+    This documentation is typeset using \lebhart{}. You can think of it as a short introduction and demonstration.
+\end{abstract}
+
+\begin{tcolorbox}[enhanced jigsaw,pad at break*=1mm,breakable,colback=yellow!25!paper,boxrule=0pt,frame hidden]
+    Since the main body of \colorist{} is modified from the \textsf{minimalist} series, some elements have not been completely redesigned yet, especially the TOC, part and chapter style. These will be added gradually in the future versions.
+\end{tcolorbox}
+
+\tableofcontents
+
+\section{On the naming and options}
+\begin{itemize}
+    \item \lebhart{} is taken from German word ``lebhaft'' (``vividly''), combined with the first three letters of ``artikel'' (``article'').
+    \item \beaulivre{} is taken from French words ``beau'' (for ``beautiful'') and ``livre'' (for ``book'').
+\end{itemize}
+
+You can use the option \verb|fast| to enable a fast but slightly rough version. The main differences are:
+\begin{itemize}
+    \item Use simpler math font configuration; 
+    \item Do not use hyperref; 
+    \item Use draft mode for all tcolorboxes; 
+    \item Use polyglossia instead of babel to support multiple languages. (Using polyglossia will increase the compilation speed slightly, but the current compatibility with Chinese is not perfect. When it becomes more stable, I will consider fully switching to polyglossia)
+\end{itemize}
+
+During the writing stage of your document, it is recommended to use the \verb|fast| option to speed up compilation and improve the smoothness of your writing experience. At the end, you can remove the ``fast'' mark to get the final version.
+
+\section{Some instructions}
+
+\subsection{Theorems and how to reference them}
+
+Environments such as definitions and theorems have been pre-defined and can be used directly, for example:
+\begin{code}
+  \begin{definition}[Strange things] \label{def: strange} ...
+\end{code}
+will produce
+\begin{definition}[Strange things]\label{def: strange}
+    This is the definition of some strange objects.
+\end{definition}
+
+\begin{definition}[Another definition]
+    Different definitions are automatically glued together, and there will be no gaps in between.
+\end{definition}
+
+When referencing, you can directly use clever reference \lstinline|\cref{(label name)}|. For example, \lstinline|\cref{def: strange}| will be displayed as: \cref{def: strange}.
+
+\bigskip
+The following are several other styles of theorem-like environments:
+
+\begin{theorem}
+    Theorem style: theorem, proposition, lemma, corollary
+\end{theorem}
+
+\begin{proof}
+    Proof style
+\end{proof}
+
+\begin{remark}
+    Remark style
+\end{remark}
+
+\begin{conjecture}
+    Conjecture style
+\end{conjecture}
+
+\begin{example*}
+    Example style: example, fact
+\end{example*}
+
+\begin{problem}
+    Problem style
+\end{problem}
+
+\subsection{Define a new theorem-like environment}
+
+First define the name of this environment in the language used: \lstinline|\(name of environment)(language name)|. Where \lstinline|(language name)| can be \lstinline|EN|, \lstinline|FR|, \lstinline|CN|, etc., and then define this environment in one of the following four ways:
+\begin{itemize}
+    \item \lstinline|\CreateTheorem*{(name of environment)}|
+    \item \lstinline|\CreateTheorem{(name of environment)}[(numbered like)]|
+    \item \lstinline|\CreateTheorem{(name of environment)}<(numbered within)>|
+    \item \lstinline|\CreateTheorem{(name of environment)}|
+\end{itemize}
+
+\def\proofideanameEN{Idea}
+\CreateTheorem*{proofidea}
+
+For example,
+\begin{code}
+  \def\proofideanameEN{Idea}
+  \CreateTheorem*{proofidea}
+\end{code}
+defines an unnumbered environment \lstinline|proofidea|, which supports using in the English context, and the effect is as follows:
+
+\begin{proofidea}
+    ...
+\end{proofidea}
+
+\subsection{Draft mark}
+
+You can use \lstinline|\dnf| to mark the unfinished part. For example:
+\begin{itemize}
+    \item \lstinline|\dnf|: \quad \dnf
+    \item \lstinline|\dnf<Still need ...>|: \quad \dnf<Still need ...>
+\end{itemize}
+
+Similarly, there is \lstinline|\needgraph| :
+\begin{itemize}
+    \item \lstinline|\needgraph|: \needgraph
+    \item \lstinline|\needgraph<About ...>|: \needgraph<About ...>
+\end{itemize}
+
+\subsection{Language configuration}
+You can use \lstinline|\UseLanguage{(name of language))}| at any time to change the language, Language names include Chinese, English, French (the case of the first letter is arbitrary, for example, ``chinese'' is also acceptable). With this, the effects of various commands and environments will also change accordingly.
+
+For example, after using \lstinline|\UseLanguage{French}|, the theorem and the draft mark will be displayed as:
+
+\UseLanguage{French}
+\begin{theorem}[Inutile]\label{thm}
+    Un théorème en français. \dnf
+\end{theorem}
+
+When referenced, the name of the theorem always matches the language of the region in which the theorem is located, for example, the definition of the beginning is still displayed in English in the current French mode: \cref{def: strange} and \cref{thm}. 
+
+\UseLanguage{English}
+
+\subsection{On the fonts}
+\lebhart{} and \beaulivre{} use Palatino Linotype as the English font, FounderType's YouSong and YouHei Simplified as the Chinese fonts, and partially use Neo Euler as the mathematical font:
+\begin{itemize}
+    \item English main font. \textsf{English sans serif font}.
+    \item 中文主要字体, \textsf{中文无衬线字体}
+    \item Math demonstration: \( \alpha, \beta, \gamma, \delta, 1,2,3,4, a,b,c,d \), \[\mathrm{li}(x)\coloneqq \int_2^{\infty} \frac{1}{\log t}\,\mathrm{d}t \]
+\end{itemize}
+
+Among them, Neo Euler can be downloaded at \url{https://github.com/khaledhosny/euler-otf}. Other fonts are not free, you need to purchase and use them on your own. (For the Chinese fonts, visit FounderType's website for detail: \url{https://www.foundertype.com} ).
+
+When the corresponding font is not installed, the font that comes with TeX Live will be used instead, and the experience might be reduced.
+
+\section{Document templates}
+
+\singlespacing
+
+\begin{minipage}{0.45\textwidth}
+\begin{code}
+%! TEX program = xelatex
+\documentclass[fast]{lebhart}
+
+\linenumbers
+\UseLanguage{French}
+
+\begin{document}
+
+\title{Titre}
+\author{Nom}
+\date{03 / 2021, Lieu}
+
+\maketitle
+
+%% Texte ici
+
+\end{document}
+\end{code}
+\end{minipage}
+%
+\hfill
+%
+\begin{minipage}{0.45\textwidth}
+\begin{code}
+%! TEX program = xelatex
+\documentclass[fast]{lebhart}
+
+\linenumbers
+\UseLanguage{Chinese}
+
+\begin{document}
+
+\title{标题}
+\author{姓名}
+\date{2021年3月,地点}
+
+\maketitle
+
+%% 正文部分
+
+\end{document}
+\end{code}
+\end{minipage}
+\par
+
+\bigskip
+(\lstinline|\UseLanguage| can be placed either in the preamble or in the body part, and can be used repeatedly as needed)
+
+\end{document}


Property changes on: branches/branch2020.0/Master/texmf-dist/doc/latex/lebhart/lebhart-doc-en.tex
___________________________________________________________________
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: branches/branch2020.0/Master/texmf-dist/tex/latex/lebhart/lebhart.cls
===================================================================
--- branches/branch2020.0/Master/texmf-dist/tex/latex/lebhart/lebhart.cls	                        (rev 0)
+++ branches/branch2020.0/Master/texmf-dist/tex/latex/lebhart/lebhart.cls	2021-03-16 22:17:11 UTC (rev 58457)
@@ -0,0 +1,237 @@
+%%
+%% This is file `lebhart/lebhart.cls',
+%% generated with the docstrip utility.
+
+%% Copyright (C) 2021 by Jinwen XU
+%% 
+%% This is part of the colorist class series.
+%% 
+%% This work may be distributed and/or modified under the conditions of the
+%% LaTeX Project Public License, either version 1.3c of this license or (at
+%% your option) any later version. The latest version of this license is in
+%% 
+%%     http://www.latex-project.org/lppl.txt
+%% 
+%% and version 1.3c or later is part of all distributions of LaTeX version
+%% 2005/12/01 or later.
+%% 
+\NeedsTeXFormat{LaTeX2e}[2020-10-01]
+\ProvidesClass{lebhart}
+    [2021/03/15 A colorful article style]
+\def\colorclass at baseclass{article}
+\RequirePackage{kvoptions}
+\RequirePackage{etoolbox}
+\SetupKeyvalOptions{
+    family = @colorclass,
+    prefix = @colorclass@,
+}
+\DeclareBoolOption[false]{draft}
+\DeclareBoolOption[false]{fast}
+\DeclareDefaultOption{\PassOptionsToClass{\CurrentOption}{\colorclass at baseclass}}
+\ProcessKeyvalOptions*\relax
+\LoadClass{\colorclass at baseclass}
+\if at colorclass@draft
+    \@colorclass at fasttrue
+\fi
+
+%%================================
+%% Page layout
+%%================================
+\RequirePackage[heightrounded]{geometry}
+\geometry{
+    % papersize={8in,11in},
+    a4paper,
+    total={47em,70em},
+    hmarginratio=1:1,
+    vmarginratio=1:1,
+    footnotesep=2em plus 2pt minus 2pt,
+}
+
+\RequirePackage{indentfirst}
+
+\if at colorclass@fast
+    \PassOptionsToPackage{fast}{colorist}
+\fi
+\if at colorclass@fast
+    \PassOptionsToPackage{polyglossia}{colorist}
+\fi
+\RequirePackage{colorist}
+
+%%================================
+%% Fonts
+%%================================
+%% Math fonts in fast mode
+\if at colorclass@fast
+    \RequirePackage{mathpazo}
+\fi
+
+%% English fonts
+\PassOptionsToPackage{no-math}{fontspec}
+\RequirePackage{fontspec}
+\IfFontExistsTF{Palatino Linotype}{%
+    \setmainfont{Palatino Linotype}
+}{
+    \setmainfont{texgyrepagella-regular.otf}[
+        BoldFont       = texgyrepagella-bold.otf ,
+        ItalicFont     = texgyrepagella-italic.otf ,
+        BoldItalicFont = texgyrepagella-bolditalic.otf ]
+}
+    \setsansfont{SourceSansPro-Regular.otf}[
+        Scale          = MatchLowercase,
+        BoldFont       = SourceSansPro-Bold.otf ,
+        ItalicFont     = SourceSansPro-RegularIt.otf ,
+        BoldItalicFont = SourceSansPro-BoldIt.otf ]
+
+%% Chinese fonts
+\PassOptionsToPackage{fontset=none,scheme=plain}{ctex}
+\RequirePackage{ctex}
+\IfFontExistsTF{FZYouSongS 507R}{%
+    \setCJKmainfont{FZYouSongS 507R}[
+        BoldFont       = FZYouSongS 509R ,
+        BoldFeatures   = {FakeBold=2} ,
+        ItalicFont     = * ,
+        BoldItalicFont = FZYouSongS 509R ,
+        BoldItalicFeatures = {FakeBold=2} ,
+        SmallCapsFont  = * ]
+}{
+    \setCJKmainfont{FandolSong-Regular.otf}[
+        BoldFont       = FandolSong-Bold.otf ,
+        ItalicFont     = FandolKai-Regular.otf ,
+        BoldItalicFont = FandolKai-Regular.otf ,
+        BoldItalicFeatures = {FakeBold=4} ,
+        SmallCapsFont  = * ]
+}
+\IfFontExistsTF{FZYouSongS 507R}{%
+    \setCJKmonofont{FZYouSongS 507R}[
+        BoldFont       = FZYouSongS 509R ,
+        BoldFeatures   = {FakeBold=2} ,
+        ItalicFont     = * ,
+        BoldItalicFont = FZYouSongS 509R ,
+        BoldItalicFeatures = {FakeBold=2} ,
+        SmallCapsFont  = * ]
+}{
+    \setCJKmonofont{FandolFang-Regular.otf}[
+        BoldFont       = * ,
+        BoldFeatures   = {FakeBold=4} ,
+        ItalicFont     = * ,
+        BoldItalicFont = * ,
+        BoldItalicFeatures = {FakeBold=4} ,
+        SmallCapsFont  = * ]
+}
+\IfFontExistsTF{FZYouHeiS 506L}{%
+    \setCJKsansfont{FZYouHeiS 506L}[
+        BoldFont       = FZYouHeiS 509R,
+        ItalicFont     = * ,
+        BoldItalicFont = FZYouHeiS 509R ,
+        SmallCapsFont  = * ]
+}{
+    \setCJKsansfont{FandolHei-Regular.otf}[
+        BoldFont       = FandolHei-Bold.otf ,
+        ItalicFont     = * ,
+        BoldItalicFont = FandolHei-Bold.otf ,
+        SmallCapsFont  = * ]
+}
+
+%% Math font
+\if at colorclass@fast\else
+\PassOptionsToPackage
+    {warnings-off={mathtools-colon,mathtools-overbracket}}{unicode-math}
+\RequirePackage{unicode-math}
+\unimathsetup{math-style=ISO}
+\setmathfont{Asana-Math.otf}
+\IfFontExistsTF{Neo Euler}{%
+\setmathfont{Neo Euler} % From https://tex.stackexchange.com/a/425887
+    [range={"0000-"0001,"0020-"007E,
+            "00A0,"00A7-"00A8,"00AC,"00AF,"00B1,"00B4-"00B5,"00B7,
+            "00D7,"00F7,
+            "0131,
+            "0237,"02C6-"02C7,"02D8-"02DA,"02DC,
+            "0300-"030C,"030F,"0311,"0323-"0325,"032E-"0332,"0338,
+            "0391-"0393,"0395-"03A1,"03A3-"03A8,"03B1-"03BB,
+            "03BD-"03C1,"03C3-"03C9,"03D1,"03D5-"03D6,"03F5,
+            "2016,"2018-"2019,"2021,"2026-"202C,"2032-"2037,"2044,
+            "2057,"20D6-"20D7,"20DB-"20DD,"20E1,"20EE-"20EF,
+            "210B-"210C,"210E-"2113,"2118,"211B-"211C,"2126-"2128,
+            "212C-"212D,"2130-"2131,"2133,"2135,"2190-"2199,
+            "21A4,"21A6,"21A9-"21AA,"21BC-"21CC,"21D0-"21D5,
+            "2200,"2202-"2209,"220B-"220C,"220F-"2213,"2215-"221E,
+            "2223,"2225,"2227-"222E,"2234-"2235,"2237-"223D,
+            "2240-"224C,"2260-"2269,"226E-"2279,"2282-"228B,"228E,
+            "2291-"2292,"2295-"2299,"22A2-"22A5,"22C0-"22C5,
+            "22DC-"22DD,"22EF,"22F0-"22F1,
+            "2308-"230B,"2320-"2321,"2329-"232A,"239B-"23AE,
+            "23DC-"23DF,
+            "27E8-"27E9,"27F5-"27FE,"2A0C,"2B1A,
+            "1D400-"1D433,"1D49C,"1D49E-"1D49F,"1D4A2,"1D4A5-"1D4A6,
+            "1D4A9-"1D4AC,"1D4AE-"1D4B5,"1D4D0-"1D4E9,"1D504-"1D505,
+            "1D507-"1D50A,"1D50D-"1D514,"1D516-"1D51C,"1D51E-"1D537,
+            "1D56C-"1D59F,"1D6A8-"1D6B8,"1D6BA-"1D6D2,"1D6D4-"1D6DD,
+            "1D6DF,"1D6E1,"1D7CE-"1D7D7 }]
+}{}
+\fi
+
+\RequirePackage[verbose=silent]{microtype}
+
+%%================================
+%% Graphics
+%%================================
+\RequirePackage{graphicx}
+\graphicspath{{images/}}
+\RequirePackage{wrapfig}
+\RequirePackage{caption}
+
+%%================================
+%% Index
+%%================================
+\RequirePackage{imakeidx}
+
+%%================================
+%% Draft mark
+%%================================
+\def\dnfFont{\ttfamily}
+\def\needgraphFont{\ttfamily}
+
+\def\dnfTextEN{To be finished here}
+\def\needgraphTextEN{A graph is needed here}
+\def\dnfTextFR{À terminer ici}
+\def\needgraphTextFR{Il manque encore un graphique ici}
+\def\dnfTextCN{这里的内容尚未完成}
+\def\needgraphTextCN{这里需要一张图片}
+
+\definecolor{dnfColor}{RGB}{21,122,20}
+\definecolor{needgraphColor}{RGB}{70,130,180}
+
+\if at colorclass@fast
+    \newcommand{\plainBox}[2][-paper]{\textcolor{#1}{%
+    \setlength{\fboxsep}{1.5pt}%
+    \setlength{\fboxrule}{1.2pt}%
+    \fbox{#2}}}
+\else
+    \PassOptionsToPackage{many}{tcolorbox}
+    \RequirePackage{tcolorbox}
+    \newtcbox{\plainBox}[1][-paper]{enhanced jigsaw,%
+        on line, arc = 1.2pt, outer arc = 1pt,breakable,%
+        colframe = #1,colupper=#1,opacityback=0,%
+        boxsep = 1pt,boxrule = 1.2pt,%
+        left = 1pt, right = 1pt, top = 0pt, bottom = 0pt,%
+    }
+\fi
+
+\NewDocumentCommand{\dnf}{d<>}{%
+    \noindent\plainBox[dnfColor]%
+    {\normalfont\dnfFont\bfseries\small%
+    \csname dnfText\csname\languagename ABBR\endcsname\endcsname%
+    \IfNoValueF{#1}{ : #1}}%
+}
+\NewDocumentCommand{\needgraph}{d<>}{%
+    \par%
+    \centerline{\plainBox[needgraphColor]%
+    {\normalfont\needgraphFont\bfseries\small%
+    \csname needgraphText\csname\languagename ABBR\endcsname\endcsname%
+    \IfNoValueF{#1}{ : #1}}}%
+    \par%
+}
+
+\endinput
+%%
+%% End of file `lebhart/lebhart.cls'.


Property changes on: branches/branch2020.0/Master/texmf-dist/tex/latex/lebhart/lebhart.cls
___________________________________________________________________
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: branches/branch2020.0/Master/tlpkg/tlpsrc/lebhart.tlpsrc
===================================================================


More information about the tex-live-commits mailing list.