José Matos wrote:
On Tuesday 18 November 2008 19:04:50 rgheck wrote:
OK, well, I take it that this effort needs co-ordination and that you
are the man to co-ordinate it. So if you want at some point to give me
some particular tasks to do here, let me know.
The purpose of this code was to initiate the development. This code is
necessary to bootstrap the procedure. If someone else wants to coordinate the
process that is OK with me. :-)
I'm perfectly happy for you to co-ordinate it. I think you're obviously
the right choice, in fact. Mostly, the question was whether we have a
roadmap and what I can do to help. So I'll wait for the other message on
that.
+def find_paragraph_boundaries(document, i):
+ j = find_end_of_layout(document.body, i)
+ k = j + 1
Presumably an error check is needed here. Actually, I guess if j = -1,
we end up returning -1 anyway, but it'd be clearer to do the check.
This should not ever happen as it would mean that the file is truncated.
Yes, of course, but there are lots of other places where we do this kind
of test and take some kind of corrective measures if there's a problem.
My impression is that we always try to make sure that we produce a valid
LyX file, even if we weren't handed one.
Richard
