fxn : yeah, you are right. I don't
understand the point to rate diaries. I thing rating articles
is more "valuable". But if the code is there, I guess it can be used to rate something else. That's good.

Have a day off today. I should dedicate it to
paper work. I have to deal with a couple administrative thinks. I also have to prepare some stuffs related to the FSF stand for the NEXT
RMS speech in Paris.... hhmmh busy day.

Went forward in writting MlView internals. I am using exclusively mlview to edit the docbook xml document.
I use intensively the element name completion
feature. This feature is definetely key because:

I don't know the docbook dtd. For each element of the
document, i rely on MlView to propose me the
children/sibling elements i have the right to create.

when i add an element, MlView automatically appends the subtree required by the dtd if any. That helps to insure the validity of the document during the edition.

Something also usefull is that i can just switch validation
off and edit the document wihtout taking the dtd in account... no stalinism there.

Writing this document is _really_ a good testbed for mlview.
I am submiting a couple of bug reports in the new mlview bug database provided by savannah.

It appears that mlview seriously needs
a new type of view to edit dtds. That would allow the users
to define new entities such as parameter entities that are
very usefull when you write big documents.

hmmmhm, i think it will take some other two or three months
of coding. Yeah, normally, it shouldn't take that long but unfortunately i write mlview during my spare time ... and
i am getting to the conclusion that their are only 24 hours in a day... i know ... that is hard to admit some time.

Their are other numerous things that mlview lacks and that
would seriously ease xml document edition. I should write these things in an other doc somewhere.

Damn, started to test mlview a bit this morning before
going to work... the "automatic-subtree-adding" feature
is still buggy.

I think i know what is going wrong : when I walk thru the
xmlElementContent tree of each dtd element declaration,
i have to take in account the 'type' field of the
xmlElementContent structure and not only the 'ocur' field.
Whether de xmlElementContent is a 'SEQ' or a 'OR'
declaration _must_ be taken in account... hmmhh,
interesting.