Hi Ilya,
is XHTML not XML enough?
I use the XHTML to extract snippets and their language, tags, sections,
section IDs...
The XHTML export is able to export each and every information an
Org-file can possibly contain. All textual content and links, IDs
... are converted to valid X(HT)ML.
As XH
> Out of curiosity, how would you want to handle textual content? Pass
> it through unchanged with org's wiki-like markup in tact, or somehow
> xml-ified?:
>
> *foo* --> *foo*
> *foo* --> foo
Probably the latter, since converting XMLified content to wiki markup
(or any other form) is easy and does
On Sat, Aug 8, 2009 at 22:25, Ilya Shlyakhter wrote:
>> In the meantime, it would be useful to describe what kind of XML output
>> do you want, because "XML" does not really describe anything per se.
>
> I'm looking for XML output that would closely mirror the logical
> structure of the org file, a
> In the meantime, it would be useful to describe what kind of XML output
> do you want, because "XML" does not really describe anything per se.
I'm looking for XML output that would closely mirror the logical
structure of the org file, and that would contain all the information
in the orgfile (si
Ilya Shlyakhter writes:
> That's great, thanks! I should be able to take it from there.
> It would be great if at some point this became official, and also
> included an XML exporter and specification.
FYI, I'll upload a slightly improved version of org-export.el next week,
together with docume
Ilya Shlyakhter wrote:
>That's great, thanks! I should be able to take it from there.
>It would be great if at some point this became official, and also
>included an XML exporter and specification.
There is some code around for converting between xml and sexp
representations. A few minutes wi
That's great, thanks! I should be able to take it from there.
It would be great if at some point this became official, and also
included an XML exporter and specification.
thanks,
ilya
On Fri, Aug 7, 2009 at 11:13 AM, Andrew Stribblehill wrote:
> [re-adding the mailing list]
>
> No, EXPERIMENTA
[re-adding the mailing list]
No, EXPERIMENTAL/org-export.el. Here's what I did after M-x load-file
/path/to/org-export.el:
(defun org-export-sexp (arg)
(interactive "p")
(let ((bufstr (org-export-parse arg)))
(save-excursion
(switch-to-buffer (get-buffer-create "*Org export*"))
I notice the experimental org-export.el contains an internal representation.
It would probably be very easy for your python to parse the lisp
s-expression it uses, if it were exported.
On Aug 6, 2009 3:55 PM, "Ilya Shlyakhter" wrote:
I'm not an emacs-lisp programmer, but I'd like to write script
I'm not an emacs-lisp programmer, but I'd like to write scripts
(ideally in Python) to generate custom reports from my .org files.
What would help a lot, is if there was a command to export an .org
file to a "native" XML format that would mirror the org file's
structure and all its logical elements
10 matches
Mail list logo
