You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by wa...@apache.org on 2020/11/01 21:10:24 UTC
[openoffice-org] 02/03: Migration of installation html content
This is an automated email from the ASF dual-hosted git repository.
wave pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
commit a126527d62db8558359b31bb24fa8e6a9df0cfa7
Author: Dave Fisher <da...@davefisher.tech>
AuthorDate: Sun Nov 1 13:10:06 2020 -0800
Migration of installation html content
---
content/installation/How_to_scp_in_ooo.html | 69 +++
.../how_to_create_native_installer.html | 208 +++++++
content/installation/how_to_repackage_oo.html | 165 ++++++
content/installation/how_to_repackage_so.html | 214 +++++++
content/installation/how_to_scp_oo.html | 576 ++++++++++++++++++
content/installation/index.html | 475 +++++++++++++++
.../installation/pics/automatical_assignments.html | 56 ++
content/installation/pics/scpitem_directory.html | 81 +++
content/installation/pics/scpitem_file.html | 156 +++++
content/installation/pics/scpitem_folder.html | 38 ++
content/installation/pics/scpitem_folderitem.html | 43 ++
.../installation/pics/scpitem_installation.html | 39 ++
content/installation/pics/scpitem_mergemodule.html | 54 ++
content/installation/pics/scpitem_module.html | 124 ++++
content/installation/pics/scpitem_profile.html | 40 ++
content/installation/pics/scpitem_profileitem.html | 43 ++
.../installation/pics/scpitem_registryitem.html | 44 ++
content/installation/pics/scpitem_scpaction.html | 55 ++
content/installation/pics/scpitem_shortcut.html | 53 ++
.../installation/pics/scpitem_templatemodule.html | 146 +++++
content/installation/pics/scpitem_unixlink.html | 46 ++
.../pics/scpitem_windowscustomaction.html | 49 ++
content/installation/pics/undefining_gids.html | 58 ++
.../pics/understanding_the_lng_files.html | 162 +++++
.../pics/understanding_the_patch_flag.html | 113 ++++
.../pics/understanding_the_scipt_elements.html | 125 ++++
.../pics/understanding_the_scipt_language.html | 106 ++++
.../pics/understanding_the_scp_project.html | 118 ++++
content/installation/proposals/netinstall.html | 177 ++++++
.../setup_feature/setup_features60_proposal.html | 660 +++++++++++++++++++++
content/installation/red.html | 140 +++++
31 files changed, 4433 insertions(+)
diff --git a/content/installation/How_to_scp_in_ooo.html b/content/installation/How_to_scp_in_ooo.html
new file mode 100644
index 0000000..36fca63
--- /dev/null
+++ b/content/installation/How_to_scp_in_ooo.html
@@ -0,0 +1,69 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 8 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20070730;17312200">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>How
+to scp in OpenOffice.org?</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Understanding
+the principles of the scp project is important for everyone, who
+makes changes, which concern the installation set. Adding a new file
+or changing an entry in the Windows registry are typical examples,
+which make necessary changes in one of the scp projects. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+scp projects are important for creating the setup script files, which
+can be found in the installation set next to the setup executable
+file. The name of the setup scripts is normally setup.inf for the
+Windows platform and setup.ins for Unix platforms.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">This
+(of course not complete) introduction describes the user in different
+steps his daily work with the scp projects. Everyone who never worked
+with scp, should read the file</FONT></P>
+<P><A HREF="pics/understanding_the_scp_project.html"><FONT FACE="Verdana, sans-serif">Understanding
+the scp projects</FONT></A></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">to
+get a better understanding of the different scp projects, the build
+mechanisms and the possibilities inside this projects. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+script language is described for an example file in the document</FONT></P>
+<P><A HREF="pics/understanding_the_scipt_language.html"><FONT FACE="Verdana, sans-serif">Understanding
+the script language</FONT></A></P>
+<P><FONT FACE="Verdana, sans-serif">All elements, which can be
+defined in the scp projects, like <A HREF="pics/scpitem_file.html">Files</A>,
+<A HREF="pics/scpitem_directory.html">Directories</A>, <A HREF="pics/scpitem_unixlink.html">Unixlinks</A>,
+... are explained in the page</FONT></P>
+<P><A HREF="pics/understanding_the_scipt_elements.html"><FONT FACE="Verdana, sans-serif">Understanding
+the script elements</FONT></A></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">This
+is a very detailed explanation of the scripting language and allows a
+very good understanding of the complete setup script. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+meaning of the lng files, which are important for translation
+reasons, in the scp projects is described in </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="pics/understanding_the_lng_files.html">Understanding
+the lng files</A>.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Additional information about the
+patch creation using the flag "PATCH" is described in </FONT>
+<FONT FACE="Verdana, sans-serif"><A HREF="pics/understanding_the_patch_flag.html">Understanding
+the PATCH flag</A>.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Two important concepts in the scp
+projects are the <A HREF="pics/automatical_assignments.html">automatical
+assignment</A> of global IDs to modules (including the removal of
+undefined global IDs from modules) and the <A HREF="pics/undefining_gids.html">undefining
+of global IDs</A>.</FONT></P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/how_to_create_native_installer.html b/content/installation/how_to_create_native_installer.html
new file mode 100644
index 0000000..6469834
--- /dev/null
+++ b/content/installation/how_to_create_native_installer.html
@@ -0,0 +1,208 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="CREATED" CONTENT="20040628;10483376">
+ <META NAME="CHANGED" CONTENT="20040628;14315971">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P><FONT SIZE=5><B>HowTo create native installation sets for
+OpenOffice.org 2.x<BR></B></FONT><BR><BR>
+</P>
+<P>by <A HREF="mailto:is@openoffice.org">Ingo Schmidt</A></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4><BR>Introduction:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">This HowTo describes the necessary
+steps to create native installation sets for OpenOffice.org 2.0. This
+includes Windows Installer for the Windows platform, RPMs for Linux
+and Solaris-packages for Solaris. Because of the usage of EPM is will
+also be possible to create native installation sets for all operating
+systems supported by EPM. In the current EPM version 3.7 this are:
+AIX, FreeBSD, NetBSD, OpenBSD, HP-UX, Debian software distribution,
+IRIX, MacOS X. The currently available process is adapted to Windows,
+Linux and Solaris. Therefore it might be necessary to make some
+changes in the new packaging process for the other platforms. The
+installation sets are created in the new cvs module
+„instsetoo_native“, but it is also still possible to
+create installation sets using the old setup application in the cvs
+module „instsetoo“. But in the near future we want to
+remove the module „instsetoo“ and with it the old setup
+application located in the cvs module „setup2“</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>The packaging program:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">New CVS modules were introduced for the
+usage of native installer. This are „setup_native“ and
+„instsetoo_native“. Additionally the packaging program
+was added to the „solenv“ module.
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>„solenv“</U>: The new
+packaging program is completely Perl based. You find it in
+solenv/bin. The main program is called „make_installer.pl“.
+It uses all the Perl submodules located in
+solenv/bin/modules/installer.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>„setup_native“</U>: This
+new cvs module contains at the moment the Windows Installer custom
+actions, that are executed during the installation process.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>„instsetoo_native“</U><SPAN STYLE="text-decoration: none">:
+This is the new packaging module. In the output tree of
+„instsetoo_native“ the installation sets are created. You
+will find there also a preregistered services.rdb, many unpacked zip
+files, logging files and many files more. Therefore you need
+sufficient disc space for the „instsetoo_native“
+directory. This shows that the new packaging process includes much
+functionality, that was included in our old setup application, but is
+not supported by the native installers. Therefore is also takes more
+time to create the native installation sets, but we are still trying
+to optimize this process.</SPAN></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>The packaging process:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Included in the new packaging process
+are different Perl programs, that create the native installation sets
+based on the information stored in our platform independent
+installation set description language „scp“. Files,
+directories, and many things more are described in the cvs module
+„scp2“. Based on these files, a platform and product
+specific setup script is created, which is then used by the new
+packaging process to create the native installation sets. The
+different processes are shown in the following graphic:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><IMG SRC="pics/how_to_create_native_installer.gif" NAME="Grafik1" ALIGN=LEFT WIDTH=571 HEIGHT=408 BORDER=0><BR CLEAR=LEFT><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>Prerequisites:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">For the new native packaging process,
+new prerequisites are needed. Especially there are different
+prerequisites for the Windows OS and the non-Windows OS:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>Windows</U>: For creating
+successfully Windows Installer installation sets it is needed, that
+you have installed the Windows Plattform SDK with Windows Installer
+SDK, Version February 2003. This is available at
+<A HREF="http://www.microsoft.com/msdownload/platformsdk/sdkupdate/">http://www.microsoft.com/msdownload/platformsdk/sdkupdate/</A>
+.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The two Windows Installer files
+instmsia.exe and instmsiw.exe (non-Unicode and Unicode version of the
+Windows Installer service) have also to be downloaded from the
+Microsoft homepage. For the packaging process they have to be located
+in the directory „instsetoo_native/inc_openoffice/windows/msifiles“.
+This will probably change in the near future.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>Non-Windows</U>:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">For the non-Windows platforms it is
+essential, that you have installed EPM, v. 3.7 on your system. You
+can download it from <A HREF="http://www.easysw.com/epm/">http://www.easysw.com/epm/</A></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Using EPM for Linux or Solaris we
+approve the usage of a patch, that can be downloaded <A HREF="epm-3.7.patch">here</A>.
+This patch fixes the following problems:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The RPMs or Solaris packages are
+relocatable. This means, that the administrator can change the
+OpenOffice.org installation directory. Non relocatable RPMs or
+Solaris packages are always installed at a fixed place in the
+directory system. In the version 4.0 of EPM it is planned, to make
+the packages relocatable, then this patch becomes superfluous.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">A second problem occurs only on Linux
+and is caused by some dependency problems of the OpenOffice.org
+libraries. Without the patch the OpenOffice.org core RPM can only be
+installed with the parameter „--nodeps“. If you use the
+patch, you can simply install „rpm -i
+openoffice-core-680-1.i586.rpm“.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Using Solaris 8 and Solaris 9 maximum
+package name contains 9 characters. Because this is not sufficient
+for for the different OpenOffice.org packages, we decided to make use
+of Bug 4025718, which introduces the maximum of 25 characters for a
+package name. This requires that the following patches are installed
+on Solaris systems:</P>
+<P STYLE="margin-bottom: 0cm"><BR>The longer packages names we
+introduce by Bug 4025718. <BR>If your building packages on Solaris 8
+you need patches: <BR>110934-12 (sparc) & 110935-12 (x86) <BR>If
+your building packages on Solaris 9 you need patches: <BR>113713-03
+(sparc) & 114568-02 (x86)
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>Installation of native
+installation sets:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>Windows:</U> The installation set is
+located in the directory
+instsetoo_native/wntmsci10.pro/OpenOffice/install . You find there an
+executable „setup.exe“, which you can simply start. Then
+you get the well-known Windows Installer GUI that will guide you
+through the installation process. The OpenOffice.org can only be
+removed with the „Add-Remove-Software-Applet“, that is
+located in the Control Panel.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P><U>Linux</U>: The installation set is located in the directory
+instsetoo_native/unxlngi5.pro/OpenOffice/install . You find there
+different RPMs belonging to the installation set. You can decide
+wheter you want to install all of them or only parts. The names of
+the RPMs are not fix yet. First of all you have to install the core
+RPM openoffice-core-680-1.i586.rpm. All other RPMs have a dependency
+to this core package. For installing a RPM you need to have root
+priviliges. Than you can simply install it by :</P>
+<P>rpm -i openoffice-core-680-1.i586.rpm --prefix=/opt/myOOOdir
+(relocatable with the optional parameter --prefix)
+</P>
+<P>Without using the EPM patch, you also have to use the parameter
+„--nodeps“.</P>
+<P>You can remove the RPM with the command (this is also system
+dependent)</P>
+<P>rpm -e openoffice-core-680-1.i586.rpm</P>
+<P><U>Solaris</U>: The installation set is located in the directory
+instsetoo_native/unxsols4.pro/OpenOffice/install
+(instsetoo_native/unxsoli4.pro/OpenOffice/install for Solaris x86) .
+You find there different Solaris packages belonging to the
+installation set. You can decide wheter you want to install all of
+them or only parts. The names of the packages are not fix yet. First
+of all you have to install the core package OOOopenoffice-core. All
+other packages have a dependency to this core package. For installing
+a Solaris package you need to have root priviliges. Than you can
+simply install it by :</P>
+<P>pkgadd -a adminfile.txt -d . OOOopenoffice-core (relocatable with
+the optional admin file (parameter -a) in which
+"basedir=/opt/myOOOdir" has to be defined)
+</P>
+<P>You can remove the Solaris package with the command:</P>
+<P>pkgrm OOOopenoffice-core</P>
+<P><BR><BR>
+</P>
+<P>And now have fun with the native installer :-)</P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/how_to_repackage_oo.html b/content/installation/how_to_repackage_oo.html
new file mode 100644
index 0000000..86638aa
--- /dev/null
+++ b/content/installation/how_to_repackage_oo.html
@@ -0,0 +1,165 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+<head>
+
+ <meta http-equiv="CONTENT-TYPE" content="text/html; charset=iso-8859-1">
+ <title></title>
+
+ <meta name="GENERATOR" content="StarOffice/5.2 (Win32)">
+
+ <meta name="AUTHOR" content="Oliver Bolte">
+
+ <meta name="CREATED" content="20001218;17461754">
+
+ <meta name="CHANGEDBY" content="Ingo Schmidt">
+
+ <meta name="CHANGED" content="20010205;15392152">
+
+ <style>
+ <!--
+ @page { margin: 2cm }
+ -->
+ </style>
+</head>
+ <body>
+
+<p align="Center" style="margin-bottom: 0cm;"><b><font size="5">HowTo repackage
+an OpenOffice.org installation set<br>
+ </font></b><font size="5"><small><small>by </small></small></font><b><font size="5"><small><small><a href="mailto:Oliver.Braun@sun.com">
+ Oliver Braun</a></small></small><br>
+ </font></b></p>
+
+<p align="Center" style="margin-bottom: 0cm;"></p>
+
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+ Introduction:</font></p>
+
+<p style="margin-bottom: 0cm;"><span style="font-weight: medium"></span></p>
+
+<p style="margin-bottom: 0cm;"> </p>
+
+<p style="margin-bottom: 0cm;">This HowTo describes the necessary steps to
+take to be able to make standard unix packages (rpm, pkg, ..) out of an OpenOffice.org
+installation set. It does not deal with any specific package manager. If you
+have created a script for your favourite package manager and want to share
+it with others, please drop me a <a href="mailto:Oliver.Braun@sun.com?subject=package%20manager%20script">
+ note</a>.</p>
+
+<p style="margin-bottom: 0cm;">The OpenOffice.org 641 B/C installation
+on a unix system differs slightly from an StarOffice<small><sup>TM</sup></small>
+ 6.0 installation, so if you are looking for instructions for the
+last one, you should look <a href="how_to_repackage_so.html">here</a>
+. The most obvious difference between OpenOffice and StarOffice<small><sup>
+TM</sup></small> 6.0 is the missing menu integration for KDE
+and GNOME. Before copying the this integration to the OpenOffice.org installation
+sets it should be made clear if the OpenOffice.org community likes the document
+centric approach of the panel menus and if it wants to create an own set
+of icons or to stick with that ones provided for StarOffice<small><sup>TM</sup></small>
+. </p>
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+ A. Install OpenOffice on your machine</font></p>
+<ol>
+ <li>
+ <p style="margin-bottom: 0cm;">Log into your machine as <b>root</b>. </p>
+ </li>
+ <li>
+ <p style="margin-bottom: 0cm;">Start the setup application with the "-net"
+ option: <b><path-to-office-installation-set>/setup -net &</b><br>
+ </p>
+ </li>
+ <li>
+ <p style="margin-bottom: 0cm;">On the "Select Installation Type" page,
+ select "<b>Custom Installation</b>".</p>
+ </li>
+ <li>
+ <p style="margin-bottom: 0cm;">On the "Select OpenOffice641 Modules"
+ page open the node "<b>Optional Components</b>" and <br>
+a) de-select "Java Environment Installation" if you want to detect/select
+ the java version yourself.<br>
+ </p>
+ </li>
+ <li>
+ <p style="margin-bottom: 0cm;">Choose the directory to install to, e.g.
+ <b>/opt/OpenOffice641</b>, and install.<br>
+ <br>
+ </p>
+ </li>
+</ol>
+<p style="margin-bottom: 0cm;"><font size="4">B. Create the package file
+list(s)</font></p>
+<p style="margin-bottom: 0cm;">Before you start to scan the directory tree
+ you should decide if you want to create one single package containing all
+ files or if you prefer two packages, a binary and a language one. The second
+ way has the advantage of saving a log of disk space if you are going to
+provide packages for different languages on the same disc.</p>
+<p style="margin-bottom: 0cm;">To split the file list into two, you should
+ include all files in <b><path-to-openoffice-root>/program/resource</b>
+ and the <b><path-to-openoffice-root>/share</b> tree into the
+ language package list and the rest into the binary package list.</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><font size="4">C. GNOME 1.4 integration</font></p>
+<p style="margin-bottom: 0cm;">StarOffice<small><sup>TM</sup></small><font size="3">
+ 6.0 comes with a user space GNOME 1.4 integration that consists of a set
+of zip files containing the menu integration files and a small binary that
+does the user space filetype registration. As you may want the GNOME integration
+to be system wide, you can only take the corresponding files as templates,
+but have to provide your own set of files.</font></p>
+<p style="margin-bottom: 0cm;"><font size="3">To find the files provided
+by </font>StarOffice<small><sup>TM</sup></small><font size="3"> you will
+have an OpenOffice.org build tree available. You should find the following
+two sets of zip files in the output tree of a successful OpenOffice build:
+ group_pngs.zip, writer_pngs.zip, calc_pngs.zip, draw_pngs.zip, impress_pngs.zip
+ (containing the icons) and gnomeappgroup.zip, gnomeappwriter.zip, gnomeappcalc.zip,
+ gnomeappdraw.zip, gnomeappimpress.zip (cntaining the .desktop templates). </font></p>
+<p style="margin-bottom: 0cm;"><font size="3">If you want to register </font>
+ the OpenOffice<font size="3"> file types, you may will find a list of
+them <a href="http://framework.openoffice.org/documentation/mimetypes/mimetypes.html">
+ here</a>. Note that there is currently a problem with Nautilus 1.x
+ with the XML file formats: Nautilus recognizes them as zip files (which is
+ correct), but does not offer a way to override this detection result for
+specific extensions.</font></p>
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+ D. GNOME 2 integration</font></p>
+<p style="margin-bottom: 0cm;"><font size="3">In the upcoming 2.0 release
+ </font>GNOME will probably switch to UTF-8 encoding for the NLS strings in
+ the .desktop file, so you may use the KDE integration files as templates.<br>
+</p>
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+ E. KDE integration<br>
+</font><font size="3"><br>
+</font><font size="3">StarOffice<small><sup>TM</sup></small></font><font size="3">
+ 6.0 comes with a user space KDE 2.x integration that consists of two sets
+of zip files containing the menu integration files and the mime registration
+files. These files contain a bunch of placeholders you will have to replace
+before using the files. You may also think about changing the menu structure
+from being document based to be apllication based for the document based
+structure has the following drawbacks: One sees a document (e.g. Textdocument)
+in the "Open with" list of the context menu of a</font> StarOffice<small><sup>
+TM</sup></small> file and the application launch feedback also names the
+document instead of the application.</p>
+<p style="margin-bottom: 0cm;"><font size="3">To find the files provided
+by </font>StarOffice<small><sup>TM</sup></small><font size="3"> </font><font size="3">
+you will have an OpenOffice.org build tree available. You should find the
+following two sets of zip files in the output tree of a successful OpenOffice
+build:</font><font size="3"> kdeappgroup.zip, kdeappwrite.zip, kdeappcalc.zip,
+kdeappdraw.zip, kdeappimpress.zip (containing the menu .desktop templates)
+and kdeappgroup.zip, kdeappwriter.zip, kdeappcalc.zip, kdeappdraw.zip, kdeappimpress.zip
+(containing the icons and the file type registration files). </font></p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><font size="4">F. Java setup</font></p>
+<p style="margin-bottom: 0cm;">coming soon ..<br>
+</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm; text-decoration: none;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><br>
+ </p>
+
+<p style="margin-bottom: 0cm; text-decoration: none;"><br>
+ </p>
+
+</body>
+</html>
diff --git a/content/installation/how_to_repackage_so.html b/content/installation/how_to_repackage_so.html
new file mode 100644
index 0000000..030a6e7
--- /dev/null
+++ b/content/installation/how_to_repackage_so.html
@@ -0,0 +1,214 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+<head>
+
+ <meta http-equiv="CONTENT-TYPE" content="text/html; charset=iso-8859-1">
+ <title></title>
+
+ <meta name="GENERATOR" content="StarOffice/5.2 (Win32)">
+
+ <meta name="AUTHOR" content="Oliver Bolte">
+
+ <meta name="CREATED" content="20001218;17461754">
+
+ <meta name="CHANGEDBY" content="Ingo Schmidt">
+
+ <meta name="CHANGED" content="20010205;15392152">
+
+ <style>
+ <!--
+ @page { margin: 2cm }
+ -->
+ </style>
+</head>
+ <body>
+
+<p align="Center" style="margin-bottom: 0cm;"><b><font size="5">HowTo repackage
+ an StarOffice<small><small><sup>TM</sup></small></small> installation
+set<br>
+ </font></b><font size="5"><small><small>by <b><a href="mailto:Oliver.Braun@sun.com">
+ Oliver Braun</a></b></small></small><b><br>
+ </b></font></p>
+
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+ Introduction:</font></p>
+
+<p style="margin-bottom: 0cm;"> </p>
+
+<p style="margin-bottom: 0cm;">This HowTo describes the necessary steps to
+ take to be able to make standard unix packages (rpm, pkg, ..) out of
+an StarOffice<small><sup> TM</sup></small> installation set. It does not
+deal with any specific package manager. If you have created a script for
+your favourite package manager and want to share it with others, please
+drop me a <a href="mailto:Oliver.Braun@sun.com?subject=package%20manager%20script">
+ note</a>.</p>
+
+<p style="margin-bottom: 0cm;">The StarOffice<small><sup>TM</sup></small>
+ 6.0 installation on a unix system differs slightly from an OpenOffice.org
+ 641 B/C installation, so if you are looking for instructions for the last
+ one, you should look <a href="how_to_repackage_oo.html">here</a>. </p>
+
+<p style="margin-bottom: 0cm;"> </p>
+
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+ A. Install StarOffice<small><sup>TM</sup></small> on your machine</font></p>
+
+<ol>
+ <li>
+ <p style="margin-bottom: 0cm;">Log into your machine as <b>root</b>. </p>
+ </li>
+ <li>
+ <p style="margin-bottom: 0cm;">Start the setup application with the "-net"
+ option: <b><path-to-office-installation-set>/setup -net &</b><br>
+ </p>
+ </li>
+ <li>
+ <p style="margin-bottom: 0cm;">On the "Select Installation Type" page,
+ select "<b>Custom Installation</b>".</p>
+ <i> </i></li>
+ <li>
+ <p style="margin-bottom: 0cm;">On the "Select StarOffice 6.0 Modules"
+ page open the node "<b>Optional Components</b>" and <br>
+ a) de-select "Adabas Database" for this is not covered by this HowTo
+yet.<br>
+ b) de-select "Java Environment Installation" if you want to detect/select
+ the java version yourself.<br>
+ c) de-select "CDE Integration" (default on Linux) even if you want the
+ integration to be included in your package.<br>
+ d) de-select "GNOME Integration" (default on Solaris) if you want to
+do the GNOME 1.4 integration yourself.<br>
+ e) <b>Linux only</b>: de-select "KDE Integration" if you want to do the
+ KDE 2 integration yourself.<br>
+ </p>
+ </li>
+ <li>
+ <p style="margin-bottom: 0cm;">Choose the directory to install to, e.g.
+ <b>/opt/staroffice6.0</b>, and install.<br>
+ <br>
+ </p>
+ </li>
+
+</ol>
+
+<p style="margin-bottom: 0cm;"><font size="4">B. Create the package file list(s)</font></p>
+
+<p style="margin-bottom: 0cm;"> </p>
+
+<p style="margin-bottom: 0cm;">Before you start to scan the directory tree
+ you should decide if you want to create one single package containing all
+ files or if you prefer two packages, a binary and a language one. The second
+ way has the advantage of saving a lot of disk space if you are going to provide
+ packages for different languages on the same disc.</p>
+
+<p style="margin-bottom: 0cm;">To split the file list into two, you should
+ include all files in <b><path-to-staroffice-root>/program/resource</b>
+ and the <b><path-to-staroffice-root>/share</b> tree into the
+ language package list and the rest into the binary package list.</p>
+
+<p style="margin-bottom: 0cm;">Note: if you don't want a CDE integration at
+all, you can remove the <b><path-to-staroffice-root>/share/cde</b>
+ subtree from your installation before creating the file lists.<br>
+ <br>
+ </p>
+
+<p style="margin-bottom: 0cm;"><font size="4">C. CDE integration</font></p>
+
+<p style="margin-bottom: 0cm;">StarOffice<small><sup>TM</sup></small> supports
+ two different ways to integrate with your CDE: a system wide panel
+integration and a user based fallback. In our senario the user based fallback
+will not work because we have deselected CDE integration during the setup.</p>
+
+<p style="margin-bottom: 0cm;">To include the system wide CDE integration
+ in your package, you should call the <b><path-to-staroffice-root>/share/cde
+ /dtappintegrate</b> script with the parameters <b><path-to-staroffice-root>
+ StarOffice 6.0 en</b> from the post-installation section of your package.
+ Note: when you install StarOffice in a different language than english, you
+ will have to replace "en" with the ISO language code of the language you
+install for ( e.g. "de" for german ). </p>
+
+<p style="margin-bottom: 0cm;">For proper deinstallation, you should invoke
+ <b>/usr/dt/bin/dtappintegrate</b> with the parameters <b>-u -s <path-to-staroffice-root></b>
+ and <b>rm -rf <path-to-staroffice-root>/dt </b>from the pre-deinstallation
+ section of your package.<br>
+ <br>
+ </p>
+
+<p style="margin-bottom: 0cm;"><font size="4">D. GNOME 1.4 integration</font></p>
+
+<p style="margin-bottom: 0cm;"><font size="3">The GNOME 1.4 integration of
+ </font>StarOffice<small><sup>TM</sup></small><font size="3"> consists of
+a set of zip files containing the menu integration files and a small binary
+ that does the user space filetype registration. As you may want the GNOME
+ integration to be system wide, you can only take the corresponding files
+as templates, but have to provide your own set of files.</font></p>
+
+<p style="margin-bottom: 0cm;"><font size="3">To find the files provided by
+</font>StarOffice<small><sup>TM</sup></small><font size="3"> go back to your
+installation set and lookup the following strings in the <b>setup.ins</b>
+ file: group_pngs.zip, writer_pngs.zip, calc_pngs.zip, draw_pngs.zip,
+impress_pngs.zip for the icons and gnomeappgroup.zip, gnomeappwriter.zip,
+gnomeappcalc.zip, gnomeappdraw.zip, gnomeappimpress.zip for the .desktop
+templates. The "PackedName" you will find close to the names stated above
+is the name of the f_xxxx zip file archieve that includes the content of
+the original zip files. You can either rename the files (e.g. f_0531 ->
+ </font><font size="3">group_pngs.zip) or try to unzip the f_xxxx files
+directly.</font></p>
+
+<p style="margin-bottom: 0cm;"><font size="3">If you want to register </font>
+ the StarOffice<small><sup>TM</sup></small><font size="3"> file types, you
+ may will find a list of them <a href="http://framework.openoffice.org/documentation/mimetypes/mimetypes.html">
+ here</a>. Note that there is currently a problem with Nautilus 1.x
+ with the XML file formats: Nautilus recognizes them as zip files (which
+is correct), but does not offer a way to override this detection result
+for specific extensions.</font></p>
+
+<p style="margin-bottom: 0cm;"> </p>
+
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+ E. GNOME 2 integration</font></p>
+
+<p style="margin-bottom: 0cm;"><font size="3">In the upcoming 2.0 release
+ </font>GNOME will probably switch to UTF-8 encoding for the NLS strings
+in the .desktop file, so you may use the KDE integration files as templates.<br>
+ </p>
+
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+ F. KDE integration<br>
+ </font><font size="3"><br>
+ The KDE 2.x integration of StarOffice<small><sup>TM</sup></small> consists
+ of two sets of zip files containing the menu integration files and the mime
+ registration files. These files contain a bunch of placeholders you will
+have to replace before using them. You may also think about changing the menu
+structure from being document based to be application based for the document
+based structure has the following drawbacks: One sees a document (e.g. Textdocument)
+in the "Open with" list of the context menu of a</font> StarOffice<small><sup>
+TM</sup></small> file and the application launch feedback also shows a document
+name instead of an application.</p>
+
+<p style="margin-bottom: 0cm;"><font size="3">To find the files provided by
+</font>StarOffice<small><sup>TM</sup></small><font size="3"> go back to your
+installation set and lookup the following strings in the <b>setup.ins</b>
+ file: kdeappgroup.zip, kdeappwrite.zip, kdeappcalc.zip, kdeappdraw.zip,
+ kdeappimpress.zip for the menu .desktop templates and kdeappgroup.zip, kdeappwriter.zip,
+kdeappcalc.zip, kdeappdraw.zip, kdeappimpress.zip for the icons and the file
+type registration files. The "PackedName" you will find close to the names
+stated above is the name of the f_xxxx zip file archieve that includes the
+content of the original zip files. You can either rename the files (e.g.
+f_0546 -> kdeappgroup.zip) or try to unzip the f_xxxx files directly.</font></p>
+
+<p style="margin-bottom: 0cm;"><br>
+ </p>
+
+<p style="margin-bottom: 0cm;"><font size="4">G. Java setup</font></p>
+
+<p style="margin-bottom: 0cm;">coming soon ..<br>
+ </p>
+
+<p style="margin-bottom: 0cm;"><br>
+ </p>
+
+<p style="margin-bottom: 0cm; text-decoration: none;"><br>
+ </p>
+
+</body>
+</html>
diff --git a/content/installation/how_to_scp_oo.html b/content/installation/how_to_scp_oo.html
new file mode 100644
index 0000000..e003b10
--- /dev/null
+++ b/content/installation/how_to_scp_oo.html
@@ -0,0 +1,576 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Oliver Bolte">
+ <META NAME="CREATED" CONTENT="20001218;17461754">
+ <META NAME="CHANGEDBY" CONTENT="Ingo Schmidt">
+ <META NAME="CHANGED" CONTENT="20010205;15392152">
+ <STYLE>
+ <!--
+ @page { margin: 2cm }
+ -->
+ </STYLE>
+</head>
+<body>
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><B><FONT SIZE=5>The
+scp-project in OpenOffice.org<BR></FONT></B><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; font-weight: medium"><FONT SIZE=4>Introduction:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><SPAN STYLE="font-weight: medium"><FONT SIZE=3>The
+scp project contains the script-particles (scp) for OpenOffice.org.
+This project</FONT></SPAN> produces *.inf (Win) and *.ins (Unx) files
+which are used to direct the setup and the production of installation
+sets with lzip.</P>
+<P STYLE="margin-bottom: 0cm">The scp project directs the whole
+installation process for the OpenOffice.org. Following components are
+supported: Directorys, files, configuration items (for *.xml files),
+registry items (for windows registry), profile items (entries for the
+ini-files), folders, default installation path, help texts for setup,
+cinema text, modules and basic scripts.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>A. How to put a new file
+in the installation set:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<OL>
+ <LI><P STYLE="margin-bottom: 0cm">Add a Gid item (e.g. like
+ GID_FILE_LIB_SFX ) <BR>into the scp/inc/gid.inc file.</P>
+ <P STYLE="margin-bottom: 0cm"></P>
+ <LI><P STYLE="margin-bottom: 0cm">For which project and which
+ setup-module is the new file relevant?</P>
+ <P STYLE="margin-bottom: 0cm">Setup: scp/source/global/setupzip.scp
+ this is for files needed by the setup.</P>
+ <P STYLE="margin-bottom: 0cm">Office: scp/source/office/files.scp
+ </P>
+ <P STYLE="margin-bottom: 0cm">and so on for calc, chart , ...<BR><BR>
+ </P>
+ <LI><P STYLE="margin-bottom: 0cm">a ) Standard filenames like
+ sfx615mi.dll or libsfx615ss.so can be integrated into<BR>the
+ files.scp (for OfficeFAT) with the macros</P>
+ <P STYLE="margin-bottom: 0cm"><BR>STD_LIB_FILE( GID_FILE_LIB_SFX ,
+ sfx )<BR><BR>
+ </P>
+ <P STYLE="margin-bottom: 0cm">or, if the dll needs to be registered
+ in the applicat.rdb:<BR><BR>
+ </P>
+ <P STYLE="margin-bottom: 0cm">STD_UNO_LIB_FILE( GID_FILE_LIB_DLL ,
+ dll)</P>
+ <P STYLE="margin-bottom: 0cm"><BR>Resource files are added
+ with<BR>STD_RES_FILE( GID_FILE_RES_SFX , sfx )</P>
+ <P STYLE="margin-bottom: 0cm"></P>
+ <P STYLE="margin-bottom: 0cm">This macro STD_RES_FILE expands the
+ file name to sfx61501.res for english or sfx61549.res for german.</P>
+ <P STYLE="margin-bottom: 0cm"><BR>b) Filenames whithout SUPD (this
+ is the version number, for example the 615) can be realised by
+ using:</P>
+ <i>
+ <BR>File GID_FILE_LIB_EXAMPLE
+ <P STYLE="margin-bottom: 0cm"> BIN_FILE_BODY;</P>
+ <P STYLE="margin-bottom: 0cm"> Styles = (PACKED);</P>
+ <P STYLE="margin-bottom: 0cm"> Dir = GID_DIR_PROGRAM;</P>
+ <P STYLE="margin-bottom: 0cm"> #ifdef UNX</P>
+ <P STYLE="margin-bottom: 0cm"> Name =
+ "libexample.so";</P>
+ <P STYLE="margin-bottom: 0cm"> #else</P>
+ <P STYLE="margin-bottom: 0cm"> Name =
+ "example.dll";</P>
+ <P STYLE="margin-bottom: 0cm"> #endif</P>
+ <P STYLE="margin-bottom: 0cm"> End<BR><BR> </i> or, if the dll
+ needs to be registered in the applicat.rdb:<BR><BR><i>
+ </P>
+ <P STYLE="margin-bottom: 0cm">File GID_FILE_LIB_EXAMPLE_UNO</P>
+ <P STYLE="margin-bottom: 0cm"> BIN_FILE_BODY;</P>
+ <P STYLE="margin-bottom: 0cm"> Styles =
+ (PACKED,UNO_COMPONENT);</P>
+ <P STYLE="margin-bottom: 0cm"> RegistryID =
+ GID_STARREGISTRY_APPLICAT_RDB;</P>
+ <P STYLE="margin-bottom: 0cm"> Dir =
+ GID_DIR_PROGRAM;</P>
+ <P STYLE="margin-bottom: 0cm"> #ifdef UNX</P>
+ <P STYLE="margin-bottom: 0cm"> Name =
+ "libexample_uno.so";</P>
+ <P STYLE="margin-bottom: 0cm"> #else</P>
+ <P STYLE="margin-bottom: 0cm"> Name =
+ "example_uno.dll";</P>
+ <P STYLE="margin-bottom: 0cm"> #endif</P>
+ <P STYLE="margin-bottom: 0cm"> End <BR><BR><BR>
+ </P>
+ </i>
+ <P STYLE="margin-bottom: 0cm"> c) Archive files as they come from the
+ extras project or any other zip-compressed file<BR> can be included
+ by using following construct:<BR><BR>
+ <i> File GID_FILE_EXTRA_EXAMPLE</P>
+ <P STYLE="margin-bottom: 0cm"> Dir =
+ GID_DIR_EXAMPLE;</P>
+ <P STYLE="margin-bottom: 0cm"> ARCHIVE_TXT_FILE_BODY;</P>
+ <P STYLE="margin-bottom: 0cm"> Name = "example.zip";</P>
+ <P STYLE="margin-bottom: 0cm"> End</P>
+ <P STYLE="margin-bottom: 0cm"><BR>
+ </P></i>
+ <P STYLE="margin-bottom: 0cm"> d) Archive files with countrycode
+ (e.g. 01, 03, 07, ..., 96)</P>
+ <P STYLE="margin-bottom: 0cm"> in the filename (extras project) can
+ be included by using following construct:<BR><BR><i> File
+ GID_FILE_EXTRA_EXAMPLE</P>
+ <P STYLE="margin-bottom: 0cm"> Dir =
+ GID_DIR_EXAMPLE;</P>
+ <P STYLE="margin-bottom: 0cm"> ARCHIVE_TXT_FILE_BODY;</P>
+ <P STYLE="margin-bottom: 0cm"> EXTRA_ALL_LANG(example);</P>
+ <P STYLE="margin-bottom: 0cm"> End</P></i>
+ <P STYLE="margin-bottom: 0cm"> <BR> Please notice, that the macro
+ EXTRA_ALL_LANG(example) expands to</P>
+ <P STYLE="margin-bottom: 0cm"><BR>
+ </P>
+ <P STYLE="margin-bottom: 0cm"> Name (01) = "example01.zip";</P>
+ <P STYLE="margin-bottom: 0cm"> Name (03) = "example03.zip";</P>
+ <P STYLE="margin-bottom: 0cm"> Name (30) = "example30.zip";</P>
+ <P STYLE="margin-bottom: 0cm"> o</P>
+ <P STYLE="margin-bottom: 0cm"> o</P>
+ <P STYLE="margin-bottom: 0cm"> Name (96) = "example96.zip";</P>
+ <P STYLE="margin-bottom: 0cm"></P>
+ <LI><P STYLE="margin-bottom: 0cm">The new file has to be linked to a
+ setup-module. Default is the root-module, meaning that this file
+ will be installed always and cannot be deselected during setup. If
+ the file belongs for example to the Calc-project, add its Gid to the
+ files section of the module in the file
+ scp/source/calc/module_calc.scp.</P>
+ <P STYLE="margin-bottom: 0cm"></P>
+ <LI><P STYLE="margin-bottom: 0cm">Conclusion:</P>
+ <P STYLE="margin-bottom: 0cm">If a new standard file is added to the
+ OpenOffice.org, two scp-files have to be updated:</P>
+ <P STYLE="margin-bottom: 0cm">scp/inc/gid.inc (for the addition of
+ the new GID)</P>
+ <P STYLE="margin-bottom: 0cm">scp/source/files.scp (for the
+ description of the file)</P>
+ <P STYLE="margin-bottom: 0cm"></P>
+</OL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>B. Configurationitems</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Configurationitems are used to add or
+change configuration entries in xml files.</P>
+<P STYLE="margin-bottom: 0cm">There are several important subentries
+like Path, Key, Value, Styles and ModuleID.</P>
+<P STYLE="margin-bottom: 0cm">A typical item looks like following
+example:</P>
+<P STYLE="margin-bottom: 0cm">
+</P><i>
+<P STYLE="margin-bottom: 0cm">ConfigurationItem
+GID_CONFIGURATIONITEM_EXAMPLE</P>
+<P STYLE="margin-bottom: 0cm"> ModuleID = GID_MODULE_SO_ROOT;</P>
+<P STYLE="margin-bottom: 0cm"> Path =
+"org.openoffice.Office.ExampleFile/Filters/draw_SGV_StarDraw_20";</P>
+<P STYLE="margin-bottom: 0cm"> Key = "UIName";</P>
+<P STYLE="margin-bottom: 0cm"> Value = "SGV - StarDraw 2.0";</P>
+<P STYLE="margin-bottom: 0cm"> Styles = (CFG_STRING, CREATE);</P>
+<P STYLE="margin-bottom: 0cm">End</P></i>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Path:</P>
+<P STYLE="margin-bottom: 0cm">The first part of this entry declares
+the filename without extension in this example</P>
+<P STYLE="margin-bottom: 0cm">org.openoffice.Office.ExampleFile.xml
+is the target file. The following part of the entry describes the
+path in the xml file.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Key and Value:</P>
+<P STYLE="margin-bottom: 0cm">Contain the entries in the xml file.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Styles:</P>
+<P STYLE="margin-bottom: 0cm">Defines the type of value:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">CFG_STRING: Value = "A string"</P>
+<P STYLE="margin-bottom: 0cm">CFG_STRINGLIST: Value = a list of
+strings</P>
+<P STYLE="margin-bottom: 0cm">CFG_BOOLEAN: Value = "TRUE"
+or "FALSE"</P>
+<P STYLE="margin-bottom: 0cm">CFG_NUMERIC: Value = 1031</P>
+<P STYLE="margin-bottom: 0cm">CFG_BINARY: Value is binary.</P>
+<P STYLE="margin-bottom: 0cm">CREATE: Creates a new entry in the
+xml file. If this entry exsists in the xml file no action takes
+place.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>C. Profile and
+ProfileItems</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">This part of setup is localized in the
+profile.scp and profile_xxx.scp files (where „xxx“ means
+for example „calc“ for different setup-modules).</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Profile declares the name and directory
+of an ini file. The gid name is needed in the ProfileItem declaration
+as ProfileID parameter. The ProfileItems are the entries in the form
+„Key = Value“ of the ini-files.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm">Profile GID_PROFILE__EXAMPLE_INI</P>
+<P STYLE="margin-bottom: 0cm"> ModuleID = GID_MODULE_EXAMPLE;</P>
+<P STYLE="margin-bottom: 0cm"> Name = "example.ini";</P>
+<P STYLE="margin-bottom: 0cm"> Dir = GID_DIR_EXAMPLE;</P>
+<P STYLE="margin-bottom: 0cm"> Styles = (NETWORK);</P>
+<P STYLE="margin-bottom: 0cm">End</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P></i>
+<P STYLE="margin-bottom: 0cm">Styles:</P>
+<P STYLE="margin-bottom: 0cm">NETWORK : <SPAN STYLE="font-weight: medium">Network
+installation</SPAN></P>
+<P STYLE="margin-bottom: 0cm">WORKSTATION : Workstation installation</P>
+<P STYLE="margin-bottom: 0cm">INSTALL_INFO : Only necessary for the
+install.ini</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm"> ProfileItem GID_PROFILEITEM_EXAMPLE_INI_TEST</P>
+<P STYLE="margin-bottom: 0cm"> ProfileID = GID_PROFILE_EXAMPLE_INI;</P>
+<P STYLE="margin-bottom: 0cm"> ModuleID = GID_MODULE_EXAMPLE;</P>
+<P STYLE="margin-bottom: 0cm"> Order = 2;</P>
+<P STYLE="margin-bottom: 0cm"> Section = "Example";</P>
+<P STYLE="margin-bottom: 0cm"> Key = "test";</P>
+<P STYLE="margin-bottom: 0cm"> Value = "testValue";</P>
+<P STYLE="margin-bottom: 0cm">End</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P></i>
+<P STYLE="margin-bottom: 0cm">ProfileID : GID of the ini file defined
+by Profile</P>
+<P STYLE="margin-bottom: 0cm">ModuleID : Setup-module GID</P>
+<P STYLE="margin-bottom: 0cm">Section : Declaration of the sectioname</P>
+<P STYLE="margin-bottom: 0cm">Order : Numerical order of the entry</P>
+<P STYLE="margin-bottom: 0cm">Key and Value : Contain the content of
+the ini-file entry</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Language dependent Value entries are in
+the correspondent lng files.</P>
+<P STYLE="margin-bottom: 0cm">Several macros are used to handle these
+entries (xx = 01,03,...,96):</P>
+<P STYLE="margin-bottom: 0cm">ALL_LANG_STR_SECTION(str) expands to
+Section(xx) = "str-xx"</P>
+<P STYLE="margin-bottom: 0cm">ALL_LANG_STR_KEY(str) expands to Key
+(xx) = "str"</P>
+<P STYLE="margin-bottom: 0cm">ALL_LANG_STR_VALUE_LNG(ID) expands to</P>
+<P STYLE="margin-bottom: 0cm">Value (01) = "Value text 01";</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Value (96) = "...";</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>when the content of the
+lng file is</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">[STR_VALUE_ID]</P>
+<P STYLE="margin-bottom: 0cm">01 = "Value text 01"</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm">96 = "..."</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">You can use the macros as follows:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm">ProfileItem GID_PROFILEITEM_EXAMPLE_INI_TEST</P>
+<P STYLE="margin-bottom: 0cm"> ProfileID = GID_PROFILE_INSTALL_INI;</P>
+<P STYLE="margin-bottom: 0cm"> ModuleID = GID_MODULE_PRG_IMPRESS_BIN;</P>
+<P STYLE="margin-bottom: 0cm"> Order = 2;</P>
+<P STYLE="margin-bottom: 0cm"> ALL_LANG_STR_SECTION(simpress-Filters);</P>
+<P STYLE="margin-bottom: 0cm"> ALL_LANG_STR_KEY("StarImpress 4.0
+Vorlage");</P>
+<P STYLE="margin-bottom: 0cm"> ALL_LANG_STR_VALUE_LNG(TEMPLATE_STAR_IMPRESS40);</P>
+<P STYLE="margin-bottom: 0cm">End</P></i>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>D. Directories</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>This part of setup is
+localized in the dir.scp and dir_xxx.scp files (where again „xxx“
+means for example „calc“ for different setup-modules).</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm">Directory GID_DIR_EXAMPLE</P>
+<P STYLE="margin-bottom: 0cm"> ParentID = PD_PROGDIR;</P>
+<P STYLE="margin-bottom: 0cm"> DosName = "example";</P>
+<P STYLE="margin-bottom: 0cm"> Styles = (WORKSTATION,
+DELETE_ONLY, CHECK_TIMESTAMP,CREATE);</P>
+<P STYLE="margin-bottom: 0cm">End</P></i>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Styles:</P>
+<P STYLE="margin-bottom: 0cm">WORKSTATION : Create directory on client
+side (Network installation only)</P>
+<P STYLE="margin-bottom: 0cm">CREATE : Create empty directory. If
+setup copies a file into a directory the directory will be
+created automatically.</P>
+<P STYLE="margin-bottom: 0cm">DELETE_ONLY : Setup removes this
+directory during deinstallation
+</P>
+<P STYLE="margin-bottom: 0cm">CHECK_TIMESTAMP : Will be only deleted
+when 'delete all' flag during deinstallation<BR> was set. Usage
+with DELETE_ONLY flag only.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">PD_PROGDIR is predefined as the
+installation path.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>E. Modules</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>This part of setup is
+localized in the module.scp and module_xxx.scp files (and again „xxx“
+means for example „calc“ for different setup-modules).</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Modules are used to
+declare installation components which are composited from files,
+directorys, basic procedures, profileitems, configurationitems. They
+are usally selectable or deselectable in the setup dialog box for
+custom installation.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Module GID_MODULE_EXAMPLE</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Name =
+"Example name";</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Description =
+"Example description"; </FONT>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> ParentID =
+GID_MODULE_PARENT;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Files =
+(GID_FILE_EXAMPLE1,GID_FILE_EXAMPLE2);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Procedures =
+(GID_PROCEDURE_EXAMPLE);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Minimal = YES;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Default = YES;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Styles =
+(HIDDEN_ROOT);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>End</FONT></P></i>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Name: Name of the module.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Description: Description
+of the module.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Minimal: If set to YES,
+this component is part of a minimal installation.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Default: If set to YES,
+this component is part of a standard installation.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Styles: HIDDEN_ROOT: Hide
+the module in the dialog box for custom installation.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> DONT_SELECT_BY_USER: The
+user can't change the selection status of the module.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3><U>Important:</U></FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>To
+switch Profiles, ProfileItems and ConfigurationItems with modules,
+the gid of the module is specified in the
+Profile/ProfileItem/ConfigurationItem ModuleID parameter.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><SPAN STYLE="text-decoration: none"><FONT SIZE=3>To
+switch customs, procedures, files and directories</FONT></SPAN>, the
+gid of these items are specified in</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>the similar Files,Customs,
+Dirs, Procedures parameters of the Module declaration.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>MOD_NAME_DESC(id):</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>The macro MOD_NAME_DESC
+is very usefull, because of the language dependencies of the name and
+description entries. It is using the corresponding module.lng and
+module_xxx.lng files which contain the language dependent strings.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Usage: </FONT>
+</P><i>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Module GID_MODULE_EXAMPLE</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>
+MOD_NAME_DESC(MODULE_EXAMPLE);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> ParentID =
+GID_MODULE_OPTIONAL;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Files =
+(GID_FILE_ZIP_ADDIN,GID_FILE_LIB_ROT,GID_FILE_LIB_DFA);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Procedures =
+(GID_PROCEDURE_EXAMPLE);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Minimal = YES;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Default = YES;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> Styles =
+(HIDDEN_ROOT);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>End</FONT></P></i>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>In this example the id
+MODULE_EXAMPLE expands to the appropriate</FONT> sections<BR>in the
+lng file:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>[STR_NAME_ MODULE_EXAMPLE]</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>01 = "Example"</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>96 = "...."</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>[STR_DESC_ MODULE_EXAMPLE]</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>01 = "Example
+description"</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>96 = "...."</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>The country codes have the
+following meaning:</FONT></P><BR>
+01: English<BR>
+03: Portuguese<BR>
+07: Russian<BR>
+30: Greek<BR>
+31: Dutch<BR>
+33: French<BR>
+34: Spanish<BR>
+39: Italian<BR>
+45: Danish<BR>
+46: Swedish<BR>
+48: Polish<BR>
+49: German<BR>
+55: Spanish (Brasil)<BR>
+81: Japanese<BR>
+82: Korean<BR>
+86: Chinese (simple)<BR>
+88: Chinese (traditional)<BR>
+90: Turkish<BR>
+96: Arabian<BR>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=4>F.
+Procedures</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><SPAN STYLE="text-decoration: none"><FONT SIZE=3>This
+part of setup is localized in the basic.scp and basic_xxx.scp files
+for Windows.</FONT></SPAN></P>
+<P STYLE="margin-bottom: 0cm">For UNIX the appropriate files are
+unxbasic.scp and unxbasic_xxx.scp <FONT SIZE=3> (and of course „xxx“
+means for example „calc“ for different setup-modules).</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>Procedure
+gid_Procedure_Example</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> ProcName =
+"ExampleProcedure";</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>
+ Styles = (STANDALONE, WORKSTATION, INSTALL, BEFORE_INST);</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> Code =
+{Sub ExampleProcedure</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> Basic
+program</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> °</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> End
+Sub</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>
+ };</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>End</FONT></P></i>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>Styles: STANDALONE Execute
+during standalone installation/deinstallation</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> NETWORK : Execute
+during network installation/deinstallation</FONT></P>
+<P STYLE="margin-bottom: 0cm"><SPAN STYLE="text-decoration: none"><FONT SIZE=3> WORKSTATION : Execute
+during workstation installation/deinstallation</FONT></SPAN></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> INSTALL : Execute
+during installation</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> UNINSTALL : Execute
+during deinstallation</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> BEFORE_INST : Execute
+before creating directories/files.</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> AFTER_INST : Execute
+at the end of installation.</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> PRE_SELECT_MODULE : Execute
+before custom select dialog</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> Only
+for one procedure allowed.</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3> LANGUAGE_SELECT_MODULE :
+Only important for checking the setup module selection</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3><U>Important:</U></FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>The
+value of ProcName must be the name of the subroutine given in the
+first line of the code parameter. In this example:
+'ExampleProcedure'.</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>The
+procedure GID must be added to a module by using the Procedures
+parameter in the module declaration (look above).</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; font-weight: medium; text-decoration: none">
+<FONT SIZE=4>G. Setup specifications</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Some setup-variables are available,
+which are replaced by the scp-linker or the setup itself.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Linker-Variables:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">%PRODUCTNAME w<SPAN STYLE="font-weight: medium">ill
+be substituted by the name of the product, here „OpenOffice.org“</SPAN></P>
+<P STYLE="margin-bottom: 0cm">%PRODUCTVERSION w<SPAN STYLE="font-weight: medium">ill
+be substituted by the version of the product, here „6.0“</SPAN></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Setup-Variables:</P>
+<P STYLE="margin-bottom: 0cm"><workpath>, <SPAN STYLE="text-decoration: none"><FONT SIZE=3><progpath>
+</FONT></SPAN> : Office-installation path</P>
+<P STYLE="margin-bottom: 0cm"><productkey> : only for the
+sversion-ini</P>
+<P STYLE="margin-bottom: 0cm"><SPAN STYLE="text-decoration: none"><FONT SIZE=3>Userdata:
+<title>, <email>, <customernr>, <position></FONT></SPAN>,
+<SPAN STYLE="text-decoration: none"><FONT SIZE=3><city>, <fax>,
+<telefonwork></FONT></SPAN>, <SPAN STYLE="text-decoration: none"><FONT SIZE=3><telefonhome>,
+<street>, <company>, <country>, <state>,
+<zip>, <userfirstname></FONT></SPAN>, <SPAN STYLE="text-decoration: none"><FONT SIZE=3><username>,
+<userid>, <sequence_languages></FONT></SPAN></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>The
+following preprocessor directive is available for OpenOffice.org:
+OSL_PRODUCT</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>Tip:
+If you make changes in one of the scp-files, please use the SUPD, for
+example if you include a new file in the files.scp use:</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>#if
+SUPD > 622</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>...
+Here is the file-definition</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>#endif</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/index.html b/content/installation/index.html
new file mode 100644
index 0000000..4c4e1af
--- /dev/null
+++ b/content/installation/index.html
@@ -0,0 +1,475 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 8 (Solaris Sparc)">
+ <META NAME="CREATED" CONTENT="20021022;14462835">
+ <META NAME="CHANGED" CONTENT="20070730;17033000">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<H1>Installation Project</H1>
+<P><B>Project Owner:</B> <A HREF="mailto:ingo.schmidt@sun.com">Ingo
+Schmidt</A>
+</P>
+<P>The Installation project contains several different modules, that
+are necessary to create OpenOffice.org installation sets. This
+includes the description of the installation sets as well as the
+packaging process in which the native installation sets are created.
+Additionally the product definition is part of the Installation
+project. Further modules are added, that contain files required for
+additional functionality for the installation (Download installation
+sets, language packs, Readme-Files, License-Files, ...) and for the
+Office suite (extras, wizards).
+</P>
+<P>The Installation project includes the following:
+</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0in">A platform independent description
+ language in which the composition of an installed product can be
+ described. This description is done in small script particles (scp),
+ that can be linked in different versions to create different
+ products.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in">Tools that analyze and link the
+ script particles and create a script for each product and each
+ platform.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in">A packaging process, that analyzes
+ the product describing scripts and that creates the corresponding
+ installation sets in the format of the native installer.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in">Source code for the setup
+ executable, that can be used to start the installation process on
+ the Windows platform.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in">NSIS code, that is used to create
+ one-file download installation sets for the Windows platform.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in">Java code, for an Installation
+ Wizard with a graphical user interface (GUI). This Wizard is
+ available as preview in OpenOffice.org 2.2.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in">The 'extras'. A collection of all
+ kinds of (binary) files that are needed by various parts of
+ OpenOffice.org.
+ </P>
+</UL>
+<P>Beginning with OpenOffice.org 2.0 the installation process of
+OpenOffice.org was completely changed. In the past, OpenOffice.org
+used its own setup application, that was platform independent. Now
+the installation is done with the platform specific installers:</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0in">Microsoft Installer (MSI) for
+ Windows platforms</P>
+ <LI><P STYLE="margin-bottom: 0in; page-break-before: always">RedHat
+ Package Manager (RPM) for Linux</P>
+ <LI><P>Solaris Packages (PKG) for Solaris</P>
+</UL>
+<P><BR><BR>
+</P>
+<H2>NEW: Java GUI installation wizard</H2>
+<P>Beginning with the release of OpenOffice.org 2.3 a new Java GUI
+installation wizard is included into the products „OpenOffice.org
+with JRE“ (Java Runtime Environment). This installation wizard
+simplifies the installation on Unix platforms. The selection of the
+components or the setting of the destination directory can be done
+with the help of a GUI. Nevertheless the installation is still based
+on native installation packages. Currently RPMs and Solaris packages
+are supported by the Java GUI installer. Of course Java is a
+requirement on your system, if you want to use this installation
+wizard.
+</P>
+<P>If you want to help creating the Java GUI installation wizard,
+your help is very appreciated. It is very important, that the
+installer supports more platforms and package formats than he does
+today. For example Debian packages should be added soon. Furthermore
+testing of this new product is very important, because a lot of
+functionality is added to OpenOffice.org. Of course translation is
+important, that the wizard soon supports all available OpenOffice.org
+languages.
+</P>
+<P>Next to a <A HREF="Java_GUI_Installer_Quick_Guide.odt">short
+introduction</A> into the Java GUI installation wizard and next to
+the <A HREF="Java_GUI_Installer.odt">specification</A>, there are
+also installation sets of an OpenOffice.org 2.2 available, that
+contain this installation wizard as preview. Please feel free to test
+this new installation process. Every feedback and every help is very
+appreciated. If you have downloaded this installation sets, read the
+<A HREF="Java_GUI_Installer_Quick_Guide.odt">Quick Guide</A> to learn
+more about the Installation Wizard. Currently installation sets are
+available for the RPM installation on Linux and for the installation
+of Solaris packages on Solaris Sparc and Solaris x86.
+</P>
+<P>
+Test the new JavaFX download installer <A HREF="testarea/install/index.html">here</A>.
+</P>
+<H2>ToDo List</H2>
+<P>In the installation project, there are several places, where you
+can help to improve OpenOffice.org. The installation project covers
+the complete section from finding the files in the solver until they
+are located on the user's hard disc. This means packaging of
+intallation sets, supporting as many package formats as possible and
+then taking care of a successful and convenient installation. If you
+have more ideas, than listed below, please do not hesitate to contact
+us.
+</P>
+<UL>
+ <LI><P STYLE="margin-bottom: 0in">The new Java GUI installation will
+ be part of OpenOffice.org 2.3 with JRE. For this installation
+ wizard, help is required for the following tasks:
+ </P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0in">Adding support of additional
+ package formats to the Java GUI Installation Wizard.</P>
+ <LI><P STYLE="margin-bottom: 0in">Testing of the new Java GUI
+ Installation Wizard, so that we can introduce it with only few
+ problems left.</P>
+ </UL>
+ <LI><P>It is also always important, to increase the number of
+ platforms, on which OpenOffice.org 2.x can be installed natively.
+ Alternatively it can be useful to offer alternative installation
+ processes, if native installers are not desired.
+ </P>
+ <LI><P>Sometimes it is necessary to think about new processes during
+ packaging. Is it an alternative to use DeltaRPMs for smaller and
+ easier update packages on Linux (RPM)? And how about using "WIX"
+ (http://sourceforge.net/projects/wix), to create the OpenOffice.org
+ msi database?
+ </P>
+ <LI><P>We are always looking for feedback, to be better informed
+ about your packaging and installation experience. If you want to
+ give us your feedback, please do not hesitate to do so.
+ </P>
+</UL>
+<P><BR><BR>
+</P>
+<H2>Documentation and Resources</H2><A NAME="doc"></A>
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=4 CELLSPACING=0 BGCOLOR="#ffffff">
+ <COL WIDTH=64*>
+ <COL WIDTH=162*>
+ <COL WIDTH=31*>
+ <TR>
+ <TD COLSPAN=3 WIDTH=100% BGCOLOR="#00315a">
+ <P ALIGN=CENTER><FONT COLOR="#ffffff"><FONT FACE="arial, helvetica"><FONT SIZE=2><B>Documentation
+ and Resources</B></FONT></FONT></FONT></P>
+ </TD>
+ </TR>
+ <TR>
+ <TH WIDTH=25% BGCOLOR="#99ccff">
+ <P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="arial, helvetica"><FONT SIZE=2><B>Document</B></FONT></FONT></FONT></P>
+ </TH>
+ <TH WIDTH=63% BGCOLOR="#99ccff">
+ <P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="arial, helvetica"><FONT SIZE=2><B>Summary</B></FONT></FONT></FONT></P>
+ </TH>
+ <TH WIDTH=12% BGCOLOR="#99ccff">
+ <P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="arial, helvetica"><FONT SIZE=2><B>Format
+ and Size</B></FONT></FONT></FONT></P>
+ </TH>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=25% BGCOLOR="#f0f0f0">
+ <P><A HREF="how_to_repackage_oo.html">Howto repackage OOo</A></P>
+ </TD>
+ <TD WIDTH=63% BGCOLOR="#f0f0f0">
+ <P>This document describe how to create a standard unix package
+ out of an OpenOffice.org installation set</P>
+ </TD>
+ <TD WIDTH=12% BGCOLOR="#f0f0f0">
+ <P>HTML, ca. 8 kb</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=25% BGCOLOR="#f0f0f0">
+ <P><A HREF="how_to_repackage_so.html">Howto repackage SO/SS</A></P>
+ </TD>
+ <TD WIDTH=63% BGCOLOR="#f0f0f0">
+ <P>This document describe how to create a standard unix package
+ out of a StarOffice/StarSuite installation set</P>
+ </TD>
+ <TD WIDTH=12% BGCOLOR="#f0f0f0">
+ <P>HTML, ca. 11 kb</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=25% BGCOLOR="#f0f0f0">
+ <P><A HREF="how_to_create_native_installer.html">Howto Create
+ Native Installer</A></P>
+ </TD>
+ <TD WIDTH=63% BGCOLOR="#f0f0f0">
+ <P>This document describes how to create native installation sets
+ for OpenOffice.org 2.0.</P>
+ <P>The EPM patch can be downloaded <A HREF="epm-3.7.patch">here</A>.</P>
+ </TD>
+ <TD WIDTH=12% BGCOLOR="#f0f0f0">
+ <P>HTML, ca. 11 kb</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=25% BGCOLOR="#f0f0f0">
+ <P><A HREF="01RESPONSE_SO52_final_rev2.pdf">01RESPONSE_SO52_final_rev2.pdf</A></P>
+ </TD>
+ <TD WIDTH=63% BGCOLOR="#f0f0f0">
+ <P>This document describe how to install OpenOffice.org 1.x
+ without any user interaction via a response file</P>
+ </TD>
+ <TD WIDTH=12% BGCOLOR="#f0f0f0">
+ <P>PDF, ca. 244 kb</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=25% BGCOLOR="#f0f0f0">
+ <P><A HREF="Java_GUI_Installer_Quick_Guide.odt">Java GUI Installer
+ Quick Guide</A></P>
+ </TD>
+ <TD WIDTH=63% BGCOLOR="#f0f0f0">
+ <P>The Java GUI Installer Quick Guide shortly describes the
+ advantages and the usage of the new Java GUI Installer</P>
+ </TD>
+ <TD WIDTH=12% BGCOLOR="#f0f0f0">
+ <P>HTML, ca. 11 kb</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=25% BGCOLOR="#f0f0f0">
+ <P><A HREF="Java_GUI_Installer.odt">Java GUI Installer
+ Specification</A></P>
+ </TD>
+ <TD WIDTH=63% BGCOLOR="#f0f0f0">
+ <P>The specification of the Java GUI Installer. Not final yet.</P>
+ </TD>
+ <TD WIDTH=12% BGCOLOR="#f0f0f0">
+ <P>HTML, ca. 11 kb</P>
+ </TD>
+ </TR>
+</TABLE>
+<P><BR><BR>
+</P>
+<H2>Installation CVS Modules</H2>
+<P STYLE="margin-bottom: 0in"><BR>
+</P>
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=4 CELLSPACING=0 BGCOLOR="#ffffff">
+ <COL WIDTH=44*>
+ <COL WIDTH=212*>
+ <TR>
+ <TD COLSPAN=2 WIDTH=100% BGCOLOR="#00315a">
+ <P ALIGN=CENTER><FONT COLOR="#ffffff"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Modules
+ in Installation Project</B> </FONT></FONT></FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TH WIDTH=17% BGCOLOR="#99ccff">
+ <P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Module
+ </B></FONT></FONT></FONT>
+ </P>
+ </TH>
+ <TH WIDTH=83% BGCOLOR="#99ccff">
+ <P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Function
+ </B></FONT></FONT></FONT>
+ </P>
+ </TH>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17% BGCOLOR="#f0f0f0">
+ <P><CODE>scp2</CODE></P>
+ </TD>
+ <TD WIDTH=83% BGCOLOR="#f0f0f0">
+ <P>The module scp2 contains the script particle, which can be used
+ to define installation set. Usually a <CODE>.scp</CODE> source
+ file summarizes all script objects which are necessary for special
+ functionality. The individual <CODE>scp</CODE> files can be merged
+ into different installation scripts during the link processes. For
+ a description of the script language in the scp2-project <A HREF="How_to_scp_in_ooo.html">click
+ here</A>.
+ </P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17% BGCOLOR="#f0f0f0">
+ <P><CODE>solenv</CODE></P>
+ </TD>
+ <TD WIDTH=83% BGCOLOR="#f0f0f0">
+ <P>The module solenv contains the code, that is required for
+ creating setup scripts from the script particles defined in scp2
+ and also the code that is required to create native installation
+ sets from the setup scripts.</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17% BGCOLOR="#f0f0f0">
+ <P><CODE>instsetoo_native</CODE></P>
+ </TD>
+ <TD WIDTH=83% BGCOLOR="#f0f0f0">
+ <P>instsetoo_native is the module, in which the products are
+ defined and in which the installation sets are created.
+ </P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17% BGCOLOR="#f0f0f0">
+ <P><CODE>setup_native</CODE></P>
+ </TD>
+ <TD WIDTH=83% BGCOLOR="#f0f0f0">
+ <P>A module for native installer specific code. This includes for
+ Windows the Windows Installer custom actions and the NSIS code for
+ download installation sets. For Unixes this module contains
+ different shellscripts, that are required for download
+ installation sets or for the installation of language packs.</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17% BGCOLOR="#f0f0f0">
+ <P><CODE>desktop</CODE></P>
+ </TD>
+ <TD WIDTH=83% BGCOLOR="#f0f0f0">
+ <P>The desktop module contains the implementation of the setup
+ executable for the Windows platform. The setup.exe is used to
+ search for the Windows Installer service, install this service if
+ necessary and start the installation with the correct language.
+ The code for the setup executable is located in the directory
+ desktop/win32/source/setup .
+ </P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17% BGCOLOR="#f0f0f0">
+ <P><CODE>readlicense</CODE></P>
+ </TD>
+ <TD WIDTH=83% BGCOLOR="#f0f0f0">
+ <P>Readme and license files.
+ </P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17% BGCOLOR="#f0f0f0">
+ <P><CODE>extras</CODE></P>
+ </TD>
+ <TD WIDTH=83% BGCOLOR="#f0f0f0">
+ <P>Contains all non-code files that are vital for OpenOffice.org
+ to run properly.
+ </P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0in"><CODE>autotext</CODE> contains
+ text blocks that are used by various wizards.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in"><CODE>database</CODE> contains
+ the bibliography database of OpenOffice.org.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in"><CODE>gallery</CODE> contains
+ clipart that is needed by OpenOffice.org's main functionality.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in"><CODE>misc_config</CODE> holds
+ miscellanious preferences files.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in">The <CODE>palettes</CODE> of
+ OpenOffice (colors, gradients, etc...) are found in this module.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in">Files responsible for the OS
+ file type recognition are found within <CODE>shellnew.</CODE>
+ </P>
+ <LI><P STYLE="margin-bottom: 0in">The symbols of OpenOffice.org
+ (toolbox icons) are found in this module.
+ </P>
+ <LI><P STYLE="margin-bottom: 0in">document <CODE>templates</CODE>
+ that are needed for the wizards are found here.
+ </P>
+ <LI><P>User dictionary are stored in <CODE>wordbook</CODE>.
+ </P>
+ </UL>
+ <P>Files not vital for OpenOffice.org's main functionality like
+ sample documents, other document templates and additional clipart
+ are not stored in the module 'extras'. They can be copied right
+ out of a StarOffice installation. However it may be possible to
+ set up dedicated sub modules if commiters wish to contribute
+ examples of these file types.
+ </P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17% BGCOLOR="#f0f0f0">
+ <P><CODE>wizards</CODE></P>
+ </TD>
+ <TD WIDTH=83% BGCOLOR="#f0f0f0">
+ <P>Basic macros and libraries for the autopilots such as the
+ wizard for importing foreign file type documents.
+ </P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=17% BGCOLOR="#f0f0f0">
+ <P><CODE>javainstaller2</CODE></P>
+ </TD>
+ <TD WIDTH=83% BGCOLOR="#f0f0f0">
+ <P>The module javainstaller2 contains the code for a Java GUI
+ installation wizard. This wizard is available in a preview in
+ OpenOffice.org 2.2. It is planned to be official part of
+ OpenOffice.org in version 2.3. The installation wizard simplifies
+ the installation process for platforms, on which no GUI installer
+ is available. A quick guide to the Java GUI installer can be found
+ at <A HREF="Java_GUI_Installer_Quick_Guide.odt">Java GUI Installer
+ Quick Guide</A>. The specification of the Java GUI installation
+ wizard is also available: <A HREF="Java_GUI_Installer.odt">Java
+ GUI Installer</A>.
+ </P>
+ </TD>
+ </TR>
+</TABLE>
+<P><BR><BR>
+</P>
+<H2>Proposals</H2>
+<TABLE WIDTH=100% BORDER=0 CELLPADDING=10 CELLSPACING=0 BGCOLOR="#ffffff">
+ <COL WIDTH=95*>
+ <COL WIDTH=96*>
+ <COL WIDTH=59*>
+ <COL WIDTH=6*>
+ <TR>
+ <TD COLSPAN=4 WIDTH=100% BGCOLOR="#00315a">
+ <P ALIGN=CENTER><FONT COLOR="#ffffff"><!-- 1. row: "Documentation"
+ 100% with
+ --><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Proposals<!-- 2. row: "Title" & "Description" & "Author"
+ 40/40/20% for every column
+ -->
+ </B></FONT></FONT></FONT>
+ </P>
+ </TD>
+ </TR>
+ <TR>
+ <TD WIDTH=37% BGCOLOR="#99ccff">
+ <P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Title
+ </B></FONT></FONT></FONT>
+ </P>
+ </TD>
+ <TD WIDTH=38% BGCOLOR="#99ccff">
+ <P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Description
+ </B></FONT></FONT></FONT>
+ </P>
+ </TD>
+ <TD WIDTH=23% BGCOLOR="#99ccff">
+ <P ALIGN=CENTER><FONT COLOR="#00315a"><FONT FACE="Arial, Helvetica"><FONT SIZE=2><B>Author<!-- 3. row: first content line
+ dialog proposal
+ --><!-- 4. row: second content line
+ system integration
+ --><!-- Standard_Printer --><!-- HelpAgent --><!-- Setup Features -->
+ </B></FONT></FONT></FONT>
+ </P>
+ </TD>
+ <TD WIDTH=2% VALIGN=TOP></TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=37% BGCOLOR="#f0f0f0">
+ <P ALIGN=LEFT><BR>
+ </P>
+ </TD>
+ <TD WIDTH=38% BGCOLOR="#f0f0f0">
+ <P ALIGN=LEFT><BR>
+ </P>
+ </TD>
+ <TD WIDTH=23% BGCOLOR="#f0f0f0"></TD>
+ <TD WIDTH=2%></TD>
+ </TR>
+</TABLE>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/automatical_assignments.html b/content/installation/pics/automatical_assignments.html
new file mode 100644
index 0000000..f0c1391
--- /dev/null
+++ b/content/installation/pics/automatical_assignments.html
@@ -0,0 +1,56 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040205;16560327">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT><SPAN STYLE="font-weight: medium"><FONT SIZE=6><FONT FACE="Verdana, sans-serif">Automatical
+assignments of global IDs to modules</FONT></FONT></SPAN></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The scp linker automatically
+optimizes the setup script to reduce the efforts needed in scp files:</FONT></P>
+<UL>
+ <LI><P><FONT FACE="Verdana, sans-serif"><B>Global IDs that are not
+ assigned to a module, are automatically assigned to the root module.</B>
+ </FONT>
+ </P>
+ <LI><P><FONT FACE="Verdana, sans-serif"><B>Global IDs that are
+ assigned to modules, but are not defined, are automatically removed
+ from modules.</B></FONT></P>
+</UL>
+<P><FONT FACE="Verdana, sans-serif">This is only relevant for
+Directories, Files, Customs and Procedures, because all other items
+do not belong to modules (Installation, HelpText, ...) or have to
+contain a ModuleID in their definition block (ProfileItem,
+RegistryItem, ...) .</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Example: </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">If you only define a file and do
+not include it into the list ( Files = ( ... ); ) of a module, the
+file is automatically added to the root module. Therefore you only
+have to edit one scp file. </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The second case is not less
+important. If you define in a module definition a file list like</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Files = (gid_File_Only_Windows,
+gid_File_Only_Linux, gid_File_Only_Solaris);</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">you do not need to write any
+platform dependencies inside this definition (take care of the
+filenames ;-) )</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">If you build a Windows script, in
+which the definitions of gid_File_Only_Linux and
+gid_File_Only_Solaris do not occur, you do not have to take care of
+the module assignments. The scplinker automatically removes these two
+assignments and writes</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Files = (gid_File_Only_Windows);</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">into the setup script in the
+installation set. </FONT>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_directory.html b/content/installation/pics/scpitem_directory.html
new file mode 100644
index 0000000..826d4fa
--- /dev/null
+++ b/content/installation/pics/scpitem_directory.html
@@ -0,0 +1,81 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040205;14570335">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a Directory </FONT></FONT>
+</P>
+<P><BR><BR>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+keyword for a directory definition is <B>Directory</B>. A global ID
+of a directory should begin with <B>gid_Dir </B>. Directories have to
+be assigned to modules in the definition block of the module. If a
+directory is not assigned to any module, it is automatically assigned
+to the root module by the scplinker. A typical definition of a
+directory in the scp projects looks like:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Directory
+gid_Dir_Autotext<BR>ParentID = gid_Dir_Share;<BR>DosName =
+"autotext";<BR>End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Directory
+gid_Dir_Share_Autocorr<BR>ParentID = gid_Dir_Share;<BR>DosName =
+"autocorr";<BR>Styles = (CREATE);<BR>End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">As
+you can see, the definition of a directory is very simple. A
+directory has a name (DosName) and a parent. Every directory has a
+parent, resulting in a directory tree. For the most directories, the
+ParentID is a global ID, which is defined in the script before. Some
+directories of course have to be defined by the setup. The most
+important is the directory:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">PREDEFINED_PROGDIR
+</FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">which
+is for example used in the definition:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Directory
+gid_Dir_Program<BR>ParentID = PREDEFINED_PROGDIR;<BR>DosName =
+"program";<BR>End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+directory program is created below the Office installation root. And
+this is described by the PREDEFINED_PROGDIR, which has to be found by
+the setup. By the way, the PREDEFINED_PROGDIR is defined by the user,
+during the installation process. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Further
+predefined directories are:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>PREDEFINED_HOMEDIR
+</B>: The user's home directory</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>PREDEFINED_CONFIGDIR</B>:
+The system's configuration directory</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>PREDEFINED_OSSHELLNEWDIR</B>:
+The shellnew directory for Windows</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>PREDEFINED_OSSYSTEMFONTDIR</B>:
+The system font directory</FONT></P>
+<P><BR><BR>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">A
+directory is created, if it is necessary to create it. This means:
+For example we take a file gid_File_A, that belongs to gid_Module_B,
+and has to be installed into directory gid_Dir_C. If the module is
+selected in the user defined installation, the file has to be
+installed. Then it is necessary for the setup, to create the
+directory gid_Dir_C. If the module is not selected, the file has not
+to be installed and, if there is no other file in gid_Dir_C, this
+gid_Dir_C must no be created. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Some
+directories have to be created empty. As in the example above the
+directory gid_Dir_Share_Autocorr has the flag <B>CREATE</B>. This
+flag means, that the directory shall be created, even though there is
+no file in it.</FONT></P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_file.html b/content/installation/pics/scpitem_file.html
new file mode 100644
index 0000000..f3491e7
--- /dev/null
+++ b/content/installation/pics/scpitem_file.html
@@ -0,0 +1,156 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040205;14595847">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a File </FONT></FONT>
+</P>
+<P><BR><BR>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+keyword for a file definition is <B>File</B>. A global ID of a file
+should begin with <B>gid_File_ </B>. Files have to be assigned to
+modules in the definition block of the module. If a file is not
+assigned to any module, it is automatically assigned to the root
+module by the scplinker. A typical definition of a file in the scp
+projects looks like:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">File
+gid_File_Lib_Dbp<BR>BIN_FILE_BODY;<BR>Name = LIBNAME(dbp);<BR>Dir =
+gid_Dir_Program;<BR>Styles = (PACKED, UNO_COMPONENT);<BR>RegistryID =
+gid_Starregistry_Applicat_Rdb;<BR>End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">This
+definition describes the library dbp. The macro LIBNAME is defined in
+the included file macros.inc. You find there some very important
+macro definitions:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">#ifdef
+UNX<BR>#define LIBNAME(name)
+STRING(CONCAT5(lib,name,OFFICEUPD,DLLSUFFIX,.so))<BR>#define
+LIBSHORTNAME(name) STRING(CONCAT4(lib,name,DLLSUFFIX,.so))<BR>#define
+LIBVERYSHORTNAME(name) STRING(CONCAT3(lib,name,.so))<BR>#define
+FILTER_LIBNAME(name) LIBNAME(name)<BR>#define EXENAME(name)
+STRING(name)<BR>#define PROFILENAME(name)
+STRING(CONCAT2(name,rc))<BR>#else<BR>#define LIBNAME(name)
+STRING(CONCAT4(name,OFFICEUPD,DLLSUFFIX,.dll))<BR>#define
+LIBSHORTNAME(name) STRING(CONCAT3(name,DLLSUFFIX,.dll))<BR>#define
+LIBVERYSHORTNAME(name) STRING(CONCAT2(name,.dll))<BR>#define
+FILTER_LIBNAME(name) LIBNAME(name)<BR>#define EXENAME(name)
+STRING(CONCAT2(name,.exe))<BR>#define PROFILENAME(name)
+STRING(CONCAT2(name,.ini))<BR>#endif</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">You
+can see, that for many different kinds of names exist different
+macros. <B>LIBNAME(dbp)</B> will be expanded for Solaris-Sparc in a
+src641 to <B>libdbp641ss.so</B>, but for Windows to <B>dbp641mi.dll</B>.
+If there is a language dependent name, like for resource files, there
+are other macro definitions: </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">File
+gid_File_Res_Dba<BR>TXT_FILE_BODY;<BR>RESFILE_ALL_LANG(dba);<BR>Dir =
+gid_Dir_Resource;<BR>Styles = (PACKED);</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">RESFILE_ALL_LANG
+is also defined in macros.inc. You find there:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">#define
+RESFILE_ALL_LANG(name) \<BR>Name (01) = RESFILENAME(name,01); \<BR>Name
+(03) = RESFILENAME(name,03); \<BR>Name (07) = RESFILENAME(name,07);
+\<BR>Name (30) = RESFILENAME(name,30); \<BR>Name (31) =
+RESFILENAME(name,31); \<BR>Name (33) = RESFILENAME(name,33); \<BR>Name
+(34) = RESFILENAME(name,34); \<BR>Name (35) = RESFILENAME(name,35);
+\<BR>Name (37) = RESFILENAME(name,37); \<BR>Name (39) =
+RESFILENAME(name,39); \<BR>Name (45) = RESFILENAME(name,45); \<BR>Name
+(46) = RESFILENAME(name,46); \<BR>Name (48) = RESFILENAME(name,48);
+\<BR>Name (49) = RESFILENAME(name,49); \<BR>Name (81) =
+RESFILENAME(name,81); \<BR>Name (82) = RESFILENAME(name,82); \<BR>Name
+(86) = RESFILENAME(name,86); \<BR>Name (88) = RESFILENAME(name,88);
+\<BR>Name (90) = RESFILENAME(name,90); \<BR>Name (96) =
+RESFILENAME(name,96); \<BR>Name (99) = RESFILENAME(name,99)</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">and
+also RESFILENAME is a macro defined in macros.inc:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">#define
+RESFILENAME(name,lang) STRING(CONCAT4(name,OFFICEUPD,lang,.res))</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">At
+the moment there are many macros for different file names, that is
+would be too much, to desribe here. Take a look into the macros.inc
+file, and you will find the macro you need. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Back
+to the definition of File gid_File_Lib_Dbp. Another entry in the
+definition block defines the directory. In this case the library
+shall be intalled into gid_Dir_Program. As you can see, this is also
+a global ID, which has to be defined in the script before the
+definition of this file. You see, everything in the setup script is
+defined in these definition blocks. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+next two lines in the definition of gid_File_Lib_Dbp are important
+for registering the services inside this library to the internal
+registry:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Styles
+= (PACKED, UNO_COMPONENT);<BR>RegistryID =
+gid_Starregistry_Applicat_Rdb;<BR></FONT><BR><BR>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+second line describes, in which internal registry file, the service
+shall be registered. This is the global ID
+gid_Starregistry_Applicat_Rdb, which again has to be defined in this
+setup script, before the definition of this file. That there is a
+service to register, shows the style UNO_COMPONENT. All libraries,
+that want to register a service need this flag. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">At
+the moment there are many flags for files and very often new flags
+are created or some that are no longer needed are deleted. Here a
+short description of the available flags:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>PACKED</B>:
+This is the mostly used flag. It says, that the file is zipped into
+the file f_xyz in the installation set.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>ARCHIVE</B>:
+This is important for files, that are already zipped in the output
+tree. In the packing process, these files must not be zipped once
+more, therefore they have to get the flag ARCHIVE.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>UNO_COMPONENT</B>:
+This flag is important for all libraries, that want to register a
+service. If this flag is set, you also have to define the RegistryID,
+as shown in the example above.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>FONT</B>:
+This flag marks all font files.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>DONT_DELETE</B>:
+This flag shows, that the file is not deleted, if the Office
+installation is removed. This is for example important for all fonts.
+</FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>FONT_WARN_IF_EXISTS</B>:
+Also a typical font flag. If there is already a font defined with the
+same name, a dialog box must appear during setup, to ask the user,
+whether he wants to overwrite the existing font. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>OVERWRITE</B>:
+Overwrite the file, if it already exists, without warning. For
+example the Shellnew files have this flag.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>DONT_OVERWRITE</B>:
+Do not overwrite the file, if it already exists, for example in one
+of the Windows system directories.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>DELETE_ONLY</B>:
+This is important for a deinstallation of the Office. This file
+definition block describes a file, that does not exist during setup,
+but is created by the Office. This flag shows, that this new created
+file, shall also be deleted during the deinstallation. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>CHECK_TIMESTAMP</B>:
+This flag is also only important for the deinstallation and the
+DELETE_ONLY flag. If this flag is set, the installation date is also
+controlled before deleting the file.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><B>PATCH</B>:
+Files containing this flag are included into a patch product. For more information please look at
+<A HREF="understanding_the_patch_flag.html">Understanding the PATCH flag</A>.
+</P>
+<P STYLE="font-weight: medium"><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_folder.html b/content/installation/pics/scpitem_folder.html
new file mode 100644
index 0000000..74ae48c
--- /dev/null
+++ b/content/installation/pics/scpitem_folder.html
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040205;15022914">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a Folder </FONT></FONT>
+</P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The keyword for a folder
+definition is <B>Folder</B>. A global ID of a folder should begin
+with <B>gid_Folder</B>. Folders are global and cannot be assigned to
+modules. Folders represent directories in the Windows system, making
+possible that the office can be started via the Windows start menu.
+Folders are during the setup process filled with <A HREF="scpitem_folderitem.html">FolderItems</A>.
+A typical definition of a folder in the scp projects looks like:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Folder
+gid_Folder_Staroffice<BR>Name = "%PRODUCTNAME
+%PRODUCTVERSION";<BR>End</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">As you can see, the definition of
+a folder needs only a name. In this case this is %PRODUCTNAME and
+%PRODUCTVERSION, which are defined in the <A HREF="scpitem_installation.html">Installation</A>
+object. Therefore the Folder name will be for example OpenOffice.org
+2.0.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Only
+if at least one FolderItem exist, the Folder will be created. The
+Folder is realized by the setup as directory in the Windows system,
+for example below the start menu directory. </FONT>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_folderitem.html b/content/installation/pics/scpitem_folderitem.html
new file mode 100644
index 0000000..bb18457
--- /dev/null
+++ b/content/installation/pics/scpitem_folderitem.html
@@ -0,0 +1,43 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040205;15055633">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a FolderItem</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The keyword for a FolderItem
+definition is <B>FolderItem</B>. A global ID of a <FONT FACE="Verdana, sans-serif">FolderItem
+should</FONT> begin with <B>gid_Folderitem. </B><FONT FACE="Verdana, sans-serif">FolderItems</FONT>
+contain the information about the assigned module in their definition
+block. <FONT FACE="Verdana, sans-serif">FolderItems </FONT>represent
+entries into <A HREF="scpitem_folder.html">Folders</A>, which exist
+in the Windows system, for example the Windows start menu folder. A
+typical definition of a <FONT FACE="Verdana, sans-serif">FolderItem
+</FONT>in the scp projects looks like:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">FolderItem
+gid_Folderitem_Staroffice_Setup<BR>ModuleID = gid_Module_Abc<BR>Name
+= "setup";<BR>FolderID = gid_Folder_Staroffice;<BR>FileID =
+gid_File_Bin_Setup;<BR>IconFile = gid_File_Bin_Setup;<BR>IconID =
+15;<BR>Parameter = ".uno:NewDoc";<BR>End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+definition of a FolderItem cotains some different entries. The
+FolderItem needs a name, which is after the installation visible in
+the Windows start menu folder. Therefore this name often has to be
+localized. Of course a FolderItem has to know, to which Folder it
+belongs. Every FolderItem is a link to a file, therefore the FileID
+has to be defined. In this case this is the setup file.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+FolderItem is realized as link to the file assigned to the FileID in
+the directory, that is specified as FolderID.</FONT></P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_installation.html b/content/installation/pics/scpitem_installation.html
new file mode 100644
index 0000000..1ad18cf
--- /dev/null
+++ b/content/installation/pics/scpitem_installation.html
@@ -0,0 +1,39 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 8 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20070730;16434200">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of Installation </FONT></FONT>
+</P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The keyword for the Installation
+block definition is <B>Installation</B>. A global ID of a
+Installation should with <B>gid_Installation</B>. Installation
+definitions cannot be assigned to modules, they are global. The
+Installation block is the first block in each setup script. There is
+exact one Installation block in each setup script. In this block some
+important global values are assigned. A typical definition of a n
+Installation block in the scp projects looks like:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Installation
+gid_Installation<BR>ProductName = "OpenOffice.org";<BR>ProductVersion
+= ''680'';<BR>DefaultDestPath =
+"<winprogpath>\%PRODUCTNAME%PRODUCTVERSION";<BR>End</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><SPAN STYLE="font-weight: medium">In
+this Installation object the variable ProductName is set to
+OpenOffice.org and ProductVersion is set to 680. Therefore the
+variables %PRODUCTNAME and %PRODUCTVERSION will contain these values.
+The DefaultDestPath is shown the user during the setup.</SPAN></FONT></P>
+<P><BR><BR>
+</P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_mergemodule.html b/content/installation/pics/scpitem_mergemodule.html
new file mode 100755
index 0000000..7b45b1c
--- /dev/null
+++ b/content/installation/pics/scpitem_mergemodule.html
@@ -0,0 +1,54 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 8 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20070730;16591800">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a MergeModule</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The keyword for a definition of a
+Microsoft merge module is
+</FONT><FONT FACE="Verdana, sans-serif"><B>MergeModule</B></FONT><FONT FACE="Verdana, sans-serif">.
+A global ID of a MergeModule should begin with
+</FONT><FONT FACE="Verdana, sans-serif"><B>gid_Mergemodule</B></FONT><FONT FACE="Verdana, sans-serif">.
+MergeModules are not assigned to modules defined in the scp project. But for the merge process
+it is necessary, that the merge module knows the directory and the feature (in Windows Installer terminology)
+under which it is integrated into the Windows Installer database. Additionally the name of the cabinet file
+has to be determined, because the cabinet file, that is included into in the msm file, always has to have the same
+specific name(MergeModule.CABinet).Therefore the definition of a merge module in scp project is straightforward. An example
+definition of a Microsoft VC80 runtime merge module looks like:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+<SPAN STYLE="font-weight: medium">
+MergeModule gid_Mergemodule_Microsoft_Vc80_Crt_X86
+<BR>Name = "Microsoft_VC80_CRT_x86.msm";
+<BR>Cabfilename = "openofficeorg-vc80crt.cab";
+<BR>Feature = "gm_Root";
+<BR>Rootdir = "TARGETDIR";
+<BR>End</SPAN></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+<SPAN STYLE="font-weight: medium">
+The definition of a MergeModule requires a name, that is the name of
+the msm file. This file has to be located into one of the include pathes
+that are defined in the cvs module instsetoo_native/util/openoffice.lst. There
+the file has to be found during packaging process.
+The defined Cabfilename is used in that way, that after successful packaging process
+a cabinet file with this name can be found next to the msi database.
+Feature and Rootdir are required, because the merge process has to know,
+under which directory and under which feature the content of the msm file has
+to be integrated into the msi database. For the Rootdir the standard value is
+"TARGETDIR", which is the correct choice in most cases.
+The Feature is the installation unit that can be selected or deselected during
+installation process. In most cases "gm_Root" is a good choice, so that
+the content of the msm file cannot be deselected during installation process.
+</SPAN></FONT></P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_module.html b/content/installation/pics/scpitem_module.html
new file mode 100644
index 0000000..ba41096
--- /dev/null
+++ b/content/installation/pics/scpitem_module.html
@@ -0,0 +1,124 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 8 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20070730;16465100">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a Module </FONT></FONT>
+</P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The keyword for a module
+definition is <B>Module</B>. A global ID of a module should begin
+with <B>gid_Module</B>. Modules are the most important structure
+element inside the setup script and also inside the complete scp
+projects. Modules are used, to make a user defined installation
+possible. During the installation it is possible for the user to
+select or deselect some modules, meaning some functuality, he is not
+interested in. Each product can be understand as a composition of
+modules. Every directory in the scp projects defines a module.
+Modules consist of files, directories and the many other items that
+are explained in this help. And products like StarOffice consist of
+the different modules. There is always one module, the root module,
+that cannot be deselected by the user.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">A typical definition of a module
+in the scp projects looks like:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Module
+gid_Module_Prg_Calc_Bin<BR>MOD_NAME_DESC ( MODULE_PRG_CALC_BIN
+);<BR>ParentID = gid_Module_Prg_Calc;<BR>Default = YES;<BR>Minimal =
+YES;<BR>Files =
+(gid_File_Exe_Scalc,gid_File_Lib_Calc,gid_File_Lib_Sc,gid_File_Res_Sc);<BR>Unixlinks
+= (gid_Unixlink_Zip);<BR>Dirs = (gid_Dir_Program_Calc);<BR>End<BR></FONT><BR><BR>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">First
+of all, a module needs next to the lists, that assign Directories,
+Files, and Unixlinks to modules, some module specific assignments.
+This are a Name, a Description, a ParentID, values for Default and
+Minimal and optionally some styles. The Name and Description are
+visible during the setup and have therefore to be localized. The
+module gid_Module_Prg_Calc_Bin above is such a module, making the
+functuality of the application Calc available, if the user wants so.
+Therefore the Name and Description is defined in the macro
+MOD_NAME_DESC, which is defined in the included file macros.inc. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">#define
+MOD_NAME_DESC(id) \<BR>ALL_LANG(Name,STR_NAME_##id);
+\<BR>ALL_LANG(Description,STR_DESC_##id)</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">MOD_NAME_DESC uses the macro
+ALL_LANG, which is also defined in macros.inc. In this case the two
+strings STR_NAME_MODULE_PRG_CALC_BIN and STR_DESC_MODULE_PRG_CALC_BIN
+are therefore used in this module, describing the name and the
+description of the module. For the translation process it is
+therefore important that these two strings are defined and translated
+in the corresponding <A HREF="understanding_the_lng_files.html">lng
+files</A>. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">There
+is also a feature, which is used, when the user shall be warned if he
+deselects a module. This is for example important if all fonts are
+deselected. With the help of the macro MOD_NAME_DESC_ON_DESELECT,
+which is also defined in the macros.inc, there can be localized a
+text, which is shown in a textbox, when the module is deselected.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">#define
+MOD_NAME_DESC_ON_DESELECT(id) \<BR>MOD_NAME_DESC(id);
+\<BR>ALL_LANG(OnDeselect,STR_DESELECT_##id)</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Very
+important for the module is the ParentID, showing that all modules
+belong to a module tree. The upper module in each setup script is the
+module gid_Module_Root. All other modules have to be in a correlation
+to this module, and every module knows its parent. In this example
+the module gid_Module_Prg_Calc_Bin, which is the program module of
+the Calc application, has the parent Calc. Also below the parent are
+modules for the Calc Samples, the Calc Templates and so on. On the
+other hand, the Calc application module is located below the all
+application module and this again is located below the root module,
+which cannot be selected by the user and is also not visible for the
+user. For a better understanding of this module tree you should start
+a installation and select the user defined installation.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+two lines:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Default
+= YES;<BR>Minimal = YES;<BR><BR>indicate, that the module is selected
+in a Default and in a Minimal installation. If the user does not
+select a user defined installation, he has the choice between default
+or minimal. With the help of these two values, you can define,
+whether the module shall be installed in these installation types or
+not. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">There
+are also some optional styles, which can be assigned to a module: </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>HIDDEN_ROOT</B></FONT><FONT FACE="Verdana, sans-serif">
+: This flag hides the module for the user and does not show it during
+the installation. A module that has the HIDDEN_ROOT flag is not
+selectable or deselectable by the user in a user defined
+installation.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=3>The
+great part of the modules are the lists for the scp items, that have
+to be assigned to modules. There are lists for:</FONT></FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_file.html">Files</A><BR><A HREF="scpitem_directory.html">Dirs</A><BR><A HREF="scpitem_unixlink.html">Unixlinks</A><BR></FONT><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>Language specific modules</B></FONT><FONT FACE="Verdana, sans-serif">
+: Beginning with src680m242 the new concept of template modules was introduced.
+This includes the new file type <B>sct</B> (script template file)
+which represents files, that contain module definitions
+without assignments. The sct file is expanded during scp2 build and the resulting
+inc-file is included into a scp file. In this way modules for all available languages
+are created automatically.
+</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+The assignment of "Files", "Dirs" or other items can be achieved by using
+template modules, that are not used to define "real" modules, but only
+assignments to modules. This template modules require the flag
+TEMPLATEMODULE. This modules can be included from every non template
+module using the key "Assigns=...". More information is available here:
+<A HREF="scpitem_templatemodule.html">Language specific modules</A>.
+<BR><BR></FONT></P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_profile.html b/content/installation/pics/scpitem_profile.html
new file mode 100644
index 0000000..eb6866a
--- /dev/null
+++ b/content/installation/pics/scpitem_profile.html
@@ -0,0 +1,40 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040205;15225638">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a Profile </FONT></FONT>
+</P>
+<P><BR><BR>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+keyword for a profile definition is <B>Profile</B>. A global ID of a
+profile should begin with <B>gid_Profile </B>. Profiles have be
+assigned to modules. The assigned module has to be listed inside the
+definition block of the Profile. Profiles represent ini- or
+.rc-files, which are created from the setup, for example sversion.ini
+respectively .sversionrc. A typical definition of a profile in the
+scp projects looks like:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Profile
+gid_Profile_Bootstrap_Ini<BR>ModuleID = gid_Module_Abc<BR>#ifdef
+UNX<BR>Name = "bootstraprc";<BR>#else<BR>Name =
+"bootstrap.ini";<BR>#endif<BR>Dir = gid_Dir_Program;<BR>Styles
+= (NETWORK);<BR>End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">As
+you can see, the definition of a profile is very simple. The profile
+needs a ModuleID a name, a directory in which the file shall be
+created and optionally some styles. In this case the
+gid_Profile_Bootstrap_Ini is defined, which is named for unix
+bootstraprc and for all other platforms bootstrap.ini. It is
+installed into gid_Dir_Program.</FONT></P>
+<P STYLE="font-weight: medium"><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_profileitem.html b/content/installation/pics/scpitem_profileitem.html
new file mode 100644
index 0000000..4e9d5ca
--- /dev/null
+++ b/content/installation/pics/scpitem_profileitem.html
@@ -0,0 +1,43 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040205;15244571">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a ProfileItem</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The keyword for a profileitem
+definition is <B>ProfileItem</B>. A global ID of a profileitem should
+begin with <B>gid_Profileitem</B>. <SPAN STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">ProfileItems
+have to be assigned to modules. The assigned module has to be listed
+inside the definition block of the ProfileItem.</FONT></SPAN>
+ProfileItems represent entries in ini- or .rc-files, the <A HREF="scpitem_profile.html">Profiles</A>,
+for example sversion.ini respectively .sversionrc. A typical
+definition of a profileitem in the scp projects looks like:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">ProfileItem
+gid_Profileitem_Bootstrap_Section<BR>ModuleID =
+gid_Module_Abc;<BR>ProfileID = gid_Profile_Bootstrap_Ini;<BR>Section
+= "Bootstrap";<BR>Order = 3;<BR>Key = "Section";<BR>Value
+= "Versions";<BR>End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">As
+you can see, the definition of a profileitem is also very simple. The
+profileitem needs a ProfileID, that is the global ID of the
+corresponding profile. In this case this is the
+gid_Profile_Bootstrap_Ini, meaning that this entry is written into
+the file bootstrap.ini respectively bootstraprc. Profiles consist of
+sections, in this case the section is called Bootstrap. Inside this
+section in the third order is written the key-value pair:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">[Bootstrap]<BR>Section
+= Versions </FONT>
+</P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_registryitem.html b/content/installation/pics/scpitem_registryitem.html
new file mode 100644
index 0000000..ac6951d
--- /dev/null
+++ b/content/installation/pics/scpitem_registryitem.html
@@ -0,0 +1,44 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040205;15270227">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a RegistryItem</FONT></FONT></P>
+<P><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The keyword for a RegistyItem
+definition is <B>RegistryItem</B>. A global ID of a RegistyItem
+should begin with <B>gid_Regitem </B>or <B>gid_Registryitem</B>.
+RegistyItems have to be assigned to modules. The assigned module has
+to be listed in the definition block of the RegistryItem.
+RegistyItems represent entries into the Windows registry. A typical
+definition of a RegistyItem in the scp projects looks like:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">RegistryItem
+gid_Regitem_Soffice_Starcalcdocument_6_Defaulticon<BR>ModuleID =
+gid_Module_Abc;<BR>ParentID = PREDEFINED_HKEY_CLASSES_ROOT;<BR>Subkey
+= "soffice.StarCalcDocument.6\DefaultIcon";<BR>Value =
+"<progpath>\program\soffice.exe,3";<BR>End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+RegistryItem definition needs a ParentID, a Subkey and a Value. The
+ParentID is one of the Windows registry sections, in this case the
+PREDEFINED_HKEY_CLASSES_ROOT. The subkey is created, if he does not
+exist. This means in this example that below the folder
+soffice.StarCalcDocument.6 a key DefaultIcon is created. And this key
+gets the value <progpath>\program\soffice.exe,3, where
+<progpath> is a variable, substituted by the setup. </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">
+It is also possible to add the flag PATCH to a RegistryItem. In this
+case it will be included into a patch. For more information about the PATCH flag please have a look at
+<A HREF="understanding_the_patch_flag.html">Understanding the PATCH flag</A>.
+</FONT>
+</P><BR><BR>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_scpaction.html b/content/installation/pics/scpitem_scpaction.html
new file mode 100644
index 0000000..e88f866
--- /dev/null
+++ b/content/installation/pics/scpitem_scpaction.html
@@ -0,0 +1,55 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040205;15293305">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a ScpAction </FONT></FONT>
+</P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The keyword for the ScpAction
+definition is <B>ScpAction</B>. A global ID of a ScpAction should
+begin with <B>gid_Scpaction</B>. ScpAction definitions cannot be
+assigned to modules, they are global. They even do not appear in the
+final setup script, which is placed into the installation set next to
+the setup executable. They are useful for scpzip to copy files from
+the output tree into the installation set. A restriction for these
+files is, that they cannot be packed. The classical exercise for
+ScpActions is the copying of the loader from the language dependent
+output tree directory. The loader is created in the setup project and
+has the name loader.bin respectively loader.exe. In the installation
+set you find this file as setup respectively setup.exe. A typical
+definition of a ScpAction in the scp projects looks therefore like:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">ScpAction
+gid_Scpaction_Copy_loader<BR>#ifdef UNX<BR>Copy =
+"loader.bin";<BR>#else<BR>Copy =
+EXENAME(loader);<BR>#endif<BR>Name = EXENAME(setup);<BR>End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+ScpAction definition needs only two assignment. The source name and
+the destination name. Copy describes the source name, in this case
+loader.bin for Unix and EXENAME(loader) for all other platforms. The
+macro EXENAME is defined in the included file macros.inc. The Name
+describes the destination name, in this case EXENAME(setup). For
+Windows does this mean: Copy the file loader.exe from the output tree
+into the installation set as setup.exe. And for Unix: Copy the file
+loader.bin from the output tree into the installation set as file
+setup. A packing or other feature are not available for ScpActions.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">ScpAction
+gid_Scpaction_Flatloader<BR>FlatLoaderZip = "setup_services.rdb";<BR>End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Another
+ScpAction needs only one assignment. This is the FlatLoaderZip. The
+assigned file setup_services.rdb is needed as internal registry for
+the setup. This file is not copied into the installation during the
+setup. But the file is packed into the setup zip and therefore
+available during the setup process.</FONT></P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_shortcut.html b/content/installation/pics/scpitem_shortcut.html
new file mode 100644
index 0000000..5a4f12e
--- /dev/null
+++ b/content/installation/pics/scpitem_shortcut.html
@@ -0,0 +1,53 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040205;15351416">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a Shortcut</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The keyword for a Shortcut
+definition is <B>Shortcut</B>. A global ID of a ShortCut should begin
+with <B>gid_Shortcut </B>. Shortcuts are not assigned to modules,
+they are always connected with a file. Shortcuts represent links to
+files, which can exist in all available platform. The classical
+Shortcuts are the links to the executables setup and soffice
+(respectively setup.exe and soffice.exe), which are installed into
+the program directory. The links exist in the root of the Office
+installation. </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The Shortcut to the Office
+executable, which is defined as global ID gid_File_Bin_Soffice can
+therefore be defined as you can see below:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Shortcut
+gid_Shortcut_Soffice<BR>FileID = gid_File_Bin_Soffice;<BR>Dir =
+PREDEFINED_PROGDIR;<BR>#ifdef WNT<BR>Name = "%PRODUCTNAME
+%PRODUCTVERSION";<BR>#else<BR>Name = "soffice";<BR>#endif<BR>Styles
+= (STANDALONE, WORKSTATION, ALL_USERS);<BR>End</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+Shortcut definition needs first of all the FileID of the file, to
+which the link shall be created. Of course this FileID is also
+realized as global ID. The next assignment is the directory, in which
+the link shall be created. And of course also this directory is
+defined as global ID, or as in this case as a setup variable. The
+PREDEFINED_PROGDIR defines the Office installation root. The next
+assignment is necessary for the name of the link. As you can see,
+this can be platform dependent. For Windows the name "%PRODUCTNAME
+%PRODUCTVERSION" is used. For Unix the link is simply named
+soffice. Optionally there are also some styles. which define, where
+the link is created. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">It is
+also possible to create links to other links. In this case the
+definition block does not contain a FileID, but a ShortcutID.</FONT></P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_templatemodule.html b/content/installation/pics/scpitem_templatemodule.html
new file mode 100755
index 0000000..321b76f
--- /dev/null
+++ b/content/installation/pics/scpitem_templatemodule.html
@@ -0,0 +1,146 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 8 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20070730;16465100">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>
+Defining Modules With Language Specific Files</FONT></FONT></P>
+<P><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">
+Before understanding this section, you have to know the scp item
+<B>Module</B>. Documentation about this item can be found
+<A HREF="scpitem_module.html">here</A>.</P>
+<P><FONT FACE="Verdana, sans-serif">
+The strict separation of language dependent and language independent files
+that is required for the new package structure of an OpenOffice.org 3.0 and the
+huge number of supported languages, made is necessary to introduce a new process
+of module creation in scp tooling.
+</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+This new process supports automatic module generation for all languages supported
+by OpenOffice.org. Therefore it was necessary to add to the existing script particle
+files (scp) the new script template files (sct). sct files contain abstract module
+definitions, without assignments of scp items like "Files", "Dirs", ... and with
+placeholders for language settings. This sct files are evaluated during
+scp2 build by Perl programs, that resolve the language settings in the
+abstract module definitions. In this process the sct file is expanded to an inc file,
+which is again included into a scp file. The result is a scp file that can be very big.
+Because of the huge number of languages it can contain thousand of module definitions.
+</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+The assignments of scp items like "Files", "Dirs", ... should not be done inside
+the sct file, but as you are used to, inside a scp file. Therefore template modules
+were introduced, that are not a visible module during product installation, but are
+only used for assignments. This modules must have the flag TEMPLATEMODULE and are
+defined in scp files. Especially language specific files should be assigned to modules
+with flag TEMPLATEMODULE in the future. The abstract modules that are defined in the
+sct files can reference this modules using the new key "Assigns=...". If the module
+shall also be used for package creation (RPM, Solaris Package, ...), it is additionally
+necessary to define a file, containing the package information for this module. This
+happens with the key "PackageInfo=..." in the Module definition.
+</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+In the following there is a step-by-step explanation of this new process for
+language dependent modules with language specific files:
+</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+Step 1:<BR>
+All sct files are currently located in the folder scp2/source/templates,
+where they are found by the Perl program, that resolves the languages.
+The Perl program expands the abstract modules for each available
+language to an inc file. The inc files are created at scp2/<platform>/inc/<incfilename>.
+From there they can be included into scp files.
+<BR>
+Example for an abstract module definition:
+<BR><BR>
+Module gid_Module_Langpack_Calc_<LANGUAGE_><BR>
+ ParentID = gid_Module_Prg_Calc_Bin;<BR>
+ Sortkey = "450";<BR>
+ Language = "<LANGUAGE>";<BR>
+ Assigns = gid_Module_Langpack_Calc_Template;<BR>
+ Name = "gid_Module_Langpack_Calc_<LANGUAGE_>";<BR>
+ Description = "gid_Module_Langpack_Calc_<LANGUAGE_>";<BR>
+ PackageInfo = "packinfo_office_lang.txt";<BR>
+ Styles =(HIDDEN_ROOT, LANGUAGEMODULE);<BR>
+End<BR>
+<BR>
+The occurences of "<LANGUAGE>" and "<LANGUAGE_>" are resolved for all supported languages
+(taking care of underlines, like "en-US" or "en_US"). In this example the file can
+be named "alllangmodules_calc.inc".
+</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+Step 2:<BR>
+The created inc file is included into a real scp file,
+for example in scp2/source/calc/module_calc.scp: <BR><BR>
+#include "alllangmodules_calc.inc"
+</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+Step 3:<BR>
+The assignments of files and directories to modules with
+language dependent files must be done at modules that have the
+flag TEMPLATEMODULE. This modules can be defined in scp files.
+From this modules no packages can be created. They are only
+used as "assignment-container" for other modules, that reference
+this module.<BR>
+Example for a template module:<BR><BR>
+Module gid_Module_Langpack_Calc_Template<BR>
+ ParentID = gid_Module_Prg_Calc_Bin;<BR>
+ Name = "gid_Module_Langpack_Calc_Template";<BR>
+ Description = "gid_Module_Langpack_Calc_Template";<BR>
+ Styles = (TEMPLATEMODULE);<BR>
+ Files = (gid_File_Help_Scalc_Zip,<BR>
+ gid_File_Res_Analysis,<BR>
+ gid_File_Res_Bf_Sc,<BR>
+ gid_File_Res_Date,<BR>
+ gid_File_Res_Sc);<BR>
+End<BR>
+</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+Step 4:<BR>
+Modules can reference another module, that has style
+TEMPLATEMODULE. This happens with the key "Assigns" in the
+module definition (see example in step 1).<BR>
+Example:<BR>
+Assigns = gid_Module_Langpack_Calc_Template;<BR>
+<BR>
+The standard case is the following:<BR>
+The module definition in the sct file is language dependent.
+But all languages use the same assignments. Therefore this module
+definition uses the "Assigns"-key. The referenced module must
+have the style TEMPLATEMODULE. The files and directories, that
+are assigned to the module with flag TEMPLATEMODULE are
+assigned to the referencing module during packaging process.
+</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+Step 5:<BR>
+Package creation cannot be done for abstract template modules,
+but only for specific modules. The modules defined in sct files
+normally are used for package creation. Therefore this modules
+have to know file containing the package info. This file has to be found
+in the solver. It can be referenced with the key "PackageInfo"
+(see example in step 1).<BR>
+PackageInfo = �packinfo_office_lang.txt�;
+</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+Step 6:<BR>
+Modules with language dependent files must have the flag "LANGUAGEMODULE"
+(see example in step 1). This is necessary, because not all language
+modules are required during packaging of one specific installation set.
+</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+Because of this changes in the SRC680 m242 it is strictly recommended,
+that all language specific files are assigned to modules with flag TEMPLATEMODULE.
+If there are wrong assignments, so that language specific files and not language
+specific files are assigned to one module, the packaging process can find this
+errors and stops the creation of the installation set.
+</FONT></P>
+<BR><BR>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_unixlink.html b/content/installation/pics/scpitem_unixlink.html
new file mode 100755
index 0000000..5eff1ab
--- /dev/null
+++ b/content/installation/pics/scpitem_unixlink.html
@@ -0,0 +1,46 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 8 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20070730;16420000">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a Unixlink </FONT></FONT>
+</P>
+<P><BR><BR>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+keyword for a link definition on Unix systems is <B>Unixlink</B>. A
+global ID of a unixlink should begin with <B>gid_Unixlink </B>.
+Unixlinks have to be assigned to modules in the definition block of
+the module. A typical definition of a procedure in the scp projects
+looks like:</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT FACE="Verdana, sans-serif"><SPAN STYLE="font-weight: medium">#ifdef
+UNX<BR>Unixlink gid_Unixlink_Zip<BR>BIN_FILE_BODY;<BR>Styles =
+();<BR>Dir = gid_Dir_Program;<BR>Name = „ziplink“;<BR>Target
+= „/usr/bin/zip“;<BR>End<BR>#endif</SPAN></FONT></FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT FACE="Verdana, sans-serif"><SPAN STYLE="font-weight: medium">#ifdef
+UNX<BR>Unixlink gid_Unixlink_Unzip<BR>BIN_FILE_BODY;<BR>Styles =
+();<BR>Dir = gid_Dir_Program;<BR>Name = „unziplink“;<BR>Target
+= „/usr/bin/unzip“;<BR>End<BR>#endif</SPAN></FONT></FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT FACE="Verdana, sans-serif"><SPAN STYLE="font-weight: medium">Assignment
+at a Module:</SPAN></FONT></FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT FACE="Verdana, sans-serif"><SPAN STYLE="font-weight: medium">Unixlinks
+= (gid_Unixlink_Zip, gid_Unixlink_Unzip);</SPAN></FONT></FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+definition of a Unixlink is simple. The link has a name, some
+privileges (555 in the case of BIN_FILE_BODY), a directory, in which
+the link is created, and a target. In the first example above, a link
+named „ziplink“ is created in the program directory in
+the Office installation, that points to the file „/usr/bin/zip“.
+</FONT>
+</P>
+<P STYLE="font-weight: medium"><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/scpitem_windowscustomaction.html b/content/installation/pics/scpitem_windowscustomaction.html
new file mode 100755
index 0000000..3f48a6d
--- /dev/null
+++ b/content/installation/pics/scpitem_windowscustomaction.html
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 8 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20070730;16591800">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Definition
+of a WindowsCustomAction</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The keyword for a definition of a
+custom action for the Windows Installer service is
+</FONT><FONT FACE="Verdana, sans-serif"><B>WindowsCustomAction</B></FONT><FONT FACE="Verdana, sans-serif">.
+A global ID of a WindowsCustomAction should begin with
+</FONT><FONT FACE="Verdana, sans-serif"><B>gid_Customaction</B></FONT><FONT FACE="Verdana, sans-serif">.
+WindowsCustomActions are not assigned to modules. They know their
+file, that contains the code of the Custom Action. A typical
+definition of a WindowsCustomAction in the scp projects looks like:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><SPAN STYLE="font-weight: medium">WindowsCustomAction
+gid_Customaction_Shellextensionsdll3<BR>Name =
+"Shellextensionsdll3";<BR>Typ = "65";<BR>Source =
+"shlxtmsi.dll";<BR>Target =
+"InstallStartmenuFolderIcon";<BR>Inbinarytable =
+1;<BR>Assignment1 = ("InstallExecuteSequence", "Not
+REMOVE=\"ALL\" And Not PATCH", "end");<BR>End</SPAN></FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><SPAN STYLE="font-weight: medium">The
+WindowsCustomAction has a name, that is the unique identifier in the
+table „CustomAction“ in the Windows Installer database.
+The type is included into the „Type“ column of the table
+„CustomAction“. The same with the source, which is in
+this case a library, that is included into the table „Binary“
+of the msi database. Therefore the key „Inbinarytable“ is
+set to „1“. The target is the name of the procedure, that
+is started by the Windows Installer service. And finally the
+Assignment1 (many more assignments are possible with increasing
+numbers) defines the table, in which the CustomAction is included
+into the action order. Possible values are InstallExecuteSequence,
+InstallAdminSequence, InstallUISequence, ... . In this case als a
+condition for the execution can be defined and the position in the
+execute sequence.</SPAN></FONT></P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/undefining_gids.html b/content/installation/pics/undefining_gids.html
new file mode 100644
index 0000000..2493615
--- /dev/null
+++ b/content/installation/pics/undefining_gids.html
@@ -0,0 +1,58 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040205;16385883">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Undefining
+global IDs</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">Beginning with src680m25 the
+concept of undefining global IDs is introduced. This is a very
+important, if a new product shall be created. Because many of our
+products are very similar, it is better, to define only the
+difference of two setup scripts. Even OpenOffice.org, StarOffice and
+StarOfficeMulti can be defined by describing only the differences
+compared to OpenOffice.org. Therefore all scp files need only to be
+build once, which reduces the build time of the scp projects
+dramatically. Furthermore definitions like OSL_PRODUCT, FAT_PRODUCT
+or FAM_PRODUCT are no longer required, which increases the
+readability of scp files.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">The introduction of
+difference-files leads to the introduction of product families:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">OpenOffice.org -> StarOffice
+-> StarOfficeMulti</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Adabas -> AdabasMulti</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">This means, that OpenOffice.org
+and Adabas are base products. A StarOffice uses the same scp files as
+OpenOffice.org and contains some additional scp files, in which new
+global IDs are defined and other global IDs are undefined.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">The undefining of a global ID is
+a very simple process. To undefine the file defined with the global
+ID ''gid_File_Lib_Abc'', you only have to include in one of the scp
+files, that are part of the product, the following line:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><B>UnFile gid_File_Lib_Abc</B></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">That's all! You only have to list
+the global ID and the item type, with an ''Un'', before the keyword
+used for the definition. Take care, all strings are case sensitive!</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">You can also use:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">UnInstallation<BR>UnHelpText<BR>UnStarRegistry<BR>UnDataCarrier<BR>....</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">and so on. </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">If you want to undefine a file
+that is added to a module, you also only have to write this one
+undefinition line. The process of removal of non defined global IDs
+from modules, automatically removes the global ID from the module
+definition.</FONT></P>
+<P><BR><BR>
+</P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/understanding_the_lng_files.html b/content/installation/pics/understanding_the_lng_files.html
new file mode 100644
index 0000000..47b0952
--- /dev/null
+++ b/content/installation/pics/understanding_the_lng_files.html
@@ -0,0 +1,162 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040204;19305088">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Understanding
+the lng files</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">Some content of the scp projects
+has to be translated in the supported languages. This is important
+for localized directory names, or text output of some basic scripts.
+This translation happens with the help of the so called lng files,
+which are automatically included into the translation process. These
+files must have the same names as the scp files, in which the
+translated string is needed, but its extensions are .lng. One example
+shows this simple behaviour:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Module
+gid_Module_Prg_Calc_Bin<BR>MOD_NAME_DESC ( MODULE_PRG_CALC_BIN
+);<BR>ParentID = gid_Module_Prg_Calc;<BR>Default = YES;<BR>Minimal =
+YES;<BR>Files =
+(gid_File_Exe_Scalc,gid_File_Lib_Calc,gid_File_Lib_Sc,gid_File_Res_Sc);<BR>End</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">As you can see, this is the
+definition of a module block. In the user defined installation, there
+is a user interface for selecting the modules. This cotains a name
+and a description of each module. And of course these have to be
+localized. In the module definition you see the line:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">MOD_NAME_DESC (
+MODULE_PRG_CALC_BIN );</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">MOD_NAME_DESC is a macro defined
+in macros.inc. There you find:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">#define MOD_NAME_DESC(id)
+\<BR>ALL_LANG(Name,STR_NAME_##id);
+\<BR>ALL_LANG(Description,STR_DESC_##id)</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Therefore this can be resolved to
+the two macros: </FONT>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT FACE="Verdana, sans-serif">ALL_LANG(Name,STR_NAME_
+MODULE_PRG_CALC_BIN )<BR>ALL_LANG(Description,STR_DESC_
+MODULE_PRG_CALC_BIN )</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><BR>And ALL_LANG is also defined
+in macros.inc, but this is not important yet. Important are the two
+strings STR_NAME_ MODULE_PRG_CALC_BIN and STR_DESC_
+MODULE_PRG_CALC_BIN, which exist in the scp file, in which the module
+gid_Module_Prg_Calc_Bin is defined. For this file xyz.scp there has
+to be also a files xyz.lng. The filenames have to be identical,
+without the extensions. Therefore in the lng file, we find the
+following two entries:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">[STR_NAME_MODULE_PRG_CALC_BIN]<BR>49
+= "Programmodul"<BR>01 = "Program Module"<BR>07 =
+"Ïðîãðàììíûé
+ìîäóëü"<BR>55 =
+"Programmodul"<BR>37 = "Módulo del programa"<BR>03
+= "Módulo do programa"<BR>30 = "ËåéôïõñãéêÞ
+ìïíÜäá ðñïãñÜììáôïò"<BR>31
+= "Programma module"<BR>33 = "Module"<BR>34 =
+"Módulo del programa"<BR>35 = "Ohjelmamoduuli"<BR>39
+= "Modulo programma"<BR>45 = "Programmodul"<BR>46
+= "Programmodul"<BR>48 = "Modu³ programu"<BR>81
+= "ÌßÛ¸Þ×ÑÓ¼Þ­°Ù"<BR>82
+= "ÇÁ·Î±×·¥
+¸ðµâ"<BR>86 = "³ÌÐòÄ£¿é"<BR>88
+= "µ{¦¡¼Ò¶ô"<BR>90
+= "Program modülü"<BR>96 = "æÍÏÉ
+ÈÑäÇãÌ äãØíÉ"</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">[STR_DESC_MODULE_PRG_CALC_BIN]<BR>49
+= "Die Anwendung %PRODUCTNAME Calc"<BR>01 = "The
+application %PRODUCTNAME Calc"<BR>07 = "Ïðèëîæåíèå
+%PRODUCTNAME Calc"<BR>55 = "Die Anwendung %PRODUCTNAME
+Calc"<BR>37 = "La aplicación %PRODUCTNAME Calc"<BR>03
+= "A aplicação %PRODUCTNAME Calc"<BR>30 = "Ç
+åöáñìïãÞ
+%PRODUCTNAME Calc"<BR>31 = "De applicatie %PRODUCTNAME
+Calc"<BR>33 = "L'application %PRODUCTNAME Calc"<BR>34
+= "La aplicación %PRODUCTNAME Calc"<BR>35 =
+"Sovellus %PRODUCTNAME Calc"<BR>39 = "L'applicazione
+%PRODUCTNAME Calc"<BR>45 = "Applikationen %PRODUCTNAME
+Calc"<BR>46 = "Tillämpningen %PRODUCTNAME Calc"<BR>48
+= "Zastosowanie %PRODUCTNAME Calc"<BR>81 = "%PRODUCTNAME
+Calc ±Ìߨ¹°¼®Ý"<BR>82
+= "%PRODUCTNAME Calc ÀÀ¿ëÇÁ·Î±×·¥"<BR>86
+= "%PRODUCTNAME Calc Ó¦ÓóÌÐò"<BR>88
+= "À³¥Îµ{¦¡
+%PRODUCTNAME Calc"<BR>90 = "%PRODUCTNAME Calc
+uygulamasý"<BR>96 = "ÇáÊØÈíÞ
+%PRODUCTNAME Calc"</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">The names and descriptions are
+translated in any supported language. Therefore the scp linker will
+create a module definition, which looks like:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Module
+gid_Module_Prg_Calc_Bin<BR>ParentID = gid_Module_Prg_Calc;<BR>Minimal
+= YES;<BR>Default = YES;<BR>Files = (gid_File_Exe_Scalc,
+gid_File_Lib_Calc, gid_File_Lib_Sc,
+gid_File_Res_Sc);<BR>ConfigurationItems = (
+gid_Configurationitem_Soffice_Apps_Scalc5);<BR>FolderItems =
+(gid_Folderitem_Scalc);<BR>Name (03) = "Módulo do
+programa";<BR>Description (03) = "A aplicação
+%PRODUCTNAME Calc";<BR>Name (07) = "Ïðîãðàììíûé
+ìîäóëü";<BR>Description (07)
+= "Ïðèëîæåíèå
+%PRODUCTNAME Calc";<BR>Name (30) = "ËåéôïõñãéêÞ
+ìïíÜäá ðñïãñÜììáôïò";<BR>Description
+(30) = "Ç åöáñìïãÞ
+%PRODUCTNAME Calc";<BR>Name (31) = "Programma
+module";<BR>Description (31) = "De applicatie %PRODUCTNAME
+Calc";<BR>Name (33) = "Module";<BR>Description (33) =
+"L'application %PRODUCTNAME Calc";<BR>Name (34) = "Módulo
+del programa";<BR>Description (34) = "La aplicación
+%PRODUCTNAME Calc";<BR>Name (35) = "Ohjelmamoduuli";<BR>Description
+(35) = "Sovellus %PRODUCTNAME Calc";<BR>Name (37) = "Módulo
+del programa";<BR>Description (37) = "La aplicación
+%PRODUCTNAME Calc";<BR>Name (39) = "Modulo
+programma";<BR>Description (39) = "L'applicazione
+%PRODUCTNAME Calc";<BR>Name (45) = "Programmodul";<BR>Description
+(45) = "Applikationen %PRODUCTNAME Calc";<BR>Name (46) =
+"Programmodul";<BR>Description (46) = "Tillämpningen
+%PRODUCTNAME Calc";<BR>Name (48) = "Modu³
+programu";<BR>Description (48) = "Zastosowanie %PRODUCTNAME
+Calc";<BR>Name (49) = "Programmodul";<BR>Description
+(49) = "Die Anwendung %PRODUCTNAME Calc";<BR>Name (81) =
+"ÌßÛ¸Þ×ÑÓ¼Þ­°Ù";<BR>Description
+(81) = "%PRODUCTNAME Calc ±Ìߨ¹°¼®Ý";<BR>Name
+(82) = "ÇÁ·Î±×·¥
+¸ðµâ";<BR>Description (82) = "%PRODUCTNAME
+Calc ÀÀ¿ëÇÁ·Î±×·¥";<BR>Name
+(86) = "³ÌÐòÄ£¿é";<BR>Description
+(86) = "%PRODUCTNAME Calc Ó¦ÓóÌÐò";<BR>Name
+(88) = "µ{¦¡¼Ò¶ô";<BR>Description
+(88) = "À³¥Îµ{¦¡
+%PRODUCTNAME Calc";<BR>Name (90) = "Program
+modülü";<BR>Description (90) = "%PRODUCTNAME Calc
+uygulamasý";<BR>Name (96) = "æÍÏÉ
+ÈÑäÇãÌ äãØíÉ";<BR>Description
+(96) = "ÇáÊØÈíÞ
+%PRODUCTNAME Calc";<BR>Name (99) =
+"STR_NAME_MODULE_PRG_CALC_BIN";<BR>Description (99) =
+"STR_DESC_MODULE_PRG_CALC_BIN";<BR>Name (01) = "Program
+Module";<BR>Description (01) = "The application
+%PRODUCTNAME Calc";<BR>End</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">You see, that most of the module
+definition is translation stuff. Finally it is the scpzip that
+creates installation sets for special languages. Therefore the final
+result for an english installation set looks like:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Module
+gid_Module_Prg_Calc_Bin<BR>ParentID = gid_Module_Prg_Calc;<BR>Name =
+"Program Module";<BR>Description = "The application
+%PRODUCTNAME Calc";<BR>Minimal = YES;<BR>Default = YES;<BR>Files
+= (gid_File_Exe_Scalc, gid_File_Lib_Calc, gid_File_Lib_Sc,
+gid_File_Res_Sc);<BR>End</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">This module definition you can
+finally find in the setup script in the installation set next to the
+setup.</FONT></P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/understanding_the_patch_flag.html b/content/installation/pics/understanding_the_patch_flag.html
new file mode 100755
index 0000000..91a1aaf
--- /dev/null
+++ b/content/installation/pics/understanding_the_patch_flag.html
@@ -0,0 +1,113 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 8 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20070730;16330200">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Understanding the PATCH flag</FONT></FONT></P>
+<P><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">
+The flat PATCH has to be used, if a file shall be included into a patch product. The flag can be assigned
+at the moment to scp items "File" and "RegistryItem". So the patch can add or exchange files and write entries
+into the Windows Registry. The PATCH flag has to be assigned to every file, that was changed after the final release
+of a product, if this file shall be included into a following patch for this final release.
+</P>
+<P>
+In the most simple case, you can just assign the PATCH flag directly in the scp project to a file. Example:
+<BR><BR>
+<FONT FACE="Verdana, sans-serif">
+File gid_File_Bin_Open_Url<BR>
+ BIN_FILE_BODY;<BR>
+ Dir = gid_Dir_Program;<BR>
+ Name = "open-url";<BR>
+ Styles = (PACKED,PATCH);<BR>
+End<BR>
+</FONT>
+<BR>
+or to a RegistryItem:<BR><BR>
+<FONT FACE="Verdana, sans-serif">
+RegistryItem gid_Regitem_Software_Manufacturer_Productname_Productversion_Productcode_Install<BR>
+ ParentID = PREDEFINED_HKEY_LOCAL_MACHINE;<BR>
+ Subkey = "Software\%MANUFACTURER\%PRODUCTNAME%PRODUCTADDON\%PRODUCTVERSION\%PRODUCTCODE";<BR>
+ ModuleID = gid_Module_Root;<BR>
+ Name = "INSTALLLOCATION";<BR>
+ Value = "<progpath>";<BR>
+ Styles = (PATCH);<BR>
+End<BR>
+</FONT>
+</P>
+<P>
+If the file is defined in a macro, there is a "PATCH"-macro available:<br><br>
+STD_RES_FILE( gid_File_Res_Abp, abp) # <- Not in Patch<br><br>
+STD_RES_FILE_PATCH( gid_File_Res_Abp, abp) # <- In Patch<br><br>
+The following macros are available, that already contain the PATCH flag:<br><br>
+<FONT FACE="Verdana, sans-serif">
+PACKED_TXT_FILE_BODY_PATCH<br>
+ARCHIVE_TXT_FILE_BODY_PATCH<br>
+ARCHIVE_SUBST_FILE_BODY_PATCH<br>
+PACKED_LIB_FILE_BODY_PATCH<br>
+PACKED_FILTER_FILE_BODY_PATCH<br>
+STD_LIB_FILE_PATCH<br>
+STD_RES_FILE_PATCH<br>
+STD_FILTER_FILE_PATCH<br>
+STD_JAR_FILE_PATCH<br>
+UNO_JAR_FILE_PATCH<br>
+PACKED_UNO_LIB_FILE_BODY_PATCH<br>
+STD_UNO_LIB_FILE_PATCH<br>
+SPECIAL_UNO_LIB_FILE_PATCH<br>
+SPECIAL_UNO_COMPONENT_LIB_FILE_PATCH<br><br>
+</FONT>
+</P>
+<P>
+A little bit more complicated is the case, if only a selection of files shall be integrated into a patch. This is
+relevant for all files, that are defined in scp project with style ARCHIVE. Such files can contain hundreds of files, from
+which only a very small number shall be integrated into the patch. Therefore this file has to get the flag PATCH and
+additionally a "Patchfiles" section, in which all files are listed in a comma separated list, that shall be included into
+the patch. Example:<br><br>
+<FONT FACE="Verdana, sans-serif">
+File gid_File_Share_Config_Sofficecfg_uiconfig_Zip<br>
+ TXT_FILE_BODY;<br>
+ Styles = (ARCHIVE,PATCH);<br>
+ Dir = gid_Dir_Share_Config_Sofficecfg;<br>
+ Name = "uiconfig.zip";<br>
+ Patchfiles = ("modules/dbbrowser/menubar/menubar.xml",<br>
+ "modules/scalc/menubar/menubar.xml",<br>
+ "modules/sglobal/accelerator/de/default.xml",<br>
+ "modules/sglobal/accelerator/en-GB/default.xml",<br>
+ "modules/sglobal/accelerator/en-US/default.xml",<br>
+ "modules/sglobal/accelerator/es/default.xml",<br>
+ "modules/sglobal/accelerator/fr/default.xml",<br>
+ "modules/sweb/accelerator/de/default.xml",<br>
+ "modules/sweb/accelerator/en-GB/default.xml",<br>
+ "modules/sweb/accelerator/en-US/default.xml",<br>
+ "modules/sweb/accelerator/es/default.xml",<br>
+ "modules/sweb/accelerator/fr/default.xml",<br>
+ "modules/swriter/accelerator/de/default.xml",<br>
+ "modules/swriter/accelerator/en-GB/default.xml",<br>
+ "modules/swriter/accelerator/en-US/default.xml",<br>
+ "modules/swriter/accelerator/es/default.xml",<br>
+ "modules/swriter/accelerator/fr/default.xml",<br>
+ "modules/simpress/accelerator/de/default.xml",<br>
+ "modules/simpress/accelerator/en-GB/default.xml",<br>
+ "modules/simpress/accelerator/en-US/default.xml",<br>
+ "modules/simpress/accelerator/es/default.xml",<br>
+ "modules/simpress/accelerator/fr/default.xml",<br>
+ "modules/simpress/menubar/menubar.xml",<br>
+ "modules/sdraw/accelerator/de/default.xml",<br>
+ "modules/sdraw/accelerator/en-gb/default.xml",<br>
+ "modules/sdraw/accelerator/en-us/default.xml",<br>
+ "modules/sdraw/accelerator/es/default.xml",<br>
+ "modules/sdraw/accelerator/fr/default.xml",<br>
+ "modules/sdraw/menubar/menubar.xml");<br>
+End
+</FONT">
+<br>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/understanding_the_scipt_elements.html b/content/installation/pics/understanding_the_scipt_elements.html
new file mode 100644
index 0000000..6efc068
--- /dev/null
+++ b/content/installation/pics/understanding_the_scipt_elements.html
@@ -0,0 +1,125 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 8 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20070730;16330200">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Understanding
+the script elements</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The setup scripts is readable
+with a text editor. It contains blocks for different items, which can
+be read by the setup. If you open a setup script file, like setup.inf
+or setup.ins, you find blocks like</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">File
+gid_File_Lib_Db31<BR>Name = "libdb32.dll";<BR>PackedName =
+"f_0320";<BR>Size = 430080;<BR>Dir =
+gid_Dir_Program;<BR>Carrier = gid_DataCarrier;<BR>UnixRights =
+755;<BR>Date = "23012002";<BR>Time = "0600";<BR>Styles
+= (PACKED);<BR>End</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Each block begins with a special
+keyword and ends with an „End“. In this case the keyword
+is „File“, showing that the following definition block
+describes a file. As already shown in the document <A HREF="understanding_the_scipt_language.html">Understanding
+the script language</A> the block definition contains the name of the
+file, the packed name in the installation set, the size of the
+unpacked file, the directory in which the file shall be installed,
+the data carrier, the unix rights, the installation date and time and
+some special styles. Each definition block has to have a unique name,
+this is the so called global ID, GID. In the example above, the
+defintion block is named gid_File_Lib_Db31 </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">There are keywords for many
+actions the setup can make. Each keyword shows the beginning of a
+definition block. An installation set only contains definition
+blocks. You can define the following items:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_file.html">File</A>:
+Describing a file in the installation set </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_directory.html">Directory</A>:
+Describes a directory the setup has to create </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_profile.html">Profile</A>:
+Describing an ini- or rc-file, the setup creates and fills during
+setup </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_profileitem.html">ProfileItem</A>:
+One line in the form Key = Value in a Profile, written by the setup</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_registryitem.html">RegistryItem</A>:
+One line in the form Key = Value in the setup registry, written by
+the setup </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_folder.html">Folder</A>:
+Creates a directory in the Windows system, for example in the start
+menu directory</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_folderitem.html">FolderItem</A>:
+Creates the links to files in the created folder, for example in the
+start menu folder </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_shortcut.html">Shortcut</A>:
+Defines a link, which has to be created by the setup </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_unixlink.html">Unixlink</A>:
+Definition of a link in a Unix system, created by the setup</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_windowscustomaction.html">WindowsCustomAction</A>:
+A custom action that is executed by the Windows Installer service</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_mergemodule.html">MergeModule</A>:
+A merge module defines a Microsoft Merge Module, that is merged into the msi database during
+packaging process</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_module.html">Module</A>:
+Defines modules, which can be selected or deselected in a user
+defined installation. This item is also used to structure the setup
+script and all scp projects. A module contains lists of Files, Dirs,
+... etc. Each product can be defined as a group of modules. There is a special
+process for modules with language specific files:
+<A HREF="scpitem_templatemodule.html">Language Specific Module</A>.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_installation.html">Installation</A>:
+This is the start definition in each setup script. It contains some
+global settings</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_scpaction.html">ScpAction</A>:
+This will not appear in the setup script in an installation set. It
+is only important for the packing process.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">There are two groups of items.
+The one group describes GIDs, which have to be connected to modules.
+The other group describes global definitions. As you can see, the
+modules have a special position in the setup script.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">A module looks like:</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif"><FONT FACE="Verdana, sans-serif">Module
+gid_Module_Prg_Math_Bin<BR>MOD_NAME_DESC ( MODULE_PRG_MATH_BIN
+);<BR>ParentID = gid_Module_Prg_Math;<BR>Default = YES;<BR>Minimal =
+YES;<BR>Files =
+(gid_File_Dtd_Math,gid_File_Exe_Smath,gid_File_Html_W3c_Ipr,gid_File_Lib_Sm,gid_File_Res_Sm);<BR>Unixlinks=(gid_Unixlink_Mylink);<BR>Dirs
+= (gid_Dir_Mydir);</FONT><BR>End</FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><U>Module dependent items:</U></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">This module block defines the
+module gid_Module_Prg_Math_Bin, which describes the math module, that
+can be selected or deselected in a userdefined installation. As you
+can see, the module definition, contains lists of other GIDs. The
+lists <B>Dirs</B> (item <B>Directory</B>), <B>Files</B> (item: <B>File</B>),
+<B>Unixlinks</B> (item: <B>Unixlink</B>), contain all GIDs, which
+describe definitions, that are installed by the setup, if the module
+is selected. Other items, like Profiles, ConfigurationItems, etc. are
+not assigned to a module, but have to contain the ModuleID in their
+definition!</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><U>Items without module
+assignment:</U></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">The items <B>Installation </B><SPAN STYLE="font-weight: medium">and</SPAN>
+<B>ScpAction</B> are <SPAN STYLE="text-decoration: none">global</SPAN>,
+they do not belong to a module. The item <B>WindowsCustomAction</B>
+knows the file, that contains the code of the custom action.
+Therefore this is assigned to a file, not to a module. The item
+<B>ShortCut</B> is assigned to a File or to another ShortCut.</FONT></P>
+<P><BR><BR>
+</P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/understanding_the_scipt_language.html b/content/installation/pics/understanding_the_scipt_language.html
new file mode 100644
index 0000000..ab4b029
--- /dev/null
+++ b/content/installation/pics/understanding_the_scipt_language.html
@@ -0,0 +1,106 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20040204;19025249">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Understanding
+the script language</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The setup scripts is a file you
+can read with a normal text editor. In an installation set it is
+placed next to setup. The script contains only blocks, beginning with
+a special keyword and ending with an „End“. </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">A typical block looks like: </FONT>
+</P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">File
+gid_File_Lib_Db31<BR>Name = "libdb32.dll";<BR>PackedName =
+"f_0320";<BR>Size = 430080;<BR>Dir =
+gid_Dir_Program;<BR>Carrier = gid_DataCarrier;<BR>UnixRights =
+755;<BR>Date = "23012002";<BR>Time = "0600";<BR>Styles
+= (PACKED);<BR>End</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">This
+block is the <B><I>definition</I></B> of the global ID
+gid_File_Lib_Db31. Due to the beginning word <B>File</B> it describes
+a file. What information is needed for a file definition? First of
+all we see the name libdb32.dll. This is the physical name of the
+file. This file is packed in the installation set in a file name
+f_0320. The size of the unpacked libdb32.dll is 430.080 bytes. It
+shall be installed into a directory with the global ID
+gid_Dir_Program. This gid has to be definded in this setup script
+before this file definition. The Carrier is the medium, on which this
+file is stored. This is important for example for multi discs
+installations. If we install this product on a Unix platform we can
+give the Unix rights 755 to it. The installation date will be the
+01/23/2002, the installation time is 0600. This file is packed into
+the file f_0320, therefore it has the Style Packed. </FONT>
+</P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">This
+block you can find in the setup script of an installation set. The
+original setup script is located in the bin directory of the output
+tree. It was created in one of the scp-projects. The block of this
+file looks in the original setup script:</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">File
+gid_File_Lib_Db31<BR>Name = "libdb32.dll";<BR>Dir =
+gid_Dir_Program;<BR>Carrier = gid_Datacarrier;<BR>UnixRights =
+755;<BR>Date = " 23012002 ";<BR>Time = "0600";<BR>Styles
+= (PACKED);<BR>End</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">As you
+can see, scpzip adds the lines for the PackedName and the Size to the
+file definition. These are data, you cannot know, when you define a
+new file. </FONT>
+</P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">But how
+looks the original file definition. As you have already read, the
+setup script in the output tree is already platform and product
+independent. It was created from scp files, which were checked,
+preprocessed, linked and edited in many ways. The original file
+definition in the scp projects is the following definition block:</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">File
+gid_File_Lib_Db31<BR>BIN_FILE_BODY;<BR>#ifdef UNX<BR>Name =
+"libdb-3.2.so";<BR>#else<BR>Name =
+"libdb32.dll";<BR>#endif<BR>Dir = gid_Dir_Program;<BR>Styles
+= (PACKED);<BR>End</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">Obviously
+the name of this file is platform dependent. You can also see a macro
+name BIN_FILE_BODY. This is defined in the file macros.inc scp2
+project.</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">#define
+BIN_FILE_BODY FILE_BODY \<BR>UnixRights = 755</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">BIN_FILE_BODY
+contains only two lines: The macro FILE_BODY and the UnixRights.</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">In this
+way one file is defined. If you do not want, that the file belongs to
+the root module and is installed always, you have to assign the file
+to a module. Modules can be deselected by a user in a user defined
+installation process. By the way, modules are also defined in such
+blocks, beginning with the keyword Module. These module definitions
+contain lists of files, of procedures and whatever can be defined in
+a setup script. One module is a root module, showing that it cannot
+be deselected during the setup. If a module contains the lines:</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">Default
+= YES;<BR>Minimal = YES;</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">it is
+selected in a Default and Minimal installation. The directories in
+the scp projects represent the modules. The directory scp2/ooo
+contains all files, registryitems, ... that belong to the root
+module. In the directory scp2/cde you find all the content of the cde
+module.</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">A
+product like an OpenOffice.org can be understand as the addition of
+all of these modules. All the defined scp files in the scp2 directory
+are bound together by the linker par2script.pl, who gets his
+information from the product definition in scp2/util/makefile.mk.</FONT></P>
+<P STYLE="line-height: 100%"><BR><BR>
+</P>
+<P STYLE="line-height: 100%"><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/pics/understanding_the_scp_project.html b/content/installation/pics/understanding_the_scp_project.html
new file mode 100644
index 0000000..af5d6d4
--- /dev/null
+++ b/content/installation/pics/understanding_the_scp_project.html
@@ -0,0 +1,118 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 8 (Solaris Sparc)">
+ <META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+ <META NAME="CREATED" CONTENT="20020419;13085671">
+ <META NAME="CHANGED" CONTENT="20070730;16142900">
+</head>
+<body LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>Understanding
+the scp2 project</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>What are scp files?</B></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">scp is the abbreviation for
+<B>script particle</B>. Every scp file is a small part of the <B>setup
+script</B>, which can be found in the installation set next to the
+setup. The setup script contains the information about the
+installation of OpenOffice.org. Every script particle contains a
+little information, for example about the kde integration, or the
+readme files or entries for the Windows registry. You will see, there
+are many, many different scp files for many different applications.</FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>When do I have to make changes
+in the scp2 project?</B></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Changes in the scp2 project are
+necessary, if the installation of OpenOffice.org has to be changed.
+This can include a new file, or an additional entry into the windows
+registry. Anything that is done by the setup, has to be available in
+the setup script. Every file and every entry into the Windows
+registry is written in the setup script in this special setup script
+language. In detail the setup script can contain the following
+information: </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><I><B>Setup Modules</B></I>,
+<I><B>Files</B></I>, <I><B>Directories</B></I>, <I><B>Profiles</B></I>
+(ini-files), <I><B>ProfileItems</B></I> (entries into ini-files),
+<I><B>RegistryItems</B></I> (entries into the Windows registry),
+<I><B>Folder</B></I> and <I><B>FolderItems</B></I> (Directories and
+Links in the Windows system directories), <I><B>ShortCuts</B></I>
+(Links to defined files or other Shortcuts), <I><B>UnixLinks</B></I>
+(Links to any location in the system), <I><B>WindowsCustomActions</B></I>
+(Windows Installer specific actions), <I><B>ScpActions</B></I>
+(copying files from the output tree into the installation set (only
+for the ZipDirector and lzip)) and <I><B>Installation</B></I> (for
+global installation parameters). </FONT>
+</P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>How do we build the setup
+script?</B></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">The setup script is made of the
+script particle. These particle contain information about the
+languages, the platform, the different products etc. Therefore the
+scp files are first of all edited by a preprocessor, who gets the
+necessary parameter. Then the program pre2par.pl prepares the files
+for the linker par2script.pl. The results of pre2par.pl are par-files
+(same filename, but extension .par), which you can find in the output
+tree in the par directory.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Which par files for which
+products and which platforms have to be built, is determined in the
+makefile.mk in the local source directories of the different scp
+projects. After creating the par files, the linker links all
+necessary par files to the different setup scripts. Which par files
+are needed for which platform and which product is described in the
+makefile.mk in the util directory of the different scp projects.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">The resulting setup script still
+contains all information for the different languages we support, but
+is specified for one product and one platform. Therefore in the last
+step of creating installation sets the scpzip packs all files which
+are mentioned in the setup script, writes this information into the
+script and changes the script corresponding to the desired language. </FONT>
+</P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>Which scp projects exist?</B></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Currently the project containing
+scp files is named <B>scp2</B>.</FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>Last changes in the scp
+structure</B></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+Caused by the strict separation of language dependent files and language
+independent files and by the increased number of supported languages for
+OpenOffice.org, a new mechanism was required, to generate modules with language
+specific files automatically. In this context a new concept with sct-files
+and modules with flag TEMPLATEMODULE was introduced into src680m242.
+sct is the abbreviation for script template files.
+</FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">
+During the scp build process, Perl programs expand the content of the sct files
+to content that would normally be defined in scp files. But the Perl programs
+"know" the supported languages and are therefore able to create a huge number
+of scp modules automatically.
+</FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">
+The assignment of "Files", "Dirs" or other items can be achieved by using
+template modules, that are not used to define "real" modules, but only
+assignments to modules. This template modules require the flag
+TEMPLATEMODULE. This modules can be included from every non template
+module using the key "Assigns=...". Please find more information
+<A HREF="scpitem_templatemodule.html">here</A>.
+</FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"> </FONT>
+</P>
+<P><BR><BR>
+</P>
+<P><BR><BR>
+</P>
+</body>
+</HTML>
diff --git a/content/installation/proposals/netinstall.html b/content/installation/proposals/netinstall.html
new file mode 100644
index 0000000..4b3643c
--- /dev/null
+++ b/content/installation/proposals/netinstall.html
@@ -0,0 +1,177 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="AUTHOR" CONTENT="Dirk Völzke">
+ <META NAME="CREATED" CONTENT="20020114;11420500">
+ <META NAME="CHANGEDBY" CONTENT="Dirk Völzke">
+ <META NAME="CHANGED" CONTENT="20020116;15265600">
+</head>
+<body LANG="de-DE">
+<H1 LANG="en-US" CLASS="western">Setup network installation</H1>
+<H2 LANG="en-US" CLASS="western">abstract</H2>
+<P LANG="en-US" CLASS="western">multi user operating systems become
+more important today so it would be good if our setup program would
+offer better support for these operating systems.</P>
+<H2 LANG="en-US" CLASS="western">Installation models</H2>
+<P LANG="en-US" CLASS="western">For better support of the multi user
+systems we will differentiate between three installation models.
+These models are the single user installation, the multi user
+installation and the network installation.</P>
+<H6 LANG="en-US" CLASS="western">Single user installation ( Windows
+98/ME )</H6>
+<P LANG="en-US" CLASS="western">In a single user installation the
+product will be installed in one single step on the computer of the
+user. All necessary system configuration ( like writing something
+into the registry, installing fonts, creating program groups, etc. )
+will be done for this single user. After the installation the product
+is ready for use.</P>
+<P LANG="en-US" CLASS="western">When someone else uses the product on
+this computer, he will use the same (user) configuration.</P>
+<H6 LANG="en-US" CLASS="western">Multi user installation (Windows NT,
+2000, XP, UNIX)</H6>
+<P LANG="en-US" CLASS="western">The system administrator installs the
+product into a common location on the computer which can be accessed
+by every user. During this installation, most of the system
+configuration will be done like font installation or file types
+registration or the creation of program groups and links to the
+program files etc. for all users.</P>
+<P LANG="en-US" CLASS="western">Before a user can use the product for
+the first time, he has to run the user installation to copy all the
+user specific data into a user specific folder. When he tries to
+start the product without running the user installation first, the
+user installation will be started by the product automatically. When
+the user installation has finished, the product will be started
+again.</P>
+<P LANG="en-US" CLASS="western">The difference to the single user
+installation is that different users of the same computer share the
+same product installation but use their own user data.</P>
+<H6 LANG="en-US" CLASS="western">Network installation (all OS, setup
+– net)</H6>
+<P LANG="en-US" CLASS="western">The system administrator installs the
+complete product on a network volume that is accessible for all
+users. No system specific or user specific installation will be done.
+All files and information necessary for user installation (e.g. fonts
+) will be stored beside the product so they are available later for
+the user installation.</P>
+<P LANG="en-US" CLASS="western">A user who wants to use the product
+has to start the setup program in the network installation to install
+the user specific data on his workstation. This will install the
+fonts, register the file types, etc. After this installation the
+user can use the product. When the user tries to start the product
+without running the user installation first, the user installation
+will be started by the product automatically. When the user
+installation has finished, the product will be started again.</P>
+<P LANG="en-US" CLASS="western">In difference to the multi user
+installation the network installation doesn't make any system
+configuration nor installs any system files on the user's computer.
+This will be done later when the user runs the user installation.</P>
+<H2 LANG="en-US" CLASS="western">Typical layout of an installation</H2>
+<P LANG="en-US" CLASS="western">We will always use the network
+installation as a base for all three kinds of installation. The
+network installation will be done using the default directories
+appropriate for the operating system. Optional you can choose another
+directory if you want.
+</P>
+<P LANG="en-US" CLASS="western"><B>Windows NT / 2000 / XP</B></P>
+<P LANG="en-US" CLASS="western"><FONT FACE="Courier, monospace"><FONT SIZE=2 STYLE="font-size: 9pt"><program
+files>\<product name>\...</FONT></FONT></P>
+<P LANG="en-US" CLASS="western"><B>UNIX / Linux</B></P>
+<P LANG="en-US" CLASS="western"><FONT FACE="Courier, monospace"><FONT SIZE=2 STYLE="font-size: 9pt">/opt/<product
+name></FONT></FONT></P>
+<P LANG="en-US" CLASS="western">The user installation uses the system
+default directories, too. These directories are:</P>
+<P LANG="en-US" CLASS="western"><B>Windows NT / 2000 / XP</B></P>
+<P LANG="en-US" CLASS="western"><FONT FACE="Courier, monospace"><FONT SIZE=2 STYLE="font-size: 9pt"><document
+and settings>\<user>\<local settings>\Sun
+Microsystems\<product name>\...</FONT></FONT></P>
+<P LANG="en-US" CLASS="western"><B>UNIX / Linux</B></P>
+<P LANG="en-US" CLASS="western"><FONT FACE="Courier, monospace"><FONT SIZE=2 STYLE="font-size: 9pt">$home/.<product
+name></FONT></FONT></P>
+<P LANG="en-US" CLASS="western">When performing a single user
+installation, both installations will be done into the same base
+directory the user chooses. This could look like:</P>
+<P LANG="en-US" CLASS="western"><B>Windows NT / 2000 / XP</B></P>
+<P LANG="en-US" CLASS="western"><FONT FACE="Courier, monospace"><FONT SIZE=2 STYLE="font-size: 9pt"><program
+files>\<product name>\...<BR><program files>\<product
+name>\user\...</FONT></FONT></P>
+<P LANG="en-US" CLASS="western"><B>UNIX / Linux</B></P>
+<P LANG="en-US" CLASS="western"><FONT SIZE=2 STYLE="font-size: 9pt"><FONT FACE="Courier, monospace">/$home/<product
+name></FONT></FONT><BR><FONT SIZE=2 STYLE="font-size: 9pt"><FONT FACE="Courier, monospace">/$home/<product
+name>/user</FONT></FONT></P>
+<H6 LANG="en-US" CLASS="western">Starting the product after a
+multiuser or network installation</H6>
+<P LANG="en-US" CLASS="western">The product has to check on startup,
+whether the user has already done a user installation. To do this
+the product has to read its version key from the <B>bootstrap.ini</B><SPAN STYLE="font-weight: medium">
+file which should reside next to the executable of the product. In
+the next step the product looks for this key in the file </SPAN><B>sversion.ini
+/ .sversionrc</B><SPAN STYLE="font-weight: medium"> ( this file is
+located in the <documents and settings>\<user>\<application
+data> directory for Windows and in the $home directory for UNIX /
+Linux ). There a three possible scenarios.</SPAN></P>
+<P LANG="en-US" CLASS="western"><I>a.) The key couldn't be found in
+the sversion.ini or there is no sversion.ini</I></P>
+<P LANG="en-US" CLASS="western" STYLE="font-style: normal">When the
+key couldn't be found then probably the user hasn't done the user
+installation. Therefor the product launches the user installation and
+quits. The setup launches the product after the successful user
+installation.</P>
+<P LANG="en-US" CLASS="western"><I>b) The path behind the key is
+invalid</I></P>
+<P LANG="en-US" CLASS="western" STYLE="font-style: normal">When the
+key could be found in both file but the path behind the key in the
+sversion.ini file is wrong, then something probably went wrong,
+therefor the setup program should be started in repair mode. So the
+product launches the setup, quits and after the successful repair the
+setup launches the product again.</P>
+<P LANG="en-US" CLASS="western"><I>c) The path behind the key is
+valid</I></P>
+<P LANG="en-US" CLASS="western" STYLE="font-style: normal">The
+product launches as usual.</P>
+<H6 LANG="en-US" CLASS="western">Starting the setup program in a
+multi user or network installation</H6>
+<P LANG="en-US" CLASS="western">When the setup is started inside a
+multi user or network installation, the setup can't decide
+automatically whether it should be used to modify or repair the
+current installation or if it is used to perform a user installation
+or modify or repair a user installation.</P>
+<P LANG="en-US" CLASS="western">When the setup finds the version key
+in the sversion.ini it will present the user the option to repair or
+deinstall or modify the user installation.</P>
+<P LANG="en-US" CLASS="western">When the setup can't find the version
+key it will present the user the option to do a user installation.</P>
+<P LANG="en-US" CLASS="western">To repair or modify or deinstall the
+multi user / network installation the setup has to be called with the
+option <B>-net</B><SPAN STYLE="font-weight: medium">. For better
+access to this option the setup should install an additional link (
+or program shortcut ) in the multi user / network installation that
+starts the setup with this option. To prevent<SPAN LANG="en-US">
+unauthorized </SPAN>access to this installation, the setup could ask
+for a password the system administrator provides during installation
+and that could be stored MD5 encoded in the installation database.</SPAN></P>
+<H2 LANG="en-US" CLASS="western">Problems</H2>
+<P LANG="en-US" CLASS="western">For a network or a multi user
+installation privileged access rights might be required.</P>
+<P LANG="en-US" CLASS="western">The user installation of a network
+installation might require privileged rights for the user's
+workstation, too, for the installation of fonts etc.</P>
+<P LANG="en-US" CLASS="western">When you try to repair an
+installation, the setup doesn't know, whether it should repair the
+user or the network ( or multi user ) installation.</P>
+<P LANG="en-US" CLASS="western">When the multi user / network
+installation has changed, it might be necessary to redo the user
+installation.</P>
+<H2 LANG="en-US" CLASS="western">Questions</H2>
+<P LANG="en-US" CLASS="western">Choose the installation method
+automatically? E.g. use single user installation for Windows 98/ME
+and the multi user installation for all other Windows versions or use
+always the multi user installation ( this uses a little bit more
+space on your harddrive for the user installation data? Use the
+network installation when installing on UNIX or Linux?</P>
+<P LANG="en-US" CLASS="western" STYLE="font-weight: medium">We prefer
+always doing a multi user / network installation with an immediately
+following user installation when necessary.</P>
+</body>
+</HTML>
diff --git a/content/installation/proposals/setup_feature/setup_features60_proposal.html b/content/installation/proposals/setup_feature/setup_features60_proposal.html
new file mode 100644
index 0000000..5feb636
--- /dev/null
+++ b/content/installation/proposals/setup_feature/setup_features60_proposal.html
@@ -0,0 +1,660 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+ <META NAME="AUTHOR" CONTENT=" ">
+ <META NAME="CREATED" CONTENT="20001213;10454075">
+ <META NAME="CHANGEDBY" CONTENT=" ">
+ <META NAME="CHANGED" CONTENT="20010216;12114919">
+ <META NAME="SDFOOTNOTE" CONTENT=";;;;;C">
+ <STYLE>
+ <!--
+ @page { size: 21cm 29.7cm; margin: 2cm }
+ H1 { margin-bottom: 0.21cm; font-family: "Arial", sans-serif; font-size: 16pt }
+ TD P { margin-bottom: 0.21cm }
+ P { margin-bottom: 0.21cm }
+ -->
+ </STYLE>
+</head>
+<body>
+<P ALIGN=CENTER STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="Arial, sans-serif"><FONT SIZE=4>
+Proposal for a StarOffice / OpenOffice.org 6.0 Setup Feature List</FONT></FONT></P>
+<P ALIGN=CENTER>Version 1, 02/16/2001,
+<A HREF="mailto:Leyla.Schroeder@germany.sun.com">Leyla.Schroeder@germany.sun.com</A></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">Priorities:</FONT></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">1 – Must</FONT></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">2 – Should</FONT></P>
+<P ALIGN=LEFT><FONT SIZE=2 STYLE="font-size: 9pt">3 - Can / Nice to
+have</FONT></P>
+<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000080" CELLPADDING=4 CELLSPACING=0>
+ <COL WIDTH=51*>
+ <COL WIDTH=161*>
+ <COL WIDTH=44*>
+ <THEAD>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Installation in General</H1>
+ </TD>
+ </TR>
+ </THEAD>
+ <TBODY>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>CD / AutoRun</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>AutoRun should be supported under Windows</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>CD / Introscreen</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>An introduction screen should offer installation of the
+ programs that are available on the CD:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">StarOffice / OpenOffice.org
+ 6.0</P>
+ <LI><P STYLE="margin-bottom: 0cm">Acrobat Reader</P>
+ <LI><P>Java Runtime Environment</P>
+ </UL>
+ <P>Furthermore, links to additional information should be
+ offered:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">Documentation</P>
+ <LI><P>Patches (for Solaris)</P>
+ </UL>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Download / Customization</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Download packages should be generated during online-connection
+ to include only those components, the user selects in his
+ session. Therefore we need a tool to create a binary installable
+ file which includes only the required modules.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Installation package</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The different installation packages should only show those
+ files to the user, that are important to him:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">setup.exe</P>
+ <LI><P STYLE="margin-bottom: 0cm">readme.txt</P>
+ <LI><P STYLE="margin-bottom: 0cm">lincense.txt</P>
+ <LI><P STYLE="margin-bottom: 0cm">jre-(...).exe</P>
+ <LI><P>setup.inf</P>
+ </UL>
+ <P>The installation files (f_00xx) should be moved to a
+ sub-folder.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Setup / Wizard</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The setup should run in window mode, not full screen. The new
+ wizard only consists of sequenced dialog windows.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Setup / Design</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The design of the setup dialogs must be worked over (=>
+ white background with Sun colors).</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Setup / Help</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><SPAN STYLE="background: transparent">Pressing the Help button
+ should open the Help in a second, resizable window. For the
+ display our own Textengine (MultiLineEdit) should be used.</SPAN></P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER><SPAN STYLE="background: transparent">2</SPAN></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Setup / Readme</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><SPAN STYLE="background: transparent">For displaying the
+ Readme in a more readable form, an additional button should be
+ offered in the dialog that opens the Readme in a HTML view.</SPAN></P>
+ <P><SPAN STYLE="background: transparent">If no browser exists on
+ the system, the button is disabled. Here only the view in the
+ text field of the dialog is available. (The txt format of the
+ Readme must still exist in the installation package.)</SPAN></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER><SPAN STYLE="background: transparent">3</SPAN></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Migration</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>A migration 5.2 => 6.0 should include:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined AutoCorrect
+ settings</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined AutoText modules</P>
+ <LI><P STYLE="margin-bottom: 0cm">User's Basic macros</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined gallery themes</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined templates</P>
+ <LI><P STYLE="margin-bottom: 0cm">User-defined dictionaries</P>
+ <LI><P STYLE="margin-bottom: 0cm">User's AddIns</P>
+ <LI><P STYLE="margin-bottom: 0cm">User's Workfolder</P>
+ <LI><P STYLE="margin-bottom: 0cm">Database migration
+ including:<BR>- Addressbook data<BR>- Bibliography data</P>
+ <LI><P><SPAN STYLE="background: transparent">User's
+ configuration data (from user/config), including:<BR>-
+ Palettes<BR>- User-defined Math symbols<BR>- User data<BR>(Further
+ configuration data has to be defined in detail.)</SPAN></P>
+ </UL>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / Program</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>An installation package for multiple languages is needed for
+ the OEM version.</P>
+ <P><FONT FACE="Times New Roman, serif"><SPAN STYLE="background: transparent">Thereby
+ choosing a language is valid for the program language (for menus,
+ dialogs) and the document language (samples, templates).</SPAN></FONT></P>
+ <P>Changing the language after installation should be possible
+ via setup (modify installation).</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / linguistic (CJK)</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The Standard installation installs a default set of languages
+ for the linguistic. This set depends on the Office language to be
+ installed. Here the language modules for the CJK version must be
+ re-defined.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / linguistic</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>AutoText and AutoCorrect data must be written language
+ dependent into the installation.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Languages / linguistic</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><SPAN STYLE="background: transparent">The languages for the
+ linguistic that are installed should include not only spell
+ checking, thesaurus and hyphenation but also language-dependent
+ AutoText modules and replacement and exception settings of
+ AutoCorrect.</SPAN></P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER><SPAN STYLE="background: transparent">1</SPAN></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Installation path</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The default installation path should
+ be:<BR>$:\Programs\(%Productname)60 under
+ Windows<BR>\home\(UserID)\(%productname)60 under Linux/Unix</P>
+ <P>The variable stands for StarOffice60, OpenOffice60,
+ StarSuite60.</P>
+ <P>If using the variable is not possible, the installation path
+ has to use "Office60" instead of the product name.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Installation space</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The user should get more information about the available space
+ when selecting the installation path. (=> list box with
+ devices and available/estimated required space)</P>
+ <P>As we cannot show how many space is really needed for a
+ customized installation as long as the user has not selected the
+ modules to be installed, here the installation path has to be
+ determined by the user after selecting the modules.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Dialog buttons</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Button for starting installation/deinstallation must be
+ renamed from "Complete" to "Install"/"Uninstall"</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Java setup</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The user should be better informed for what installing the JRE
+ is good for (Applets, Java services). For this the setup dialog
+ should give a hint and/or the help must be improved.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="3" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Progress bar</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>During the installation process a progress bar appears with
+ text display for actual process description.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Install on demand</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Features, that are not installed yet, will be installed on
+ demand. Thereby the needed files are left on the source (CD or
+ network share) and can be copied down automatically the first
+ time they are used.</P>
+ <P>The user's workflow will not be aborted by this process.</P>
+ <P><A NAME="DDE_LINK1"></A>(It is not clear, if this feature can
+ be realized.)</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">File type info</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>If more than one installation exists on the system, the file
+ type info should be assigned to the latest installation.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>Done</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Adabas</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Adabas must be re-integrated in the setup.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Custom Installation</H1>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Module selection</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The user may not be allowed to deselect something, that is
+ necessary for a feature/component to be installed.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Subtree icons</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Icons in the subtree should be replaced by more meaningful
+ ones.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><FONT FACE="Times New Roman, serif">Module descriptions</FONT></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Module descriptions must be improved</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Languages / dictionaries</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The dictionaries of the add-on folder must be included in the
+ setup to offer more than 5 languages.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><SPAN STYLE="background: transparent">Filterlist</SPAN></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The filterlist must be reviewed and updated.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Fonts</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>It must be clear to the user which fonts will be installed and
+ for what they are needed. For this a font list must be offered
+ that shows all fonts to be installed (same as Writer / Textfilter
+ Im/Export). Selecting a font entry would display a description.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Product name</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The module selection list box should use the variable for the
+ product name like:
+ </P>
+ <P>- %Productname components</P>
+ <P>+Writer<BR>+Calc</P>
+ <P>Whenever the product name itself is clear, we can use just the
+ short names (Writer, Calc etc. instead of %Productname Writer,
+ %Productname Calc). Thus the variable is necessary only the first
+ time.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Summary</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Before starting the installation the user should get a summary
+ of the settings made.</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Change / Repair / Deinstallation</H1>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Control Panel</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Win95/98/NT:<BR>When starting deinstallation from the Control
+ Panel's Add/Remove Programs of Windows the option Deinstallation
+ must be selected as default. (Windows only)</P>
+ <P>Win2000:<BR>Here we should offer one Change and one Remove
+ button (instead of Change/Remove). When Change is selected, the
+ default option is "Change installation", when Remove is
+ selected, a message box should appear to ask, if StarOffice /
+ OpenOffice.org really should be deleted.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="3" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>3</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Restricted User</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Under W2000/NT installation, deinstallation and changes of the
+ installation are not allowed for restricted users and may not be
+ possible.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>File Deletion</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>All program files and folders of the StarOffice /
+ OpenOffice.org installation must be deleted when deinstalling,
+ only those created or modified by the user remain on the disc
+ (unless, before starting the deinstallation, the user explicitly
+ states that these files have to be deleted, too).</P>
+ </TD>
+ <TD WIDTH=17%>
+ <P ALIGN=CENTER>1 (Windows)</P>
+ <P ALIGN=CENTER>2 (others)</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Repair / Description</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Option is often not understood, must be made more transparent
+ (change text).</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Repair / Source</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Repairing from CD should be possible.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#e6e6e6">
+ <TD COLSPAN=3 WIDTH=100% VALIGN=TOP>
+ <H1>Network installation</H1>
+ </TD>
+ </TR>
+ <TR BGCOLOR="#23b8dc" VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P><B>Area</B></P>
+ </TD>
+ <TD WIDTH=63%>
+ <P><B>Description</B></P>
+ </TD>
+ <TD WIDTH=17%>
+ <P><B>Priority</B></P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>/net</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>For calling a network installation we should offer a new
+ possibility (in addition to using DOS box + /net). For this
+ clicking on setupnet.lnk starts network installation:</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">setup.exe (calls single-user
+ installation)</P>
+ <LI><P>setupnet.lnk (executes the command "setup -net")</P>
+ </UL>
+ <P>Changing an installation should be possible via
+ double-clicking on the setupnet.lnk, which must remain on the CD)</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Multilingual version</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>Installing StarOffice / OpenOffice.org in more than one
+ language should be possible for the network installation. The
+ administrator can choose the language to be installed from all
+ available languages that we offer. The user can choose his
+ language from this sub-set. Only one language can be selected by
+ the user. Thus he should be able to change it later by the setup.</P>
+ <P>=> The workstation installation needs a page for choosing
+ the language.</P>
+ </TD>
+ <TD WIDTH=17% SDVAL="1" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>1</P>
+ </TD>
+ </TR>
+ <TR VALIGN=TOP>
+ <TD WIDTH=20%>
+ <P>Naming</P>
+ </TD>
+ <TD WIDTH=63%>
+ <P>The workstation installation offers the two options "Standard
+ Workstation Installation" and Standard Installation local".
+ </P>
+ <P>These options should be renamed to</P>
+ <UL>
+ <LI><P STYLE="margin-bottom: 0cm">Workstation Installation</P>
+ <LI><P>Local Installation</P>
+ </UL>
+ </TD>
+ <TD WIDTH=17% SDVAL="2" SDNUM="1031;0;@">
+ <P ALIGN=CENTER>2</P>
+ </TD>
+ </TR>
+ </TBODY>
+</TABLE>
+<H1><BR><BR>
+</H1>
+<DIV TYPE=FOOTER>
+ <P ALIGN=RIGHT STYLE="margin-top: 0.5cm; margin-bottom: 0cm"><SDFIELD TYPE=PAGE SUBTYPE=RANDOM FORMAT=PAGE>1</SDFIELD></P>
+</DIV>
+</body>
+</HTML>
diff --git a/content/installation/red.html b/content/installation/red.html
new file mode 100644
index 0000000..a17da36
--- /dev/null
+++ b/content/installation/red.html
@@ -0,0 +1,140 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<head>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+ <TITLE></TITLE>
+ <META NAME="GENERATOR" CONTENT="StarOffice 6.1 EA2 (Win32)">
+ <META NAME="AUTHOR" CONTENT="Martin Damboldt">
+ <META NAME="CREATED" CONTENT="20021017;10193800">
+ <META NAME="CHANGEDBY" CONTENT="Martin Damboldt">
+ <META NAME="CHANGED" CONTENT="20021021;14350092">
+ <STYLE>
+ <!--
+ @page { size: 21cm 29.7cm; margin: 2cm }
+ P { margin-bottom: 0.21cm }
+ -->
+ </STYLE>
+</head>
+<body LANG="de-DE">
+<P LANG="en-US" ALIGN=CENTER STYLE="margin-top: 0.42cm; page-break-after: avoid">
+<FONT FACE="Albany, sans-serif"><FONT SIZE=3><B><SPAN STYLE="background: transparent">HowTo
+reduce the size of multiple installation sets<BR>to fit them on one
+CDROM by using red</SPAN></B></FONT></FONT></P>
+<P ALIGN=CENTER><SPAN STYLE="background: transparent"><SPAN LANG="en-US"><FONT FACE="Albany, sans-serif">by
+</FONT></SPAN></SPAN><A HREF="mailto:martin.damboldt@sun.com"><SPAN STYLE="background: transparent"><SPAN LANG="en-US"><FONT FACE="Albany, sans-serif">Martin
+Damboldt</FONT></SPAN></SPAN></A></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">Introduction:</SPAN></FONT></FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">This
+HowTo describes the necessary steps to take to be able to fit for
+example seventeen OpenOffice installation sets in different languages
+for Windows which have at all a size of about 920 megabyte on a
+single 640 MB CD-R.</SPAN></FONT></FONT></P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent"><BR>OpenOffice
+installation sets of different languages have many equal files
+included. When you like to put the install sets of seventeen
+languages for Windows on a single CD you can use red to create links
+to equal files instead of having them multiple times on the image.
+The creation of those links can be done by red. Red extracts the
+content of the “f_” files of installation sets and diff
+it to each other, then it creates links so that you will have just
+one real file of each “f_” instead of having them twice
+or more. Red will do this for all files in the CD image structure you
+provide, not only for “f_” files.<BR><BR>Since red uses
+Unix file links this tool runs only on Unix systems. Red can not be
+used on Windows operating systems. But of course you can create CD's
+with Windows OpenOffice installation sets on Unix.</SPAN></FONT></FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">A.
+download necessary files for red</SPAN></FONT></FONT></P>
+<OL>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">Download
+ the solver tree package for the Unix platform you prefer (Solaris or
+ Linux) you can find it in OOo at Download->Source->Solver:
+ Output Tree</SPAN></FONT></FONT></P>
+</OL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">B.
+prepare the environment for running red</SPAN></FONT></FONT></P>
+<OL>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">extract
+ the downloaded archiv, for example
+ “Ooo_1.0.1_SolarisSparc_solver.tar.gz”, to a directory
+ of your choice</SPAN></FONT></FONT></P>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">After
+ this you will have the following
+ structure<BR>./solver/641/<platform>/bin/<BR>./solver/641/<platform>/lib/<BR>./solver/641/<platform>/.......and
+ so on</SPAN></FONT></FONT></P>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">make
+ sure that you include ./solver/641/<platform>/lib/ path of the
+ structure to you LD_LIBRARY_PATH</SPAN></FONT></FONT></P>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">set
+ the TEMP and also the TMP variable correctly to a volume which has
+ enough free space</SPAN></FONT></FONT></P>
+</OL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">C.
+prepare the CD structure</SPAN></FONT></FONT></P>
+<OL>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">create
+ the directory and content structure for the CD you like to create on
+ your harddisk</SPAN></FONT></FONT></P>
+</OL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">D.
+commands for using red</SPAN></FONT></FONT></P>
+<OL>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">possible
+ command syntax: ./red [-s] [directory] [-t][-v]<BR>[-s] [directory]
+ delivers the source directory which contains the CD structure which
+ will be modified by red</SPAN></FONT></FONT></P>
+</OL>
+<OL>
+ <P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">[-t]
+ sets red to test mode only, no links will be created but you can see
+ what the result would be</SPAN></FONT></FONT></P>
+ <P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">[-v]
+ activates verbose mode, you can see if red is still running, useful
+ since red takes some time</SPAN></FONT></FONT></P>
+</OL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">D.
+running red</SPAN></FONT></FONT></P>
+<OL>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">start
+ red: /<red-installation-directory>/red -s
+ <directory-with-CD-content> -v</SPAN></FONT></FONT></P>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">after
+ you have done this the <directory-with-CD-content> will
+ reflect the new content which might take less space on a CD like it
+ does before since now multiple equal files have been eliminated by
+ creating links</SPAN></FONT></FONT></P>
+</OL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">E.
+create an ISO file with mkisofs of the CD structure</SPAN></FONT></FONT></P>
+<OL>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">one
+ of the best tools on Unix to create an ISO image file which you can
+ burn on a CD-R is mkisofs to do so use the following command</SPAN></FONT></FONT></P>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">mkisofs
+ -o <output-directory>/<filename>.iso -V <CD name>
+ -L -l -D -r -v -J -f <directory-with-CD-content><BR>for more
+ information about mkisofs please have a look to the man pages</SPAN></FONT></FONT></P>
+ <LI><P LANG="en-US" STYLE="margin-bottom: 0cm"><FONT FACE="Albany, sans-serif"><FONT SIZE=3><SPAN STYLE="background: transparent">the
+ created ISO file you can be burned to a CD-R with the burning
+ program of your choice</SPAN></FONT></FONT></P>
+</OL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+</body>
+</HTML>