Javascript Export Issue

Javascript Export Issue

[srandby]

Greetings,

When I export (using org-mode 6.23) to html an org file that has options 
for org-info.js, the html file contains this:

<script type="text/javascript">
<!--/*--><![CDATA[/*><!--*/
THE SCRIPT
/*]]>*/-->
</script>

Earlier versions of org-mode exported scripts this way:

<script type="text/javascript">
/* <![CDATA[ */
THE SCRIPT
/* ]]> */
</script>

Today, I discovered that the first script listed above will work with 
Firefox, but not with Safari (I don't know about IE). After some 
research, I discovered several fixes, including the old way of 
exporting, the easiest being:

<script type="text/javascript">
<!--
THE SCRIPT
-->
</script>


I realize there are issues here with the differences between html 
browsers and xml browsers, so I've decided that I would like to have 
scripts (and styles) exported as separate files. Is this possible?

When I export my org file to html, the html file contains one style 
section and two script sections. If these three were instead exported to 
separate files, that would eliminate the need to worry about how to 
enclose styles and scripts with comments in a way that works for all 
browsers. Of course, then org-mode would be creating four files instead 
of one, but I would like to have this option. Everything I've read about 
this matter recommends keeping styles and scripts as external files.

When I create the three files manually and edit the html file 
appropriately, the html file lacks all the style and script code which 
is replaced by:

<link rel="stylesheet" type="text/css" href="gen-style.css">
<link rel="stylesheet" type="text/css" href="style.css">
<script type="text/javascript" src="org-info.v.0.1.0.5.js"></script>
<script type="text/javascript" src="org-html.js"></script>
<script type="text/javascript" src="mystery.js"></script>

Here gen-style.css contains the style generated by org-mode, style.css 
is my own style, org-html.js is the first script generated by org-mode, 
and mystery.js is the second script generated by org-mode (it is 
mysterious to me).

Scott Randby

Re: Javascript Export Issue

[Sebastian Rose]

Hi Scott,


True. Safari needs this one here (note the two additional slashes in the
second last line):


<script type="text/javascript">
 <!--/*--><![CDATA[/*><!--*/
 THE SCRIPT
 /*]]>*///-->
</script>


Sorry. I'll search the org sources and compile a patch for this issue.



srandby@gmail.com writes:
> Greetings,
>
> When I export (using org-mode 6.23) to html an org file that has options for
> org-info.js, the html file contains this:
>
> <script type="text/javascript">
> <!--/*--><![CDATA[/*><!--*/
> THE SCRIPT
> /*]]>*/-->
> </script>
>
> Earlier versions of org-mode exported scripts this way:
>
> <script type="text/javascript">
> /* <![CDATA[ */
> THE SCRIPT
> /* ]]> */
> </script>
>
> Today, I discovered that the first script listed above will work with Firefox,
> but not with Safari (I don't know about IE). After some research, I discovered
> several fixes, including the old way of exporting, the easiest being:
>
> <script type="text/javascript">
> <!--
> THE SCRIPT
> -->
> </script>


This is not valid XHTML because of the missing `<![CDATA[' tags. XML
parsers will stop when reading the JavaScript code.




>
> I realize there are issues here with the differences between html browsers and
> xml browsers, so I've decided that I would like to have scripts (and styles)
> exported as separate files. Is this possible?
>
> When I export my org file to html, the html file contains one style section and
> two script sections. If these three were instead exported to separate files,
> that would eliminate the need to worry about how to enclose styles and scripts
> with comments in a way that works for all browsers. Of course, then org-mode
> would be creating four files instead of one, but I would like to have this
> option. Everything I've read about this matter recommends keeping styles and
> scripts as external files.
>
> When I create the three files manually and edit the html file appropriately, the
> html file lacks all the style and script code which is replaced by:
>
> <link rel="stylesheet" type="text/css" href="gen-style.css">
> <link rel="stylesheet" type="text/css" href="style.css">
> <script type="text/javascript" src="org-info.v.0.1.0.5.js"></script>
> <script type="text/javascript" src="org-html.js"></script>
> <script type="text/javascript" src="mystery.js"></script>


Good idea.
But this should be valid XHTML too:

<link rel="stylesheet" type="text/css" href="gen-style.css" />
<link rel="stylesheet" type="text/css" href="style.css" />


Regards,


-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
Http:  www.emma-stil.de

Re: Javascript Export Issue

[Sebastian Rose]

[-- Attachment #1: Type: text/plain, Size: 39 bytes --]


Here's the patch to fix this issue.



[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Make JavaScript work in Safari --]
[-- Type: text/x-diff, Size: 857 bytes --]

diff --git a/lisp/org-exp.el b/lisp/org-exp.el
index c21755a..952eb9a 100644
--- a/lisp/org-exp.el
+++ b/lisp/org-exp.el
@@ -563,7 +563,7 @@ not be modified."
    if(elem.cacheClassTarget)
      target.className = elem.cacheClassTarget;
  }
-/*]]>*/-->
+/*]]>*///-->
 </script>"
 "Basic javascript that is needed by HTML files produced by Org-mode.")
 
diff --git a/lisp/org-jsinfo.el b/lisp/org-jsinfo.el
index 285169b..b24f65b 100644
--- a/lisp/org-jsinfo.el
+++ b/lisp/org-jsinfo.el
@@ -110,7 +110,7 @@ means to use the maximum value consistent with other options."
 <!--/*--><![CDATA[/*><!--*/
 %MANAGER_OPTIONS
 org_html_manager.setup();  // activate after the parameters are set
-/*]]>*/-->
+/*]]>*///-->
 </script>"
   "The template for the export style additions when org-info.js is used.
 Option settings will replace the %MANAGER-OPTIONS cookie."

[-- Attachment #3: Type: text/plain, Size: 197 bytes --]


-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Http:  www.emma-stil.de

[-- Attachment #4: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Javascript Export Issue

[Carsten Dominik]

Hi Sebastian,

I take it this will continue to work on other browsers?

- Carsten

On Mar 7, 2009, at 11:23 AM, Sebastian Rose wrote:

>
> Here's the patch to fix this issue.
>
>
> diff --git a/lisp/org-exp.el b/lisp/org-exp.el
> index c21755a..952eb9a 100644
> --- a/lisp/org-exp.el
> +++ b/lisp/org-exp.el
> @@ -563,7 +563,7 @@ not be modified."
>    if(elem.cacheClassTarget)
>      target.className = elem.cacheClassTarget;
>  }
> -/*]]>*/-->
> +/*]]>*///-->
> </script>"
> "Basic javascript that is needed by HTML files produced by Org-mode.")
>
> diff --git a/lisp/org-jsinfo.el b/lisp/org-jsinfo.el
> index 285169b..b24f65b 100644
> --- a/lisp/org-jsinfo.el
> +++ b/lisp/org-jsinfo.el
> @@ -110,7 +110,7 @@ means to use the maximum value consistent with  
> other options."
> <!--/*--><![CDATA[/*><!--*/
> %MANAGER_OPTIONS
> org_html_manager.setup();  // activate after the parameters are set
> -/*]]>*/-->
> +/*]]>*///-->
> </script>"
>   "The template for the export style additions when org-info.js is  
> used.
> Option settings will replace the %MANAGER-OPTIONS cookie."
>
> -- 
> Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449  
> Hannover
> Tel.:  +49 (0)511 - 36 58 472
> Fax:   +49 (0)1805 - 233633 - 11044
> mobil: +49 (0)173 - 83 93 417
> Http:  www.emma-stil.de
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Javascript Export Issue

[Carsten Dominik]

[-- Attachment #1.1: Type: text/plain, Size: 3447 bytes --]

Hi Scott,

I do not think it makes sense to automatically produce these files.
Among other things, it would mean that the extra files are
produces for every single export of a file.
If you want external files, You likely will use the
same for a set of pages.

After pulling the latest version you can do this:

1. prepare any style files and script files you want to use

2. do this

(setq org-export-html-style-include-default nil)
(setq org-export-html-style-include-scripts nil)
(setq org-export-html-style
    "<link rel="stylesheet" type="text/css" href="gen-style.css">
     <link rel="stylesheet" type="text/css" href="style.css">
     <script type="text/javascript" src="org-info.v.0.1.0.5.js"></ 
script>
     <script type="text/javascript" src="org-html.js"></script>
     <script type="text/javascript" src="mystery.js"></script>")


Instead of the last setting, you can also use #+STYLE in a file
to specify the style files for this particular page.

HTH

- Carsten


>


On Mar 7, 2009, at 3:30 AM, srandby@gmail.com wrote:

> Greetings,
>
> When I export (using org-mode 6.23) to html an org file that has  
> options for org-info.js, the html file contains this:
>
> <script type="text/javascript">
> <!--/*--><![CDATA[/*><!--*/
> THE SCRIPT
> /*]]>*/-->
> </script>
>
> Earlier versions of org-mode exported scripts this way:
>
> <script type="text/javascript">
> /* <![CDATA[ */
> THE SCRIPT
> /* ]]> */
> </script>
>
> Today, I discovered that the first script listed above will work  
> with Firefox, but not with Safari (I don't know about IE). After  
> some research, I discovered several fixes, including the old way of  
> exporting, the easiest being:
>
> <script type="text/javascript">
> <!--
> THE SCRIPT
> -->
> </script>
>
>
> I realize there are issues here with the differences between html  
> browsers and xml browsers, so I've decided that I would like to have  
> scripts (and styles) exported as separate files. Is this possible?
>
> When I export my org file to html, the html file contains one style  
> section and two script sections. If these three were instead  
> exported to separate files, that would eliminate the need to worry  
> about how to enclose styles and scripts with comments in a way that  
> works for all browsers. Of course, then org-mode would be creating  
> four files instead of one, but I would like to have this option.  
> Everything I've read about this matter recommends keeping styles and  
> scripts as external files.
>
> When I create the three files manually and edit the html file  
> appropriately, the html file lacks all the style and script code  
> which is replaced by:
>
> <link rel="stylesheet" type="text/css" href="gen-style.css">
> <link rel="stylesheet" type="text/css" href="style.css">
> <script type="text/javascript" src="org-info.v.0.1.0.5.js"></script>
> <script type="text/javascript" src="org-html.js"></script>
> <script type="text/javascript" src="mystery.js"></script>
>
> Here gen-style.css contains the style generated by org-mode,  
> style.css is my own style, org-html.js is the first script generated  
> by org-mode, and mystery.js is the second script generated by org- 
> mode (it is mysterious to me).
>
> Scott Randby
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[-- Attachment #1.2: Type: text/html, Size: 4360 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Javascript Export Issue

[Carsten Dominik]

Applied, thanks.

- Carsten

On Mar 7, 2009, at 11:23 AM, Sebastian Rose wrote:

>
> Here's the patch to fix this issue.
>
>
> diff --git a/lisp/org-exp.el b/lisp/org-exp.el
> index c21755a..952eb9a 100644
> --- a/lisp/org-exp.el
> +++ b/lisp/org-exp.el
> @@ -563,7 +563,7 @@ not be modified."
>    if(elem.cacheClassTarget)
>      target.className = elem.cacheClassTarget;
>  }
> -/*]]>*/-->
> +/*]]>*///-->
> </script>"
> "Basic javascript that is needed by HTML files produced by Org-mode.")
>
> diff --git a/lisp/org-jsinfo.el b/lisp/org-jsinfo.el
> index 285169b..b24f65b 100644
> --- a/lisp/org-jsinfo.el
> +++ b/lisp/org-jsinfo.el
> @@ -110,7 +110,7 @@ means to use the maximum value consistent with  
> other options."
> <!--/*--><![CDATA[/*><!--*/
> %MANAGER_OPTIONS
> org_html_manager.setup();  // activate after the parameters are set
> -/*]]>*/-->
> +/*]]>*///-->
> </script>"
>   "The template for the export style additions when org-info.js is  
> used.
> Option settings will replace the %MANAGER-OPTIONS cookie."
>
> -- 
> Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449  
> Hannover
> Tel.:  +49 (0)511 - 36 58 472
> Fax:   +49 (0)1805 - 233633 - 11044
> mobil: +49 (0)173 - 83 93 417
> Http:  www.emma-stil.de
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Javascript Export Issue

[srandby]

Carsten Dominik wrote:
> Hi Scott,
> 
> I do not think it makes sense to automatically produce these files.
> Among other things, it would mean that the extra files are
> produces for every single export of a file.

Yes, I agree, but I still would like to be able to do it. Perhaps, when 
I eventually learn lisp, I'll work on a way to implement this.

> If you want external files, You likely will use the
> same for a set of pages.
> 
> After pulling the latest version you can do this:
> 
> 1. prepare any style files and script files you want to use
> 
> 2. do this
> 
> (setq org-export-html-style-include-default nil)
> (setq org-export-html-style-include-scripts nil)
> (setq org-export-html-style
>    "<link rel="stylesheet" type="text/css" href="gen-style.css">
>     <link rel="stylesheet" type="text/css" href="style.css">
>     <script type="text/javascript" src="org-info.v.0.1.0.5.js"></script>
>     <script type="text/javascript" src="org-html.js"></script>
>     <script type="text/javascript" src="mystery.js"></script>")
> 
> 
> Instead of the last setting, you can also use #+STYLE in a file
> to specify the style files for this particular page.

Thanks, this helps a lot.

> 
> HTH
> 
> - Carsten
> 
> 
>>
> 
> 
> On Mar 7, 2009, at 3:30 AM, srandby@gmail.com wrote:
> 
>> Greetings,
>>
>> When I export (using org-mode 6.23) to html an org file that has 
>> options for org-info.js, the html file contains this:
>>
>> <script type="text/javascript">
>> <!--/*--><![CDATA[/*><!--*/
>> THE SCRIPT
>> /*]]>*/-->
>> </script>
>>
>> Earlier versions of org-mode exported scripts this way:
>>
>> <script type="text/javascript">
>> /* <![CDATA[ */
>> THE SCRIPT
>> /* ]]> */
>> </script>
>>
>> Today, I discovered that the first script listed above will work with 
>> Firefox, but not with Safari (I don't know about IE). After some 
>> research, I discovered several fixes, including the old way of 
>> exporting, the easiest being:
>>
>> <script type="text/javascript">
>> <!--
>> THE SCRIPT
>> -->
>> </script>
>>
>>
>> I realize there are issues here with the differences between html 
>> browsers and xml browsers, so I've decided that I would like to have 
>> scripts (and styles) exported as separate files. Is this possible?
>>
>> When I export my org file to html, the html file contains one style 
>> section and two script sections. If these three were instead exported 
>> to separate files, that would eliminate the need to worry about how to 
>> enclose styles and scripts with comments in a way that works for all 
>> browsers. Of course, then org-mode would be creating four files 
>> instead of one, but I would like to have this option. Everything I've 
>> read about this matter recommends keeping styles and scripts as 
>> external files.
>>
>> When I create the three files manually and edit the html file 
>> appropriately, the html file lacks all the style and script code which 
>> is replaced by:
>>
>> <link rel="stylesheet" type="text/css" href="gen-style.css">
>> <link rel="stylesheet" type="text/css" href="style.css">
>> <script type="text/javascript" src="org-info.v.0.1.0.5.js"></script>
>> <script type="text/javascript" src="org-html.js"></script>
>> <script type="text/javascript" src="mystery.js"></script>
>>
>> Here gen-style.css contains the style generated by org-mode, style.css 
>> is my own style, org-html.js is the first script generated by 
>> org-mode, and mystery.js is the second script generated by org-mode 
>> (it is mysterious to me).
>>
>> Scott Randby
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> 
>