On Apr 17, 2009, at 12:37 AM, Sebastian Rose wrote:
Carsten Dominik writes:
On Apr 16, 2009, at 10:50 PM, Sebastian Rose wrote:
Carsten Dominik writes:
Hi Sebastian,
On Apr 16, 2009, at 3:14 PM, Sebastian Rose wrote:
Hm - counter arguments?
The only counter argument is, that hand made
Carsten Dominik writes:
> On Apr 16, 2009, at 10:50 PM, Sebastian Rose wrote:
>
>> Carsten Dominik writes:
>>> Hi Sebastian,
>>>
>>> On Apr 16, 2009, at 3:14 PM, Sebastian Rose wrote:
>>>
Hm - counter arguments?
The only counter argument is, that hand made IDs for links are prone t
On Apr 16, 2009, at 10:50 PM, Sebastian Rose wrote:
Carsten Dominik writes:
Hi Sebastian,
On Apr 16, 2009, at 3:14 PM, Sebastian Rose wrote:
Hm - counter arguments?
The only counter argument is, that hand made IDs for links are
prone to
error. But that risk should be up to the user.
Carsten Dominik writes:
> Hi Sebastian,
>
> On Apr 16, 2009, at 3:14 PM, Sebastian Rose wrote:
>
>> Hm - counter arguments?
>>
>> The only counter argument is, that hand made IDs for links are prone to
>> error. But that risk should be up to the user.
>
> Yes. and during the export, I can actuall
Hi Sebastian,
On Apr 16, 2009, at 3:14 PM, Sebastian Rose wrote:
Hm - counter arguments?
The only counter argument is, that hand made IDs for links are prone
to
error. But that risk should be up to the user.
Yes. and during the export, I can actually check and throw a warning
or an err
Hm - counter arguments?
The only counter argument is, that hand made IDs for links are prone to
error. But that risk should be up to the user.
I actually changed my mind a little in this concern.
If the user clicks a section link in the toc to jump to a section, he
can bookmark the page with exa
On Apr 16, 2009, at 10:50 AM, Sebastian Rose wrote:
Carsten Dominik writes:
Hi Sebastian,
I kind of like the idea to have a property that can be
used to set an ID, as an alternative to the <>
notation. Actually, using a property seems a lot cleaner,
thanks for coming up with this idea, Dani
Carsten Dominik writes:
> Hi Sebastian,
>
> I kind of like the idea to have a property that can be
> used to set an ID, as an alternative to the <>
> notation. Actually, using a property seems a lot cleaner,
> thanks for coming up with this idea, Daniel.
>
> I can also follow the reasoning that i
Hi Sebastian,
I kind of like the idea to have a property that can be
used to set an ID, as an alternative to the <>
notation. Actually, using a property seems a lot cleaner,
thanks for coming up with this idea, Daniel.
I can also follow the reasoning that it is useful to have
the table of conte
El dv, mar 27 2009, Sebastian Rose va escriure:
>
> What we have now, just as Carstens said:
>
> # <>
> * Section B
>
> Creates this headline in HTML:
>
> 2 Section B
>
>
> This is enough for all the use cases I can think of.
>
Yes, this is enough except for two things:
1. The TOC still
I don't think this is an important change.
Here some thoughts that come to mind in this context.
What we have now, just as Carstens said:
# <>
* Section B
Creates this headline in HTML:
2 Section B
This is enough for all the use cases I can think of.
The section and headline may b
Carsten Dominik writes:
> I guess, with some work, we could reorganize the link storage
> in a way that a user-given target of an ID become the preferred
> hrefs and that section numbers will only be used when there is
> not alternative.
>
> h. How important is this.?
I think it would b
12 matches
Mail list logo
