export to html

export to html

[Cecil Westerhof]

I understood that a table can be exported to HTML. I can not find how to
do this. How do I do this?

-- 
Cecil Westerhof <CecilWesterhof@xs4all.nl>

Re: export to html

[Carsten Dominik]

On Jun 16, 2007, at 8:14, Cecil Westerhof wrote:

> I understood that a table can be exported to HTML. I can not find how 
> to
> do this. How do I do this?

http://staff.science.uva.nl/~dominik/Tools/org/org.html#Exporting


- Carsten

Export to html

[Thomas S. Dye]

Aloha all,

On the bus this morning I was able to find out a bit more about  
problems with html export.

Using Bernt's minimal.emacs and exporting to html with C-c C-e H, git  
bisect says:

459d99c44c7df4cd09d82fa54c53e5d5eec47a4e is the first bad commit
commit 459d99c44c7df4cd09d82fa54c53e5d5eec47a4e
Author: Tom Breton (Tehom) <tehom@panix.com>
Date:   Mon May 17 18:17:38 2010 -0400

     Moved to new branch

Prior to this commit file links are exported like this:

<a href="index.pdf">file:index.pdf</a>

After the commit, file links are exported like this:

<a href="file:index.pdf">index.pdf</a>

I was a bit surprised at the git bisect result because I understood  
Tom Breton (Tehom) to be working on a testing framework, rather than  
html export.  So, I ran through git bisect a second time and got  
identical results.

I hope I've understood the procedure correctly and that this  
information is useful.  At this point, I'm in way over my head and  
won't be able to do more without specific instructions.

I'm currently using commit d56d417bc214088114e10c959ce78bee2d26635d on  
the master branch to make my exporting and publishing setup work as  
expected.

All the best,
Tom

Re: Export to html

[Nick Dokos]

Thomas S. Dye <tsd@tsdye.com> wrote:

> Aloha all,
> 
> On the bus this morning I was able to find out a bit more about
> problems with html export.
> 
> Using Bernt's minimal.emacs and exporting to html with C-c C-e H, git
> bisect says:
> 
> 459d99c44c7df4cd09d82fa54c53e5d5eec47a4e is the first bad commit
> commit 459d99c44c7df4cd09d82fa54c53e5d5eec47a4e
> Author: Tom Breton (Tehom) <tehom@panix.com>
> Date:   Mon May 17 18:17:38 2010 -0400
> 
>     Moved to new branch
> 
> Prior to this commit file links are exported like this:
> 
> <a href="index.pdf">file:index.pdf</a>
> 
> After the commit, file links are exported like this:
> 
> <a href="file:index.pdf">index.pdf</a>
> 
> I was a bit surprised at the git bisect result because I understood
> Tom Breton (Tehom) to be working on a testing framework, rather than
> html export.  So, I ran through git bisect a second time and got
> identical results.
> 
> I hope I've understood the procedure correctly and that this
> information is useful.  At this point, I'm in way over my head and
> won't be able to do more without specific instructions.
> 
> I'm currently using commit d56d417bc214088114e10c959ce78bee2d26635d on
> the master branch to make my exporting and publishing setup work as
> expected.
> 

Tom,

I can't reproduce the busted link. With more-or-less-current Org-mode
(version 6.36trans (release_6.36.102.g67b5)), the link looks like this:

    <a href="foo.pdf">foo.pdf</a>

Reverting the commit you identified (the revert was not clean: I had to
resolve a merge conflict by hand - a dicey proposition, particularly in
this situation where I have no idea what the patch is trying to do)
gives me:

    <a href="foo.pdf">file:foo.pdf</a>

That's with your minimal.emacs for the other problem you've identified
(changed to produce html of course). So it looks like the patch cleaned
up the link name in this case.

Nick

PS. I also looked at the commit: I gave up on figuring it out in any
reasonable time, but I must say the commit comment is no help.

Re: Export to html

[Thomas S. Dye]

Thanks Nick,

