Closed brittAnderson closed 9 years ago
Hi,
By my understanding, you are generating HTML by converting org-mode file to md, and then to HTML. I am afraid the flow won't work because some structural information may be lost during the conversion.
Is there any problem when using org-reveal to export Org-mode contents to HTML directly?
Regards, Yujie
2015-03-03 21:43 GMT+08:00 brittAnderson notifications@github.com:
Org-reveal is only producing one long slide, it does not break the slides at the proper header and there are no controls. I know that the reveal files are being accessed because the CSS is used to produce the html.
This problem is true for the Readme file as well as my own files. It is also true for a native reveal.js. If I open the introduction to reveal that works fine. If I use pandoc to convert to md, and back to html, and then use reveal the same problem occurs.
I wonder if this could be due to some problem with line break new line characters, but I am not sure how to debug further. Please let me know what tests you might suggest I try.
Thank you.
— Reply to this email directly or view it on GitHub https://github.com/yjwen/org-reveal/issues/99.
No. That was just a test to see if I could identify what was broken.
Here is a test.org file, and the test.html file generated. I never get any slide breaks or controls no matter how I fiddled with the Header level option or other commands. But I can see a proper functioning version if I just open up the index.html that comes with the installation of reveal.js-master
test.org:
Created for UWloo Neuroscience UG Group.
\ This is subheading one
\ and a second
*\ And a third
test.html:
<?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html>
Created for UWloo Neuroscience UG Group.
On 03.03, Yujie Wen wrote:
Hi,
By my understanding, you are generating HTML by converting org-mode file to md, and then to HTML. I am afraid the flow won't work because some structural information may be lost during the conversion.
Is there any problem when using org-reveal to export Org-mode contents to HTML directly?
Regards, Yujie
2015-03-03 21:43 GMT+08:00 brittAnderson notifications@github.com:
Org-reveal is only producing one long slide, it does not break the slides at the proper header and there are no controls. I know that the reveal files are being accessed because the CSS is used to produce the html.
This problem is true for the Readme file as well as my own files. It is also true for a native reveal.js. If I open the introduction to reveal that works fine. If I use pandoc to convert to md, and back to html, and then use reveal the same problem occurs.
I wonder if this could be due to some problem with line break new line characters, but I am not sure how to debug further. Please let me know what tests you might suggest I try.
Thank you.
— Reply to this email directly or view it on GitHub https://github.com/yjwen/org-reveal/issues/99.
— Reply to this email directly or view it on GitHub.*
Britt Anderson, PhD & MD Psychology & Centre Theoretical Neuroscience University of Waterloo CANADA tel: 519.888.4567 x 33056
Hi,
I just tried with the test.org and there are slides for each headings. And there is nothing wrong with the generated HTML that you pasted.
Let me confirm one possible reason. Are you using Firefox or Chrome? IE based browsers don't support HTML5 standard quite well. It is suggested to use Firefox/Chrome to show the slides.
Regards, Yujie
I am using Firefox version 35.0.1. In this browser the index.html that comes with reveal.js opens and displays properly, but the test.html does not. I am not saying the problem is with org-reveal per se, just that I cannot get org-reveal to work on my machine, and am not able to determine the location of the problem. On Tue, 10 Mar 2015 04:51:21 -0400, Yujie Wen wrote:
Hi,
I just tried with the test.org and there are slides for each headings. And there is nothing wrong with the generated HTML that you pasted.
Let me confirm one possible reason. Are you using Firefox or Chrome? IE based browsers don't support HTML5 standard quite well. It is suggested to use Firefox/Chrome to show the slides.
Regards, Yujie
$B!=(B Reply to this email directly or view it on GitHub.*
I saw the reveal.js paths in test.html are relative ones, like:
<link rel="stylesheet" href="./css/reveal.min.css"/> <link rel="stylesheet" href="./css/theme/moon.css" id="theme"/>
Then could you please try to place the test.html into reveal.js's root director (same as index.html that come with the reveal.js release) and open it there.
Please also refer to https://github.com/yjwen/org-reveal/#set-the-location-of-revealjs for details about let org-reveal to know where your reveal.js is.
The problem is that reveal.min.js does not exist. When I manually edit the html file to refer to reveal.js everything works. I see that you refer to this explicitly in ox-reveal.el, but when I download reveal.js-master there is no reveal.min.js file in the js directory. That seems to be the problem.
Maybe it is something weird with my installation, but the fact that the C-c C-e R R command is generating html referring to the missing js file is the problem.
Cheers, Britt
On 10.03, Yujie Wen wrote:
I saw the reveal.js paths in test.html are relative ones, like:
Then could you please try to place the test.html into reveal.js's root director (same as index.html that come with the reveal.js release) and open it there.
Please also refer to https://github.com/yjwen/org-reveal/# set-the-location-of-revealjs for details about let org-reveal to know where your reveal.js is.
— Reply to this email directly or view it on GitHub.*
Britt Anderson, PhD & MD Psychology & Centre Theoretical Neuroscience University of Waterloo CANADA tel: 519.888.4567 x 33056
OK, I see! It is because reveal.js has renamed reveal.min.js to reveal.js recently. Org-reveal has been also updated to follow the file name changes. If your org-reveal is from github, please simply pull the latest. MELPA's ox-reveal should also have been updated, but I am not sure.
Regards, Yujie
Org-reveal is only producing one long slide, it does not break the slides at the proper header and there are no controls. I know that the reveal files are being accessed because the CSS is used to produce the html.
This problem is true for the Readme file as well as my own files. It is also true for a native reveal.js. If I open the introduction to reveal that works fine. If I use pandoc to convert to md, and back to html, and then use reveal the same problem occurs.
I wonder if this could be due to some problem with line break new line characters, but I am not sure how to debug further. Please let me know what tests you might suggest I try.
Thank you.