diff --git a/Documentation/Models/Docbook/Tcar-ug/Scripts/Bash/render.docbook b/Documentation/Models/Docbook/Tcar-ug/Scripts/Bash/render.docbook
index 020e10d..9f280b1 100644
--- a/Documentation/Models/Docbook/Tcar-ug/Scripts/Bash/render.docbook
+++ b/Documentation/Models/Docbook/Tcar-ug/Scripts/Bash/render.docbook
@@ -9,7 +9,7 @@
render
- Standardize rendition tasks inside &TCAR;
+ Standardize rendition tasks inside &TCAR;.
@@ -28,7 +28,7 @@
--theme-model="MODELNAME"--with-brands--sync-changes
- LOCATION
+ LOCATION
@@ -36,24 +36,61 @@
Description
- The render functionality exists to render
- final image and documentation files from their respective
- source files.
+ The render functionality exists to
+ automate content rendition inside &TCAR;. The content
+ rendition process itself takes place through the following
+ rendition modes:
+
+
+
+
+
+ svg — This modes works with both
+ gzip-compressed (.svgz)
+ or uncompressed (.svg)
+ scalable vector graphics as source files and produces portable
+ network graphics as main output.
+
+
+
+
+ docbook — This mode works with
+ DocBook source files and produces XHTML as main output. It is
+ also possible to produce PDF output from DocBook source files,
+ however PDF output is commented because its production fails
+ trying to create indexes.
+
+
+
+
+ conf — This mode works with one or
+ more configuration files as source and produces portable
+ network graphics as main output. The format used in these
+ configuration files is described in .
+
+
+
+
+
+ To determine the rendition mode, the
+ render functionality uses the path
+ provided as LOCATION argument and
+ the path name convention described in .
- Render-able directories
+ Render-able Directories
- Inside the working copy of &TCAR;, render-able directories are
- conventional locations inside the working copy where you can
- find output files, produced from source files and optionally
- auxiliary files. Auxiliary files are optionally used to modify
- the way output files are produced from source files (e.g., to
- produce localized output). Inside render-able directories the
- rendition process is performed through different rendition
- flows known as base-rendition, post-rendition, last-rendition
- and directory-specific rendition.
+ The render-able directories are conventional locations inside
+ the working copy where you can find final output files. The
+ final output files are produced from source files and
+ auxiliary files. Auxiliary files are frequently used to
+ create localized instances of source files which are, in turn,
+ used to create final output files in different forms (e.g., in
+ a different language).
@@ -96,6 +133,81 @@
+
+ Inside render-able directories the rendition process is
+ performed through different rendition flows known as
+ theme-rendition, base-rendition, post-rendition and
+ last-rendition.
+
+
+
+
+ Theme-Rendition Flow
+
+ The theme-rendition flow exists to produce content inside
+ trunk/Identity/Images/Themes/ directory
+ structure. This rendition flow identifies which directories
+ are render-able and uses the base-rendition on them, one by
+ one.
+
+
+ The theme-rendition flow exists to support massive rendition
+ of themes through the following command:
+
+
+
+ centos-art render trunk/Identity/Images/Themes
+
+
+
+ In case you need to limit the amount of themes or components
+ inside themes you want to render, you can be more
+ specific about the LOCATION you
+ passed as argument and use the
+
+ to specify the file you want to render. For example, if you
+ only want to render the 01-welcome.png
+ Anaconda file for CentOS-5 distribution based on version 2 of
+ Modern artistic motif, then you can run the following command:
+
+
+
+ centos-art render trunk/Identity/Images/Themes/Modern/2/Distro/5/Anaconda --filter="01-welcome"
+
+
+
+ Notice that you can reach the same result in different ways
+ here by creating combinations between the path you provide as
+ LOCATION and the
+ option. For example, all the
+ following commands produce the same result:
+
+
+
+ centos-art render trunk/Identity/Images/Themes/Modern/2/Distro/5/Anaconda
+
+
+
+ centos-art render trunk/Identity/Images/Themes/Modern --filter="2/Distro/5/Anaconda"
+
+
+
+ centos-art render trunk/Identity/Images/Themes --filter="Modern/2/Distro/5/Anaconda"
+
+
+
+ You can use whatever combination you like whenever it matches
+ a valid render-able directory inside the working copy. But it
+ seems to be an acceptable practice to use the
+ LOCATION argument to specify the
+ render-able directory path inside the trunk/Identity/Images/Themes
+ directory which images need to be rendered for and the
+ option only when it is needed to
+ restrict rendition to a specific file inside the directory
+ provided as LOCATION.
+
+
@@ -118,6 +230,13 @@
...
+
+
+ Configuration Files (<filename>render.conf</filename>)
+
+ ...
+
+