unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Ben Phipathananunth" <siraben@disroot.org>
Cc: emacs-devel@gnu.org
Subject: Re: Org Mode Documentation Patch
Date: Fri, 22 Jun 2018 21:14:16 +0300	[thread overview]
Message-ID: <83zhzmpu2v.fsf@gnu.org> (raw)
In-Reply-To: <34982f421aec69d062d32c0c36bbcddf@disroot.org> (siraben@disroot.org)

> Date: Fri, 22 Jun 2018 16:08:35 +0000
> From: "Ben Phipathananunth" <siraben@disroot.org>
> 
> I've begun reading the Org Mode manual, and noticed that the wording
> in some places could be improved (so far I've read up to Section 4.8).
> I've attached my patch.  Some of the more drastic changes:
> 
> - Changed all occurrences of "the cursor" to "point", I thought the
>   inconsistency was confusing, especially since the Emacs manual
>   maintains usage of "point" throughout, so too should the Org Mode
>   manual.
> 
> I have a couple of questions regarding the Org Mode manual and
> submitting patches:
> 
> Section 4.6 "Link abbreviations" in the Org Mode manual link to
> websites that have and/or promote non-free software.  The URLs are
> used to illustrate link abbreviations in Org Mode, but I suppose this
> was purely coincidental because long URLs to websites such as
> gnu.org/some/long/path could be used instead.  Would it be appropriate
> to change the examples in a later patch?
> 
> When the PDF version of the Org Mode manual is generated with "make
> docs", the footnotes (3 and 4) around Section 4.3 are incorrectly
> indented, can anyone reproduce this?  What is causing it?
> 
> Should I submit my patches as smaller ones as I read sections of the
> manual or bulk them together into a larger patch, or is it just a
> matter of preference?

Please submit this to Org developers first, as the manual's master
copy is maintained there.  (I think they are moving towards using Org
format for the manual source anyway, so submitting patches in Texinfo
will not be useful.)

Thanks.



      reply	other threads:[~2018-06-22 18:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 16:08 Org Mode Documentation Patch Ben Phipathananunth
2018-06-22 18:14 ` Eli Zaretskii [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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zhzmpu2v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=siraben@disroot.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.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).