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





------- Additional comments from [EMAIL PROTECTED] Thu Nov 27 14:27:57 +0000 
2008 -------
This is the problem with all 3rd party code. We include several parts in OOo
that we don't create ourselves. As an example, if a bug in the libxml2 creates a
problem in OOo, we won't track it in our Issue Tracker but forward it to the
project responsible for libxml2.

So again, your request is totally valid and it is absolutely OK that you have
submitted it in Issue Tracker. Users don't know (and shouldn't need to know)
which part of OOo might be the root cause for a particular problem and who is
responsible for the problem.

OTOH we must handle the issues somehow, and unfortunately Issue Tracker has no
way to refer to external projects. So usually we close the issue as "invalid"
and forward the issue into the tracking system of the external project. 

The "external component" here is the dictionary, and the only "tracking system"
it has is the comment section of the repository.

Tracking issues for 3rd party extensions is a good suggestion, though it
requires that the submitter has an OOo account. In the current case that seems
to be doable, but it seems that auberon preferred to use the comment section. I
leave it up to him to decide whether he wants to reopen this issue and assign it
to himself.

---------------------------------------------------------------------
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