To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=72116
User obr changed the following:
What |Old value |New value
================================================================================
Status|NEW |STARTED
--------------------------------------------------------------------------------
Priority|P4 |P2
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Fri Dec 1 02:19:20 -0800
2006 -------
To give us more time to discuss the optimal solution, we reverted the patch for
70388 for OOo 2.1
(OOE680), which makes a vanilla OOo build appear as soffice.bin again. However,
it is still VCLSalFrame
for OOo 2.2 (SRC680), so I raise the Priority again to make sure the final
solution gets into OOo 2.2 in
time.
What is speaking against a hardcoded "soffice.bin" is that a) tools like
unopkg, which use VCL as well,
would expose "soffice.bin" as well and b) the ".bin" part is an implementation
detail, which should not
exposed as part of an application name.
OTOH using "OpenOffice.org" would result in several names for ORCA to check for
(StarOffice, StarSuite
...).
---------------------------------------------------------------------
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]
