tsindt/Notizen
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

initiale Übernahme

Browse Source
This commit is contained in:
tsindt
2026-06-03 13:56:26 +02:00
parent c281c28563
commit 262fc39737
805 changed files with 660083 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

92
07_Zettlr/Pandoc/COPYING.rtf Normal file
View File

@@ -0,0 +1,92 @@
{\rtf1\ansi\deff0{\fonttbl{\f0 \fswiss Helvetica;}{\f1 \fmodern Courier;}}
{\colortbl;\red255\green0\blue0;\red0\green0\blue255;}
\widowctrl\hyphauto
{\pard \ql \f0 \sa180 \li0 \fi0 \outlinelevel2 \b \fs28 GNU GENERAL PUBLIC LICENSE\par}
{\pard \ql \f0 \sa180 \li0 \fi0 Version 2, June 1991\par}
{\pard \ql \f0 \sa180 \li0 \fi0 \f1 Copyright (C) 1989, 1991 Free Software Foundation, Inc. \line
<https://fsf.org/>\line
\line
Everyone is permitted to copy and distribute verbatim copies\line
of this license document, but changing it is not allowed.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 \outlinelevel2 \b \fs28 Preamble\par}
{\pard \ql \f0 \sa180 \li0 \fi0 The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software\u8211-to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation\u8217's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 Also, for each author\u8217's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors\u8217' reputations.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone\u8217's free use or not licensed at all.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 The precise terms and conditions for copying, distribution and modification follow.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 \outlinelevel2 \b \fs28 TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 0.} This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The \u8220"Program\u8221", below, refers to any such program or work, and a \u8220"work based on the Program\u8221" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term \u8220"modification\u8221".) Each licensee is addressed as \u8220"you\u8221".\par}
{\pard \ql \f0 \sa180 \li0 \fi0 Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 1.} You may copy and distribute verbatim copies of the Program\u8217's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 2.} You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b a)} You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b b)} You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b c)} If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)\par}
{\pard \ql \f0 \sa180 \li0 \fi0 These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 3.} You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b a)} Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b b)} Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b c)} Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)\par}
{\pard \ql \f0 \sa180 \li0 \fi0 The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 4.} You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 5.} You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 6.} Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients\u8217' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 7.} If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 8.} If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 9.} The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and \u8220"any later version\u8221", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 10.} If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b NO WARRANTY}\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 11.} BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \u8220"AS IS\u8221" 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 PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 {\b 12.} IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 \outlinelevel2 \b \fs28 END OF TERMS AND CONDITIONS\par}
{\pard \ql \f0 \sa180 \li0 \fi0 \outlinelevel2 \b \fs28 How to Apply These Terms to Your New Programs\par}
{\pard \ql \f0 \sa180 \li0 \fi0 If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the \u8220"copyright\u8221" line and a pointer to where the full notice is found.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 \f1 one line to give the program's name and an idea of what it does.\line
Copyright (C) yyyy name of author\line
\line
This program is free software; you can redistribute it and/or\line
modify it under the terms of the GNU General Public License\line
as published by the Free Software Foundation; either version 2\line
of the License, or (at your option) any later version.\line
\line
This program is distributed in the hope that it will be useful,\line
but WITHOUT ANY WARRANTY; without even the implied warranty of\line
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\line
GNU General Public License for more details.\line
\line
You should have received a copy of the GNU General Public License along\line
with this program; if not, see <https://www.gnu.org/licenses/>.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 Also add information on how to contact you by electronic and paper mail.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 If the program is interactive, make it output a short notice like this when it starts in an interactive mode:\par}
{\pard \ql \f0 \sa180 \li0 \fi0 \f1 Gnomovision version 69, Copyright (C) year name of author\line
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details\line
type `show w'. This is free software, and you are welcome\line
to redistribute it under certain conditions; type `show c' \line
for details.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 The hypothetical commands `show w\u8217' and `show c\u8217' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w\u8217' and `show c\u8217'; they could even be mouse-clicks or menu items\u8211-whatever suits your program.\par}
{\pard \ql \f0 \sa180 \li0 \fi0 You should also get your employer (if you work as a programmer) or your school, if any, to sign a \u8220"copyright disclaimer\u8221" for the program, if necessary. Here is a sample; alter the names:\par}
{\pard \ql \f0 \sa180 \li0 \fi0 \f1 Yoyodyne, Inc., hereby disclaims all copyright\line
interest in the program `Gnomovision'\line
(which makes passes at compilers) written \line
by James Hacker.\line
\line
signature of Ty Coon, 1 April 1989\line
Ty Coon, President of Vice\par}
{\pard \ql \f0 \sa180 \li0 \fi0 This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the {\field{\*\fldinst{HYPERLINK "https://www.gnu.org/licenses/lgpl.html"}}{\fldrslt{\ul
GNU Lesser General Public License
}}}
instead of this License.\par}
}

198
07_Zettlr/Pandoc/COPYRIGHT.txt Normal file
View File

