emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [HELP] Translate/extend `org-clock-clocktable-language-setup' for Spanish/Dutch/more languages
Date: Tue, 6 Dec 2022 18:12:54 +0700	[thread overview]
Message-ID: <tmn83n$4kl$1@ciao.gmane.io> (raw)
In-Reply-To: <87pmczif2f.fsf@localhost>

On 04/12/2022 18:27, Ihor Radchenko wrote:
> Max Nikulin writes:
> 
>> For some reason I believed that gettext was available in Emacs.
...
> 
> It would indeed be interesting to have a unified approach to bring
> translations into Emacs. I'd discuss it on emacs-devel.

I found the following thread:

Eli Zaretskii to emacs-devel… Re: Internationalize Emacs's messages 
(swahili) Thu, 24 Dec 2020 16:16:24 +0200. mid:834kkbp9vr.fsf@gnu.org

> They are easy enough to find: search the list archives for "gettext"
> or "l10n", and you will find them.  The last one starts here:
> 
>   https://lists.gnu.org/archive/html/emacs-devel/2019-03/msg00081.html
> 
> A previous one starts here:
> 
>   https://lists.gnu.org/archive/html/emacs-devel/2017-04/msg00750.html

So a translations framework for Emacs is to be implemented. This 
particular thread is concentrated on 2 issues:
- Attempt to not count all elements in list for performance reason. 
Unfortunately `ngettext' would not work for languages having more than 
"" and "s" forms.
- "Fluent" would be better than gettext since it allows arbitrary 
categories, not just numbers, but someone should write its 
implementation in C. This part of discussion is mostly dedicated to the 
question if linking with a Rust library is acceptable.



  reply	other threads:[~2022-12-06 11:14 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27  0:06 [HELP] Translate/extend `org-clock-clocktable-language-setup' for Spanish/Dutch/more languages Ihor Radchenko
2022-11-27  9:02 ` gerard.vermeulen
2022-11-28  5:10   ` Ihor Radchenko
2022-11-28  5:47     ` gerard.vermeulen
2022-12-04 11:14       ` Ihor Radchenko
2022-12-04 11:21         ` Ihor Radchenko
2022-11-27  9:15 ` Esteban Ordóñez
2022-11-28  5:26   ` Ihor Radchenko
2022-11-28 10:21     ` Esteban Ordóñez
2022-12-04 11:17       ` Ihor Radchenko
2022-12-05 13:08         ` Esteban Ordóñez
2022-12-05 13:15           ` Ihor Radchenko
2022-12-05 13:34             ` Esteban Ordóñez
2022-12-05 13:37               ` Esteban Ordóñez
2022-12-05 13:44                 ` Ihor Radchenko
2022-12-05 16:47                   ` Esteban Ordóñez
2022-12-05 13:50             ` Christian Moe
2022-12-05 14:33               ` Esteban Ordóñez
2022-12-05 15:25                 ` Christian Moe
2022-12-05 16:51                   ` Esteban Ordóñez
2022-12-14 13:17       ` [HELP] Things to help Org that do not involve programming Ihor Radchenko
2023-02-03  9:09         ` Kevin Brubeck Unhammer
2023-02-11 11:51           ` Ihor Radchenko
2022-11-28  5:01 ` [HELP] Translate/extend `org-clock-clocktable-language-setup' for Spanish/Dutch/more languages Ihor Radchenko
2022-11-29  0:07 ` Jonathan Gregory
2022-12-04 11:24   ` Ihor Radchenko
2022-12-04 17:44     ` Jonathan Gregory
2022-12-10 13:26       ` Ihor Radchenko
2022-11-30  0:19 ` Rudolf Adamkovič
2022-12-04 11:26   ` Ihor Radchenko
2022-12-12 12:34     ` Ihor Radchenko
2022-12-13 21:35     ` Rudolf Adamkovič
2022-11-30 15:01 ` Max Nikulin
2022-12-04 11:27   ` Ihor Radchenko
2022-12-06 11:12     ` Max Nikulin [this message]
2023-02-03  8:55 ` Kevin Brubeck Unhammer
2023-02-03  9:52   ` Christian Moe
2023-02-03 11:01     ` Kevin Brubeck Unhammer
2023-02-11 11:56   ` Ihor Radchenko
  -- strict thread matches above, loose matches on Subject: below --
2022-12-01  6:44 Pedro Andres Aranda Gutierrez
2022-12-12 12:18 ` Ihor Radchenko
2022-12-12 12:32   ` Pedro Andres Aranda Gutierrez
2023-02-02 11:05   ` Ihor Radchenko
2023-02-04  2:02     ` Esteban Ordóñez

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='tmn83n$4kl$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).