emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: emacs@supporter.mailer.me
Cc: emacs-orgmode@gnu.org
Subject: Re: Help me contribute to org
Date: Fri, 08 Sep 2023 07:54:41 +0000	[thread overview]
Message-ID: <87il8l2j7i.fsf@localhost> (raw)
In-Reply-To: <b2499cacca259eb19d0233a847c01a24@supporter.mailer.me>

emacs@supporter.mailer.me writes:

> I would like to contribute to org-mode but I have no experience with git. I would like to start with something small - adding translations for my language.
>
> Could somebody please guide?

The easiest way would be:

1. Download Org mode source code from command line:

   git clone https://git.savannah.gnu.org/cgit/emacs/org-mode.git

   This will create "org-mode" folder in the place you run the above
   command.

2. Open one of the Org files in the downloaded folder.
   For example org-mode/lisp/ox.el has `org-export-dictionary' variable
   - you can search for the variable in the file simply using isearch:
     C-s org-export-dictionary

3. Edit the file as needed, adding translations. You simply can follow
   by example when adding new translations.

4. M-x vc-diff <RET>
   This will open a buffer with you edits converted into "diff".

5. C-x C-w in the diff buffer and save it to a file like
   "my-edits.diff".

6. Drop an email to this mailing list, explaining what you did and
   attaching the "diff" file.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
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>


  reply	other threads:[~2023-09-08  7:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 14:14 Help me contribute to org emacs
2023-09-08  7:54 ` Ihor Radchenko [this message]
2023-09-09 11:51   ` emacs
2023-09-10  8:09     ` Ihor Radchenko
     [not found]       ` <dbd0996e126b1e9fc4fcfececf8f8ac2@supporter.mailer.me>
2023-09-15  9:05         ` Ihor Radchenko
2023-10-13 14:47           ` Ihor Radchenko
     [not found]             ` <0d1626ff0caf376decdf1d84c5b94a5a@supporter.mailer.me>
     [not found]               ` <87il70t8oi.fsf@localhost>
     [not found]                 ` <e0e3d6e683fd423cccee43e26a67b26f@supporter.mailer.me>
2023-10-22 10:02                   ` Ihor Radchenko
     [not found]                     ` <12228b72ebfdff31f62203521b6710ed@supporter.mailer.me>
     [not found]                       ` <87jzreaah0.fsf@localhost>
     [not found]                         ` <371a138218d2cef580ddc57cc16de26c@supporter.mailer.me>
     [not found]                           ` <87h6mg73ju.fsf@localhost>
     [not found]                             ` <391d3354599a7da733fbe8fd458f7366@supporter.mailer.me>
2023-10-25 10:41                               ` 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=87il8l2j7i.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=emacs@supporter.mailer.me \
    /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).