Hi Samuel,
Samuel Wales writes:
> How do we make it a reality NOW?
No, I stated my reasons here:
http://article.gmane.org/gmane.emacs.orgmode/67829
--
Bastien
Samuel Wales writes:
> On 3/6/13, Bastien wrote:
>> Hello Jambunathan,
>>
>> You are not welcome on this list anymore, please ban yourself.
>>
>> Thanks,
>
> Thank you, Bastien. This has been necessary since around May of 2011.
> How do we make it a reality NOW?
I said I want to be banned. L
On 3/6/13, Bastien wrote:
> Hello Jambunathan,
>
> You are not welcome on this list anymore, please ban yourself.
>
> Thanks,
Thank you, Bastien. This has been necessary since around May of 2011.
How do we make it a reality NOW?
Samuel Wales
--
The Kafka Pandemic: http://thekafkapandemic.blo
Bastien writes:
> Jambunathan K writes:
>
>> Bastien writes:
>>
>>> Hello Jambunathan,
>>>
>>> You are not welcome on this list anymore, please ban yourself.
>>
>> I asked you to exercise moderator controls. Why should I ban
>> myself?
>
> I am not a moderator of this list. And I would not li
Jambunathan K writes:
> Bastien writes:
>
>> Hello Jambunathan,
>>
>> You are not welcome on this list anymore, please ban yourself.
>
> I asked you to exercise moderator controls. Why should I ban
> myself?
I am not a moderator of this list. And I would not like moderators to
exercise their
> My request was merely for valid XML ID's for tables of contents from
> the HTML exporter
I understand the request but I will not comment upon whether or not it
will be supported in the exporter because that would be Nicolas call.
He has to work out the details not only for HTML exporter but als
Hello Jambunathan,
Jambunathan K writes:
> Jambunathan K writes:
[... 13 lines omitted ...]
>> Subtree export of headline 1, but with section numbers starting at 1.
>> Subtree export of headline 2, but with section numbers starting at 2.
>> Splice them together.
>
> Considering that HTML expo
Torrey
I don't mind being insulted publicly and in this mailing list. I have
weathered even better insults both on and off the list.
So you are welcome.
Jambunathan K.
tftor...@tftorrey.com (T.F. Torrey) writes:
> Hello Jambunathan,
>
> I admire your energy and coding skill, but I wish you w
Bastien writes:
> Hello Jambunathan,
>
> You are not welcome on this list anymore, please ban yourself.
I asked you to exercise moderator controls. Why should I ban myself?
> Thanks,
Hello Jambunathan,
You are not welcome on this list anymore, please ban yourself.
Thanks,
--
Bastien
Hello Jambunathan,
Jambunathan K writes:
> Is there a way your specific problem could be solved if we were to use
> CSS counters for numbering various things? Would you like to submit a
> patch to ox-html.el that uses CSS-based counters rather than counters
> computed with hand.
No.
I'm not s
Hello Jambunathan,
I admire your energy and coding skill, but I wish you would stop
occupying our time with replies like this. Your tone is insulting, and
seems deliberately so, and none of this response is helpful to the
original thread.
I won't reply to more of your posts like this, so if you
Jambunathan K writes:
>>> This gives a significant advantage in that authors can link to the
>>> various instances just by knowing their own usage. For instance, if
>>> they provided a top-level toc at the beginning of their book, and a
>>> deeper-level toc later on, they could link to each sepa
tftor...@tftorrey.com (T.F. Torrey) writes:
> extensive experience developing XSLT and lisp to process the XHTML
> output of Org,
Is there a way your specific problem could be solved if we were to use
CSS counters for numbering various things? Would you like to submit a
patch to ox-html.el that
tftor...@tftorrey.com (T.F. Torrey) writes:
>>> This gives a significant advantage in that authors can link to the
>>> various instances just by knowing their own usage. For instance, if
>>> they provided a top-level toc at the beginning of their book, and a
>>> deeper-level toc later on, they co
Hello Jambunathan,
Jambunathan K writes:
> Torrey
>
One small problem, though: I see that if there is a TOC at the top and
then one included later using #+TOC, the exporter gives them both the
same id (). Duplicate ID's makes the XML
invalid.
>>>
>>> What do you suggest inst
>> This gives a significant advantage in that authors can link to the
>> various instances just by knowing their own usage. For instance, if
>> they provided a top-level toc at the beginning of their book, and a
>> deeper-level toc later on, they could link to each separately by id by
>> knowing
Torrey
>>> One small problem, though: I see that if there is a TOC at the top and
>>> then one included later using #+TOC, the exporter gives them both the
>>> same id (). Duplicate ID's makes the XML
>>> invalid.
>>
>> What do you suggest instead? id="table-of-contents-1" for the first
>> #+TOC
Nicolas Goaziou writes:
> Hello,
>
> tftor...@tftorrey.com (T.F. Torrey) writes:
>
>> One small problem, though: I see that if there is a TOC at the top and
>> then one included later using #+TOC, the exporter gives them both the
>> same id (). Duplicate ID's makes the XML
>> invalid.
>
> What d
Hello,
tftor...@tftorrey.com (T.F. Torrey) writes:
> One small problem, though: I see that if there is a TOC at the top and
> then one included later using #+TOC, the exporter gives them both the
> same id (). Duplicate ID's makes the XML
> invalid.
What do you suggest instead? id="table-of-con
Hello Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> tftor...@tftorrey.com (T.F. Torrey) writes:
>
>> The new exporter currently puts the generated Table of Contents at the
>> beginning of the exported document in addition to the location of
>> "#+TOC: headlines". I don't think it should insert
Hello,
tftor...@tftorrey.com (T.F. Torrey) writes:
> The new exporter currently puts the generated Table of Contents at the
> beginning of the exported document in addition to the location of
> "#+TOC: headlines". I don't think it should insert it at the beginning
> when it is called later.
I
Hello,
The new exporter currently puts the generated Table of Contents at the
beginning of the exported document in addition to the location of
"#+TOC: headlines". I don't think it should insert it at the beginning
when it is called later.
However, I think the new exporter introduces disparitie
23 matches
Mail list logo
