From 5c85374da580915299ca390c114ec78cdf5553a6 Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: May 17 2011 03:27:25 +0000 Subject: Update repository documentation manual. --- diff --git a/Manual/Directories/trunk/Scripts/Functions/Help.texi b/Manual/Directories/trunk/Scripts/Functions/Help.texi index e226b31..05ae6ca 100644 --- a/Manual/Directories/trunk/Scripts/Functions/Help.texi +++ b/Manual/Directories/trunk/Scripts/Functions/Help.texi @@ -1,8 +1,100 @@ -@subheading Goals +@subheading Name -@itemize -@item ... -@end itemize +The @code{help} functionlity is part of @command{centos-art.sh} script +and standardizes documentation tasks inside the working copy of CentOS +Artwork Repository. + +@subheading Synopsis + +@command{centos-art help [OPTIONS] path/to/dir @dots{}} + +The @file{path/to/dir} parameter specifies what directory structure +inside the working copy of CentOS Artwork Repository you want to +process. + +The @code{help} functionality of @command{centos-art.sh} script +accepts the following options: + +@table @option +@item --quiet + +Supress all output messages except error messages. When this option +is passed, all confirmation requests are supressed as well and a +possitive answer is assumed for them, just as if the +@option{--answer-yes} option had been provided. + +@item --answer-yes + +Assume `yes' to all confirmation requests. + +@item --dont-commit-changes + +Supress all commit and update actions realized over files, before and +after the action itself had took place over files in the working copy. + +@item --search="STRING" + +Go to node pointed by index entry @samp{STRING}. + +@item --edit "path/to/dir" + +Edit documentation entry related to path specified by +@file{path/to/dir}. + +The @file{path/to/dir} must point to any directory inside the +repository. When more than one @file{path/to/dir} are passed as +non-option arguments to the @command{centos-art.sh} script +command-line, they are queued for further edition. The edition itself +takes place through your default text editor (e.g., the one you +specified in the @env{EDITOR} environment variable) and the text +editor opens one file at time (i.e., the queue of files to edit is not +loaded in the text editor.). + +@item --read "path/to/dir" + +Read documentation entry specified by @file{file/to/dir} path, using +@command{info} command. This option is useful to read the repository +manual on text-based terminals. This option is also used internally by +@command{centos-art.sh} script to print out the reference you can +follow to know more about an error message. + +@item --update + +Update output files rexporting them from Texinfo source files. + +@item --copy "path/to/file.texi" "path/to/dir" + +Duplicate documentation entries under @file{trunk/Manual} directory +structure. + +When documentation entries are copied, it is possible to pass more +than one Texinfo file as source location. In this case, they all and +their dependent files will be copied into the target location. The +target location must be a directory and passed as last non-option +argument in the command-line. + +@item --delete "path/to/file.texi" + +Delete documentation entries under @file{trunk/Manual} directory +structure. + +When documentation entries are deleted, all cross references that +point to the deleted documentation entry will be rebuilt to remove +Texinfo markup and remark the fact that it had been removed indeed +from the repository. + +@item --rename "path/to/file.texi" "path/to/file.texi" + +Rename documentation entries under @file{trunk/Manual} directory +structure. + +@end table + +When documentation entries are removed (e.g., through +@option{--delete} or @option{--rename} options), the +@command{centos-art.sh} script takes care of updating nodes, menus and +cross references related to documentation entries in order to keep the +manual structure in a correct state. @subheading Description @@ -10,13 +102,32 @@ @item ... @end itemize -@subheading Usage +@subheading Examples @itemize @item ... @end itemize +@subheading Author + +Written by Alain Reguera Delgado. + +@subheading Reporting bugs + +Report bugs to @email{centos-artwork@@centos.org} mailing list. + +@subheading Copyright + +Copyright @copyright{} 2009, 2010, 2011 The CentOS Project. + +This is free software. You may redistribute copies of it under the +terms of the GNU General Public License (@pxref{GNU General Public +License}). There is NO WARRANTY, to the extent permitted by law. + @subheading See also -@menu -@end menu +@itemize +@item @ref{Directories trunk Scripts Functions} +@item @ref{Directories trunk Scripts} +@item @ref{Directories trunk} +@end itemize diff --git a/Manual/Directories/trunk/Scripts/Functions/Locale.texi b/Manual/Directories/trunk/Scripts/Functions/Locale.texi index 4d582f0..187308e 100644 --- a/Manual/Directories/trunk/Scripts/Functions/Locale.texi +++ b/Manual/Directories/trunk/Scripts/Functions/Locale.texi @@ -1,18 +1,18 @@ @subheading Name -The @strong{@code{locale}} functionlity is part of -@command{centos-art.sh} script and standardizes localization tasks -inside the working copy of CentOS Artwork Repository. +The @code{locale} functionlity is part of @command{centos-art.sh} +script and standardizes localization tasks inside the working copy of +CentOS Artwork Repository. @subheading Synopsis -@command{centos-art} @code{@strong{locale}} @code{[OPTIONS] path/to/dir} +@command{centos-art locale [OPTIONS] path/to/dir} The @file{path/to/dir} parameter specifies what directory structure inside the working copy of CentOS Artwork Repository you want to create translation messages for. -The @strong{@code{locale}} functionality of @command{centos-art.sh} script +The @code{locale} functionality of @command{centos-art.sh} script accepts the following options: @table @option @@ -97,18 +97,18 @@ C#, Shell Scripts, Python, Java, GNU awk, PHP, etc.). Design models are used as input to produce most images and some other contents as well. Design models are always XML-based files (e.g., SVG, -XHTML, Docbook), so the @strong{@code{locale}} functionality uses the +XHTML, Docbook), so the @code{locale} functionality uses the @command{xml2po} program to create protable objects from them under @file{trunk/Locales/Models} directory. Portable objects contain the relation between message id and message translation, as translator, need to take care of. -Thanks to @command{xml2po}, it is possible for the -@strong{@code{locale}} functionality to separate designing tasks from -the translating tasks. It is possible for graphic designers to -concentrate their efforts on designing models in English language -while translators take care of their localization using the -@option{--update} and @option{--edit} options as much as it be needed. +Thanks to @command{xml2po}, it is possible for the @code{locale} +functionality to separate designing tasks from the translating tasks. +It is possible for graphic designers to concentrate their efforts on +designing models in English language while translators take care of +their localization using the @option{--update} and @option{--edit} +options as much as it be needed. Once design models have been localized, rendering them in different language is a matter using the @strong{@code{render}} functionality of @@ -117,19 +117,19 @@ Functions Render}, for more information about it. @subsubheading Shell script localization -Additionally to design models localization, the @strong{@code{locale}} +Additionally to design models localization, the @code{locale} functionality is also used to localize the @command{centos-art.sh} script itself. The @command{centos-art.sh} script is a shell script -written in Bash, so the @strong{@code{locale}} functionality uses the +written in Bash, so the @code{locale} functionality uses the @command{gettext} tools to retrive translatable strings, create portable objects and machine objects. -Thanks to @command{gettext}, it is possible for the -@strong{@code{locale}} functionality to separate programming tasks -from the translating tasks. It is possible for programmer to -concentrate their efforts in programming output messages in English -language while translators take care of their localization using the -@option{--update} and @option{--edit} options as much as it be needed. +Thanks to @command{gettext}, it is possible for the @code{locale} +functionality to separate programming tasks from the translating +tasks. It is possible for programmer to concentrate their efforts in +programming output messages in English language while translators take +care of their localization using the @option{--update} and +@option{--edit} options as much as it be needed. Once @command{centos-art.sh} script has been localized, the translated messages should be immediatly visible to you, the next time you diff --git a/Manual/Directories/trunk/Scripts/Functions/Prepare.texi b/Manual/Directories/trunk/Scripts/Functions/Prepare.texi index d46f6dc..ea9f743 100644 --- a/Manual/Directories/trunk/Scripts/Functions/Prepare.texi +++ b/Manual/Directories/trunk/Scripts/Functions/Prepare.texi @@ -1,19 +1,19 @@ @subheading Name -The @strong{@code{prepare}} functionality is part of the +The @code{prepare} functionality is part of the @command{centos-art.sh} script and standardizes configuration of preliminar steps you need to follow in order to get your workstation ready for using a working copy of CentOS Artwork Repository. @subheading Synopsis -@command{centos-art @strong{prepare} [OPTIONS]} +@command{centos-art prepare [OPTIONS]} There is no need to specify @file{path/to/dir} information in this functionality. Most actions are performed through options. -The @strong{@code{prepare}} functionality of centos-art.sh script -accepts the following options: +The @code{prepare} functionality of centos-art.sh script accepts the +following options: @table @option @@ -79,16 +79,15 @@ Print the name and value of some of the environment variables used by @subheading Description -The @strong{@code{prepare}} functionality of @command{centos-art.sh} -script is part of the CentOS Artwork Repository. So, in order to -execute the @strong{@code{prepare}} functionality of -@command{centos-art.sh} script you need to have access to a working -copy of CentOS Artwork Repository, first. Working copies of CentOS -Artwork Repository are downloaded from the source repository and made -available to you by mean of workstations. A workstation is a computer -that you install and configure (prepare) to do something. In this -case, you pick up a computer and prepare it for working on the CentOS -Artwork Repository. +The @code{prepare} functionality of @command{centos-art.sh} script is +part of the CentOS Artwork Repository. So, in order to execute the +@code{prepare} functionality of @command{centos-art.sh} script you +need to have access to a working copy of CentOS Artwork Repository, +first. Working copies of CentOS Artwork Repository are downloaded +from the source repository and made available to you by mean of +workstations. A workstation is a computer that you install and +configure (prepare) to do something. In this case, you pick up a +computer and prepare it for working on the CentOS Artwork Repository. @subsubheading Installing the workstation @@ -234,9 +233,9 @@ sudo yum install subversion @subsubheading Configuring the working copy Once you have a working copy of CentOS Artwork Repository in your -workstation, you can go and run the @strong{@code{prepare}} -functionality of @command{centos-art.sh} script to realize the -remaining configuration stuff. +workstation, you can go and run the @code{prepare} functionality of +@command{centos-art.sh} script to realize the remaining configuration +stuff. Assuming this is the very first time you run the @command{centos-art.sh} script, you'll find that there is no @@ -249,7 +248,7 @@ the @command{centos-art.sh} script using its absolute path: ~/artwork/trunk/Scripts/centos-art.sh prepare [OPTIONS] @end verbatim -Assuming you've already run the @strong{@code{prepare}} functionality +Assuming you've already run the @code{prepare} functionality before, there is no need for you to use the absolute path again. Instead, you can use the @command{centos-art} command-line interface directly, as the following example describes: @@ -258,8 +257,8 @@ directly, as the following example describes: centos-art.sh prepare [OPTIONS] @end verbatim -Notice that you can execute the @strong{@code{prepare}} functionality -more than once. This is specially useful to keep the link information +Notice that you can execute the @code{prepare} functionality more than +once. This is specially useful to keep the link information syncronized. For example, considering you've added new brushes to or removed old brushes from your working copy of CentOS Artwork Repository, the link information related to those files need to be diff --git a/Manual/Directories/trunk/Scripts/Functions/Render.texi b/Manual/Directories/trunk/Scripts/Functions/Render.texi index ae4baea..36b5c2d 100644 --- a/Manual/Directories/trunk/Scripts/Functions/Render.texi +++ b/Manual/Directories/trunk/Scripts/Functions/Render.texi @@ -1,19 +1,19 @@ @subheading Name -The @strong{@code{render}} functionlity is part of -@command{centos-art.sh} script and standardizes rendition tasks inside -the working copy of CentOS Artwork Repository. +The @code{render} functionlity is part of @command{centos-art.sh} +script and standardizes rendition tasks inside the working copy of +CentOS Artwork Repository. @subheading Synopsis -@command{centos-art} @code{@strong{render}} @code{[OPTIONS] path/to/dir} +@command{centos-art render [OPTIONS] path/to/dir} The @file{path/to/dir} parameter specifies what directory structure inside the working copy of CentOS Artwork Repository you want to produce. -The @strong{@code{render}} functionality of @command{centos-art.sh} -script accepts the following options: +The @code{render} functionality of @command{centos-art.sh} script +accepts the following options: @table @option @item --quiet @@ -82,11 +82,11 @@ post-rendition and directory-specific rendition outputs. @subheading Description Inside the working copy of CentOS Artwork Repository, rendition tasks -take place inside renderable directories. Inside the -@strong{@code{render}} functionality of @command{centos-art.sh} -script, you can control rendition tasks through different flows of -rendition named base-rendition, post-rendition, last-rendition and -directory-specific rendition. +take place inside renderable directories. Inside the @code{render} +functionality of @command{centos-art.sh} script, you can control +rendition tasks through different flows of rendition named +base-rendition, post-rendition, last-rendition and directory-specific +rendition. @subsubheading Renderable directories @@ -108,7 +108,7 @@ files (e.g., @file{trunk/Identity/Images}). Optionally, a third directory structure is available to store the input related translation files (e.g., @file{trunk/Locales/Identity/Models}). -In direct rendition, when the @strong{@code{render}} functionality of +In direct rendition, when the @code{render} functionality of @command{centos-art.sh} script is executed, it uses the input directory structure to build a list of files to process, which is used as reference to determine the location of the translation file and the @@ -124,11 +124,11 @@ structure to store artistic motifs (@file{trunk/Identity/Images/Themes}) and one directory structure to store output files (@file{trunk/Identity/Images/Themes}). -In theme-specific rendition, when the @strong{@code{render}} -functionality of @command{centos-art.sh} script is executed, it uses -the input directory structure to build a list of files to process, -which is used as reference to determine the location of the -translation file and the location of the output file, as well. +In theme-specific rendition, when the @code{render} functionality of +@command{centos-art.sh} script is executed, it uses the input +directory structure to build a list of files to process, which is used +as reference to determine the location of the translation file and the +location of the output file, as well. In contrast with direct rendition, when we use theme-specific rendition, it is possible to combine both design models and artistic @@ -144,12 +144,12 @@ among them all. @end table In both direct and theme-specific rendition, if the location where the -output file should be stored doesn't exist, the @strong{@code{render}} +output file should be stored doesn't exist, the @code{render} functionality of @command{centos-art.sh} script will create it for you. In both direct and theme-specific rendition, if the input related -translation file doesn't exist, the @strong{@code{render}} functionality of +translation file doesn't exist, the @code{render} functionality of @command{centos-art.sh} script will produce the output in the same language of its input file. @@ -157,7 +157,7 @@ language of its input file. The base-rendition flow is the first rendition flow of all rendition flows available and takes place immediatly after executing the -@strong{@code{render}} functionality of @command{centos-art.sh} script. +@code{render} functionality of @command{centos-art.sh} script. The base-rendition produces different outputs from one unique input format. This is, one input file is used to produce one ore more output @@ -166,14 +166,14 @@ base-rendition applies the translation file to the input file in order to produce a translated instance of it, then this translated instance is used as input file to produce one or more output files. -Inside the @strong{@code{render}} functionality of -@command{centos-art.sh} script, the input format is always XML (e.g., -SVG, XHTML, Docbook), the translation files are always portable -objects (e.g., PO) and the output format depends on the input file -provided (e.g., when the input format is a SVG file, the base output -is a PNG file; when the input format is XHTML the base output is an -XHTML file; when the input format is a Docbook file the base output -might be either HTML, RTF, PS or PDF). +Inside the @code{render} functionality of @command{centos-art.sh} +script, the input format is always XML (e.g., SVG, XHTML, Docbook), +the translation files are always portable objects (e.g., PO) and the +output format depends on the input file provided (e.g., when the +input format is a SVG file, the base output is a PNG file; when the +input format is XHTML the base output is an XHTML file; when the input +format is a Docbook file the base output might be either HTML, RTF, PS +or PDF). As application example of base-rendition flow, consider the description of the following sections: diff --git a/Manual/Directories/trunk/Scripts/Functions/Tuneup.texi b/Manual/Directories/trunk/Scripts/Functions/Tuneup.texi index 68611bb..2b6845d 100755 --- a/Manual/Directories/trunk/Scripts/Functions/Tuneup.texi +++ b/Manual/Directories/trunk/Scripts/Functions/Tuneup.texi @@ -1,12 +1,12 @@ @subheading Name -The @strong{@code{tuneup}} functionlity is part of -@command{centos-art.sh} script and standardizes tasks related to file -maintainance inside the working copy of CentOS Artwork Repository. +The @code{tuneup} functionlity is part of @command{centos-art.sh} +script and standardizes tasks related to file maintainance inside the +working copy of CentOS Artwork Repository. @subheading Synopsis -@command{centos-art} @code{@strong{tuneup}} @code{[OPTIONS] path/to/dir} +@command{centos-art tuneup [OPTIONS] path/to/dir} The @file{path/to/dir} parameter specifies what directory structure inside the working copy of CentOS Artwork Repository you want to diff --git a/Manual/Introduction/copying.texi b/Manual/Introduction/copying.texi index 5b82ea0..1d3d4cf 100755 --- a/Manual/Introduction/copying.texi +++ b/Manual/Introduction/copying.texi @@ -10,7 +10,7 @@ license document, but changing it is not allowed. The CentOS Artwork Repository organizes files in a very specific way to implement The CentOS Project corporate visual identity. This very specific organization of files is part of @command{centos-art.sh} -script, a bash script that automates most of the frequent tasks inside +script, a bash script that automate most of the frequent tasks inside the repository. The @command{centos-art.sh} script and the organization of files it @@ -58,14 +58,14 @@ Documentation License (@pxref{GNU Free Documentation License}). The CentOS Brand (@pxref{Directories trunk Identity Models Brands}) is the main visual manifestaion of The CentOS Project. The CentOS Project uses The CentOS Brand to connect all its visual manifestions (e.g., -GNU/Linux Distributions, Websites, Stationery, etc.) and, this way, -provide recognition among other similar projects. +GNU/Linux Distributions, Websites, Stationery, etc.) and, this way, it +provides recognition among other similar projects. Both The CentOS Brand and all the visual manifestations that derivate -from it are available for you to be able to study and improve them -around a good citizen's will inside The CentOS Community environment, -but you are not allowed to redistribute them elsewhere, without the -given permission of The CentOS Project. +from it are available for you to study and propose improvement around +a good citizen's will at The CentOS Community environment, but you are +not allowed to redistribute them elsewhere, without the given +permission of The CentOS Project. If you need to redistribute either The CentOS Brand or any the visual manifestatinos that derivate from it, write your intentions to the diff --git a/Manual/Introduction/doc-convenctions.texi b/Manual/Introduction/doc-convenctions.texi index f74c31a..9a9cca6 100644 --- a/Manual/Introduction/doc-convenctions.texi +++ b/Manual/Introduction/doc-convenctions.texi @@ -67,9 +67,9 @@ error messages and responses to commands. For example: The @command{ls} command displays the contents of a directory. For example: @verbatim -Config manual_renameEntry.sh -manual_copyEntry.sh manual_restoreCrossReferences.sh -manual_deleteCrossReferences.sh manual_searchIndex.sh +Config help_renameEntry.sh +help_copyEntry.sh help_restoreCrossReferences.sh +help_deleteCrossReferences.sh help_searchIndex.sh @end verbatim The output returned in response to the command (in this case, the diff --git a/Manual/Introduction/history.texi b/Manual/Introduction/history.texi index 4815e72..1785ad1 100755 --- a/Manual/Introduction/history.texi +++ b/Manual/Introduction/history.texi @@ -8,15 +8,15 @@ list (@email{centos-devel@@centos.org}) during a discussion about how to automate the slide images of Anaconda. In such discussion, Ralph Angenendt rose up his hand to ask: Do you have something to show? -To answer the question, Alain Reguera Delgado posted a bash script to -produce slide images in different languages ---together with the -proposition of creating a Subversion centralized repository where -translations and image production could be distributed inside The -CentOS Community---. +To answer the question, Alain Reguera Delgado suggested a bash script +which combined SVG and SED files in order to produce PNG images in +different languages ---together with the proposition of creating a +Subversion repository where translations and image production could be +distributed inside The CentOS Community---. -Karanbirn Sighn considered the idea intresting and provides the +Karanbirn Sighn considered the idea intresting and provided the infrastructure necessary to support the effort. This way the CentOS -Artwork SIG and the CentOS Artwork Repository are officially created +Artwork SIG and the CentOS Artwork Repository were officially created and made available in the following urls: @itemize @@ -35,35 +35,34 @@ slide images in their own languages. The rendition script is at a very rustic state where only slide images can be produced. -The rendition script is improved to produce not only slide images, but -PNG images using one SVG file as input. In this configuration one -translated SVG instance was created from the SVG provided as input in -order to produce one translated PNG image as output. The translation -of SVG files is made through SED replacement commands and the -rendition of PNG images is realized through Inkscape command line +The rendition script was redesigned to extend image production to +other areas, not just slide images. In this configuration one +translated SVG instance was created from the SVG file provided as +input in order to produce one translated PNG image as output. The +translation of SVG files was made through SED replacement commands and +the rendition of PNG images was realized through Inkscape command line internface. -The rendition script is named @command{render.sh}. The directory -structures are prepared to receive the rendition script so images -could be produced inside them. Each directory structure has design +The rendition script was named @command{render.sh}. The directory +structures were prepared to receive the rendition script so images +could be produced inside them. Each directory structure had design templates (.svg), translation files (.sed), and translated images (.png). -The rendition script is unified in a common place and linked from -different directory structures. There is no need to have the same code -in different directory structures if it can be in just one place and -then be linked from different locations. +The rendition script was unified in a common place and linked from +different directory structures. There was no need to have the same +code in different directory structures if it could be in just one +place and then be linked from different locations. -The concepts of corporate identity started to be considered. As -referece, it is used Wikipedia -(@url{http://en.wikipedia.org/Corporate_identity}) and the book -@emph{Corporate Identity} by Wally Olins (1989). +Concepts about corporate identity began to be considered. As referece, +it was used the book @emph{Corporate Identity} by Wally Olins (1989) +and Wikipedia (@url{http://en.wikipedia.org/Corporate_identity}). The rendition script main's goal becomes to: automate production of a -monolithic corporate visual identity structure based on The CentOS +monolithic corporate visual identity structure, based on The CentOS Mission and The CentOS Release Schema. -The documentation of CentOS Artwork Repository starts to take form in +The documentation of CentOS Artwork Repository started to take form in @LaTeX{} format. @subheading 2010 @@ -74,34 +73,37 @@ script, but a collection of functionalities grouped into the among others. The @command{centos-art.sh} is created to automate most frequent tasks inside the repository. There is no need to have links all around the repository if a command-line interface can be created -and called anywhere inside the repository as it is usually done with +(through symbolic links, in the @file{~/bin} directory) and be called +anywhere inside the repository as it would be usually done with regular commands. Inside @command{centos-art.sh}, functionalities started to get -identified and separated one another. For example, when images are -rendered, there is no need to load functionalities related to -documentation manual. There is now common functionalities and specific -functionalities. Common functionalities are loaded when the script is -initiated and are available to specific functionalities. +identified and separated one another. For example, when images were +rendered, there was no need to load functionalities related to +documentation manual. This moved us onto common functionalities and +specific functionalities inside @command{centos-art.sh} script. Common +functionalities are loaded when the script is initiated and are +available to specific functionalities. -The @command{centos-art.sh} script is updated to handle options trough -@command{getopt} option parser. +The @command{centos-art.sh} script was redesigned to handle options +trough @command{getopt} option parser. -The repository directory structure is updated to improve the -implementation of corporate visual identity concepts. +The repository directory structure was updated to improve the +implementation of concepts related to corporate visual identity. +Specially in the area related to themes which were divided into design +models and artistic motifs. @subheading 2011 -The @command{centos-art.sh} script is updated to translate SVG and -other XML-based files (e.g., XHTML and Docbook) through -@command{xml2po} program and shell scripts files through -@command{xgettext} command. In this configuration there is no need to -use `.sed' translation files as they previously were used. +The @command{centos-art.sh} script was redesigned to start translating +SVG and other XML-based files (e.g., XHTML and Docbook files) through +the @command{xml2po} program and shell scripts files (e.g., Bash +scripts) through GNU @command{gettext} tools. This configuration +provided a stronger interface for graphic designers, translators and +programmers at time of producing localized content. @file{.sed} files +are no longer used to handle translations. -The @command{centos-art.sh} script is updated to improve option -parsing through @command{getopt} program. All arguments are parsed by -@command{getopt} now. Once all option arguments have been parsed, only -non-option arguments remain for processing. +Improve option parsing through @command{getopt}. The @command{centos-art.sh} script is updated to organize functionalities in two groups: ``the administrative functionalities'' diff --git a/Manual/repository.info.bz2 b/Manual/repository.info.bz2 index 978a482..52ffefe 100644 Binary files a/Manual/repository.info.bz2 and b/Manual/repository.info.bz2 differ diff --git a/Manual/repository.pdf b/Manual/repository.pdf index b5c7ba2..4790123 100644 Binary files a/Manual/repository.pdf and b/Manual/repository.pdf differ diff --git a/Manual/repository.txt.bz2 b/Manual/repository.txt.bz2 index ae7a982..fe7dde1 100644 Binary files a/Manual/repository.txt.bz2 and b/Manual/repository.txt.bz2 differ diff --git a/Manual/repository.xhtml.tar.bz2 b/Manual/repository.xhtml.tar.bz2 index 2233783..5cd7620 100644 Binary files a/Manual/repository.xhtml.tar.bz2 and b/Manual/repository.xhtml.tar.bz2 differ diff --git a/Manual/repository.xml b/Manual/repository.xml index 79b99ec..c356195 100644 --- a/Manual/repository.xml +++ b/Manual/repository.xml @@ -122,8 +122,8 @@ HistoryThis section records noteworthy changes of CentOS Artwork Repository through years. 2008 The CentOS Artwork Repository started at CentOS Developers mailing list (centos-devel@centos.org) during a discussion about how to automate the slide images of Anaconda. In such discussion, Ralph Angenendt rose up his hand to ask: Do you have something to show? - To answer the question, Alain Reguera Delgado posted a bash script to produce slide images in different languages —together with the proposition of creating a Subversion centralized repository where translations and image production could be distributed inside The CentOS Community—. - Karanbirn Sighn considered the idea intresting and provides the infrastructure necessary to support the effort. This way the CentOS Artwork SIG and the CentOS Artwork Repository are officially created and made available in the following urls: + To answer the question, Alain Reguera Delgado suggested a bash script which combined SVG and SED files in order to produce PNG images in different languages —together with the proposition of creating a Subversion repository where translations and image production could be distributed inside The CentOS Community—. + Karanbirn Sighn considered the idea intresting and provided the infrastructure necessary to support the effort. This way the CentOS Artwork SIG and the CentOS Artwork Repository were officially created and made available in the following urls: • @@ -136,20 +136,20 @@ Once the CentOS Artwork Repository was available, Alain Reguera Delagdo uploaded the bash script for rendering Anaconda slides; Ralph Angenendt documented it very well and The CentOS Translators started to download working copies of CentOS Artwork Repository to produce slide images in their own languages. 2009 The rendition script is at a very rustic state where only slide images can be produced. - The rendition script is improved to produce not only slide images, but PNG images using one SVG file as input. In this configuration one translated SVG instance was created from the SVG provided as input in order to produce one translated PNG image as output. The translation of SVG files is made through SED replacement commands and the rendition of PNG images is realized through Inkscape command line internface. - The rendition script is named render.sh. The directory structures are prepared to receive the rendition script so images could be produced inside them. Each directory structure has design templates (.svg), translation files (.sed), and translated images (.png). - The rendition script is unified in a common place and linked from different directory structures. There is no need to have the same code in different directory structures if it can be in just one place and then be linked from different locations. - The concepts of corporate identity started to be considered. As referece, it is used Wikipedia (http://en.wikipedia.org/Corporate_identity) and the book Corporate Identity by Wally Olins (1989). - The rendition script main's goal becomes to: automate production of a monolithic corporate visual identity structure based on The CentOS Mission and The CentOS Release Schema. - The documentation of CentOS Artwork Repository starts to take form in &latex; format. + The rendition script was redesigned to extend image production to other areas, not just slide images. In this configuration one translated SVG instance was created from the SVG file provided as input in order to produce one translated PNG image as output. The translation of SVG files was made through SED replacement commands and the rendition of PNG images was realized through Inkscape command line internface. + The rendition script was named render.sh. The directory structures were prepared to receive the rendition script so images could be produced inside them. Each directory structure had design templates (.svg), translation files (.sed), and translated images (.png). + The rendition script was unified in a common place and linked from different directory structures. There was no need to have the same code in different directory structures if it could be in just one place and then be linked from different locations. + Concepts about corporate identity began to be considered. As referece, it was used the book Corporate Identity by Wally Olins (1989) and Wikipedia (http://en.wikipedia.org/Corporate_identity). + The rendition script main's goal becomes to: automate production of a monolithic corporate visual identity structure, based on The CentOS Mission and The CentOS Release Schema. + The documentation of CentOS Artwork Repository started to take form in &latex; format. 2010 - The rendition script render.sh is no longer a rendition script, but a collection of functionalities grouped into the centos-art.sh script where rendition is one functionality among others. The centos-art.sh is created to automate most frequent tasks inside the repository. There is no need to have links all around the repository if a command-line interface can be created and called anywhere inside the repository as it is usually done with regular commands. - Inside centos-art.sh, functionalities started to get identified and separated one another. For example, when images are rendered, there is no need to load functionalities related to documentation manual. There is now common functionalities and specific functionalities. Common functionalities are loaded when the script is initiated and are available to specific functionalities. - The centos-art.sh script is updated to handle options trough getopt option parser. - The repository directory structure is updated to improve the implementation of corporate visual identity concepts. + The rendition script render.sh is no longer a rendition script, but a collection of functionalities grouped into the centos-art.sh script where rendition is one functionality among others. The centos-art.sh is created to automate most frequent tasks inside the repository. There is no need to have links all around the repository if a command-line interface can be created (through symbolic links, in the ~/bin directory) and be called anywhere inside the repository as it would be usually done with regular commands. + Inside centos-art.sh, functionalities started to get identified and separated one another. For example, when images were rendered, there was no need to load functionalities related to documentation manual. This moved us onto common functionalities and specific functionalities inside centos-art.sh script. Common functionalities are loaded when the script is initiated and are available to specific functionalities. + The centos-art.sh script was redesigned to handle options trough getopt option parser. + The repository directory structure was updated to improve the implementation of concepts related to corporate visual identity. Specially in the area related to themes which were divided into design models and artistic motifs. 2011 - The centos-art.sh script is updated to translate SVG and other XML-based files (e.g., XHTML and Docbook) through xml2po program and shell scripts files through xgettext command. In this configuration there is no need to use `.sed' translation files as they previously were used. - The centos-art.sh script is updated to improve option parsing through getopt program. All arguments are parsed by getopt now. Once all option arguments have been parsed, only non-option arguments remain for processing. + The centos-art.sh script was redesigned to start translating SVG and other XML-based files (e.g., XHTML and Docbook files) through the xml2po program and shell scripts files (e.g., Bash scripts) through GNU gettext tools. This configuration provided a stronger interface for graphic designers, translators and programmers at time of producing localized content. .sed files are no longer used to handle translations. + Improve option parsing through getopt. The centos-art.sh script is updated to organize functionalities in two groups: “the administrative functionalities” and “the productive functionalities”. The administrative functionalities cover actions like: copying, deleting and renaming directory structures inside the repository. Also, preparing your workstation for using centos-art.sh script, making backups of the distribution theme currently installed, installing themes created inside repository and restoring themes from backup. On the other hand, the productive functionalities cover actions like: content rendition, content localization, content documentation and content maintainance. @@ -233,7 +233,7 @@ Copyright (C) 2009, 2010, 2011 The CentOS Project ]]> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble - The CentOS Artwork Repository organizes files in a very specific way to implement The CentOS Project corporate visual identity. This very specific organization of files is part of centos-art.sh script, a bash script that automates most of the frequent tasks inside the repository. + The CentOS Artwork Repository organizes files in a very specific way to implement The CentOS Project corporate visual identity. This very specific organization of files is part of centos-art.sh script, a bash script that automate most of the frequent tasks inside the repository. The centos-art.sh script and the organization of files it needs to work are not in the public domain; they are copyrighted and there are restrictions on their distribution, but these restrictions are designed to permit everything that a good cooperating citizen would want to do. What is not allowed is to try to prevent others from further sharing any version of this program that they might get from you. Specifically, we want to make sure that you have the right to give away copies of centos-art.sh script, that you receive source code or else can get it if you want it, that you can change this program or use pieces of it in new free programs, and that you know you can do these things. To make sure that everyone has such rights, we have to forbid you to deprive anyone else of these rights. For example, if you distribute copies of the centos-art.sh script, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must tell them their rights. @@ -241,8 +241,8 @@ Copyright (C) 2009, 2010, 2011 The CentOS Project The centos-art.sh script is released as a GPL work. Individual packages used by centos-art.sh script include their own licenses and the centos-art.sh script license applies to all packages that it does not clash with. If there is a clash between the centos-art.sh script license and individual package licenses, the individual package license applies instead. The precise conditions of the license for the centos-art.sh script are found in the General Public Licenses (see GNU General Public License). This manual specifically is covered by the GNU Free Documentation License (see GNU Free Documentation License). 1. The CentOS Brand - The CentOS Brand (see Directories trunk Identity Models Brands) is the main visual manifestaion of The CentOS Project. The CentOS Project uses The CentOS Brand to connect all its visual manifestions (e.g., GNU/Linux Distributions, Websites, Stationery, etc.) and, this way, provide recognition among other similar projects. - Both The CentOS Brand and all the visual manifestations that derivate from it are available for you to be able to study and improve them around a good citizen's will inside The CentOS Community environment, but you are not allowed to redistribute them elsewhere, without the given permission of The CentOS Project. + The CentOS Brand (see Directories trunk Identity Models Brands) is the main visual manifestaion of The CentOS Project. The CentOS Project uses The CentOS Brand to connect all its visual manifestions (e.g., GNU/Linux Distributions, Websites, Stationery, etc.) and, this way, it provides recognition among other similar projects. + Both The CentOS Brand and all the visual manifestations that derivate from it are available for you to study and propose improvement around a good citizen's will at The CentOS Community environment, but you are not allowed to redistribute them elsewhere, without the given permission of The CentOS Project. If you need to redistribute either The CentOS Brand or any the visual manifestatinos that derivate from it, write your intentions to the centos-devel@centos.org mailing list. @@ -299,9 +299,9 @@ Copyright (C) 2009, 2010, 2011 The CentOS Project Text in this style indicates text displayed to a shell prompt such as error messages and responses to commands. For example: The ls command displays the contents of a directory. For example: The output returned in response to the command (in this case, the contents of the directory) is shown in this style. @@ -2767,30 +2767,112 @@ centos-art locale --edit trunk/Scripts
The <file>trunk/Scripts/Functions/Help</file> Directory Directories trunk Scripts Functions Help - Goals + Name + The help functionlity is part of centos-art.sh script and standardizes documentation tasks inside the working copy of CentOS Artwork Repository. + Synopsis + centos-art help [OPTIONS] path/to/dir &dots; + The path/to/dir parameter specifies what directory structure inside the working copy of CentOS Artwork Repository you want to process. + The help functionality of centos-art.sh script accepts the following options: + + + + + Supress all output messages except error messages. When this option is passed, all confirmation requests are supressed as well and a possitive answer is assumed for them, just as if the option had been provided. + + + + + + Assume `yes' to all confirmation requests. + + + + + + Supress all commit and update actions realized over files, before and after the action itself had took place over files in the working copy. + + + + + + Go to node pointed by index entry STRING. + + + + + + Edit documentation entry related to path specified by path/to/dir. + The path/to/dir must point to any directory inside the repository. When more than one path/to/dir are passed as non-option arguments to the centos-art.sh script command-line, they are queued for further edition. The edition itself takes place through your default text editor (e.g., the one you specified in the EDITOR environment variable) and the text editor opens one file at time (i.e., the queue of files to edit is not loaded in the text editor.). + + + + + + Read documentation entry specified by file/to/dir path, using info command. This option is useful to read the repository manual on text-based terminals. This option is also used internally by centos-art.sh script to print out the reference you can follow to know more about an error message. + + + + + + Update output files rexporting them from Texinfo source files. + + + + + + Duplicate documentation entries under trunk/Manual directory structure. + When documentation entries are copied, it is possible to pass more than one Texinfo file as source location. In this case, they all and their dependent files will be copied into the target location. The target location must be a directory and passed as last non-option argument in the command-line. + + + + + + Delete documentation entries under trunk/Manual directory structure. + When documentation entries are deleted, all cross references that point to the deleted documentation entry will be rebuilt to remove Texinfo markup and remark the fact that it had been removed indeed from the repository. + + + + + + Rename documentation entries under trunk/Manual directory structure. + + +
+ When documentation entries are removed (e.g., through or options), the centos-art.sh script takes care of updating nodes, menus and cross references related to documentation entries in order to keep the manual structure in a correct state. + Description • ... - Description + Examples • ... - Usage + Author + Written by Alain Reguera Delgado. + Reporting bugs + Report bugs to centos-artwork@centos.org mailing list. + Copyright + Copyright ©right; 2009, 2010, 2011 The CentOS Project. + This is free software. You may redistribute copies of it under the terms of the GNU General Public License (see GNU General Public License). There is NO WARRANTY, to the extent permitted by law. + See also • - ... + Directories trunk Scripts Functions + + + Directories trunk Scripts + + + Directories trunk - See also - -
@@ -2802,11 +2884,11 @@ centos-art locale --edit trunk/Scripts The <file>trunk/Scripts/Functions/Locale</file> Directory Directories trunk Scripts Functions Locale Name - The locale functionlity is part of centos-art.sh script and standardizes localization tasks inside the working copy of CentOS Artwork Repository. + The locale functionlity is part of centos-art.sh script and standardizes localization tasks inside the working copy of CentOS Artwork Repository. Synopsis - centos-art locale [OPTIONS] path/to/dir + centos-art locale [OPTIONS] path/to/dir The path/to/dir parameter specifies what directory structure inside the working copy of CentOS Artwork Repository you want to create translation messages for. - The locale functionality of centos-art.sh script accepts the following options: + The locale functionality of centos-art.sh script accepts the following options: @@ -2863,12 +2945,12 @@ locale -a | less The localization process is very tied to the input files we want to provide localized messages for. Inside the CentOS Artwork Repository, it is possible to localize XML files (e.g., SVG, XHTML, Docbook) and programs written in most popular programming languages (e.g., C, C++, C#, Shell Scripts, Python, Java, GNU awk, PHP, etc.). Design models localization - Design models are used as input to produce most images and some other contents as well. Design models are always XML-based files (e.g., SVG, XHTML, Docbook), so the locale functionality uses the xml2po program to create protable objects from them under trunk/Locales/Models directory. Portable objects contain the relation between message id and message translation, as translator, need to take care of. - Thanks to xml2po, it is possible for the locale functionality to separate designing tasks from the translating tasks. It is possible for graphic designers to concentrate their efforts on designing models in English language while translators take care of their localization using the and options as much as it be needed. + Design models are used as input to produce most images and some other contents as well. Design models are always XML-based files (e.g., SVG, XHTML, Docbook), so the locale functionality uses the xml2po program to create protable objects from them under trunk/Locales/Models directory. Portable objects contain the relation between message id and message translation, as translator, need to take care of. + Thanks to xml2po, it is possible for the locale functionality to separate designing tasks from the translating tasks. It is possible for graphic designers to concentrate their efforts on designing models in English language while translators take care of their localization using the and options as much as it be needed. Once design models have been localized, rendering them in different language is a matter using the render functionality of centos-art.sh script. See Directories trunk Scripts Functions Render, for more information about it. Shell script localization - Additionally to design models localization, the locale functionality is also used to localize the centos-art.sh script itself. The centos-art.sh script is a shell script written in Bash, so the locale functionality uses the gettext tools to retrive translatable strings, create portable objects and machine objects. - Thanks to gettext, it is possible for the locale functionality to separate programming tasks from the translating tasks. It is possible for programmer to concentrate their efforts in programming output messages in English language while translators take care of their localization using the and options as much as it be needed. + Additionally to design models localization, the locale functionality is also used to localize the centos-art.sh script itself. The centos-art.sh script is a shell script written in Bash, so the locale functionality uses the gettext tools to retrive translatable strings, create portable objects and machine objects. + Thanks to gettext, it is possible for the locale functionality to separate programming tasks from the translating tasks. It is possible for programmer to concentrate their efforts in programming output messages in English language while translators take care of their localization using the and options as much as it be needed. Once centos-art.sh script has been localized, the translated messages should be immediatly visible to you, the next time you execute the centos-art.sh script Note In order to localize translatable strings from English language to another language you need to be sure the LANG environment variable has been already set to the locale code you want to localize message for or see them printed out before running the centos-art.sh script. Localizing English language to itself is not supported. @@ -2940,11 +3022,11 @@ locale -a | less The <file>trunk/Scripts/Functions/Prepare</file> Directory Directories trunk Scripts Functions Prepare Name - The prepare functionality is part of the centos-art.sh script and standardizes configuration of preliminar steps you need to follow in order to get your workstation ready for using a working copy of CentOS Artwork Repository. + The prepare functionality is part of the centos-art.sh script and standardizes configuration of preliminar steps you need to follow in order to get your workstation ready for using a working copy of CentOS Artwork Repository. Synopsis - centos-art prepare [OPTIONS] + centos-art prepare [OPTIONS] There is no need to specify path/to/dir information in this functionality. Most actions are performed through options. - The prepare functionality of centos-art.sh script accepts the following options: + The prepare functionality of centos-art.sh script accepts the following options:
@@ -2982,7 +3064,7 @@ locale -a | less
Description - The prepare functionality of centos-art.sh script is part of the CentOS Artwork Repository. So, in order to execute the prepare functionality of centos-art.sh script you need to have access to a working copy of CentOS Artwork Repository, first. Working copies of CentOS Artwork Repository are downloaded from the source repository and made available to you by mean of workstations. A workstation is a computer that you install and configure (prepare) to do something. In this case, you pick up a computer and prepare it for working on the CentOS Artwork Repository. + The prepare functionality of centos-art.sh script is part of the CentOS Artwork Repository. So, in order to execute the prepare functionality of centos-art.sh script you need to have access to a working copy of CentOS Artwork Repository, first. Working copies of CentOS Artwork Repository are downloaded from the source repository and made available to you by mean of workstations. A workstation is a computer that you install and configure (prepare) to do something. In this case, you pick up a computer and prepare it for working on the CentOS Artwork Repository. Installing the workstation Installing the workstation is the first step you need to do. In this step you make your computer functional through an operating system. In this case, The Community Enterprise Operating System; which is also know as The CentOS Distribution or just CentOS, for short. To install The CentOS Distribution you need to have the installation media somehow (e.g., CDs, DVDs, Pendrives, etc.). There are several different ways to perform the installation process of CentOS distribution, but generally, you put the installation media in your media reader, boot the computer from it, and follow the installer intructions. That simple. @@ -3044,16 +3126,16 @@ sudo yum install subversion ]]> Configuring the working copy - Once you have a working copy of CentOS Artwork Repository in your workstation, you can go and run the prepare functionality of centos-art.sh script to realize the remaining configuration stuff. + Once you have a working copy of CentOS Artwork Repository in your workstation, you can go and run the prepare functionality of centos-art.sh script to realize the remaining configuration stuff. Assuming this is the very first time you run the centos-art.sh script, you'll find that there is no centos-art command-line interface for it in your workstation. This is correct. In order to have the centos-art command-line in your workstation, you need to run the centos-art.sh script using its absolute path: - Assuming you've already run the prepare functionality before, there is no need for you to use the absolute path again. Instead, you can use the centos-art command-line interface directly, as the following example describes: + Assuming you've already run the prepare functionality before, there is no need for you to use the absolute path again. Instead, you can use the centos-art command-line interface directly, as the following example describes: - Notice that you can execute the prepare functionality more than once. This is specially useful to keep the link information syncronized. For example, considering you've added new brushes to or removed old brushes from your working copy of CentOS Artwork Repository, the link information related to those files need to be updated in the ~/.gimp-2.2/brushes directory too, in a way the addition/deletion change that took place in your working copy can be reflected there, as well. The same is true for other similar components like fonts, patterns and palettes components. + Notice that you can execute the prepare functionality more than once. This is specially useful to keep the link information syncronized. For example, considering you've added new brushes to or removed old brushes from your working copy of CentOS Artwork Repository, the link information related to those files need to be updated in the ~/.gimp-2.2/brushes directory too, in a way the addition/deletion change that took place in your working copy can be reflected there, as well. The same is true for other similar components like fonts, patterns and palettes components. Examples @@ -3100,11 +3182,11 @@ centos-art.sh prepare [OPTIONS] The <file>trunk/Scripts/Functions/Render</file> Directory Directories trunk Scripts Functions Render Name - The render functionlity is part of centos-art.sh script and standardizes rendition tasks inside the working copy of CentOS Artwork Repository. + The render functionlity is part of centos-art.sh script and standardizes rendition tasks inside the working copy of CentOS Artwork Repository. Synopsis - centos-art render [OPTIONS] path/to/dir + centos-art render [OPTIONS] path/to/dir The path/to/dir parameter specifies what directory structure inside the working copy of CentOS Artwork Repository you want to produce. - The render functionality of centos-art.sh script accepts the following options: + The render functionality of centos-art.sh script accepts the following options:
@@ -3162,7 +3244,7 @@ centos-art.sh prepare [OPTIONS]
Description - Inside the working copy of CentOS Artwork Repository, rendition tasks take place inside renderable directories. Inside the render functionality of centos-art.sh script, you can control rendition tasks through different flows of rendition named base-rendition, post-rendition, last-rendition and directory-specific rendition. + Inside the working copy of CentOS Artwork Repository, rendition tasks take place inside renderable directories. Inside the render functionality of centos-art.sh script, you can control rendition tasks through different flows of rendition named base-rendition, post-rendition, last-rendition and directory-specific rendition. Renderable directories In order for a directory structure to be considered renderable, it should have one directory structure for input files and one directory structure for output files. Optionally, a third directory structure might be available for storing translation files. Renderable directories are very tied to the way content is produced inside the working copy of CentOS Artwork Repository. Presently, content is produced through the following organizations: @@ -3171,24 +3253,24 @@ centos-art.sh prepare [OPTIONS] Direct rendition In direct rendition, there is one directory structure for input files (trunk/Identity/Models) and one directory structure for output files (e.g., trunk/Identity/Images). Optionally, a third directory structure is available to store the input related translation files (e.g., trunk/Locales/Identity/Models). - In direct rendition, when the render functionality of centos-art.sh script is executed, it uses the input directory structure to build a list of files to process, which is used as reference to determine the location of the translation file and the location of the output file, as well. + In direct rendition, when the render functionality of centos-art.sh script is executed, it uses the input directory structure to build a list of files to process, which is used as reference to determine the location of the translation file and the location of the output file, as well. Theme-specific rendition In theme-specific rendition, there is one directory structure to store input files (trunk/Identity/Themes/Models), one directory structure to store translation files (trunk/Locales/Identity/Themes/Models/), one directory structure to store artistic motifs (trunk/Identity/Images/Themes) and one directory structure to store output files (trunk/Identity/Images/Themes). - In theme-specific rendition, when the render functionality of centos-art.sh script is executed, it uses the input directory structure to build a list of files to process, which is used as reference to determine the location of the translation file and the location of the output file, as well. + In theme-specific rendition, when the render functionality of centos-art.sh script is executed, it uses the input directory structure to build a list of files to process, which is used as reference to determine the location of the translation file and the location of the output file, as well. In contrast with direct rendition, when we use theme-specific rendition, it is possible to combine both design models and artistic motifs to produce output in an arbitrary way. This configuration is specially interesting because it is possible to create different artistic motifs and one unique design model in order to produce one unique theme structure with different visual styles. Or the opposite, to create different theme structures and apply one unique visual style to produce one unique visual styles on different theme structure. Or even get a bit farther and experiment with arbitrary combinations among them all. - In both direct and theme-specific rendition, if the location where the output file should be stored doesn't exist, the render functionality of centos-art.sh script will create it for you. - In both direct and theme-specific rendition, if the input related translation file doesn't exist, the render functionality of centos-art.sh script will produce the output in the same language of its input file. + In both direct and theme-specific rendition, if the location where the output file should be stored doesn't exist, the render functionality of centos-art.sh script will create it for you. + In both direct and theme-specific rendition, if the input related translation file doesn't exist, the render functionality of centos-art.sh script will produce the output in the same language of its input file. The base-rendition flow - The base-rendition flow is the first rendition flow of all rendition flows available and takes place immediatly after executing the render functionality of centos-art.sh script. + The base-rendition flow is the first rendition flow of all rendition flows available and takes place immediatly after executing the render functionality of centos-art.sh script. The base-rendition produces different outputs from one unique input format. This is, one input file is used to produce one ore more output files. When translation files are available for input files, the base-rendition applies the translation file to the input file in order to produce a translated instance of it, then this translated instance is used as input file to produce one or more output files. - Inside the render functionality of centos-art.sh script, the input format is always XML (e.g., SVG, XHTML, Docbook), the translation files are always portable objects (e.g., PO) and the output format depends on the input file provided (e.g., when the input format is a SVG file, the base output is a PNG file; when the input format is XHTML the base output is an XHTML file; when the input format is a Docbook file the base output might be either HTML, RTF, PS or PDF). + Inside the render functionality of centos-art.sh script, the input format is always XML (e.g., SVG, XHTML, Docbook), the translation files are always portable objects (e.g., PO) and the output format depends on the input file provided (e.g., when the input format is a SVG file, the base output is a PNG file; when the input format is XHTML the base output is an XHTML file; when the input format is a Docbook file the base output might be either HTML, RTF, PS or PDF). As application example of base-rendition flow, consider the description of the following sections: • @@ -3309,9 +3391,9 @@ centos-art.sh prepare [OPTIONS] The <file>trunk/Scripts/Functions/Tuneup</file> Directory Directories trunk Scripts Functions Tuneup Name - The tuneup functionlity is part of centos-art.sh script and standardizes tasks related to file maintainance inside the working copy of CentOS Artwork Repository. + The tuneup functionlity is part of centos-art.sh script and standardizes tasks related to file maintainance inside the working copy of CentOS Artwork Repository. Synopsis - centos-art tuneup [OPTIONS] path/to/dir + centos-art tuneup [OPTIONS] path/to/dir The path/to/dir parameter specifies what directory structure inside the working copy of CentOS Artwork Repository you want to process. The tuneup functionality of centos-art.sh script accepts the following options: