1.3.1 Export Frontend

1.3.2 Export setting

#+OPTIONS: H:1 num:nil author:nil creator:nil timestamp:nil email:nil toc:t \n:nil @:t     ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:nil skip:nil d:t tags:not-in-toc

1. Language

   To set the overall language of a document you can use org-export-default-language or the local directive, e.g., #+LANGUAGE: el for greek. That’s for html export. latex you’ll need a #+latex_attr directive. org-mode has a semi automatic solution for this, the AUTO keyword. So the complete preamble for greek would be

   #+LANGUAGE: el
   #+LATEX_HEADER: \usepackage[AUTO]{babel}
   

   For multilanguage documents in html you have to choose exactly one language for the document. In latex documents the last language option of the package inclusion command is set as default language used at the beginning of the document. See 9.2 The babel user interface of [3]. So the following command should set italian as the default language.

   \usepackage[ngerman,italian]{babel}
   

   Although that’s opposed to Tyler’s strange observation self-commented to his answer of the StackExchange posting Change table of contents title in Org mode according to document language.

   Another hint from this section of the latex Companion is to put the languages into the options bracket of the documentclass. Then other packages can also detect their presence.

   : \documentclass[ngerman,italian]{article}
   : \usepackage{babel}
   : \usepackage{varioref}
   

   Further on in the document you could also accept the approaches of latex‘s babel package to change the current language. This package implements macros to

   • change all language-related settings including translations for strings like Chapter, the typesetting conventions, or the set-up for shorthand commands keep the translations unchanged but modify everything else, e.g., when typesetting short texts in a foreign language within the main text
   • change only the hyphenation rules

   The macros taking care of switching the language or certain aspects of a language are

   • \selectlanguage{language} would switch to a previously declared language symbol, e.g., american. The command calls the macros defined in the language definition file and activates the special definitions for the language in question. It also updates the setting of tex‘s \language primitive used for hyphenation. Usage:

     {\selectlanguage{language} part of document with paragraphs and sections} 
     

     Or as a switch at certain parts of the document.

   • \begin{otherlanguage}{language} same effect as the \selectlanguage{} declaration, except that the language change is local to the environment. Ideal for mixing left-to-right typesetting with right-to-left typesetting.
   • \foreignlanguage{language}{phrase} typesets phrase according to the rules of language. It switches only the extra definitions and the hyphenation rules for the language, not the names and dates.
   • \begin{otherlanguage*}{language} the environment equivalent for \foreignlanguage{}{}.
   • \begin{hyphenrules}{language} starts an environment with hyphenrules of the chosen language, provided that hyphenation rules for the specified language are loaded into the format. As a special application, this environment can be used to prevent hyphenation altogether, if nohyphenation is defined like a language in the corresponding  language.dat file. See 9.5.1 Hyphenating in several languages of [3].

   In html we can’t simulate the switching macro, we’re only able to put some language attributes into tags like <div>, <span>, <p>, <tr>, or <td>. Language dependent strings in html may be realized by dbpedia or linked data, but right now we don’t bother.

   We just want to be able to use another keyboard layout and write it into an appropriate environment. The html language definitions can be found at Language tags in HTML and XML.

1.3.3 Advanced Export Config

1.4.1 Publishing images

ln -s ../Pic img

1.6.1 inline markup

1. words, delimited by whitespacesee manual at 11.2 Emphasis and MonospaceYou can mark words
   • *bold* – never go bold for you have to loose pounds again
   • /italic/ – why is this setting called italic?
   • _underlined_ – underlined gym text,
   • =verbatim= – Created: 2019-01-17 Do 15:22 and, both are HTML’ized to \xmlTag{code},
   • ~code~ – Created: 2019-01-17 Do 15:22, and,
   • +strike-through+ – This is absolutely wrong.

   The decoding of the latex export for these markups is saved in the variable org-latex-text-markup-alist in the org-export-latex group. If I invoke M-x customize-variable org-latex-text-markup-alist a list of latex expressions to convert org’s text markup appears.

   • Key: bold – Value: "\\textbf{%s}"
   • Key: code – Value: protectedtexttt
   • Key: italic – Value: "\\emph{%s}"
   • Key: strike-through – Value: "\\sout{%s}"
   • Key: underline – Value: "\\myuline{%s}"
   • Key: verbatim – Value: protectedtexttt

   The key must be a symbol among ‘bold’, ‘code’, ‘italic’, ‘strike-through’, ‘underline’ and ‘verbatim’. The value is a formatting string to wrap fontified text with.

   Value can also be set to the symbols verb and protectedtexttt. For the former, Org will use \verb to create a format string and select a delimiter character that isn’t in the string. For the latter, Org will use \texttt to typeset and try to protect special characters.

   If no association can be found for a given markup, text will be returned as-is.

   Text in the code and verbatim string is not processed for Org mode specific syntax; it is exported verbatim, i.e., both are html‘ized into a tag.

1.6.2 block markup – environments

