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


User sb changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|REOPENED                  |STARTED
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Thu Sep 25 12:05:41 +0000 
2008 -------
Indeed, a libxml2.dll from a Windows system directory will take precedence over
the URE layer libxml2.dll (which the soffice.exe wrapper puts into the PATH of
soffice.bin), see <http://msdn.microsoft.com/en-us/library/ms682586.aspx>.  As a
quick hack, for now place an additional copy of the URE layer libxml2.dll into
the brand layer program directory (where in turn it will take precedence over a
libxml2.dll from a Windows system directory).

The modifications already done on CWS sb97 (see above) appear to not be that
urgently necessary after all, so we should not include that CWS in OOo 3.0.0,
but rather in OOo 3.1.0.

A proper fix for this issue would involve a manifest file for our URE layer
libxml2.dll (and other external libraries bundled with OOo), so that OOo
executables would no longer "by accident" pick a libxml2.dll from a Windows
system directory.  This will be done later, in a separate issue.

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