[Docutils-develop] Re: Help!

[Felix W. <Fel...@gm...>]

David Abrahams wrote:

> David Abrahams writes:
>
>> David Goodger writes:
>> 
>>> I'm very busy right now, but I'll try to take a look this weekend.
>>
>> Me too; I know how it is.  There's no rush, 
>
> Okay, I probably shouldn't have said that, but...

:)

>> but I do want to make sure it hasn't fallen into a black hole.
>
> ...now I am getting desperate.  The book is finished;

Cool.  I mean, that the book is finished.

> I have to move on to my next project, and I need to choose a
> documentation system.

If there are any reasons against reST, I'd be glad to hear them.

> I need to know whether there's a future for me here.

Depends on whose future you mean:

*Your* future here, as a user and/or developer: Sure, you're always
welcome.  (You hopefully didn't expect anything else, did you?)

The future of the nested inline parser you started: I don't know for
sure.  Frankly, I reckon it might be necessary to refactor the inline
parser from scratch in order to get nested inline markup working,
especially because the parser uses many regexes.  (I don't mean the
design is bad or so.  It's just that it may be unsuitable for nested
markup.)  On the other hand, I must admit that I do not fully understand
how the implementation of the current inline parser is structured, and
neither do I know very much about writing parsers in general, so I might
very well be wrong.

The future of nested inline markup in general: I'm quite confident that
it will be implemented sooner or later.

-- 
When replying to my email address, please ensure
that the mail header contains 'Felix Wiemann'.

http://www.ososo.de/