On Sat, Feb 11, 2006 at 10:22:59AM +0100, Michael Gerz wrote:
> Martin Vermeer wrote:
>
> >Basically it introduces one more position in a paragraph, after the last
> >character (i.e., pos = par.size() ) to represent the change attached to
> >the paragraph break ("carriage return", which we don't really have in
> >our model).
> >
> >
> Martin, thank you very much for your work! One question: Others have
> pointed out that there should be an inset for line and paragraph breaks.
> This sounds like a more elegant solution that just adding one more
> hidden character.I don't necessarily agree. We do have a newline inset, but I kind of like the current philosophy of a text being a container of paragraphs, with one more cursor position than there are characters [not considering boundary, that is] > >2) I added a "[C]" display in the status bar when change tracking is on. > >Actually I believe we can now allow CT to be switched on and off by the > >user without demanding a merge, which caused trouble under the old > >architecture. That's more like the way OOo (and MS Word?) works, and > >saner IMHO. > > > > > That is just great! > > I am busy right now but I will hopefully find some time for testing by > the end of next week. Let's hope the tree is open for 1.4.1 then... - Martin
pgpql4Ku3u1wm.pgp
Description: PGP signature
