From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [patch] Fixes and improvements in org-latex-language-alist (was: ox-latex language handling in Org-9.5 vs 9.6)
Date: Tue, 12 Sep 2023 00:06:20 +0700 [thread overview]
Message-ID: <udnheh$c9o$1@ciao.gmane.io> (raw)
In-Reply-To: <877coy9djg.fsf@localhost>
On 10/09/2023 23:52, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>> On 09/09/2023 16:11, Ihor Radchenko wrote:
>>> I am not sure if making a breaking change to public constant is the best
>>> approach.
>>> What about simply adding an extra entry:
>>> ("de" ....)
>>> ("de-de" <copy of "de" property list>)
>>
>> Ideally it should not be a public constant. Values should be accessed
>> using a helper that returns "de" value for "de-de", "de-ch", "de-it"
>> without copies, unless a more specific key is defined as it is done for
>> de-at.
>
> It is already a public constant. And I see no strong reason to change
> this (strong enough to justify breaking change).
Every piece of code accessing this public constant must implement
fallback from e.g. "de-ch" (or de_CH) to "de". Or to "en" for an
unsupported language. To achieve consistent behavior it is better to
provide a helper function.
>> I have a hope that properties may be generated from CLDR data, LaTeX
>> babel .ini files, etc. However it should be possible to override
>> specific properties.
>
> For context, I plan to provide a global language-identifier alist that
> will link human-readable language names to abbreviations like "de",
> "de-de", etc.
This languange-region identifiers may be written in different way
(dash/underscore, case), but they are used specify POSIX locale LANG,
LC_* and extensions like LANGUAGE, so in some cases human friendly names
may be less convenient.
> Thus, auto-generating the alist may be not reliable. At least some
> manual overseeing may be needed.
Of course, some overrides may be necessary. E.g. it was decided to use
French inner quotes different from CLDR.
> Though I am not sure if we can easily handle tricky
> cases like weird installation directory for TeXLive or MikTeX.
kpsewhich babel-de.ini
/usr/share/texlive/texmf-dist/tex/generic/babel/locale/de/babel-de.ini
next prev parent reply other threads:[~2023-09-11 17:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 14:55 ox-latex language handling in Org-9.5 vs 9.6 Max Nikulin
2023-09-06 22:20 ` Juan Manuel Macías
2023-09-07 10:38 ` Max Nikulin
2023-09-07 11:50 ` Ihor Radchenko
2023-09-07 14:19 ` Juan Manuel Macías
2023-09-07 14:49 ` Max Nikulin
2023-09-08 10:30 ` Max Nikulin
2023-09-08 14:42 ` Juan Manuel Macías
2023-09-08 19:02 ` [patch] Fixes and improvements in org-latex-language-alist (was: ox-latex language handling in Org-9.5 vs 9.6) Juan Manuel Macías
2023-09-09 9:11 ` Ihor Radchenko
2023-09-09 10:36 ` [patch] Fixes and improvements in org-latex-language-alist Juan Manuel Macías
2023-09-09 11:33 ` Ihor Radchenko
2023-09-09 23:59 ` Juan Manuel Macías
2023-09-10 7:55 ` Ihor Radchenko
2023-09-10 11:06 ` Juan Manuel Macías
2023-09-10 13:36 ` Ihor Radchenko
2023-09-10 16:15 ` [patch] Fixes and improvements in org-latex-language-alist (was: ox-latex language handling in Org-9.5 vs 9.6) Max Nikulin
2023-09-10 16:52 ` Ihor Radchenko
2023-09-10 21:15 ` [patch] Fixes and improvements in org-latex-language-alist Juan Manuel Macías
2023-09-11 8:32 ` Ihor Radchenko
2023-09-11 17:06 ` Max Nikulin [this message]
2023-09-12 9:05 ` [patch] Fixes and improvements in org-latex-language-alist (was: ox-latex language handling in Org-9.5 vs 9.6) Ihor Radchenko
2023-09-12 15:22 ` Max Nikulin
2023-09-12 18:12 ` [patch] Fixes and improvements in org-latex-language-alist Juan Manuel Macías
2023-09-15 9:54 ` Ihor Radchenko
2023-09-15 9:51 ` [patch] Fixes and improvements in org-latex-language-alist (was: ox-latex language handling in Org-9.5 vs 9.6) 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='udnheh$c9o$1@ciao.gmane.io' \
--to=manikulin@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).