On Sunday 12 November 2006 11:10 pm, Michael Gerz wrote:
> Dear Jose,
>
> Nov 13th is getting closer (oops, it's already there) and, to my
> greatest regret, I haven't managed to fix all CT problems.

  That is OK. :-)

> AFAICS, the following things do not work presently:
>
> - No change bar is given in LaTeX output if (only) the par break has
> changed - No visual clue is presente to the user, which indicates the
> status of the imaginary end-of-par character.
> - In tables, cut & paste (complete cells) do not support change tracking
> - Capitalize, Uppercase, and Lowercase are broken and must be rewritten
> to better support CT
> - When accepting or rejecting changes, paragraphs with deleted par
> breaks are not merged in nested text insets
> - There may be potential problems with breaking paragraphs (two places
> in the code look suspicious)
> - When accepting a change, LyX may hang (same as in 1.4.3)

  Maybe this should be add to the file created by Christian as missing 
features, no?

> Jose, I don't know whether you are going to publish LyX 1.5alpha today.
> IMHO, none of the open issues above should stop you from doing so. I am
> pretty confident that CT is already in a better state than it is in
> 1.4.3. People, who don't use CT, shouldn't be affected at all. Moreover,
> there is bigger problems (e.g., broken spell checker). Nevertheless, the
> open issues MUST be addressed for the first LyX 1.5beta.

  Sure.

> Unfortunately, I won't be able to work on the open issues in the next
> two days. With a little luck, I will continue on Wednesday.

  No problem, we all have a life outside LyX. (Do we?) ;-)

> Regards,
> Michael
>
> PS: I like the way LyX 1.5 evolves. The LyX developers have become a
> real good team!

  I agree. :-)
-- 
José Abílio

Reply via email to