@@ -0,0 +1,198 @@
Pandoc
Copyright (C) 2006-2024 John MacFarlane <jgm at berkeley dot edu>
With the exceptions noted below, this code is released under the [GPL],
version 2 or later:
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, see <https://www.gnu.org/licenses/>.
The GNU General Public License is available in the file COPYING.md in
the source distribution. On Debian systems, the complete text of the
GPL can be found in `/usr/share/common-licenses/GPL`.
[GPL]: https://www.gnu.org/copyleft/gpl.html
The complete source code for pandoc version X.Y.Z is available at
<https://hackage.haskell.org/package/pandoc-X.Y.Z/pandoc-X.Y.Z.tar.gz>
and at <https://github.com/jgm/pandoc/tree/X.Y.Z>.
Pandoc includes some code with different copyrights, or subject to different
licenses. The copyright and license statements for these sources are included
below. All are GPL-compatible licenses.
----------------------------------------------------------------------
The modules in the `pandoc-types` repository (Text.Pandoc.Definition,
Text.Pandoc.Builder, Text.Pandoc.Generics, Text.Pandoc.JSON,
Text.Pandoc.Walk) are licensed under the BSD 3-clause license:
Copyright (c) 2006-2024, John MacFarlane
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided
with the distribution.
* Neither the name of John MacFarlane nor the names of other
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------------------------------------------
Pandoc's templates (in `data/templates`) are dual-licensed as either
GPL (v2 or higher, same as pandoc) or (at your option) the BSD
3-clause license.
Copyright (c) 2014--2024, John MacFarlane
----------------------------------------------------------------------
src/Text/Pandoc/Writers/Muse.hs
Copyright (C) 2017-2020 Alexander Krotov
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Writers/Texinfo.hs
Copyright (C) 2008-2024 John MacFarlane and Peter Wang
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Writers/OpenDocument.hs
Copyright (C) 2008-2024 Andrea Rossato and John MacFarlane
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Writers/Org.hs
Copyright (C) 2010-2024 Puneeth Chaganti, John MacFarlane, and
Albert Krewinkel
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Writers/ZimWiki.hs
Copyright (C) 2017 Alex Ivkin
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Readers/Docx.hs
src/Text/Pandoc/Readers/Docx/*
Copyright (C) 2014-2020 Jesse Rosenthal
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Readers/Textile.hs
Copyright (C) 2010-2024 Paul Rivier and John MacFarlane
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Readers/TikiWiki.hs
Copyright (C) 2017 Robin Lee Powell
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Readers/JATS.hs
Copyright (C) 2017-2018 Hamish Mackenzie
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Readers/EPUB.hs
Copyright (C) 2014-2024 Matthew Pickering and John MacFarlane
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Readers/Org.hs
src/Text/Pandoc/Readers/Org/*
test/Tests/Readers/Org/*
Copyright (C) 2014-2024 Albert Krewinkel
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
pandoc-lua-engine/src/Text/Pandoc/Lua.hs
pandoc-lua-engine/src/Text/Pandoc/Lua/*
pandoc-lua-engine/test/lua/*
Copyright (C) 2017--2024 Albert Krewinkel and John MacFarlane
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Readers/Jira.hs
src/Text/Pandoc/Writers/Jira.hs
test/Tests/Readers/Jira.hs
Copyright (C) 2019--2024 Albert Krewinkel
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
src/Text/Pandoc/Readers/FB2.hs
Copyright (C) 2018--2019 Alexander Krotov
Released under the GNU General Public License version 2 or later.
----------------------------------------------------------------------
The dzslides template contains JavaScript and CSS from Paul Rouget's
dzslides template.
https://github.com/paulrouget/dzslides
Released under the Do What the Fuck You Want To Public License.
------------------------------------------------------------------------
Pandoc embeds a Lua interpreter (via hslua).
Copyright © 1994--2023 Lua.org, PUC-Rio.
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

8701
07_Zettlr/Pandoc/Pandoc User's Guide.html Normal file
View File

File diff suppressed because it is too large Load Diff

37
07_Zettlr/Pandoc/THS Article XeLaTeX PDF.yaml Normal file
View File

@@ -0,0 +1,37 @@
# ZETTLR DEFAULTS FILE
# ====================
# Conversion: Markdown --> PDF (requires TeX suite to be installed)
# More info: https://pandoc.org/MANUAL.html
reader: markdown
writer: pdf
self-contained: true
variables:
# Sets the size of the document's pages.
papersize: a5 # Possible values: a0-a6, b0-b6, c0-c6,b0j, letter, executive, legal
# Further variables are documented here: https://pandoc.org/MANUAL.html#variables-for-latex
documentclass: scrartcl
metadata-files: []
include-before-body: []
include-after-body: []
include-in-header: []
bibliography: []
filters:
- type: citeproc
pdf-engine: xelatex # Change this if you want to use a different engine, e.g. pdflatex
dpi: 72
toc: false # Include a table of contents?
toc-depth: 2 # 2 means to only include headings level 1 and 2 in the ToC
number-sections: false
section-divs: true
identifier-prefix: ''
title-prefix: ''
eol: lf
strip-comments: false
indented-code-classes: []
ascii: false
default-image-extension: .jpg
highlight-style: pygments
tab-stop: 4
preserve-tabs: false
fail-if-warnings: false

39
07_Zettlr/Pandoc/THS XeLaTeX PDF.yaml Normal file
View File

@@ -0,0 +1,39 @@
# ZETTLR DEFAULTS FILE
# ====================
# Conversion: Markdown --> PDF (requires TeX suite to be installed)
# More info: https://pandoc.org/MANUAL.html
reader: markdown
writer: pdf
self-contained: true
variables:
# Sets the size of the document's pages.
papersize: a5 # Possible values: a0-a6, b0-b6, c0-c6,b0j, letter, executive, legal
documentclass: scrbook
classoption:
- twoside
# Further variables are documented here: https://pandoc.org/MANUAL.html#variables-for-latex
metadata-files: []
include-before-body: []
include-after-body: []
include-in-header: []
bibliography: []
filters:
- type: citeproc
pdf-engine: xelatex # Change this if you want to use a different engine, e.g. pdflatex
dpi: 72
toc: true # Include a table of contents?
toc-depth: 3 # 2 means to only include headings level 1 and 2 in the ToC
number-sections: true
section-divs: true
identifier-prefix: ''
title-prefix: ''
eol: lf
strip-comments: false
indented-code-classes: []
ascii: false
default-image-extension: .jpg
highlight-style: pygments
tab-stop: 4
preserve-tabs: false
fail-if-warnings: false

40
07_Zettlr/Pandoc/pandoc-templates-main/.github/workflows/generate.yml vendored Normal file
View File

@@ -0,0 +1,40 @@
name: Generate
on:
push:
paths:
- 'templates/**'
workflow_dispatch: {} # Enable manual triggers
workflow_call: {} # Enable other workflows to call this one
env:
NODE_VERSION: '22'
jobs:
generate:
runs-on: ubuntu-latest
steps:
- name: Checkout source
uses: actions/checkout@v4
with:
ref: ${{ github.ref_name }}
- name: Setup NodeJS ${{ env.NODE_VERSION }}
uses: actions/setup-node@v4
with:
node-version: ${{ env.NODE_VERSION }}
cache: npm
- name: Install dependencies
run: npm install
- name: Generate
run: npm run generate
- name: Commit
run: |
git config --local user.email "github-actions[bot]@users.noreply.github.com"
git config --local user.name "github-actions[bot]"
git add metadata.json
git diff-index --quiet HEAD || git commit -m "chore: Regenerate metadata"
- name: Push changes
uses: ad-m/github-push-action@v0.6.0
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
branch: ${{ github.ref_name }}

29
07_Zettlr/Pandoc/pandoc-templates-main/.github/workflows/validate.yml vendored Normal file
View File

@@ -0,0 +1,29 @@
name: Validate
on:
pull_request:
paths:
- 'templates/**'
workflow_dispatch: {} # Enable manual triggers
workflow_call: {} # Enable other workflows to call this one
env:
NODE_VERSION: '22'
jobs:
validate:
runs-on: ubuntu-latest
steps:
- name: Checkout source
uses: actions/checkout@v4
with:
ref: ${{ github.ref_name }}
- name: Setup NodeJS ${{ env.NODE_VERSION }}
uses: actions/setup-node@v4
with:
node-version: ${{ env.NODE_VERSION }}
cache: npm
- name: Install dependencies
run: npm install
- name: Validate
run: npm run validate

3
07_Zettlr/Pandoc/pandoc-templates-main/.gitignore vendored Normal file
View File

@@ -0,0 +1,3 @@
node_modules
.DS_STORE
.yarn

5
07_Zettlr/Pandoc/pandoc-templates-main/.vscode/settings.json vendored Normal file
View File

@@ -0,0 +1,5 @@
{
"yaml.schemas": {
"./template.schema.json": "index.yml"
}
}

1
07_Zettlr/Pandoc/pandoc-templates-main/.yarnrc.yml Normal file
View File

@@ -0,0 +1 @@
nodeLinker: node-modules

83
07_Zettlr/Pandoc/pandoc-templates-main/CONTRIBUTING.md Normal file
View File

@@ -0,0 +1,83 @@
# Contributing
Thank you for contributing to the Pandoc Template Repository! In this document, we describe everything you need to know to successfully open your first PR. We will discuss some general guidelines, and describe the steps required to either modify an existing template, or adding another template.
> [!NOTE]
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119).
> [!NOTE]
> This document defines the terms "layout," "template," and "reference doc" as such: A "layout" for the purposes of this document is, e.g., a `.tex` or `.html`-file that can be filled with content to produce a specific layout of text, but which is not compatible with Pandoc's template syntax. A `template` is this layout, but adapted so that Pandoc can use it as a template. A "reference doc" is a variation of the "template" for use with output formats of Pandoc that support reference docs instead of templates. Naturally, if you create a template for the intent purpose of using it with Pandoc, the "layout" and "template" are one and the same file.
## General Guidelines
The Pandoc Template Repository is intended for community-created and journal- or conference-provided templates that can be used to format Markdown documents (or anything that Pandoc can ingest) in a specific style. That being said, each template needs to follow some criteria:
* It MUST be suitable for a somewhat larger audience. "Somewhat larger audience" SHOULD reference an academic field, a community of people, or any social context that is not defined by kinship. Whether your template fulfills this will be discussed on a case-by-case basis. If you design your own templates, and you believe other people may find them aesthetic, it is suited for this repository. It does not have to be a template for a conference or journal.
* It SHOULD make liberal use of the Pandoc templating system to allow for more than one specific use-case, and ensure that end users can adapt the template to their own documents.
* It MUST be usable as-is, that is, anything dynamic in the template is REQUIRED to be customizable via YAML frontmatter variables, and MUST NOT require the user to modify the template itself.
* It SHOULD NOT require an internet connection to work, that is, all resources the template needs (except, e.g., packages from CTAN) SHOULD be present in the folder. Exceptions are discussed on a case-by-case basis (such as JavaScript libraries for HTML templates).
* You MUST have the right to provide the resources for the template in this repository. If you are not certain (e.g., because you want to adapt a template which has no clearly visible license), it is your responsibility to research this fact, and reflect it appropriately.
* The template SHOULD NOT be time-limited. However, some conferences have new templates each year. In these cases, the template is still suitable for this repository, since the conference itself is not strictly time-limited. Ideally, you SHOULD update an existing template, and denote the corresponding year for which the template is valid in description and/or name, instead of creating new templates each year.
* The language used for the metadata is English. The template can be in a different language (e.g., Portuguese if it is aimed only at, say, Brazilian scholars), and the description MUST indicate this fact, but the metadata itself MUST be in English.
* The template MUST NOT contain any profane language, or language not suitable for an audience below the age of 18. It MUST NOT be in any way legally objectionable in any country globally. You MUST follow common standards for what you can, and cannot write on the internet.
These guidelines are subject to change as we encounter more questions and discussions about whether or not to include a particular template. If you cannot fulfill one or more of these guidelines, you can make a case for inclusion of your template anyways, which will be heard.
### Creating New Templates
Before creating a new template, you MUST make sure that the template does not yet exist in the repository. If the layout has been transformed into a template by someone else already, you MUST modify the template, instead of creating a new one.
**Folder Name**: To create a new template, you MUST create a new folder in this repository. The folder name MUST reflect the template name and SHOULD be an abbreviation. It MUST be an abbreviation if the name is very long. It is RECOMMENDED to use a template provider's "official" abbreviation where available. (Example: The journal "Network Science" abbreviates itself "nws".) The folder name MUST consist of digits, English alphabet letters, and hyphens (a-z0-9-), and it MUST NOT contain any spaces. It MUST be lowercase. It SHOULD be less than 20 characters in length.
### Modifying Existing Templates
To modify an existing template, first make sure that you are familiar with its workings. Ideally, you should be using the template yourself, since most changes SHOULD be rather bug fixes than actual visual changes.
Then, implement your changes to the template files. Afterwards you MUST follow these steps:
1. Add your name to the `authors.contributors` key in the `index.yml` file, if you aren't already an author in there. Create the key if necessary.
2. Update the `updated` timestamp in the `index.yml` file.
3. If necessary/applicable, update `description` and `instructions` in the `index.yml` file.
4. If your change introduced a visual change, we RECOMMEND you update the `preview.png` file.
5. You MUST increment the `version` field in `index.yml` by one.
6. We RECOMMEND you add at least one new entry to the `changelog` key in the `index.yml` file. Create the key if necessary. You MUST include one individual entry for every field you changed in the `defaults.yml` file.
## Guidelines for Template Files
### The `index.yml` file
Fill this file according to the technical specification in the README file.
The `name` property MUST contain the official name of the layout (e.g., the journal name for a template using the journal's official layout). It MUST NOT be a duplicate of an existing name in this repository.
The `description` MUST be precise in explaining to users what they can and cannot do with this template. You MUST use full sentences. Do not use bullet points. However, keep the description as short and concise as possible.
The optional `instructions` property MAY be used to indicate to users any additional steps they need to follow before they can use the template. We RECOMMEND to enumerate the specific LaTeX packages they will need, and indicate any other additional software they may need to install on their computers in this property.
The `authors` MUST correctly reflect the authorship of layout and template. If you found a template online, you MUST accredit the original author. If you yourself designed the template from scratch, "original" and "templater" are the same person.
The `copyright` MUST under all circumstances be precise. If you cannot find a correct copyright for the template, you SHALL NOT propose its inclusion in this repository.
The `changelog` key MUST implement the following guidelines. It MUST be a list of changes implemented since version 1. It MUST contain one entry each per version. More specifically, for every change to the accompanying defaults file, it MUST indicate what you changed, and how. For example, if you changed the `reader` property of the defaults file from `markdown` to `markdown+mark`, you SHOULD write a changelog entry like the following: "Changed the `reader` property in the defaults file from `markdown` to `markdown+mark`." A changelog entry MUST end with a period (`.`). We RECOMMEND you create multiple changelog entries if you did multiple changes, so that the individual bullet points are shorter.
### The `preview.png` file
The `preview.png` file should serve as a quick visual indicator for how the template looks once you export a file with it. For conference or journal templates, you may be able to provide their logo instead. Make sure the copyright allows this.
The image MUST be in landscape orientation and be exactly 600x480px in resolution. It MUST be below 1MB in file size. While especially PDF templates usually result in portrait orientation pages, landscape is more common on the internet, and as such we default to landscape images. You MAY use this to your advantage to include multiple pages in the preview image.
The image MUST NOT contain personal or private information, or reveal any specific information that has nothing to do with the template itself. It MAY contain actual published text, such as a paper.
### The `defaults.yml` file
The `defaults.yml` file is a Pandoc defaults file that contains instructions for Pandoc that allow it to render your template appropriately. It SHOULD be crafted in such a way that the user does not have to change it in order to properly export files.
The file MUST feature a `reader` and `writer` property which can be parsed to indicate to the user how the template is intended to be used. The `reader` SHOULD be `markdown` and MAY include any Pandoc extensions. You can use a different reader, though, where applicable.
The file MUST NOT contain any input or output file specification. This MUST be provided by the user.
The file MUST contain the `template` directive relative to the template file. That is, usually, it should be `template: template.tex` (for a LaTeX template).
The file SHOULD NOT contain more than the absolute minimum of other fields as needed for proper output.
All changes made to this file after the fact MUST BE documented in the `changelog` field of the `index.yml` file.

150
07_Zettlr/Pandoc/pandoc-templates-main/README.md Normal file
View File

@@ -0,0 +1,150 @@
# Pandoc Template Repository
> A repository of Pandoc-compatible templates, ready to go.
Welcome to Zettlr's Pandoc Template Repository. This repository hosts a variety of Pandoc-compatible templates that you can use to transform your Markdown files ready for various conferences, journals, or just for your own pleasure.
This repository aims to grow over time based on user-contributions. Each folder contains all necessary files for one template, including a metadata file with some information.
Each template folder contains at least four required files: A `preview.png` to see what the template looks like in action, an `index.yml` that describes the template, a `defaults.yml` that defines how Pandoc should export files using the template, and a template file itself, which varies depending on the target format (e.g., HTML, PDF, or DOCX).
## Usage
To use these templates, you have two options. The first is to use [Zettlr](https://www.zettlr.com/), which parses the metadata file from this repository automatically, and allows you to install these templates with a beautiful, graphical user interface.
You can also browse these templates from the Zettlr template browser. (TODO)
However, in line with our approach to keep everything fully open, we made sure that these templates work with Pandoc as-is, which means that you do not have to use Zettlr or any specific app to download and use these templates. You can download and use individual templates yourself, using Pandoc directly, or any other app that uses Pandoc under the hood, such as RMarkdown or Quarto. However, please note that, depending on your exact setup, some changes may be required.
To use the templates "bare metal," you can try the following. First, download the entire template folder which you want to use (e.g., `cup-journal`) to your computer. Then, with a Markdown document ready at hand, you can run the following code:
```bash
pandoc --defaults /path/to/the/template/defaults.yml -o output.ext markdown-file.md
```
## Contribute
This repository depends on user contributions, which are described in our [contribution guide](./CONTRIBUTING.md). Please refer to the section on repository structure below to learn how to add or modify templates from a technical perspective. To add a contribution, please follow these steps:
1. Clone this repository locally: `git clone https://github.com/Zettlr/pandoc-templates`
2. Implement your changes or add your template
3. Test your changes (i.e., run an export and verify that it works)
4. Create or adapt the `index.yml` file
5. Commit your changes
6. Open a Pull Request
Once you have opened a pull request, it will be reviewed by trusted contributors, who may instruct you to implement certain changes. Once your PR passes, it will be merged.
> [!NOTE]
> Before starting to add new templates, please review our [contribution guide](./CONTRIBUTING.md). Contributions that do not follow this guide will be rejected without discussion. This pertains particularly to copyrighted content.
## Repository Structure
This section introduces the repository structure. Whenever you add or remove files, or modify a `index.yml` file, ensure that the structure remains valid. Several automated workflows continuously monitor all PRs and verify that none harms the consistency of the file structure.
### File: `metadata.json`
The metadata file serves as a machine-maintained and machine-readable entry point into the repository. Do not modify or touch this file under any circumstances. Zettlr (and, potentially other apps who digest this file) require that the file retains its structure at all times. You may inspect the file. It consists of a large array with one metadata chunk for each template folder. Essentially, each entry corresponds to the same format as the `index.yml` file, with a few changes:
* Each entry has an `id` property equal to its folder name.
* The preview image will be an absolute URL to the image on the repository.
* The object contains `reader` and `writer` properties, indicating from which format Pandoc can convert it into which other format.
### Individual Folder Structure / API Schema
Each individual folder must contain four files at minimum:
* A `index.yml` file, which serves as the entry point for an individual template, and allows apps to digest this repository.
* A `preview.png` file, which is a 600x480px preview image for this template.
* The `template.xyz` file (where `xyz` is the proper filename extension, such as `.tex` or `.htm`). Note that reference docs (as used by Pandoc) are also called "template" for consistency reasons.
* A `defaults.yml` file, which contains directives for Pandoc to export a file using the template successfully.
All other files in the folder are deemed required files for the template. You can add as many or few that you want, and in principle there are no strict naming restrictions (aside that they should not contain spaces, and only stick to the 26 English alphabet characters, and digits).
> [!TIP]
> Refer to the [CONTRIBUTING](CONTRIBUTING.md) file to learn how to create your own template.
### `index.yml`
Each template metadata file requires a set of fields. Below is one example of such a index.yml file:
```yml
name: "Network Science Research Article Submission"
version: 1
updated: "2025-05-03T20:40:00+02:00"
description: |
Use this template to export your submission to the journal Network Science
using the official template from Cambridge University Press.
template: template.tex
preview: preview.png
authors:
original: "Cambridge University Press"
templater: "Hendrik Erz <hendrik@zettlr.com>"
copyright: "All rights reserved (Cambridge University Press)"
```
> [!TIP]
> Each metadata file will be checked against the YAML schema file [`template.schema.json`](./template.schema.json) by automated workflows. We recommend you use VS Code or instruct your editor of choice to validate the `index.yml` files against this schema to ensure your file is valid.
#### `name` (required)
This must be a descriptive name for the template.
#### `version` (required)
The version number. This is simply an integer. This field must be initiated with `1` for a new template. Each change – even if it is just a single character – must result in an increase of this number. "Change" is defined as a single PR, so you can make multiple changes to a template, and only increment the version once.
#### `description` (required)
Describe what this template is, what it aims for, or anything else that is important to know before choosing to use this template. Markdown is supported. Do not include a description of the variables supported by this template, or any setup instructions here. See below.
#### `instructions` (optional)
An optional field with specific instructions for using this template, e.g., for setup. Use this also to, e.g., describe to your users which frontmatter variables your template supports (or which it doesn't).
#### `changelog` (optional/required)
The `changelog` field is optional for version 1, but mandatory for every version afterwards. It is a list of entries, ordered chronologically descending. That is, if you add a changelog entry to an existing template, it must be the first entry. (This makes it easier for users to parse changelogs, as they can be sure the first entry is the most recent change.) You can use Markdown in it, but each item should be short and concise. Use this property in particular to denote changes to the defaults file.
#### `authors` (required)
Tell users who created the template originally, and who adapted the template to use with Pandoc (may contain the same information if you, e.g., created the template from scratch). If you are a contributor, add your name there, too.
* `authors.original`: The name of the original author of the layout
* `authors.templater`: The name of the person who converted this layout into a Pandoc-compatible template
* `authors.contributors`: A list of names of any additional contributors
The fields can be a simple string (implies that this is just the name). You can also be more explicit and use `name: The name`. You must use the property-format if you also want to add an `email` and a `website` (optional).
#### `copyright` (required)
Use this field to tell people the copyright of the template file(s). Ideally, should be a permissive license, but this can also be some form of "all rights reserved" (usually for templates from organizations, e.g., journals).
#### `license` (optional)
If the work has been licensed, include information about it here.
### `defaults.yml`
This is a Pandoc-compatible defaults file. It is required so that users can start using the template with zero setup (except downloading the template). Use this file to do three things:
1. Tell Pandoc where the main entry file for the template is (usually something like `template.tex`).
2. Tell Pandoc the supported `reader` and `writer`, as well as potential extensions (e.g., `+mark`).
3. Add any other information Pandoc needs to successfully produce output (e.g., `shift-heading-level-by: 1` if the template should only use headings level 2 and below).
A minimal example of a `defaults.yml` file for a LaTeX template would be:
```yml
reader: markdown
writer: pdf
pdf-engine: xelatex
template: template.tex
```
### `preview.png`
The preview image must be in 600x480px, which is landscape. It should show how the template looks like when you export a file with it. Where the looks are not the crucial part — such as templates for conferences or journals —, you may also add the conference or journal logo, if copyright permits. We do not yet have hard requirements for this image, except that it must show the template's output, and not violate any common rules of civility. We take discretion in refusing images we deem inappropriate.
## License
This repository is free to use for anybody. It is not licensed, as each template requires its own license field. Refer to the individual folders to learn about the templates' licenses.

61
07_Zettlr/Pandoc/pandoc-templates-main/metadata.json Normal file
View File

@@ -0,0 +1,61 @@
{
"generatedOn": "2025-11-07T09:22:55.795Z",
"templates": [
{
"id": "cup-journal",
"name": "Cambridge University Press Journal Template",
"version": 1,
"description": "Use this template to export your submission to the journal Network Science\nusing the official template from Cambridge University Press.\n",
"instructions": "This template requires the frontmatter variables `title`, `abstract`,\n`keywords`, and `author`. If any of these is not present, the PDF engine may\nthrow errors.\n\nThis template supports the frontmatter variable `cup-journal`, which must be\none of the supported journals of this template:\n\n* Annals of Actuarial Science: `aas``\n* British Journal of Political Science: `jps`\n* Network Science: `nws`\n* Political Analysis: `pla`\n* Political Science Research and Methods: `ram`\n* Evolutionary Human Sciences: `ehs`\n* Natural Language Processing: `nlp`\n\nFurther frontmatter variables supported by this template:\n\n* `title`: The article title\n* `author`: A list of authors, with sub-keys `name`, `affiliation`, and\n `email`. Property `email` is optional; each `author` that has `email` set is\n assumed to be a corresponding author.\n* `keywords`: A list of keywords\n* `abstract`: The article's abstract\n* `acknowledgements`: An acknowledgements section\n* `funding-statement`: A funding statement\n* `competing-interests`: A competing interests statement\n* `data-availability-statement`: A data availability statement\n* `ethical-standards`: A statement on ethical standards\n* `author-contributions`: An author contributions statement\n* `nocite-ids`: A list of works to be referenced in the bibliography that\n haven't been cited in the main body.\n",
"authors": {
"original": "Cambridge University Press",
"templater": {
"name": "Hendrik Erz",
"email": "hendrik@zettlr.com",
"website": "https://www.hendrik-erz.de/"
}
},
"copyright": "Copyright (c) by Mats Dahlgren (1996-1998), Joseph Wright (2008-2018), Overleaf (2019), Donald Arsenau (1989-2009, cite.sty)",
"license": "LaTeX Project Public License (LPPL) 1.3c or later",
"reader": "markdown",
"writer": "pdf",
"preview": "https://raw.githubusercontent.com/Zettlr/pandoc-templates/refs/heads/main/templates/cup-journal/preview.png"
},
{
"id": "ic2s2",
"name": "IC2S2 Conference Abstract",
"version": 1,
"description": "This template allows you to format your extended conference abstracts for the\nInternational Conference of Computational Social Science (IC2S2). This\ntemplate is valid for IC2S2 2025 (Norrköping, Sweden).\n",
"authors": {
"original": {
"name": "The International Society for Computational Social Science (ISCSS)",
"website": "https://iscss.org/"
},
"templater": {
"name": "Hendrik Erz",
"email": "hendrik@zettlr.com",
"website": "https://www.hendrik-erz.de/"
}
},
"copyright": "ICSSI",
"reader": "markdown",
"writer": "pdf",
"preview": "https://raw.githubusercontent.com/Zettlr/pandoc-templates/refs/heads/main/templates/ic2s2/preview.png"
},
{
"id": "simple-application-cover-letter",
"name": "Simple Application Cover Letter",
"version": 1,
"description": "A simple cover letter template for applications.\n",
"instructions": "This template allows you to typeset cover letters for applications. It is\nintended to be run simply by writing the main body of the cover letter in a\nMarkdown file and provide some metadata, including addresses, as YAML\nfrontmatter variables. You have the following variables available:\n\n* `author`: An object with information about yourself. It must contain the\n following keys:\n * `firstname`: Your firstname, and potential middle names\n * `lastname`: Your last, or family name\n * `address`: This is a list of address lines. These appear on the top-right.\n * `email`: Your email address. Appears below the address.\n * `phone`: Your phone number. Appears below the address.\n* `subject`: This is the subject line of the cover letter. Appears between\n addressée and the main body of your letter.\n* `to_address`: This is a list of address lines to where you are addressing\n the letter.\n* `attachments`: If you have attachments to your application (such as a CV),\n and want to include them on your letter, list them here.\n* `attachments_title`: By default, the attachment section will be headed by\n \"Attachments\". Here you can customize this (e.g., by translating).\n\nNote that you also have some of the standard Pandoc variables such as\n`fontsize` available to use in your frontmatter, too.\n",
"authors": {
"original": "Unknown",
"templater": "Hendrik Erz"
},
"copyright": "None",
"reader": "markdown+mark",
"writer": "pdf",
"preview": "https://raw.githubusercontent.com/Zettlr/pandoc-templates/refs/heads/main/templates/simple-application-cover-letter/preview.png"
}
]
}

99
07_Zettlr/Pandoc/pandoc-templates-main/package-lock.json generated Normal file
View File

@@ -0,0 +1,99 @@
{
"name": "pandoc-templates",
"version": "1.0.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "pandoc-templates",
"version": "1.0.0",
"dependencies": {
"ajv": "^8.17.1",
"ajv-formats": "^3.0.1",
"yaml": "^2.7.1"
}
},
"node_modules/ajv": {
"version": "8.17.1",
"resolved": "https://registry.npmjs.org/ajv/-/ajv-8.17.1.tgz",
"integrity": "sha512-B/gBuNg5SiMTrPkC+A2+cW0RszwxYmn6VYxB/inlBStS5nx6xHIt/ehKRhIMhqusl7a8LjQoZnjCs5vhwxOQ1g==",
"license": "MIT",
"dependencies": {
"fast-deep-equal": "^3.1.3",
"fast-uri": "^3.0.1",
"json-schema-traverse": "^1.0.0",
"require-from-string": "^2.0.2"
},
"funding": {
"type": "github",
"url": "https://github.com/sponsors/epoberezkin"
}
},
"node_modules/ajv-formats": {
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/ajv-formats/-/ajv-formats-3.0.1.tgz",
"integrity": "sha512-8iUql50EUR+uUcdRQ3HDqa6EVyo3docL8g5WJ3FNcWmu62IbkGUue/pEyLBW8VGKKucTPgqeks4fIU1DA4yowQ==",
"license": "MIT",
"dependencies": {
"ajv": "^8.0.0"
},
"peerDependencies": {
"ajv": "^8.0.0"
},
"peerDependenciesMeta": {
"ajv": {
"optional": true
}
}
},
"node_modules/fast-deep-equal": {
"version": "3.1.3",
"resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz",
"integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==",
"license": "MIT"
},
"node_modules/fast-uri": {
"version": "3.0.6",
"resolved": "https://registry.npmjs.org/fast-uri/-/fast-uri-3.0.6.tgz",
"integrity": "sha512-Atfo14OibSv5wAp4VWNsFYE1AchQRTv9cBGWET4pZWHzYshFSS9NQI6I57rdKn9croWVMbYFbLhJ+yJvmZIIHw==",
"funding": [
{
"type": "github",
"url": "https://github.com/sponsors/fastify"
},
{
"type": "opencollective",
"url": "https://opencollective.com/fastify"
}
],
"license": "BSD-3-Clause"
},
"node_modules/json-schema-traverse": {
"version": "1.0.0",
"resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-1.0.0.tgz",
"integrity": "sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==",
"license": "MIT"
},
"node_modules/require-from-string": {
"version": "2.0.2",
"resolved": "https://registry.npmjs.org/require-from-string/-/require-from-string-2.0.2.tgz",
"integrity": "sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==",
"license": "MIT",
"engines": {
"node": ">=0.10.0"
}
},
"node_modules/yaml": {
"version": "2.7.1",
"resolved": "https://registry.npmjs.org/yaml/-/yaml-2.7.1.tgz",
"integrity": "sha512-10ULxpnOCQXxJvBgxsn9ptjq6uviG/htZKk9veJGhlqn3w/DxQ631zFF+nlQXLwmImeS5amR2dl2U8sg6U9jsQ==",
"license": "ISC",
"bin": {
"yaml": "bin.mjs"
},
"engines": {
"node": ">= 14"
}
}
}
}

24
07_Zettlr/Pandoc/pandoc-templates-main/package.json Normal file
View File

@@ -0,0 +1,24 @@
{
"name": "pandoc-templates",
"version": "1.0.0",
"description": "A collection of ready-to-use, Pandoc-compatible templates",
"main": "index.js",
"scripts": {
"validate": "node ./scripts/validate-templates.js",
"generate": "node ./scripts/generate-metadata.js",
"test": "echo \"Error: no test specified\" && exit 1"
},
"type": "module",
"keywords": [
"pandoc",
"template",
"pdf",
"html"
],
"author": "Hendrik Erz <hendrik@zettlr.com>",
"dependencies": {
"ajv": "^8.17.1",
"ajv-formats": "^3.0.1",
"yaml": "^2.7.1"
}
}

43
07_Zettlr/Pandoc/pandoc-templates-main/scripts/generate-metadata.js Normal file
View File

@@ -0,0 +1,43 @@
// This file takes all templates in the template folder, and (re)generates
// the metadata.json file.
import fs from 'fs'
import path from 'path'
import yaml from 'yaml'
const templates = fs.readdirSync('templates')
.filter(name => {
const stat = fs.statSync(`templates/${name}`)
return stat.isDirectory()
})
const metadata = {
generatedOn: new Date().toISOString(),
templates: []
}
for (const template of templates) {
console.log(`Reading template ${template}...`)
let data, parsedData
data = fs.readFileSync(`templates/${template}/index.yml`, 'utf-8')
parsedData = yaml.parse(data)
const templateData = {
id: template, // Folder name == ID
...parsedData
}
// Provide reader/writer properties
data = fs.readFileSync(`templates/${template}/defaults.yml`, 'utf-8')
parsedData = yaml.parse(data)
templateData.reader = parsedData.reader
templateData.writer = parsedData.writer
// Transform image to URL
const basePath = `/Zettlr/pandoc-templates/refs/heads/main/templates/`
const fullPath = path.join(basePath, template, 'preview.png')
templateData.preview = 'https://raw.githubusercontent.com' + fullPath
metadata.templates.push(templateData)
}
fs.writeFileSync('metadata.json', JSON.stringify(metadata, undefined, 2), 'utf-8')

74
07_Zettlr/Pandoc/pandoc-templates-main/scripts/validate-templates.js Normal file
View File

@@ -0,0 +1,74 @@
// This file validates all templates in the template folder.
import fs from 'fs'
import Ajv from 'ajv'
import addFormats from "ajv-formats"
import yaml from 'yaml'
const REQUIRED_FILES = ['index.yml', 'defaults.yml', 'preview.png']
// Preflight: Load JSON schema
const data = fs.readFileSync('template.schema.json', 'utf-8')
const schemaJson = JSON.parse(data)
// Read in all templates
const templates = fs.readdirSync('templates')
.filter(name => {
const stat = fs.statSync(`templates/${name}`)
return stat.isDirectory()
})
const errors = []
for (const template of templates) {
let data, parsedData
console.log(`Checking ${template}...`)
// Check for required files
const contents = fs.readdirSync(`templates/${template}`)
for (const file of REQUIRED_FILES) {
if (!contents.includes(file)) {
errors.push(new Error(`Template ${template}: Required file ${file} not found`))
}
}
if (!contents.includes('index.yml') || !contents.includes('defaults.yml')) {
continue
}
data = fs.readFileSync(`templates/${template}/index.yml`, 'utf-8')
parsedData = yaml.parse(data)
// Validate index.yml
const ajv = new Ajv()
addFormats(ajv) // Required to parse `format`, such as `date-time`
const validate = ajv.compile(schemaJson)
const isValid = validate(parsedData)
if (!isValid) {
if (validate.errors) {
for (const error of validate.errors) {
errors.push(new Error(`Template ${template} [index.yml]: ${error.message}`))
}
} else {
errors.push(new Error(`Template ${template} [index.yml]: Errors encountered while parsing index.yml`))
}
}
// Validate defaults.yml
data = fs.readFileSync(`templates/${template}/defaults.yml`, 'utf-8')
parsedData = yaml.parse(data)
if (parsedData.writer === undefined || parsedData.reader === undefined) {
errors.push(new Error(`Template ${template} [defaults.yml]: Reader or writer property not present.`))
}
}
if (errors.length > 0) {
console.error('=== VALIDATION FAILED ===\n')
for (const error of errors) {
console.error(error.message)
}
process.exit(1)
} else {
console.log('Validation successful.')
process.exit(0)
}

138
07_Zettlr/Pandoc/pandoc-templates-main/template.schema.json Normal file
View File

@@ -0,0 +1,138 @@
{
"title": "Pandoc Templates index.yml Schema",
"description": "A schema to validate template metadata files against.",
"type": "object",
"properties": {
"name": {
"description": "The full name of this template.",
"type": "string"
},
"version": {
"description": "The version number of this template. Must start at `1` and be incremented for each change.",
"type": "number"
},
"changelog": {
"description": "Describe changes to this template, one change per item",
"type": "array",
"items": { "type": "string" }
},
"description": {
"description": "Describe the template. Markdown is supported. Be as extensive as necessary, but as concise as possible. Do not include setup instructions here (see property `instructions`).",
"type": "string"
},
"instructions": {
"description": "If the template requires some setup, explain this here. Also, describe any variables the template supports.",
"type": "string"
},
"authors": {
"type": "object",
"description": "People or organizations who have contributed to this template.",
"required": [
"original",
"templater"
],
"properties": {
"original": {
"description": "Original author of the template itself (not the adaptation to Pandoc). Can be the same as `templater`.",
"anyOf": [
{
"type": "string"
},
{
"type": "object",
"properties": {
"name": {
"type": "string"
},
"email": {
"type": "string",
"format": "email"
},
"website": {
"type": "string",
"format": "uri"
}
},
"required": [
"name"
]
}
]
},
"templater": {
"description": "The person or institution who has adapted this template for usage with Pandoc (can be the same as `original`).",
"anyOf": [
{
"type": "string"
},
{
"type": "object",
"properties": {
"name": {
"type": "string"
},
"email": {
"type": "string",
"format": "email"
},
"website": {
"type": "string",
"format": "uri"
}
},
"required": [
"name"
]
}
]
},
"contributors": {
"description": "A list of contributors to this template, aside from `original` and `templater`.",
"type": "array",
"items": {
"anyOf": [
{
"type": "string"
},
{
"type": "object",
"properties": {
"name": {
"type": "string"
},
"email": {
"type": "string",
"format": "email"
},
"website": {
"type": "string",
"format": "uri"
}
},
"required": [
"name"
]
}
]
}
}
}
},
"copyright": {
"description": "Use this to describe the template's copyright(s).",
"type": "string"
},
"license": {
"description": "Is the template licensed? If so, include a canonical form of the license name.",
"type": "string"
}
},
"additionalProperties": false,
"required": [
"name",
"version",
"description",
"authors",
"copyright"
]
}

2263
07_Zettlr/Pandoc/pandoc-templates-main/templates/cup-journal/cup-journal.cls Normal file
View File

File diff suppressed because it is too large Load Diff

BIN
07_Zettlr/Pandoc/pandoc-templates-main/templates/cup-journal/cup-logo-new.pdf Normal file
View File

Binary file not shown.

5
07_Zettlr/Pandoc/pandoc-templates-main/templates/cup-journal/defaults.yml Normal file
View File

@@ -0,0 +1,5 @@
# Defaults file for CUP Journal template
reader: markdown
writer: pdf
pdf-engine: xelatex
template: ./template.tex

45
07_Zettlr/Pandoc/pandoc-templates-main/templates/cup-journal/index.yml Normal file
View File

@@ -0,0 +1,45 @@
name: "Cambridge University Press Journal Template"
version: 1
description: |
Use this template to export your submission to the journal Network Science
using the official template from Cambridge University Press.
instructions: |
This template requires the frontmatter variables `title`, `abstract`,
`keywords`, and `author`. If any of these is not present, the PDF engine may
throw errors.
This template supports the frontmatter variable `cup-journal`, which must be
one of the supported journals of this template:
* Annals of Actuarial Science: `aas``
* British Journal of Political Science: `jps`
* Network Science: `nws`
* Political Analysis: `pla`
* Political Science Research and Methods: `ram`
* Evolutionary Human Sciences: `ehs`
* Natural Language Processing: `nlp`
Further frontmatter variables supported by this template:
* `title`: The article title
* `author`: A list of authors, with sub-keys `name`, `affiliation`, and
`email`. Property `email` is optional; each `author` that has `email` set is
assumed to be a corresponding author.
* `keywords`: A list of keywords
* `abstract`: The article's abstract
* `acknowledgements`: An acknowledgements section
* `funding-statement`: A funding statement
* `competing-interests`: A competing interests statement
* `data-availability-statement`: A data availability statement
* `ethical-standards`: A statement on ethical standards
* `author-contributions`: An author contributions statement
* `nocite-ids`: A list of works to be referenced in the bibliography that
haven't been cited in the main body.
authors:
original: "Cambridge University Press"
templater:
name: "Hendrik Erz"
email: "hendrik@zettlr.com"
website: "https://www.hendrik-erz.de/"
copyright: "Copyright (c) by Mats Dahlgren (1996-1998), Joseph Wright (2008-2018), Overleaf (2019), Donald Arsenau (1989-2009, cite.sty)"
license: "LaTeX Project Public License (LPPL) 1.3c or later"

BIN
07_Zettlr/Pandoc/pandoc-templates-main/templates/cup-journal/preview.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 67 KiB

125
07_Zettlr/Pandoc/pandoc-templates-main/templates/cup-journal/template.tex Normal file
View File

@@ -0,0 +1,125 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% To select a journal, use its code for the
% journal= option in the \documentclass command.
% The journal codes for this template are:
%
% Annals of Actuarial Science: aas
% British Journal of Political Science: jps
% Network Science: nws
% Political Analysis: pla
% Political Science Research and Methods: ram
% Evolutionary Human Sciences: ehs
% Natural Language Processing: nlp
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\documentclass[
journal=$cup-journal$,
manuscript=Research\ Article,
year=,
volume=,
]{cup-journal}
\usepackage{amsmath}
\usepackage[nopatch]{microtype}
\usepackage{booktabs}
$fonts.latex()$
$font-settings.latex()$
$common.latex()$
$for(header-includes)$
$header-includes$
$endfor$
$after-header-includes.latex()$
$hypersetup.latex()$
\title{$title$}
$if(author)$
$for(author)$
\author{$author.name$}
\affiliation{$author.affiliation$}
% Every author with an email set will be assumed corresponding author.
$if(author.email)$
\email[$author.name$]{$author.email$}
$endif$
$endfor$
$endif$
\keywords{$for(keywords)$$keywords$$sep$, $endfor$}
\begin{document}
% DOC START
$if(abstract)$
\begin{abstract}
$abstract$
\end{abstract}
$endif$
$for(include-before)$
$include-before$
$endfor$
$body$
$if(acknowledgements)$
\paragraph{Acknowledgments}
$acknowledgements$
$endif$
$if(funding-statement)$
\paragraph{Funding Statement}
$funding-statement$
$endif$
$if(competing-interests)$
\paragraph{Competing Interests}
$competing-interests$
$endif$
$if(data-availability-statement)$
\paragraph{Data Availability Statement}
$data-availability-statement$
$endif$
$if(ethical-standards)$
\paragraph{Ethical Standards}
$ethical-standards$
$endif$
$if(author-contributions)$
\paragraph{Author Contributions}
$author-contributions$
$endif$
%\endnote in some journals will behave like \footnote; and \printendnotes will not output anything.
\printendnotes
$if(nocite-ids)$
\nocite{$for(nocite-ids)$$it$$sep$, $endfor$}
$endif$
$if(natbib)$
$if(bibliography)$
$if(biblio-title)$
$if(has-chapters)$
\renewcommand\bibname{$biblio-title$}
$else$
\renewcommand\refname{$biblio-title$}
$endif$
$endif$
\bibliography{$for(bibliography)$$bibliography$$sep$,$endfor$}
$endif$
$endif$
$if(biblatex)$
\printbibliography$if(biblio-title)$[title=$biblio-title$]$endif$
$endif$
$for(include-after)$
$include-after$
$endfor$
\end{document}

6
07_Zettlr/Pandoc/pandoc-templates-main/templates/ic2s2/defaults.yml Normal file
View File

@@ -0,0 +1,6 @@
# Defaults file for IC2S2 template
reader: markdown
writer: pdf
pdf-engine: xelatex
template: ./template.tex
shift-heading-level-by: 1 # Heading 1 -> Heading 2

15
07_Zettlr/Pandoc/pandoc-templates-main/templates/ic2s2/index.yml Normal file
View File

@@ -0,0 +1,15 @@
name: "IC2S2 Conference Abstract"
version: 1
description: |
This template allows you to format your extended conference abstracts for the
International Conference of Computational Social Science (IC2S2). This
template is valid for IC2S2 2025 (Norrköping, Sweden).
authors:
original:
name: "The International Society for Computational Social Science (ISCSS)"
website: "https://iscss.org/"
templater:
name: "Hendrik Erz"
email: "hendrik@zettlr.com"
website: "https://www.hendrik-erz.de/"
copyright: "ICSSI"

BIN
07_Zettlr/Pandoc/pandoc-templates-main/templates/ic2s2/preview.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 28 KiB

83
07_Zettlr/Pandoc/pandoc-templates-main/templates/ic2s2/template.tex Normal file
View File

@@ -0,0 +1,83 @@
\documentclass[a4paper,12pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[english]{babel}
\usepackage{authblk}
\usepackage{graphicx}
\usepackage{mathptmx}
\usepackage[singlespacing]{setspace}
\usepackage[headheight=1in,margin=1in]{geometry}
\usepackage{fancyhdr}
\renewcommand{\headrulewidth}{0pt}
\pagestyle{fancy}
\setcounter{secnumdepth}{-\maxdimen} % remove section numbering (taken from Pandoc default template)
\makeatletter
\def\@maketitle{%
\newpage
\begin{center}%
\let \footnote \thanks
{\LARGE \@title \par}%
\end{center}%
\par
\vskip 0.1em}
\makeatother
\lhead{}
\chead{%
$$11$$$$^{th}$$ International Conference on Computational Social Science IC$$^{2}$$S$$^{2}$$\\
July 21-24, 2025, Norrköping, Sweden%
}
\rhead{}
\graphicspath{{images/}}
\title{$title$}
$if(date)$
\date{$date$}
$else$
\date{\today}
$endif$
\begin{document}
\maketitle
\thispagestyle{fancy}
\begin{center}
\textit{Keywords: $for(keywords)$$keywords$$sep$, $endfor$}
\newline
\end{center}
\section*{Extended Abstract}
$body$
$if(nocite-ids)$
\nocite{$for(nocite-ids)$$it$$sep$, $endfor$}
$endif$
\section*{References}
$if(natbib)$
$if(bibliography)$
$if(biblio-title)$
$if(has-chapters)$
\renewcommand\bibname{$biblio-title$}
$else$
\renewcommand\refname{$biblio-title$}
$endif$
$endif$
\bibliography{$for(bibliography)$$bibliography$$sep$,$endfor$}
$endif$
$endif$
$if(biblatex)$
\printbibliography
$endif$
\end{document}

191
07_Zettlr/Pandoc/pandoc-templates-main/templates/simple-application-cover-letter/application_cover_letter.tex Normal file
View File

@@ -0,0 +1,191 @@
$passoptions.latex()$
\documentclass[
$for(babel-otherlangs)$
$babel-otherlangs$,
$endfor$
$if(babel-lang)$
$babel-lang$,
$endif$
$if(fontsize)$
$fontsize$,
$endif$
$if(papersize)$
$papersize$paper,
$else$
a4paper,
$endif$
$for(classoption)$
$classoption$$sep$,
$endfor$
]{article}
%%%%%%%
\usepackage{xcolor}
\usepackage{amsmath,amssymb}
$if(cancel)$
\usepackage{cancel}
$endif$
$--
$-- section numbering
$--
$if(numbersections)$
\setcounter{secnumdepth}{$if(secnumdepth)$$secnumdepth$$else$5$endif$}
$else$
\setcounter{secnumdepth}{-\maxdimen} % remove section numbering
$endif$
$fonts.latex()$
$font-settings.latex()$
$common.latex()$
$for(header-includes)$
$header-includes$
$endfor$
$after-header-includes.latex()$
$hypersetup.latex()$
$if(pdf-trailer-id)$
\ifXeTeX
\special{pdf:trailerid [ $pdf-trailer-id$ ]}
\fi
\ifPDFTeX
\pdftrailerid{}
\pdftrailer{/ID [ $pdf-trailer-id$ ]}
\fi
\ifLuaTeX
\pdfvariable trailerid {[ $pdf-trailer-id$ ]}
\fi
$endif$
%%%%%%%
\usepackage[$if(babel-lang)$$babel-lang$$else$english$endif$]{babel}
\usepackage[utf8x]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{lmodern}
\usepackage{marvosym}
\usepackage[dvips]{graphicx}
\pagestyle{empty}
\def\textblockwidth{35mm}
$if(attachments)$
\def\marginaliasize{50mm}
$else$
\def\marginaliasize{20mm}
$endif$
\usepackage[
scale=0.775,
top=20mm,
bottom=20mm,
left=\marginaliasize, % To place attachment list to the side
right=20mm
]{geometry}
\setlength{\parindent}{0pt}
\addtolength{\parskip}{6pt}
\renewcommand{\ttdefault}{pcr}
\usepackage{url}
\urlstyle{tt}
\usepackage{hyperref}
\hypersetup{
pdfauthor = $author.firstname$ $author.lastname$,%
pdftitle = Application $author.firstname$ $author.lastname$,%
pdfsubject = Application,%
pdfcreator = \LaTeX,%
pdfproducer = \LaTeX
}
\definecolor{color1}{RGB}{85,85,125}
\definecolor{color2}{RGB}{57,74,138}
\definecolor{attachments}{RGB}{128, 128, 128}
\hypersetup{pdfborder=0 0 0}
\usepackage{pdfpages}
\usepackage{ragged2e} % For enabling hyphenation on demand (RaggedRight instead of raggedright)
% Additional stuff for the CV attachments
\usepackage[overlay,absolute]{textpos}
\usepackage{enumitem} % For very tight lists
\begin{document}
\sffamily % for use with a résumé using sans serif fonts;
%\rmfamily % for use with a résumé using serif fonts;
$for(include-before)$
$include-before$
$endfor$
$if(linestretch)$
\setstretch{$linestretch$}
$endif$
\hfill%
\begin{minipage}[t]{1\textwidth}
\begin{FlushRight}
{\bfseries\color{color1} $author.firstname$ $author.lastname$}\\[.35ex]
\small%
$for(author.address)$
$it$ \\
$endfor$ [.35ex]
\Mobilefone~$author.phone$\\
\Letter~\href{mailto:$author.email$}{$author.email$}
\end{FlushRight}
\end{minipage}
%
{\color{color1}\rule{\textwidth}{.25ex}}
%
\vspace{.25ex}
\begin{minipage}[t]{1\textwidth}
\begin{FlushLeft}
$for(to_address)$
$to_address$ \\
$endfor$
\end{FlushLeft}
\end{minipage}
\vspace{-2em}
\begin{minipage}[t]{1\textwidth}
\begin{FlushRight}
$if(date)$
$date$
$else$
\today
$endif$
\end{FlushRight}
\end{minipage}
\vspace{1em}
{\bfseries \color{color2}$subject$}
\vspace{1em}
$body$
$if(attachments)$
\textblockorigin{0mm}{0mm}
\begin{textblock*}{30mm}[0,0](15mm,20mm) % Place on top
\begin{minipage}[t]{30mm}
\raggedright
\color{attachments}
\fontsize{8}{8}\selectfont
%\tiny
{\bfseries $if(attachments_title)$$attachments_title$$else$Attachments$endif$}\\[5mm]
\begin{itemize}[leftmargin=0mm]
\setlength\itemsep{2pt}
$for(attachments)$
\item[--] $attachments$
$endfor$
\end{itemize}
\end{minipage}
\end{textblock*}
$endif$
\end{document}

33
07_Zettlr/Pandoc/pandoc-templates-main/templates/simple-application-cover-letter/defaults.yml Normal file
View File

@@ -0,0 +1,33 @@
# ZETTLR DEFAULTS FILE
# ====================
# Conversion: Markdown --> PDF (requires TeX suite to be installed)
# More info: https://pandoc.org/MANUAL.html
reader: markdown+mark
writer: pdf
self-contained: true
file-scope: true
template: '/Users/hendrik/Nextcloud/Templates/application_cover_letter.tex'
variables:
# Sets the size of the document's pages.
papersize: a4 # Possible values: a0-a6, b0-b6, c0-c6,b0j, letter, executive, legal
# Further variables are documented here: https://pandoc.org/MANUAL.html#variables-for-latex
metadata:
reference-section-title: References
top-level-division: default
pdf-engine: xelatex # Change this if you want to use a different engine, e.g. pdflatex
dpi: 72
toc: false # Include a table of contents?
toc-depth: 2 # 2 means to only include headings level 1 and 2 in the ToC
number-sections: false
section-divs: true
identifier-prefix: ''
title-prefix: ''
eol: lf
strip-comments: false
indented-code-classes: []
ascii: false
default-image-extension: .jpg
highlight-style: pygments
tab-stop: 4
preserve-tabs: false
fail-if-warnings: false

32
07_Zettlr/Pandoc/pandoc-templates-main/templates/simple-application-cover-letter/index.yml Normal file
View File

@@ -0,0 +1,32 @@
name: Simple Application Cover Letter
version: 1
description: |
A simple cover letter template for applications.
instructions: |
This template allows you to typeset cover letters for applications. It is
intended to be run simply by writing the main body of the cover letter in a
Markdown file and provide some metadata, including addresses, as YAML
frontmatter variables. You have the following variables available:
* `author`: An object with information about yourself. It must contain the
following keys:
* `firstname`: Your firstname, and potential middle names
* `lastname`: Your last, or family name
* `address`: This is a list of address lines. These appear on the top-right.
* `email`: Your email address. Appears below the address.
* `phone`: Your phone number. Appears below the address.
* `subject`: This is the subject line of the cover letter. Appears between
addressée and the main body of your letter.
* `to_address`: This is a list of address lines to where you are addressing
the letter.
* `attachments`: If you have attachments to your application (such as a CV),
and want to include them on your letter, list them here.
* `attachments_title`: By default, the attachment section will be headed by
"Attachments". Here you can customize this (e.g., by translating).
Note that you also have some of the standard Pandoc variables such as
`fontsize` available to use in your frontmatter, too.
authors:
original: Unknown
templater: Hendrik Erz
copyright: None

BIN
07_Zettlr/Pandoc/pandoc-templates-main/templates/simple-application-cover-letter/preview.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 70 KiB

79
07_Zettlr/Pandoc/pandoc-templates-main/yarn.lock Normal file
View File

@@ -0,0 +1,79 @@
# This file is generated by running "yarn install" inside your project.
# Manual changes might be lost - proceed with caution!
__metadata:
version: 8
cacheKey: 10c0
"ajv-formats@npm:^3.0.1":
version: 3.0.1
resolution: "ajv-formats@npm:3.0.1"
dependencies:
ajv: "npm:^8.0.0"
peerDependencies:
ajv: ^8.0.0
peerDependenciesMeta:
ajv:
optional: true
checksum: 10c0/168d6bca1ea9f163b41c8147bae537e67bd963357a5488a1eaf3abe8baa8eec806d4e45f15b10767e6020679315c7e1e5e6803088dfb84efa2b4e9353b83dd0a
languageName: node
linkType: hard
"ajv@npm:^8.0.0, ajv@npm:^8.17.1":
version: 8.17.1
resolution: "ajv@npm:8.17.1"
dependencies:
fast-deep-equal: "npm:^3.1.3"
fast-uri: "npm:^3.0.1"
json-schema-traverse: "npm:^1.0.0"
require-from-string: "npm:^2.0.2"
checksum: 10c0/ec3ba10a573c6b60f94639ffc53526275917a2df6810e4ab5a6b959d87459f9ef3f00d5e7865b82677cb7d21590355b34da14d1d0b9c32d75f95a187e76fff35
languageName: node
linkType: hard
"fast-deep-equal@npm:^3.1.3":
version: 3.1.3
resolution: "fast-deep-equal@npm:3.1.3"
checksum: 10c0/40dedc862eb8992c54579c66d914635afbec43350afbbe991235fdcb4e3a8d5af1b23ae7e79bef7d4882d0ecee06c3197488026998fb19f72dc95acff1d1b1d0
languageName: node
linkType: hard
"fast-uri@npm:^3.0.1":
version: 3.1.0
resolution: "fast-uri@npm:3.1.0"
checksum: 10c0/44364adca566f70f40d1e9b772c923138d47efeac2ae9732a872baafd77061f26b097ba2f68f0892885ad177becd065520412b8ffeec34b16c99433c5b9e2de7
languageName: node
linkType: hard
"json-schema-traverse@npm:^1.0.0":
version: 1.0.0
resolution: "json-schema-traverse@npm:1.0.0"
checksum: 10c0/71e30015d7f3d6dc1c316d6298047c8ef98a06d31ad064919976583eb61e1018a60a0067338f0f79cabc00d84af3fcc489bd48ce8a46ea165d9541ba17fb30c6
languageName: node
linkType: hard
"pandoc-templates@workspace:.":
version: 0.0.0-use.local
resolution: "pandoc-templates@workspace:."
dependencies:
ajv: "npm:^8.17.1"
ajv-formats: "npm:^3.0.1"
yaml: "npm:^2.7.1"
languageName: unknown
linkType: soft
"require-from-string@npm:^2.0.2":
version: 2.0.2
resolution: "require-from-string@npm:2.0.2"
checksum: 10c0/aaa267e0c5b022fc5fd4eef49d8285086b15f2a1c54b28240fdf03599cbd9c26049fee3eab894f2e1f6ca65e513b030a7c264201e3f005601e80c49fb2937ce2
languageName: node
linkType: hard
"yaml@npm:^2.7.1":
version: 2.8.1
resolution: "yaml@npm:2.8.1"
bin:
yaml: bin.mjs
checksum: 10c0/7c587be00d9303d2ae1566e03bc5bc7fe978ba0d9bf39cc418c3139d37929dfcb93a230d9749f2cb578b6aa5d9ebebc322415e4b653cb83acd8bc0bc321707f3
languageName: node
linkType: hard

BIN
07_Zettlr/Pandoc/pandoc.exe Normal file
View File

Binary file not shown.

707
07_Zettlr/Pandoc/templates/eisvogel.beamer Normal file
View File

@@ -0,0 +1,707 @@
%%
% Copyright (c) 2017 - 2025, Pascal Wagler;
% Copyright (c) 2014 - 2025, John MacFarlane
%
% All rights reserved.
%
% Redistribution and use in source and binary forms, with or without
% modification, are permitted provided that the following conditions
% are met:
%
% - Redistributions of source code must retain the above copyright
% notice, this list of conditions and the following disclaimer.
%
% - Redistributions in binary form must reproduce the above copyright
% notice, this list of conditions and the following disclaimer in the
% documentation and/or other materials provided with the distribution.
%
% - Neither the name of John MacFarlane nor the names of other
% contributors may be used to endorse or promote products derived
% from this software without specific prior written permission.
%
% THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
% "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
% LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
% FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
% COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
% INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
% BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
% LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
% CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
% LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
% ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
% POSSIBILITY OF SUCH DAMAGE.
%%
%%
% This is the Eisvogel pandoc LaTeX template.
%
% For usage information and examples visit the official GitHub page:
% https://github.com/Wandmalfarbe/pandoc-latex-template
%%
% Options for packages loaded elsewhere
\PassOptionsToPackage{unicode$for(hyperrefoptions)$,$hyperrefoptions$$endfor$}{hyperref}
\PassOptionsToPackage{hyphens}{url}
\PassOptionsToPackage{dvipsnames,svgnames,x11names,table}{xcolor}
$if(CJKmainfont)$
\PassOptionsToPackage{space}{xeCJK}
$endif$
\documentclass[
$if(fontsize)$
$fontsize$,
$endif$
ignorenonframetext,
$if(handout)$
handout,
$endif$
$if(aspectratio)$
aspectratio=$aspectratio$,
$endif$
$if(babel-lang)$
$babel-lang$,
$endif$
$for(classoption)$
$classoption$$sep$,
$endfor$
]{$documentclass$}
$if(geometry)$
\geometry{$for(geometry)$$geometry$$sep$,$endfor$}
$endif$
\newif\ifbibliography
$if(background-image)$
\usebackgroundtemplate{%
\includegraphics[width=\paperwidth]{$background-image$}%
}
% In beamer background-image does not work well when other images are used, so this is the workaround
\pgfdeclareimage[width=\paperwidth,height=\paperheight]{background}{$background-image$}
\usebackgroundtemplate{\pgfuseimage{background}}
$endif$
\usepackage{pgfpages}
\setbeamertemplate{caption}[numbered]
\setbeamertemplate{caption label separator}{: }
\setbeamercolor{caption name}{fg=normal text.fg}
\beamertemplatenavigationsymbols$if(navigation)$$navigation$$else$empty$endif$
$--
$-- section numbering
$--
$if(numbersections)$
$else$
% remove section numbering
\setbeamertemplate{part page}{
\centering
\begin{beamercolorbox}[sep=16pt,center]{part title}
\usebeamerfont{part title}\insertpart\par
\end{beamercolorbox}
}
\setbeamertemplate{section page}{
\centering
\begin{beamercolorbox}[sep=12pt,center]{section title}
\usebeamerfont{section title}\insertsection\par
\end{beamercolorbox}
}
\setbeamertemplate{subsection page}{
\centering
\begin{beamercolorbox}[sep=8pt,center]{subsection title}
\usebeamerfont{subsection title}\insertsubsection\par
\end{beamercolorbox}
}
$endif$
$for(beameroption)$
\setbeameroption{$beameroption$}
$endfor$
% Prevent slide breaks in the middle of a paragraph
\widowpenalties 1 10000
\raggedbottom
$if(section-titles)$
\AtBeginPart{
\frame{\partpage}
}
\AtBeginSection{
\ifbibliography
\else
\frame{\sectionpage}
\fi
}
\AtBeginSubsection{
\frame{\subsectionpage}
}
$endif$
\usepackage{iftex}
\ifPDFTeX
\usepackage[$if(fontenc)$$fontenc$$else$T1$endif$]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{textcomp} % provide euro and other symbols
\else % if luatex or xetex
$if(mathspec)$
\ifXeTeX
\usepackage{mathspec} % this also loads fontspec
\else
\usepackage{unicode-math} % this also loads fontspec
\fi
$else$
\usepackage{unicode-math} % this also loads fontspec
$endif$
\defaultfontfeatures{Scale=MatchLowercase}$-- must come before Beamer theme
\defaultfontfeatures[\rmfamily]{Ligatures=TeX,Scale=1}
\fi
$if(fontfamily)$
$else$
$-- Set default font before Beamer theme so the theme can override it
\usepackage{lmodern}
$endif$
$-- Set Beamer theme before user font settings so they can override theme
$if(theme)$
\usetheme[$for(themeoptions)$$themeoptions$$sep$,$endfor$]{$theme$}
$endif$
$if(colortheme)$
\usecolortheme[$for(colorthemeoptions)$$colorthemeoptions$$sep$,$endfor$]{$colortheme$}
$endif$
$if(fonttheme)$
\usefonttheme[$for(fontthemeoptions)$$fontthemeoptions$$sep$,$endfor$]{$fonttheme$}
$endif$
$if(mainfont)$
\usefonttheme{serif} % use mainfont rather than sansfont for slide text
$endif$
$if(innertheme)$
\useinnertheme[$for(innerthemeoptions)$$innerthemeoptions$$sep$,$endfor$]{$innertheme$}
$endif$
$if(outertheme)$
\useoutertheme[$for(outerthemeoptions)$$outerthemeoptions$$sep$,$endfor$]{$outertheme$}
$endif$
$-- User font settings (must come after default font and Beamer theme)
$if(fontfamily)$
\usepackage[$for(fontfamilyoptions)$$fontfamilyoptions$$sep$,$endfor$]{$fontfamily$}
$endif$
\ifPDFTeX\else
% xetex/luatex font selection
$if(mainfont)$
$if(mainfontfallback)$
\ifLuaTeX
\usepackage{luaotfload}
\directlua{luaotfload.add_fallback("mainfontfallback",{
$for(mainfontfallback)$"$mainfontfallback$"$sep$,$endfor$
})}
\fi
$endif$
\setmainfont[$for(mainfontoptions)$$mainfontoptions$$sep$,$endfor$$if(mainfontfallback)$,RawFeature={fallback=mainfontfallback}$endif$]{$mainfont$}
$endif$
$if(sansfont)$
$if(sansfontfallback)$
\ifLuaTeX
\usepackage{luaotfload}
\directlua{luaotfload.add_fallback("sansfontfallback",{
$for(sansfontfallback)$"$sansfontfallback$"$sep$,$endfor$
})}
\fi
$endif$
\setsansfont[$for(sansfontoptions)$$sansfontoptions$$sep$,$endfor$$if(sansfontfallback)$,RawFeature={fallback=sansfontfallback}$endif$]{$sansfont$}
$endif$
$if(monofont)$
$if(monofontfallback)$
\ifLuaTeX
\usepackage{luaotfload}
\directlua{luaotfload.add_fallback("monofontfallback",{
$for(monofontfallback)$"$monofontfallback$"$sep$,$endfor$
})}
\fi
$endif$
\setmonofont[$for(monofontoptions)$$monofontoptions$$sep$,$endfor$$if(monofontfallback)$,RawFeature={fallback=monofontfallback}$endif$]{$monofont$}
$endif$
$for(fontfamilies)$
\newfontfamily{$fontfamilies.name$}[$for(fontfamilies.options)$$fontfamilies.options$$sep$,$endfor$]{$fontfamilies.font$}
$endfor$
$if(mathfont)$
$if(mathspec)$
\ifXeTeX
\setmathfont(Digits,Latin,Greek)[$for(mathfontoptions)$$mathfontoptions$$sep$,$endfor$]{$mathfont$}
\else
\setmathfont[$for(mathfontoptions)$$mathfontoptions$$sep$,$endfor$]{$mathfont$}
\fi
$else$
\setmathfont[$for(mathfontoptions)$$mathfontoptions$$sep$,$endfor$]{$mathfont$}
$endif$
$endif$
$if(CJKmainfont)$
\ifXeTeX
\usepackage{xeCJK}
\setCJKmainfont[$for(CJKoptions)$$CJKoptions$$sep$,$endfor$]{$CJKmainfont$}
$if(CJKsansfont)$
\setCJKsansfont[$for(CJKoptions)$$CJKoptions$$sep$,$endfor$]{$CJKsansfont$}
$endif$
$if(CJKmonofont)$
\setCJKmonofont[$for(CJKoptions)$$CJKoptions$$sep$,$endfor$]{$CJKmonofont$}
$endif$
\fi
$endif$
$if(luatexjapresetoptions)$
\ifLuaTeX
\usepackage[$for(luatexjapresetoptions)$$luatexjapresetoptions$$sep$,$endfor$]{luatexja-preset}
\fi
$endif$
$if(CJKmainfont)$
\ifLuaTeX
\usepackage[$for(luatexjafontspecoptions)$$luatexjafontspecoptions$$sep$,$endfor$]{luatexja-fontspec}
\setmainjfont[$for(CJKoptions)$$CJKoptions$$sep$,$endfor$]{$CJKmainfont$}
\fi
$endif$
\fi
$if(zero-width-non-joiner)$
%% Support for zero-width non-joiner characters.
\makeatletter
\def\zerowidthnonjoiner{%
% Prevent ligatures and adjust kerning, but still support hyphenating.
\texorpdfstring{%
\TextOrMath{\nobreak\discretionary{-}{}{\kern.03em}%
\ifvmode\else\nobreak\hskip\z@skip\fi}{}%
}{}%
}
\makeatother
\ifPDFTeX
\DeclareUnicodeCharacter{200C}{\zerowidthnonjoiner}
\else
\catcode`^^^^200c=\active
\protected\def ^^^^200c{\zerowidthnonjoiner}
\fi
%% End of ZWNJ support
$endif$
% Use upquote if available, for straight quotes in verbatim environments
\IfFileExists{upquote.sty}{\usepackage{upquote}}{}
\IfFileExists{microtype.sty}{% use microtype if available
\usepackage[$for(microtypeoptions)$$microtypeoptions$$sep$,$endfor$]{microtype}
\UseMicrotypeSet[protrusion]{basicmath} % disable protrusion for tt fonts
}{}
$if(linestretch)$
\usepackage{setspace}
$else$
% Use setspace anyway because we change the default line spacing.
% The spacing is changed early to affect the titlepage and the TOC.
\usepackage{setspace}
\setstretch{1.2}
$endif$
$--
$-- paragraph formatting
$--
$if(indent)$
$else$
\makeatletter
\@ifundefined{KOMAClassName}{% if non-KOMA class
\IfFileExists{parskip.sty}{%
\usepackage{parskip}
}{% else
\setlength{\parindent}{0pt}
\setlength{\parskip}{6pt plus 2pt minus 1pt}}
}{% if KOMA class
\KOMAoptions{parskip=half}}
\makeatother
$endif$
$if(beamer)$
$else$
$if(block-headings)$
% Make \paragraph and \subparagraph free-standing
\makeatletter
\ifx\paragraph\undefined\else
\let\oldparagraph\paragraph
\renewcommand{\paragraph}{
\@ifstar
\xxxParagraphStar
\xxxParagraphNoStar
}
\newcommand{\xxxParagraphStar}[1]{\oldparagraph*{#1}\mbox{}}
\newcommand{\xxxParagraphNoStar}[1]{\oldparagraph{#1}\mbox{}}
\fi
\ifx\subparagraph\undefined\else
\let\oldsubparagraph\subparagraph
\renewcommand{\subparagraph}{
\@ifstar
\xxxSubParagraphStar
\xxxSubParagraphNoStar
}
\newcommand{\xxxSubParagraphStar}[1]{\oldsubparagraph*{#1}\mbox{}}
\newcommand{\xxxSubParagraphNoStar}[1]{\oldsubparagraph{#1}\mbox{}}
\fi
\makeatother
$endif$
$endif$
$--
$-- verbatim in notes
$--
$if(verbatim-in-note)$
\usepackage{fancyvrb}
$endif$
$-- highlighting
$if(listings)$
\usepackage{listings}
\newcommand{\passthrough}[1]{#1}
\lstset{defaultdialect=[5.3]Lua}
\lstset{defaultdialect=[x86masm]Assembler}
$endif$
$if(listings-no-page-break)$
\usepackage{etoolbox}
\BeforeBeginEnvironment{lstlisting}{\par\noindent\begin{minipage}{\linewidth}}
\AfterEndEnvironment{lstlisting}{\end{minipage}\par\addvspace{\topskip}}
$endif$
$if(lhs)$
\lstnewenvironment{code}{\lstset{language=Haskell,basicstyle=\small\ttfamily}}{}
$endif$
$if(highlighting-macros)$
$highlighting-macros$
% Workaround/bugfix from jannick0.
% See https://github.com/jgm/pandoc/issues/4302#issuecomment-360669013)
% or https://github.com/Wandmalfarbe/pandoc-latex-template/issues/2
%
% Redefine the verbatim environment 'Highlighting' to break long lines (with
% the help of fvextra). Redefinition is necessary because it is unlikely that
% pandoc includes fvextra in the default template.
\usepackage{fvextra}
\DefineVerbatimEnvironment{Highlighting}{Verbatim}{breaklines,fontsize=$if(code-block-font-size)$$code-block-font-size$$else$\small$endif$,commandchars=\\\{\}}
$endif$
$--
$-- tables
$--
$if(tables)$
\usepackage{longtable,booktabs,array}
\newcounter{none} % for unnumbered tables
$if(multirow)$
\usepackage{multirow}
$endif$
\usepackage{calc} % for calculating minipage widths
$if(beamer)$
\usepackage{caption}
% Make caption package work with longtable
\makeatletter
\def\fnum@table{\tablename~\thetable}
\makeatother
$else$
% Correct order of tables after \paragraph or \subparagraph
\usepackage{etoolbox}
\makeatletter
\patchcmd\longtable{\par}{\if@noskipsec\mbox{}\fi\par}{}{}
\makeatother
% Allow footnotes in longtable head/foot
\IfFileExists{footnotehyper.sty}{\usepackage{footnotehyper}}{\usepackage{footnote}}
\makesavenoteenv{longtable}
$endif$
$endif$
$--
$-- graphics
$--
$if(graphics)$
\usepackage{graphicx}
\makeatletter
\newsavebox\pandoc@box
\newcommand*\pandocbounded[1]{% scales image to fit in text height/width
\sbox\pandoc@box{#1}%
\Gscale@div\@tempa{\textheight}{\dimexpr\ht\pandoc@box+\dp\pandoc@box\relax}%
\Gscale@div\@tempb{\linewidth}{\wd\pandoc@box}%
\ifdim\@tempb\p@<\@tempa\p@\let\@tempa\@tempb\fi% select the smaller of both
\ifdim\@tempa\p@<\p@\scalebox{\@tempa}{\usebox\pandoc@box}%
\else\usebox{\pandoc@box}%
\fi%
}
% Set default figure placement to htbp
% Make use of float-package and set default placement for figures to H.
% The option H means 'PUT IT HERE' (as opposed to the standard h option which means 'You may put it here if you like').
\usepackage{float}
\floatplacement{figure}{$if(float-placement-figure)$$float-placement-figure$$else$H$endif$}
\makeatother
$endif$
$if(svg)$
\usepackage{svg}
$endif$
$--
$-- strikeout/underline
$--
$if(strikeout)$
\ifLuaTeX
\usepackage{luacolor}
\usepackage[soul]{lua-ul}
\else
\usepackage{soul}
$if(beamer)$
\makeatletter
\let\HL\hl
\renewcommand\hl{% fix for beamer highlighting
\let\set@color\beamerorig@set@color
\let\reset@color\beamerorig@reset@color
\HL}
\makeatother
$endif$
$if(CJKmainfont)$
\ifXeTeX
% soul's \st doesn't work for CJK:
\usepackage{xeCJKfntef}
\renewcommand{\st}[1]{\sout{#1}}
\fi
$endif$
\fi
$endif$
$--
$-- CSL citations
$--
$if(csl-refs)$
% definitions for citeproc citations
\NewDocumentCommand\citeproctext{}{}
\NewDocumentCommand\citeproc{mm}{%
\begingroup\def\citeproctext{#2}\cite{#1}\endgroup}
\makeatletter
% allow citations to break across lines
\let\@cite@ofmt\@firstofone
% avoid brackets around text for \cite:
\def\@biblabel#1{}
\def\@cite#1#2{{#1\if@tempswa , #2\fi}}
\makeatother
\newlength{\cslhangindent}
\setlength{\cslhangindent}{1.5em}
\newlength{\csllabelwidth}
\setlength{\csllabelwidth}{3em}
\newenvironment{CSLReferences}[2] % #1 hanging-indent, #2 entry-spacing
{\begin{list}{}{%
\setlength{\itemindent}{0pt}
\setlength{\leftmargin}{0pt}
\setlength{\parsep}{0pt}
% turn on hanging indent if param 1 is 1
\ifodd #1
\setlength{\leftmargin}{\cslhangindent}
\setlength{\itemindent}{-1\cslhangindent}
\fi
% set entry spacing
\setlength{\itemsep}{#2\baselineskip}}}
{\end{list}}
\usepackage{calc}
\newcommand{\CSLBlock}[1]{\hfill\break\parbox[t]{\linewidth}{\strut\ignorespaces#1\strut}}
\newcommand{\CSLLeftMargin}[1]{\parbox[t]{\csllabelwidth}{\strut#1\strut}}
\newcommand{\CSLRightInline}[1]{\parbox[t]{\linewidth - \csllabelwidth}{\strut#1\strut}}
\newcommand{\CSLIndent}[1]{\hspace{\cslhangindent}#1}
$endif$
$--
$-- Babel language support
$--
$if(lang)$
\ifLuaTeX
\usepackage[bidi=basic$if(shorthands)$$else$,shorthands=off$endif$$for(babeloptions)$,$babeloptions$$endfor$]{babel}
\else
\usepackage[bidi=default$if(shorthands)$$else$,shorthands=off$endif$$for(babeloptions)$,$babeloptions$$endfor$]{babel}
\fi
$if(babel-lang)$
$if(mainfont)$
\ifPDFTeX
\else
\babelfont{rm}[$for(mainfontoptions)$$mainfontoptions$$sep$,$endfor$$if(mainfontfallback)$,RawFeature={fallback=mainfontfallback}$endif$]{$mainfont$}
\fi
$endif$
$endif$
$for(babelfonts/pairs)$
\babelfont[$babelfonts.key$]{rm}{$babelfonts.value$}
$endfor$
\ifLuaTeX
\usepackage{selnolig} % disable illegal ligatures
\fi
$endif$
$--
$-- pagestyle
$--
$if(pagestyle)$
\pagestyle{$pagestyle$}
$endif$
$--
$-- prevent overfull lines
$--
\setlength{\emergencystretch}{3em} % prevent overfull lines
$--
$-- tight lists
$--
\providecommand{\tightlist}{%
\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
$--
$-- subfigure support
$--
$if(subfigure)$
\usepackage{subcaption}
$endif$
$--
$-- text direction support for pdftex
$--
$if(dir)$
\ifPDFTeX
\TeXXeTstate=1
\newcommand{\RL}[1]{\beginR #1\endR}
\newcommand{\LR}[1]{\beginL #1\endL}
\newenvironment{RTL}{\beginR}{\endR}
\newenvironment{LTR}{\beginL}{\endL}
\fi
\ifluatex
\newcommand{\RL}[1]{\bgroup\textdir TRT#1\egroup}
\newcommand{\LR}[1]{\bgroup\textdir TLT#1\egroup}
\newenvironment{RTL}{\textdir TRT\pardir TRT\bodydir TRT}{}
\newenvironment{LTR}{\textdir TLT\pardir TLT\bodydir TLT}{}
\fi
$endif$
$--
$-- bibliography support support for natbib and biblatex
$--
$if(natbib)$
\usepackage[$natbiboptions$]{natbib}
\bibliographystyle{$if(biblio-style)$$biblio-style$$else$plainnat$endif$}
$endif$
$if(biblatex)$
\usepackage[$if(biblio-style)$style=$biblio-style$,$endif$$for(biblatexoptions)$$biblatexoptions$$sep$,$endfor$]{biblatex}
$for(bibliography)$
\addbibresource{$bibliography$}
$endfor$
$endif$
$--
$-- csquotes
$--
$if(csquotes)$
\usepackage[$for(csquotesoptions)$$csquotesoptions$$sep$,$endfor$]{csquotes}
$endif$
$for(header-includes)$
$header-includes$
$endfor$
\usepackage{bookmark}
\IfFileExists{xurl.sty}{\usepackage{xurl}}{} % add URL line breaks if available
\urlstyle{$if(urlstyle)$$urlstyle$$else$same$endif$}
$if(links-as-notes)$
% Make links footnotes instead of hotlinks:
\DeclareRobustCommand{\href}[2]{#2\footnote{\url{#1}}}
$endif$
$if(verbatim-in-note)$
\VerbatimFootnotes % allow verbatim text in footnotes
$endif$
\definecolor{default-linkcolor}{HTML}{A50000}
\definecolor{default-filecolor}{HTML}{A50000}
\definecolor{default-citecolor}{HTML}{4077C0}
\definecolor{default-urlcolor}{HTML}{4077C0}
\hypersetup{
$if(title-meta)$
pdftitle={$title-meta$},
$endif$
$if(author-meta)$
pdfauthor={$author-meta$},
$endif$
$if(lang)$
pdflang={$lang$},
$endif$
$if(subject)$
pdfsubject={$subject$},
$endif$
$if(keywords)$
pdfkeywords={$for(keywords)$$keywords$$sep$, $endfor$},
$endif$
$if(colorlinks)$
colorlinks=true,
linkcolor={$if(linkcolor)$$linkcolor$$else$default-linkcolor$endif$},
filecolor={$if(filecolor)$$filecolor$$else$default-filecolor$endif$},
citecolor={$if(citecolor)$$citecolor$$else$default-citecolor$endif$},
urlcolor={$if(urlcolor)$$urlcolor$$else$default-urlcolor$endif$},
$else$
$if(boxlinks)$
$else$
hidelinks,
$endif$
$endif$
breaklinks=true,
pdfcreator={LaTeX via pandoc with the Eisvogel template}}
$if(title)$
\title$if(shorttitle)$[$shorttitle$]$endif${\texorpdfstring{$title$}{$title-meta$}$if(thanks)$\thanks{$thanks$}$endif$}
$endif$
$if(subtitle)$
\subtitle$if(shortsubtitle)$[$shortsubtitle$]$endif${\texorpdfstring{$subtitle$}{$subtitle-meta$}}
$endif$
\author$if(shortauthor)$[$shortauthor$]$endif${\texorpdfstring{$for(author)$$author$$sep$ \and $endfor$}{$author-meta$}}
\date$if(shortdate)$[$shortdate$]$endif${$date$}
$if(institute)$
\institute$if(shortinstitute)$[$shortinstitute$]$endif${$for(institute)$$institute$$sep$ \and $endfor$}
$endif$
$if(titlegraphic)$
\titlegraphic{
$for(titlegraphic)$
\includegraphics$if(titlegraphicoptions)$[$for(titlegraphicoptions)$$titlegraphicoptions$$sep$, $endfor$]$endif${$titlegraphic$}$sep$\enspace
$endfor$}
$endif$
$if(logo)$
\logo{\includegraphics{$logo$}}
$endif$
\begin{document}
$if(title)$
\frame{\titlepage}
$if(abstract)$
\begin{abstract}
$abstract$
\end{abstract}
$endif$
$endif$
$for(include-before)$
$include-before$
$endfor$
$if(toc)$
$if(toc-title)$
\renewcommand*\contentsname{$toc-title$}
$endif$
\begin{frame}[allowframebreaks]
$if(toc-title)$
\frametitle{$toc-title$}
$endif$
\setcounter{tocdepth}{$toc-depth$}
\tableofcontents
\end{frame}
$if(toc-own-page)$
\newpage
$endif$
\setcounter{tocdepth}{$toc-depth$}
\tableofcontents
}
$endif$
$if(lof)$
\listoffigures
$endif$
$if(lot)$
\listoftables
$endif$
$if(linestretch)$
\setstretch{$linestretch$}
$endif$
$body$
$if(natbib)$
$if(bibliography)$
$if(biblio-title)$
$if(has-chapters)$
\renewcommand\bibname{$biblio-title$}
$else$
\renewcommand\refname{$biblio-title$}
$endif$
$endif$
\begin{frame}[allowframebreaks]{$biblio-title$}
$if(nocite-ids)$
\nocite{$for(nocite-ids)$$it$$sep$, $endfor$}
$endif$
\bibliographytrue
\bibliography{$for(bibliography)$$bibliography$$sep$,$endfor$}
\end{frame}
$endif$
$endif$
$if(biblatex)$
\begin{frame}[allowframebreaks]{$biblio-title$}
$if(nocite-ids)$
\nocite{$for(nocite-ids)$$it$$sep$, $endfor$}
$endif$
\bibliographytrue
\printbibliography[heading=none]
\end{frame}
$endif$
$for(include-after)$
$include-after$
$endfor$
\end{document}

1065
07_Zettlr/Pandoc/templates/eisvogel.latex Normal file
View File

File diff suppressed because it is too large Load Diff