Sebastian Rose thinks this is fixed now.  I haven't had time to pull  
the latest org-mode, but hope to do so soon.

Apologies if my adventure with git bisect led you into dicey territory.

As always, I appreciate the benefit of your experience.

All the best,
Tom

On May 27, 2010, at 11:30 AM, Nick Dokos wrote:

> Thomas S. Dye <tsd@tsdye.com> wrote:
>
>> Aloha all,
>>
>> On the bus this morning I was able to find out a bit more about
>> problems with html export.
>>
>> Using Bernt's minimal.emacs and exporting to html with C-c C-e H, git
>> bisect says:
>>
>> 459d99c44c7df4cd09d82fa54c53e5d5eec47a4e is the first bad commit
>> commit 459d99c44c7df4cd09d82fa54c53e5d5eec47a4e
>> Author: Tom Breton (Tehom) <tehom@panix.com>
>> Date:   Mon May 17 18:17:38 2010 -0400
>>
>>    Moved to new branch
>>
>> Prior to this commit file links are exported like this:
>>
>> <a href="index.pdf">file:index.pdf</a>
>>
>> After the commit, file links are exported like this:
>>
>> <a href="file:index.pdf">index.pdf</a>
>>
>> I was a bit surprised at the git bisect result because I understood
>> Tom Breton (Tehom) to be working on a testing framework, rather than
>> html export.  So, I ran through git bisect a second time and got
>> identical results.
>>
>> I hope I've understood the procedure correctly and that this
>> information is useful.  At this point, I'm in way over my head and
>> won't be able to do more without specific instructions.
>>
>> I'm currently using commit d56d417bc214088114e10c959ce78bee2d26635d  
>> on
>> the master branch to make my exporting and publishing setup work as
>> expected.
>>
>
> Tom,
>
> I can't reproduce the busted link. With more-or-less-current Org-mode
> (version 6.36trans (release_6.36.102.g67b5)), the link looks like  
> this:
>
>    <a href="foo.pdf">foo.pdf</a>
>
> Reverting the commit you identified (the revert was not clean: I had  
> to
> resolve a merge conflict by hand - a dicey proposition, particularly  
> in
> this situation where I have no idea what the patch is trying to do)
> gives me:
>
>    <a href="foo.pdf">file:foo.pdf</a>
>
> That's with your minimal.emacs for the other problem you've identified
> (changed to produce html of course). So it looks like the patch  
> cleaned
> up the link name in this case.
>
> Nick
>
> PS. I also looked at the commit: I gave up on figuring it out in any
> reasonable time, but I must say the commit comment is no help.
>

Re: Export to html

[Sebastian Rose]

Nick Dokos <nicholas.dokos@hp.com> writes:
> Thomas S. Dye <tsd@tsdye.com> wrote:
>
>> Aloha all,
>> 
>> On the bus this morning I was able to find out a bit more about
>> problems with html export.
>> 
>> Using Bernt's minimal.emacs and exporting to html with C-c C-e H, git
>> bisect says:
>> 
>> 459d99c44c7df4cd09d82fa54c53e5d5eec47a4e is the first bad commit
>> commit 459d99c44c7df4cd09d82fa54c53e5d5eec47a4e
>> Author: Tom Breton (Tehom) <tehom@panix.com>
>> Date:   Mon May 17 18:17:38 2010 -0400
>> 
>>     Moved to new branch
>> 
>> Prior to this commit file links are exported like this:
>> 
>> <a href="index.pdf">file:index.pdf</a>
>> 
>> After the commit, file links are exported like this:
>> 
>> <a href="file:index.pdf">index.pdf</a>
>> 
>> I was a bit surprised at the git bisect result because I understood
>> Tom Breton (Tehom) to be working on a testing framework, rather than
>> html export.  So, I ran through git bisect a second time and got
>> identical results.
>> 
>> I hope I've understood the procedure correctly and that this
>> information is useful.  At this point, I'm in way over my head and
>> won't be able to do more without specific instructions.
>> 
>> I'm currently using commit d56d417bc214088114e10c959ce78bee2d26635d on
>> the master branch to make my exporting and publishing setup work as
>> expected.