1. Literal Examples

   In literal examples, Org interprets strings like (ref:name) as labels, and use them as targets for special hyperlinks like [[(name)]] – i.e., the reference name enclosed in single parenthesis. In html, hovering the mouse over such a link remote-highlights the corresponding code line. Highlighting doesn’t work with the textarea attribute. And it doesn’t work in pdf‘s neither as ref-label functionality nor, of course, as hovering version. The code

   #+NAME: elsip1
   #+attr_latex: :environment lstlisting
   #+BEGIN_SRC emacs-lisp -n
   (save-excursion (label1)
     (goto-char (point-min)) (ref:label2))
   #+END_SRC
   
   In line [[(sc)]] we remember the current position. [[(jump)][Line (jump)]] jumps to point-min.
   

   delivers:

   1: (save-excursion (sc)
   2:   (goto-char (point-min)) (jump)
   

   In line 1 we remember the current position. Line 2 jumps to point-min.

   The labels in the example block have to be named differently, i.e. label1 and label2, because the references sc and jump in the showcase elisp block – preceded by delivers: – would otherwise remote-highlight the label in the example block – preceded by The code. In the You can also see, that #+attr_latex: :environment lstlisting only works for the org example block.

   If you name the literal blocks, the line numbering starts anew with every -n option. And the -r removes the labels from the source code and the display of the literal example

   #+NAME: pitty1
   #+BEGIN_SRC python -n -r
      print "hello" (label3)
      print "bye" (label4)
   #+END_SRC
   
   In line [[(psc)]] we say hello. And in [[(pjump)][line (pjump)]]
   we say kind of goodbye.
   

   is shown, now with a reference to the line numbers, as

   1: print "hello"
   2: print "bye"
   

   In line 1 we say hello. And in line 2 we say kind of goodbye.

   Continuing the code in another block

   11: print "hello, again"
   12: print "bye, again"
   

   In line 11 we say hello, again. And in line 12 we say kind of goodbye, again.

2. LaTeX

   12.10.9 Example blocks in LaTeX export

   This sentence is false.
   

   For adding listings options, see C-h v

   • org-latex-listings [_verbatim_|listings|minted]This package will fontify source code, possibly even with color. If you want to use this, you also need to make LaTeX use the listingspackage, and if you want to have color, the color package. Just add these to ‘org-latex-packages-alist’, for example using customize, or with something like:

     (require 'ox-latex)
     (add-to-list 'org-latex-packages-alist '("" "listings"))
     (add-to-list 'org-latex-packages-alist '("" "color"))
     

     Alternatively,

     (setq org-latex-listings 'minted)
     

     causes source code to be exported using the minted package as opposed to listings. If you want to use minted, you need to add the minted package to ‘org-latex-packages-alist’, for example using customize, or with

     (require 'ox-latex)
     (add-to-list 'org-latex-packages-alist '("newfloat" "minted"))
     

     In addition, it is necessary to install pygments (URL ‘http://pygments.org>’), and to configure the variable ‘org-latex-pdf-process’ so that the -shell-escape option is passed to pdflatex.

     The minted choice has possible repercussions on the preview of latex fragments (see org-preview-latex-fragment). If you run into previewing problems, please consult URL ‘https://orgmode.org/worg/org-tutorials/org-latex-preview.html

   • org-latex-listings-langs – Alist mapping languages to their listing language counterpart. Hide The key is a symbol, the major mode symbol without the “-mode”. The value is the string that should be inserted as the language parameter for the listings package. If the mode name and the listings name are the same, the language does not need an entry in this list – but it does not hurt if it is present.
   • org-latex-listings-optionsAssociation list of options for the latex listings package. HideThese options are supplied as a comma-separated list to the \lstset{} command. Each element of the association list should be a list containing two strings: the name of the option, and the value. For example,

   (setq org-latex-listings-options
      '(("basicstyle" "\\small")
        ("keywordstyle" "\\color{black}\\bfseries\\underbar")))
   

   will typeset the code in a small size font with underlined, bold black keywords.

   Note that the same options will be applied to blocks of all languages. If you need block-specific options, you may use the following syntax:

   #+ATTR_LATEX: :options key1=value1,key2=value2
   #+BEGIN_SRC 
   ...
   #+END_SRC
   

   The option is inserted like

   Org Source, which isn’t org-mode‘d, because I didn’t add an

   appropriate org-babel-execute function for org.

   This sentence is /emphazised/. 
   

3. Advanced Export Configuration

1.7.1 DIY with BibTeX2HTML

1.7.2 ox-bibtex

(require 'ox-bibtex) 
(setq reftex-default-bibliography (list "./bib/file1" "./bib/file2"))

ln -s ./path/to/my/bib/folder bib

kpsewhich -var-value BIBINPUTS

1.7.3 ox-bibtex workflow

aux2bib Tools.aux > Tools1.bib
bib2bib --remove file --remove owner --remove timestamp Tools1.bib > Tools2.bib

1.7.4 RefTeX