To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=66594
User as changed the following:
What |Old value |New value
================================================================================
Assigned to|as |hro
--------------------------------------------------------------------------------
Target milestone|--- |OOo Later
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Wed Jul 26 23:23:03 -0700
2006 -------
a) You say that the file "ProtocolHandler.xcu" isnt realy a problem, because it
does not
exist in real ... That's true and false at the same time .-)
TRUE: If you installed an office as new, these file does not exists.
But then these error message cant occure. Nobody search for such file if it was
not
installed before.
FALSE: If you installed an AddOn using "Tools->PackageManager" such file can
exists. And then it's needed. Otherwhise the installed addon does not work.
It's not a problem for the core functionality of OOo ... but the addon will be
missing.
b) The second problem is also related to a configuration file (means xcs/xcu
file).
Those files are needed by an office installation. And they must be ready for
reading /
writing. If (as it is in your case) the filter configuration cant be read
completely the office
doesnt start - because then it's not possible to open documents ... further
it's not
possible to create empty doicuments also. Both facts are not acceptable for an
office.
Ok - the xslt filter file is only one part of the whole set of filter
configuration files. But all
these files will be merged together at runtime. And the code of OOo itself will
see the
results only. So one missing part will be enough to produce a corrupted merged
configuration view.
=>
All these errors are related to our configuration. Those files are read nativly
by using the
funtionality of OSL (a c++-library of OOo). Opening of files instead uses the
UCB (an
uno component, which uses internaly OSL). For me it looks like a problem of OSL
...
might be triggered by the configuration component by using OSL "wrong or not in
an
optimized way".
Might be it's a problem of the used windows API also.
AS->HRO: seams to be your part - i guess.
---------------------------------------------------------------------
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]
