Author: buildbot
Date: Thu Sep 26 23:10:57 2013
New Revision: 880029
Log:
Staging update by buildbot for ooo-site
Modified:
websites/staging/ooo-site/trunk/cgi-bin/ (props changed)
websites/staging/ooo-site/trunk/content/ (props changed)
websites/staging/ooo-site/trunk/content/documentation/online_help/index.html
Propchange: websites/staging/ooo-site/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Sep 26 23:10:57 2013
@@ -1 +1 @@
-1526605
+1526741
Propchange: websites/staging/ooo-site/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Sep 26 23:10:57 2013
@@ -1 +1 @@
-1526605
+1526741
Modified:
websites/staging/ooo-site/trunk/content/documentation/online_help/index.html
==============================================================================
---
websites/staging/ooo-site/trunk/content/documentation/online_help/index.html
(original)
+++
websites/staging/ooo-site/trunk/content/documentation/online_help/index.html
Thu Sep 26 23:10:57 2013
@@ -23,7 +23,7 @@
<h2>OpenOffice.org 2.0 Online Help</h2>
-<p><i>Last modified: $Date: 2006/03/15 15:11:25 $</i></p>
+
<h3>Summary</h3>
<p>
@@ -37,31 +37,31 @@ Online Help</a> document.</p>
<h4>What has changed?</h4>
<style>
dt {font-weight: bold; margin-top: 10px;}
- dd { margin-top: 4px;}
+ dd { margin: 4px, 4px, 4px, 10px;}
</style>
<dl>
<dt>Help File Format</dt>
-<dd><b>Before release 2.0</b>, the help files were available in an
unspecified, intermediate XML format based on the OpenOffice.org XML format.
+<dd><b>Before release 2.0</b>: the help files were available in an
unspecified, intermediate XML format based on the OpenOffice.org XML format.
</dd>
-<dd><b>Now</b>, the help files are migrated to a well-defined, easy and
concise XML DTD which was discussed on and is <link>available from</link>
OpenOffice.org.<br/>
+<dd><b>Now</b>: the help files are migrated to a well-defined, easy and
concise XML DTD which was discussed on and is <link>available from</link>
OpenOffice.org.<br/>
The new extension for all help files is <tt>.xhp</tt>
</dd>
<dt>Help File Sources</dt>
-<dd><b>Before release 2.0</b>, the nature of the help building process
prevented the help source files to be part of the product CVS repository.</dd>
-<dd><b>Now</b>, all help source XML files are part of the product CVS and
available in the helpcontent2 module.</dd>
+<dd><b>Before release 2.0</b>: the nature of the help building process
prevented the help source files to be part of the product CVS repository.</dd>
+<dd><b>Now</b>: all help source XML files are part of the product CVS and
available in the helpcontent2 module.</dd>
<dt>Building Help</dt>
-<dd><b>Before release 2.0</b>, the binary online help files were built using a
complicated process inside Sun.</dd>
-<dd><b>Now</b>, the help building process is part of the building process of
the application and in the hand of the release engineering. Controlled by
makefiles, online help can be built by using standard build and make commands
in the cvs module.</dd>
+<dd><b>Before release 2.0</b>: the binary online help files were built using a
complicated process inside Sun.</dd>
+<dd><b>Now</b>: the help building process is part of the building process of
the application and in the hand of the release engineering. Controlled by
makefiles, online help can be built by using standard build and make commands
in the cvs module.</dd>
<dt>Help Images and Icons Handling</dt>
-<dd><b>Before release 2.0</b>, the help file set contained screen shots and
application icons in its own archive making it necessary to duplicate each icon
used in the application. This also made it necessary to compile a separate help
set for differently branded products (like StarOffice and OpenOffice.org).</dd>
-<dd><b>Now</b>, all application icons that are used in the help are taken from
the central icon repository that is also accessed by the application itself to
fetch the icons. In this way, the help always uses the same icons as the
application avoiding inconsistencies.<br/>
+<dd><b>Before release 2.0</b>: the help file set contained screen shots and
application icons in its own archive making it necessary to duplicate each icon
used in the application. This also made it necessary to compile a separate help
set for differently branded products (like StarOffice and OpenOffice.org).</dd>
+<dd><b>Now</b>: all application icons that are used in the help are taken from
the central icon repository that is also accessed by the application itself to
fetch the icons. In this way, the help always uses the same icons as the
application avoiding inconsistencies.<br/>
All images that are specific to the online help, like screen shots used in
some help files, are now in the helpimg folder of the res CVS module and are
accessed by the help in the same way as the icons.</dd>
<dt>Help Authoring</dt>
-<dd><b>Before release 2.0</b>, authoring or editing the help files was
virtually impossible for the community since the source files were not
available.</dd>
-<dd><b>Now</b>, there is an import and export filter for the OpenOffice.org
help file format for OpenOffice.org. Also, there is a set of macros that allows
authoring and editing of online help files right from within
OpenOffice.org.</dd>
+<dd><b>Before release 2.0</b>: authoring or editing the help files was
virtually impossible for the community since the source files were not
available.</dd>
+<dd><b>Now</b>: there is an import and export filter for the OpenOffice.org
help file format for OpenOffice.org. Also, there is a set of macros that allows
authoring and editing of online help files right from within
OpenOffice.org.</dd>
<dt>Help Localization</dt>
-<dd><b>Before release 2.0</b>, localization followed non-standard process that
involved many manual steps to extract and reintegrate content.</dd>
-<dd><b>Now</b>, the localization uses the same process as the UI localization.
All of this is conducted by the release engineering. For more information about
the UI/Help localization process, please contact the corresponding release
engineer Ivo Hinkelmann ([email protected]).</dd>
+<dd><b>Before release 2.0</b>: localization followed non-standard process that
involved many manual steps to extract and reintegrate content.</dd>
+<dd><b>Now</b>: the localization uses the same process as the UI localization.
All of this is conducted by the release engineering. For more information about
the UI/Help localization process, please contact the corresponding release
engineer Ivo Hinkelmann ([email protected]).</dd>
<h4>Why was it changed?</h4>
<p>All of these changes were introduced for several reasons:</p>
<ul>
