From: Zenny <garbytrash@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: kaobook tex template integration to a org file to make self-contained, portable?
Date: Tue, 8 Aug 2023 20:39:32 +0200 [thread overview]
Message-ID: <CACuV5sDG_XEDcnYr=FoEd0CRKXLOqESnz8EagyxTfYQ9praieQ@mail.gmail.com> (raw)
In-Reply-To: <CACuV5sBwXZMwy+8Y_DtzhPMCm-um5-dG-kUEKTh=vBx5ASmZFA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 6517 bytes --]
The pdf rendered after appending the org-latex-class looked like the
attachment which appears the three features of kaobook skipping, fyi.
Thanks!
On Tue, Aug 8, 2023 at 8:35 PM Zenny <garbytrash@gmail.com> wrote:
> Hi again,
>
> I updated the texlive to 2023 and can produce a pdf with the following
> snippets inside the https://github.com/asilata/emacsconf2021/ggm.org:
>
> ** Org LaTeX setup
>> #+latex_class: kaobook
>> #+latex_class_options: [openany, a5paper]
>> #+latex_header:
>> \usepackage{amsmath,amssymb,amsthm,geometry,hyperref,paralist,svg,thmtools,tikz,tikz-cd}
>> #+latex_header: \usepackage{mathtools}
>> #+latex_header: \usepackage[capitalise,noabbrev]{cleveref}
>> #+latex_header: \usepackage{environ} \NewEnviron{abmn}{\marginnote{\BODY}}
>> #+latex_header: \setcounter{tocdepth}{1}
>> #+latex_header: \newtheorem{theorem}{Theorem}
>> #+latex_header: \newtheorem{example}[theorem]{Example}
>> #+latex_header: \newtheorem{exmpl}[theorem]{Example}
>> #+latex_header: \newtheorem{definition}[theorem]{Definition}
>> #+latex_header: \newtheorem{proposition}[theorem]{Proposition}
>> #+latex_header: \newtheorem{lemma}[theorem]{Lemma}
>> #+latex_header: \newtheorem{exercise}[theorem]{Exercise}
>> #+latex_header: \usetikzlibrary{arrows,automata,positioning}
>> ** Export settings
>> Export into the artifacts directory
>> #+export_file_name: artifacts/ggm
>>
>> Add ~kaobook~ to ~org-latex-classes~ and update ~org-latex-pdf-process~.
>> #+name: export-setup
>> #+begin_src emacs-lisp :results silent :var this-year="2023"
>> (add-to-list 'org-latex-classes
>> `("kaobook"
>> ,(string-join
>> '("\\documentclass{kaobook}"
>> "\\usepackage{color}"
>> "\\usepackage{amsmath,amssymb}")
>> "\n")
>> ("\\chapter{%s}" . "\\chapter*{%s}")
>> ("\\section{%s}" . "\\section*{%s}")
>> ("\\subsection{%s}" . "\\subsection*{%s}")
>> ("\\paragraph{%s}" . "\\paragraph*{%s}")
>> ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
>>
>
> However, the pdf did not inherit all the kaobook template features like:
>
> 1. Mini table of contents in the margin at the start of each chapter.
> 2. Chapter headings.
> 3. Huge chapter number with a vertical line
>
> Any input will be appreciated to render the file that looks like
> https://github.com/fmarotta/kaobook/blob/master/example_and_documentation.pdf
> or https://github.com/tudelft3d/terrainbook/releases/latest.
>
> Thank you in advance,
> /z
>
> On Mon, Aug 7, 2023 at 1:55 PM Christian Moe <mail@christianmoe.com>
> wrote:
>
>>
>>
>> Hi,
>>
>> For starters, have you added the kaobook document class to the variable
>> org-latex-classes? (If yes, ignore the rest of this message, if not, do
>> so and see what happens.)
>>
>> This is needed to tell Org how to set the document class and what commands
>> are used for sections. See the manual 13.10.2 and 13.10.3,
>> [[info:org#LaTeX specific export settings]] and [[info:org#LaTeX header
>> and sectioning]], and look up the docstring for org-latex-classes if you
>> need help.
>>
>> E.g., in .emacs I have this for Tufte-Latex:
>>
>> (add-to-list 'org-latex-classes
>> '("tufte-handout"
>> "\\documentclass[11pt,a4paper]{tufte-handout}"
>> ("\\section{%s}" . "\\section*{%s}")
>> ("\\subsection{%s}" . "\\subsection*{%s}")))
>>
>> (add-to-list 'org-latex-classes
>> '("tufte-book"
>> "\\documentclass[11pt,a5paper,nols]{tufte-book}"
>> ("\\part{%s}" . "\\part*{%s}")
>> ("\\section{%s}" . "\\section*{%s}")
>> ("\\subsection{%s}" . "\\subsection*{%s}")
>> ("\\paragraph{%s}" . "\\paragraph*{%s}")))
>>
>> Yours,
>> Christian
>>
>>
>> Zenny writes:
>>
>> > Hi,
>> >
>> > References of interest:
>> > 1. https://github.com/fmarotta/kaobook
>> > 2. https://github.com/asilata/emacsconf2021
>> >
>> > Can anyone guide me how to get a self-contained and portable template
>> that
>> > executes kaobook tex templates (see 1) to create an org-file that
>> resembles
>> > with the instance in 2 above?
>> >
>> > I tried the best I can by adding the kaobook.cls and kaobook.sty files
>> > inside `~/texmf/tex/latex/kaobook/` folder and specified 'kaobook' in
>> the
>> > `#+latex_class: kaobook` but it failed to produce the desired look of
>> pdf
>> > similar to
>> >
>> https://github.com/fmarotta/kaobook/blob/master/example_and_documentation.pdf
>> > withing the same examples directory!
>> >
>> > Any input appreciated!
>> >
>> > Cheers and have a nice week,
>> > /z
>>
>>
>
>
>
--
Cheers,
/z
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
CONFIDENTIALITY NOTICE AND DISCLAIMER: Access to this e-mail and its
contents by anyone other than the intended recipient is unauthorized as it
contains privileged and confidential information, and is subject to legal
privilege. Please do not re/distribute it. If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver the email and part of its contents
to anyone this message (or any part of its contents or take any action in
connection to it. In such case, you should destroy this message, and notify
the sender immediately. If you have received this email in error, please
notify the sender or your sysadmin immediately by e-mail or telephone, and
delete the e-mail from any computer. If you or your employer does not
consent to internet e-mail messages of this kind, please notify the sender
immediately. All reasonable precautions have been taken to ensure no
viruses are present in this e-mail and attachments included. As the sender
cannot accept responsibility for any loss or damage arising from the use of
this e-mail or attachments it is recommended that you are responsible to
follow your virus checking procedures prior to use. The views, opinions,
conclusions and other informations expressed in this electronic mail are
not given or endorsed by any company including the network providers unless
otherwise indicated by an authorized representative independent of this
message.
-.. .. ... -.-. .-.. .- .. -- . .-. | -.. .. ... -.-. .-.. .- .. -- . .-.
[-- Attachment #1.2: Type: text/html, Size: 8797 bytes --]
[-- Attachment #2: ggm-A4.pdf --]
[-- Type: application/pdf, Size: 272803 bytes --]
next prev parent reply other threads:[~2023-08-08 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 7:13 kaobook tex template integration to a org file to make self-contained, portable? Zenny
2023-08-07 11:55 ` Christian Moe
2023-08-08 8:12 ` Zenny
2023-08-08 18:35 ` Zenny
2023-08-08 18:39 ` Zenny [this message]
2023-08-08 20:02 ` Thomas S. Dye
2023-08-09 5:33 ` Zenny
2023-08-09 17:21 ` Thomas S. Dye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACuV5sDG_XEDcnYr=FoEd0CRKXLOqESnz8EagyxTfYQ9praieQ@mail.gmail.com' \
--to=garbytrash@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).