From: Robert Klein <roklein@roklein.de>
To: Adam Aviv <aviv@usna.edu>
Cc: "Emacs-orgmode@gnu.org" <Emacs-orgmode@gnu.org>,
"Charles C. Berry" <ccberry@ucsd.edu>
Subject: Re: #+BEGIN_html/#+END_html tags not exporting literally to html anymore?
Date: Fri, 22 Jul 2016 22:58:09 +0200 [thread overview]
Message-ID: <20160722225809.43c7f3e7@x121e.fritz.box> (raw)
In-Reply-To: <CAJV1Hcy-vKhDZwBMCH4BXAKUpk4zpbPjwp3Jb5U4EvJAWkwakQ@mail.gmail.com>
Hi,
On Fri, 22 Jul 2016 15:33:53 -0400
Adam Aviv <aviv@usna.edu> wrote:
> On Fri, Jul 22, 2016 at 12:38 PM, Charles C. Berry <ccberry@ucsd.edu>
> wrote:
>
> > It is updated. For example, see
> >
> > (info "(org) Special blocks")
> > and
> > (info "(org) results")
> >
> > and in ORG-NEWS.
> >
>
> I see that now, but the online documentation is still out dated:
>
> http://orgmode.org/manual/Quoting-HTML-tags.html
>
> Is there a push cycle to keep the online documents up to date with the
> source documentation? Or is that controlled differently?
The online documentation is for the released version and its
maintenance (i.e. git release `8.3.5' and git branch `maint').
Your org version is from the development branch `master'. It is
documented in the doc/ directory. To create the HTML manual run `gmake
html' in the top directory of the source; for a printable PDF run
`gmake pdf'. The final manual will also be in the doc/ directory.
Best regards
Robert
next prev parent reply other threads:[~2016-07-22 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <03f355f9d8a6478c816a612e156e2772@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-07-22 14:17 ` #+BEGIN_html/#+END_html tags not exporting literally to html anymore? Eric S Fraga
2016-07-22 15:04 ` Adam Aviv
2016-07-22 16:38 ` Charles C. Berry
2016-07-22 19:33 ` Adam Aviv
2016-07-22 20:58 ` Robert Klein [this message]
2016-07-22 21:15 ` Nick Dokos
2016-07-24 15:53 ` Adam Aviv
2016-07-22 13:46 Adam Aviv
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=20160722225809.43c7f3e7@x121e.fritz.box \
--to=roklein@roklein.de \
--cc=Emacs-orgmode@gnu.org \
--cc=aviv@usna.edu \
--cc=ccberry@ucsd.edu \
/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).