Re: [O] #+BEGIN_html/#+END_html tags not exporting literally to html anymore?

[Adam Aviv]

Thanks for the comments... very helpful! This is a perfect example of when
living on the bleeding edge of a library and searching for solutions can
come into conflict. I'll stick to looking at the docs built off the git
repo.

On Fri, Jul 22, 2016 at 5:15 PM, Nick Dokos  wrote:

> Adam Aviv  writes:
>
> > On Fri, Jul 22, 2016 at 12:38 PM, Charles C. Berry 
> 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?
> >
>
> That's because the online docs are for the stable version (the version
> you get from the maint branch of the git repo).
>
> If you are using latest (i.e. the master branch of the git repo), then
> you have to build and use the docs that come with it:
>
>   make info
>
> I do
>
> --8<---cut here---start->8---
>
> INFOPATH=$HOME/src/emacs/org/org-mode/doc:/usr/local/share/info:/usr/share/info
> export INFOPATH
> --8<---cut here---end--->8---
>
> in my login shell initialization file to make sure that I pick the
> version I built over any other versions installed on my system.
> There are other ways to do that - and even for this one, you will
> have to modify the paths appropriately.
>
> --
> Nick
>
>
>


-- 
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655 <%28410%29%20293-%206655>*

Re: [O] #+BEGIN_html/#+END_html tags not exporting literally to html anymore?

[Eric S Fraga]

On Friday, 22 Jul 2016 at 13:46, Adam Aviv wrote:
> I just did an update to my org install, and when I recompiled my
> notes, I noticed that I was not getting literal exporting for things
> between a #+BEGIN_HTML and #+END_HTML tag, however #+HTML: prefix
> still exports properly.
>
> Am I to assume that
>
> #+BEGIN_HTML
> #+END_HTML
>
>
> will be completely replaced now with
>
> #+BEGIN_EXPORT html
> #+END_HTML

Yes with #+end_export of course.

> If so, is there a way to make compilation backwards compatible. I have
> a lot of old org files that would be a pain to update.  Further, all
> the documentation on the org site is also out of date.

a simple regex replace (or two I guess) will fix all in a file?

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.94.1, Org release_8.3.4-1049-g481709

Re: [O] #+BEGIN_html/#+END_html tags not exporting literally to html anymore?

[Nick Dokos]

Adam Aviv  writes:

> On Fri, Jul 22, 2016 at 12:38 PM, Charles C. Berry  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?
>

That's because the online docs are for the stable version (the version
you get from the maint branch of the git repo).

If you are using latest (i.e. the master branch of the git repo), then
you have to build and use the docs that come with it:

  make info

I do

--8<---cut here---start->8---
INFOPATH=$HOME/src/emacs/org/org-mode/doc:/usr/local/share/info:/usr/share/info
export INFOPATH
--8<---cut here---end--->8---

in my login shell initialization file to make sure that I pick the
version I built over any other versions installed on my system.
There are other ways to do that - and even for this one, you will
have to modify the paths appropriately.

-- 
Nick

Re: [O] #+BEGIN_html/#+END_html tags not exporting literally to html anymore?

[Robert Klein]

Hi,
On Fri, 22 Jul 2016 15:33:53 -0400
Adam Aviv  wrote:

> On Fri, Jul 22, 2016 at 12:38 PM, Charles C. Berry 
> 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

Re: [O] #+BEGIN_html/#+END_html tags not exporting literally to html anymore?

[Adam Aviv]

On Fri, Jul 22, 2016 at 12:38 PM, Charles C. Berry  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?


-- 
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655*

Re: [O] #+BEGIN_html/#+END_html tags not exporting literally to html anymore?

[Charles C. Berry]

On Fri, 22 Jul 2016, Adam Aviv wrote:


On Fri, Jul 22, 2016 at 10:17 AM, Eric S Fraga  wrote:




If so, is there a way to make compilation backwards compatible. I have
a lot of old org files that would be a pain to update.  Further, all
the documentation on the org site is also out of date.


a simple regex replace (or two I guess) will fix all in a file?




Better still `org-repair-export-blocks' will fix them.

It can be found in the

: *** New syntax for export blocks

section of ORG-NEWS.



Yes, I agree --- but that's a burden on long time users even if it is a
simple sed script.

I just wonder why the #+BEGIN_HTML was removed in the first place? What
harm was it doing?


As the ORG-NEWS section above notes, it fixes some parsing issues.

And, why was this change made without updating the documentation to 
reflect it?




It is updated. For example, see

(info "(org) Special blocks")
and
(info "(org) results")

and in ORG-NEWS.

Chuck

Re: [O] #+BEGIN_html/#+END_html tags not exporting literally to html anymore?

[Adam Aviv]

On Fri, Jul 22, 2016 at 10:17 AM, Eric S Fraga  wrote:

>
> > If so, is there a way to make compilation backwards compatible. I have
> > a lot of old org files that would be a pain to update.  Further, all
> > the documentation on the org site is also out of date.
>
> a simple regex replace (or two I guess) will fix all in a file?


Yes, I agree --- but that's a burden on long time users even if it is a
simple sed script.

I just wonder why the #+BEGIN_HTML was removed in the first place? What
harm was it doing? And, why was this change made without updating the
documentation to reflect it?




-- 
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655*

[O] #+BEGIN_html/#+END_html tags not exporting literally to html anymore?

[Adam Aviv]

I just did an update to my org install, and when I recompiled my notes, I
noticed that I was not getting literal exporting for things between a
#+BEGIN_HTML and #+END_HTML tag, however #+HTML: prefix still exports
properly.

Am I to assume that

#+BEGIN_HTML
#+END_HTML

will be completely replaced now with

#+BEGIN_EXPORT html
#+END_HTML

If so, is there a way to make compilation backwards compatible. I have a
lot of old org files that would be a pain to update.  Further, all the
documentation on the org site is also out of date.



-- 
Adam J. Aviv, PhD
*Asst. Professor*
*Computer Science*
*U.S. Naval Academy*
*(410) 293- 6655*