From: David Rogers <davidandrewrogers@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: minute suggestion for documentation, chapter 12.5 (export to html)
Date: Mon, 16 Sep 2013 10:50:18 -0700 [thread overview]
Message-ID: <87bo3s7j1h.fsf@gmail.com> (raw)
In-Reply-To: <20130916121138.GC2637@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Mon, 16 Sep 2013 14:11:38 +0200")
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> Hello Gijs,
>
> On Mon, Sep 16, 2013 at 01:54:40PM +0200, Gijs Hillenius wrote:
>> I have a really wee suggestion for a change in the documentation that
>> comes with Org-mode version 7.9.3f and in Org 8.1 (on the web)
>>
>> In chapter 12.5 on Html export there is this section
>>
>> ,----
>> | 12.5.9 CSS support
>> |
>> | You can also give style information for the exported file.
>> `----
>>
>> To my non-English eyes the word "also" is ambigous. Earlier this month
>> it made me look all over that chapter for /other/ ways to give style
>> information.
>>
>> I think that "also" refers to "12.5.3 Quoting HTML tags" but I am not
>> sure.
>>
>> So, maybe the above quoted text for 12.5.9 could be improved by writing:
>>
>> Next to including simple HTML tags (see 12.5.3), style information can
>> be added to the exported file.
>
> I think also here suggests style information is optional; as in, you may
> or may not include it.
>
> Maybe others can chime in with their opinion?
I think the "also" is not meant to be about "other ways to give style
information", but about "other things you could do that are not the same
as the immediately-preceding item".
Gijs - would it be clearer, in your opinion, to replace the word "also"
with "optionally"?
--
David R
next prev parent reply other threads:[~2013-09-16 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 11:54 minute suggestion for documentation, chapter 12.5 (export to html) Gijs Hillenius
2013-09-16 12:11 ` Suvayu Ali
2013-09-16 17:50 ` David Rogers [this message]
2013-09-17 5:19 ` Carsten Dominik
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=87bo3s7j1h.fsf@gmail.com \
--to=davidandrewrogers@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.com \
/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).