You are here

Language Packs make problems during installation with OOP 3

8 posts / 0 new
Last post
portable_sunray
portable_sunray's picture
Offline
Last seen: 4 years 2 months ago
Joined: 2008-12-21 11:59
Language Packs make problems during installation with OOP 3

I installed the new portable version 3 today - THANKS TO THE AUTHORS!!! - after having uninstalled the "normal" version 3.

When I tried to add several language packs for v3 I got into trouble. The lang packs wouldn't recognize the portable version at all in neither subfolder I tried.

Then I got the idea
- to rename the folder \portableapps\OOP3\App\openoffice temporarely into
openoffice.org 3,
- installed several Lang packs,
- renamed the folder back to the original name "openoffice".

Everything seems to work fine even on another computer from USB stick. On the other hand I have no idea where else the lang packs left files.

So I have 2 Qs:
(1) Is there an easier way to install additional languages?

(2) Why does the portable version not use the original folder name "openopffice.org 3"?

John T. Haller
John T. Haller's picture
Online
Last seen: 8 min 27 sec ago
AdminDeveloperModerator
Joined: 2005-11-28 22:21
Not Yet Supported

The language pack installers from OpenOffice.org are made to only work with the local install. We would need to repackage them for portable use.

We may or may not release additional language packs in addition to our supported full packages as it is a lot of extra work to build and maintain for the 0.01% of users who would want multiple interface languages.

Sometimes, the impossible can become possible, if you're awesome!

portable_sunray
portable_sunray's picture
Offline
Last seen: 4 years 2 months ago
Joined: 2008-12-21 11:59
TNX

Thanks for that piece of information. I understand the problem better now.

Would I damage my OOP3 installation by integrating the lang pack with the trick of temporarely renaming a folder as I described?
It seems to work and I am happy with that solution.

Let's keep the free world free.

MarkoMLM
MarkoMLM's picture
Offline
Last seen: 5 years 11 months ago
DeveloperTranslator
Joined: 2006-01-16 04:08
some answers ...

first, the folder OpenOffice.org 3 cause problems esp. for upgrades, that is one reason we dont use it. There were some other problems with pre-release 1 because of this folder.

second, die installation with this trick will leave entries in Your local registry and some other files/informations for ininstall.

This trick will not demage Your OpenOffice.org 3 Portable installation but will mess up Your host system and thats why ist not recommended.

Paid for Software more or less?
What You need is OSS!

John T. Haller
John T. Haller's picture
Online
Last seen: 8 min 27 sec ago
AdminDeveloperModerator
Joined: 2005-11-28 22:21
Hmm

Hey Marko, would it work if we created an installer helper that could rename the drive's openoffice folder to OpenOffice.org 3, launch the language pack setup pointing it to the proper place and once it finished, clean up the local PC registry entries? It would require admin rights, but it might be an easy way to quickly make OOo Portable available in multiple languages.

Sometimes, the impossible can become possible, if you're awesome!

portable_sunray
portable_sunray's picture
Offline
Last seen: 4 years 2 months ago
Joined: 2008-12-21 11:59
Registry entries...

Meanwhile, I had an intensive discussion via Ccleaner.com with my XP MUI registry and found some interesting details:

  1. I had an OOO3 (non-portable) installation with 5 additional lang packs and several other add-ons without entries in the Windows Add and remove programs menu. I un-installed first the lang packs, than OOO3 - one after the other. I never interfered with any of the folders in my OOO3.
    There still existed 15 registry entries left from OOO3 concerning the
    ..\Basis\program\python...,
    ..\Basis\program\help\en...,
    ..\share\uno-packages\cache... folders.
    .
  2. With the additional lang packs installed by temporarily renaming the OO folder in OOP3 (portable) I really got about 30 registry entries for each lang pack, a total of almost 150 for 5 lang packs. Impressive!
    It was no real problem to delete them with the help of the Ccleaner.
  • Q: The portable MUI version with 5 additional lang packs works perfectly on other computers. Switching between the languages is easy. Why are so many registry entries necessary anyway?

Thanks again to all the people who keep this fantastic software running!
Have a nice and relaxing holiday season and a wonderful 2009!

Let's keep the free world free.

MarkoMLM
MarkoMLM's picture
Offline
Last seen: 5 years 11 months ago
DeveloperTranslator
Joined: 2006-01-16 04:08
Nope!

... cause this makes no sense.
To create such a solution will take longer as the current way to create portable language packs and the result will be a package with more problems than a real benefit.
As John said admins rights are needed, but thats not the real no go. There will be a lot of registry entries on the host computer and we will have no secure way to catch and deletem them all.

Perhaps, if we will have a way to create the portables in future direct from source over the builtbots there will also packages for the languagepacks without this issue.

In the meantime I prefere languagepacks as plugin installer.

Paid for Software more or less?
What You need is OSS!

loveleeyoungae
Offline
Last seen: 2 years 1 month ago
Joined: 2008-06-01 01:04
Extract the langpack installer?

I notice that you can open the installer with 7-zip, and there is a CAB containing the localized files. So, is there a way to just extract those files and copy them over to OOo Portable, because I don't want to run the installer?

Log in or register to post comments