From: Sebastian Rose <sebastian_rose@gmx.de>
To: srandby@gmail.com
Cc: "[Orgmode]" <emacs-orgmode@gnu.org>
Subject: Re: Javascript Export Issue
Date: Sat, 07 Mar 2009 11:14:02 +0100 [thread overview]
Message-ID: <871vt97i8l.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <49B1DC36.1020505@gmail.com> (srandby@gmail.com's message of "Fri, 06 Mar 2009 21:30:14 -0500")
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
next prev parent reply other threads:[~2009-03-07 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 2:30 Javascript Export Issue srandby
2009-03-07 10:14 ` Sebastian Rose [this message]
2009-03-07 10:23 ` Sebastian Rose
2009-03-07 10:28 ` Carsten Dominik
2009-03-07 10:32 ` Carsten Dominik
2009-03-07 10:30 ` Carsten Dominik
2009-03-08 2:20 ` srandby
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=871vt97i8l.fsf@kassiopeya.MSHEIMNETZ \
--to=sebastian_rose@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=srandby@gmail.com \
/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).