![adding fonts to openoffice 3.3 adding fonts to openoffice 3.3](https://i.ytimg.com/vi/2Zd3f89fIt4/maxresdefault.jpg)
- Adding fonts to openoffice 3.3 install#
- Adding fonts to openoffice 3.3 zip file#
- Adding fonts to openoffice 3.3 registration#
- Adding fonts to openoffice 3.3 windows#
At the end of the installation, the CustomAction RegisterExtension (you can see it for example with Orca tool), is executed.
Adding fonts to openoffice 3.3 windows#
No, you do not need to create the CustomAction for the Windows Installer. If we need to create the custom action, which command line do we need to use (unopkg add -shared )? What kind of customization do you mean? Typically the installation is customized by using custom actions (Windows) or shell scripts (Unix). Talking about the customization of the OOo MSI, under Windows and Unix, do we need to create a custom action or a script, or does the OOo process manages that? If you want to make an additional customization for, you can of course do so.
Adding fonts to openoffice 3.3 install#
When you install the msi installation set, at the end of the installation unopkg is executed and registers the extension to. Of course you have to create a new installation set after delivering the oxt file and making the required changes in scp. You do not change the msi package, you only add an oxt-file to the installation set. Can those instructions be used to add customization to the OOo msi package or are those instructions only valid if you add the extension to the build tree and compile OOo with the extension? Of course this can be changed to all extension types supported by unopkg in the future. Other files are not found and therefore not installed with unopkg. uno.pkg)? That means are old extensions supported?Īt the end of the installation, only oxt files are searched in the directory share/extension/install. This is the only important thing: The oxt file has to be located in share/extension/install after the installation process. And this rpm installs the oxt file into the directory share/extension/install. This is packed into RPM, pkg or whatever. In scp (see later) you have to define the oxt file. or the unzipped version of the extension?
![adding fonts to openoffice 3.3 adding fonts to openoffice 3.3](https://www.qualogycaribbean.com/static/upload/lightbox/4b367b2d-7912-4fab-9e87-96343fdb184b/screenshot1-1024x614.jpg)
"Extensions need to be copied or unpacked", that means that we can put the zip, oxt. Info: This questions were asked before release of 3.3
![adding fonts to openoffice 3.3 adding fonts to openoffice 3.3](https://4.bp.blogspot.com/-ha6ykFBobiI/WLqH9PBytZI/AAAAAAAAL7M/W_p28SUEVEgdXzHP4ec1I9CbH-bQrLARgCLcB/s1600/Untitled.png)
The module defined in scp should not contain any additional content. Therefore they are packed into their own RPM (Linux) or Solaris package (Solaris) and can be selected and deselected during the installation process on all platforms. The scripts (Unix) and CustomActions (Windows), that register the extensions using the tool "unopkg", look only in the directory “share/extension/install” for oxt files.Īll extensions have to be included into an own module in scp project.
Adding fonts to openoffice 3.3 registration#
"Installed" means in this context only "copied" or "unpacked" from the installation set and does not include the registration process in the Office product. Old text for before version 3.3Īll extensions that need to be registered during installation process have to be installed into the directory “share/extension/install” in the Office installation. In the following description the changes that are required starting with 3.3 are added to the old descriptions. The inclusion of specific shellscripts is no longer required for this Unix packages and there are no more the difficult dependencies necessary, that were caused by the usage of unopkg during the installation. Furthermore for Unixes it is necessary to define a package in setup_native, so that the content of the oxt file is repackages into a native Unix package. So it is necessary to define the file (now with flag ARCHIVE!) and the directory and a module in scp2 project. This makes the installation much more robust and independent from shell scripts on Unix or CustomActions on Windows.Īll extensions are now installed into the directory “share/extensions/“. The registration of the extension into the database of happens during the start of the application, no longer during installation.
Adding fonts to openoffice 3.3 zip file#
Instead every extension is handled like a zip file with flag ARCHIVE and is repackaged during the packaging process into a native package (Solaris pkg, Linux rpm, Windows msi database), that is installed or uninstalled like every other package. The most important simplification is, that during installation no longer the tool unopkg is called. Starting with 3.3 there are some important changes concerning the integration of extensions into an installation set.