Hi Kay,

Kay Ramme - Sun Germany - Hamburg wrote:
Oliver Braun wrote:
Assuming that users might have language packs installed in their OOs 2.0.x, the result when updating will be platform dependant:

* on Windows, the installer will detect the existing 2.0.4 and propose "OpenOffice.org 2.0" as destination directory instead => language packs still there, but potentially incompatible (might even lead to crashes).
What does "potentially" mean? Does it vary with the language, or do we just don't know?
It should not vary with the language, but with the amount of changes made. A good candidate for crashes or unexpected behavior would be to remove a tab page in Tools - Options: since the tree view to the left is loaded from the old language pack resource, but the code for the corresponding page is no longer there, any attempt to create this page will lead to a crash (or bring up another page if the id had been re-used).


* on Unix, the default directory "openoffice.org2.1" will be used, resulting in a naked OOo 2.1 with the language packs still present in "openoffice.org2.0".
As one might expect OOo2.1 to be compatible with OOo2.0, the right choice might have been simply OOo2.
I agree, but this was not clear when 2.0 was released.
So, what about future 2.x releases, do we already have an understanding what the behavior regarding language packs is going to be?
I don't think so.

Shouldn't we issue a warning on Windows and install to "OpenOffice.org 2.1" by default as on Unix ? Users willing to take the risk might still choose the "OpenOffice.org 2.0" manually.
How big is the risk, actually?
See my answer above. Any conjunction of code and string lists might be a problem. Currently I can not think of anything more, since resources missing completely in one language should get taken from default language already, but I am not an expert in this area.

Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to