incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksch...@apache.org
Subject svn commit: r1206376 [1/2] - /incubator/ooo/ooo-site/trunk/content/installation/pics/
Date Fri, 25 Nov 2011 23:39:54 GMT
Author: kschenk
Date: Fri Nov 25 23:39:52 2011
New Revision: 1206376

URL: http://svn.apache.org/viewvc?rev=1206376&view=rev
Log:
kls -- updating installation/pics


Added:
    incubator/ooo/ooo-site/trunk/content/installation/pics/
    incubator/ooo/ooo-site/trunk/content/installation/pics/automatical_assignments.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/how_to_create_native_installer.gif   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_directory.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_file.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folder.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folderitem.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_installation.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_mergemodule.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_module.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profile.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profileitem.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_registryitem.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_scpaction.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_shortcut.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_templatemodule.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_unixlink.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_windowscustomaction.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/undefining_gids.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_lng_files.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_patch_flag.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scipt_elements.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scipt_language.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scp_project.html   (with props)

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/automatical_assignments.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/automatical_assignments.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/automatical_assignments.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/automatical_assignments.html Fri Nov 25 23:39:52 2011
@@ -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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/automatical_assignments.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/how_to_create_native_installer.gif
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/how_to_create_native_installer.gif?rev=1206376&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/how_to_create_native_installer.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_directory.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_directory.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_directory.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_directory.html Fri Nov 25 23:39:52 2011
@@ -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 =
+&quot;autotext&quot;;<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 =
+&quot;autocorr&quot;;<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 =
+&quot;program&quot;;<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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_directory.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_file.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_file.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_file.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_file.html Fri Nov 25 23:39:52 2011
@@ -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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_file.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folder.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folder.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folder.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folder.html Fri Nov 25 23:39:52 2011
@@ -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 = &quot;%PRODUCTNAME
+%PRODUCTVERSION&quot;;<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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folder.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folderitem.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folderitem.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folderitem.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folderitem.html Fri Nov 25 23:39:52 2011
@@ -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
+= &quot;setup&quot;;<BR>FolderID = gid_Folder_Staroffice;<BR>FileID =
+gid_File_Bin_Setup;<BR>IconFile = gid_File_Bin_Setup;<BR>IconID =
+15;<BR>Parameter = &quot;.uno:NewDoc&quot;;<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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_folderitem.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_installation.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_installation.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_installation.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_installation.html Fri Nov 25 23:39:52 2011
@@ -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 = &quot;OpenOffice.org&quot;;<BR>ProductVersion
+= ''680'';<BR>DefaultDestPath =
+&quot;&lt;winprogpath&gt;\%PRODUCTNAME%PRODUCTVERSION&quot;;<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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_installation.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_mergemodule.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_mergemodule.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_mergemodule.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_mergemodule.html Fri Nov 25 23:39:52 2011
@@ -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 = &quot;Microsoft_VC80_CRT_x86.msm&quot;;
+<BR>Cabfilename = &quot;openofficeorg-vc80crt.cab&quot;;
+<BR>Feature = &quot;gm_Root&quot;;
+<BR>Rootdir = &quot;TARGETDIR&quot;;
+<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
+&quot;TARGETDIR&quot;, 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 &quot;gm_Root&quot; 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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_mergemodule.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_mergemodule.html
------------------------------------------------------------------------------
    svn:executable = *

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_module.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_module.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_module.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_module.html Fri Nov 25 23:39:52 2011
@@ -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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_module.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profile.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profile.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profile.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profile.html Fri Nov 25 23:39:52 2011
@@ -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 = &quot;bootstraprc&quot;;<BR>#else<BR>Name =
+&quot;bootstrap.ini&quot;;<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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profile.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profileitem.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profileitem.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profileitem.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profileitem.html Fri Nov 25 23:39:52 2011
@@ -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
+= &quot;Bootstrap&quot;;<BR>Order = 3;<BR>Key = &quot;Section&quot;;<BR>Value
+= &quot;Versions&quot;;<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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_profileitem.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_registryitem.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_registryitem.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_registryitem.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_registryitem.html Fri Nov 25 23:39:52 2011
@@ -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
+= &quot;soffice.StarCalcDocument.6\DefaultIcon&quot;;<BR>Value =
+&quot;&lt;progpath&gt;\program\soffice.exe,3&quot;;<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 &lt;progpath&gt;\program\soffice.exe,3, where
+&lt;progpath&gt; 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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_registryitem.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_scpaction.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_scpaction.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_scpaction.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_scpaction.html Fri Nov 25 23:39:52 2011
@@ -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 =
+&quot;loader.bin&quot;;<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 = &quot;setup_services.rdb&quot;;<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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_scpaction.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_shortcut.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_shortcut.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_shortcut.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_shortcut.html Fri Nov 25 23:39:52 2011
@@ -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 = &quot;%PRODUCTNAME
+%PRODUCTVERSION&quot;;<BR>#else<BR>Name = &quot;soffice&quot;;<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 &quot;%PRODUCTNAME
+%PRODUCTVERSION&quot; 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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_shortcut.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_templatemodule.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_templatemodule.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_templatemodule.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_templatemodule.html Fri Nov 25 23:39:52 2011
@@ -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/&#60;platform&#62;/inc/&#60;incfilename&#62;.
+From there they can be included into scp files.
+<BR>
+Example for an abstract module definition:
+<BR><BR>
+Module gid_Module_Langpack_Calc_&#60;LANGUAGE_&#62;<BR>
+    ParentID = gid_Module_Prg_Calc_Bin;<BR>
+    Sortkey = "450";<BR>
+    Language = "&#60;LANGUAGE&#62;";<BR>
+    Assigns = gid_Module_Langpack_Calc_Template;<BR>
+    Name = "gid_Module_Langpack_Calc_&#60;LANGUAGE_&#62;";<BR>
+    Description = "gid_Module_Langpack_Calc_&#60;LANGUAGE_&#62;";<BR>
+    PackageInfo = "packinfo_office_lang.txt";<BR>
+    Styles =(HIDDEN_ROOT, LANGUAGEMODULE);<BR>
+End<BR>
+<BR>
+The occurences of "&#60;LANGUAGE&#62;" and "&#60;LANGUAGE_&#62;" 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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_templatemodule.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_templatemodule.html
------------------------------------------------------------------------------
    svn:executable = *

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_unixlink.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_unixlink.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_unixlink.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_unixlink.html Fri Nov 25 23:39:52 2011
@@ -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 = &bdquo;ziplink&ldquo;;<BR>Target
+= &bdquo;/usr/bin/zip&ldquo;;<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 = &bdquo;unziplink&ldquo;;<BR>Target
+= &bdquo;/usr/bin/unzip&ldquo;;<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 &bdquo;ziplink&ldquo; is created in the program directory in
+the Office installation, that points to the file &bdquo;/usr/bin/zip&ldquo;.
+</FONT>
+</P>
+<P STYLE="font-weight: medium"><BR><BR>
+</P>
+</BODY>
+</HTML>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_unixlink.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_unixlink.html
------------------------------------------------------------------------------
    svn:executable = *

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_windowscustomaction.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_windowscustomaction.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_windowscustomaction.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_windowscustomaction.html Fri Nov 25 23:39:52 2011
@@ -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 =
+&quot;Shellextensionsdll3&quot;;<BR>Typ = &quot;65&quot;;<BR>Source =
+&quot;shlxtmsi.dll&quot;;<BR>Target =
+&quot;InstallStartmenuFolderIcon&quot;;<BR>Inbinarytable =
+1;<BR>Assignment1 = (&quot;InstallExecuteSequence&quot;, &quot;Not
+REMOVE=\&quot;ALL\&quot; And Not PATCH&quot;, &quot;end&quot;);<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 &bdquo;CustomAction&ldquo; in the Windows Installer database.
+The type is included into the &bdquo;Type&ldquo; column of the table
+&bdquo;CustomAction&ldquo;. The same with the source, which is in
+this case a library, that is included into the table &bdquo;Binary&ldquo;
+of the msi database. Therefore the key &bdquo;Inbinarytable&ldquo; is
+set to &bdquo;1&ldquo;. 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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_windowscustomaction.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/scpitem_windowscustomaction.html
------------------------------------------------------------------------------
    svn:executable = *

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/undefining_gids.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/undefining_gids.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/undefining_gids.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/undefining_gids.html Fri Nov 25 23:39:52 2011
@@ -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 -&gt; StarOffice
+-&gt; StarOfficeMulti</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Adabas -&gt; 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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/undefining_gids.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_lng_files.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_lng_files.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_lng_files.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_lng_files.html Fri Nov 25 23:39:52 2011
@@ -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
+= &quot;Programmodul&quot;<BR>01 = &quot;Program Module&quot;<BR>07 =
+&quot;&Iuml;&eth;&icirc;&atilde;&eth;&agrave;&igrave;&igrave;&iacute;&ucirc;&eacute;
+&igrave;&icirc;&auml;&oacute;&euml;&uuml;&quot;<BR>55 =
+&quot;Programmodul&quot;<BR>37 = &quot;M&oacute;dulo del programa&quot;<BR>03
+= &quot;M&oacute;dulo do programa&quot;<BR>30 = &quot;&Euml;&aring;&eacute;&ocirc;&iuml;&otilde;&ntilde;&atilde;&eacute;&ecirc;&THORN;
+&igrave;&iuml;&iacute;&Uuml;&auml;&aacute; &eth;&ntilde;&iuml;&atilde;&ntilde;&Uuml;&igrave;&igrave;&aacute;&ocirc;&iuml;&ograve;&quot;<BR>31
+= &quot;Programma module&quot;<BR>33 = &quot;Module&quot;<BR>34 =
+&quot;M&oacute;dulo del programa&quot;<BR>35 = &quot;Ohjelmamoduuli&quot;<BR>39
+= &quot;Modulo programma&quot;<BR>45 = &quot;Programmodul&quot;<BR>46
+= &quot;Programmodul&quot;<BR>48 = &quot;Modu&sup3; programu&quot;<BR>81
+= &quot;&Igrave;&szlig;&Ucirc;&cedil;&THORN;&times;&Ntilde;&Oacute;&frac14;&THORN;&shy;&deg;&Ugrave;&quot;<BR>82
+= &quot;&Ccedil;&Aacute;&middot;&Icirc;&plusmn;&times;&middot;&yen;
+&cedil;&eth;&micro;&acirc;&quot;<BR>86 = &quot;&sup3;&Igrave;&ETH;&ograve;&Auml;&pound;&iquest;&eacute;&quot;<BR>88
+= &quot;&micro;{&brvbar;&iexcl;&frac14;&Ograve;&para;&ocirc;&quot;<BR>90
+= &quot;Program mod&uuml;l&uuml;&quot;<BR>96 = &quot;&aelig;&Iacute;&Iuml;&Eacute;
+&Egrave;&Ntilde;&auml;&Ccedil;&atilde;&Igrave; &auml;&atilde;&Oslash;&iacute;&Eacute;&quot;</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">[STR_DESC_MODULE_PRG_CALC_BIN]<BR>49
+= &quot;Die Anwendung %PRODUCTNAME Calc&quot;<BR>01 = &quot;The
+application %PRODUCTNAME Calc&quot;<BR>07 = &quot;&Iuml;&eth;&egrave;&euml;&icirc;&aelig;&aring;&iacute;&egrave;&aring;
+%PRODUCTNAME Calc&quot;<BR>55 = &quot;Die Anwendung %PRODUCTNAME
+Calc&quot;<BR>37 = &quot;La aplicaci&oacute;n %PRODUCTNAME Calc&quot;<BR>03
+= &quot;A aplica&ccedil;&atilde;o %PRODUCTNAME Calc&quot;<BR>30 = &quot;&Ccedil;
+&aring;&ouml;&aacute;&ntilde;&igrave;&iuml;&atilde;&THORN;
+%PRODUCTNAME Calc&quot;<BR>31 = &quot;De applicatie %PRODUCTNAME
+Calc&quot;<BR>33 = &quot;L'application %PRODUCTNAME Calc&quot;<BR>34
+= &quot;La aplicaci&oacute;n %PRODUCTNAME Calc&quot;<BR>35 =
+&quot;Sovellus %PRODUCTNAME Calc&quot;<BR>39 = &quot;L'applicazione
+%PRODUCTNAME Calc&quot;<BR>45 = &quot;Applikationen %PRODUCTNAME
+Calc&quot;<BR>46 = &quot;Till&auml;mpningen %PRODUCTNAME Calc&quot;<BR>48
+= &quot;Zastosowanie %PRODUCTNAME Calc&quot;<BR>81 = &quot;%PRODUCTNAME
+Calc &plusmn;&Igrave;&szlig;&Oslash;&sup1;&deg;&frac14;&reg;&Yacute;&quot;<BR>82
+= &quot;%PRODUCTNAME Calc &Agrave;&Agrave;&iquest;&euml;&Ccedil;&Aacute;&middot;&Icirc;&plusmn;&times;&middot;&yen;&quot;<BR>86
+= &quot;%PRODUCTNAME Calc &Oacute;&brvbar;&Oacute;&Atilde;&sup3;&Igrave;&ETH;&ograve;&quot;<BR>88
+= &quot;&Agrave;&sup3;&yen;&Icirc;&micro;{&brvbar;&iexcl;
+%PRODUCTNAME Calc&quot;<BR>90 = &quot;%PRODUCTNAME Calc
+uygulamas&yacute;&quot;<BR>96 = &quot;&Ccedil;&aacute;&Ecirc;&Oslash;&Egrave;&iacute;&THORN;
+%PRODUCTNAME Calc&quot;</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) = &quot;M&oacute;dulo do
+programa&quot;;<BR>Description (03) = &quot;A aplica&ccedil;&atilde;o
+%PRODUCTNAME Calc&quot;;<BR>Name (07) = &quot;&Iuml;&eth;&icirc;&atilde;&eth;&agrave;&igrave;&igrave;&iacute;&ucirc;&eacute;
+&igrave;&icirc;&auml;&oacute;&euml;&uuml;&quot;;<BR>Description (07)
+= &quot;&Iuml;&eth;&egrave;&euml;&icirc;&aelig;&aring;&iacute;&egrave;&aring;
+%PRODUCTNAME Calc&quot;;<BR>Name (30) = &quot;&Euml;&aring;&eacute;&ocirc;&iuml;&otilde;&ntilde;&atilde;&eacute;&ecirc;&THORN;
+&igrave;&iuml;&iacute;&Uuml;&auml;&aacute; &eth;&ntilde;&iuml;&atilde;&ntilde;&Uuml;&igrave;&igrave;&aacute;&ocirc;&iuml;&ograve;&quot;;<BR>Description
+(30) = &quot;&Ccedil; &aring;&ouml;&aacute;&ntilde;&igrave;&iuml;&atilde;&THORN;
+%PRODUCTNAME Calc&quot;;<BR>Name (31) = &quot;Programma
+module&quot;;<BR>Description (31) = &quot;De applicatie %PRODUCTNAME
+Calc&quot;;<BR>Name (33) = &quot;Module&quot;;<BR>Description (33) =
+&quot;L'application %PRODUCTNAME Calc&quot;;<BR>Name (34) = &quot;M&oacute;dulo
+del programa&quot;;<BR>Description (34) = &quot;La aplicaci&oacute;n
+%PRODUCTNAME Calc&quot;;<BR>Name (35) = &quot;Ohjelmamoduuli&quot;;<BR>Description
+(35) = &quot;Sovellus %PRODUCTNAME Calc&quot;;<BR>Name (37) = &quot;M&oacute;dulo
+del programa&quot;;<BR>Description (37) = &quot;La aplicaci&oacute;n
+%PRODUCTNAME Calc&quot;;<BR>Name (39) = &quot;Modulo
+programma&quot;;<BR>Description (39) = &quot;L'applicazione
+%PRODUCTNAME Calc&quot;;<BR>Name (45) = &quot;Programmodul&quot;;<BR>Description
+(45) = &quot;Applikationen %PRODUCTNAME Calc&quot;;<BR>Name (46) =
+&quot;Programmodul&quot;;<BR>Description (46) = &quot;Till&auml;mpningen
+%PRODUCTNAME Calc&quot;;<BR>Name (48) = &quot;Modu&sup3;
+programu&quot;;<BR>Description (48) = &quot;Zastosowanie %PRODUCTNAME
+Calc&quot;;<BR>Name (49) = &quot;Programmodul&quot;;<BR>Description
+(49) = &quot;Die Anwendung %PRODUCTNAME Calc&quot;;<BR>Name (81) =
+&quot;&Igrave;&szlig;&Ucirc;&cedil;&THORN;&times;&Ntilde;&Oacute;&frac14;&THORN;&shy;&deg;&Ugrave;&quot;;<BR>Description
+(81) = &quot;%PRODUCTNAME Calc &plusmn;&Igrave;&szlig;&Oslash;&sup1;&deg;&frac14;&reg;&Yacute;&quot;;<BR>Name
+(82) = &quot;&Ccedil;&Aacute;&middot;&Icirc;&plusmn;&times;&middot;&yen;
+&cedil;&eth;&micro;&acirc;&quot;;<BR>Description (82) = &quot;%PRODUCTNAME
+Calc &Agrave;&Agrave;&iquest;&euml;&Ccedil;&Aacute;&middot;&Icirc;&plusmn;&times;&middot;&yen;&quot;;<BR>Name
+(86) = &quot;&sup3;&Igrave;&ETH;&ograve;&Auml;&pound;&iquest;&eacute;&quot;;<BR>Description
+(86) = &quot;%PRODUCTNAME Calc &Oacute;&brvbar;&Oacute;&Atilde;&sup3;&Igrave;&ETH;&ograve;&quot;;<BR>Name
+(88) = &quot;&micro;{&brvbar;&iexcl;&frac14;&Ograve;&para;&ocirc;&quot;;<BR>Description
+(88) = &quot;&Agrave;&sup3;&yen;&Icirc;&micro;{&brvbar;&iexcl;
+%PRODUCTNAME Calc&quot;;<BR>Name (90) = &quot;Program
+mod&uuml;l&uuml;&quot;;<BR>Description (90) = &quot;%PRODUCTNAME Calc
+uygulamas&yacute;&quot;;<BR>Name (96) = &quot;&aelig;&Iacute;&Iuml;&Eacute;
+&Egrave;&Ntilde;&auml;&Ccedil;&atilde;&Igrave; &auml;&atilde;&Oslash;&iacute;&Eacute;&quot;;<BR>Description
+(96) = &quot;&Ccedil;&aacute;&Ecirc;&Oslash;&Egrave;&iacute;&THORN;
+%PRODUCTNAME Calc&quot;;<BR>Name (99) =
+&quot;STR_NAME_MODULE_PRG_CALC_BIN&quot;;<BR>Description (99) =
+&quot;STR_DESC_MODULE_PRG_CALC_BIN&quot;;<BR>Name (01) = &quot;Program
+Module&quot;;<BR>Description (01) = &quot;The application
+%PRODUCTNAME Calc&quot;;<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 =
+&quot;Program Module&quot;;<BR>Description = &quot;The application
+%PRODUCTNAME Calc&quot;;<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>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_lng_files.html
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message