From: Jean-Christophe Helary <lists@traduction-libre.org>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: export dispatch → change the default "Contents" string
Date: Sat, 2 Oct 2021 01:45:03 +0900 [thread overview]
Message-ID: <DA09E452-1506-46A4-B7C8-0440B34BA98F@traduction-libre.org> (raw)
In-Reply-To: <87mtns3dow.fsf@posteo.net>
Thank you Juan.
It does not seem to work as I expected, but that's OK, I just removed the ToC.
Jean-Christophe
> On Oct 2, 2021, at 1:35, Juan Manuel Macías <maciaschain@posteo.net> wrote:
>
> Hi, jean-Christophe,
>
> Jean-Christophe Helary writes:
>
>> What is the parameter to change the default "Contents" ToC string when exporting to PDF ?
>
> If I'm not wrong, I think there is no native Org way to change the
> default string for LaTeX literals. But if you use babel (the LaTeX
> package), you can add this command:
>
> #+LaTeX_Header: \addto{\captionsenglish}{\renewcommand\contentsname{foo}}
>
> That's the old way of doing it, and it still works. The latest Babel
> versions also incorporate this other variant:
>
> \setlocalecaption{language-name}{caption-name}{string}
>
> for example:
>
> \setlocalecaption{english}{contents}{Table of Contents}
>
> NB: I strongly recommend using babel always for LaTeX, in any of its
> flavors (pdfLaTeX, XeLaTeX, LuaLaTeX), instead of polyglossia, which is
> a very buggy package. This package came up when babel didn't support
> XeTeX and LuaTeX, years ago, but now it doesn't sense to use it.
>
> Best regards,
>
> Juan Manuel
>
>
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
prev parent reply other threads:[~2021-10-01 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 15:59 export dispatch → change the default "Contents" string Jean-Christophe Helary
2021-10-01 16:35 ` Juan Manuel Macías
2021-10-01 16:45 ` Jean-Christophe Helary [this message]
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=DA09E452-1506-46A4-B7C8-0440B34BA98F@traduction-libre.org \
--to=lists@traduction-libre.org \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
/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).