Note
Configuration of third party repositories inside CentOS +distribution is described in CentOS wiki, specifically in the +following URL: +http://wiki.centos.org/AdditionalResources/Repositories +
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_48.html b/Manuals/en/Html/Repository/repository_48.html
index 78bc350..1849b43 100644
--- a/Manuals/en/Html/Repository/repository_48.html
+++ b/Manuals/en/Html/Repository/repository_48.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
This section exists to organize the "svg" functionality of +centos-art.sh script. +
The "svg" functionality of centos-art.sh script helps you to +maintain scalable vector graphics (SVG) inside repository. For +example, suppose you've been working in a set of (let's say 30) SVG +files, and you want to set common metadata to all of them. Doing so +file by file is a tedious task, so the centos-art.sh script provides +the "svg" functionality to aid you maintain such actions. +
+Most "svg" actions take one opening tag (e.g., `<metadata'), +and one closing tag (e.g., `</metadata') and replace everything +in-between with the information you define. The information you need +to define is inside template files as sed's replacement commands. +Template files are stored under +`trunk/Scripts/Bash/Functions/Svg/Tpl/' directory and can contain +translation markers. +
+Translation markers have the form `=SOMETEXT='. Translation +markers are used by "svg" functionalities to introduce dynamic +information (e.g., dates, keywords based on path, etc.) +
centos-art svg --update-metadata='path/to/dir'Use this command to update metadata information to all `.svg' +files under `path/to/dir' as defined in the metadata template +file. +
+centos-art svg --update-metadata='path/to/dir' --filter='filename'Use this command to update metadata information to +`path/to/dir/filename', as defined in the metadata template file. +
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_49.html b/Manuals/en/Html/Repository/repository_49.html
index 8f70f57..7902985 100644
--- a/Manuals/en/Html/Repository/repository_49.html
+++ b/Manuals/en/Html/Repository/repository_49.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
This section exists to organize the "svg" functionality of -centos-art.sh script. +
This section exists to organize files related to "verify" +functionality of `centos-art.sh' script. The "verify" +functionality of `centos-art.sh' script helps you to prepare the +workstation you are planning to use `centos-art.sh' script.
The "svg" functionality of centos-art.sh script helps you to -maintain scalable vector graphics (SVG) inside repository. For -example, suppose you've been working in a set of (let's say 30) SVG -files, and you want to set common metadata to all of them. Doing so -file by file is a tedious task, so the centos-art.sh script provides -the "svg" functionality to aid you maintain such actions. +
The first time you download CentOS Artwork Repository you need to +configure your workstation in order to use `centos-art.sh' +script. These preliminar configurations are based mainly on auxiliar +RPM packages installation, symbolic links creations, and environment +variables definitions. The "verify" functionality of +`centos-art.sh' script guides you through this preliminar +configuration process.
-Most "svg" actions take one opening tag (e.g., `<metadata'), -and one closing tag (e.g., `</metadata') and replace everything -in-between with the information you define. The information you need -to define is inside template files as sed's replacement commands. -Template files are stored under -`trunk/Scripts/Bash/Functions/Svg/Tpl/' directory and can contain -translation markers. -
-Translation markers have the form `=SOMETEXT='. Translation -markers are used by "svg" functionalities to introduce dynamic -information (e.g., dates, keywords based on path, etc.) +
If this is the first time you run centos-art command, the
+appropriate way to use its "verify" functionality is not using the
+centos-art command directly, but the absolute path to
+centos-art.sh script instead (i.e.,
+`~/artwork/trunk/Scripts/Bash/centos-art.sh'). This is necessary
+because centos-art symbolic link, under `~/bin/'
+directory, has not been created yet.
Installation of auxiliar RPM packages provides the software required
+to manipulate files inside the repository (e.g., image files,
+documentation files, translation files, script files, etc.). Most of
+RPM packages centos-art.sh script uses are shipped with
+CentOS distribution, and can be installed from CentOS base repository.
+The only exception is `inkscape', the package we use to
+manipulate SVG files. The `inkscape' package is not inside
+CentOS distribution so it needs to be installed from third party
+repositories.
+
+ +Note
Configuration of third party repositories inside CentOS +distribution is described in CentOS wiki, specifically in the +following URL: +http://wiki.centos.org/AdditionalResources/Repositories +
Before installing packages, the `centos-art.sh' script uses
+sudo to request root privileges to execute yum's
+installation functionality. If your user isn't defined as a
+privileged user--at least to run yum commands-- inside
+`/etc/sudoers' configuration file, you will not be able to
+perform package installation tasks as set in `centos-art.sh'
+script "verify" functionality.
+
Setting sudo privileges to users is an administrative task you have to
+do by yourself. If you don't have experience with sudo
+command, please read its man page running the command: man
+sudo. This reading will be very useful, and with some practice, you
+will be able to configure your users to have sudo
+privileges.
+
Creation of symbolic links helps us to alternate between different
+implementations of centos-art command-line (e.g.,
+`centos-art.sh', for Bash implementation; `centos-art.py',
+for Python implementation; `centos-art.pl', for Perl
+implementation; and so on for other implementations). The
+centos-art command-line definition takes place inside your
+personal binary (`~/bin/') directory in order to make the script
+implementation --the one that centos-art links to--
+available to PATH environment variable.
+
Creation of symbolic links helps us to reuse components from repository +working copy. For example, color information files maintained inside +your working copy must never be duplicated inside program-specific +configuration directories that uses them in your workstation (e.g., +Gimp, Inkscape, etc.). Instead, a symbolic link must be created for +each one of them, from program-specific configuration directories to +files in the working copy. In this configuration, when someone +commits changes to color information files up to central repository, +they--the changes committed-- will be immediatly available to your +programs the next time you update your working copy --the place +inside your workstation those color information files are stored--. +
+Creation of symbolic links helps us to make `centos-art.sh'
+script functionalities available outside `trunk/' repository
+directory structure, but at its same level in repository tree. This is
+useful if you need to use the "render" functionality of
+centos-art.sh under `branches/' repository directory
+structure as you usually do inside `trunk/' repository directory
+structure. As consequence of this configuration, automation scripts
+cannot be branched under `branches/Scripts' directory structure.
+
Definition of environemnt variables helps us to set default values to +our user session life. The user session environment variable defintion +takes place in the user's `~/.bash_profile' file. The "verify" +functionality of `centos-art.sh' script doesn't modify your +`~/.bash_profile' file. +
+The "verify" functionality of `centos-art.sh' script evaluates +the following environment variables: +
+The EDITOR environment variable defines your user session +default text editor. +
+If EDITOR environment variable is not set --or it uses one +value other than `/usr/bin/vim', `/usr/bin/emacs', or +`/usr/bin/nano'-- the `centos-art.sh' script uses +`/usr/bin/vim' as default text editor. +
+Default text editor is used by `centos-art.sh' script whenever it +needs to edit text-based files (e.g., subversion's pre-commit +messages, translation files, configuration files, script files, etc.) +
+The TZ environment variable defines your user session default +time zone representation. +
+Time representation inside repository server is set to Coordinated +Universal Time (UTC). Time represetation inside repository working +copies is set as their administrators personally define. +
+When repository working copies time representation be defined, it +would be a very good convention to follow if working copies +administrators would set their systems clock to use UTC. Otherwise it +would be difficult for working copies users to find out when changes +were committed up to repository server exactly in time. +
++ +Tip
Coordinated Univeral Time (UTC) representation can be +configured when you install CentOS distribution, or later in your +graphical interface using the following command: +
system-config-date +
+ +Note
If you set your system clock to use UTC representation, +you also need to set the TZ environment variable inside +`~/.bash_profile' as follows: +
export TZ=UTC +This is required in order for your terminal to display the correct +time information of your zone, taking UTC representation as reference. +
centos-art svg --update-metadata='path/to/dir'Use this command to update metadata information to all `.svg' -files under `path/to/dir' as defined in the metadata template -file. +
This command verifies required packages your workstation needs in
+order to run the centos-art command correctly. If there are
+missing packages, the `centos-art.sh' script asks you to confirm
+their installation. When installing packages, the `centos-art.sh'
+script uses the yum application in order to achieve the
+task.
+
This command verifies required links your workstation needs in order
+to run the centos-art command correctly. If there are
+missing links, the `centos-art.sh' script asks you to confirm
+their creation. When creating links, the `centos-art.sh' script
+uses the ln application in order to achieve the task.
centos-art svg --update-metadata='path/to/dir' --filter='filename'Use this command to update metadata information to -`path/to/dir/filename', as defined in the metadata template file. +
This command verifies required environment variables your workstation
+needs in order to run centos-art command correctly. If
+environment variables evaluated by `centos-art.sh' script are
+emtpy, the `centos-art.sh' script informs you about it and
+nothing else happens.
| 3.35 trunk/Scripts/Bash/Functions | + |
| [ < ] | -[ > ] | +|||||
| [ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_5.html b/Manuals/en/Html/Repository/repository_5.html
index 77f8a24..7137aad 100644
--- a/Manuals/en/Html/Repository/repository_5.html
+++ b/Manuals/en/Html/Repository/repository_5.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
-
+
| [ < ] | -[ > ] | +||||||||||||||
| [ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
This section exists to organize files related to "verify" -functionality of `centos-art.sh' script. The "verify" -functionality of `centos-art.sh' script helps you to prepare the -workstation you are planning to use `centos-art.sh' script. -
- - -The first time you download CentOS Artwork Repository you need to -configure your workstation in order to use `centos-art.sh' -script. These preliminar configurations are based mainly on auxiliar -RPM packages installation, symbolic links creations, and environment -variables definitions. The "verify" functionality of -`centos-art.sh' script guides you through this preliminar -configuration process. -
-If this is the first time you run centos-art command, the
-appropriate way to use its "verify" functionality is not using the
-centos-art command directly, but the absolute path to
-centos-art.sh script instead (i.e.,
-`~/artwork/trunk/Scripts/Bash/centos-art.sh'). This is necessary
-because centos-art symbolic link, under `~/bin/'
-directory, has not been created yet.
-
Installation of auxiliar RPM packages provides the software required
-to manipulate files inside the repository (e.g., image files,
-documentation files, translation files, script files, etc.). Most of
-RPM packages centos-art.sh script uses are shipped with
-CentOS distribution, and can be installed from CentOS base repository.
-The only exception is `inkscape', the package we use to
-manipulate SVG files. The `inkscape' package is not inside
-CentOS distribution so it needs to be installed from third party
-repositories.
-
+Note
Configuration of third party repositories inside CentOS -distribution is described in CentOS wiki, specifically in the -following URL: -http://wiki.centos.org/AdditionalResources/Repositories -
Before installing packages, the `centos-art.sh' script uses
-sudo to request root privileges to execute yum's
-installation functionality. If your user isn't defined as a
-privileged user--at least to run yum commands-- inside
-`/etc/sudoers' configuration file, you will not be able to
-perform package installation tasks as set in `centos-art.sh'
-script "verify" functionality.
-
Setting sudo privileges to users is an administrative task you have to
-do by yourself. If you don't have experience with sudo
-command, please read its man page running the command: man
-sudo. This reading will be very useful, and with some practice, you
-will be able to configure your users to have sudo
-privileges.
-
Creation of symbolic links helps us to alternate between different
-implementations of centos-art command-line (e.g.,
-`centos-art.sh', for Bash implementation; `centos-art.py',
-for Python implementation; `centos-art.pl', for Perl
-implementation; and so on for other implementations). The
-centos-art command-line definition takes place inside your
-personal binary (`~/bin/') directory in order to make the script
-implementation --the one that centos-art links to--
-available to PATH environment variable.
-
Creation of symbolic links helps us to reuse components from repository -working copy. For example, color information files maintained inside -your working copy must never be duplicated inside program-specific -configuration directories that uses them in your workstation (e.g., -Gimp, Inkscape, etc.). Instead, a symbolic link must be created for -each one of them, from program-specific configuration directories to -files in the working copy. In this configuration, when someone -commits changes to color information files up to central repository, -they--the changes committed-- will be immediatly available to your -programs the next time you update your working copy --the place -inside your workstation those color information files are stored--. -
-Creation of symbolic links helps us to make `centos-art.sh'
-script functionalities available outside `trunk/' repository
-directory structure, but at its same level in repository tree. This is
-useful if you need to use the "render" functionality of
-centos-art.sh under `branches/' repository directory
-structure as you usually do inside `trunk/' repository directory
-structure. As consequence of this configuration, automation scripts
-cannot be branched under `branches/Scripts' directory structure.
+
This command looks for `.sh' files inside Bash directory and
+extracts translatable strings from files, using xgettext
+command, in order to create a portable object template
+(`centos-art.sh.pot') file for them.
+
With the `centos-art.sh.pot' file up to date, the
+centos-art command removes the temporal list of files sotred
+inside `/tmp' directory and checks the current language of your
+user's session to create a portable object file for it, in the
+location `$CLI_LANG/$CLI_LANG.po'.
+
The CLI_LANG variable discribes the locale language used to
+output messages inside centos-art command. The locale
+language used inside centos-art command is taken from the
+LANG environment variable. The CLI_LANG variable has the
+`LL_CC' format, where `LL' is a language code from the
+ISO-639 standard, and `CC' a country code from the ISO-3166
+standard.
+
The LANG environment variable is set when you do log in to your
+system. If you are using a graphical session, change language to your
+native language and do login. That would set and exoprt the LANG
+environment variable to the correct value. On the other side, if you
+are using a text session edit your `~/.bash_profile' file to set
+and export the LANG environment variable to your native locale
+as defines the locale -a command output; do logout, and do
+login again.
+
At this point, the LANG environment variable has the appropriate
+value you need, in order to translate centos-art.sh messages
+to your native language (the one set in LANG environment
+variable).
+
With the `$CLI_LANG/$CLI_LANG.po' file up to date, the
+centos-art opens it for you to update translation strings.
+The centos-art command uses the value of EDITOR
+environment variable to determine your favorite text editor. If no
+value is defined on EDITOR, the `/usr/bin/vim' text editor
+is used as default.
+
When you finish PO file's edition and quit text editor, the
+centos-art command creates the related machine object in the
+location `$CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo'.
+
At this point, all translations you made in the PO file should be
+available to your language when runing centos-art.sh script.
Definition of environemnt variables helps us to set default values to -our user session life. The user session environment variable defintion -takes place in the user's `~/.bash_profile' file. The "verify" -functionality of `centos-art.sh' script doesn't modify your -`~/.bash_profile' file. -
-The "verify" functionality of `centos-art.sh' script evaluates -the following environment variables: -
-The EDITOR environment variable defines your user session -default text editor. -
-If EDITOR environment variable is not set --or it uses one -value other than `/usr/bin/vim', `/usr/bin/emacs', or -`/usr/bin/nano'-- the `centos-art.sh' script uses -`/usr/bin/vim' as default text editor. +
In order to make the centos-art.sh internationalization, the
+centos-art.sh script was modified as described in the
+gettext info documentation (info gettext). You
+can find such modifications in the following files:
Default text editor is used by `centos-art.sh' script whenever it -needs to edit text-based files (e.g., subversion's pre-commit -messages, translation files, configuration files, script files, etc.) -
-The TZ environment variable defines your user session default -time zone representation. -
-Time representation inside repository server is set to Coordinated -Universal Time (UTC). Time represetation inside repository working -copies is set as their administrators personally define. -
-When repository working copies time representation be defined, it -would be a very good convention to follow if working copies -administrators would set their systems clock to use UTC. Otherwise it -would be difficult for working copies users to find out when changes -were committed up to repository server exactly in time. -
-+Tip
Coordinated Univeral Time (UTC) representation can be -configured when you install CentOS distribution, or later in your -graphical interface using the following command: -
system-config-date -
-Note
If you set your system clock to use UTC representation, -you also need to set the TZ environment variable inside -`~/.bash_profile' as follows: -
export TZ=UTC -This is required in order for your terminal to display the correct -time information of your zone, taking UTC representation as reference. -
centos-art `locale-cli' action This command verifies required packages your workstation needs in
-order to run the centos-art command correctly. If there are
-missing packages, the `centos-art.sh' script asks you to confirm
-their installation. When installing packages, the `centos-art.sh'
-script uses the yum application in order to achieve the
-task.
-
This command verifies required links your workstation needs in order
-to run the centos-art command correctly. If there are
-missing links, the `centos-art.sh' script asks you to confirm
-their creation. When creating links, the `centos-art.sh' script
-uses the ln application in order to achieve the task.
-
This command verifies required environment variables your workstation
-needs in order to run centos-art command correctly. If
-environment variables evaluated by `centos-art.sh' script are
-emtpy, the `centos-art.sh' script informs you about it and
-nothing else happens.
+
Use this command to translate command-line interface output messages +in the current system locale you are using (as specified in LANG +environment variable). +
Use this command to see the command-line interface locale report.
| 3.35 trunk/Scripts/Bash/Functions | ||
| 3.33 trunk/Scripts | + |
| [ < ] | -[ > ] | +||||||
| [ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_51.html b/Manuals/en/Html/Repository/repository_51.html
index 83ba40e..5c94aef 100644
--- a/Manuals/en/Html/Repository/repository_51.html
+++ b/Manuals/en/Html/Repository/repository_51.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
| [ < ] | -[ > ] | +||||||||||||||
| [ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
This command looks for `.sh' files inside Bash directory and
-extracts translatable strings from files, using xgettext
-command, in order to create a portable object template
-(`centos-art.sh.pot') file for them.
-
With the `centos-art.sh.pot' file up to date, the
-centos-art command removes the temporal list of files sotred
-inside `/tmp' directory and checks the current language of your
-user's session to create a portable object file for it, in the
-location `$CLI_LANG/$CLI_LANG.po'.
-
The CLI_LANG variable discribes the locale language used to
-output messages inside centos-art command. The locale
-language used inside centos-art command is taken from the
-LANG environment variable. The CLI_LANG variable has the
-`LL_CC' format, where `LL' is a language code from the
-ISO-639 standard, and `CC' a country code from the ISO-3166
-standard.
-
The LANG environment variable is set when you do log in to your
-system. If you are using a graphical session, change language to your
-native language and do login. That would set and exoprt the LANG
-environment variable to the correct value. On the other side, if you
-are using a text session edit your `~/.bash_profile' file to set
-and export the LANG environment variable to your native locale
-as defines the locale -a command output; do logout, and do
-login again.
-
At this point, the LANG environment variable has the appropriate
-value you need, in order to translate centos-art.sh messages
-to your native language (the one set in LANG environment
-variable).
-
With the `$CLI_LANG/$CLI_LANG.po' file up to date, the
-centos-art opens it for you to update translation strings.
-The centos-art command uses the value of EDITOR
-environment variable to determine your favorite text editor. If no
-value is defined on EDITOR, the `/usr/bin/vim' text editor
-is used as default.
-
When you finish PO file's edition and quit text editor, the
-centos-art command creates the related machine object in the
-location `$CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo'.
-
At this point, all translations you made in the PO file should be
-available to your language when runing centos-art.sh script.
-
In order to make the centos-art.sh internationalization, the
-centos-art.sh script was modified as described in the
-gettext info documentation (info gettext). You
-can find such modifications in the following files:
-
centos-art `locale-cli' action Use this command to translate command-line interface output messages -in the current system locale you are using (as specified in LANG -environment variable). -
Use this command to see the command-line interface locale report. -
| 3.35 trunk/Scripts/Bash/Functions | - | |
| 3.33 trunk/Scripts | - |
| [ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_52.html b/Manuals/en/Html/Repository/repository_52.html
index 68ce42d..e6c7ec2 100644
--- a/Manuals/en/Html/Repository/repository_52.html
+++ b/Manuals/en/Html/Repository/repository_52.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_53.html b/Manuals/en/Html/Repository/repository_53.html
index fd587bb..bdff94d 100644
--- a/Manuals/en/Html/Repository/repository_53.html
+++ b/Manuals/en/Html/Repository/repository_53.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
The `trunk/Translations' directory exists to: +
When you create artwork for CentOS distribution you find that some +artworks need to be created for different major releases of CentOS +distribution and inside each major release they need to be created for +different locales. To get an approximate idea of how many files we are +talking about, consider the followig approximate statistic: +
In order to aliviate maintainance of artwork production for such +environment, we divided artwork production in three production lines: +
+Inside CentOS Artwork Repository, the artworks' translation production +line is stored under `trunk/Translations' directory. +
+Inside `trunk/Translations' directory, we use "translation +entries" to organize artworks' "translation files" and artworks' +"translation templates". +
-Translation entries exists for each artwork you want to produce. +Translation entries can be empty directories, or directories +containing translation files and translation templates. +
+When translation entries are empty directories, the identity entry is
+used as reference to create file names and directories layout for
+rendered files. In this case, the centos-art script takes
+one design template and outputs one non-translated file for each
+design template available. This configuration is mainly used to
+produce non-translatable artworks like themes' backgrounds.
+
When translation entries contain translation files, the translation
+entry implements the CentOS release schema and is used as reference to
+create file names and directories layout for translated artworks. In
+this case, the centos-art script applies one translation
+file to one design template to create one translated instance which is
+used to output one translated file. When the translated file is
+rendered, the centos-art script remove the previous instance
+and takes the next file in the list of translation files to repate the
+whole process once again, and so on for all files in the list. This
+configuration is mainly used to produce translatable artworks like
+Anaconda's progress slide images.
+
To find out correspondence between translation entries and identity +entries, you need to look the path of both translation entries and +identity entries. For example, if you are using the Modern's artisitic +motif, the identity entry for Anaconda progress artwork is: +
+trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress ++
and its translation entry is: +
+trunk/Translations/Identity/Themes/Distro/Anaconda/Progress ++
Note how the `Translations/' directory prefixes `Identity/' +directory, also how static values (e.g., Identity, Themes, Distro, +etc.) in the identity's entry path remain in translation's entry path, +and how variable values like theme names (e.g., Modern) are stript out +from translation's entry path. The same convenction can be applied to +other identity entries in order to determine their translation +entries, or to other translation entries to determine their identity +entries. +
++Note
Translation entries related to identity entries under +`trunk/Identity/Themes/Motifs' do not use `Motifs/' in the +path. We've done this because `trunk/Identity/Themes/Models' +structure, the other structure under `trunk/Identity/Themes', +doesn't require translation paths so far. So in the sake of saving +characters space when building translation entries for +`trunk/Identity/Themes/Motifs' structure, we organize Motifs +translation entries under `trunk/Translations/Identity/Themes/' +directly. +
+If for some reason `trunk/Identity/Themes/Models' structure +requires translation entries, we need to re-oraganize the current +directory structure accordingly. +
Translation entries, as described above, can be re-used by similar +identity entries. For example the following identity entries: +
+trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ +trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Progress/ +trunk/Identity/Themes/Motifs/Mettle/Distro/Anaconda/Progress/ ++
are all valid identity entries able to re-use translation files inside +Anaconda progress translation entry (the one shown in our example +above). This way, you can create several identity entries and maintain +just one translation entry for all of them. Once you change the +translation files inside the common translation entry, changes inside +identity entries will take effect inside the next you render them. +
+Trying to make things plain and simple: inside CentOS Artwork +Repository, graphic designers can concentrate their efforts in +artworks look and feel (the identity entries), and translators in +artworks translations (the translation entries). +
+Translation markers are used in "Theme Model Designs" and
+"Translation Files" as replacement patterns to commit content
+translation. When you are rendering content using
+centos-art script inisde `trunk/Identity' structure,
+artistic motifs and translation files are applied to model designs to
+produce translated content as result. In order to have the appropriate
+translation in content rendered, markers defintion in translation
+files should match markers in model designs exactly.
+
Figure 3.6: The image rendering flow. + +
+Translation markers can be whatever text you want, but as convenction +we use the following to represent releases of CentOS distribution: +
+Replace with minor release of CentOS distribution. In the schema M.N, the minor +release is represented by the N letter. +
Replace with major release of CentOS distribution. In the schema M.N, +the major release is represented by the M letter. +
Replace the full release of CentOS distribution. It is +`=MAJOR_RELEASE=.=MINOR_RELEASE=' basically. +
Specific translation markers convenctions are described inside +specific translation entries. Read translation entries documentation +to know more about supported translation markers. +
+Translation markers standardization creates a common point of +reference for translators and graphic designers. To have translation +markers well defined makes possible that translators and graphic +designers can work together but independently one another. +
+ + +Translation files are text files with sed's commands inside,
+replacement commands mainly. As convenction, translation file names
+end in `.sed'. Translation files are used by centos-art
+script to produce translated artworks for specific major releases of
+CentOS Distribution. There are common translation files, specific
+translation, and template translation files.
+
For example, the Firstboot artwork of CentOS distribution uses the +images `splash-small.png' and `firstboot-left.png' as based +to control its visual style. The `splash-small.png' image +contains, in its graphic design, the release number information of +CentOS distribution. So the `splash-small.png' is +release-specific. In the other hand, the `firstboot-left.png' +doesn't contain release number information. So the +`firstboot-left.png' is not release-specific. +
+If we want to produce Firstboot artwork for different major releases +of CentOS distribution, using a monolithic visual identity, all +Firstboot images should have the same visual style and, at the same +time, the release-specific information in the release-specific images. +
++ +Note
The monolithic visual identity is implemented using +theme models (see section trunk/Identity/Themes/Models) and artistic +motifs (see section trunk/Identity/Themes/Motifs). +
Assuming that both theme models and theme motifs are ready for using, +the initial translation entry to produce Firstboot artworks would look +like the following: +
+trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ +|-- Tpl +| `-- splash-small.sed +`-- firstboot-left.sed ++
With the translation entry above, centos-art command is able
+to produce the image `firstboot-left.png' only. To produce
+`splash-small.png' images for major releases (e.g., 3, 4, 5, and
+6) of CentOS distribution we need to produce the release-specific
+translation files using the centos-art script as following:
+
centos-art render --entry=/home/centos/artwork/trunk/Translations/Identity/Themes/BootUp/Firstboot --filter='3,4,5,6' ++
The above command produces the following translation entiry: +
+trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ +|-- 3 +| `-- splash-small.sed +|-- 4 +| `-- splash-small.sed +|-- 5 +| `-- splash-small.sed +|-- 6 +| `-- splash-small.sed +|-- Tpl +| `-- splash-small.sed +`-- firstboot-left.sed ++
At this point centos-art is able to produce the Firstboot
+artwork images for major releases of CentOS distribution. To add new
+release-specific translation files, run the translation rendering
+command with the release number you want to produce translation files
+for in the `--filter='release-number'' argument.
+
Template translation files are translation files stored inside
+translation template directory. Template translation files are used by
+centos-art script to produce specific translation files
+only. Template translation files may be empty or contain
+sed's replacement commands. If template translation files
+are empty files, the final specifc translation file built from it
+contains release-specific replacement commands only. For example,
+see the following translation entry:
+
trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ +|-- 3 +| `-- splash-small.sed +|-- 4 +| `-- splash-small.sed +|-- 5 +| `-- splash-small.sed +|-- 6 +| `-- splash-small.sed +|-- Tpl +| `-- splash-small.sed <-- template translation file. +`-- firstboot-left.sed ++
In the above exmaple, the `splash-small.sed' file is a template +translation file and looks like: +
+# ------------------------------------- +# $Id: splash-small.sed 94 2010-09-18 10:59:42Z al $ +# ------------------------------------- ++
In the above template translation file there are three comments lines,
+but when you render it, the centos-art adds the
+release-specific replacement commands. In our Firstboot example, after
+rendering Firstboot translation entry, the `splash-small.sed'
+translation file specific to CentOS 5, looks like the following:
+
# Warning: Do not modify this file directly. This file is created +# automatically using 'centos-art' command line interface. Any change +# you do in this file will be lost the next time you update +# translation files using 'centos-art' command line interface. If you +# want to improve the content of this translation file, improve its +# template file instead and run the 'centos-art' command line +# interface later to propagate your changes. +# ------------------------------------- +# $Id: splash-small.sed 94 2010-09-18 10:59:42Z al $ +# ------------------------------------- + +# Release number information. +s!=RELEASE=!=MAJOR_RELEASE=.=MINOR_RELEASE=!g +s!=MINOR_RELEASE=!0!g +s!=MAJOR_RELEASE=!5!g ++
If template translation files are not empty, replacement commands +inside template translation files are preserved inside +release-specific translation files. For example, consider the English +template translation file of Anaconda progress welcome slide. The +translation template directory structure looks like the following: +
+trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ +`-- Tpl + `-- en + `-- 01-welcome.sed ++
and if we render translation files for CentOS 4 and CentOS 5 major +releases, the translation entry would look like the following: +
+trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ +|-- 4 +| `-- en +| `-- 01-welcome.sed +|-- 5 +| `-- en +| `-- 01-welcome.sed +`-- Tpl + `-- en + `-- 01-welcome.sed ++
+ +Note
Release-specific translation directories preserve +template translation directory structure and file names. +
In the example above, the template translation file looks like the +following: +
+# ------------------------------------------------------------ +# $Id: 01-welcome.sed 94 2010-09-18 10:59:42Z al $ +# ------------------------------------------------------------ +s/=TITLE=/Welcome to CentOS =MAJOR_RELEASE= !/ +s/=TEXT1=/Thank you for installing CentOS =MAJOR_RELEASE=./ +s/=TEXT2=/CentOS is an enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor./ +s/=TEXT3=/CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. CentOS mainly changes packages to remove upstream vendor branding and artwork./ +s/=TEXT4=// +s/=TEXT5=// +s/=TEXT6=// +s!=URL=!http://www.centos.org/! ++
and, after render the translation entry, specific translation files +look like the following: +
+# Warning: Do not modify this file directly. This file is created +# automatically using 'centos-art' command line interface. Any change +# you do in this file will be lost the next time you update +# translation files using 'centos-art' command line interface. If you +# want to improve the content of this translation file, improve its +# template file instead and run the 'centos-art' command line +# interface later to propagate your changes. +# ------------------------------------------------------------ +# $Id: 01-welcome.sed 94 2010-09-18 10:59:42Z al $ +# ------------------------------------------------------------ + +s/=TITLE=/Welcome to CentOS =MAJOR_RELEASE= !/ +s/=TEXT1=/Thank you for installing CentOS =MAJOR_RELEASE=./ +s/=TEXT2=/CentOS is an enterprise-class Linux Distribution derived from sources freely provided to the public by a prominen t North American Enterprise Linux vendor./ +s/=TEXT3=/CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. Cent OS mainly changes packages to remove upstream vendor branding and artwork./ +s/=TEXT4=// +s/=TEXT5=// +s/=TEXT6=// +s!=URL=!http://www.centos.org/! + +# Release number information. +s!=RELEASE=!=MAJOR_RELEASE=.=MINOR_RELEASE=!g +s!=MINOR_RELEASE=!0!g +s!=MAJOR_RELEASE=!5!g ++
In the example above, relevant lines begin with the `s' word +followed by a separation character (e.g., `/', `!', etc.). +These lines have the following format: +
+s/REGEXP/REPLACEMENT/FLAGS ++
The `/' characters may be uniformly replaced by any other single
+character within any given s command. The `/'
+character (or whatever other character is used in its stead) can
+appear in the REGEXP or REPLACEMENT only if it is preceded by a
+`\' character.
+
The s command is probably the most important in
+sed and has a lot of different options. Its basic concept
+is simple: the s command attempts to match the pattern space
+against the supplied REGEXP; if the match is successful, then that
+portion of the pattern space which was matched is replaced with
+REPLACEMENT.
+
In the context of our translation files, the REGEXP is where you +define translation markers and REPLACEMENT where you define the +translation text you want to have after artworks rendering. Sometimes +we use the FLAG component with the `g' command to apply the +replacements globally. +
++ +Tip
More information about how to use
sed's +replacement commands and flags is available insed's +documentation manual. To read sed's documentation manual type the +following command: +info sed +
Inside translation files, you can use translation markers not only +inside the REGEXP but in the REPLACEMENT too. In order for this +configuration to work, the REPLACEMENT of translation markers needs to +be define after its definition. For example, see in the +release-specific translation file above, how the +`s!=MAJOR_RELASE=!5!g' replacement command is defined +after `=MAJOR_RELASE=' translation marker definition in +the REPLACEMENT of `=TITLE=' translation marker replacement +command. +
+ + +Common translation files contain common translations or no +translation at all for their related artworks. They are in the root +directory of the translation entry. Common translation files create +common artworks for all major releases of CentOS Distribution. +
+Translation entries, with common translation files inside, look like +the following: +
+trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ +|-- 3 +| `-- splash-small.sed +|-- 4 +| `-- splash-small.sed +|-- 5 +| `-- splash-small.sed +|-- 6 +| `-- splash-small.sed +|-- Tpl +| `-- splash-small.sed +`-- firstboot-left.sed <-- common translation file. ++ + +
Specific translation files contain specific translations for their
+related artworks. Specific translation files are not in the root
+directory of the translation entry, but inside directories which
+describe the type of translation they are doing. Specific translation
+files are produced automatically using the centos-art
+script.
+
trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ +|-- 3 +| `-- splash-small.sed <-- CentOS 3 specific translation file. +|-- 4 +| `-- splash-small.sed <-- CentOS 4 specific translation file. +|-- 5 +| `-- splash-small.sed <-- CentOS 5 specific translation file. +|-- 6 +| `-- splash-small.sed <-- CentOS 6 specific translation file. +|-- Tpl +| `-- splash-small.sed +`-- firstboot-left.sed ++ + +
When rendering translations, the centos-art script checks
+the translation entry to verify that it has a translation template
+directory inside. The translation template directory (`Tpl/')
+contains common translation files used to build release-specific
+translation files. If the translation template directory doesn't exist
+inside the translation entry the translation rendering fails. In this
+case the centos-art script outputs a message and quits
+script execution.
+
When the centos-art script finds a translation template
+directory inside translation entry, it looks for translations
+pre-rendering configuration scripts for that translation entry.
+Translation pre-rendering configuration scripts let you extend
+translation's default functionality (described below).
+
Translation pre-rendering configuration scripts are stored under
+`trunk/Scripts' directory, specifically under the appropriate
+language implementation. If you are using centos-art Bash's
+implementation, the translation pre-rendering scripts are store in the
+`trunk/Scripts/Bash/Config' location; if you are using
+centos-art Python's implementation, then translation
+pre-rendering scripts are stored in the
+`trunk/Scripts/Python/Config' location, and so on for other
+implementations.
+
Bash's translation pre-rendering configuration scripts look like the +following: +
+
+
+#!/bin/bash
+#
+# render_loadConfig.sh -- brief description here.
+#
+# Copyright (C) YEAR YOURNAME
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+# General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
+# USA.
+#
+# ----------------------------------------------------------------------
+# $Id: splash-small.sed 94 2010-09-18 10:59:42Z al $
+# ----------------------------------------------------------------------
+
+function render_loadConfig {
+...
+}
+
+Translation pre-rendering scripts are function scripts loaded and
+executed when rendering a translation entry. Translation pre-rendering
+scripts are loaded using the translation entry being rendered as
+reference. For example, suppose you are using the
+centos-art Bash's implementation, and you are rendering
+translations for CentOS brands, in this situation the translation
+entry would be:
+
trunk/Translations/Identity/Brands ++
and the entry inside the translation pre-rendering configuration +structure would be: +
+trunk/Scripts/Bash/Config/Identity/Brands ++
Once the centos-art script detects that translation
+pre-rendering configuration directory exists, the centos-art
+script looks for the translation pre-rendering configuration file. If
+the translation pre-rendering configuration file exists, it is loaded
+and executed. Once the translation pre-rendering configuration file
+has been executed the translation rendering process is over, and so
+the script execution.
+
+ +Note
Translation pre-rendering configuration files have the +following form: +
render.conf.extension +where `extension' refers the programming language implementation +you are using. For example, `sh' for Bash's, `py' for +Python's, `pl' for Perl's, and so on for other implementations. +
As we are using Bash implementation to describe the translation
+pre-rendering configuration example, the translation pre-rendering
+configuration file that centos-art looks for, inside the
+above translation pre-rendering configuration directory, is
+`render.conf.sh'.
+
In the other hand, if the translation pre-rendering configuration file
+doesn't exist, or it isn't written as function script, the
+centos-art script ignore translation pre-rendering
+configuration functionality and passes to render translation using
+default functionality instead.
+
The translation rendering default functionality takes template
+translation directory structure, duplicates it for each release number
+specified in the `--filter='release-number'' argument and
+produces release-specific directories. As part of template translation
+duplication process take place, the centos-art script adds
+release-specific replacement commands to each specific translation
+file inside release-specific directories. As result, specific
+translation files, inside release-specific directories, contain
+template translation replacement commands plus,
+release-specific replacement commands.
+
+ + + + +Note
Release-specific replacement commands are standardized +inside
centos-artscript using predifined release +translation markers. Release translation markers are described in the +translation marker section +(see Translation Markers). +
When `path/to/dir' refers one directory under +`trunk/Translations', this command orverwrites available +translation files using translation templates. +
+When `path/to/dir' refers one directory under +`trunk/Translations', this command renders release-specific +translation files as you specify in the `--filter='pattern'' +argument. In this case, `pattern' not a regular expression but an +number (e.g., `5') or a list of numbers separated by commas +(e.g., `3,4,5,6') that specify the major release of CentOS +distribution you want to render translations for. +
+| [ < ] | -[ > ] | +|||||
| [ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_54.html b/Manuals/en/Html/Repository/repository_54.html
index 68335c7..7bb8cd2 100644
--- a/Manuals/en/Html/Repository/repository_54.html
+++ b/Manuals/en/Html/Repository/repository_54.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
| [ < ] | -[ > ] | +||||||||||||||
| [ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
The `trunk/Translations' directory exists to: -
When you create artwork for CentOS distribution you find that some -artworks need to be created for different major releases of CentOS -distribution and inside each major release they need to be created for -different locales. To get an approximate idea of how many files we are -talking about, consider the followig approximate statistic: -
In order to aliviate maintainance of artwork production for such -environment, we divided artwork production in three production lines: -
-Inside CentOS Artwork Repository, the artworks' translation production -line is stored under `trunk/Translations' directory. -
-Inside `trunk/Translations' directory, we use "translation -entries" to organize artworks' "translation files" and artworks' -"translation templates". -
- - -Translation entries exists for each artwork you want to produce. -Translation entries can be empty directories, or directories -containing translation files and translation templates. -
-When translation entries are empty directories, the identity entry is
-used as reference to create file names and directories layout for
-rendered files. In this case, the centos-art script takes
-one design template and outputs one non-translated file for each
-design template available. This configuration is mainly used to
-produce non-translatable artworks like themes' backgrounds.
-
When translation entries contain translation files, the translation
-entry implements the CentOS release schema and is used as reference to
-create file names and directories layout for translated artworks. In
-this case, the centos-art script applies one translation
-file to one design template to create one translated instance which is
-used to output one translated file. When the translated file is
-rendered, the centos-art script remove the previous instance
-and takes the next file in the list of translation files to repate the
-whole process once again, and so on for all files in the list. This
-configuration is mainly used to produce translatable artworks like
-Anaconda's progress slide images.
-
To find out correspondence between translation entries and identity -entries, you need to look the path of both translation entries and -identity entries. For example, if you are using the Modern's artisitic -motif, the identity entry for Anaconda progress artwork is: -
-trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress --
and its translation entry is: -
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress --
Note how the `Translations/' directory prefixes `Identity/' -directory, also how static values (e.g., Identity, Themes, Distro, -etc.) in the identity's entry path remain in translation's entry path, -and how variable values like theme names (e.g., Modern) are stript out -from translation's entry path. The same convenction can be applied to -other identity entries in order to determine their translation -entries, or to other translation entries to determine their identity -entries. -
-- -Note
Translation entries related to identity entries under -`trunk/Identity/Themes/Motifs' do not use `Motifs/' in the -path. We've done this because `trunk/Identity/Themes/Models' -structure, the other structure under `trunk/Identity/Themes', -doesn't require translation paths so far. So in the sake of saving -characters space when building translation entries for -`trunk/Identity/Themes/Motifs' structure, we organize Motifs -translation entries under `trunk/Translations/Identity/Themes/' -directly. -
-If for some reason `trunk/Identity/Themes/Models' structure -requires translation entries, we need to re-oraganize the current -directory structure accordingly. -
Translation entries, as described above, can be re-used by similar -identity entries. For example the following identity entries: -
-trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ -trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Progress/ -trunk/Identity/Themes/Motifs/Mettle/Distro/Anaconda/Progress/ --
are all valid identity entries able to re-use translation files inside -Anaconda progress translation entry (the one shown in our example -above). This way, you can create several identity entries and maintain -just one translation entry for all of them. Once you change the -translation files inside the common translation entry, changes inside -identity entries will take effect inside the next you render them. -
-Trying to make things plain and simple: inside CentOS Artwork -Repository, graphic designers can concentrate their efforts in -artworks look and feel (the identity entries), and translators in -artworks translations (the translation entries). -
- - -Translation markers are used in "Theme Model Designs" and
-"Translation Files" as replacement patterns to commit content
-translation. When you are rendering content using
-centos-art script inisde `trunk/Identity' structure,
-artistic motifs and translation files are applied to model designs to
-produce translated content as result. In order to have the appropriate
-translation in content rendered, markers defintion in translation
-files should match markers in model designs exactly.
-
Figure 3.6: The image rendering flow. - -
-Translation markers can be whatever text you want, but as convenction -we use the following to represent releases of CentOS distribution: -
-Replace with minor release of CentOS distribution. In the schema M.N, the minor -release is represented by the N letter. -
Replace with major release of CentOS distribution. In the schema M.N, -the major release is represented by the M letter. -
Replace the full release of CentOS distribution. It is -`=MAJOR_RELEASE=.=MINOR_RELEASE=' basically. -
Specific translation markers convenctions are described inside -specific translation entries. Read translation entries documentation -to know more about supported translation markers. -
-Translation markers standardization creates a common point of -reference for translators and graphic designers. To have translation -markers well defined makes possible that translators and graphic -designers can work together but independently one another. -
- - -Translation files are text files with sed's commands inside,
-replacement commands mainly. As convenction, translation file names
-end in `.sed'. Translation files are used by centos-art
-script to produce translated artworks for specific major releases of
-CentOS Distribution. There are common translation files, specific
-translation, and template translation files.
-
For example, the Firstboot artwork of CentOS distribution uses the -images `splash-small.png' and `firstboot-left.png' as based -to control its visual style. The `splash-small.png' image -contains, in its graphic design, the release number information of -CentOS distribution. So the `splash-small.png' is -release-specific. In the other hand, the `firstboot-left.png' -doesn't contain release number information. So the -`firstboot-left.png' is not release-specific. -
-If we want to produce Firstboot artwork for different major releases -of CentOS distribution, using a monolithic visual identity, all -Firstboot images should have the same visual style and, at the same -time, the release-specific information in the release-specific images. -
-- -Note
The monolithic visual identity is implemented using -theme models (see section trunk/Identity/Themes/Models) and artistic -motifs (see section trunk/Identity/Themes/Motifs). -
Assuming that both theme models and theme motifs are ready for using, -the initial translation entry to produce Firstboot artworks would look -like the following: -
-trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ -|-- Tpl -| `-- splash-small.sed -`-- firstboot-left.sed --
With the translation entry above, centos-art command is able
-to produce the image `firstboot-left.png' only. To produce
-`splash-small.png' images for major releases (e.g., 3, 4, 5, and
-6) of CentOS distribution we need to produce the release-specific
-translation files using the centos-art script as following:
-
centos-art render --entry=/home/centos/artwork/trunk/Translations/Identity/Themes/BootUp/Firstboot --filter='3,4,5,6' --
The above command produces the following translation entiry: -
-trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ -|-- 3 -| `-- splash-small.sed -|-- 4 -| `-- splash-small.sed -|-- 5 -| `-- splash-small.sed -|-- 6 -| `-- splash-small.sed -|-- Tpl -| `-- splash-small.sed -`-- firstboot-left.sed --
At this point centos-art is able to produce the Firstboot
-artwork images for major releases of CentOS distribution. To add new
-release-specific translation files, run the translation rendering
-command with the release number you want to produce translation files
-for in the `--filter='release-number'' argument.
-
Template translation files are translation files stored inside
-translation template directory. Template translation files are used by
-centos-art script to produce specific translation files
-only. Template translation files may be empty or contain
-sed's replacement commands. If template translation files
-are empty files, the final specifc translation file built from it
-contains release-specific replacement commands only. For example,
-see the following translation entry:
-
trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ -|-- 3 -| `-- splash-small.sed -|-- 4 -| `-- splash-small.sed -|-- 5 -| `-- splash-small.sed -|-- 6 -| `-- splash-small.sed -|-- Tpl -| `-- splash-small.sed <-- template translation file. -`-- firstboot-left.sed --
In the above exmaple, the `splash-small.sed' file is a template -translation file and looks like: -
-# ------------------------------------- -# $Id: splash-small.sed 94 2010-09-18 10:59:42Z al $ -# ------------------------------------- --
In the above template translation file there are three comments lines,
-but when you render it, the centos-art adds the
-release-specific replacement commands. In our Firstboot example, after
-rendering Firstboot translation entry, the `splash-small.sed'
-translation file specific to CentOS 5, looks like the following:
-
# Warning: Do not modify this file directly. This file is created -# automatically using 'centos-art' command line interface. Any change -# you do in this file will be lost the next time you update -# translation files using 'centos-art' command line interface. If you -# want to improve the content of this translation file, improve its -# template file instead and run the 'centos-art' command line -# interface later to propagate your changes. -# ------------------------------------- -# $Id: splash-small.sed 94 2010-09-18 10:59:42Z al $ -# ------------------------------------- - -# Release number information. -s!=RELEASE=!=MAJOR_RELEASE=.=MINOR_RELEASE=!g -s!=MINOR_RELEASE=!0!g -s!=MAJOR_RELEASE=!5!g --
If template translation files are not empty, replacement commands -inside template translation files are preserved inside -release-specific translation files. For example, consider the English -template translation file of Anaconda progress welcome slide. The -translation template directory structure looks like the following: -
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ -`-- Tpl - `-- en - `-- 01-welcome.sed --
and if we render translation files for CentOS 4 and CentOS 5 major -releases, the translation entry would look like the following: -
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ -|-- 4 -| `-- en -| `-- 01-welcome.sed -|-- 5 -| `-- en -| `-- 01-welcome.sed -`-- Tpl - `-- en - `-- 01-welcome.sed --
- -Note
Release-specific translation directories preserve -template translation directory structure and file names. -
In the example above, the template translation file looks like the -following: -
-# ------------------------------------------------------------ -# $Id: 01-welcome.sed 94 2010-09-18 10:59:42Z al $ -# ------------------------------------------------------------ -s/=TITLE=/Welcome to CentOS =MAJOR_RELEASE= !/ -s/=TEXT1=/Thank you for installing CentOS =MAJOR_RELEASE=./ -s/=TEXT2=/CentOS is an enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor./ -s/=TEXT3=/CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. CentOS mainly changes packages to remove upstream vendor branding and artwork./ -s/=TEXT4=// -s/=TEXT5=// -s/=TEXT6=// -s!=URL=!http://www.centos.org/! --
and, after render the translation entry, specific translation files -look like the following: -
-# Warning: Do not modify this file directly. This file is created -# automatically using 'centos-art' command line interface. Any change -# you do in this file will be lost the next time you update -# translation files using 'centos-art' command line interface. If you -# want to improve the content of this translation file, improve its -# template file instead and run the 'centos-art' command line -# interface later to propagate your changes. -# ------------------------------------------------------------ -# $Id: 01-welcome.sed 94 2010-09-18 10:59:42Z al $ -# ------------------------------------------------------------ - -s/=TITLE=/Welcome to CentOS =MAJOR_RELEASE= !/ -s/=TEXT1=/Thank you for installing CentOS =MAJOR_RELEASE=./ -s/=TEXT2=/CentOS is an enterprise-class Linux Distribution derived from sources freely provided to the public by a prominen t North American Enterprise Linux vendor./ -s/=TEXT3=/CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. Cent OS mainly changes packages to remove upstream vendor branding and artwork./ -s/=TEXT4=// -s/=TEXT5=// -s/=TEXT6=// -s!=URL=!http://www.centos.org/! - -# Release number information. -s!=RELEASE=!=MAJOR_RELEASE=.=MINOR_RELEASE=!g -s!=MINOR_RELEASE=!0!g -s!=MAJOR_RELEASE=!5!g --
In the example above, relevant lines begin with the `s' word -followed by a separation character (e.g., `/', `!', etc.). -These lines have the following format: -
-s/REGEXP/REPLACEMENT/FLAGS --
The `/' characters may be uniformly replaced by any other single
-character within any given s command. The `/'
-character (or whatever other character is used in its stead) can
-appear in the REGEXP or REPLACEMENT only if it is preceded by a
-`\' character.
-
The s command is probably the most important in
-sed and has a lot of different options. Its basic concept
-is simple: the s command attempts to match the pattern space
-against the supplied REGEXP; if the match is successful, then that
-portion of the pattern space which was matched is replaced with
-REPLACEMENT.
-
In the context of our translation files, the REGEXP is where you -define translation markers and REPLACEMENT where you define the -translation text you want to have after artworks rendering. Sometimes -we use the FLAG component with the `g' command to apply the -replacements globally. -
-- -Tip
More information about how to use
sed's -replacement commands and flags is available insed's -documentation manual. To read sed's documentation manual type the -following command: -info sed -
Inside translation files, you can use translation markers not only -inside the REGEXP but in the REPLACEMENT too. In order for this -configuration to work, the REPLACEMENT of translation markers needs to -be define after its definition. For example, see in the -release-specific translation file above, how the -`s!=MAJOR_RELASE=!5!g' replacement command is defined -after `=MAJOR_RELASE=' translation marker definition in -the REPLACEMENT of `=TITLE=' translation marker replacement -command. -
- - -Common translation files contain common translations or no -translation at all for their related artworks. They are in the root -directory of the translation entry. Common translation files create -common artworks for all major releases of CentOS Distribution. -
-Translation entries, with common translation files inside, look like -the following: -
-trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ -|-- 3 -| `-- splash-small.sed -|-- 4 -| `-- splash-small.sed -|-- 5 -| `-- splash-small.sed -|-- 6 -| `-- splash-small.sed -|-- Tpl -| `-- splash-small.sed -`-- firstboot-left.sed <-- common translation file. -- - -
Specific translation files contain specific translations for their
-related artworks. Specific translation files are not in the root
-directory of the translation entry, but inside directories which
-describe the type of translation they are doing. Specific translation
-files are produced automatically using the centos-art
-script.
-
trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ -|-- 3 -| `-- splash-small.sed <-- CentOS 3 specific translation file. -|-- 4 -| `-- splash-small.sed <-- CentOS 4 specific translation file. -|-- 5 -| `-- splash-small.sed <-- CentOS 5 specific translation file. -|-- 6 -| `-- splash-small.sed <-- CentOS 6 specific translation file. -|-- Tpl -| `-- splash-small.sed -`-- firstboot-left.sed -- - -
When rendering translations, the centos-art script checks
-the translation entry to verify that it has a translation template
-directory inside. The translation template directory (`Tpl/')
-contains common translation files used to build release-specific
-translation files. If the translation template directory doesn't exist
-inside the translation entry the translation rendering fails. In this
-case the centos-art script outputs a message and quits
-script execution.
-
When the centos-art script finds a translation template
-directory inside translation entry, it looks for translations
-pre-rendering configuration scripts for that translation entry.
-Translation pre-rendering configuration scripts let you extend
-translation's default functionality (described below).
-
Translation pre-rendering configuration scripts are stored under
-`trunk/Scripts' directory, specifically under the appropriate
-language implementation. If you are using centos-art Bash's
-implementation, the translation pre-rendering scripts are store in the
-`trunk/Scripts/Bash/Config' location; if you are using
-centos-art Python's implementation, then translation
-pre-rendering scripts are stored in the
-`trunk/Scripts/Python/Config' location, and so on for other
-implementations.
-
Bash's translation pre-rendering configuration scripts look like the -following: -
-#!/bin/bash
-#
-# render_loadConfig.sh -- brief description here.
-#
-# Copyright (C) YEAR YOURNAME
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful, but
-# WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-# General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
-# USA.
-#
-# ----------------------------------------------------------------------
-# $Id: splash-small.sed 94 2010-09-18 10:59:42Z al $
-# ----------------------------------------------------------------------
-
-function render_loadConfig {
-...
-}
-
-Translation pre-rendering scripts are function scripts loaded and
-executed when rendering a translation entry. Translation pre-rendering
-scripts are loaded using the translation entry being rendered as
-reference. For example, suppose you are using the
-centos-art Bash's implementation, and you are rendering
-translations for CentOS brands, in this situation the translation
-entry would be:
-
trunk/Translations/Identity/Brands --
and the entry inside the translation pre-rendering configuration -structure would be: -
-trunk/Scripts/Bash/Config/Identity/Brands --
Once the centos-art script detects that translation
-pre-rendering configuration directory exists, the centos-art
-script looks for the translation pre-rendering configuration file. If
-the translation pre-rendering configuration file exists, it is loaded
-and executed. Once the translation pre-rendering configuration file
-has been executed the translation rendering process is over, and so
-the script execution.
-
- -Note
Translation pre-rendering configuration files have the -following form: -
render.conf.extension -where `extension' refers the programming language implementation -you are using. For example, `sh' for Bash's, `py' for -Python's, `pl' for Perl's, and so on for other implementations. -
As we are using Bash implementation to describe the translation
-pre-rendering configuration example, the translation pre-rendering
-configuration file that centos-art looks for, inside the
-above translation pre-rendering configuration directory, is
-`render.conf.sh'.
-
In the other hand, if the translation pre-rendering configuration file
-doesn't exist, or it isn't written as function script, the
-centos-art script ignore translation pre-rendering
-configuration functionality and passes to render translation using
-default functionality instead.
-
The translation rendering default functionality takes template
-translation directory structure, duplicates it for each release number
-specified in the `--filter='release-number'' argument and
-produces release-specific directories. As part of template translation
-duplication process take place, the centos-art script adds
-release-specific replacement commands to each specific translation
-file inside release-specific directories. As result, specific
-translation files, inside release-specific directories, contain
-template translation replacement commands plus,
-release-specific replacement commands.
-
- -Note
Release-specific replacement commands are standardized -inside
centos-artscript using predifined release -translation markers. Release translation markers are described in the -translation marker section -(see Translation Markers). -
When `path/to/dir' refers one directory under -`trunk/Translations', this command orverwrites available -translation files using translation templates. -
-When `path/to/dir' refers one directory under -`trunk/Translations', this command renders release-specific -translation files as you specify in the `--filter='pattern'' -argument. In this case, `pattern' not a regular expression but an -number (e.g., `5') or a list of numbers separated by commas -(e.g., `3,4,5,6') that specify the major release of CentOS -distribution you want to render translations for. -
-| 3.53 trunk/Translations/Identity/Brands | + | |
| 3.52 trunk/Translations/Identity/Brands | + | |
| 3.54 trunk/Translations/Identity/Fonts | ||
| 3.55 trunk/Translations/Identity/Fonts | + | |
| 3.55 trunk/Translations/Identity/Models | ||
| 3.56 trunk/Translations/Identity/Models | + | |
| 3.56 trunk/Translations/Identity/Release | ||
| 3.57 trunk/Translations/Identity/Release | + | |
| 3.57 trunk/Translations/Identity/Themes | ||
| 3.58 trunk/Translations/Identity/Themes | + | |
| 3.60 trunk/Translations/Identity/Widgets | ||
| 3.1 trunk/Identity | [ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_55.html b/Manuals/en/Html/Repository/repository_55.html
index bcbb2b5..9c549b9 100644
--- a/Manuals/en/Html/Repository/repository_55.html
+++ b/Manuals/en/Html/Repository/repository_55.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
Translation files, inside `trunk/Translations/Identity/Brands' +translation entry, don't use default rendering translation +functionality, they use the following translation pre-rendering +configuration file instead: +
+/home/centos/artwork/trunk/Translation/Identity/Brands/render.conf.sh ++
Inside `trunk/Translations/Identity/Brands' translation entry, +translation files are symbolic links pointing to the common template +translation structure, inside the translation template (`Tpl/') +directory. +
+Inside `trunk/Translations/Identity/Brands' translation entry, +translation files are created using identity design templates as +reference. The translation pre-rendering script creates a translation +structure where the translation template (`Tpl/') directory +structure applies to each single design template available. +
+For example, if the brands' translation template (`Tpl/')
+directory has 30 translation files, and there are 20 design templates;
+the brands' translation pre-rendering script creates a translation
+structure of symbolic links where the 30 translation files apply the
+20 design templates one by one, producing 600 translation symbolic
+links as result. At this point, when rendering identity, the
+centos-art script considers translation symbolic links as
+translation files.
+
Translation file names, inside brands' translation template +(`Tpl') directory have special meaning: +
-Convenctional file names look like `blue.sed', `2c-a.sed', +etc. Replacement commands inside translation file are applied to +design templates and translation file names are used as final image +name. The image dimensions use the same dimensions that design +template has. +
+Numeric file names look like `300.sed', `200.sed', etc. +Replacements commands inside translation files are applied to design +templates, and translation file names are used as final image name. +The final image is saved using an specific `width' defined by the +number part of the translation file name. The image `height' is +automatically scaled based on the previous `width' definition to +maintain the design's ratio. +
+For example, if your design template has 400x200 pixels of dimension, +and you apply a translation file named `300.sed' to it, the final +image you get as result will have 300x100 pixels of dimension. The +same is true if you use higher numbers like `1024.sed', `2048.sed', +etc. In these cases you have bigger images proportionally. +
+As we are using scalable vector graphics to design identity templates, +the image size you produce is not limitted in size. You can use one +design template produced in 400x200 pixels to produce larger or +shorter PNG images using numeric translation files as described +above. +
+ + +Inside `trunk/Translations/Identity/Brands/', translation files +combine the following translation markers: +
+Specify which color to use when rendering brand images. +
++Note
As translation files inside +`trunk/Translations/Identity/Brands' are symbolic links that +point to template translation files, translation markers are defined +inside template translation files. +
To render brands' translation files, use the following command: +
+centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands ++ +
| [ < ] | -[ > ] | +|||||
| [ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_56.html b/Manuals/en/Html/Repository/repository_56.html
index 3fdecdc..354c16b 100644
--- a/Manuals/en/Html/Repository/repository_56.html
+++ b/Manuals/en/Html/Repository/repository_56.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
| [ < ] | -[ > ] | +||||||||||||||
| [ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
Translation files, inside `trunk/Translations/Identity/Brands' -translation entry, don't use default rendering translation -functionality, they use the following translation pre-rendering -configuration file instead: -
-/home/centos/artwork/trunk/Translation/Identity/Brands/render.conf.sh --
Inside `trunk/Translations/Identity/Brands' translation entry, -translation files are symbolic links pointing to the common template -translation structure, inside the translation template (`Tpl/') -directory. -
-Inside `trunk/Translations/Identity/Brands' translation entry, -translation files are created using identity design templates as -reference. The translation pre-rendering script creates a translation -structure where the translation template (`Tpl/') directory -structure applies to each single design template available. -
-For example, if the brands' translation template (`Tpl/')
-directory has 30 translation files, and there are 20 design templates;
-the brands' translation pre-rendering script creates a translation
-structure of symbolic links where the 30 translation files apply the
-20 design templates one by one, producing 600 translation symbolic
-links as result. At this point, when rendering identity, the
-centos-art script considers translation symbolic links as
-translation files.
-
Translation file names, inside brands' translation template -(`Tpl') directory have special meaning: -
- + -Convenctional file names look like `blue.sed', `2c-a.sed', -etc. Replacement commands inside translation file are applied to -design templates and translation file names are used as final image -name. The image dimensions use the same dimensions that design -template has. -
-Numeric file names look like `300.sed', `200.sed', etc. -Replacements commands inside translation files are applied to design -templates, and translation file names are used as final image name. -The final image is saved using an specific `width' defined by the -number part of the translation file name. The image `height' is -automatically scaled based on the previous `width' definition to -maintain the design's ratio. -
-For example, if your design template has 400x200 pixels of dimension, -and you apply a translation file named `300.sed' to it, the final -image you get as result will have 300x100 pixels of dimension. The -same is true if you use higher numbers like `1024.sed', `2048.sed', -etc. In these cases you have bigger images proportionally. -
-As we are using scalable vector graphics to design identity templates, -the image size you produce is not limitted in size. You can use one -design template produced in 400x200 pixels to produce larger or -shorter PNG images using numeric translation files as described -above. -
+Inside `trunk/Translations/Identity/Brands/', translation files -combine the following translation markers: -
-Specify which color to use when rendering brand images. -
--Note
As translation files inside -`trunk/Translations/Identity/Brands' are symbolic links that -point to template translation files, translation markers are defined -inside template translation files. -
To render brands' translation files, use the following command: -
-centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands -
| 3.54 trunk/Translations/Identity/Brands/Tpl | - | |
| 3.2 trunk/Identity/Brands | - |
| [ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_57.html b/Manuals/en/Html/Repository/repository_57.html
index fde680c..e292962 100644
--- a/Manuals/en/Html/Repository/repository_57.html
+++ b/Manuals/en/Html/Repository/repository_57.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
Translation files, inside `trunk/Translations/Fonts', have the +following structure: +
+# ---------------------------------------------------------------------- +# $Id: Fonts.texi 29 2010-09-12 05:32:26Z al $ +# ---------------------------------------------------------------------- + +s!font-family:Denmark!font-family:DejaVu LGC Sans! +s!font-weight:normal!font-weight:bold! +s!font-style:normal!font-style:italic! ++
Inside `trunk/Translations/Fonts', there is one translation file +for each font preview image you want to produce. This way, we create +one translation file for each font-family we use somewhere inside +CentOS visual identity. +
++ -Important
Do not create translation files for font-families +not used somewhere inside CentOS visual identity. The font's identity +entry (see section trunk/Identity/Fonts) is used as reference when someone +needs to know which font-families are allowed to use inside CentOS +visual identity. +
Inside `trunk/Translations/Identity/Fonts', translation files +combine the following translation markers: +
+Specify which font family to use when rendering font preview images. +
Specify which font weight to use when rendering font preview images. +
Specify which font style to use when rendering font preview images. +
Inside `trunk/Translations/Fonts' you use your favorite text
+editor to create translation files. Inside
+`trunk/Translations/Fonts' there is not translation template
+directory (`Tpl/'), nor translation rendering using
+centos-art script. For example, to create the
+`dejavu_lgc_sans-boldoblique.sed' translation file using
+vim editor, type the following command:
+
vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed ++ +
| 3.3 trunk/Identity/Fonts | + |
| [ < ] | -[ > ] | +|||||
| [ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_58.html b/Manuals/en/Html/Repository/repository_58.html
index 3c62da6..feec7cc 100644
--- a/Manuals/en/Html/Repository/repository_58.html
+++ b/Manuals/en/Html/Repository/repository_58.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
| [ < ] | -[ > ] | +||||||||||||||
| [ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
Translation files, inside `trunk/Translations/Fonts', have the -following structure: -
-# ---------------------------------------------------------------------- -# $Id: Fonts.texi 29 2010-09-12 05:32:26Z al $ -# ---------------------------------------------------------------------- - -s!font-family:Denmark!font-family:DejaVu LGC Sans! -s!font-weight:normal!font-weight:bold! -s!font-style:normal!font-style:italic! --
Inside `trunk/Translations/Fonts', there is one translation file -for each font preview image you want to produce. This way, we create -one translation file for each font-family we use somewhere inside -CentOS visual identity. -
-+Important
Do not create translation files for font-families -not used somewhere inside CentOS visual identity. The font's identity -entry (see section trunk/Identity/Fonts) is used as reference when someone -needs to know which font-families are allowed to use inside CentOS -visual identity. -
Inside `trunk/Translations/Identity/Fonts', translation files -combine the following translation markers: -
-Specify which font family to use when rendering font preview images. -
Specify which font weight to use when rendering font preview images. -
Specify which font style to use when rendering font preview images. -
Inside `trunk/Translations/Fonts' you use your favorite text
-editor to create translation files. Inside
-`trunk/Translations/Fonts' there is not translation template
-directory (`Tpl/'), nor translation rendering using
-centos-art script. For example, to create the
-`dejavu_lgc_sans-boldoblique.sed' translation file using
-vim editor, type the following command:
-
vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed -
| 3.3 trunk/Identity/Fonts | - |
| [ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_59.html b/Manuals/en/Html/Repository/repository_59.html
index 60a3294..169f1e9 100644
--- a/Manuals/en/Html/Repository/repository_59.html
+++ b/Manuals/en/Html/Repository/repository_59.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_6.html b/Manuals/en/Html/Repository/repository_6.html
index 278e949..899492a 100644
--- a/Manuals/en/Html/Repository/repository_6.html
+++ b/Manuals/en/Html/Repository/repository_6.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
-
+
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_61.html b/Manuals/en/Html/Repository/repository_61.html
index 086a10e..dadd0ba 100644
--- a/Manuals/en/Html/Repository/repository_61.html
+++ b/Manuals/en/Html/Repository/repository_61.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_62.html b/Manuals/en/Html/Repository/repository_62.html
index 2ffedec..f8e4ea3 100644
--- a/Manuals/en/Html/Repository/repository_62.html
+++ b/Manuals/en/Html/Repository/repository_62.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
Use the following command to produce translation files based: +
+trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +`-- Tpl + |-- en + | |-- 01-welcome.sed + | |-- 02-donate.sed + | `-- 03-yum.sed + `-- es + |-- 01-welcome.sed + |-- 02-donate.sed + `-- 03-yum.sed + |
In order to produce the slide images in PNG format we need to have the +translation files first. So we use the following commands to create +translation files for CentOS 3, 4, and 5 major releases: +
+centos-art render --translation --filter='3,4,5' + |
The above commands will produce the following translation structure: +
+trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +|-- 3 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +|-- 4 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +|-- 5 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +`-- Tpl + |-- en + | |-- 01-welcome.sed + | |-- 02-donate.sed + | `-- 03-yum.sed + `-- es + |-- 01-welcome.sed + |-- 02-donate.sed + `-- 03-yum.sed + |
At this point we have all the translation files we need to produce +Anaconda progress welcome, donate and yum slides images; in English +and Spanish languages; for CentOS 3, CentOS 4, and CentOS 5. That is, +a sum of 18 images around. +
+Now, with translation files in place, let's move to +`trunk/Identity' structure and render them. +
Translation rendering is described in `trunk/Translations' +documentation entry (see section trunk/Translations). +
| [ < ] | [ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_63.html b/Manuals/en/Html/Repository/repository_63.html
index 924210e..e5fc687 100644
--- a/Manuals/en/Html/Repository/repository_63.html
+++ b/Manuals/en/Html/Repository/repository_63.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
Use the following command to produce translation files based: -
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress -`-- Tpl - |-- en - | |-- 01-welcome.sed - | |-- 02-donate.sed - | `-- 03-yum.sed - `-- es - |-- 01-welcome.sed - |-- 02-donate.sed - `-- 03-yum.sed - |
In order to produce the slide images in PNG format we need to have the -translation files first. So we use the following commands to create -translation files for CentOS 3, 4, and 5 major releases: -
-centos-art render --translation --filter='3,4,5' - |
The above commands will produce the following translation structure: -
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress -|-- 3 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -|-- 4 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -|-- 5 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -`-- Tpl - |-- en - | |-- 01-welcome.sed - | |-- 02-donate.sed - | `-- 03-yum.sed - `-- es - |-- 01-welcome.sed - |-- 02-donate.sed - `-- 03-yum.sed - |
At this point we have all the translation files we need to produce -Anaconda progress welcome, donate and yum slides images; in English -and Spanish languages; for CentOS 3, CentOS 4, and CentOS 5. That is, -a sum of 18 images around. -
-Now, with translation files in place, let's move to -`trunk/Identity' structure and render them. -
Translation rendering is described in `trunk/Translations' -documentation entry (see section trunk/Translations). -
+| 3.60 trunk/Translations/Identity/Widgets | + |
| [ < ] | @@ -179,11 +118,11 @@ documentation entry (see section trunk/Trans[ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on October, 30 2010 using texi2html 1.76.
+ This document was generated on October, 31 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_64.html b/Manuals/en/Html/Repository/repository_64.html
index 4d932bf..29d946b 100644
--- a/Manuals/en/Html/Repository/repository_64.html
+++ b/Manuals/en/Html/Repository/repository_64.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
| [ < ] | -[ > ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
