From: Max Nikulin <manikulin@gmail.com>
To: shosseinib <shosseinib@ut.ac.ir>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] lisp/ox.el: Add Persian/Farsi to org-export
Date: Wed, 9 Mar 2022 19:29:34 +0700 [thread overview]
Message-ID: <8002c375-4789-eee5-92d5-a99b28a60777@gmail.com> (raw)
In-Reply-To: <20220304153034.374103-1-shosseinib@ut.ac.ir>
On 04/03/2022 22:30, shosseinib wrote:
> * Add Persian/Farsi translation to the org-export-dictionary variable at lisp/ox.el.
> - Persian/Farsi is a native language to ~ 110 million speakers around the world (mostly in Iran, Afghanistan, Tajiskistan, Uzbekistan, and Iraq).
> - "fa" abbreviation stands for "farsi" according to [[ISO 639-1][https://en.wikipedia.org/wiki/ISO_639-1]].
Thank you for contributing. Your patch is tracked on
https://updates.orgmode.org/ Some patches are committed before a major
release, so it may take months to complete.
Unfortunately your first message did not get any response:
https://list.orgmode.org/fdfdadd20b2b145c8cf507787cf3ee0c@ut.ac.ir
It seems, nobody on the mail list can independently confirm that the
suggested change has no typos and follows established practice. It seems
quotes are consistent with ones specified in the Common Locale Data
Repository https://cldr.unicode.org/ but it is difficult for me to check
if more strings that might be available there are consistent.
I do not see your name in the list of contributor who have signed the
FSF copyright form, maintainers may have a fresher version of the list.
I am not sure but your patch may exceed the limit for TINYCHANGE, so
some paperwork may be required before it will be possible to accept the
patch. For details see https://orgmode.org/worg/org-contribute.html and
https://www.gnu.org/software/emacs/CONTRIBUTE
prev parent reply other threads:[~2022-03-09 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 15:30 [PATCH] lisp/ox.el: Add Persian/Farsi to org-export shosseinib
2022-03-09 12:29 ` Max Nikulin [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=8002c375-4789-eee5-92d5-a99b28a60777@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=shosseinib@ut.ac.ir \
/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).