In the current Org-mode's version this should be fixed.
Carsten pushed a fix yesterday.




> Tom,
>
> I can't reproduce the busted link. With more-or-less-current Org-mode
> (version 6.36trans (release_6.36.102.g67b5)), the link looks like this:
>
>     <a href="foo.pdf">foo.pdf</a>
>
> Reverting the commit you identified (the revert was not clean: I had to
> resolve a merge conflict by hand - a dicey proposition, particularly in
> this situation where I have no idea what the patch is trying to do)
> gives me:
>
>     <a href="foo.pdf">file:foo.pdf</a>
>
> That's with your minimal.emacs for the other problem you've identified
> (changed to produce html of course). So it looks like the patch cleaned
> up the link name in this case.
>
> Nick
>
> PS. I also looked at the commit: I gave up on figuring it out in any
> reasonable time, but I must say the commit comment is no help.



  Sebastian

Re: Export to html

[Thomas S. Dye]

Aloha Sebastian,

Yes, the links are exporting correctly now.

Thanks,
Tom

On May 27, 2010, at 12:35 PM, Sebastian Rose wrote:

> Nick Dokos <nicholas.dokos@hp.com> writes:
>> Thomas S. Dye <tsd@tsdye.com> wrote:
>>
>>> Aloha all,
>>>
>>> On the bus this morning I was able to find out a bit more about
>>> problems with html export.
>>>
>>> Using Bernt's minimal.emacs and exporting to html with C-c C-e H,  
>>> git
>>> bisect says:
>>>
>>> 459d99c44c7df4cd09d82fa54c53e5d5eec47a4e is the first bad commit
>>> commit 459d99c44c7df4cd09d82fa54c53e5d5eec47a4e
>>> Author: Tom Breton (Tehom) <tehom@panix.com>
>>> Date:   Mon May 17 18:17:38 2010 -0400
>>>
>>>    Moved to new branch
>>>
>>> Prior to this commit file links are exported like this:
>>>
>>> <a href="index.pdf">file:index.pdf</a>
>>>
>>> After the commit, file links are exported like this:
>>>
>>> <a href="file:index.pdf">index.pdf</a>
>>>
>>> I was a bit surprised at the git bisect result because I understood
>>> Tom Breton (Tehom) to be working on a testing framework, rather than
>>> html export.  So, I ran through git bisect a second time and got
>>> identical results.
>>>
>>> I hope I've understood the procedure correctly and that this
>>> information is useful.  At this point, I'm in way over my head and
>>> won't be able to do more without specific instructions.
>>>
>>> I'm currently using commit  
>>> d56d417bc214088114e10c959ce78bee2d26635d on
>>> the master branch to make my exporting and publishing setup work as
>>> expected.
>
>
>
>
> In the current Org-mode's version this should be fixed.
> Carsten pushed a fix yesterday.
>
>
>
>
>> Tom,
>>
>> I can't reproduce the busted link. With more-or-less-current Org-mode
>> (version 6.36trans (release_6.36.102.g67b5)), the link looks like  
>> this:
>>
>>    <a href="foo.pdf">foo.pdf</a>
>>
>> Reverting the commit you identified (the revert was not clean: I  
>> had to
>> resolve a merge conflict by hand - a dicey proposition,  
>> particularly in
>> this situation where I have no idea what the patch is trying to do)
>> gives me:
>>
>>    <a href="foo.pdf">file:foo.pdf</a>
>>
>> That's with your minimal.emacs for the other problem you've  
>> identified
>> (changed to produce html of course). So it looks like the patch  
>> cleaned
>> up the link name in this case.
>>
>> Nick
>>
>> PS. I also looked at the commit: I gave up on figuring it out in any
>> reasonable time, but I must say the commit comment is no help.
>
>
>
>  Sebastian