> Fabien Costantini wrote:
> > [...] Albrecht, if you need help with dox files, we are here.
>
> Okay then, if somebody can help with these warnings, I'd appreciate
> this:
>
> (1) drawing.dox:646: Warning: Unsupported symbol ¸ found
>
> IMHO, this should be fixed with a UTF-8 symbol, but I can't do that.
> Otherwise, someone could rewrite the corresponding text.
>
> (2) fluid.dox:413: Warning: found </c> tag without matching <c>
>
> I can't find that </c> tag ! Nowhere ! Am I blind ?
>
> (3) intro.dox:318: Warning: Unexpected tag <dd> found
OK,

- I fixed the dl,dt,dd tag sequences.
- For the &cedil; tag I'm afraid it's doxygen fault, it recognizes uumlaut but 
not all accents ...
- I don't see the /c problem too
 - I found another limitation of doxygen : it accepts <small> tag but not <big> 
and not even older <font size=+1> (which is the same)


> Fabien, you seem to have experience with OpenGL - would you
> please look at the chapters opengl.dox and glut.dox ?
Ok, I'll check it out.

> Also, if someone can fix this <b>nightmare</b> Enumerations.H !
> I tried some grouping, but I don't know enough of doxygen yet,
> to get a usable structure into this. Enum's seem to work fine,
> but define's are a mess. And there are lots of not yet
> commented defines. --- I GAVE UP --- WRT Enumerations.H ;-)
ahah, I can imagine that as Enumerations was like Fl in a way, real nightmares 
;-)
I doesn't matter if it does not look that good provided that the content is 
there and is consistent.
Remove the grouping that does not fully work for now if it's easier.
What matters first is the content, more cosmetics may come after.

> Checking links would also be appreciated. However, be careful:
> There are internal links within the same document, links to
> other tutorial documents, and links to (previous!) html files
> that can be replaced by direct references to class names and
> so on. If we don't want to destroy the tutorials, we can't
> simply replace all links with class or function/method names.
> That's what it makes is so difficult.

Okay, good work overall tonight :)


_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to