Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


There isn't really any other source files than the transform itself.
The transform is an encoded XML file 

Hmm, OK, so it isn't a relational database like .msi files. 

and I don't know of a way to
decompile it. There are some tools that can decompile Windows
Installer files but not transforms. 

What tool did you use to create the Windows Installer files?

They are created from .idt files (textual source/dump format for the relational database tables in 
the .msi) using msidb etc. These .idt files are created from information in the scp2 module, and 
then the .idt files are processed by the MSI tools in the Windows SDK. All this done and run by a 
pile of Perl in solenv/bin/make_installer.pl, and the Perl modules that it includes. Note that "we" 
(LibreOffice) did not design this, this is all stuff that has a very long history in OOo.
 
Couldn't we just create the installer database (the .msi) with your transform (suitably modified) 
pre-applied? So that if the installer is run with any of these GERMAN, SWEDISH etc parameters set, 
then that is used to decide what UI languages to install (and any IS9999 parameters are ignored).

--tml



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.