Hi Hisao,
KURODA Hisao writes:
> It would be much great if org-mode has upper-compatible notation like:
> #+ORG_VERSION 7
> Then I could use
> #+STYLE
> as well?
If you want to use #+STYLE you should use Org-mode from git and
checkout an older version
~$ cd org-mode/
~$ git checkout re
Hello,
Thank you for the tips!. I appreciate.
On Tue, Jun 10, 2014 at 5:42 PM, Bastien wrote:
>> (2) org-8.2.6 seems to ignore whole #+STYLE: description.
>
> You need to use #+HTML_STYLE
It would be much great if org-mode has upper-compatible notation like:
#+ORG_VERSION 7
Then I could u
Hi Hisao,
KURODA Hisao writes:
> I tried org-8. Now org-html-export-as-html works as you said. Thank you.
> However, still there are serious problems.
>
> (1) Even if I edit the original file with coding-system iso-2022-jp,
> the generated HTML's header says it is UTF-8. Previous version kee
Hi,
Thank you for your answer and sorry for delayed reply.
I tried org-8. Now org-html-export-as-html works as you said. Thank you.
However, still there are serious problems.
(1) Even if I edit the original file with coding-system iso-2022-jp,
the generated HTML's header says it is UTF-8. Pr
Hi Hisao,
KURODA Hisao writes:
> A very simple literal example below seems not work
> with M-x org-export-as-html.
>
>
> #+BEGIN_SRC emacs-lisp
>(save-excursion
> (goto-char (point-min)))
> #+END_SRC
>
>
> The HTML output is class=example not emacs-lisp as follows.
>
> (sa
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
-
