From: Ihor Radchenko <[email protected]> To: Pedro Andres Aranda Gutierrez <[email protected]> Cc: Org Mode List <[email protected]> Subject: Re: Status of the all-tex-fonts feature branch Date: Sun, 29 Jun 2025 08:21:47 +0000 [thread overview] Message-ID: <87ldpb2c10.fsf@localhost> (raw) In-Reply-To: <CAO48Bk9GjRGO=gBa2HRszeSx4RjGc9-jVdHWHMMoSO4k9SMeQg@mail.gmail.com> Pedro Andres Aranda Gutierrez <[email protected]> writes: > I'd like to go on a step-by-step review instead of getting all > comments in one email (if that is possible). Sure. I will start from reviewing changes to the manual. > -Org file. See the docstring for the > -~org-latex-default-packages-alist~ for loading packages with certain > -compilers. Also see ~org-latex-bibtex-compiler~ to set the > -bibliography compiler[fn:48]. > +Org file. In conjunction with the ~org-latex-multi-lang-driver~ > +variable or the ~#+LATEX_MULTI_LANG~ keyword below, it controls the > +package to support multiple languages and/or scripts in your document. > +See the docstring for the ~org-latex-default-packages-alist~ for > +loading packages with certain compilers. Also see > +~org-latex-bibtex-compiler~ to set the bibliography compiler[fn:48]. This paragraph becomes loaded enough that we may want to split it into multiple, I think. > In order to be effective, the =babel= or =polyglossia= > packages---according to the LaTeX compiler used---must be loaded I think that this statement is no longer strictly accurate. With LATEX_MULTI_LANG, babel/polyglossia may be loaded automatically. I suggest merging description of LANGUAGE and LATEX_MULTI_LANG into one record, similar to =LATEX_HEADER=, =LATEX_HEADER_EXTRA=. Also, since we now allow multiple languages to be listed in #+LANGUAGE, we may need to update the manual when talking about #+LANGUAGE keyword in other places as well; not just in latex export section. > The LaTeX package handling multi-lingual features. Possible values > + are ~"polyglossia"~, ~"babel"~, ~t~ or ~nil~. When it is ~t~, the > + new font control features are activated. When it is either Please avoid word "new" and other relative time references in the manual. > +The LaTeX export backend can handle multiple languages with the LateX > +packages =babel= or =polyglossia=. It will use the =LANGUAGE= keyword, > +if present in the document or the value of > +~org-export-default-language~ to determine the languages used in a > +document. If this value is a comma-separated list of languages, it > +will assume the first one to be the main language in the list. > ... I suggest making this into a dedicated section. > The LaTeX templates in =org= may include the =[FONTSPEC]= keyword, > which acts as a placeholder for font specification code. By default, > Org mode places the font specification code at the beginning of the > generated LaTeX output. When referring to Org mode, use "Org mode", not =org= :) > # This feature is currently supported for LuaLaTeX and XeLaTex. > # (c.f. [[#lualatex-fontspec][below]]). An empty string will be > # generated for PDFLaTeX. This comment is unnecessary, right? > #+BEGIN_SRC elisp :results output :exports both > ("math" :font "TeX Gyre Termes Math") > #+END_SRC I suggest providing example snippets that can be copy-pasted directly. It will make life easier for the users. > #+BEGIN_SRC latex > \directlua{ > luaotfload.add_fallback ("fallback_main",{ > "Noto Color Emoji:mode=harf", > }) > } > #+END_SRC What will happen in XeLaTeX? > *Notes* I think you can drop "notes" > - You may use any font name used in the ~\set..font{}~ command by the > ~fontspec~ package. For example, when using XeLaTeX, you can > compose Chinese, Japanese or Korean test using the ~xeCJK~ and > ~xpinyin~ packages. These packages define the ~\\setCKJmainfont{}~, > ~\\setCJKsansfont{}~ and ~\\setCJKmonofnt{}~ commands. Use the > ~CJKmain~, ~CJKsans~ and ~CJK mono~ definitions in your documents to > customise them: > If you need more features, add then to this list. *them > # TODO: Subsection with the font configuration specific to > # polyglossia. This is done already, right? So, should be removed. > The properties you can define are: > > 1. =:font=: a string with the system font name. This property is *mandatory*. > 2. =:variant=: a string for the font variant (e.g. "=sf=", "=tt=", etc.). May we give a brief description of when these variants mean? For people unfamiliar with font intricacies. > 3. =:tag=: a string that will used to define the language name in the > font family. For example, the language may be ="hindi"= but the > name for the font family ="devanagari"=. In this case, the latter > can be indicated with a =:tag=, Should this be an Org language name? We should refer to the list of available names somewhere in the manual. > 4. =:props=: a string for extra properties. The square bracket are not > needed, because they are added by Org. We should probably refer again to some polyglossia manual here, to direct users to other available properties. > +[fn:49] Emacs will look up the whole directory tree until your =$HOME= > +directory and load the first directory local variable definition file > +it finds. You can, for example, set a common definition for all your > +documents in your =Documents= directory and then create a specific > +file for projects that deviate from it. Rather than repeating Emacs manual, just refer to it via info: link. There are examples how to do it in the Org manual. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2025-06-29 8:24 UTC|newest]
Thread overview: 208+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 5:46 Status of the all-tex-fonts feature branch Pedro Andres Aranda Gutierrez
2025-06-29 8:21 ` Ihor Radchenko [this message]
2025-06-29 8:51 ` Pedro Andres Aranda Gutierrez
2025-06-29 16:59 ` Pedro Andres Aranda Gutierrez
2025-06-29 18:02 ` Ihor Radchenko
2025-06-30 6:41 ` Pedro Andres Aranda Gutierrez
2025-06-30 10:35 ` Pedro Andres Aranda Gutierrez
2025-06-30 17:32 ` Ihor Radchenko
2025-07-01 5:28 ` Pedro Andres Aranda Gutierrez
2025-07-02 16:03 ` Pedro Andres Aranda Gutierrez
2025-07-04 7:44 ` Pedro Andres Aranda Gutierrez
2025-07-06 17:35 ` Ihor Radchenko
2025-07-07 7:55 ` Pedro Andres Aranda Gutierrez
2025-07-07 16:26 ` Ihor Radchenko
2025-07-06 17:11 ` Ihor Radchenko
2025-06-30 17:50 ` Ihor Radchenko
2025-07-01 5:20 ` Pedro Andres Aranda Gutierrez
2025-07-06 17:15 ` Ihor Radchenko
2025-07-15 17:22 ` Ihor Radchenko
2025-07-16 6:08 ` Pedro Andres Aranda Gutierrez
2025-07-16 7:41 ` Pedro Andres Aranda Gutierrez
2025-07-17 10:57 ` Max Nikulin
2025-07-17 15:18 ` Pedro Andres Aranda Gutierrez
2025-07-19 14:11 ` Ihor Radchenko
2025-07-17 15:23 ` Pedro Andres Aranda Gutierrez
2025-07-17 15:39 ` Pedro Andres Aranda Gutierrez
2025-07-17 15:59 ` Pedro Andres Aranda Gutierrez
2025-07-19 14:27 ` Ihor Radchenko
2025-07-19 15:37 ` Pedro Andres Aranda Gutierrez
2025-07-19 15:44 ` Ihor Radchenko
2025-07-19 15:45 ` Ihor Radchenko
2025-07-22 8:11 ` Pedro Andres Aranda Gutierrez
2025-07-27 13:02 ` Ihor Radchenko
2025-07-28 5:50 ` Pedro Andres Aranda Gutierrez
2025-07-28 7:00 ` Pedro Andres Aranda Gutierrez
2025-07-28 17:48 ` Ihor Radchenko
2025-07-29 5:17 ` Pedro Andres Aranda Gutierrez
2025-07-30 7:05 ` Pedro Andres Aranda Gutierrez
2025-07-30 7:07 ` Ihor Radchenko
2025-09-27 11:28 ` Ihor Radchenko
2025-09-27 18:49 ` Pedro Andres Aranda Gutierrez
2025-09-28 5:15 ` Pedro Andres Aranda Gutierrez
2025-09-28 12:59 ` Ihor Radchenko
2025-09-29 5:32 ` Pedro Andres Aranda Gutierrez
2025-09-29 6:36 ` Pedro Andres Aranda Gutierrez
2025-09-29 8:54 ` Pedro Andres Aranda Gutierrez
2025-09-29 9:49 ` Ihor Radchenko
2025-09-30 6:19 ` Pedro Andres Aranda Gutierrez
2025-10-03 18:12 ` Ihor Radchenko
2025-10-04 5:39 ` Pedro Andres Aranda Gutierrez
2025-10-04 6:43 ` Ihor Radchenko
2025-10-04 8:19 ` Pedro Andres Aranda Gutierrez
2025-10-04 8:53 ` Ihor Radchenko
2025-10-04 10:13 ` Pedro Andres Aranda Gutierrez
2025-10-04 10:45 ` Pedro Andres Aranda Gutierrez
2025-10-04 12:20 ` Ihor Radchenko
2025-10-04 14:36 ` Pedro Andres Aranda Gutierrez
2025-10-04 18:01 ` Ihor Radchenko
2025-10-05 5:17 ` Pedro Andres Aranda Gutierrez
2025-10-05 9:39 ` Ihor Radchenko
2025-10-05 15:15 ` Pedro Andres Aranda Gutierrez
2025-10-05 18:48 ` Ihor Radchenko
2025-10-06 6:12 ` Pedro Andres Aranda Gutierrez
2025-10-06 15:25 ` Ihor Radchenko
2025-10-06 16:09 ` Pedro Andres Aranda Gutierrez
2025-10-06 17:06 ` Ihor Radchenko
2025-10-07 5:32 ` Pedro Andres Aranda Gutierrez
2025-10-07 16:58 ` Ihor Radchenko
2025-10-08 6:13 ` Pedro Andres Aranda Gutierrez
2025-10-11 11:50 ` Ihor Radchenko
2025-10-11 17:12 ` Pedro Andres Aranda Gutierrez
2025-10-12 7:10 ` Pedro A. Aranda
2025-10-12 8:56 ` Ihor Radchenko
2025-10-12 8:57 ` Ihor Radchenko
2025-10-12 9:14 ` Ihor Radchenko
[not found] ` <CAO48Bk9hxtk_n+AwgyuF+YxO3nMf94EjBa=JVfY8G6s3pgk1zQ@mail.gmail.com>
2025-10-12 11:01 ` Ihor Radchenko
2025-10-12 15:40 ` Pedro Andres Aranda Gutierrez
2025-10-12 17:08 ` Pedro Andres Aranda Gutierrez
2025-10-12 18:55 ` Ihor Radchenko
2025-10-13 5:36 ` Pedro Andres Aranda Gutierrez
2025-10-16 17:23 ` Ihor Radchenko
2025-10-17 6:25 ` Pedro Andres Aranda Gutierrez
2025-10-17 16:53 ` Ihor Radchenko
2025-10-18 8:30 ` Pedro Andres Aranda Gutierrez
2025-10-18 9:29 ` Ihor Radchenko
2025-10-18 16:50 ` Pedro Andres Aranda Gutierrez
2025-10-18 17:25 ` Ihor Radchenko
2025-10-18 19:03 ` Pedro Andres Aranda Gutierrez
2025-10-19 8:28 ` Ihor Radchenko
2025-10-19 8:43 ` Pedro Andres Aranda Gutierrez
2025-10-19 6:27 ` Pedro Andres Aranda Gutierrez
2025-10-19 8:25 ` Ihor Radchenko
2025-10-21 17:57 ` Ihor Radchenko
2025-10-22 5:48 ` Pedro A. Aranda
2025-10-22 16:55 ` Ihor Radchenko
[not found] ` <[email protected]>
2025-10-23 15:22 ` Fwd: " Pedro Andres Aranda Gutierrez
2025-10-23 17:16 ` Ihor Radchenko
2025-10-24 6:07 ` Pedro Andres Aranda Gutierrez
2025-10-24 18:27 ` Ihor Radchenko
2025-10-25 6:09 ` Pedro Andres Aranda Gutierrez
2025-10-25 10:13 ` Ihor Radchenko
2025-10-25 10:55 ` Pedro Andres Aranda Gutierrez
2025-10-25 12:14 ` Ihor Radchenko
2025-10-25 14:27 ` Pedro Andres Aranda Gutierrez
2025-10-25 15:10 ` Ihor Radchenko
2025-10-30 6:31 ` Pedro Andres Aranda Gutierrez
2025-11-01 13:23 ` Ihor Radchenko
2025-11-02 7:44 ` Pedro A. Aranda
2025-11-02 11:27 ` Ihor Radchenko
[not found] ` <[email protected]>
[not found] ` <87346unccd.fsf@localhost>
2025-11-07 17:27 ` Pedro Andres Aranda Gutierrez
2025-11-07 18:51 ` Ihor Radchenko
2025-11-08 7:12 ` Pedro Andres Aranda Gutierrez
2025-11-08 10:10 ` Ihor Radchenko
2025-11-08 16:32 ` Pedro Andres Aranda Gutierrez
2025-11-08 20:37 ` Ihor Radchenko
2025-11-09 7:15 ` Pedro Andres Aranda Gutierrez
[not found] ` <CAO48Bk-YH_9cjjeDogH57SFf4WmOC4CaiRv4zVpTYZ=Y+mUgAQ@mail.gmail.com>
2025-11-09 10:58 ` Fwd: " Huang Jing
2025-11-09 12:21 ` Ihor Radchenko
2025-11-09 13:34 ` Huang Jing
2025-11-10 18:14 ` Ihor Radchenko
2025-11-11 13:35 ` RadioNoiseE
2025-11-11 14:05 ` Pedro Andres Aranda Gutierrez
2025-11-11 15:01 ` RadioNoiseE
2025-11-11 15:35 ` Pedro Andres Aranda Gutierrez
2025-11-14 10:07 ` Fwd: " Pedro A. Aranda
2025-11-15 10:35 ` Ihor Radchenko
2025-11-15 11:46 ` Pedro Andres Aranda Gutierrez
2025-11-17 2:03 ` RadioNoiseE
[not found] ` <CAO48Bk_ua3JQYM0bjHrmE1b7gyymAwPTT4d7HX0YYCOv0KB6pw@mail.gmail.com>
2025-11-17 7:22 ` Fwd: " Pedro Andres Aranda Gutierrez
2025-11-18 17:52 ` Pedro Andres Aranda Gutierrez
2025-11-19 20:14 ` Ihor Radchenko
2025-11-20 5:50 ` Pedro Andres Aranda Gutierrez
2025-11-20 6:25 ` Ihor Radchenko
2025-11-20 6:34 ` Pedro Andres Aranda Gutierrez
2025-11-20 20:22 ` Ihor Radchenko
2025-11-21 6:12 ` Pedro Andres Aranda Gutierrez
2025-11-21 8:05 ` Ihor Radchenko
2025-11-21 8:43 ` Pedro Andres Aranda Gutierrez
2025-11-21 13:45 ` Ihor Radchenko
2025-11-21 15:59 ` Pedro Andres Aranda Gutierrez
2025-11-21 16:56 ` Pedro Andres Aranda Gutierrez
2025-11-21 17:08 ` Pedro Andres Aranda Gutierrez
2025-11-21 18:31 ` Ihor Radchenko
2025-11-22 6:46 ` Pedro Andres Aranda Gutierrez
2025-11-22 9:16 ` Ihor Radchenko
2025-11-22 12:06 ` Pedro Andres Aranda Gutierrez
2025-11-22 13:12 ` Ihor Radchenko
2025-11-22 15:58 ` Pedro Andres Aranda Gutierrez
2025-11-22 16:20 ` Ihor Radchenko
2025-11-22 16:26 ` Pedro Andres Aranda Gutierrez
2025-11-23 3:23 ` Max Nikulin
2025-11-23 5:52 ` Pedro Andres Aranda Gutierrez
2025-11-23 7:52 ` Max Nikulin
2025-11-23 8:44 ` Pedro Andres Aranda Gutierrez
2025-11-23 9:30 ` Ihor Radchenko
2025-11-23 9:58 ` Pedro Andres Aranda Gutierrez
2025-11-23 10:07 ` Ihor Radchenko
2025-11-22 16:20 ` Pedro Andres Aranda Gutierrez
2025-11-23 7:36 ` Pedro Andres Aranda Gutierrez
2025-11-23 9:20 ` Ihor Radchenko
2025-11-23 9:46 ` Pedro Andres Aranda Gutierrez
2025-11-23 11:10 ` Ihor Radchenko
2025-11-24 9:34 ` Pedro Andres Aranda Gutierrez
2025-11-24 17:57 ` Ihor Radchenko
2025-11-24 19:31 ` Pedro Andres Aranda Gutierrez
2025-11-24 19:36 ` Ihor Radchenko
2025-11-24 19:37 ` Pedro Andres Aranda Gutierrez
2025-11-24 19:40 ` Ihor Radchenko
2025-11-24 19:44 ` Ihor Radchenko
2025-11-25 6:02 ` Pedro Andres Aranda Gutierrez
2025-11-25 6:56 ` Pedro Andres Aranda Gutierrez
2025-11-25 20:01 ` Ihor Radchenko
2025-11-26 7:02 ` Pedro Andres Aranda Gutierrez
2025-11-26 7:46 ` Pedro Andres Aranda Gutierrez
2025-11-29 14:18 ` Ihor Radchenko
2025-11-29 18:52 ` Pedro Andres Aranda Gutierrez
2025-11-30 10:57 ` Ihor Radchenko
2025-11-30 11:47 ` Pedro Andres Aranda Gutierrez
2025-11-30 12:55 ` Ihor Radchenko
2025-11-30 16:43 ` Pedro Andres Aranda Gutierrez
2025-11-30 18:06 ` Ihor Radchenko
2025-11-30 19:42 ` Pedro Andres Aranda Gutierrez
2025-12-01 18:04 ` Pedro Andres Aranda Gutierrez
2025-12-01 20:26 ` Ihor Radchenko
2025-11-29 14:11 ` Ihor Radchenko
2025-11-23 7:29 ` Pedro Andres Aranda Gutierrez
2025-11-23 7:36 ` Ihor Radchenko
2025-11-23 7:40 ` Pedro Andres Aranda Gutierrez
2025-11-23 9:22 ` Ihor Radchenko
2025-11-15 6:48 ` Fwd: " Pedro Andres Aranda Gutierrez
2025-11-15 18:33 ` Ihor Radchenko
2025-11-16 6:13 ` Pedro Andres Aranda Gutierrez
2025-11-17 2:16 ` RadioNoiseE
[not found] ` <CAO48Bk_0K+EGtbk08xHUJ0C7oksuH5JoFnyS4GBQxFUPBfvzPg@mail.gmail.com>
2025-11-17 7:21 ` Pedro Andres Aranda Gutierrez
2025-11-17 7:22 ` Fwd: " Pedro Andres Aranda Gutierrez
2025-11-17 2:07 ` RadioNoiseE
2025-11-09 11:15 ` Ihor Radchenko
2025-11-09 16:38 ` Pedro Andres Aranda Gutierrez
2025-11-10 18:30 ` Ihor Radchenko
2025-11-11 6:19 ` Pedro Andres Aranda Gutierrez
2025-11-11 12:43 ` Ihor Radchenko
2025-11-11 13:40 ` Pedro Andres Aranda Gutierrez
2025-11-15 10:32 ` Ihor Radchenko
2025-11-15 11:41 ` Pedro Andres Aranda Gutierrez
2025-11-12 7:00 ` Pedro Andres Aranda Gutierrez
2025-11-15 6:13 ` Max Nikulin
2025-11-15 6:53 ` Pedro Andres Aranda Gutierrez
2025-09-27 11:30 ` Ihor Radchenko
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=87ldpb2c10.fsf@localhost \
[email protected] \
[email protected] \
[email protected] \
/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.
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).