To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=106434


User fs changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|''                        |'jsc'
--------------------------------------------------------------------------------
OtherIssuesDependingOnTh|                          |99999
                      is|                          |
--------------------------------------------------------------------------------
        Target milestone|---                       |OOo 3.2
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Thu Oct 29 12:35:44 +0000 
2009 -------
The attached file illustrates the problem (or at least parts of it): Place it in
offapi/com/sun/star/sdb, and run autodoc: The see-tags for the global entity and
for the first member are ignored by autodoc, though there's nothing fancy there,
they're most straight-forward.

Only the tag for the second member is respected, here the difference seems to be
thatt the tag is followed by additional text. However, the following text is
(wrongly) put below the "See also" item in the HTML file, so even here, autodoc
is not completely right

Nominating as 3.2 stopper. I do not think we should release an API documentation
in this state.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to