Re: [Orgmode] Javascript Export Issue
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. sran...@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.r...@emma-stil.de, sebastian_r...@gmx.de 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: [Orgmode] Javascript Export Issue
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: [Orgmode] Javascript Export Issue
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 ___ 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: [Orgmode] Javascript Export Issue
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, sran...@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 ___ 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: [Orgmode] Javascript Export Issue
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 ___ 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
[Orgmode] Re: done-ing a repeating scheduled task now inserts closed timestamp?
Carsten Dominik domi...@science.uva.nl writes: Hi Bernt, Hi :) to me this sounds like a pretty convincing argument *not* to copy entries... I think I agree with that. Another problem is that entries can have IDs, and I would like the ID of such an entry to remain the same, as a link target. I don't currently use ids (as far as I know) so I hadn't thought of that issue. I'm currently comfortable with the way it works now. If some better method comes along I'll try to adapt my workflow. Thanks, Bernt ___ 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: [Orgmode] [PATCH] org-exp-bibtex.el changes
On 05.03 16:44, Chris Gray wrote: Here is a patch that uses the -a switch of bibtex2html to sort the citations as bibtex would. It also changes the invocations of replace-match to set fixedcase and literal to t. This is so that emacs does not try to interpret backslash characters in the bibtex file as it is inserting them. That looks nice. +1 to get it committed. - Taru Karttunen ___ 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
[Orgmode] Worglets without dependencies
For everyone who's interested in fast access to the sources of published online contents (not restricted to, but geard for Org-mode): There is now an elisp version of org-worglet, now called worglet.el, online for testing: http://github.com/SebastianRose/worglet/tree/master I rewrote the stuff in elisp to get rid of external dependencies (zenity, bash scripts...). NEWS: * Only _one_ bookmark and protocol handler required (Firefox/Opera)! The projects are destinguished through base URI. * You can now customize `worglets-alist' to add/remove projects. This is painless, since you never have to adjust protocol handler and bookmarks anymore. * You might even open arbitrary sources of published online content, as long as the relative paths match, online and locally (e.g. open code files while browsing the docs). It's tested in emacs23 and works. I'd appreciate any testing and bug reporting, so we can make it production ready as soon as possible (I found no more bugs here). I'd also be happy if anyone with better elisp skills than me could look through it. Also, I'm shure we could reuse worglet.el to get rid of the shell scripts for org-annotation-helper and org-browser-url too. Best 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 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
[Orgmode] Worg: broken link for tracking habits minitutorial
It looks like the link to his tutorial has been lost with the new addition of the git/bzr tutorial that follows it, on worg. I hope it's still available, as I intend to implement some of the ideas in that document. Alan -- Alan Davis An inviscid theory of flow renders the screw useless, but the need for one non-existent. ---Lord Raleigh (John William Strutt), or else his son, who was also a scientist. It is undesirable to believe a proposition when there is no ground whatsoever for supposing it is true. Bertrand Russell ___ 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: [Orgmode] Javascript Export Issue
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, sran...@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 ___ 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: [Orgmode] org-annotation mode version 0.4
I have installed this new version three times. Using your faq.html was more straightforward. When I tried it by hand, I failed. I have taken the liberty to edit a copy of org-annotation-helper.el in my git repository of org-mode. I have tried to clarify the explanation of how to get this tool running. When I figure out how to make a patch, I will attempt that. Meanwhile, the explanation for Firefox 3 can use some clarifcation, as follows: ;; Step 3: Browser set-up - add the protocol handlers for the ;; remember:// and annotation:// URIs. ;; ;; [Firefox] ;; ;; To add a protocol handler (eg: remember://) in Firefox, take the ;; following steps: ;; ;; * For Firefox 2 and 3, type about:config in the location bar. ;; ;;[What happens in Firefox 2?] ;; ;; * In firefox 3, you will will receive a warning: you will have to ;;click on I'll be careful, I promise! A screen will appear with a ;;list of ;; ;;Right click on the screen anywhere to get the pop-up menu. ;;Select New -- String. ;;A window will appear titled New String Value. ;;You are asked to Enter the preference name. ;;In the field enter network.protocol-handler.app.remember. ;;The window appears again, with a title Enter String Value. ;;A text message says network.protocol-handler.app.remember with a ;;blue diamond to the left with a ? (question mark). ;;Enter as the value, the name of the shell script. In GNU/Linux is ;;unnecessary to include the path. ;; ;; * Lather, rinse, repeat for the annotation protocol. The string to ;;add is, in this case, network.protocol-handler.app.annotation, ;;The value will be the same script name as above, org-annotation-helper. ;; ;; [I am uncertain what the next means. Does this mean you HAVE TO ;; use a file selection protocol to navigate to the script? Does it ;; mean that you can OPTIONALLY edit the about:config list, or that this is ;; the appropriate next action?] ;; ;; | In Firefox 3, when you first click on the button associated with ;; | the bookmarklet, you should get a pop-up asking if you'd like to ;; | associate the bookmarklet with a particular file. Use the ;; | file-select process to navigate to the org-annotation-helper ;; | script and select it. You can still edit the about:config ;; | list directly as in Firefox 2. ;; ;; * the value should be the name of the file containing the shell ;;script, e.g. in Step 1, we called it org-annotation-helper. ;;At least under Linux this does not need to be the full path to ;;the script. ;; ;; ;; You should have two new entries like this: ;; ;; network.protocol-handler.app.annotation user set string path ;; network.protocol-handler.app.remember user set string path ;; ;; where path is the location where org-annotation-helper is ;; for example, in my case it is /home/dmg/bin/org-annotation-helper ;; See http://kb.mozillazine.org/Register_protocol for more details. ;; I don't know the procedure for Firefox 2, but perhaps they should be clearly differentiated, or not at all. I, at least, need the extra clarification, as I stumbled over the instructions every time I have installed org-annotation-helper, version 0.3 and version 0.4. The package you provided as an attachment to the list is far easier to install, and less problematical. I suggest, once again, that in contrib, this entire package would best be included under packages. Thank you for this package. It works. Alan -- Alan Davis An inviscid theory of flow renders the screw useless, but the need for one non-existent. ---Lord Raleigh (John William Strutt), or else his son, who was also a scientist. It is undesirable to believe a proposition when there is no ground whatsoever for supposing it is true. Bertrand Russell ___ 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
[Orgmode] DocBook exporter code (version 1.0)
Hi, I just posted the code for DocBook exporter to Google Code. You can use the following link to get access to the code and example files: http://code.google.com/p/bcui-emacs/source/browse/#svn/trunk/org-docbook Here is the README: # # File: org-docbook/README # # $Id$ # This is the DocBook exporter for Org-mode, a tool written in Emacs Lisp to export text files written in Org-mode to DocBook. This directory contains: README This file. org-export-docbook.el The main part of DocBook exporter code. org-exp.el Slightly modified version of file org-exp.el that is part of Org-mode. Currently this file is synced up with Org-mode 6.24. test.org An Org file used for testing. It includes all the features that current version of DocBook exporter supports. test.xml DocBook XML file exported from test.org. test.pdf PDF file generated from DocBook XML file test.xml. If you have any comments on how to improve this exporter, please send email to cbaoqiu AT yahoo DOT com. You are welcome to try this out, and give me any comments you may have. Bug reports and ideas on how to improve this will be highly appreciated. Thanks, Baoqiu ___ 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
[Orgmode] Re: DocBook exporter for Org-mode
Gour g...@mail.inet.hr writes: Baoqiu == Baoqiu Cui cbao...@yahoo.com writes: Baoqiu I knew it must be FOP that you did not like. ;-) I had similar Baoqiu experience using FOP, and I (and all other team members) had to Baoqiu find workarounds when hitting problems in FOP (like formatting Baoqiu footnotes in lists or tables). Not hard to guess - not many players around. ;) Baoqiu Don't know if you have tried XEP from RenderX. I have not found Baoqiu any problems in XEP. This is commercial app, right? Yes, it is. I do like its PDF output quality. Moreover, I do not believe it produces better output than TeX. You won't see real difference if we are talking about software manuals or documentation etc. Frankly speaking, reST provides a lot of expressive power if you want it, while still keeping document very readable and no DTDs, schemas, validation, fiddling with catalogs etc. :-D Otoh, number of tags in DocBook is overwhelming and, imgo, way too distracting for most documentation tasks, at least, for *my* use-cases. Maybe you should take a look at Simplified DocBook: http://www.docbook.org/schemas/simplified - Baoqiu ___ 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
[Orgmode] Re: DocBook exporter for Org-mode
Dale Smith da...@vxitech.com writes: Sebastian Rose sebastian_r...@gmx.de writes: Gour g...@mail.inet.hr writes: Otoh, number of tags in DocBook is overwhelming and, imgo, way too distracting for most documentation tasks, at least, for *my* use-cases. It is, and that's exactly why the DocBook export is such a great thing. You could say a similar thing about (valid) XHTML, LaTeX, reST - whatever markup you're not familiar with. With the DocBook exporter, learning DocBook is reduced to pressing `C-c C-e' and choose the right option ;-) And that's one of the reasons I would like a docbook exporter. I see myself with two usage patterns. One is where I keep the file in org (or muse) format, and export to docbook and eventually pdf for external consumption. The other is where I use org (or muse) to start the docbook file, and then continue to edit the docbook. This is because docbook is so much richer than any wiki format, and I want to take advantage of what's there. With the DocBook exporter, I can imagine another usage pattern: we can use the powerful list, section, and table editing functionality, quickly edit some paragraphs or sections, export them into DocBook format, and then include them into other big DocBook files. Baoqiu ___ 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
[Orgmode] Re: DocBook exporter for Org-mode
Baoqiu Cui cbao...@yahoo.com writes: Dale Smith da...@vxitech.com writes: Baoqiu Cui cbao...@yahoo.com writes: The only thing that is missing (at least to me) in current Org-mode is the exporter for DocBook format. There is quite a bit of similarity between org and muse formats. I've found that I can edit .muse files in org-mode and stiil publish to docbook. Yes, Muse and Org-mode do have some similarity. While Muse is mainly for publishing, Org-mode focuses on many other things beyond some good publishing functionality. Since Org-mode already has a very good publishing framework in its HTML exporter , it is relatively easy (a small step) to make Org-mode a strong publishing environment too. I have not used Muse in the past 2+ years. Don't know whether it has got much improvement... It's a nice trick to edit .muse files in Org-mode. :-) During the last week (mainly during the last weekend), I wrote some code to export Org files to DocBook V5.0 format, and everything looks very promising (I have to admit that a lot of work still needs to be done to make the code complete and stable) . Looks pretty good to me. I'm ready to ty it out! Thanks. I'll work on the code a little bit more during the weekend and post it to the group. Link to the code: http://code.google.com/p/bcui-emacs/source/browse/#svn/trunk/org-docbook Baoqiu ___ 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: [Orgmode] org-annotation mode version 0.4
Hi Alan, if you find making a patch hard, just send me a modified version. Even better, write a better version of http://orgmode.org/worg/org-contrib/org-annotation-helper.php Do you know how to use worg in order to modify this file? - Carsten On Mar 8, 2009, at 3:41 AM, Alan E. Davis wrote: I have installed this new version three times. Using your faq.html was more straightforward. When I tried it by hand, I failed. I have taken the liberty to edit a copy of org-annotation-helper.el in my git repository of org-mode. I have tried to clarify the explanation of how to get this tool running. When I figure out how to make a patch, I will attempt that. Meanwhile, the explanation for Firefox 3 can use some clarifcation, as follows: ;; Step 3: Browser set-up - add the protocol handlers for the ;; remember:// and annotation:// URIs. ;; ;; [Firefox] ;; ;; To add a protocol handler (eg: remember://) in Firefox, take the ;; following steps: ;; ;; * For Firefox 2 and 3, type about:config in the location bar. ;; ;;[What happens in Firefox 2?] ;; ;; * In firefox 3, you will will receive a warning: you will have to ;;click on I'll be careful, I promise! A screen will appear with a ;;list of ;; ;;Right click on the screen anywhere to get the pop-up menu. ;;Select New -- String. ;;A window will appear titled New String Value. ;;You are asked to Enter the preference name. ;;In the field enter network.protocol-handler.app.remember. ;;The window appears again, with a title Enter String Value. ;;A text message says network.protocol-handler.app.remember with a ;;blue diamond to the left with a ? (question mark). ;;Enter as the value, the name of the shell script. In GNU/ Linux is ;;unnecessary to include the path. ;; ;; * Lather, rinse, repeat for the annotation protocol. The string to ;;add is, in this case, network.protocol-handler.app.annotation, ;;The value will be the same script name as above, org- annotation-helper. ;; ;; [I am uncertain what the next means. Does this mean you HAVE TO ;; use a file selection protocol to navigate to the script? Does it ;; mean that you can OPTIONALLY edit the about:config list, or that this is ;; the appropriate next action?] ;; ;; | In Firefox 3, when you first click on the button associated with ;; | the bookmarklet, you should get a pop-up asking if you'd like to ;; | associate the bookmarklet with a particular file. Use the ;; | file-select process to navigate to the org-annotation-helper ;; | script and select it. You can still edit the about:config ;; | list directly as in Firefox 2. ;; ;; * the value should be the name of the file containing the shell ;;script, e.g. in Step 1, we called it org-annotation-helper. ;;At least under Linux this does not need to be the full path to ;;the script. ;; ;; ;; You should have two new entries like this: ;; ;; network.protocol-handler.app.annotation user set string path ;; network.protocol-handler.app.remember user set string path ;; ;; where path is the location where org-annotation-helper is ;; for example, in my case it is /home/dmg/bin/org-annotation-helper ;; See http://kb.mozillazine.org/Register_protocol for more details. ;; I don't know the procedure for Firefox 2, but perhaps they should be clearly differentiated, or not at all. I, at least, need the extra clarification, as I stumbled over the instructions every time I have installed org-annotation-helper, version 0.3 and version 0.4. The package you provided as an attachment to the list is far easier to install, and less problematical. I suggest, once again, that in contrib, this entire package would best be included under packages. Thank you for this package. It works. Alan -- Alan Davis An inviscid theory of flow renders the screw useless, but the need for one non-existent. ---Lord Raleigh (John William Strutt), or else his son, who was also a scientist. It is undesirable to believe a proposition when there is no ground whatsoever for supposing it is true. Bertrand Russell ___ 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 ___ 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: [Orgmode] DocBook exporter code (version 1.0)
Hi Baoqui, thanks for the link to the code. Forgive me for so far staying quiet on this subject. When you first posted the announcement, I had some mixed feelings. First of all, I don't really know docbook, and I have never used it. Then: One of the really weak features in Org's design is that exporting is not implemented in a generic way. All exporters share a preprocessing step that turns Org format into something a little more sane and consistent. Then each exporter goes its own way. This setup makes maintenance sort of a nightmare, because each change to Org syntax needs to be implemented in all exporters separately. Maybe you have read my swearing when I was trying to fix the LaTeX exporter which I did not understand completely at first - it was written by Bastien. I had really hoped that the next step in exporting Org would be to rewrite the exporter from scratch, in a generic way, that will then make supporting different formatters more stable and easy. Adding a new exporter does not get us closer to that idea. And I had feared that your exporter would be a badly hacked attempt reinventing lots of wheels, that could never become a really complete export. I have misjudged severely, the exporter you made looks quite complete, you have based it very heavily on the XHTML exporter and in this way it seems to be able to handle the entire Org syntax, if I see correctly. So I have now made the changes you require in org-exp.el, and I would like to include the exporter, once you are satisfied, into our contrib directory or even, depending on copyright assignment, into the core. However, I need to make clear that I have no time to maintain another exporter, so I would hope that you would be willing to to the necessary work to keep it up to date and working. Best wishes - Carsten On Mar 8, 2009, at 6:10 AM, Baoqiu Cui wrote: Hi, I just posted the code for DocBook exporter to Google Code. You can use the following link to get access to the code and example files: http://code.google.com/p/bcui-emacs/source/browse/#svn/trunk/org- docbook Here is the README: = = == # # File: org-docbook/README # # $Id$ # This is the DocBook exporter for Org-mode, a tool written in Emacs Lisp to export text files written in Org-mode to DocBook. This directory contains: README This file. org-export-docbook.el The main part of DocBook exporter code. org-exp.el Slightly modified version of file org-exp.el that is part of Org-mode. Currently this file is synced up with Org-mode 6.24. test.org An Org file used for testing. It includes all the features that current version of DocBook exporter supports. test.xml DocBook XML file exported from test.org. test.pdf PDF file generated from DocBook XML file test.xml. If you have any comments on how to improve this exporter, please send email to cbaoqiu AT yahoo DOT com. = = == You are welcome to try this out, and give me any comments you may have. Bug reports and ideas on how to improve this will be highly appreciated. Thanks, Baoqiu ___ 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 ___ 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
