diff --git a/Automation/Manuals/Locales/en_US/centos-art.sh.po b/Automation/Manuals/Locales/en_US/centos-art.sh.po new file mode 100644 index 0000000..7875450 --- /dev/null +++ b/Automation/Manuals/Locales/en_US/centos-art.sh.po @@ -0,0 +1,308 @@ +msgid "" +msgstr "" +"Project-Id-Version: centos-art.sh.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-07 00:08-0500\n" +"PO-Revision-Date: 2013-11-07 00:08-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "centos-art.sh" +msgstr "centos-art.sh" + +msgid "1" +msgstr "1" + +msgid "The CentOS artwork repository automation tool." +msgstr "The CentOS artwork repository automation tool." + +msgid "" +"centos-art.sh [--help|--version]" +msgstr "" +"centos-art.sh [--help|--version]" + +msgid "" +"Print information about centos-art.sh script itself." +msgstr "" +"Print information about centos-art.sh script itself." + +msgid "" +"centos-art.shMODULE [--help|--" +"version]" +msgstr "" +"centos-art.shMODULE [--help|--" +"version]" + +msgid "" +"Print information about the specified module. See below to see which modules centos-art.sh script supports." +msgstr "" +"Print information about the specified module. See below to see which modules centos-art.sh script supports." + +msgid "Description" +msgstr "Description" + +msgid "" +"centos-art.sh exists to " +"standardize frequent tasks inside the CentOS artwork repository. " +"Inside centos-art.sh script, " +"frequent tasks are organized inside modules." +msgstr "" +"centos-art.sh exists to " +"standardize frequent tasks inside the CentOS artwork repository. " +"Inside centos-art.sh script, " +"frequent tasks are organized inside modules." + +msgid "" +"When you execute the centos-art.sh script in a terminal, it requests you to enter the " +"absolute path of CentOS artwork repository in your workstation. " +"This information is required in order for centos-art.sh to know where the repository directory " +"structure you want to work with is stored in. Later, once centos-art.sh knows where your copy of " +"CentOS artwork repository is stored in, it initializes " +"configuration variables and global functions. At this point, it " +"continues reading the command-line arguments to retrieve the " +"module's name, process common options next to it, store module-" +"specific options and initiates the module's environment by " +"executing the module's initialization script, based on the module's " +"name retrieved from the command-line." +msgstr "" +"When you execute the centos-art.sh script in a terminal, it requests you to enter the " +"absolute path of CentOS artwork repository in your workstation. " +"This information is required in order for centos-art.sh to know where the repository directory " +"structure you want to work with is stored in. Later, once centos-art.sh knows where your copy of " +"CentOS artwork repository is stored in, it initializes " +"configuration variables and global functions. At this point, it " +"continues reading the command-line arguments to retrieve the " +"module's name, process common options next to it, store module-" +"specific options and initiates the module's environment by " +"executing the module's initialization script, based on the module's " +"name retrieved from the command-line." + +msgid "Modules" +msgstr "Modules" + +msgid "" +"The centos-art.sh script " +"supports the following modules:" +msgstr "" +"The centos-art.sh script " +"supports the following modules:" + +msgid "prepare" +msgstr "prepare" + +msgid "" +"Standardize configuration tasks needed by your working copy (e.g., " +"verify whether required packages are installed or not in your " +"workstation, calls render module to produce images and manuals in " +"the correct order). This is the first task you should run in your " +"workstation, just after downloading a fresh working copy of CentOS " +"artwork repository." +msgstr "" +"Standardize configuration tasks needed by your working copy (e.g., " +"verify whether required packages are installed or not in your " +"workstation, calls render module to produce images and manuals in " +"the correct order). This is the first task you should run in your " +"workstation, just after downloading a fresh working copy of CentOS " +"artwork repository." + +msgid "render" +msgstr "render" + +msgid "" +"Standardize the way content is produced inside the repository. This " +"function relies on configuration files to do its work. Whenever you " +"need to produce images, documentation or localized content this is " +"the module you'll need to use." +msgstr "" +"Standardize the way content is produced inside the repository. This " +"function relies on configuration files to do its work. Whenever you " +"need to produce images, documentation or localized content this is " +"the module you'll need to use." + +msgid "locale" +msgstr "locale" + +msgid "" +"Standardize the way translatable strings are retrieved from source " +"files and put into portable objects for you to edit. Portable " +"objects produced by this module are used by render module to produce localized content. Whenever " +"you need to produce the intermediate files holding the translatable " +"strings required to produce localized content, use this module." +msgstr "" +"Standardize the way translatable strings are retrieved from source " +"files and put into portable objects for you to edit. Portable " +"objects produced by this module are used by render module to produce localized content. Whenever " +"you need to produce the intermediate files holding the translatable " +"strings required to produce localized content, use this module." + +msgid "tuneup" +msgstr "tuneup" + +msgid "" +"Standardize maintenance tasks frequently run inside the repository " +"(e.g., reset written by, copyright and license information inside " +"shell script's top-comments; transform probably malformed HTML " +"documents into valid documents, and remove unused tags inside SVG " +"documents.)." +msgstr "" +"Standardize maintenance tasks frequently run inside the repository " +"(e.g., reset written by, copyright and license information inside " +"shell script's top-comments; transform probably malformed HTML " +"documents into valid documents, and remove unused tags inside SVG " +"documents.)." + +msgid "Options" +msgstr "Options" + +msgid "" +"The centos-art.sh script " +"supports the following options:" +msgstr "" +"The centos-art.sh script " +"supports the following options:" + +msgid "--help" +msgstr "--help" + +msgid "Print script documentation." +msgstr "Print script documentation." + +msgid "--version" +msgstr "--version" + +msgid "Print script version." +msgstr "Print script version." + +msgid "--debug" +msgstr "--debug" + +msgid "" +"Run the script in debugging mode. This option is very useful if you " +"want to get a closer look to the way modules are opened and closed " +"inside centos-art.sh script." +msgstr "" +"Run the script in debugging mode. This option is very useful if you " +"want to get a closer look to the way modules are opened and closed " +"inside centos-art.sh script." + +msgid "--quiet" +msgstr "--quiet" + +msgid "" +"Run the script quietly. This option reduces the amount of " +"information the centos-art.sh " +"script prints out when processing source files." +msgstr "" +"Run the script quietly. This option reduces the amount of " +"information the centos-art.sh " +"script prints out when processing source files." + +msgid "--yes" +msgstr "--yes" + +msgid "" +"Run the script in affirmative mode. This is answering “yes” to all " +"“yes or no” questions. This option is useful when you run centos-art.sh with the --quiet option." +msgstr "" +"Run the script in affirmative mode. This is answering “yes” to all " +"“yes or no” questions. This option is useful when you run centos-art.sh with the --quiet option." + +msgid "Exit Status" +msgstr "Exit Status" + +msgid "0 — Exit successfully without errors." +msgstr "0 — Exit successfully without errors." + +msgid "1 — Exit with errors." +msgstr "1 — Exit with errors." + +msgid "Bugs" +msgstr "Bugs" + +msgid "https://centos.org.cu/bugs/" +msgstr "https://centos.org.cu/bugs/" + +msgid "Author" +msgstr "Author" + +msgid "" +"The centos-art.sh script has " +"received contribution from the following people:" +msgstr "" +"The centos-art.sh script has " +"received contribution from the following people:" + +msgid "" +"Alain Reguera Delgado <al@centos.org.cu>, 2009-2013" +msgstr "" +"Alain Reguera Delgado <al@centos.org.cu>, 2009-2013" + +msgid "Copyright" +msgstr "Copyright" + +msgid "Copyright © 2009-2013 The CentOS Artwork SIG" +msgstr "Copyright © 2009-2013 The CentOS Artwork SIG" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." +msgstr "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Manuals/Locales/en_US/tcar_setModuleEnvironment.sh.po b/Automation/Manuals/Locales/en_US/tcar_setModuleEnvironment.sh.po new file mode 100644 index 0000000..aaa9567 --- /dev/null +++ b/Automation/Manuals/Locales/en_US/tcar_setModuleEnvironment.sh.po @@ -0,0 +1,223 @@ +msgid "" +msgstr "" +"Project-Id-Version: tcar_setModuleEnvironment.sh.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-07 00:08-0500\n" +"PO-Revision-Date: 2013-11-07 00:08-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "tcar_setmoduleenvironment.sh" +msgstr "tcar_setmoduleenvironment.sh" + +msgid "1" +msgstr "1" + +msgid "tcar_setModuleEnvironment.sh" +msgstr "tcar_setModuleEnvironment.sh" + +msgid "Initiate module environments." +msgstr "Initiate module environments." + +msgid "" +"tcar_setModuleEnvironment [-m \"MODULE_NAME\"] [-t \"MODULE_TYPE\"] " +"[-g MODULE_ARGUMENT] …" +msgstr "" +"tcar_setModuleEnvironment [-m \"MODULE_NAME\"] [-t \"MODULE_TYPE\"] " +"[-g MODULE_ARGUMENT] …" + +msgid "Description" +msgstr "Description" + +msgid "Options" +msgstr "Options" + +msgid "" +"The tcar_setModuleEnvironment " +"function accepts the following options:" +msgstr "" +"The tcar_setModuleEnvironment " +"function accepts the following options:" + +msgid "-m" +msgstr "-m" + +msgid "This option specifies the name of the module you want to load." +msgstr "" +"This option specifies the name of the module you want to load." + +msgid "-t" +msgstr "-t" + +msgid "" +"This option specifies the type of the module you want to load. " +"Modules can be one of the following types:" +msgstr "" +"This option specifies the type of the module you want to load. " +"Modules can be one of the following types:" + +msgid "top-module" +msgstr "top-module" + +msgid "" +"This modules are stored in the first level of Modules directory. " +"This type of modules initiate module environments for specific " +"tasks so it can be called from anywhere inside centos-art.sh script." +msgstr "" +"This modules are stored in the first level of Modules directory. " +"This type of modules initiate module environments for specific " +"tasks so it can be called from anywhere inside centos-art.sh script." + +msgid "sub-module" +msgstr "sub-module" + +msgid "" +"This modules are stored from the second-level of Modules directory " +"on. This type of modules can be executed from top-modules, sub-" +"modules, or sib-modules but never the centos-art.sh file itself." +msgstr "" +"This modules are stored from the second-level of Modules directory " +"on. This type of modules can be executed from top-modules, sub-" +"modules, or sib-modules but never the centos-art.sh file itself." + +msgid "sib-module" +msgstr "sib-module" + +msgid "" +"This modules are stored from the second-level of Modules directory " +"on. This type of modules can be executed from sub-modules or sib-" +"modules, but never top-modules or the centos-art.sh file itself." +msgstr "" +"This modules are stored from the second-level of Modules directory " +"on. This type of modules can be executed from sub-modules or sib-" +"modules, but never top-modules or the centos-art.sh file itself." + +msgid "-g" +msgstr "-g" + +msgid "" +"This option specifies the module-specific option you want to pass " +"for processing in the module environment you are about to execute. " +"Generally, module-specific options are passed through centos-art.sh command-line but you may " +"need to pass them internally in some cases (e.g., you are executing " +"a top-module from a sub-module). If you need to pass more than one " +"option, then you need to put the -g option before each option you " +"want to pass." +msgstr "" +"This option specifies the module-specific option you want to pass " +"for processing in the module environment you are about to execute. " +"Generally, module-specific options are passed through centos-art.sh command-line but you may " +"need to pass them internally in some cases (e.g., you are executing " +"a top-module from a sub-module). If you need to pass more than one " +"option, then you need to put the -g option before each option you " +"want to pass." + +msgid "Bugs" +msgstr "Bugs" + +msgid "" +"In the very beginning of tcar_setModuleEnvironment function, it used just non-" +"array variables and it worked fine for top-module and sub-module " +"processing, however when it was needed to do sibling processing, it " +"didn't work as expected. The failure was produced because a wrong " +"variable assignment when tried to set the path of the next module " +"to load. There was not a clean way to “remember” what was the base " +"directory of the parent directory, so it ended up using the last " +"loaded module base directory which made impossible to load a " +"sibling module. The tcar_setModuleEnvironment function as implemented in " +"version 0.5 of The CentOS Artwork Repository, fixes this issue " +"replacing non-array variables by array variables which can remember " +"module information." +msgstr "" +"In the very beginning of tcar_setModuleEnvironment function, it used just non-" +"array variables and it worked fine for top-module and sub-module " +"processing, however when it was needed to do sibling processing, it " +"didn't work as expected. The failure was produced because a wrong " +"variable assignment when tried to set the path of the next module " +"to load. There was not a clean way to “remember” what was the base " +"directory of the parent directory, so it ended up using the last " +"loaded module base directory which made impossible to load a " +"sibling module. The tcar_setModuleEnvironment function as implemented in " +"version 0.5 of The CentOS Artwork Repository, fixes this issue " +"replacing non-array variables by array variables which can remember " +"module information." + +msgid "" +"See also: https://centos." +"org.cu/bugs/" +msgstr "" +"See also: https://centos." +"org.cu/bugs/" + +msgid "Author" +msgstr "Author" + +msgid "" +"The centos-art.sh script has " +"received contribution from the following people:" +msgstr "" +"The centos-art.sh script has " +"received contribution from the following people:" + +msgid "" +"Alain Reguera Delgado <al@centos.org.cu>, 2009-2013" +msgstr "" +"Alain Reguera Delgado <al@centos.org.cu>, 2009-2013" + +msgid "Copyright" +msgstr "Copyright" + +msgid "Copyright © 2009-2013 The CentOS Artwork SIG" +msgstr "Copyright © 2009-2013 The CentOS Artwork SIG" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." +msgstr "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Manuals/Understanding_Modules/Locales/en_US/understanding_modules.asciidoc.po b/Automation/Manuals/Understanding_Modules/Locales/en_US/understanding_modules.asciidoc.po new file mode 100644 index 0000000..8e5cef6 --- /dev/null +++ b/Automation/Manuals/Understanding_Modules/Locales/en_US/understanding_modules.asciidoc.po @@ -0,0 +1,2127 @@ +msgid "" +msgstr "" +"Project-Id-Version: understanding_modules.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-07 14:18-0500\n" +"PO-Revision-Date: 2013-11-07 14:18-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "Understanding Modules" +msgstr "Understanding Modules" + +msgid "Oct 2013" +msgstr "Oct 2013" + +msgid "Alain" +msgstr "Alain" + +msgid "Reguera" +msgstr "Reguera" + +msgid "Delgado" +msgstr "Delgado" + +msgid "al@centos.org.cu" +msgstr "al@centos.org.cu" + +msgid "ARD" +msgstr "ARD" + +msgid "0.1" +msgstr "0.1" + +msgid "Overview" +msgstr "Overview" + +msgid "" +"From version 0.5, the centos-art.sh script introduces the idea of modules to its base design. " +"Modules are a collection of functions written in Bash that can call " +"one another to create individual execution environments. They may " +"be nested to achieve high levels of maintainability and " +"extensibility. This make possible for modules writers to divide " +"complicated tasks into smaller tasks that can be easier to debug, " +"maintain and share with other modules efficiently (e.g., instead of " +"loading modules all at once, they are only loaded at demand and " +"unset once they conclude their execution)." +msgstr "" +"From version 0.5, the centos-art.sh script introduces the idea of modules to its base design. " +"Modules are a collection of functions written in Bash that can call " +"one another to create individual execution environments. They may " +"be nested to achieve high levels of maintainability and " +"extensibility. This make possible for modules writers to divide " +"complicated tasks into smaller tasks that can be easier to debug, " +"maintain and share with other modules efficiently (e.g., instead of " +"loading modules all at once, they are only loaded at demand and " +"unset once they conclude their execution)." + +msgid "" +"This article describes the modular design of centos-art.sh script. It is a good place for you to " +"start if you are planning to contribute new module environments to " +"centos-art.sh script or want " +"to know more about how it works. The next section delves into what " +"a module environment is, the three module types you can find in it " +"and the correct way of execute each one of them." +msgstr "" +"This article describes the modular design of centos-art.sh script. It is a good place for you to " +"start if you are planning to contribute new module environments to " +"centos-art.sh script or want " +"to know more about how it works. The next section delves into what " +"a module environment is, the three module types you can find in it " +"and the correct way of execute each one of them." + +msgid "Module Environment" +msgstr "Module Environment" + +msgid "" +"When you execute the centos-art.sh script you create an execution environment in which " +"variables and functions are defined. The execution environment is " +"the higher environment inside centos-art." +"sh script. It is considered to have a “global” scope, so " +"variables and functions defined in it are always available for any " +"function execution made from it. You can control the execution " +"environment of centos-art.sh " +"script through files centos-art.sh and " +"centos-art.conf.sh. These files don't provide " +"too much functionality so module environments are executed from " +"centos-art.sh, to extend its functionality." +msgstr "" +"When you execute the centos-art.sh script you create an execution environment in which " +"variables and functions are defined. The execution environment is " +"the higher environment inside centos-art." +"sh script. It is considered to have a “global” scope, so " +"variables and functions defined in it are always available for any " +"function execution made from it. You can control the execution " +"environment of centos-art.sh " +"script through files centos-art.sh and " +"centos-art.conf.sh. These files don't provide " +"too much functionality so module environments are executed from " +"centos-art.sh, to extend its functionality." + +msgid "" +"Module environments are made of small functions that perform small " +"tasks and can be further executed in a specific order to produce " +"the desired result. Module environments are executed and destroyed " +"at demand. Inside centos-art.sh, module environments can be either “parent modules,” " +"“child modules,” or “sibling modules.”" +msgstr "" +"Module environments are made of small functions that perform small " +"tasks and can be further executed in a specific order to produce " +"the desired result. Module environments are executed and destroyed " +"at demand. Inside centos-art.sh, module environments can be either “parent modules,” " +"“child modules,” or “sibling modules.”" + +msgid "Parent Modules" +msgstr "Parent Modules" + +msgid "" +"Parent modules are initiated by executing the tcar_setModuleEnvironment function with the " +"-t parent option set on it. " +"Parent modules are very simple in design and you can use them to " +"implement simple solutions quickly. Normally, when you execute a " +"parent module, you initiate the highest module environment possible " +"inside centos-art.sh script. " +"Because of such high scope, parent modules are frequently used to " +"define module's global variables, interpret module-specific options " +"passed through the command-line and execute the appropriate actions " +"based on them." +msgstr "" +"Parent modules are initiated by executing the tcar_setModuleEnvironment function with the " +"-t parent option set on it. " +"Parent modules are very simple in design and you can use them to " +"implement simple solutions quickly. Normally, when you execute a " +"parent module, you initiate the highest module environment possible " +"inside centos-art.sh script. " +"Because of such high scope, parent modules are frequently used to " +"define module's global variables, interpret module-specific options " +"passed through the command-line and execute the appropriate actions " +"based on them." + +msgid "" +"In , we have executed the " +"hello module with the " +"—greeting=hi and —debug options through the command-line. " +"In this example, centos-art.sh " +"script executes a parent module named hello, processes the module-specific options passed " +"through the command-line, prints a greeting message to standard " +"output and exits successfully." +msgstr "" +"In , we have executed the " +"hello module with the " +"—greeting=hi and —debug options through the command-line. " +"In this example, centos-art.sh " +"script executes a parent module named hello, processes the module-specific options passed " +"through the command-line, prints a greeting message to standard " +"output and exits successfully." + +msgid "Debugging execution of parent modules" +msgstr "Debugging execution of parent modules" + +#, no-wrap +msgid "" +"Thu 10 Oct 2013 11:53:28 PM CDT =========================> [0] | main\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_BASEDIR Automation/Modules\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_NAME [0]=hello\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_TYPE parent\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_ARGUMENT --greeting=hi\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_LIST hello|help|locale|prepare|render|tuneup|vcs\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Manuals\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Configs\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/hello.sh\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TEXTDOMAIN hello.sh\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:53:28 PM CDT export -f hello\n" +"Thu 10 Oct 2013 11:53:28 PM CDT export -f hello_getOptions\n" +"Thu 10 Oct 2013 11:53:28 PM CDT -------------------------> hello --greeting=hi\n" +"hi\n" +"Thu 10 Oct 2013 11:53:28 PM CDT <------------------------- hello\n" +"Thu 10 Oct 2013 11:53:28 PM CDT unset -f hello\n" +"Thu 10 Oct 2013 11:53:28 PM CDT unset -f hello_getOptions\n" +"Thu 10 Oct 2013 11:53:28 PM CDT <========================= [0] | main" +msgstr "" +"Thu 10 Oct 2013 11:53:28 PM CDT =========================> [0] | main\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_BASEDIR Automation/Modules\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_NAME [0]=hello\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_TYPE parent\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_ARGUMENT --greeting=hi\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_LIST hello|help|locale|prepare|render|tuneup|vcs\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Manuals\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Configs\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/hello.sh\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TEXTDOMAIN hello.sh\n" +"Thu 10 Oct 2013 11:53:28 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:53:28 PM CDT export -f hello\n" +"Thu 10 Oct 2013 11:53:28 PM CDT export -f hello_getOptions\n" +"Thu 10 Oct 2013 11:53:28 PM CDT -------------------------> hello --greeting=hi\n" +"hi\n" +"Thu 10 Oct 2013 11:53:28 PM CDT <------------------------- hello\n" +"Thu 10 Oct 2013 11:53:28 PM CDT unset -f hello\n" +"Thu 10 Oct 2013 11:53:28 PM CDT unset -f hello_getOptions\n" +"Thu 10 Oct 2013 11:53:28 PM CDT <========================= [0] | main" + +msgid "" +" describes an entire module " +"environment in action. With this information you can create your " +"own module environment, already. However, when your module is " +"getting too much complicated you probably want to divide it in " +"smaller pieces that you can execute accordingly, based on the " +"purpose you defined for it. Such kind of division can be " +"implemented as described in ." +msgstr "" +" describes an entire module " +"environment in action. With this information you can create your " +"own module environment, already. However, when your module is " +"getting too much complicated you probably want to divide it in " +"smaller pieces that you can execute accordingly, based on the " +"purpose you defined for it. Such kind of division can be " +"implemented as described in ." + +msgid "Summary" +msgstr "Summary" + +msgid "" +"This section has covered basic concepts related to module " +"environment inside centos-art.sh script. The next section takes these concepts and focuses " +"on the implementation of them. Once you finish it, you should be " +"able of writing your own module environments from scratch inside " +"centos-art.sh script." +msgstr "" +"This section has covered basic concepts related to module " +"environment inside centos-art.sh script. The next section takes these concepts and focuses " +"on the implementation of them. Once you finish it, you should be " +"able of writing your own module environments from scratch inside " +"centos-art.sh script." + +msgid "Module Implementation" +msgstr "Module Implementation" + +msgid "" +"The centos-art.sh script " +"implements module environments inside the “Modules” directory, as described in ." +msgstr "" +"The centos-art.sh script " +"implements module environments inside the “Modules” directory, as described in ." + +msgid "" +"For example, consider the creation of a module named hello. The purpose of this module is to print " +"a greeting message to standard output and then exit successfully. " +"To create such a module, we need to create a directory named " +"“Hello” inside the “Modules” directory and put an initialization " +"file named “hello.sh” inside it. Because we want to execute the " +"hello module from centos-art.sh script command-line, we " +"put it in the first level of directories of Modules directory. See ." +msgstr "" +"For example, consider the creation of a module named hello. The purpose of this module is to print " +"a greeting message to standard output and then exit successfully. " +"To create such a module, we need to create a directory named " +"“Hello” inside the “Modules” directory and put an initialization " +"file named “hello.sh” inside it. Because we want to execute the " +"hello module from centos-art.sh script command-line, we " +"put it in the first level of directories of Modules directory. See ." + +msgid "Directory layout used by parent modules" +msgstr "Directory layout used by parent modules" + +#, no-wrap +msgid "" +".\n" +"|-- COPYING \n" +"|-- Locales/ \n" +"|-- Manuals/ \n" +"|-- Modules/ \n" +"| `-- Hello/ \n" +"| |-- hello.sh \n" +"| `-- hello_getOptions.sh \n" +"|-- Scripts/ \n" +"|-- centos-art.conf.sh \n" +"`-- centos-art.sh " +msgstr "" +".\n" +"|-- COPYING \n" +"|-- Locales/ \n" +"|-- Manuals/ \n" +"|-- Modules/ \n" +"| `-- Hello/ \n" +"| |-- hello.sh \n" +"| `-- hello_getOptions.sh \n" +"|-- Scripts/ \n" +"|-- centos-art.conf.sh \n" +"`-- centos-art.sh " + +msgid "Script's copying conditions." +msgstr "Script's copying conditions." + +msgid "Script's localization files." +msgstr "Script's localization files." + +msgid "Script's documentation files." +msgstr "Script's documentation files." + +msgid "Script's modules. Here is where you store parent modules." +msgstr "Script's modules. Here is where you store parent modules." + +msgid "Parent directory of module named hello." +msgstr "Parent directory of module named hello." + +msgid "Initialization file of module named hello." +msgstr "Initialization file of module named hello." + +msgid "Function related to module named hello." +msgstr "Function related to module named hello." + +msgid "Script's global functions." +msgstr "Script's global functions." + +msgid "Script's configuration file." +msgstr "Script's configuration file." + +msgid "Script's initialization file." +msgstr "Script's initialization file." + +msgid "" +" presents a complete module " +"layout you can use as reference to create your own module " +"implementations. However, it is not complete yet. At this point, " +"when you execute centos-art.sh, it is able to find out hello module's initialization file and execute it but that " +"prints an error message because the initialization file doesn't " +"have a function definition inside. It is completely empty. In order " +"for centos-art.sh script to do " +"something useful, you need to write a function definition inside " +"the initialization file, as described in ." +msgstr "" +" presents a complete module " +"layout you can use as reference to create your own module " +"implementations. However, it is not complete yet. At this point, " +"when you execute centos-art.sh, it is able to find out hello module's initialization file and execute it but that " +"prints an error message because the initialization file doesn't " +"have a function definition inside. It is completely empty. In order " +"for centos-art.sh script to do " +"something useful, you need to write a function definition inside " +"the initialization file, as described in ." + +msgid "The Initialization File" +msgstr "The Initialization File" + +msgid "" +"The module's initialization file contains the module's main " +"function definition and a comment describing what it does on top of " +"it. This comment includes a small description about what the " +"function does, a written by section, the copyright note and the " +"legal status of the file. The function definition is set later and " +"must be written using the long definition format (i.e., it must " +"begin with the word “function,” then the " +"function name, and finally the “{” character). " +"The name of the function is exactly the same of the initialization " +"file but without the .sh extension. These " +"conditions are required in order for centos-art.sh script to execute the function " +"definition and destroy it when it is no longer used. See ." +msgstr "" +"The module's initialization file contains the module's main " +"function definition and a comment describing what it does on top of " +"it. This comment includes a small description about what the " +"function does, a written by section, the copyright note and the " +"legal status of the file. The function definition is set later and " +"must be written using the long definition format (i.e., it must " +"begin with the word “function,” then the " +"function name, and finally the “{” character). " +"The name of the function is exactly the same of the initialization " +"file but without the .sh extension. These " +"conditions are required in order for centos-art.sh script to execute the function " +"definition and destroy it when it is no longer used. See ." + +msgid "" +"The function definition is where you write all the commands you " +"want the module runs, once executed. The function definition can be " +"as simple as just one single line of code or as complex as you can " +"imagine. It is the place where you express your solutions. However, " +"when writing initialization files, it is considered a good practice " +"to avoid any sort of complexity. Instead, try to write small and " +"simple initialization files. In case you notice the initialization " +"file is growing up inevitably, you can reduce its code by " +"refactoring it. To do this, you can use resources like module " +"related functions and child modules. These resources are described " +"in , and they help you to " +"keep the initialization file in a clean state, easy to understand, " +"maintain and debug." +msgstr "" +"The function definition is where you write all the commands you " +"want the module runs, once executed. The function definition can be " +"as simple as just one single line of code or as complex as you can " +"imagine. It is the place where you express your solutions. However, " +"when writing initialization files, it is considered a good practice " +"to avoid any sort of complexity. Instead, try to write small and " +"simple initialization files. In case you notice the initialization " +"file is growing up inevitably, you can reduce its code by " +"refactoring it. To do this, you can use resources like module " +"related functions and child modules. These resources are described " +"in , and they help you to " +"keep the initialization file in a clean state, easy to understand, " +"maintain and debug." + +msgid "Initialization file used by hello module" +msgstr "Initialization file used by hello module" + +#, no-wrap +msgid "" +"#!/bin/bash\n" +"######################################################################\n" +"#\n" +"# hello.sh -- Print out greetings to standard output and exit\n" +"# successfully.\n" +"#\n" +"# Written by:\n" +"# * Alain Reguera Delgado <al@centos.org.cu>, 2013\n" +"#\n" +"# Copyright (C) 2009-2013 The CentOS Artwork SIG\n" +"#\n" +"# This program is free software; you can redistribute it and/or modify\n" +"# it under the terms of the GNU General Public License as published by\n" +"# the Free Software Foundation; either version 2 of the License, or (at\n" +"# your option) any later version.\n" +"#\n" +"# This program is distributed in the hope that it will be useful, but\n" +"# WITHOUT ANY WARRANTY; without even the implied warranty of\n" +"# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU\n" +"# General Public License for more details.\n" +"#\n" +"# You should have received a copy of the GNU General Public License\n" +"# along with this program; if not, write to the Free Software\n" +"# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.\n" +"#\n" +"######################################################################\n" +"\n" +"function hello {\n" +"\n" +" tcar_printMessage \"`gettext \"Hello, World!\"`\" --as-stdout-line\n" +"\n" +"}" +msgstr "" +"#!/bin/bash\n" +"######################################################################\n" +"#\n" +"# hello.sh -- Print out greetings to standard output and exit\n" +"# successfully.\n" +"#\n" +"# Written by:\n" +"# * Alain Reguera Delgado <al@centos.org.cu>, 2013\n" +"#\n" +"# Copyright (C) 2009-2013 The CentOS Artwork SIG\n" +"#\n" +"# This program is free software; you can redistribute it and/or modify\n" +"# it under the terms of the GNU General Public License as published by\n" +"# the Free Software Foundation; either version 2 of the License, or (at\n" +"# your option) any later version.\n" +"#\n" +"# This program is distributed in the hope that it will be useful, but\n" +"# WITHOUT ANY WARRANTY; without even the implied warranty of\n" +"# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU\n" +"# General Public License for more details.\n" +"#\n" +"# You should have received a copy of the GNU General Public License\n" +"# along with this program; if not, write to the Free Software\n" +"# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.\n" +"#\n" +"######################################################################\n" +"\n" +"function hello {\n" +"\n" +" tcar_printMessage \"`gettext \"Hello, World!\"`\" --as-stdout-line\n" +"\n" +"}" + +msgid "" +"The function definition described in uses the tcar_printMessage global function to print localized versions of the string " +"“Hello, World!” to standard output. Because there isn't no other " +"command in the function definition, when the greeting message is " +"printed out, centos-art.sh " +"destroys the hello module and " +"exit successfully. This process is more visible when also pass the " +"—debug option. See ." +msgstr "" +"The function definition described in uses the tcar_printMessage global function to print localized versions of the string " +"“Hello, World!” to standard output. Because there isn't no other " +"command in the function definition, when the greeting message is " +"printed out, centos-art.sh " +"destroys the hello module and " +"exit successfully. This process is more visible when also pass the " +"—debug option. See ." + +msgid "" +"Congratulations! You've implemented a module environment inside " +"centos-art.sh script. With the " +"information you have so far, you are able to create your own module " +"environment implementations. The next section delves into available " +"resources you can use to simplify module environments when the " +"initialization file starts growing inevitably and complexity " +"daemons begin hammering your head." +msgstr "" +"Congratulations! You've implemented a module environment inside " +"centos-art.sh script. With the " +"information you have so far, you are able to create your own module " +"environment implementations. The next section delves into available " +"resources you can use to simplify module environments when the " +"initialization file starts growing inevitably and complexity " +"daemons begin hammering your head." + +msgid "Module Optimization" +msgstr "Module Optimization" + +msgid "" +"The centos-art.sh script " +"provides four resources you can use to optimize your module " +"implementations. These resources are “related functions,” “child " +"modules,” “sibling modules” and “recursive modules”." +msgstr "" +"The centos-art.sh script " +"provides four resources you can use to optimize your module " +"implementations. These resources are “related functions,” “child " +"modules,” “sibling modules” and “recursive modules”." + +msgid "Related Functions" +msgstr "Related Functions" + +msgid "" +"Related functions are very useful when you need to simplify the " +"function definition of one initialization file. For example, " +"consider extending the hello " +"module so it is able to interpret arguments passed through the " +"command-line. Now, inside the initialization file, we have some " +"variable definitions, one function call to a module related " +"function named hello_getOptions, and a decision on how the greeting message must be " +"printed out based on the collected actions. See ." +msgstr "" +"Related functions are very useful when you need to simplify the " +"function definition of one initialization file. For example, " +"consider extending the hello " +"module so it is able to interpret arguments passed through the " +"command-line. Now, inside the initialization file, we have some " +"variable definitions, one function call to a module related " +"function named hello_getOptions, and a decision on how the greeting message must be " +"printed out based on the collected actions. See ." + +msgid "Initialization file used by hello module (extended)" +msgstr "Initialization file used by hello module (extended)" + +#, no-wrap +msgid "" +"function hello {\n" +"\n" +" # Define default greeting message.\n" +" local HELLO_WORLD=\"`gettext \"Hello, World!\"`\"\n" +"\n" +" # Define actions variable. Here is where actions related to\n" +" # module-specific options are stored in for further processing.\n" +" local ACTIONS=''\n" +"\n" +" # Interpret module-specific options and store related actions.\n" +" hello_getOptions\n" +"\n" +" # Print greeting message\n" +" if [[ -z ${ACTIONS} ]];then\n" +" # Using parent module.\n" +" tcar_printMessage \"${HELLO_WORLD}\" --as-stdout-line\n" +" else\n" +" # Using child module.\n" +" tcar_setModuleEnvironment -m 'output' -t 'child'\n" +" fi\n" +"\n" +"}" +msgstr "" +"function hello {\n" +"\n" +" # Define default greeting message.\n" +" local HELLO_WORLD=\"`gettext \"Hello, World!\"`\"\n" +"\n" +" # Define actions variable. Here is where actions related to\n" +" # module-specific options are stored in for further processing.\n" +" local ACTIONS=''\n" +"\n" +" # Interpret module-specific options and store related actions.\n" +" hello_getOptions\n" +"\n" +" # Print greeting message\n" +" if [[ -z ${ACTIONS} ]];then\n" +" # Using parent module.\n" +" tcar_printMessage \"${HELLO_WORLD}\" --as-stdout-line\n" +" else\n" +" # Using child module.\n" +" tcar_setModuleEnvironment -m 'output' -t 'child'\n" +" fi\n" +"\n" +"}" + +msgid "" +"When you execute the command centos-art." +"sh hello with the —" +"greeting=hi argument, centos-" +"art.sh stores module-specific arguments inside the " +"TCAR_MODULE_ARGUMENT variable, creates a list of " +"all function definitions inside the module directory and exports " +"them. This includes the function definition of the initialization " +"file itself. Then centos-art.sh executes the function definition set inside the " +"initialization file and leaves all other function definitions, " +"already in memory, waiting for further execution. At this point, " +"the hello initialization " +"function sets some default values and execute the hello_getOptions function to parse all the " +"arguments passed through the command-line and redefines the " +"ACTIONS variable based on them. Using the " +"ACTIONS variables it decides whether to print " +"the greeting message immediately or execute the child modules named " +"output so it decides what to " +"do with the information collected so far." +msgstr "" +"When you execute the command centos-art." +"sh hello with the —" +"greeting=hi argument, centos-" +"art.sh stores module-specific arguments inside the " +"TCAR_MODULE_ARGUMENT variable, creates a list of " +"all function definitions inside the module directory and exports " +"them. This includes the function definition of the initialization " +"file itself. Then centos-art.sh executes the function definition set inside the " +"initialization file and leaves all other function definitions, " +"already in memory, waiting for further execution. At this point, " +"the hello initialization " +"function sets some default values and execute the hello_getOptions function to parse all the " +"arguments passed through the command-line and redefines the " +"ACTIONS variable based on them. Using the " +"ACTIONS variables it decides whether to print " +"the greeting message immediately or execute the child modules named " +"output so it decides what to " +"do with the information collected so far." + +msgid "" +" defines the options " +"you can pass to hello module " +"and the associated actions they must perform for each of them. " +"Actions aren't immediately executed here. Instead, they are stored " +"in the ACTIONS variable for further processing " +"(e.g., we store the names of the modules we want to execute later). " +"The ACTIONS variable was defined in the " +"initialization file so it has a global scope inside the module " +"environment and is reachable from any related function executed " +"inside it. Storing the actions this way lets the hello module to collect information about " +"different actions and execute them all in just one command. When " +"all options have been parsed, only non-option arguments remain in " +"the TCAR_MODULE_ARGUMENT variable." +msgstr "" +" defines the options " +"you can pass to hello module " +"and the associated actions they must perform for each of them. " +"Actions aren't immediately executed here. Instead, they are stored " +"in the ACTIONS variable for further processing " +"(e.g., we store the names of the modules we want to execute later). " +"The ACTIONS variable was defined in the " +"initialization file so it has a global scope inside the module " +"environment and is reachable from any related function executed " +"inside it. Storing the actions this way lets the hello module to collect information about " +"different actions and execute them all in just one command. When " +"all options have been parsed, only non-option arguments remain in " +"the TCAR_MODULE_ARGUMENT variable." + +msgid "Related function definition (hello_getOptions)" +msgstr "Related function definition (hello_getOptions)" + +#, no-wrap +msgid "" +"function hello_getOptions {\n" +"\n" +" # Define short options we want to support.\n" +" local ARGSS=\"h::,v,g:,l,u,c,r\"\n" +"\n" +" # Define long options we want to support.\n" +" local ARGSL=\"help::,version,greeting:,lower,upper,camel,random\"\n" +"\n" +" # Redefine arguments using getopt(1) command parser.\n" +" tcar_setModuleArguments\n" +"\n" +" # Reset positional parameters on this function, using output\n" +" # produced from (getopt) arguments parser.\n" +" eval set -- \"${TCAR_MODULE_ARGUMENT}\"\n" +"\n" +" # Look for options passed through command-line.\n" +" while true; do\n" +" case \"${1}\" in\n" +"\n" +" -h | --help )\n" +" tcar_printHelp \"${2}\"\n" +" ;;\n" +"\n" +" -v | --version )\n" +" tcar_printVersion \"${TCAR_MODULE_NAME}\"\n" +" ;;\n" +"\n" +" -g | --greeting )\n" +" HELLO_WORLD=\"${2:-${HELLO_WORLD}}\"\n" +" shift 2\n" +" ;;\n" +"\n" +" -l | --lower )\n" +" ACTIONS=\"lower ${ACTIONS}\"\n" +" shift 1\n" +" ;;\n" +"\n" +" -u | --upper )\n" +" ACTIONS=\"upper ${ACTIONS}\"\n" +" shift 1\n" +" ;;\n" +"\n" +" -c | --camel )\n" +" ACTIONS=\"camel ${ACTIONS}\"\n" +" shift 1\n" +" ;;\n" +"\n" +" -r | --random )\n" +" ACTIONS=\"random ${ACTIONS}\"\n" +" shift 1\n" +" ;;\n" +"\n" +" -- )\n" +" shift 1\n" +" break\n" +" ;;\n" +" esac\n" +" done\n" +"\n" +" # Redefine arguments using current positional parameters. Only\n" +" # paths should remain as arguments, at this point.\n" +" TCAR_MODULE_ARGUMENT=\"${@}\"\n" +"\n" +"}" +msgstr "" +"function hello_getOptions {\n" +"\n" +" # Define short options we want to support.\n" +" local ARGSS=\"h::,v,g:,l,u,c,r\"\n" +"\n" +" # Define long options we want to support.\n" +" local ARGSL=\"help::,version,greeting:,lower,upper,camel,random\"\n" +"\n" +" # Redefine arguments using getopt(1) command parser.\n" +" tcar_setModuleArguments\n" +"\n" +" # Reset positional parameters on this function, using output\n" +" # produced from (getopt) arguments parser.\n" +" eval set -- \"${TCAR_MODULE_ARGUMENT}\"\n" +"\n" +" # Look for options passed through command-line.\n" +" while true; do\n" +" case \"${1}\" in\n" +"\n" +" -h | --help )\n" +" tcar_printHelp \"${2}\"\n" +" ;;\n" +"\n" +" -v | --version )\n" +" tcar_printVersion \"${TCAR_MODULE_NAME}\"\n" +" ;;\n" +"\n" +" -g | --greeting )\n" +" HELLO_WORLD=\"${2:-${HELLO_WORLD}}\"\n" +" shift 2\n" +" ;;\n" +"\n" +" -l | --lower )\n" +" ACTIONS=\"lower ${ACTIONS}\"\n" +" shift 1\n" +" ;;\n" +"\n" +" -u | --upper )\n" +" ACTIONS=\"upper ${ACTIONS}\"\n" +" shift 1\n" +" ;;\n" +"\n" +" -c | --camel )\n" +" ACTIONS=\"camel ${ACTIONS}\"\n" +" shift 1\n" +" ;;\n" +"\n" +" -r | --random )\n" +" ACTIONS=\"random ${ACTIONS}\"\n" +" shift 1\n" +" ;;\n" +"\n" +" -- )\n" +" shift 1\n" +" break\n" +" ;;\n" +" esac\n" +" done\n" +"\n" +" # Redefine arguments using current positional parameters. Only\n" +" # paths should remain as arguments, at this point.\n" +" TCAR_MODULE_ARGUMENT=\"${@}\"\n" +"\n" +"}" + +msgid "" +" presents the " +"standard construction we use inside centos-art.sh script for parsing arguments passed " +"through the command-line in a per-module basis. As convention, all " +"the parent modules you write must be able to interpret the " +"—help and —version options using the construction " +"described here." +msgstr "" +" presents the " +"standard construction we use inside centos-art.sh script for parsing arguments passed " +"through the command-line in a per-module basis. As convention, all " +"the parent modules you write must be able to interpret the " +"—help and —version options using the construction " +"described here." + +msgid "" +"Related functions are very useful when you are refactoring the " +"initialization file of a module. However, they aren't so efficient " +"when you need to execute them at demand (e.g., based on specific " +"conditions). When a module is executed, related functions are " +"exported to centos-art.sh " +"script execution environment. They remain there, consuming memory, " +"until the module they belong to is destroyed. If you create a " +"related function and never execute it, it will consume memory, as " +"well. So, use related functions when you are absolutely sure they " +"will be executed at some point, in one single iteration of " +"centos-art.sh script. If you " +"need to execute functions at demand, use child modules, instead." +msgstr "" +"Related functions are very useful when you are refactoring the " +"initialization file of a module. However, they aren't so efficient " +"when you need to execute them at demand (e.g., based on specific " +"conditions). When a module is executed, related functions are " +"exported to centos-art.sh " +"script execution environment. They remain there, consuming memory, " +"until the module they belong to is destroyed. If you create a " +"related function and never execute it, it will consume memory, as " +"well. So, use related functions when you are absolutely sure they " +"will be executed at some point, in one single iteration of " +"centos-art.sh script. If you " +"need to execute functions at demand, use child modules, instead." + +msgid "Child Modules" +msgstr "Child Modules" + +msgid "" +"Child modules are initiated by executing the tcar_setModuleEnvironment function with the -t child option set on it. Child modules " +"have the characteristic of being nested modules. They cannot be " +"executed from the command-line. Normally, child modules are " +"executed from parent modules but they can be executed from other " +"child modules, too. When several child modules are executed in one " +"single iteration of centos-art.sh, they create a chain of modules. A chain of modules is " +"very useful in situations where you want to divide one large task " +"into smaller tasks and also control which of these smaller tasks is " +"executed based on specific conditions (e.g., you may want to render " +"images or documentation, but not both, in one single iteration of " +"centos-art.sh script). In a " +"chain of modules, lower modules in the chain (those started last) " +"have access to information set by modules higher in the chain " +"(those started first), but not the opposite. When processing " +"information this way, modules aren't destroyed until the last " +"module executed in the chain has finished its work (e.g., all the " +"commands inside it have been executed). At that point, child " +"modules are destroyed in the reverse order they were executed." +msgstr "" +"Child modules are initiated by executing the tcar_setModuleEnvironment function with the -t child option set on it. Child modules " +"have the characteristic of being nested modules. They cannot be " +"executed from the command-line. Normally, child modules are " +"executed from parent modules but they can be executed from other " +"child modules, too. When several child modules are executed in one " +"single iteration of centos-art.sh, they create a chain of modules. A chain of modules is " +"very useful in situations where you want to divide one large task " +"into smaller tasks and also control which of these smaller tasks is " +"executed based on specific conditions (e.g., you may want to render " +"images or documentation, but not both, in one single iteration of " +"centos-art.sh script). In a " +"chain of modules, lower modules in the chain (those started last) " +"have access to information set by modules higher in the chain " +"(those started first), but not the opposite. When processing " +"information this way, modules aren't destroyed until the last " +"module executed in the chain has finished its work (e.g., all the " +"commands inside it have been executed). At that point, child " +"modules are destroyed in the reverse order they were executed." + +msgid "" +"For example, when you execute the hello module with both —debug and —upper option, " +"centos-art.sh script creates a " +"chain of three modules to produce the greeting message. Firstly, it " +"begins by executing the parent module named hello, then it continues with the child module named " +"output which in turn executes " +"the child module name lower to " +"finally print the expected greeting message. In this example, the " +"module named lower is the last " +"module in the chain of executed modules. It has access to all " +"information defined by earlier modules (e.g., in hello and output modules) and none of its earlier modules will be " +"destroyed until it has finished its work. This process becomes more " +"visible when you take a look at ." +msgstr "" +"For example, when you execute the hello module with both —debug and —upper option, " +"centos-art.sh script creates a " +"chain of three modules to produce the greeting message. Firstly, it " +"begins by executing the parent module named hello, then it continues with the child module named " +"output which in turn executes " +"the child module name lower to " +"finally print the expected greeting message. In this example, the " +"module named lower is the last " +"module in the chain of executed modules. It has access to all " +"information defined by earlier modules (e.g., in hello and output modules) and none of its earlier modules will be " +"destroyed until it has finished its work. This process becomes more " +"visible when you take a look at ." + +msgid "Debugging execution of child modules" +msgstr "Debugging execution of child modules" + +#, no-wrap +msgid "" +"Thu 10 Oct 2013 11:52:41 PM CDT =========================> [0] | main\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_BASEDIR Automation/Modules\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_NAME [0]=hello\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_TYPE parent\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_ARGUMENT --upper --greeting=hi\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_LIST hello|help|locale|prepare|render|tuneup|vcs\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Manuals\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Configs\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/hello.sh\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TEXTDOMAIN hello.sh\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:52:41 PM CDT export -f hello\n" +"Thu 10 Oct 2013 11:52:41 PM CDT export -f hello_getOptions\n" +"Thu 10 Oct 2013 11:52:41 PM CDT -------------------------> hello --upper --greeting=hi\n" +"Thu 10 Oct 2013 11:52:41 PM CDT =========================> [1] | hello\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_NAME [1]=output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_LIST output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Manuals\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Configs\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/output.sh\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TEXTDOMAIN output.sh\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:52:41 PM CDT export -f output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT -------------------------> output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT =========================> [2] | output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_NAME [2]=upper\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_LIST camel|lower|random|upper\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output/Modules/Upper\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules/Upper/Modules\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Modules/Upper/Manuals\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Modules/Upper/Locales\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Modules/Upper/Configs\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/Modules/Upper/upper.sh\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TEXTDOMAIN upper.sh\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Modules/Upper/Locales\n" +"Thu 10 Oct 2013 11:52:42 PM CDT export -f upper\n" +"Thu 10 Oct 2013 11:52:42 PM CDT -------------------------> upper\n" +"HI\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <------------------------- upper\n" +"Thu 10 Oct 2013 11:52:42 PM CDT unset -f upper\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <========================= [2] | output\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <------------------------- output\n" +"Thu 10 Oct 2013 11:52:42 PM CDT unset -f output\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <========================= [1] | hello\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <------------------------- hello\n" +"Thu 10 Oct 2013 11:52:42 PM CDT unset -f hello\n" +"Thu 10 Oct 2013 11:52:42 PM CDT unset -f hello_getOptions\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <========================= [0] | main" +msgstr "" +"Thu 10 Oct 2013 11:52:41 PM CDT =========================> [0] | main\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_BASEDIR Automation/Modules\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_NAME [0]=hello\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_TYPE parent\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_ARGUMENT --upper --greeting=hi\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_LIST hello|help|locale|prepare|render|tuneup|vcs\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Manuals\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Configs\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/hello.sh\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TEXTDOMAIN hello.sh\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:52:41 PM CDT export -f hello\n" +"Thu 10 Oct 2013 11:52:41 PM CDT export -f hello_getOptions\n" +"Thu 10 Oct 2013 11:52:41 PM CDT -------------------------> hello --upper --greeting=hi\n" +"Thu 10 Oct 2013 11:52:41 PM CDT =========================> [1] | hello\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_NAME [1]=output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_LIST output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Manuals\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Configs\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/output.sh\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TEXTDOMAIN output.sh\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:52:41 PM CDT export -f output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT -------------------------> output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT =========================> [2] | output\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_NAME [2]=upper\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_LIST camel|lower|random|upper\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output/Modules/Upper\n" +"Thu 10 Oct 2013 11:52:41 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules/Upper/Modules\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Modules/Upper/Manuals\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Modules/Upper/Locales\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Modules/Upper/Configs\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/Modules/Upper/upper.sh\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TEXTDOMAIN upper.sh\n" +"Thu 10 Oct 2013 11:52:42 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Modules/Upper/Locales\n" +"Thu 10 Oct 2013 11:52:42 PM CDT export -f upper\n" +"Thu 10 Oct 2013 11:52:42 PM CDT -------------------------> upper\n" +"HI\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <------------------------- upper\n" +"Thu 10 Oct 2013 11:52:42 PM CDT unset -f upper\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <========================= [2] | output\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <------------------------- output\n" +"Thu 10 Oct 2013 11:52:42 PM CDT unset -f output\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <========================= [1] | hello\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <------------------------- hello\n" +"Thu 10 Oct 2013 11:52:42 PM CDT unset -f hello\n" +"Thu 10 Oct 2013 11:52:42 PM CDT unset -f hello_getOptions\n" +"Thu 10 Oct 2013 11:52:42 PM CDT <========================= [0] | main" + +msgid "" +"The module environment described in shows the child modules' ability of reducing scope as " +"they get deeper in the chain of executed modules. However, child " +"modules lack the possibility of nest modules that share the same " +"scope. For example, in the hello module described above, you cannot execute the modules " +"lower or upper from camel module, as if they were child modules of it. That is not " +"possible because they all have the same scope, which is, to print " +"the greeting message to standard output. Child modules are " +"conceived to reduce the module scope as new child modules are " +"executed. When you need to execute new module environments and, " +"also, retain the last scope from which the new module is executed, " +"you need to use “sibling modules,” instead." +msgstr "" +"The module environment described in shows the child modules' ability of reducing scope as " +"they get deeper in the chain of executed modules. However, child " +"modules lack the possibility of nest modules that share the same " +"scope. For example, in the hello module described above, you cannot execute the modules " +"lower or upper from camel module, as if they were child modules of it. That is not " +"possible because they all have the same scope, which is, to print " +"the greeting message to standard output. Child modules are " +"conceived to reduce the module scope as new child modules are " +"executed. When you need to execute new module environments and, " +"also, retain the last scope from which the new module is executed, " +"you need to use “sibling modules,” instead." + +msgid "Sibling Modules" +msgstr "Sibling Modules" + +msgid "" +"Sibling modules are initiated by executing the tcar_setModuleEnvironment function with the " +"-t sibling option set on it. " +"Sibling modules are another type of nested modules but, in contrast " +"with child modules, sibling modules cannot be executed from parent " +"modules. Normally, sibling modules are executed from other sibling " +"modules but, considering the context, they can be executed from " +"child module too, to initiate sibling processing. When several " +"siblings modules are executed, they also build a chain of modules. " +"In contrast with the chain of child modules, the chain of sibling " +"modules destroys the last sibling module executed before executing " +"the next sibling module. This make the chain to stop its growing at " +"sibling module processing, unless you call a child module from a " +"sibling module. In this case, the chain expansion would continue as " +"long as the number of child modules you execute. This process " +"becomes more visible when you take a look at ." +msgstr "" +"Sibling modules are initiated by executing the tcar_setModuleEnvironment function with the " +"-t sibling option set on it. " +"Sibling modules are another type of nested modules but, in contrast " +"with child modules, sibling modules cannot be executed from parent " +"modules. Normally, sibling modules are executed from other sibling " +"modules but, considering the context, they can be executed from " +"child module too, to initiate sibling processing. When several " +"siblings modules are executed, they also build a chain of modules. " +"In contrast with the chain of child modules, the chain of sibling " +"modules destroys the last sibling module executed before executing " +"the next sibling module. This make the chain to stop its growing at " +"sibling module processing, unless you call a child module from a " +"sibling module. In this case, the chain expansion would continue as " +"long as the number of child modules you execute. This process " +"becomes more visible when you take a look at ." + +msgid "" +"In , we've executed the " +"hello module with the " +"—greeting=hi, —camel, and —debug options. In this example, centos-art.sh script executes the hello module then the output module which in turn executes the camel module. At this point, can " +"appreciate how the chain of modules stop growing. Observe that " +"camel module has gained the " +"position 2 in the chain of modules and executes the upper module which takes the position 3, as " +"expected. Now, when upper " +"module finishes its work it is destroyed and the module's counter " +"is reset to its previous value which is 2 (the one set by camel module). Then, camel executes the lower module which take position 3 at the chain of " +"modules until it finishes. When it finishes, the camel module finishes its work and is " +"destroyed, then output, then " +"hello." +msgstr "" +"In , we've executed the " +"hello module with the " +"—greeting=hi, —camel, and —debug options. In this example, centos-art.sh script executes the hello module then the output module which in turn executes the camel module. At this point, can " +"appreciate how the chain of modules stop growing. Observe that " +"camel module has gained the " +"position 2 in the chain of modules and executes the upper module which takes the position 3, as " +"expected. Now, when upper " +"module finishes its work it is destroyed and the module's counter " +"is reset to its previous value which is 2 (the one set by camel module). Then, camel executes the lower module which take position 3 at the chain of " +"modules until it finishes. When it finishes, the camel module finishes its work and is " +"destroyed, then output, then " +"hello." + +msgid "Debugging execution of sibling modules" +msgstr "Debugging execution of sibling modules" + +#, no-wrap +msgid "" +"Thu 10 Oct 2013 11:51:42 PM CDT =========================> [0] | main\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_BASEDIR Automation/Modules\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_NAME [0]=hello\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_TYPE parent\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_ARGUMENT --camel --greeting=hi\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_LIST hello|help|locale|prepare|render|tuneup|vcs\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Manuals\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Configs\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/hello.sh\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TEXTDOMAIN hello.sh\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT export -f hello\n" +"Thu 10 Oct 2013 11:51:43 PM CDT export -f hello_getOptions\n" +"Thu 10 Oct 2013 11:51:43 PM CDT -------------------------> hello --camel --greeting=hi\n" +"Thu 10 Oct 2013 11:51:43 PM CDT =========================> [1] | hello\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_NAME [1]=output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_LIST output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Manuals\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Configs\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/output.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAIN output.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT export -f output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT -------------------------> output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT =========================> [2] | output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_NAME [2]=camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_LIST camel|lower|random|upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output/Modules/Camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules/Camel/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Modules/Camel/Manuals\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Modules/Camel/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Modules/Camel/Configs\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/Modules/Camel/camel.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAIN camel.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Modules/Camel/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT export -f camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT -------------------------> camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT =========================> [3] | camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_NAME [3]=upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_TYPE sibling\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_LIST camel|lower|random|upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output/Modules/Upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules/Upper/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Modules/Upper/Manuals\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Modules/Upper/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Modules/Upper/Configs\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/Modules/Upper/upper.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAIN upper.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Modules/Upper/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT export -f upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT -------------------------> upper\n" +"H\n" +"Thu 10 Oct 2013 11:51:43 PM CDT <------------------------- upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT unset -f upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT <========================= [3] | camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT =========================> [3] | camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_NAME [3]=lower\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_TYPE sibling\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_LIST camel|lower|random|upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output/Modules/Lower\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules/Lower/Modules\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Modules/Lower/Manuals\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Modules/Lower/Locales\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Modules/Lower/Configs\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/Modules/Lower/lower.sh\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TEXTDOMAIN lower.sh\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Modules/Lower/Locales\n" +"Thu 10 Oct 2013 11:51:44 PM CDT export -f lower\n" +"Thu 10 Oct 2013 11:51:44 PM CDT -------------------------> lower\n" +"i\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <------------------------- lower\n" +"Thu 10 Oct 2013 11:51:44 PM CDT unset -f lower\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <========================= [3] | camel\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <------------------------- camel\n" +"Thu 10 Oct 2013 11:51:44 PM CDT unset -f camel\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <========================= [2] | output\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <------------------------- output\n" +"Thu 10 Oct 2013 11:51:44 PM CDT unset -f output\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <========================= [1] | hello\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <------------------------- hello\n" +"Thu 10 Oct 2013 11:51:44 PM CDT unset -f hello\n" +"Thu 10 Oct 2013 11:51:44 PM CDT unset -f hello_getOptions\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <========================= [0] | main" +msgstr "" +"Thu 10 Oct 2013 11:51:42 PM CDT =========================> [0] | main\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_BASEDIR Automation/Modules\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_NAME [0]=hello\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_TYPE parent\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_ARGUMENT --camel --greeting=hi\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_LIST hello|help|locale|prepare|render|tuneup|vcs\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Manuals\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Configs\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/hello.sh\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TEXTDOMAIN hello.sh\n" +"Thu 10 Oct 2013 11:51:42 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT export -f hello\n" +"Thu 10 Oct 2013 11:51:43 PM CDT export -f hello_getOptions\n" +"Thu 10 Oct 2013 11:51:43 PM CDT -------------------------> hello --camel --greeting=hi\n" +"Thu 10 Oct 2013 11:51:43 PM CDT =========================> [1] | hello\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_NAME [1]=output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_LIST output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Manuals\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Configs\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/output.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAIN output.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT export -f output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT -------------------------> output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT =========================> [2] | output\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_NAME [2]=camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_LIST camel|lower|random|upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output/Modules/Camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules/Camel/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Modules/Camel/Manuals\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Modules/Camel/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Modules/Camel/Configs\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/Modules/Camel/camel.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAIN camel.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Modules/Camel/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT export -f camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT -------------------------> camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT =========================> [3] | camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_NAME [3]=upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_TYPE sibling\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_LIST camel|lower|random|upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output/Modules/Upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules/Upper/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Modules/Upper/Manuals\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Modules/Upper/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Modules/Upper/Configs\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/Modules/Upper/upper.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAIN upper.sh\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Modules/Upper/Locales\n" +"Thu 10 Oct 2013 11:51:43 PM CDT export -f upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT -------------------------> upper\n" +"H\n" +"Thu 10 Oct 2013 11:51:43 PM CDT <------------------------- upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT unset -f upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT <========================= [3] | camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT =========================> [3] | camel\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_NAME [3]=lower\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_TYPE sibling\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_LIST camel|lower|random|upper\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output/Modules/Lower\n" +"Thu 10 Oct 2013 11:51:43 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules/Lower/Modules\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Modules/Lower/Manuals\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Modules/Lower/Locales\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Modules/Lower/Configs\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/Modules/Lower/lower.sh\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TEXTDOMAIN lower.sh\n" +"Thu 10 Oct 2013 11:51:44 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Modules/Lower/Locales\n" +"Thu 10 Oct 2013 11:51:44 PM CDT export -f lower\n" +"Thu 10 Oct 2013 11:51:44 PM CDT -------------------------> lower\n" +"i\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <------------------------- lower\n" +"Thu 10 Oct 2013 11:51:44 PM CDT unset -f lower\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <========================= [3] | camel\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <------------------------- camel\n" +"Thu 10 Oct 2013 11:51:44 PM CDT unset -f camel\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <========================= [2] | output\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <------------------------- output\n" +"Thu 10 Oct 2013 11:51:44 PM CDT unset -f output\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <========================= [1] | hello\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <------------------------- hello\n" +"Thu 10 Oct 2013 11:51:44 PM CDT unset -f hello\n" +"Thu 10 Oct 2013 11:51:44 PM CDT unset -f hello_getOptions\n" +"Thu 10 Oct 2013 11:51:44 PM CDT <========================= [0] | main" + +msgid "" +" shows a single iteration " +"of centos-art.sh script " +"executing different types of modules. Normally, one module is " +"executed at some point and destroyed at the same point when it has " +"finished its work, however, what if the next immediate module you " +"are about to execute is the same module you are about to destroyed? " +"This is, you need to execute the last module in the chain of " +"executed modules again, but, this time, from itself. In cases like " +"this, the centos-art.sh script " +"doesn't destroy the last module. It cannot, because you are " +"certainly executing a new module from itself, so it has to wait for " +"this new call to finish in order to be destroyed. This kind of " +"processing is known as processing modules recursively." +msgstr "" +" shows a single iteration " +"of centos-art.sh script " +"executing different types of modules. Normally, one module is " +"executed at some point and destroyed at the same point when it has " +"finished its work, however, what if the next immediate module you " +"are about to execute is the same module you are about to destroyed? " +"This is, you need to execute the last module in the chain of " +"executed modules again, but, this time, from itself. In cases like " +"this, the centos-art.sh script " +"doesn't destroy the last module. It cannot, because you are " +"certainly executing a new module from itself, so it has to wait for " +"this new call to finish in order to be destroyed. This kind of " +"processing is known as processing modules recursively." + +msgid "Recursive Modules" +msgstr "Recursive Modules" + +msgid "" +"When one module environment executes itself we are in presence of a " +"recursive module execution. The execution of modules recursively " +"doesn't destroy the last module in the chain of executed modules " +"and doesn't increment or decrement the module counter either. The " +"module counter is somehow frozen until a different module " +"environment is executed. In these cases, the last module " +"environment remains in memory for the new module execution to make " +"use of. This process becomes more visible when you take a look at " +"." +msgstr "" +"When one module environment executes itself we are in presence of a " +"recursive module execution. The execution of modules recursively " +"doesn't destroy the last module in the chain of executed modules " +"and doesn't increment or decrement the module counter either. The " +"module counter is somehow frozen until a different module " +"environment is executed. In these cases, the last module " +"environment remains in memory for the new module execution to make " +"use of. This process becomes more visible when you take a look at " +"." + +msgid "" +"When you execute modules recursively, you should be very careful " +"not to get trapped into an endless loop." +msgstr "" +"When you execute modules recursively, you should be very careful " +"not to get trapped into an endless loop." + +msgid "" +"In , we've executed the " +"hello module with the " +"—greeting=hello, —random, and —" +"debug options. In this example, centos-art.sh script executes a parent module named " +"hello which in turn executes a " +"child module named output " +"which in turn executes a child module named random. At this point, the random modules executes itself five times (the number " +"of characters passed as value to greeting option) to print out " +"random letters from the greeting message. The output may have no " +"much sense on itself but the related debugging information helps to " +"understand the execution of modules recursively." +msgstr "" +"In , we've executed the " +"hello module with the " +"—greeting=hello, —random, and —" +"debug options. In this example, centos-art.sh script executes a parent module named " +"hello which in turn executes a " +"child module named output " +"which in turn executes a child module named random. At this point, the random modules executes itself five times (the number " +"of characters passed as value to greeting option) to print out " +"random letters from the greeting message. The output may have no " +"much sense on itself but the related debugging information helps to " +"understand the execution of modules recursively." + +msgid "Processing execution of modules recursively" +msgstr "Processing execution of modules recursively" + +#, no-wrap +msgid "" +"Thu 10 Oct 2013 11:50:03 PM CDT =========================> [0] | main\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_BASEDIR Automation/Modules\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_NAME [0]=hello\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_TYPE parent\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_ARGUMENT --random --greeting=Hello\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_LIST hello|help|locale|prepare|render|tuneup|vcs\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Manuals\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Configs\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/hello.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAIN hello.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT export -f hello\n" +"Thu 10 Oct 2013 11:50:04 PM CDT export -f hello_getOptions\n" +"Thu 10 Oct 2013 11:50:04 PM CDT -------------------------> hello --random --greeting=Hello\n" +"Thu 10 Oct 2013 11:50:04 PM CDT =========================> [1] | hello\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_NAME [1]=output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_LIST output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Manuals\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Configs\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/output.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAIN output.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT export -f output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT -------------------------> output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT =========================> [2] | output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_NAME [2]=random\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_LIST camel|lower|random|upper\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output/Modules/Random\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules/Random/Modules\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Modules/Random/Manuals\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Modules/Random/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Modules/Random/Configs\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/Modules/Random/random.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAIN random.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Modules/Random/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT export -f random\n" +"Thu 10 Oct 2013 11:50:04 PM CDT -------------------------> random\n" +"H\n" +"Thu 10 Oct 2013 11:50:04 PM CDT ~~~~~~~~~~~~~~~~~~~~~~~~~> random\n" +"H\n" +"Thu 10 Oct 2013 11:50:04 PM CDT ~~~~~~~~~~~~~~~~~~~~~~~~~> random\n" +"l\n" +"Thu 10 Oct 2013 11:50:04 PM CDT ~~~~~~~~~~~~~~~~~~~~~~~~~> random\n" +"l\n" +"Thu 10 Oct 2013 11:50:04 PM CDT ~~~~~~~~~~~~~~~~~~~~~~~~~> random\n" +"H\n" +"Thu 10 Oct 2013 11:50:04 PM CDT <------------------------- random\n" +"Thu 10 Oct 2013 11:50:04 PM CDT unset -f random\n" +"Thu 10 Oct 2013 11:50:04 PM CDT <========================= [2] | output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT <------------------------- output\n" +"Thu 10 Oct 2013 11:50:05 PM CDT unset -f output\n" +"Thu 10 Oct 2013 11:50:05 PM CDT <========================= [1] | hello\n" +"Thu 10 Oct 2013 11:50:05 PM CDT <------------------------- hello\n" +"Thu 10 Oct 2013 11:50:05 PM CDT unset -f hello\n" +"Thu 10 Oct 2013 11:50:05 PM CDT unset -f hello_getOptions\n" +"Thu 10 Oct 2013 11:50:05 PM CDT <========================= [0] | main" +msgstr "" +"Thu 10 Oct 2013 11:50:03 PM CDT =========================> [0] | main\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_BASEDIR Automation/Modules\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_NAME [0]=hello\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_TYPE parent\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_ARGUMENT --random --greeting=Hello\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_LIST hello|help|locale|prepare|render|tuneup|vcs\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:50:03 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Manuals\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Configs\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/hello.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAIN hello.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT export -f hello\n" +"Thu 10 Oct 2013 11:50:04 PM CDT export -f hello_getOptions\n" +"Thu 10 Oct 2013 11:50:04 PM CDT -------------------------> hello --random --greeting=Hello\n" +"Thu 10 Oct 2013 11:50:04 PM CDT =========================> [1] | hello\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_NAME [1]=output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_LIST output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Manuals\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Configs\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/output.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAIN output.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT export -f output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT -------------------------> output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT =========================> [2] | output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_BASEDIR Automation/Modules/Hello/Modules/Output/Modules\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_NAME [2]=random\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_TYPE child\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_ARGUMENT\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_LIST camel|lower|random|upper\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR Automation/Modules/Hello/Modules/Output/Modules/Random\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_MODULES Automation/Modules/Hello/Modules/Output/Modules/Random/Modules\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_MANUALS Automation/Modules/Hello/Modules/Output/Modules/Random/Manuals\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_LOCALES Automation/Modules/Hello/Modules/Output/Modules/Random/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_DIR_CONFIGS Automation/Modules/Hello/Modules/Output/Modules/Random/Configs\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TCAR_MODULE_INIT_FILE Automation/Modules/Hello/Modules/Output/Modules/Random/random.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAIN random.sh\n" +"Thu 10 Oct 2013 11:50:04 PM CDT TEXTDOMAINDIR Automation/Modules/Hello/Modules/Output/Modules/Random/Locales\n" +"Thu 10 Oct 2013 11:50:04 PM CDT export -f random\n" +"Thu 10 Oct 2013 11:50:04 PM CDT -------------------------> random\n" +"H\n" +"Thu 10 Oct 2013 11:50:04 PM CDT ~~~~~~~~~~~~~~~~~~~~~~~~~> random\n" +"H\n" +"Thu 10 Oct 2013 11:50:04 PM CDT ~~~~~~~~~~~~~~~~~~~~~~~~~> random\n" +"l\n" +"Thu 10 Oct 2013 11:50:04 PM CDT ~~~~~~~~~~~~~~~~~~~~~~~~~> random\n" +"l\n" +"Thu 10 Oct 2013 11:50:04 PM CDT ~~~~~~~~~~~~~~~~~~~~~~~~~> random\n" +"H\n" +"Thu 10 Oct 2013 11:50:04 PM CDT <------------------------- random\n" +"Thu 10 Oct 2013 11:50:04 PM CDT unset -f random\n" +"Thu 10 Oct 2013 11:50:04 PM CDT <========================= [2] | output\n" +"Thu 10 Oct 2013 11:50:04 PM CDT <------------------------- output\n" +"Thu 10 Oct 2013 11:50:05 PM CDT unset -f output\n" +"Thu 10 Oct 2013 11:50:05 PM CDT <========================= [1] | hello\n" +"Thu 10 Oct 2013 11:50:05 PM CDT <------------------------- hello\n" +"Thu 10 Oct 2013 11:50:05 PM CDT unset -f hello\n" +"Thu 10 Oct 2013 11:50:05 PM CDT unset -f hello_getOptions\n" +"Thu 10 Oct 2013 11:50:05 PM CDT <========================= [0] | main" + +msgid "" +"Recursive execution of modules occurs only when the module you are " +"executing is considered sibling of the last module executed in the " +"chain of executed modules and they both have the same name. The " +"fact that no variable name is printed out in means that they were not created. The arrows " +"change from -> to ~>, " +"means that module's related functions weren't exported for the new " +"module execution either. It also means that the initialization " +"script is reusing both related functions and variables from the " +"last module environment in the chain of executed modules. In this " +"case the random module." +msgstr "" +"Recursive execution of modules occurs only when the module you are " +"executing is considered sibling of the last module executed in the " +"chain of executed modules and they both have the same name. The " +"fact that no variable name is printed out in means that they were not created. The arrows " +"change from -> to ~>, " +"means that module's related functions weren't exported for the new " +"module execution either. It also means that the initialization " +"script is reusing both related functions and variables from the " +"last module environment in the chain of executed modules. In this " +"case the random module." + +msgid "" +"This section covered the resources you can use to optimize module " +"environments inside centos-art.sh script. The next section summarizes the base files and " +"directories you might find inside one module environment." +msgstr "" +"This section covered the resources you can use to optimize module " +"environments inside centos-art.sh script. The next section summarizes the base files and " +"directories you might find inside one module environment." + +msgid "Module Structure" +msgstr "Module Structure" + +msgid "" +"The module structure takes place at the root location of centos-art.sh script, specifically, in a " +"directory named Modules. The Modules directory at centos-art.sh root location is the highest level which you can store " +"modules in. Modules stored in this location are known as parent " +"modules. Parent modules can optimize their structure by using " +"related functions, child modules, sibling modules and recursive " +"modules. Basically, all these types of modules share the same " +"structure. They all have function files and, optionally, module " +"related stuff like locales, documentation, configuration and " +"dependent modules. See ." +msgstr "" +"The module structure takes place at the root location of centos-art.sh script, specifically, in a " +"directory named Modules. The Modules directory at centos-art.sh root location is the highest level which you can store " +"modules in. Modules stored in this location are known as parent " +"modules. Parent modules can optimize their structure by using " +"related functions, child modules, sibling modules and recursive " +"modules. Basically, all these types of modules share the same " +"structure. They all have function files and, optionally, module " +"related stuff like locales, documentation, configuration and " +"dependent modules. See ." + +msgid "" +"From version 0.7 on, child modules no longer have Locales, Manuals and Configs " +"directories inside. Only initialization files, related functions " +"and Modules directory are supported inside child " +"modules. See Bug 114." +msgstr "" +"From version 0.7 on, child modules no longer have Locales, Manuals and Configs " +"directories inside. Only initialization files, related functions " +"and Modules directory are supported inside child " +"modules. See Bug 114." + +msgid "The directory structure of hello module" +msgstr "The directory structure of hello module" + +#, no-wrap +msgid "" +".\n" +"|-- COPYING\n" +"|-- Locales/\n" +"|-- Manuals/\n" +"|-- Modules/\n" +"| `-- Hello/ \n" +"| |-- Locales\n" +"| | |-- es_ES\n" +"| | | |-- LC_MESSAGES\n" +"| | | | `-- hello.sh.mo \n" +"| | | `-- hello.sh.po\n" +"| | `-- hello.sh.pot\n" +"| |-- Manuals\n" +"| | |-- hello.asciidoc\n" +"| | |-- man1\n" +"| | | `-- hello.1 \n" +"| | `-- render.conf \n" +"| |-- Modules\n" +"| | `-- Output \n" +"| | |-- Modules\n" +"| | | |-- Camel\n" +"| | | | `-- camel.sh\n" +"| | | |-- Lower \n" +"| | | | `-- lower.sh \n" +"| | | |-- Random\n" +"| | | | `-- random.sh\n" +"| | | `-- Upper\n" +"| | | `-- upper.sh\n" +"| | `-- output.sh \n" +"| |-- hello.sh \n" +"| `-- hello_getOptions.sh \n" +"|-- Scripts/\n" +"|-- centos-art.conf.sh\n" +"`-- centos-art.sh" +msgstr "" +".\n" +"|-- COPYING\n" +"|-- Locales/\n" +"|-- Manuals/\n" +"|-- Modules/\n" +"| `-- Hello/ \n" +"| |-- Locales\n" +"| | |-- es_ES\n" +"| | | |-- LC_MESSAGES\n" +"| | | | `-- hello.sh.mo \n" +"| | | `-- hello.sh.po\n" +"| | `-- hello.sh.pot\n" +"| |-- Manuals\n" +"| | |-- hello.asciidoc\n" +"| | |-- man1\n" +"| | | `-- hello.1 \n" +"| | `-- render.conf \n" +"| |-- Modules\n" +"| | `-- Output \n" +"| | |-- Modules\n" +"| | | |-- Camel\n" +"| | | | `-- camel.sh\n" +"| | | |-- Lower \n" +"| | | | `-- lower.sh \n" +"| | | |-- Random\n" +"| | | | `-- random.sh\n" +"| | | `-- Upper\n" +"| | | `-- upper.sh\n" +"| | `-- output.sh \n" +"| |-- hello.sh \n" +"| `-- hello_getOptions.sh \n" +"|-- Scripts/\n" +"|-- centos-art.conf.sh\n" +"`-- centos-art.sh" + +msgid "" +"Child module of centos-art.sh " +"script and parent module of output module." +msgstr "" +"Child module of centos-art.sh " +"script and parent module of output module." + +msgid "" +"Spanish translated strings of hello module." +msgstr "" +"Spanish translated strings of hello module." + +msgid "" +"Manpage shown when you request help of hello module." +msgstr "" +"Manpage shown when you request help of hello module." + +msgid "" +"Configuration file used to produce the manpage of hello module." +msgstr "" +"Configuration file used to produce the manpage of hello module." + +msgid "" +"Child module of hello module " +"and parent module of camel,lower,random and upper modules." +msgstr "" +"Child module of hello module " +"and parent module of camel,lower,random and upper modules." + +msgid "" +"Child module of output module " +"and sibling module of camel,random and upper module." +msgstr "" +"Child module of output module " +"and sibling module of camel,random and upper module." + +msgid "" +"Initialization file of lower " +"module." +msgstr "" +"Initialization file of lower " +"module." + +msgid "" +"Initialization file of output " +"module." +msgstr "" +"Initialization file of output " +"module." + +msgid "" +"Initialization file of hello " +"module." +msgstr "" +"Initialization file of hello " +"module." + +msgid "" +"Function file related to hello " +"module." +msgstr "" +"Function file related to hello " +"module." + +msgid "" +" presents a complete " +"structure for module environments you can use as reference for " +"writing your own modules. It begins with a parent module directory " +"named “Hello” which contains an initialization file (“hello.sh”) " +"and one related function file (“hello_getOptions.sh”). These files " +"work together with a child module named output which in turn has four child modules inside " +"named camel,lower,random, and upper. The " +"Locales directory contains the required " +"information to print hello " +"messages in different languages (e.g., it only supports Spanish " +"language in our example, but it can be extended to other languages " +"as needed). The Manuals directory contains all " +"the files required to produce documentation for the hello module (e.g., the information you read " +"when provide the —help option " +"in the command-line)." +msgstr "" +" presents a complete " +"structure for module environments you can use as reference for " +"writing your own modules. It begins with a parent module directory " +"named “Hello” which contains an initialization file (“hello.sh”) " +"and one related function file (“hello_getOptions.sh”). These files " +"work together with a child module named output which in turn has four child modules inside " +"named camel,lower,random, and upper. The " +"Locales directory contains the required " +"information to print hello " +"messages in different languages (e.g., it only supports Spanish " +"language in our example, but it can be extended to other languages " +"as needed). The Manuals directory contains all " +"the files required to produce documentation for the hello module (e.g., the information you read " +"when provide the —help option " +"in the command-line)." + +msgid "The Function Files" +msgstr "The Function Files" + +msgid "" +"The function files are used to create the initialization file of a " +"module and the related functions of it. As convention, both " +"initialization file and related function files are stored in the " +"module's directory, see ." +msgstr "" +"The function files are used to create the initialization file of a " +"module and the related functions of it. As convention, both " +"initialization file and related function files are stored in the " +"module's directory, see ." + +msgid "" +"At execution time, the definition of related function are exported " +"to centos-art.sh execution " +"environment before executing the function definition set inside the " +"initialization file, so related functions are always available for " +"you to use in the initialization file file and other related " +"functions as well. This is rather useful when you are refactoring " +"your initialization scripts and probably related functions as well." +msgstr "" +"At execution time, the definition of related function are exported " +"to centos-art.sh execution " +"environment before executing the function definition set inside the " +"initialization file, so related functions are always available for " +"you to use in the initialization file file and other related " +"functions as well. This is rather useful when you are refactoring " +"your initialization scripts and probably related functions as well." + +msgid "" +"As naming convention, related function files are written using the " +"module's name, then an underscore (“_”), then a descriptive name " +"and, finally, the “.sh” extension. The function " +"definition inside the function file also follows this convention " +"but excludes the “.sh” extension from name (e." +"g., the function file “hello_getOptions.sh” has " +"a function definition named “hello_getOptions” " +"inside). The centos-art.sh " +"script relays in these conventions to export and destroy related " +"functions when new module environments are created and destroyed. " +"If you create related function files with a pattern different from " +"that described here, they will not be executed nor available inside " +"the initialization file of the module environment being currently " +"executed." +msgstr "" +"As naming convention, related function files are written using the " +"module's name, then an underscore (“_”), then a descriptive name " +"and, finally, the “.sh” extension. The function " +"definition inside the function file also follows this convention " +"but excludes the “.sh” extension from name (e." +"g., the function file “hello_getOptions.sh” has " +"a function definition named “hello_getOptions” " +"inside). The centos-art.sh " +"script relays in these conventions to export and destroy related " +"functions when new module environments are created and destroyed. " +"If you create related function files with a pattern different from " +"that described here, they will not be executed nor available inside " +"the initialization file of the module environment being currently " +"executed." + +msgid "" +"See also: and ." +msgstr "" +"See also: and ." + +msgid "The Modules Directory" +msgstr "The Modules Directory" + +msgid "" +"This directory contains nested modules (e.g., child modules) and is " +"used for extending the current module functionality in a modular " +"way. There isn't a visible limitation in the number of " +"Modules directory you can nest inside one module " +"to achieve certain functionality so, you can create as many levels " +"of Modules directories as you need." +msgstr "" +"This directory contains nested modules (e.g., child modules) and is " +"used for extending the current module functionality in a modular " +"way. There isn't a visible limitation in the number of " +"Modules directory you can nest inside one module " +"to achieve certain functionality so, you can create as many levels " +"of Modules directories as you need." + +msgid "The Locales Directory" +msgstr "The Locales Directory" + +msgid "" +"This directory contains module-specific localization files. The " +"content of this directory is automatically generated by locale module of centos-art.sh script, when you execute it using the " +"initialization file as source and the —" +"update —sibling options. Once the localization files " +"have been created, you need to edit PO files to translate the " +"strings from English to your preferred language. If the " +"translatable strings inside the module's source files change, you " +"need to run the locale module " +"again to update the PO files and repeat the localization process " +"all over again." +msgstr "" +"This directory contains module-specific localization files. The " +"content of this directory is automatically generated by locale module of centos-art.sh script, when you execute it using the " +"initialization file as source and the —" +"update —sibling options. Once the localization files " +"have been created, you need to edit PO files to translate the " +"strings from English to your preferred language. If the " +"translatable strings inside the module's source files change, you " +"need to run the locale module " +"again to update the PO files and repeat the localization process " +"all over again." + +msgid "The Manuals Directory" +msgstr "The Manuals Directory" + +msgid "" +"This directory contains module-specific documentation. " +"Documentation in this directory is written in asciidoc format and " +"produced through the render " +"module of centos-art.sh script " +"to different formats, including man pages and html." +msgstr "" +"This directory contains module-specific documentation. " +"Documentation in this directory is written in asciidoc format and " +"produced through the render " +"module of centos-art.sh script " +"to different formats, including man pages and html." + +msgid "The Configs Directory" +msgstr "The Configs Directory" + +msgid "" +"This directory contains module-specific configuration. Some modules " +"(e.g., “tuneup”) need to store auxiliary files required to achieve " +"its main goal (e.g., the “tuneup” module uses sed files to " +"transform the top-comment of scripts each time it is executed, the " +"sed file itself is stored in this directory). Whenever you need to " +"make reference to a file inside this directory, use the " +"“TCAR_MODULE_DIR_CONFIGS” variable. This variable provides the " +"absolute path of module-related configuration file." +msgstr "" +"This directory contains module-specific configuration. Some modules " +"(e.g., “tuneup”) need to store auxiliary files required to achieve " +"its main goal (e.g., the “tuneup” module uses sed files to " +"transform the top-comment of scripts each time it is executed, the " +"sed file itself is stored in this directory). Whenever you need to " +"make reference to a file inside this directory, use the " +"“TCAR_MODULE_DIR_CONFIGS” variable. This variable provides the " +"absolute path of module-related configuration file." + +msgid "" +"This section has covered the directories and files a module is made " +"of inside the centos-art.sh " +"script." +msgstr "" +"This section has covered the directories and files a module is made " +"of inside the centos-art.sh " +"script." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Manuals/Understanding_Modules/render.conf b/Automation/Manuals/Understanding_Modules/render.conf index e705483..ccb0c7a 100644 --- a/Automation/Manuals/Understanding_Modules/render.conf +++ b/Automation/Manuals/Understanding_Modules/render.conf @@ -2,7 +2,7 @@ render-type = "asciidoc" render-flow = "article" render-from = "understanding_modules.asciidoc" -locale-from = "${TCAR_SCRIPT_LANG_LC}/messages.po" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/understanding_modules.asciidoc.po" images-from = "${TCAR_BASEDIR}/Artworks/Icons/Webenv" styles-from = "${TCAR_BASEDIR}/Artworks/Webenv/Docbook/1.69.1/Css" formats = "xhtml" diff --git a/Automation/Manuals/Understanding_Modules/understanding_modules.asciidoc b/Automation/Manuals/Understanding_Modules/understanding_modules.asciidoc index 8dc8f20..6b2f156 100644 --- a/Automation/Manuals/Understanding_Modules/understanding_modules.asciidoc +++ b/Automation/Manuals/Understanding_Modules/understanding_modules.asciidoc @@ -6,20 +6,20 @@ v0.1, Oct 2013 Overview -------- -From version 0.5, the *centos-art.sh* script introduces the idea of +From version 0.5, *centos-art.sh* script implements the idea of modules to its base design. Modules are a collection of functions -written in Bash that can call one another to create individual -execution environments. They may be nested to achieve high levels of -maintainability and extensibility. This make possible for modules -writers to divide complicated tasks into smaller tasks that can be -easier to debug, maintain and share with other modules efficiently -(e.g., instead of loading modules all at once, they are only loaded at -demand and unset once they conclude their execution). +written in Bash that can call themselves one another to create +individual execution environments. They may be nested to achieve high +levels of maintainability and extensibility. This make possible for +modules writers to divide complicated tasks into smaller tasks that +can be easier to debug, maintain and share with other modules +efficiently (e.g., instead of loading modules all at once, they are +only loaded at demand and unset once they conclude their execution). This article describes the modular design of *centos-art.sh* script. It is a good place for you to start if you are planning to contribute new module environments to *centos-art.sh* script or want to know more -about how it works. The next section delves into what a module +about how they work. The next section delves into what a module environment is, the three module types you can find in it and the correct way of execute each one of them. @@ -28,18 +28,18 @@ Module Environment ------------------ When you execute the *centos-art.sh* script you create an execution -environment in which variables and functions are defined. The +environment in which variables and functions are defined. This execution environment is the higher environment inside *centos-art.sh* script. It is considered to have a ``global'' scope, so variables and -functions defined in it are always available for any function +functions defined inside it are always available for any function execution made from it. You can control the execution environment of -*centos-art.sh* script through files +centos-art.sh+ and -+centos-art.conf.sh+. These files don't provide too much functionality -so module environments are executed from +centos-art.sh+, to extend -its functionality. +*centos-art.sh* script through +centos-art.sh+ and ++centos-art.conf.sh+ files. These files don't provide too much +functionality so specific module environments are executed from ++centos-art.sh+ at demand, to extend its functionality. Module environments are made of small functions that perform small -tasks and can be further executed in a specific order to produce the +tasks and can be further executed in a specific order to produce a desired result. Module environments are executed and destroyed at demand. Inside *centos-art.sh*, module environments can be either ``parent modules,'' ``child modules,'' or ``sibling modules.'' diff --git a/Automation/Manuals/render.conf b/Automation/Manuals/render.conf index 20d26de..9ba001d 100644 --- a/Automation/Manuals/render.conf +++ b/Automation/Manuals/render.conf @@ -2,7 +2,7 @@ render-type = "asciidoc" render-flow = "manpage" render-from = "centos-art.sh.asciidoc" -locale-from = "${TCAR_SCRIPT_LANG_LC}/centos-art.sh.po" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/centos-art.sh.po" formats = "xhtml manpage" mansect = "1" @@ -10,6 +10,6 @@ mansect = "1" render-type = "asciidoc" render-flow = "manpage" render-from = "tcar_setModuleEnvironment.sh.asciidoc" -locale-from = "${TCAR_SCRIPT_LANG_LC}/tcar_setModuleEnvironment.sh.po" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/tcar_setModuleEnvironment.sh.po" formats = "xhtml manpage" mansect = "1" diff --git a/Automation/Modules/Hello/Manuals/Locales/en_US/hello.asciidoc.po b/Automation/Modules/Hello/Manuals/Locales/en_US/hello.asciidoc.po new file mode 100644 index 0000000..b0558b4 --- /dev/null +++ b/Automation/Modules/Hello/Manuals/Locales/en_US/hello.asciidoc.po @@ -0,0 +1,225 @@ +msgid "" +msgstr "" +"Project-Id-Version: hello.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-07 14:34-0500\n" +"PO-Revision-Date: 2013-11-07 14:34-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "hello" +msgstr "hello" + +msgid "1" +msgstr "1" + +msgid "Print out greetings and exit successfully." +msgstr "Print out greetings and exit successfully." + +msgid "centos-art hello [OPTIONS]" +msgstr "centos-art hello [OPTIONS]" + +msgid "Description" +msgstr "Description" + +msgid "" +"The hello module is very " +"simple. Its main purpose is to print out the “Hello, World!” " +"greeting to standard output and exit successfully. You can use " +"options to change the greeting message and the way it is printed " +"out. The hello module provides " +"a very simple example you can use as base to understand how modules " +"work inside centos-art.sh " +"script. You can this understanding to start writing your own " +"modules for centos-art.sh " +"script." +msgstr "" +"The hello module is very " +"simple. Its main purpose is to print out the “Hello, World!” " +"greeting to standard output and exit successfully. You can use " +"options to change the greeting message and the way it is printed " +"out. The hello module provides " +"a very simple example you can use as base to understand how modules " +"work inside centos-art.sh " +"script. You can this understanding to start writing your own " +"modules for centos-art.sh " +"script." + +msgid "Options" +msgstr "Options" + +msgid "" +"The hello module accepts the " +"following options:" +msgstr "" +"The hello module accepts the " +"following options:" + +msgid "-h | --help" +msgstr "-h | --help" + +msgid "Print out module's documentation." +msgstr "Print out module's documentation." + +msgid "-v | --version" +msgstr "-v | --version" + +msgid "Print out module's version and legal status." +msgstr "Print out module's version and legal status." + +msgid "-d | --debug" +msgstr "-d | --debug" + +msgid "" +"Run the script in debugging mode. This option is very useful if you " +"want to get a closer look to module environments being executed and " +"destroyed at run-time." +msgstr "" +"Run the script in debugging mode. This option is very useful if you " +"want to get a closer look to module environments being executed and " +"destroyed at run-time." + +msgid "-g \"TEXT\" | --greeting=\"TEXT\"" +msgstr "-g \"TEXT\" | --greeting=\"TEXT\"" + +msgid "" +"Set a different greeting message to be printed out. This option " +"accepts a value as argument. The text you provide must not have " +"empty spaces on it. By default, when you don't provide this option, " +"hello module prints out " +"“Hello, World” as greeting. If translations of this message are " +"available for your locale, they will be printed instead." +msgstr "" +"Set a different greeting message to be printed out. This option " +"accepts a value as argument. The text you provide must not have " +"empty spaces on it. By default, when you don't provide this option, " +"hello module prints out " +"“Hello, World” as greeting. If translations of this message are " +"available for your locale, they will be printed instead." + +msgid "-l | --lower" +msgstr "-l | --lower" + +msgid "" +"Print greeting message in lowercase. The final output is printed " +"out all in one line." +msgstr "" +"Print greeting message in lowercase. The final output is printed " +"out all in one line." + +msgid "-u | --upper" +msgstr "-u | --upper" + +msgid "" +"Print greeting message in uppercase. The final output is printed " +"out all in one line." +msgstr "" +"Print greeting message in uppercase. The final output is printed " +"out all in one line." + +msgid "-c | --camel" +msgstr "-c | --camel" + +msgid "" +"Print greeting messages in camel-case (e.g., \"HeLlO, WoRlD!\"). " +"The output is printed out one character per line. This might not " +"have sense but it helps to describe how execution of sibling " +"modules work. Notice that, when printing final output, punctuation " +"marks doesn't count for formating." +msgstr "" +"Print greeting messages in camel-case (e.g., \"HeLlO, WoRlD!\"). " +"The output is printed out one character per line. This might not " +"have sense but it helps to describe how execution of sibling " +"modules work. Notice that, when printing final output, punctuation " +"marks doesn't count for formating." + +msgid "-r | --random" +msgstr "-r | --random" + +msgid "" +"Print letters of a greeting message in a random order (e.g., " +"rdodldrl!,,!). The final output is printed out one character per " +"line. This might not have sense but it helps to describe how " +"recursive execution of sibling modules work." +msgstr "" +"Print letters of a greeting message in a random order (e.g., " +"rdodldrl!,,!). The final output is printed out one character per " +"line. This might not have sense but it helps to describe how " +"recursive execution of sibling modules work." + +msgid "Exit Status" +msgstr "Exit Status" + +msgid "" +"The hello module ends its " +"execution with one of the following exit status:" +msgstr "" +"The hello module ends its " +"execution with one of the following exit status:" + +msgid "0 — Exit successfully without errors." +msgstr "0 — Exit successfully without errors." + +msgid "1 — Exit with errors." +msgstr "1 — Exit with errors." + +msgid "Authors" +msgstr "Authors" + +msgid "" +"The hello module has received " +"contribution from the following people:" +msgstr "" +"The hello module has received " +"contribution from the following people:" + +msgid "" +"Alain Reguera Delgado <al@centos.org.cu>, 2013" +msgstr "" +"Alain Reguera Delgado <al@centos.org.cu>, 2013" + +msgid "Copyright" +msgstr "Copyright" + +msgid "Copyright © 2009-2013 The CentOS Artwork SIG" +msgstr "Copyright © 2009-2013 The CentOS Artwork SIG" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." +msgstr "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Modules/Hello/Manuals/render.conf b/Automation/Modules/Hello/Manuals/render.conf index d74bd04..f01d586 100644 --- a/Automation/Modules/Hello/Manuals/render.conf +++ b/Automation/Modules/Hello/Manuals/render.conf @@ -2,6 +2,6 @@ render-type = "asciidoc" render-flow = "manpage" render-from = "hello.asciidoc" -locale-from = "${TCAR_SCRIPT_LANG_LC}/hello.asciidoc.po" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/hello.asciidoc.po" formats = "xhtml manpage" mansect = "1" diff --git a/Automation/Modules/Prepare/Manuals/Locales/en_US/prepare.po b/Automation/Modules/Prepare/Manuals/Locales/en_US/prepare.po new file mode 100644 index 0000000..8472ab2 --- /dev/null +++ b/Automation/Modules/Prepare/Manuals/Locales/en_US/prepare.po @@ -0,0 +1,331 @@ +msgid "" +msgstr "" +"Project-Id-Version: prepare.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-07 14:49-0500\n" +"PO-Revision-Date: 2013-11-07 14:49-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "prepare" +msgstr "prepare" + +msgid "1" +msgstr "1" + +msgid "Prepare your workstation for using the repository." +msgstr "Prepare your workstation for using the repository." + +msgid "centos-art.sh prepare [OPTIONS]" +msgstr "centos-art.sh prepare [OPTIONS]" + +msgid "Description" +msgstr "Description" + +msgid "" +"The first time you download the CentOS artwork repository into your " +"workstation, you only find source files inside the repository. In " +"order to produce each component of CentOS corporate visual " +"identity, it is necessary that you first transform the source files " +"(e.g., .svgz, .asciidoc, " +".po) into final files (e.g., .png, .html, .mo). This " +"process is known as preparing your workstation to use the " +"repository and is standardized through the prepare module. This way, the prepare module is the first command you " +"execute after downloading a fresh copy of CentOS artwork repository." +msgstr "" +"The first time you download the CentOS artwork repository into your " +"workstation, you only find source files inside the repository. In " +"order to produce each component of CentOS corporate visual " +"identity, it is necessary that you first transform the source files " +"(e.g., .svgz, .asciidoc, " +".po) into final files (e.g., .png, .html, .mo). This " +"process is known as preparing your workstation to use the " +"repository and is standardized through the prepare module. This way, the prepare module is the first command you " +"execute after downloading a fresh copy of CentOS artwork repository." + +msgid "" +"When you execute the prepare " +"module without any option, it first checks existence of required " +"packages (see --packages), then updates the locale information " +"required by centos-art.sh " +"script to show messages in your current locale, later renders " +"documentation (see --documents) and images (see --images) using " +"source files available inside the repository. Finally, it updates " +"the link relation that connects content inside the repository and " +"the applications outside it (see --links)." +msgstr "" +"When you execute the prepare " +"module without any option, it first checks existence of required " +"packages (see --packages), then updates the locale information " +"required by centos-art.sh " +"script to show messages in your current locale, later renders " +"documentation (see --documents) and images (see --images) using " +"source files available inside the repository. Finally, it updates " +"the link relation that connects content inside the repository and " +"the applications outside it (see --links)." + +msgid "" +"When you execute the prepare " +"module with options, the order in which preparation actions take " +"place is set by the order in which you passed the options. See " +", for more information about available " +"options and what they do." +msgstr "" +"When you execute the prepare " +"module with options, the order in which preparation actions take " +"place is set by the order in which you passed the options. See " +", for more information about available " +"options and what they do." + +msgid "" +"Once the prepare module " +"completes its execution, both your workstation and your copy of " +"CentOS artwork repository will be ready for production." +msgstr "" +"Once the prepare module " +"completes its execution, both your workstation and your copy of " +"CentOS artwork repository will be ready for production." + +msgid "Options" +msgstr "Options" + +msgid "" +"The prepare module accepts the " +"following options:" +msgstr "" +"The prepare module accepts the " +"following options:" + +msgid "--help" +msgstr "--help" + +msgid "Print module's documentation." +msgstr "Print module's documentation." + +msgid "--version" +msgstr "--version" + +msgid "Print module's version." +msgstr "Print module's version." + +msgid "--packages" +msgstr "--packages" + +msgid "" +"This option verifies whether you have installed the required " +"packages in your workstation or not. If they are not installed an " +"error will be printed telling you what the missing package is, so " +"you can install it. It is important that all the required packages " +"be installed for centos-art.sh " +"script modules to work as expected." +msgstr "" +"This option verifies whether you have installed the required " +"packages in your workstation or not. If they are not installed an " +"error will be printed telling you what the missing package is, so " +"you can install it. It is important that all the required packages " +"be installed for centos-art.sh " +"script modules to work as expected." + +msgid "" +"When you are verifying packages, be aware that it is required that " +"you have installed EPEL repository. The EPEL configuration package " +"(epel-release) isn't part of " +"CentOS distribution and you need to download it and install it " +"manually. The epel-release " +"package can be found in either of the locations (based on your " +"system version):" +msgstr "" +"When you are verifying packages, be aware that it is required that " +"you have installed EPEL repository. The EPEL configuration package " +"(epel-release) isn't part of " +"CentOS distribution and you need to download it and install it " +"manually. The epel-release " +"package can be found in either of the locations (based on your " +"system version):" + +msgid "" +"For CentOS-5: http://download.fedoraproject.org/pub/epel/5/i386/" +msgstr "" +"For CentOS-5: http://download.fedoraproject.org/pub/epel/5/i386/" + +msgid "" +"For CentOS-6: http://download.fedoraproject.org/pub/epel/6/i386/" +msgstr "" +"For CentOS-6: http://download.fedoraproject.org/pub/epel/6/i386/" + +msgid "--locales" +msgstr "--locales" + +msgid "" +"This option looks for all translatable strings inside the centos-art.sh script, updates the " +"related POT and PO files and produces the related MO file using the " +"specific locale environment information the script was run in. If " +"the PO file already have translations, they are preserved and used " +"to build the MO file." +msgstr "" +"This option looks for all translatable strings inside the centos-art.sh script, updates the " +"related POT and PO files and produces the related MO file using the " +"specific locale environment information the script was run in. If " +"the PO file already have translations, they are preserved and used " +"to build the MO file." + +msgid "--links" +msgstr "--links" + +msgid "" +"This updates the link information that connects the information " +"inside the repository with the information outside the repository. " +"For example, inside the repository we have the font information " +"required to build messages in specific typography, such information " +"isn't by default in the default system locations so we install them " +"in the home directory of the user running the prepare module, using symbolic links." +msgstr "" +"This updates the link information that connects the information " +"inside the repository with the information outside the repository. " +"For example, inside the repository we have the font information " +"required to build messages in specific typography, such information " +"isn't by default in the default system locations so we install them " +"in the home directory of the user running the prepare module, using symbolic links." + +msgid "" +"Whenever you need to update this information, use this option. Take " +"care that all links previously created in the target location will " +"be removed and recreated again. So, you can change the name " +"relation in the configuration files and install the changes without " +"leaving broken links in the target location." +msgstr "" +"Whenever you need to update this information, use this option. Take " +"care that all links previously created in the target location will " +"be removed and recreated again. So, you can change the name " +"relation in the configuration files and install the changes without " +"leaving broken links in the target location." + +msgid "" +"The file that controls the link configuration is inside the " +"repository at Automation/Modules/Prepare/Modules/Links/" +"Configs/render.conf." +msgstr "" +"The file that controls the link configuration is inside the " +"repository at Automation/Modules/Prepare/Modules/Links/" +"Configs/render.conf." + +msgid "--images" +msgstr "--images" + +msgid "" +"This option produces images from source files available inside the " +"repository, using the correct order. When you use this option, " +"centos-art.sh script calls the render module internally which " +"produces content for all configuration (render.conf) files found inside the repository." +msgstr "" +"This option produces images from source files available inside the " +"repository, using the correct order. When you use this option, " +"centos-art.sh script calls the render module internally which " +"produces content for all configuration (render.conf) files found inside the repository." + +msgid "--documents" +msgstr "--documents" + +msgid "" +"This options produces documentation from source files available " +"inside the repository. When you pass this option, the current " +"locale information is considered to produce the documentation. If " +"the current locale doesn't have translation files set for the " +"current locale information, English language is used as default " +"language." +msgstr "" +"This options produces documentation from source files available " +"inside the repository. When you pass this option, the current " +"locale information is considered to produce the documentation. If " +"the current locale doesn't have translation files set for the " +"current locale information, English language is used as default " +"language." + +msgid "Author" +msgstr "Author" + +msgid "" +"The prepare module has " +"received contributions from the following people:" +msgstr "" +"The prepare module has " +"received contributions from the following people:" + +msgid "" +"Alain Reguera Delgado <al@centos.org.cu>, 2009-2013" +msgstr "" +"Alain Reguera Delgado <al@centos.org.cu>, 2009-2013" + +msgid "Copyright" +msgstr "Copyright" + +msgid "Copyright © 2009-2013 The CentOS Project" +msgstr "Copyright © 2009-2013 The CentOS Project" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." +msgstr "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." + +msgid "See Also" +msgstr "See Also" + +msgid "" +"centos-art.sh(1), centos-art.sh-render(1), centos-art.sh-locale(1)" +msgstr "" +"centos-art.sh(1), centos-art.sh-render(1), centos-art.sh-locale(1)" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Modules/Prepare/Manuals/render.conf b/Automation/Modules/Prepare/Manuals/render.conf index 8822248..1b130ce 100644 --- a/Automation/Modules/Prepare/Manuals/render.conf +++ b/Automation/Modules/Prepare/Manuals/render.conf @@ -2,6 +2,6 @@ render-type = "asciidoc" render-flow = "manpage" render-from = "prepare.asciidoc" -locale-from = "${TCAR_SCRIPT_LANG_LC}/prepare.po" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/prepare.po" formats = "xhtml manpage" mansect = "1" diff --git a/Automation/Modules/Render/Manuals/Locales/en_US/render.asciidoc.po b/Automation/Modules/Render/Manuals/Locales/en_US/render.asciidoc.po new file mode 100644 index 0000000..53504ac --- /dev/null +++ b/Automation/Modules/Render/Manuals/Locales/en_US/render.asciidoc.po @@ -0,0 +1,1423 @@ +msgid "" +msgstr "" +"Project-Id-Version: render.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-07 15:16-0500\n" +"PO-Revision-Date: 2013-11-07 15:16-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "render" +msgstr "render" + +msgid "1" +msgstr "1" + +msgid "Standardize production tasks based on configuration files." +msgstr "Standardize production tasks based on configuration files." + +msgid "centos-art.sh render [OPTIONS] [DIRECTORY …]" +msgstr "centos-art.sh render [OPTIONS] [DIRECTORY …]" + +msgid "Description" +msgstr "Description" + +msgid "" +"When you execute the render " +"module, it looks for configuration files inside the “DIRECTORY” " +"specified in the command-line and processes them in the order they " +"were found. When no “DIRECTORY” is specified to centos-art.sh script, the render module looks for configuration files " +"inside the current directory it was executed from. If no " +"configuration file is found, the render module will end its execution with an error message." +msgstr "" +"When you execute the render " +"module, it looks for configuration files inside the “DIRECTORY” " +"specified in the command-line and processes them in the order they " +"were found. When no “DIRECTORY” is specified to centos-art.sh script, the render module looks for configuration files " +"inside the current directory it was executed from. If no " +"configuration file is found, the render module will end its execution with an error message." + +msgid "Options" +msgstr "Options" + +msgid "" +"The render module accepts the " +"following options:" +msgstr "" +"The render module accepts the " +"following options:" + +msgid "--help" +msgstr "--help" + +msgid "Print module's documentation." +msgstr "Print module's documentation." + +msgid "--version" +msgstr "--version" + +msgid "Print module's version." +msgstr "Print module's version." + +msgid "--filter=\"REGEX\"" +msgstr "--filter=\"REGEX\"" + +msgid "" +"This option reduces the number of section blocks inside " +"configuration files the render " +"module will take for processing. “REGEX” is a regular expression " +"pattern matching one or more section names inside the configuration " +"files found under “DIRECTORY”." +msgstr "" +"This option reduces the number of section blocks inside " +"configuration files the render " +"module will take for processing. “REGEX” is a regular expression " +"pattern matching one or more section names inside the configuration " +"files found under “DIRECTORY”." + +msgid "Configuration Files" +msgstr "Configuration Files" + +msgid "" +"The configuration files are regular files with the .conf extension. The name of configuration files is frequently " +"chosen for helping you to remember what the configuration files are " +"for and, in some cases, for producing section blocks in specific " +"order." +msgstr "" +"The configuration files are regular files with the .conf extension. The name of configuration files is frequently " +"chosen for helping you to remember what the configuration files are " +"for and, in some cases, for producing section blocks in specific " +"order." + +msgid "" +"The format used in configuration files use section blocks in the " +"form [section-name]. Each section block ends " +"when the next section block begins or at the end of the file. " +"Section blocks contain one or more variable definitions in the form " +"option = \"value\". In the specific case of " +"render module, the " +"section-name is an alphanumeric value and points " +"to the final file or directory you want to save the processing " +"results in. The configuration variables describe how to produce the " +"file or directory specified as section-name. " +"Name values in the section-name don't accept " +"variables or any kind of expansion in it, but configuration values " +"do. Commentaries are introduced by using the # " +"character at the beginning of lines. Commentaries defined this way " +"are excluded from processing so you can use them freely." +msgstr "" +"The format used in configuration files use section blocks in the " +"form [section-name]. Each section block ends " +"when the next section block begins or at the end of the file. " +"Section blocks contain one or more variable definitions in the form " +"option = \"value\". In the specific case of " +"render module, the " +"section-name is an alphanumeric value and points " +"to the final file or directory you want to save the processing " +"results in. The configuration variables describe how to produce the " +"file or directory specified as section-name. " +"Name values in the section-name don't accept " +"variables or any kind of expansion in it, but configuration values " +"do. Commentaries are introduced by using the # " +"character at the beginning of lines. Commentaries defined this way " +"are excluded from processing so you can use them freely." + +msgid "" +"The configuration files are processed from top to bottom. This is a " +"very important aspect to consider in situations where you need to " +"grantee specific priority for content production (e.g., you have " +"several files in a configuration file and need to produce some of " +"them before others). So, because configuration files are processed " +"from top to bottom, section blocks set first in the configuration " +"file are processed first and section blocks set later are processed " +"later." +msgstr "" +"The configuration files are processed from top to bottom. This is a " +"very important aspect to consider in situations where you need to " +"grantee specific priority for content production (e.g., you have " +"several files in a configuration file and need to produce some of " +"them before others). So, because configuration files are processed " +"from top to bottom, section blocks set first in the configuration " +"file are processed first and section blocks set later are processed " +"later." + +msgid "" +"The configuration files can be divided in separated configuration " +"files to produce specific section blocks with a given priority. For " +"example, if you have the file “render.conf”, you can divide its " +"content in “render-1.conf”, “render-2.conf” to produce section " +"blocks inside “render-1.conf” first and “render-2.conf” later. This " +"sort of division might be very useful when the configuration file " +"begins to grow, or you want to control the order in which specific " +"groups of files are produced inside “DIRECTORY”." +msgstr "" +"The configuration files can be divided in separated configuration " +"files to produce specific section blocks with a given priority. For " +"example, if you have the file “render.conf”, you can divide its " +"content in “render-1.conf”, “render-2.conf” to produce section " +"blocks inside “render-1.conf” first and “render-2.conf” later. This " +"sort of division might be very useful when the configuration file " +"begins to grow, or you want to control the order in which specific " +"groups of files are produced inside “DIRECTORY”." + +msgid "" +"Inside configuration files, configuration variables can take " +"different meanings based on the section contexts. The context of a " +"section block is defined by the render-" +"type variables." +msgstr "" +"Inside configuration files, configuration variables can take " +"different meanings based on the section contexts. The context of a " +"section block is defined by the render-" +"type variables." + +msgid "render-type" +msgstr "render-type" + +msgid "" +"Optional. This variable specifies the type of content rendition the " +"render module will perform. " +"This variable can take one of the following values: “archive”, " +"“asciidoc”, “compress”, “images”, “palette”, and “svg”. When this " +"variable is not set, the render module tries to determine the type of rendition based on " +"the file extension of the first file passed through render-from variable. If no valid value is " +"found there either, the render " +"module ends with an error message." +msgstr "" +"Optional. This variable specifies the type of content rendition the " +"render module will perform. " +"This variable can take one of the following values: “archive”, " +"“asciidoc”, “compress”, “images”, “palette”, and “svg”. When this " +"variable is not set, the render module tries to determine the type of rendition based on " +"the file extension of the first file passed through render-from variable. If no valid value is " +"found there either, the render " +"module ends with an error message." + +msgid "render-from" +msgstr "render-from" + +msgid "" +"Required. This variable specifies the file name of the source file " +"(design model) used to produce the final file specified in the " +"section line. This option can receive absolute paths and relative " +"paths. Absolute paths begin with a slash (“/”) character while " +"relative paths begin with the dot slash (“./”) characters or no " +"character at all. This variable can receive more than one value by " +"using either path expansion in one variable definition, or several " +"variables definitions." +msgstr "" +"Required. This variable specifies the file name of the source file " +"(design model) used to produce the final file specified in the " +"section line. This option can receive absolute paths and relative " +"paths. Absolute paths begin with a slash (“/”) character while " +"relative paths begin with the dot slash (“./”) characters or no " +"character at all. This variable can receive more than one value by " +"using either path expansion in one variable definition, or several " +"variables definitions." + +msgid "Using Paths" +msgstr "Using Paths" + +msgid "" +"When you provide absolute paths inside configuration files, there " +"isn't confusion about the location where the file is or should be. " +"However, it introduces rigidity to directory structures inside the " +"working copy when it is necessary to move directories from one " +"place to another inside the working copy. To eliminate this " +"mobility restrictions, relative paths can be used to create modular " +"directory structures." +msgstr "" +"When you provide absolute paths inside configuration files, there " +"isn't confusion about the location where the file is or should be. " +"However, it introduces rigidity to directory structures inside the " +"working copy when it is necessary to move directories from one " +"place to another inside the working copy. To eliminate this " +"mobility restrictions, relative paths can be used to create modular " +"directory structures." + +msgid "" +"When you use relative paths inside configuration files, paths are " +"relative to the location where the configuration file is stored in. " +"This way it is possible to move whole directory structures without " +"touching the configuration file and still have a render-able " +"structures inside the working copy. However, relative paths get " +"limited in situations where the production process needs files " +"outside the directory where the configuration file is stored in. In " +"such cases, a combination of relative and absolute paths is the " +"solution to apply." +msgstr "" +"When you use relative paths inside configuration files, paths are " +"relative to the location where the configuration file is stored in. " +"This way it is possible to move whole directory structures without " +"touching the configuration file and still have a render-able " +"structures inside the working copy. However, relative paths get " +"limited in situations where the production process needs files " +"outside the directory where the configuration file is stored in. In " +"such cases, a combination of relative and absolute paths is the " +"solution to apply." + +msgid "" +"When we need to use absolute paths to several files in the same " +"directory (e.g., we are combining them all to produce a new image) " +"but outside the current directory the configuration file is stored " +"in, it is possible to use a list of absolute paths one beside " +"another separated by space or we can use path expansion which is " +"shorter and easier to read. Path expansion is interpreted when you " +"enclose a list of file names in curly brackets using comma as " +"separator without spaces (e.g., /some/dir/{file1,file2," +"file3}). In order for path expansion to work correctly, " +"all the file names you put inside the curly brackets' list must " +"exist in the location specified first." +msgstr "" +"When we need to use absolute paths to several files in the same " +"directory (e.g., we are combining them all to produce a new image) " +"but outside the current directory the configuration file is stored " +"in, it is possible to use a list of absolute paths one beside " +"another separated by space or we can use path expansion which is " +"shorter and easier to read. Path expansion is interpreted when you " +"enclose a list of file names in curly brackets using comma as " +"separator without spaces (e.g., /some/dir/{file1,file2," +"file3}). In order for path expansion to work correctly, " +"all the file names you put inside the curly brackets' list must " +"exist in the location specified first." + +msgid "Using Environment Variables" +msgstr "Using Environment Variables" + +msgid "" +"The configuration files let you to use environment variables inside " +"them. This might result very useful when you need to provide " +"absolute paths based on variable information (e.g., the current " +"locale information). Some of the most important environment " +"variables used by centos-art.sh script -and its configuration files- are described below:" +msgstr "" +"The configuration files let you to use environment variables inside " +"them. This might result very useful when you need to provide " +"absolute paths based on variable information (e.g., the current " +"locale information). Some of the most important environment " +"variables used by centos-art.sh script -and its configuration files- are described below:" + +msgid "TCAR_BASEDIR" +msgstr "TCAR_BASEDIR" + +msgid "" +"This variable contains the absolute path to your repository's " +"working copy. The value of this variable is defined as read-only " +"inside centos-art.sh script " +"and cannot be modified later. As a matter of convenience, users " +"make use of their “~/.bash_profile” file to define this variable " +"there and, this way, skip the sometimes annoyance absolute path " +"questioning the centos-art.sh " +"script does in order to know the absolute path of the working copy " +"it is going to work with." +msgstr "" +"This variable contains the absolute path to your repository's " +"working copy. The value of this variable is defined as read-only " +"inside centos-art.sh script " +"and cannot be modified later. As a matter of convenience, users " +"make use of their “~/.bash_profile” file to define this variable " +"there and, this way, skip the sometimes annoyance absolute path " +"questioning the centos-art.sh " +"script does in order to know the absolute path of the working copy " +"it is going to work with." + +msgid "" +"Whenever you set absolute paths inside configuration files to refer " +"locations inside your working copy, it is necessary that you use " +"the TCAR_BASEDIR environment variable in front " +"of each path definition you set. TCAR_SCRIPT_LANG_LL:: This variable contains the language part of the current " +"locale information. For instance, if the current locale is “en_US." +"UTF-8”, the value of this variable would be “en”. " +"TCAR_SCRIPT_LANG_CC:: This variable contains the " +"country part of the current locale information. For instance, if " +"the current locale is “en_US.UTF-8”, the value of this variable " +"would be “US”. TCAR_SCRIPT_LANG_LC:: This " +"variable contains the current locale information in ll_CC format (e." +"g., es_ES). LANG:: This variable contains the " +"environment's current locale information." +msgstr "" +"Whenever you set absolute paths inside configuration files to refer " +"locations inside your working copy, it is necessary that you use " +"the TCAR_BASEDIR environment variable in front " +"of each path definition you set. TCAR_SCRIPT_LANG_LL:: This variable contains the language part of the current " +"locale information. For instance, if the current locale is “en_US." +"UTF-8”, the value of this variable would be “en”. " +"TCAR_SCRIPT_LANG_CC:: This variable contains the " +"country part of the current locale information. For instance, if " +"the current locale is “en_US.UTF-8”, the value of this variable " +"would be “US”. TCAR_SCRIPT_LANG_LC:: This " +"variable contains the current locale information in ll_CC format (e." +"g., es_ES). LANG:: This variable contains the " +"environment's current locale information." + +msgid "Rendering Archives" +msgstr "Rendering Archives" + +msgid "" +"When the render-type variable " +"is set to archive, the render module takes the list of files set through " +"render-from variable and " +"applies the value of command " +"to them all in order to produce the final file specified in the " +"section line. When the command variable is not specified, the " +"/bin/tar --remove-files -czf command is used as " +"default." +msgstr "" +"When the render-type variable " +"is set to archive, the render module takes the list of files set through " +"render-from variable and " +"applies the value of command " +"to them all in order to produce the final file specified in the " +"section line. When the command variable is not specified, the " +"/bin/tar --remove-files -czf command is used as " +"default." + +msgid "Rendering Image Files" +msgstr "Rendering Image Files" + +msgid "" +"When the render-type variable " +"is set to svg, the section block is interpreted " +"for rendering image files. When rendering image files, the " +"render-from variable must " +"point to a SVG files (either compressed or uncompressed). The " +"following following complementary variables are also accepted:" +msgstr "" +"When the render-type variable " +"is set to svg, the section block is interpreted " +"for rendering image files. When rendering image files, the " +"render-from variable must " +"point to a SVG files (either compressed or uncompressed). The " +"following following complementary variables are also accepted:" + +msgid "render-flow" +msgstr "render-flow" + +msgid "" +"Optional. This variable specifies the rendition flow to follow when " +"transforming SVG files into PNG images. This variable can take " +"either base or extended as " +"value. The base rendition flow takes one SVG " +"file and produces just one PNG image for it. The extended value applies the base rendition flow " +"and then transform the final PNG image to different heights, " +"formats, foreground colors and background colors. By default, when " +"this variable is not set, the base rendition " +"flow is used." +msgstr "" +"Optional. This variable specifies the rendition flow to follow when " +"transforming SVG files into PNG images. This variable can take " +"either base or extended as " +"value. The base rendition flow takes one SVG " +"file and produces just one PNG image for it. The extended value applies the base rendition flow " +"and then transform the final PNG image to different heights, " +"formats, foreground colors and background colors. By default, when " +"this variable is not set, the base rendition " +"flow is used." + +msgid "export-id" +msgstr "export-id" + +msgid "" +"Optional. This variable specifies the export id you want to use as " +"reference to produce PNG images from SVG files. The export-id is an " +"attribute you specified as unique value to an objects inside the " +"SVG file in order to export that object only but not the rest in " +"the SVG file. If this variable is not provided or it is empty, the " +"drawing area of the SVG file is used as reference to produce the " +"final PNG image." +msgstr "" +"Optional. This variable specifies the export id you want to use as " +"reference to produce PNG images from SVG files. The export-id is an " +"attribute you specified as unique value to an objects inside the " +"SVG file in order to export that object only but not the rest in " +"the SVG file. If this variable is not provided or it is empty, the " +"drawing area of the SVG file is used as reference to produce the " +"final PNG image." + +msgid "heights" +msgstr "heights" + +msgid "" +"Optional. This variable is available only for extended rendition flow and specifies the different image heights " +"you want to create copies of the final PNG image. The values " +"specified in this variable are separated by white space and should " +"be understandable by ImageMagick tool set. When this variable is " +"not provided, the render " +"module will create copies of final PNG image for several standard " +"heights." +msgstr "" +"Optional. This variable is available only for extended rendition flow and specifies the different image heights " +"you want to create copies of the final PNG image. The values " +"specified in this variable are separated by white space and should " +"be understandable by ImageMagick tool set. When this variable is " +"not provided, the render " +"module will create copies of final PNG image for several standard " +"heights." + +msgid "formats" +msgstr "formats" + +msgid "" +"Optional. This variable is available only for extended rendition flow and specifies the different image formats " +"you want to create copies of the final PNG image. The values " +"specified in this variable are separated by white space and should " +"be supported by ImageMagick tool set. When this variable is not " +"provided or set in the configuration file, the render module will create copies of final PNG " +"image for several standard formats." +msgstr "" +"Optional. This variable is available only for extended rendition flow and specifies the different image formats " +"you want to create copies of the final PNG image. The values " +"specified in this variable are separated by white space and should " +"be supported by ImageMagick tool set. When this variable is not " +"provided or set in the configuration file, the render module will create copies of final PNG " +"image for several standard formats." + +msgid "" +"To see the list of possible image formats supported by ImageMagick " +"tool set, run the following command: identify -list format." +msgstr "" +"To see the list of possible image formats supported by ImageMagick " +"tool set, run the following command: identify -list format." + +msgid "fgcolors" +msgstr "fgcolors" + +msgid "" +"Optional. This variable is available only for extended rendition flow and specifies the different foreground " +"colors you want to create copies of the final PNG image. To do " +"this, the image you want to copy should be rendered with black " +"color (000000) so the color replacement can be performed. The " +"values specified in this variable are separated by white space and " +"should be understandable by ImageMagick tool set. When this " +"variable is not provided the black foreground (000000) is used." +msgstr "" +"Optional. This variable is available only for extended rendition flow and specifies the different foreground " +"colors you want to create copies of the final PNG image. To do " +"this, the image you want to copy should be rendered with black " +"color (000000) so the color replacement can be performed. The " +"values specified in this variable are separated by white space and " +"should be understandable by ImageMagick tool set. When this " +"variable is not provided the black foreground (000000) is used." + +msgid "bgcolors" +msgstr "bgcolors" + +msgid "" +"Optional. This variable is available only for extended rendition flow and specifies the different background " +"colors you want to create copies of the final PNG image. This " +"variable uses Inkscape's --export-background " +"and --export-background-opacity options to " +"control the background information of final PNG images. Possible " +"values to this variable take the form XXXXXX-X, " +"where the first six X represent a color in " +"hexadecimal format and the final X might be 1 or " +"0. 1 for full opacity and 0 for full transparency. Intermediate " +"values between 0 and 1 (e.g., 0.55) can be given to control the " +"background opacity. When this variable is not provided, white " +"background full transparency (ffffff-0) is used " +"as default value." +msgstr "" +"Optional. This variable is available only for extended rendition flow and specifies the different background " +"colors you want to create copies of the final PNG image. This " +"variable uses Inkscape's --export-background " +"and --export-background-opacity options to " +"control the background information of final PNG images. Possible " +"values to this variable take the form XXXXXX-X, " +"where the first six X represent a color in " +"hexadecimal format and the final X might be 1 or " +"0. 1 for full opacity and 0 for full transparency. Intermediate " +"values between 0 and 1 (e.g., 0.55) can be given to control the " +"background opacity. When this variable is not provided, white " +"background full transparency (ffffff-0) is used " +"as default value." + +msgid "command" +msgstr "command" + +msgid "" +"Optional. This variable specifies the command used to modify the " +"production of final images. During the rendition process, images " +"are produced inside a temporal directory, and later moved to its " +"final location using the command specified as value in this " +"variable. When this variable is not specified, it can take one of " +"two values based on the amount of files passed through render-from variable. When just one file " +"is passed through the render-from variable, the default value for this variable is " +"/bin/cp, but when there are reference to more " +"than one file, the value of this option is /usr/bin/" +"convert +append which combines all images into the final " +"images." +msgstr "" +"Optional. This variable specifies the command used to modify the " +"production of final images. During the rendition process, images " +"are produced inside a temporal directory, and later moved to its " +"final location using the command specified as value in this " +"variable. When this variable is not specified, it can take one of " +"two values based on the amount of files passed through render-from variable. When just one file " +"is passed through the render-from variable, the default value for this variable is " +"/bin/cp, but when there are reference to more " +"than one file, the value of this option is /usr/bin/" +"convert +append which combines all images into the final " +"images." + +msgid "comment" +msgstr "comment" + +msgid "" +"Optional. This variable contains a sentence describing the image " +"you are creating. This information is written in the " +"comment field of PNG images. When this variable " +"is empty, no comment information will be written to the final PNG " +"image files." +msgstr "" +"Optional. This variable contains a sentence describing the image " +"you are creating. This information is written in the " +"comment field of PNG images. When this variable " +"is empty, no comment information will be written to the final PNG " +"image files." + +msgid "brand" +msgstr "brand" + +msgid "" +"Optional. This variable describes the branding information applied " +"to final images. The value of this variable has the form " +"FILENAME:GEOMETRY, where FILENAME is the absolute path to the PNG image you want to apply as " +"brand and, GEOMETRY takes the form " +"xHEIGHT+X+Y. In order to apply brand information " +"to final images correctly, the brand images files you want to apply " +"must be available. In case they don't exist the render module ends its execution with an " +"error message." +msgstr "" +"Optional. This variable describes the branding information applied " +"to final images. The value of this variable has the form " +"FILENAME:GEOMETRY, where FILENAME is the absolute path to the PNG image you want to apply as " +"brand and, GEOMETRY takes the form " +"xHEIGHT+X+Y. In order to apply brand information " +"to final images correctly, the brand images files you want to apply " +"must be available. In case they don't exist the render module ends its execution with an " +"error message." + +msgid "Rendering Image Files From Other Image Files" +msgstr "Rendering Image Files From Other Image Files" + +msgid "" +"To render image files from other image files, the render-type variable must be set to “images” " +"and one or more image files must be provided in the render-from variable. When the render module finds a section block with this " +"characteristics, it applies the value of command variable to all files found in render-from variable to produce the final " +"file specified in the section name." +msgstr "" +"To render image files from other image files, the render-type variable must be set to “images” " +"and one or more image files must be provided in the render-from variable. When the render module finds a section block with this " +"characteristics, it applies the value of command variable to all files found in render-from variable to produce the final " +"file specified in the section name." + +msgid "" +"When the command variable is " +"not specified, the “/usr/bin/convert -append” command is used as " +"default. This command takes all the images passed through render-from and appends them from top to " +"bottom and saves the result in the file you specified in the " +"section name. When you render files this way, the order in which " +"you define source files through render-" +"from may affect the final result based in the command you provided." +msgstr "" +"When the command variable is " +"not specified, the “/usr/bin/convert -append” command is used as " +"default. This command takes all the images passed through render-from and appends them from top to " +"bottom and saves the result in the file you specified in the " +"section name. When you render files this way, the order in which " +"you define source files through render-" +"from may affect the final result based in the command you provided." + +msgid "" +"The “images” rendition type provides an interface for external " +"image manipulation programs, like ImageMagick and NetPbm. You can " +"use these programs to manipulate images in great detail through the " +"command-line." +msgstr "" +"The “images” rendition type provides an interface for external " +"image manipulation programs, like ImageMagick and NetPbm. You can " +"use these programs to manipulate images in great detail through the " +"command-line." + +msgid "Rendering Images With Reduced Number Of Colors" +msgstr "Rendering Images With Reduced Number Of Colors" + +msgid "" +"When the render-type variable " +"is set to palette, the section block where this " +"variable was defined is interpreted for producing images with a " +"reduced number of colors. In these cases, the render-from variable must point to an image " +"file. The following complementary variables are also accepted:" +msgstr "" +"When the render-type variable " +"is set to palette, the section block where this " +"variable was defined is interpreted for producing images with a " +"reduced number of colors. In these cases, the render-from variable must point to an image " +"file. The following complementary variables are also accepted:" + +msgid "palette-gpl" +msgstr "palette-gpl" + +msgid "" +"Required. This variable addresses the palette of colors that will " +"be use for reducing colors. Generally, the palette of color file " +"ends with the .gpl extension and is stored in " +"the same directory of the configuration file. This file can be " +"produced by GIMP and provides an optimized set of colors for the " +"specific image you provided in the render-" +"from variable." +msgstr "" +"Required. This variable addresses the palette of colors that will " +"be use for reducing colors. Generally, the palette of color file " +"ends with the .gpl extension and is stored in " +"the same directory of the configuration file. This file can be " +"produced by GIMP and provides an optimized set of colors for the " +"specific image you provided in the render-" +"from variable." + +msgid "" +"To find the optimized set of colors, you need to open the image " +"specified in render-from in " +"GIMP, reduce its colors to the desired number using GIMP's Indexed " +"feature and, then, create a new palette by importing it from the " +"indexed image file. Once you have the palette this way, you need to " +"edit it using the Palettes dialog to add the hexadecimal value of " +"each color in the palette to the comment field, so you have a " +"palette file similar to the following:" +msgstr "" +"To find the optimized set of colors, you need to open the image " +"specified in render-from in " +"GIMP, reduce its colors to the desired number using GIMP's Indexed " +"feature and, then, create a new palette by importing it from the " +"indexed image file. Once you have the palette this way, you need to " +"edit it using the Palettes dialog to add the hexadecimal value of " +"each color in the palette to the comment field, so you have a " +"palette file similar to the following:" + +#, no-wrap +msgid "" +"GIMP Palette\n" +"Name: Syslinux-Default\n" +"Columns: 16\n" +"#\n" +" 32 76 141 204c8d\n" +" 37 82 146 255292\n" +" 52 94 153 345e99\n" +" 73 110 162 496ea2\n" +" 91 124 172 5b7cac\n" +"108 136 180 6c88b4\n" +"120 146 186 7892ba\n" +"131 158 193 839ec1\n" +"255 255 255 ffffff\n" +"146 170 200 92aac8\n" +"162 182 209 a2b6d1\n" +"183 199 219 b7c7db\n" +"204 216 230 ccd8e6\n" +"221 229 238 dde5ee\n" +"235 241 245 ebf1f5\n" +"246 251 254 f6fbfe" +msgstr "" +"GIMP Palette\n" +"Name: Syslinux-Default\n" +"Columns: 16\n" +"#\n" +" 32 76 141 204c8d\n" +" 37 82 146 255292\n" +" 52 94 153 345e99\n" +" 73 110 162 496ea2\n" +" 91 124 172 5b7cac\n" +"108 136 180 6c88b4\n" +"120 146 186 7892ba\n" +"131 158 193 839ec1\n" +"255 255 255 ffffff\n" +"146 170 200 92aac8\n" +"162 182 209 a2b6d1\n" +"183 199 219 b7c7db\n" +"204 216 230 ccd8e6\n" +"221 229 238 dde5ee\n" +"235 241 245 ebf1f5\n" +"246 251 254 f6fbfe" + +msgid "" +"Now that the palette has been created, you can set a path to " +"palette-gpl variable. Even you " +"can set path of palette-gpl " +"from GIMP's palettes directory (~/.gimp-x.x/palettes/), it is much more preferable that you copy the palette " +"file from that location to the configuration file's DIRECTORY " +"inside the repository and put it under version control, so others " +"can take benefit of it. The palette file is an integral part of " +"color specific image reduction so it must be near the configuration " +"file you use for such actions." +msgstr "" +"Now that the palette has been created, you can set a path to " +"palette-gpl variable. Even you " +"can set path of palette-gpl " +"from GIMP's palettes directory (~/.gimp-x.x/palettes/), it is much more preferable that you copy the palette " +"file from that location to the configuration file's DIRECTORY " +"inside the repository and put it under version control, so others " +"can take benefit of it. The palette file is an integral part of " +"color specific image reduction so it must be near the configuration " +"file you use for such actions." + +msgid "Rendering Documentation Files" +msgstr "Rendering Documentation Files" + +msgid "" +"To render documentation files, the render-" +"type variable must be set to “asciidoc” and the " +"render-from variable must " +"point to an Asciidoc file. When the render module finds this information in a section " +"block, it takes the asciidoc file as source and transforms it into " +"a docbook file using the asciidoc program. The docbook file is created temporarily for " +"further format transformations and removed later, once the final " +"format has been rendered." +msgstr "" +"To render documentation files, the render-" +"type variable must be set to “asciidoc” and the " +"render-from variable must " +"point to an Asciidoc file. When the render module finds this information in a section " +"block, it takes the asciidoc file as source and transforms it into " +"a docbook file using the asciidoc program. The docbook file is created temporarily for " +"further format transformations and removed later, once the final " +"format has been rendered." + +msgid "" +"When the render module creates " +"the intermediate docbook file, it considers the current locale " +"information of your environment (e.g., by reading the LANG " +"environment variable). In case the current locale information is " +"different to English (e.g., the value of LANG environment variable " +"doesn't begin with the “en” characters), the docbook file will be " +"localized based on the translation file specified in the locale-from variable, before applying " +"further format transformations to it. This way, further format " +"transformations from the temporarily docbook file will end up being " +"localized as well. If the locale-from variable is not present in the section block, the " +"intermediate docbook file won't be localized which make the final " +"result to be not localized either." +msgstr "" +"When the render module creates " +"the intermediate docbook file, it considers the current locale " +"information of your environment (e.g., by reading the LANG " +"environment variable). In case the current locale information is " +"different to English (e.g., the value of LANG environment variable " +"doesn't begin with the “en” characters), the docbook file will be " +"localized based on the translation file specified in the locale-from variable, before applying " +"further format transformations to it. This way, further format " +"transformations from the temporarily docbook file will end up being " +"localized as well. If the locale-from variable is not present in the section block, the " +"intermediate docbook file won't be localized which make the final " +"result to be not localized either." + +msgid "" +"When you set the render-type " +"variable to “asciidoc”, the section blocks need to have the " +"render-flow variable set to " +"“article”, “book” or “manpage”. This information defines the way " +"the intermediate docbook file is produced from the asciidoc file " +"and, by extension, the possible final results, too." +msgstr "" +"When you set the render-type " +"variable to “asciidoc”, the section blocks need to have the " +"render-flow variable set to " +"“article”, “book” or “manpage”. This information defines the way " +"the intermediate docbook file is produced from the asciidoc file " +"and, by extension, the possible final results, too." + +msgid "" +"When render-flow variable is " +"set to “article” or “book”, it is possible to produce final files " +"in “xhtml” format but not in “manpage” format. This is because man " +"pages require a specific document structure that both articles and " +"books don't need to have. When producing articles and books in " +"XHTML format, you can use the render-" +"page variable to control whether to produce the entire " +"book or article in just one file (“single”) or in separate files " +"linked one another (“chunks”)." +msgstr "" +"When render-flow variable is " +"set to “article” or “book”, it is possible to produce final files " +"in “xhtml” format but not in “manpage” format. This is because man " +"pages require a specific document structure that both articles and " +"books don't need to have. When producing articles and books in " +"XHTML format, you can use the render-" +"page variable to control whether to produce the entire " +"book or article in just one file (“single”) or in separate files " +"linked one another (“chunks”)." + +msgid "" +"When render-flow variable is " +"set to “manpage” it is possible to set the formats variable to either “manpage” or “xhtml” in " +"order to render the docbook file as man page or XHTML format, " +"respectively. you are producing man pages to a language different " +"to English, these required in order for man command to find the man pages in different " +"locales. The value of the man's volume section can be set using the " +"mansect variable. If this " +"variable is not set, the value of man's volume section will be 1." +msgstr "" +"When render-flow variable is " +"set to “manpage” it is possible to set the formats variable to either “manpage” or “xhtml” in " +"order to render the docbook file as man page or XHTML format, " +"respectively. you are producing man pages to a language different " +"to English, these required in order for man command to find the man pages in different " +"locales. The value of the man's volume section can be set using the " +"mansect variable. If this " +"variable is not set, the value of man's volume section will be 1." + +msgid "" +"When render-flow variable is " +"not set, the “article” value is used as default value." +msgstr "" +"When render-flow variable is " +"not set, the “article” value is used as default value." + +msgid "" +"When the formats variable has " +"the “xhtml” value, you need to set the images-from and styles-" +"from variables inside the related section block, no " +"matter what the value of render-flow would be. The value of images-" +"from and styles-from variables must point to a directory, inside the working " +"copy, containing the share images and CSS files used by XHTML " +"documents, respectively. If none of these two variables are set the " +"directories them." +msgstr "" +"When the formats variable has " +"the “xhtml” value, you need to set the images-from and styles-" +"from variables inside the related section block, no " +"matter what the value of render-flow would be. The value of images-" +"from and styles-from variables must point to a directory, inside the working " +"copy, containing the share images and CSS files used by XHTML " +"documents, respectively. If none of these two variables are set the " +"directories them." + +msgid "" +"When the formats variable is " +"not set, the “xhtml” value is used as default value." +msgstr "" +"When the formats variable is " +"not set, the “xhtml” value is used as default value." + +msgid "Rendering Localized Images" +msgstr "Rendering Localized Images" + +msgid "" +"To produce localized content, you need to set the locale-from variable in the section block you " +"want to provide translations and point its value to the translation " +"file where string translations will take place. Then, you need to " +"check the value of LANG environment variable to be sure it has the " +"locale information you want to translate messages for." +msgstr "" +"To produce localized content, you need to set the locale-from variable in the section block you " +"want to provide translations and point its value to the translation " +"file where string translations will take place. Then, you need to " +"check the value of LANG environment variable to be sure it has the " +"locale information you want to translate messages for." + +msgid "" +"If the LANG environment variable has the value you expect, run the " +"locale module on the " +"“DIRECTORY” you want to locale content. This read the source files " +"you specified in render-from " +"variable and would create the translation files (a.k.a., portable " +"objects) you need to edit to provide the string translations from " +"one language to another. Verify the translation file exist and edit " +"it to provide the strings translations. Once the strings have been " +"translated, execute the render " +"module on the “DIRECTORY”." +msgstr "" +"If the LANG environment variable has the value you expect, run the " +"locale module on the " +"“DIRECTORY” you want to locale content. This read the source files " +"you specified in render-from " +"variable and would create the translation files (a.k.a., portable " +"objects) you need to edit to provide the string translations from " +"one language to another. Verify the translation file exist and edit " +"it to provide the strings translations. Once the strings have been " +"translated, execute the render " +"module on the “DIRECTORY”." + +msgid "" +"When the render module finds " +"the locale-from variable in a " +"section block, it uses the xml2po program to create a localized instance of each source " +"file it finds in render-from " +"variable. Then, using the source files' localized instances, it " +"produces the final files based on render-" +"type variable's value." +msgstr "" +"When the render module finds " +"the locale-from variable in a " +"section block, it uses the xml2po program to create a localized instance of each source " +"file it finds in render-from " +"variable. Then, using the source files' localized instances, it " +"produces the final files based on render-" +"type variable's value." + +msgid "Examples" +msgstr "Examples" + +msgid "" +"Here are some practical configuration examples you can use as " +"reference to create your own configuration files." +msgstr "" +"Here are some practical configuration examples you can use as " +"reference to create your own configuration files." + +#, no-wrap +msgid "" +"[Xhtml-single]\n" +"render-type = \"asciidoc\"\n" +"render-flow = \"article\"\n" +"render-from = \"corporate.asciidoc\"\n" +"locale-from = \"${TCAR_SCRIPT_LANG_LC}/messages.po\"\n" +"images-from = \"${TCAR_BASEDIR}/Artworks/Icons/Webenv\"\n" +"styles-from = \"${TCAR_BASEDIR}/Artworks/Webenv/Docbook/1.69.1/Css\"\n" +"formats = \"xhtml\"\n" +"render-page = \"single\"" +msgstr "" +"[Xhtml-single]\n" +"render-type = \"asciidoc\"\n" +"render-flow = \"article\"\n" +"render-from = \"corporate.asciidoc\"\n" +"locale-from = \"${TCAR_SCRIPT_LANG_LC}/messages.po\"\n" +"images-from = \"${TCAR_BASEDIR}/Artworks/Icons/Webenv\"\n" +"styles-from = \"${TCAR_BASEDIR}/Artworks/Webenv/Docbook/1.69.1/Css\"\n" +"formats = \"xhtml\"\n" +"render-page = \"single\"" + +msgid "" +"When the render module reads " +"this configuration file, it initiates the asscidoc module which in turn initiates the xhtml module for transforming the corporate.asciidoc file into corporate.docbook file using " +"article as document type and result, the " +"render module produces the " +"directory of the configuration file as base directory." +msgstr "" +"When the render module reads " +"this configuration file, it initiates the asscidoc module which in turn initiates the xhtml module for transforming the corporate.asciidoc file into corporate.docbook file using " +"article as document type and result, the " +"render module produces the " +"directory of the configuration file as base directory." + +#, no-wrap +msgid "" +"[centos-artwork.png]\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,artwork}.svgz\"\n" +"formats = \"xpm pdf jpg tif\"\n" +"heights = \"16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512\"\n" +"fgcolors = \"000000 ffffff\"\n" +"bgcolors = \"ffffff-0\"\n" +"command = \"/usr/bin/convert +append\"" +msgstr "" +"[centos-artwork.png]\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,artwork}.svgz\"\n" +"formats = \"xpm pdf jpg tif\"\n" +"heights = \"16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512\"\n" +"fgcolors = \"000000 ffffff\"\n" +"bgcolors = \"ffffff-0\"\n" +"command = \"/usr/bin/convert +append\"" + +msgid "" +"When the render module reads " +"this configuration file, it takes the centos.svgz and artwork.svgz files as source to " +"produce the centos.png and artwork.png files considering the first value in the list of heights, " +"background, foreground colors specified in the configuration file. " +"Then, it combines the results horizontally to create the " +"centos-artwork.png file. Later, the " +"centos-artwork.png file is converted to produce " +"one image file for each image format specified in the configuration " +"file. At this point, all the process repeats again but for the next " +"height and color values in the list." +msgstr "" +"When the render module reads " +"this configuration file, it takes the centos.svgz and artwork.svgz files as source to " +"produce the centos.png and artwork.png files considering the first value in the list of heights, " +"background, foreground colors specified in the configuration file. " +"Then, it combines the results horizontally to create the " +"centos-artwork.png file. Later, the " +"centos-artwork.png file is converted to produce " +"one image file for each image format specified in the configuration " +"file. At this point, all the process repeats again but for the next " +"height and color values in the list." + +#, no-wrap +msgid "" +"[syslinux-splash.png]\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Syslinux/syslinux-splash.svgz\"\n" +"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Default/Images/ffffff/ffffff-0/48/centos.png:x48+20+232\"\n" +"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/Images/ffffff/ffffff-0/96/5.png:x96+300+184\"\n" +"\n" +"[syslinux-splash.lss]\n" +"render-from = \"syslinux-splash.png\"\n" +"render-type = \"palette\"\n" +"palette-gpl = \"colors.gpl\"" +msgstr "" +"[syslinux-splash.png]\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Syslinux/syslinux-splash.svgz\"\n" +"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Default/Images/ffffff/ffffff-0/48/centos.png:x48+20+232\"\n" +"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/Images/ffffff/ffffff-0/96/5.png:x96+300+184\"\n" +"\n" +"[syslinux-splash.lss]\n" +"render-from = \"syslinux-splash.png\"\n" +"render-type = \"palette\"\n" +"palette-gpl = \"colors.gpl\"" + +msgid "" +"When the render module reads " +"this configuration file," +msgstr "" +"When the render module reads " +"this configuration file," + +#, no-wrap +msgid "" +"[screenshot.png]\n" +"render-type = \"svg\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/screenshot.svgz\"\n" +"render-flow = \"base\"\n" +"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Symbols/Default/Images/ffffff/ffffff-0/16/centos.png:x16+5+5\"\n" +"\n" +"[800x600.tar.gz]\n" +"render-type = \"archive\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Motifs/${MOTIF}/Backgrounds/Images/800x600-final.png:background.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.desktop\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.xml\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-language.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-reboot.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-session.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-shutdown.png\"\n" +"render-from = \"screenshot.png\"\n" +"command = \"/bin/tar -czf\"\n" +"\n" +"[1360x768.tar.gz]\n" +"render-type = \"archive\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Motifs/${MOTIF}/Backgrounds/Images/1360x768-final.png:background.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.desktop\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.xml\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-language.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-reboot.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-session.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-shutdown.png\"\n" +"render-from = \"screenshot.png\"\n" +"command = \"/bin/tar --remove-files -czf\"" +msgstr "" +"[screenshot.png]\n" +"render-type = \"svg\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/screenshot.svgz\"\n" +"render-flow = \"base\"\n" +"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Symbols/Default/Images/ffffff/ffffff-0/16/centos.png:x16+5+5\"\n" +"\n" +"[800x600.tar.gz]\n" +"render-type = \"archive\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Motifs/${MOTIF}/Backgrounds/Images/800x600-final.png:background.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.desktop\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.xml\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-language.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-reboot.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-session.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-shutdown.png\"\n" +"render-from = \"screenshot.png\"\n" +"command = \"/bin/tar -czf\"\n" +"\n" +"[1360x768.tar.gz]\n" +"render-type = \"archive\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Motifs/${MOTIF}/Backgrounds/Images/1360x768-final.png:background.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.desktop\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.xml\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-language.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-reboot.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-session.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-shutdown.png\"\n" +"render-from = \"screenshot.png\"\n" +"command = \"/bin/tar --remove-files -czf\"" + +msgid "Bugs" +msgstr "Bugs" + +msgid "" +"The render module has some " +"issues I would like you to be aware of. Mainly, to see if you could " +"help me find better solutions for them ;)" +msgstr "" +"The render module has some " +"issues I would like you to be aware of. Mainly, to see if you could " +"help me find better solutions for them ;)" + +msgid "" +"The process implemented to reduce image colors through GIMP's " +"palettes involves too much user intervention compared with " +"ImageMagick's --colors option that reduces image colors instantly " +"without user intervention. Nevertheless, the procedure of reducing " +"color through GIMP's palettes provides more quality to final images " +"than ImageMagic's --colors option does. Also, using GIMP's palettes " +"let us create LSS images from PNG images using the same exact " +"information we used to reduce colors on PNG images. This is very " +"important in order to have the same result in both image types. " +"Because of these reasons I prefer GIMP's palettes procedure against " +"others methods like it is the case of ImageMagick's for producing " +"images with reduced number of colors." +msgstr "" +"The process implemented to reduce image colors through GIMP's " +"palettes involves too much user intervention compared with " +"ImageMagick's --colors option that reduces image colors instantly " +"without user intervention. Nevertheless, the procedure of reducing " +"color through GIMP's palettes provides more quality to final images " +"than ImageMagic's --colors option does. Also, using GIMP's palettes " +"let us create LSS images from PNG images using the same exact " +"information we used to reduce colors on PNG images. This is very " +"important in order to have the same result in both image types. " +"Because of these reasons I prefer GIMP's palettes procedure against " +"others methods like it is the case of ImageMagick's for producing " +"images with reduced number of colors." + +msgid "Rendering PDF Files From Localized Docbook Files" +msgstr "Rendering PDF Files From Localized Docbook Files" + +msgid "" +"Even it is possible to produce PDF files from Docbook files using " +"current applications inside CentOS-5, there are some production " +"issues when we use localized docbook files as source to produce " +"localized PDF files that made me not to implement them as part of " +"centos-art.sh script by now." +msgstr "" +"Even it is possible to produce PDF files from Docbook files using " +"current applications inside CentOS-5, there are some production " +"issues when we use localized docbook files as source to produce " +"localized PDF files that made me not to implement them as part of " +"centos-art.sh script by now." + +msgid "" +"When using the XML(DocBook)->XML(FO)->PDF transformation " +"chain, the result produced by docbook-style-xsl-1.69.1-" +"5.1 and passivetex-1.25-5.1.1 " +"doesn't render heading boxes very well on page's top and page's " +"bottom. The text put inside these boxes seem to have not enough " +"space in their respective areas." +msgstr "" +"When using the XML(DocBook)->XML(FO)->PDF transformation " +"chain, the result produced by docbook-style-xsl-1.69.1-" +"5.1 and passivetex-1.25-5.1.1 " +"doesn't render heading boxes very well on page's top and page's " +"bottom. The text put inside these boxes seem to have not enough " +"space in their respective areas." + +msgid "" +"Tried using dblatex-0.2.8-2.el5 but didn't " +"work for localized docbook files (i.e., those who has the " +"lang=\"lang\" string in their root element). If " +"you just remove the language specification string it just work. We " +"need the language specification in order for internal document " +"strings like Abstract and Table of " +"contents to be automatically translated. When the " +"language specific attribute is present in the root element, dblatex " +"outputs the following:" +msgstr "" +"Tried using dblatex-0.2.8-2.el5 but didn't " +"work for localized docbook files (i.e., those who has the " +"lang=\"lang\" string in their root element). If " +"you just remove the language specification string it just work. We " +"need the language specification in order for internal document " +"strings like Abstract and Table of " +"contents to be automatically translated. When the " +"language specific attribute is present in the root element, dblatex " +"outputs the following:" + +#, no-wrap +msgid "" +"Build the listings...\n" +"XSLT stylesheets DocBook - LaTeX 2e (0.2.8)\n" +"===================================================\n" +"Processing Revision History\n" +"Build 2912-corporate.docbook.pdf\n" +"This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)\n" +"entering extended mode\n" +"pdflatex failed\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:160: No counter 'chapter' defined.\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:160: leading text: \\newfloat{example}{htb}{loe}[chapter]\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:164: No counter 'chapter' defined.\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:164: leading text: \\newfloat{dbequation}{htb}{loe}[chapter]\n" +"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" +"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" +"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" +"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" +"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" +"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" +"Error: pdflatex compilation failed" +msgstr "" +"Build the listings...\n" +"XSLT stylesheets DocBook - LaTeX 2e (0.2.8)\n" +"===================================================\n" +"Processing Revision History\n" +"Build 2912-corporate.docbook.pdf\n" +"This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)\n" +"entering extended mode\n" +"pdflatex failed\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:160: No counter 'chapter' defined.\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:160: leading text: \\newfloat{example}{htb}{loe}[chapter]\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:164: No counter 'chapter' defined.\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:164: leading text: \\newfloat{dbequation}{htb}{loe}[chapter]\n" +"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" +"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" +"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" +"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" +"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" +"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" +"Error: pdflatex compilation failed" + +msgid "Reporting Bugs" +msgstr "Reporting Bugs" + +msgid "" +"Report bugs on the automation " +"category of centos-artwork " +"project at the The " +"CentOS Bugs website." +msgstr "" +"Report bugs on the automation " +"category of centos-artwork " +"project at the The " +"CentOS Bugs website." + +msgid "Author" +msgstr "Author" + +msgid "" +"Written by Alain Reguera " +"Delgado, 2009-2013" +msgstr "" +"Written by Alain Reguera " +"Delgado, 2009-2013" + +msgid "Copyright" +msgstr "Copyright" + +msgid "Copyright © 2009-2013 The CentOS Project" +msgstr "Copyright © 2009-2013 The CentOS Project" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." +msgstr "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Modules/Render/Manuals/Locales/es_ES/render.asciidoc.po b/Automation/Modules/Render/Manuals/Locales/es_ES/render.asciidoc.po new file mode 100644 index 0000000..f7693db --- /dev/null +++ b/Automation/Modules/Render/Manuals/Locales/es_ES/render.asciidoc.po @@ -0,0 +1,834 @@ +msgid "" +msgstr "" +"Project-Id-Version: centos-art.sh 0.5\n" +"POT-Creation-Date: 2013-08-06 01:36-0400\n" +"PO-Revision-Date: 2013-08-06 01:36-0400\n" +"Last-Translator: Localization SIG \n" +"Language-Team: Spanish\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "centos-art.sh-render" +msgstr "" + +msgid "1" +msgstr "" + +msgid "Standardize production tasks based on configuration files." +msgstr "Normaliza las tareas de producción basado en ficheros de configuración" + +msgid "centos-art.sh render [OPTIONS] [DIRECTORY …]" +msgstr "" + +msgid "Description" +msgstr "Descripción" + +msgid "" +"When you execute the render module, it " +"looks for configuration files inside the “DIRECTORY” specified in the " +"command-line and processes them in the order they were found. When no " +"“DIRECTORY” is specified to centos-art.sh script, the render module " +"looks for configuration files inside the current directory it was executed " +"from. If no configuration file is found, the render module will end its execution with an error message." +msgstr "" + +msgid "Options" +msgstr "" + +msgid "" +"The render module accepts the following " +"options:" +msgstr "" + +msgid "--help" +msgstr "" + +msgid "" +"This option shows the render module's " +"documentation (this page)." +msgstr "" + +msgid "--version" +msgstr "" + +msgid "" +"This option shows the render module's " +"name and version." +msgstr "" + +msgid "--filter=\"REGEX\"" +msgstr "" + +msgid "" +"This option reduces the number of section blocks inside configuration files " +"the render module will take for " +"processing. “REGEX” is a regular expression pattern matching one or more " +"section names inside the configuration files found under “DIRECTORY”." +msgstr "" + +msgid "Configuration Files" +msgstr "" + +msgid "" +"The configuration files are regular files with the .conf " +"extension. The name of configuration files is frequently chosen for helping " +"you to remember what the configuration files are for and, in some cases, for " +"producing section blocks in specific order." +msgstr "" + +msgid "" +"The format used in configuration files use section blocks in the form " +"[section-name]. Each section block ends when the next " +"section block begins or at the end of the file. Section blocks contain one " +"or more variable definitions in the form option = \"value\". In the specific case of render module, the section-name is an alphanumeric " +"value and points to the final file or directory you want to save the " +"processing results in. The configuration variables describe how to produce " +"the file or directory specified as section-name. Name " +"values in the section-name don't accept variables or any " +"kind of expansion in it, but configuration values do. Commentaries are " +"introduced by using the # character at the beginning of " +"lines. Commentaries defined this way are excluded from processing so you can " +"use them freely." +msgstr "" + +msgid "" +"The configuration files are processed from top to bottom. This is a very " +"important aspect to consider in situations where you need to grantee " +"specific priority for content production (e.g., you have several files in a " +"configuration file and need to produce some of them before others). So, " +"because configuration files are processed from top to bottom, section blocks " +"set first in the configuration file are processed first and section blocks " +"set later are processed later." +msgstr "" + +msgid "" +"The configuration files can be divided in separated configuration files to " +"produce specific section blocks with a given priority. For example, if you " +"have the file “render.conf”, you can divide its content in “render-1.conf”, " +"“render-2.conf” to produce section blocks inside “render-1.conf” first and " +"“render-2.conf” later. This sort of division might be very useful when the " +"configuration file begins to grow, or you want to control the order in which " +"specific groups of files are produced inside “DIRECTORY”." +msgstr "" + +msgid "" +"Inside configuration files, configuration variables can take different " +"meanings based on the section contexts. The context of a section block is " +"defined by the render-type variables." +msgstr "" + +msgid "render-type" +msgstr "" + +msgid "" +"Optional. This variable specifies the type of content rendition the " +"render module will perform. This " +"variable can take one of the following values: “archive”, “asciidoc”, " +"“compress”, “images”, “palette”, and “svg”. When this variable is not set, " +"the render module tries to determine " +"the type of rendition based on the file extension of the first file passed " +"through render-from variable. If no " +"valid value is found there either, the render module ends with an error message." +msgstr "" + +msgid "render-from" +msgstr "" + +msgid "" +"Required. This variable specifies the file name of the source file (design " +"model) used to produce the final file specified in the section line. This " +"option can receive absolute paths and relative paths. Absolute paths begin " +"with a slash (“/”) character while relative paths begin with the dot slash " +"(“./”) characters or no character at all. This variable can receive more " +"than one value by using either path expansion in one variable definition, or " +"several variables definitions." +msgstr "" + +msgid "Using Paths" +msgstr "" + +msgid "" +"When you provide absolute paths inside configuration files, there isn't " +"confusion about the location where the file is or should be. However, it " +"introduces rigidity to directory structures inside the working copy when it " +"is necessary to move directories from one place to another inside the " +"working copy. To eliminate this mobility restrictions, relative paths can be " +"used to create modular directory structures." +msgstr "" + +msgid "" +"When you use relative paths inside configuration files, paths are relative " +"to the location where the configuration file is stored in. This way it is " +"possible to move whole directory structures without touching the " +"configuration file and still have a render-able structures inside the " +"working copy. However, relative paths get limited in situations where the " +"production process needs files outside the directory where the configuration " +"file is stored in. In such cases, a combination of relative and absolute " +"paths is the solution to apply." +msgstr "" + +msgid "" +"When we need to use absolute paths to several files in the same directory (e." +"g., we are combining them all to produce a new image) but outside the " +"current directory the configuration file is stored in, it is possible to use " +"a list of absolute paths one beside another separated by space or we can use " +"path expansion which is shorter and easier to read. Path expansion is " +"interpreted when you enclose a list of file names in curly brackets using " +"comma as separator without spaces (e.g., /some/dir/{file1,file2," +"file3}). In order for path expansion to work correctly, all the " +"file names you put inside the curly brackets' list must exist in the " +"location specified first." +msgstr "" + +msgid "Using Environment Variables" +msgstr "" + +msgid "" +"The configuration files let you to use environment variables inside them. " +"This might result very useful when you need to provide absolute paths based " +"on variable information (e.g., the current locale information). Some of the " +"most important environment variables used by centos-art.sh script -and its configuration files- are " +"described below:" +msgstr "" + +msgid "TCAR_BASEDIR" +msgstr "" + +msgid "" +"This variable contains the absolute path to your repository's working copy. " +"The value of this variable is defined as read-only inside centos-art.sh script and cannot be modified later. As " +"a matter of convenience, users make use of their “~/.bash_profile” file to " +"define this variable there and, this way, skip the sometimes annoyance " +"absolute path questioning the centos-art.sh script does in order to know the absolute path of the working copy " +"it is going to work with." +msgstr "" + +msgid "" +"Whenever you set absolute paths inside configuration files to refer " +"locations inside your working copy, it is necessary that you use the " +"TCAR_BASEDIR environment variable in front of each path " +"definition you set. TCAR_SCRIPT_LANG_LL:: This variable " +"contains the language part of the current locale information. For instance, " +"if the current locale is “en_US.UTF-8”, the value of this variable would be " +"“en”. TCAR_SCRIPT_LANG_CC:: This variable contains the " +"country part of the current locale information. For instance, if the current " +"locale is “en_US.UTF-8”, the value of this variable would be “US”. " +"TCAR_SCRIPT_LANG_LC:: This variable contains the current " +"locale information in ll_CC format (e.g., es_ES). LANG:: " +"This variable contains the environment's current locale information." +msgstr "" + +msgid "Rendering Archives" +msgstr "" + +msgid "" +"When the render-type variable is set to " +"archive, the render " +"module takes the list of files set through render-" +"from variable and applies the value of command to them all in order to produce the final file " +"specified in the section line. When the command variable is not specified, " +"the /bin/tar --remove-files -czf command is used as " +"default." +msgstr "" + +msgid "Rendering Image Files" +msgstr "" + +msgid "" +"When the render-type variable is set to " +"svg, the section block is interpreted for rendering image " +"files. When rendering image files, the render-" +"from variable must point to a SVG files (either compressed or " +"uncompressed). The following following complementary variables are also " +"accepted:" +msgstr "" + +msgid "render-flow" +msgstr "" + +msgid "" +"Optional. This variable specifies the rendition flow to follow when " +"transforming SVG files into PNG images. This variable can take either " +"base or extended as value. The " +"base rendition flow takes one SVG file and produces just " +"one PNG image for it. The extended value applies the " +"base rendition flow and then transform the final PNG " +"image to different heights, formats, foreground colors and background " +"colors. By default, when this variable is not set, the base rendition flow is used." +msgstr "" + +msgid "export-id" +msgstr "" + +msgid "" +"Optional. This variable specifies the export id you want to use as reference " +"to produce PNG images from SVG files. The export-id is an attribute you " +"specified as unique value to an objects inside the SVG file in order to " +"export that object only but not the rest in the SVG file. If this variable " +"is not provided or it is empty, the drawing area of the SVG file is used as " +"reference to produce the final PNG image." +msgstr "" + +msgid "heights" +msgstr "" + +msgid "" +"Optional. This variable is available only for extended " +"rendition flow and specifies the different image heights you want to create " +"copies of the final PNG image. The values specified in this variable are " +"separated by white space and should be understandable by ImageMagick tool " +"set. When this variable is not provided, the render module will create copies of final PNG image for " +"several standard heights." +msgstr "" + +msgid "formats" +msgstr "" + +msgid "" +"Optional. This variable is available only for extended " +"rendition flow and specifies the different image formats you want to create " +"copies of the final PNG image. The values specified in this variable are " +"separated by white space and should be supported by ImageMagick tool set. " +"When this variable is not provided or set in the configuration file, the " +"render module will create copies of " +"final PNG image for several standard formats." +msgstr "" + +msgid "" +"To see the list of possible image formats supported by ImageMagick tool set, " +"run the following command: identify -list " +"format." +msgstr "" + +msgid "fgcolors" +msgstr "" + +msgid "" +"Optional. This variable is available only for extended " +"rendition flow and specifies the different foreground colors you want to " +"create copies of the final PNG image. To do this, the image you want to copy " +"should be rendered with black color (000000) so the color replacement can be " +"performed. The values specified in this variable are separated by white " +"space and should be understandable by ImageMagick tool set. When this " +"variable is not provided the black foreground (000000) is " +"used." +msgstr "" + +msgid "bgcolors" +msgstr "" + +msgid "" +"Optional. This variable is available only for extended " +"rendition flow and specifies the different background colors you want to " +"create copies of the final PNG image. This variable uses Inkscape's " +"--export-background and --export-background-" +"opacity options to control the background information of final " +"PNG images. Possible values to this variable take the form XXXXXX-" +"X, where the first six X represent a color in " +"hexadecimal format and the final X might be 1 or 0. 1 for " +"full opacity and 0 for full transparency. Intermediate values between 0 and " +"1 (e.g., 0.55) can be given to control the background opacity. When this " +"variable is not provided, white background full transparency " +"(ffffff-0) is used as default value." +msgstr "" + +msgid "command" +msgstr "" + +msgid "" +"Optional. This variable specifies the command used to modify the production " +"of final images. During the rendition process, images are produced inside a " +"temporal directory, and later moved to its final location using the command " +"specified as value in this variable. When this variable is not specified, it " +"can take one of two values based on the amount of files passed through " +"render-from variable. When just one " +"file is passed through the render-from " +"variable, the default value for this variable is /bin/cp, " +"but when there are reference to more than one file, the value of this option " +"is /usr/bin/convert +append which combines all images " +"into the final images." +msgstr "" + +msgid "comment" +msgstr "" + +msgid "" +"Optional. This variable contains a sentence describing the image you are " +"creating. This information is written in the comment " +"field of PNG images. When this variable is empty, no comment information " +"will be written to the final PNG image files." +msgstr "" + +msgid "brand" +msgstr "" + +msgid "" +"Optional. This variable describes the branding information applied to final " +"images. The value of this variable has the form FILENAME:GEOMETRY, where FILENAME is the absolute path to the PNG " +"image you want to apply as brand and, GEOMETRY takes the " +"form xHEIGHT+X+Y. In order to apply brand information to " +"final images correctly, the brand images files you want to apply must be " +"available. In case they don't exist the render module ends its execution with an error message." +msgstr "" + +msgid "Rendering Image Files From Other Image Files" +msgstr "" + +msgid "" +"To render image files from other image files, the render-type variable must be set to “images” and one or more " +"image files must be provided in the render-from variable. When the render " +"module finds a section block with this characteristics, it applies the value " +"of command variable to all files found " +"in render-from variable to produce the " +"final file specified in the section name." +msgstr "" + +msgid "" +"When the command variable is not " +"specified, the “/usr/bin/convert -append” command is used as default. This " +"command takes all the images passed through render-" +"from and appends them from top to bottom and saves the result in " +"the file you specified in the section name. When you render files this way, " +"the order in which you define source files through render-from may affect the final result based in the command you provided." +msgstr "" + +msgid "" +"The “images” rendition type provides an interface for external image " +"manipulation programs, like ImageMagick and NetPbm. You can use these " +"programs to manipulate images in great detail through the command-line." +msgstr "" + +msgid "Rendering Images With Reduced Number Of Colors" +msgstr "" + +msgid "" +"When the render-type variable is set to " +"palette, the section block where this variable was " +"defined is interpreted for producing images with a reduced number of colors. " +"In these cases, the render-from " +"variable must point to an image file. The following complementary variables " +"are also accepted:" +msgstr "" + +msgid "palette-gpl" +msgstr "" + +msgid "" +"Required. This variable addresses the palette of colors that will be use for " +"reducing colors. Generally, the palette of color file ends with the " +".gpl extension and is stored in the same directory of the " +"configuration file. This file can be produced by GIMP and provides an " +"optimized set of colors for the specific image you provided in the render-from variable." +msgstr "" + +msgid "" +"To find the optimized set of colors, you need to open the image specified in " +"render-from in GIMP, reduce its colors " +"to the desired number using GIMP's Indexed feature and, then, create a new " +"palette by importing it from the indexed image file. Once you have the " +"palette this way, you need to edit it using the Palettes dialog to add the " +"hexadecimal value of each color in the palette to the comment field, so you " +"have a palette file similar to the following:" +msgstr "" + +#, no-wrap +msgid "" +"GIMP Palette\n" +"Name: Syslinux-Default\n" +"Columns: 16\n" +"#\n" +" 32 76 141 204c8d\n" +" 37 82 146 255292\n" +" 52 94 153 345e99\n" +" 73 110 162 496ea2\n" +" 91 124 172 5b7cac\n" +"108 136 180 6c88b4\n" +"120 146 186 7892ba\n" +"131 158 193 839ec1\n" +"255 255 255 ffffff\n" +"146 170 200 92aac8\n" +"162 182 209 a2b6d1\n" +"183 199 219 b7c7db\n" +"204 216 230 ccd8e6\n" +"221 229 238 dde5ee\n" +"235 241 245 ebf1f5\n" +"246 251 254 f6fbfe" +msgstr "" + +msgid "" +"Now that the palette has been created, you can set a path to palette-gpl variable. Even you can set path of " +"palette-gpl from GIMP's palettes " +"directory (~/.gimp-x.x/palettes/), it is much more " +"preferable that you copy the palette file from that location to the " +"configuration file's DIRECTORY inside the repository and put it under " +"version control, so others can take benefit of it. The palette file is an " +"integral part of color specific image reduction so it must be near the " +"configuration file you use for such actions." +msgstr "" + +msgid "Rendering Documentation Files" +msgstr "" + +msgid "" +"To render documentation files, the render-type variable must be set to “asciidoc” and the render-from variable must point to an Asciidoc file. When the " +"render module finds this information in " +"a section block, it takes the asciidoc file as source and transforms it into " +"a docbook file using the asciidoc " +"program. The docbook file is created temporarily for further format " +"transformations and removed later, once the final format has been rendered." +msgstr "" + +msgid "" +"When the render module creates the " +"intermediate docbook file, it considers the current locale information of " +"your environment (e.g., by reading the LANG environment variable). In case " +"the current locale information is different to English (e.g., the value of " +"LANG environment variable doesn't begin with the “en” characters), the " +"docbook file will be localized based on the translation file specified in " +"the locale-from variable, before " +"applying further format transformations to it. This way, further format " +"transformations from the temporarily docbook file will end up being " +"localized as well. If the locale-from " +"variable is not present in the section block, the intermediate docbook file " +"won't be localized which make the final result to be not localized either." +msgstr "" + +msgid "" +"When you set the render-type variable " +"to “asciidoc”, the section blocks need to have the render-flow variable set to “article”, “book” or “manpage”. " +"This information defines the way the intermediate docbook file is produced " +"from the asciidoc file and, by extension, the possible final results, too." +msgstr "" + +msgid "" +"When render-flow variable is set to " +"“article” or “book”, it is possible to produce final files in “xhtml” format " +"but not in “manpage” format. This is because man pages require a specific " +"document structure that both articles and books don't need to have. When " +"producing articles and books in XHTML format, you can use the render-page variable to control whether to produce the " +"entire book or article in just one file (“single”) or in separate files " +"linked one another (“chunks”)." +msgstr "" + +msgid "" +"When render-flow variable is set to " +"“manpage” it is possible to set the formats variable to either “manpage” or “xhtml” in order to render the " +"docbook file as man page or XHTML format, respectively. you are producing " +"man pages to a language different to English, these required in order for " +"man command to find the man pages in " +"different locales. The value of the man's volume section can be set using " +"the mansect variable. If this variable " +"is not set, the value of man's volume section will be 1." +msgstr "" + +msgid "" +"When render-flow variable is not set, " +"the “article” value is used as default value." +msgstr "" + +msgid "" +"When the formats variable has the " +"“xhtml” value, you need to set the images-from and styles-from variables " +"inside the related section block, no matter what the value of render-flow would be. The value of images-from and styles-from variables must point to a directory, inside the working copy, " +"containing the share images and CSS files used by XHTML documents, " +"respectively. If none of these two variables are set the directories them." +msgstr "" + +msgid "" +"When the formats variable is not set, " +"the “xhtml” value is used as default value." +msgstr "" + +msgid "Rendering Localized Images" +msgstr "" + +msgid "" +"To produce localized content, you need to set the locale-from variable in the section block you want to provide " +"translations and point its value to the translation file where string " +"translations will take place. Then, you need to check the value of LANG " +"environment variable to be sure it has the locale information you want to " +"translate messages for." +msgstr "" + +msgid "" +"If the LANG environment variable has the value you expect, run the locale module on the “DIRECTORY” you want to " +"locale content. This read the source files you specified in render-from variable and would create the translation " +"files (a.k.a., portable objects) you need to edit to provide the string " +"translations from one language to another. Verify the translation file exist " +"and edit it to provide the strings translations. Once the strings have been " +"translated, execute the render module " +"on the “DIRECTORY”." +msgstr "" + +msgid "" +"When the render module finds the " +"locale-from variable in a section " +"block, it uses the xml2po program to " +"create a localized instance of each source file it finds in render-from variable. Then, using the source files' " +"localized instances, it produces the final files based on render-type variable's value." +msgstr "" + +msgid "Examples" +msgstr "" + +msgid "" +"Here are some practical configuration examples you can use as reference to " +"create your own configuration files." +msgstr "" + +#, no-wrap +msgid "" +"[Xhtml-single]\n" +"render-type = \"asciidoc\"\n" +"render-flow = \"article\"\n" +"render-from = \"corporate.asciidoc\"\n" +"locale-from = \"${TCAR_SCRIPT_LANG_LC}/messages.po\"\n" +"images-from = \"${TCAR_BASEDIR}/Artworks/Icons/Webenv\"\n" +"styles-from = \"${TCAR_BASEDIR}/Artworks/Webenv/Docbook/1.69.1/Css\"\n" +"formats = \"xhtml\"\n" +"render-page = \"single\"" +msgstr "" + +msgid "" +"When the render module reads this " +"configuration file, it initiates the asscidoc module " +"which in turn initiates the xhtml module for transforming " +"the corporate.asciidoc file into corporate." +"docbook file using article as document type and " +"result, the render module produces the " +"directory of the configuration file as base directory." +msgstr "" + +#, no-wrap +msgid "" +"[centos-artwork.png]\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,artwork}.svgz\"\n" +"formats = \"xpm pdf jpg tif\"\n" +"heights = \"16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512\"\n" +"fgcolors = \"000000 ffffff\"\n" +"bgcolors = \"ffffff-0\"\n" +"command = \"/usr/bin/convert +append\"" +msgstr "" + +msgid "" +"When the render module reads this " +"configuration file, it takes the centos.svgz and " +"artwork.svgz files as source to produce the " +"centos.png and artwork.png files " +"considering the first value in the list of heights, background, foreground " +"colors specified in the configuration file. Then, it combines the results " +"horizontally to create the centos-artwork.png file. " +"Later, the centos-artwork.png file is converted to " +"produce one image file for each image format specified in the configuration " +"file. At this point, all the process repeats again but for the next height " +"and color values in the list." +msgstr "" + +#, no-wrap +msgid "" +"[syslinux-splash.png]\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Syslinux/syslinux-splash.svgz\"\n" +"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Default/Images/ffffff/ffffff-0/48/centos.png:x48+20+232\"\n" +"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/Images/ffffff/ffffff-0/96/5.png:x96+300+184\"\n" +"\n" +"[syslinux-splash.lss]\n" +"render-from = \"syslinux-splash.png\"\n" +"render-type = \"palette\"\n" +"palette-gpl = \"colors.gpl\"" +msgstr "" + +msgid "" +"When the render module reads this " +"configuration file," +msgstr "" + +#, no-wrap +msgid "" +"[screenshot.png]\n" +"render-type = \"svg\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/screenshot.svgz\"\n" +"render-flow = \"base\"\n" +"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Symbols/Default/Images/ffffff/ffffff-0/16/centos.png:x16+5+5\"\n" +"\n" +"[800x600.tar.gz]\n" +"render-type = \"archive\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Motifs/${MOTIF}/Backgrounds/Images/800x600-final.png:background.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.desktop\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.xml\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-language.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-reboot.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-session.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-shutdown.png\"\n" +"render-from = \"screenshot.png\"\n" +"command = \"/bin/tar -czf\"\n" +"\n" +"[1360x768.tar.gz]\n" +"render-type = \"archive\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Motifs/${MOTIF}/Backgrounds/Images/1360x768-final.png:background.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.desktop\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.xml\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-language.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-reboot.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-session.png\"\n" +"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-shutdown.png\"\n" +"render-from = \"screenshot.png\"\n" +"command = \"/bin/tar --remove-files -czf\"" +msgstr "" + +msgid "Bugs" +msgstr "" + +msgid "" +"The render module has some issues I " +"would like you to be aware of. Mainly, to see if you could help me find " +"better solutions for them ;)" +msgstr "" + +msgid "" +"The process implemented to reduce image colors through GIMP's palettes " +"involves too much user intervention compared with ImageMagick's --colors " +"option that reduces image colors instantly without user intervention. " +"Nevertheless, the procedure of reducing color through GIMP's palettes " +"provides more quality to final images than ImageMagic's --colors option " +"does. Also, using GIMP's palettes let us create LSS images from PNG images " +"using the same exact information we used to reduce colors on PNG images. " +"This is very important in order to have the same result in both image types. " +"Because of these reasons I prefer GIMP's palettes procedure against others " +"methods like it is the case of ImageMagick's for producing images with " +"reduced number of colors." +msgstr "" + +msgid "Rendering PDF Files From Localized Docbook Files" +msgstr "" + +msgid "" +"Even it is possible to produce PDF files from Docbook files using current " +"applications inside CentOS-5, there are some production issues when we use " +"localized docbook files as source to produce localized PDF files that made " +"me not to implement them as part of centos-art.sh script by now." +msgstr "" + +msgid "" +"When using the XML(DocBook)->XML(FO)->PDF transformation chain, the " +"result produced by docbook-style-xsl-1.69.1-5.1 and " +"passivetex-1.25-5.1.1 doesn't render heading boxes very " +"well on page's top and page's bottom. The text put inside these boxes seem " +"to have not enough space in their respective areas." +msgstr "" + +msgid "" +"Tried using dblatex-0.2.8-2.el5 but didn't work for " +"localized docbook files (i.e., those who has the lang=\"lang\" string in their root element). If you just remove the language " +"specification string it just work. We need the language specification in " +"order for internal document strings like Abstract and " +"Table of contents to be automatically translated. When " +"the language specific attribute is present in the root element, dblatex " +"outputs the following:" +msgstr "" + +#, no-wrap +msgid "" +"Build the listings...\n" +"XSLT stylesheets DocBook - LaTeX 2e (0.2.8)\n" +"===================================================\n" +"Processing Revision History\n" +"Build 2912-corporate.docbook.pdf\n" +"This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)\n" +"entering extended mode\n" +"pdflatex failed\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:160: No counter 'chapter' defined.\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:160: leading text: \\newfloat{example}{htb}{loe}[chapter]\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:164: No counter 'chapter' defined.\n" +"/usr/share/texmf/tex/latex/dblatex/docbook.sty:164: leading text: \\newfloat{dbequation}{htb}{loe}[chapter]\n" +"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" +"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" +"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" +"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" +"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" +"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" +"Error: pdflatex compilation failed" +msgstr "" + +msgid "Reporting Bugs" +msgstr "" + +msgid "" +"Report bugs on the automation category " +"of centos-artwork project at the The CentOS Bugs website." +msgstr "" + +msgid "Author" +msgstr "" + +msgid "" +"Written by Alain Reguera Delgado, 2009-2013" +msgstr "" + +msgid "Copyright" +msgstr "" + +msgid "Copyright © 2009-2013 The CentOS Project" +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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., 675 Mass " +"Ave, Cambridge, MA 02139, USA." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "" diff --git a/Automation/Modules/Render/Manuals/es_ES/render.asciidoc.po b/Automation/Modules/Render/Manuals/es_ES/render.asciidoc.po deleted file mode 100644 index f7693db..0000000 --- a/Automation/Modules/Render/Manuals/es_ES/render.asciidoc.po +++ /dev/null @@ -1,834 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: centos-art.sh 0.5\n" -"POT-Creation-Date: 2013-08-06 01:36-0400\n" -"PO-Revision-Date: 2013-08-06 01:36-0400\n" -"Last-Translator: Localization SIG \n" -"Language-Team: Spanish\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "centos-art.sh-render" -msgstr "" - -msgid "1" -msgstr "" - -msgid "Standardize production tasks based on configuration files." -msgstr "Normaliza las tareas de producción basado en ficheros de configuración" - -msgid "centos-art.sh render [OPTIONS] [DIRECTORY …]" -msgstr "" - -msgid "Description" -msgstr "Descripción" - -msgid "" -"When you execute the render module, it " -"looks for configuration files inside the “DIRECTORY” specified in the " -"command-line and processes them in the order they were found. When no " -"“DIRECTORY” is specified to centos-art.sh script, the render module " -"looks for configuration files inside the current directory it was executed " -"from. If no configuration file is found, the render module will end its execution with an error message." -msgstr "" - -msgid "Options" -msgstr "" - -msgid "" -"The render module accepts the following " -"options:" -msgstr "" - -msgid "--help" -msgstr "" - -msgid "" -"This option shows the render module's " -"documentation (this page)." -msgstr "" - -msgid "--version" -msgstr "" - -msgid "" -"This option shows the render module's " -"name and version." -msgstr "" - -msgid "--filter=\"REGEX\"" -msgstr "" - -msgid "" -"This option reduces the number of section blocks inside configuration files " -"the render module will take for " -"processing. “REGEX” is a regular expression pattern matching one or more " -"section names inside the configuration files found under “DIRECTORY”." -msgstr "" - -msgid "Configuration Files" -msgstr "" - -msgid "" -"The configuration files are regular files with the .conf " -"extension. The name of configuration files is frequently chosen for helping " -"you to remember what the configuration files are for and, in some cases, for " -"producing section blocks in specific order." -msgstr "" - -msgid "" -"The format used in configuration files use section blocks in the form " -"[section-name]. Each section block ends when the next " -"section block begins or at the end of the file. Section blocks contain one " -"or more variable definitions in the form option = \"value\". In the specific case of render module, the section-name is an alphanumeric " -"value and points to the final file or directory you want to save the " -"processing results in. The configuration variables describe how to produce " -"the file or directory specified as section-name. Name " -"values in the section-name don't accept variables or any " -"kind of expansion in it, but configuration values do. Commentaries are " -"introduced by using the # character at the beginning of " -"lines. Commentaries defined this way are excluded from processing so you can " -"use them freely." -msgstr "" - -msgid "" -"The configuration files are processed from top to bottom. This is a very " -"important aspect to consider in situations where you need to grantee " -"specific priority for content production (e.g., you have several files in a " -"configuration file and need to produce some of them before others). So, " -"because configuration files are processed from top to bottom, section blocks " -"set first in the configuration file are processed first and section blocks " -"set later are processed later." -msgstr "" - -msgid "" -"The configuration files can be divided in separated configuration files to " -"produce specific section blocks with a given priority. For example, if you " -"have the file “render.conf”, you can divide its content in “render-1.conf”, " -"“render-2.conf” to produce section blocks inside “render-1.conf” first and " -"“render-2.conf” later. This sort of division might be very useful when the " -"configuration file begins to grow, or you want to control the order in which " -"specific groups of files are produced inside “DIRECTORY”." -msgstr "" - -msgid "" -"Inside configuration files, configuration variables can take different " -"meanings based on the section contexts. The context of a section block is " -"defined by the render-type variables." -msgstr "" - -msgid "render-type" -msgstr "" - -msgid "" -"Optional. This variable specifies the type of content rendition the " -"render module will perform. This " -"variable can take one of the following values: “archive”, “asciidoc”, " -"“compress”, “images”, “palette”, and “svg”. When this variable is not set, " -"the render module tries to determine " -"the type of rendition based on the file extension of the first file passed " -"through render-from variable. If no " -"valid value is found there either, the render module ends with an error message." -msgstr "" - -msgid "render-from" -msgstr "" - -msgid "" -"Required. This variable specifies the file name of the source file (design " -"model) used to produce the final file specified in the section line. This " -"option can receive absolute paths and relative paths. Absolute paths begin " -"with a slash (“/”) character while relative paths begin with the dot slash " -"(“./”) characters or no character at all. This variable can receive more " -"than one value by using either path expansion in one variable definition, or " -"several variables definitions." -msgstr "" - -msgid "Using Paths" -msgstr "" - -msgid "" -"When you provide absolute paths inside configuration files, there isn't " -"confusion about the location where the file is or should be. However, it " -"introduces rigidity to directory structures inside the working copy when it " -"is necessary to move directories from one place to another inside the " -"working copy. To eliminate this mobility restrictions, relative paths can be " -"used to create modular directory structures." -msgstr "" - -msgid "" -"When you use relative paths inside configuration files, paths are relative " -"to the location where the configuration file is stored in. This way it is " -"possible to move whole directory structures without touching the " -"configuration file and still have a render-able structures inside the " -"working copy. However, relative paths get limited in situations where the " -"production process needs files outside the directory where the configuration " -"file is stored in. In such cases, a combination of relative and absolute " -"paths is the solution to apply." -msgstr "" - -msgid "" -"When we need to use absolute paths to several files in the same directory (e." -"g., we are combining them all to produce a new image) but outside the " -"current directory the configuration file is stored in, it is possible to use " -"a list of absolute paths one beside another separated by space or we can use " -"path expansion which is shorter and easier to read. Path expansion is " -"interpreted when you enclose a list of file names in curly brackets using " -"comma as separator without spaces (e.g., /some/dir/{file1,file2," -"file3}). In order for path expansion to work correctly, all the " -"file names you put inside the curly brackets' list must exist in the " -"location specified first." -msgstr "" - -msgid "Using Environment Variables" -msgstr "" - -msgid "" -"The configuration files let you to use environment variables inside them. " -"This might result very useful when you need to provide absolute paths based " -"on variable information (e.g., the current locale information). Some of the " -"most important environment variables used by centos-art.sh script -and its configuration files- are " -"described below:" -msgstr "" - -msgid "TCAR_BASEDIR" -msgstr "" - -msgid "" -"This variable contains the absolute path to your repository's working copy. " -"The value of this variable is defined as read-only inside centos-art.sh script and cannot be modified later. As " -"a matter of convenience, users make use of their “~/.bash_profile” file to " -"define this variable there and, this way, skip the sometimes annoyance " -"absolute path questioning the centos-art.sh script does in order to know the absolute path of the working copy " -"it is going to work with." -msgstr "" - -msgid "" -"Whenever you set absolute paths inside configuration files to refer " -"locations inside your working copy, it is necessary that you use the " -"TCAR_BASEDIR environment variable in front of each path " -"definition you set. TCAR_SCRIPT_LANG_LL:: This variable " -"contains the language part of the current locale information. For instance, " -"if the current locale is “en_US.UTF-8”, the value of this variable would be " -"“en”. TCAR_SCRIPT_LANG_CC:: This variable contains the " -"country part of the current locale information. For instance, if the current " -"locale is “en_US.UTF-8”, the value of this variable would be “US”. " -"TCAR_SCRIPT_LANG_LC:: This variable contains the current " -"locale information in ll_CC format (e.g., es_ES). LANG:: " -"This variable contains the environment's current locale information." -msgstr "" - -msgid "Rendering Archives" -msgstr "" - -msgid "" -"When the render-type variable is set to " -"archive, the render " -"module takes the list of files set through render-" -"from variable and applies the value of command to them all in order to produce the final file " -"specified in the section line. When the command variable is not specified, " -"the /bin/tar --remove-files -czf command is used as " -"default." -msgstr "" - -msgid "Rendering Image Files" -msgstr "" - -msgid "" -"When the render-type variable is set to " -"svg, the section block is interpreted for rendering image " -"files. When rendering image files, the render-" -"from variable must point to a SVG files (either compressed or " -"uncompressed). The following following complementary variables are also " -"accepted:" -msgstr "" - -msgid "render-flow" -msgstr "" - -msgid "" -"Optional. This variable specifies the rendition flow to follow when " -"transforming SVG files into PNG images. This variable can take either " -"base or extended as value. The " -"base rendition flow takes one SVG file and produces just " -"one PNG image for it. The extended value applies the " -"base rendition flow and then transform the final PNG " -"image to different heights, formats, foreground colors and background " -"colors. By default, when this variable is not set, the base rendition flow is used." -msgstr "" - -msgid "export-id" -msgstr "" - -msgid "" -"Optional. This variable specifies the export id you want to use as reference " -"to produce PNG images from SVG files. The export-id is an attribute you " -"specified as unique value to an objects inside the SVG file in order to " -"export that object only but not the rest in the SVG file. If this variable " -"is not provided or it is empty, the drawing area of the SVG file is used as " -"reference to produce the final PNG image." -msgstr "" - -msgid "heights" -msgstr "" - -msgid "" -"Optional. This variable is available only for extended " -"rendition flow and specifies the different image heights you want to create " -"copies of the final PNG image. The values specified in this variable are " -"separated by white space and should be understandable by ImageMagick tool " -"set. When this variable is not provided, the render module will create copies of final PNG image for " -"several standard heights." -msgstr "" - -msgid "formats" -msgstr "" - -msgid "" -"Optional. This variable is available only for extended " -"rendition flow and specifies the different image formats you want to create " -"copies of the final PNG image. The values specified in this variable are " -"separated by white space and should be supported by ImageMagick tool set. " -"When this variable is not provided or set in the configuration file, the " -"render module will create copies of " -"final PNG image for several standard formats." -msgstr "" - -msgid "" -"To see the list of possible image formats supported by ImageMagick tool set, " -"run the following command: identify -list " -"format." -msgstr "" - -msgid "fgcolors" -msgstr "" - -msgid "" -"Optional. This variable is available only for extended " -"rendition flow and specifies the different foreground colors you want to " -"create copies of the final PNG image. To do this, the image you want to copy " -"should be rendered with black color (000000) so the color replacement can be " -"performed. The values specified in this variable are separated by white " -"space and should be understandable by ImageMagick tool set. When this " -"variable is not provided the black foreground (000000) is " -"used." -msgstr "" - -msgid "bgcolors" -msgstr "" - -msgid "" -"Optional. This variable is available only for extended " -"rendition flow and specifies the different background colors you want to " -"create copies of the final PNG image. This variable uses Inkscape's " -"--export-background and --export-background-" -"opacity options to control the background information of final " -"PNG images. Possible values to this variable take the form XXXXXX-" -"X, where the first six X represent a color in " -"hexadecimal format and the final X might be 1 or 0. 1 for " -"full opacity and 0 for full transparency. Intermediate values between 0 and " -"1 (e.g., 0.55) can be given to control the background opacity. When this " -"variable is not provided, white background full transparency " -"(ffffff-0) is used as default value." -msgstr "" - -msgid "command" -msgstr "" - -msgid "" -"Optional. This variable specifies the command used to modify the production " -"of final images. During the rendition process, images are produced inside a " -"temporal directory, and later moved to its final location using the command " -"specified as value in this variable. When this variable is not specified, it " -"can take one of two values based on the amount of files passed through " -"render-from variable. When just one " -"file is passed through the render-from " -"variable, the default value for this variable is /bin/cp, " -"but when there are reference to more than one file, the value of this option " -"is /usr/bin/convert +append which combines all images " -"into the final images." -msgstr "" - -msgid "comment" -msgstr "" - -msgid "" -"Optional. This variable contains a sentence describing the image you are " -"creating. This information is written in the comment " -"field of PNG images. When this variable is empty, no comment information " -"will be written to the final PNG image files." -msgstr "" - -msgid "brand" -msgstr "" - -msgid "" -"Optional. This variable describes the branding information applied to final " -"images. The value of this variable has the form FILENAME:GEOMETRY, where FILENAME is the absolute path to the PNG " -"image you want to apply as brand and, GEOMETRY takes the " -"form xHEIGHT+X+Y. In order to apply brand information to " -"final images correctly, the brand images files you want to apply must be " -"available. In case they don't exist the render module ends its execution with an error message." -msgstr "" - -msgid "Rendering Image Files From Other Image Files" -msgstr "" - -msgid "" -"To render image files from other image files, the render-type variable must be set to “images” and one or more " -"image files must be provided in the render-from variable. When the render " -"module finds a section block with this characteristics, it applies the value " -"of command variable to all files found " -"in render-from variable to produce the " -"final file specified in the section name." -msgstr "" - -msgid "" -"When the command variable is not " -"specified, the “/usr/bin/convert -append” command is used as default. This " -"command takes all the images passed through render-" -"from and appends them from top to bottom and saves the result in " -"the file you specified in the section name. When you render files this way, " -"the order in which you define source files through render-from may affect the final result based in the command you provided." -msgstr "" - -msgid "" -"The “images” rendition type provides an interface for external image " -"manipulation programs, like ImageMagick and NetPbm. You can use these " -"programs to manipulate images in great detail through the command-line." -msgstr "" - -msgid "Rendering Images With Reduced Number Of Colors" -msgstr "" - -msgid "" -"When the render-type variable is set to " -"palette, the section block where this variable was " -"defined is interpreted for producing images with a reduced number of colors. " -"In these cases, the render-from " -"variable must point to an image file. The following complementary variables " -"are also accepted:" -msgstr "" - -msgid "palette-gpl" -msgstr "" - -msgid "" -"Required. This variable addresses the palette of colors that will be use for " -"reducing colors. Generally, the palette of color file ends with the " -".gpl extension and is stored in the same directory of the " -"configuration file. This file can be produced by GIMP and provides an " -"optimized set of colors for the specific image you provided in the render-from variable." -msgstr "" - -msgid "" -"To find the optimized set of colors, you need to open the image specified in " -"render-from in GIMP, reduce its colors " -"to the desired number using GIMP's Indexed feature and, then, create a new " -"palette by importing it from the indexed image file. Once you have the " -"palette this way, you need to edit it using the Palettes dialog to add the " -"hexadecimal value of each color in the palette to the comment field, so you " -"have a palette file similar to the following:" -msgstr "" - -#, no-wrap -msgid "" -"GIMP Palette\n" -"Name: Syslinux-Default\n" -"Columns: 16\n" -"#\n" -" 32 76 141 204c8d\n" -" 37 82 146 255292\n" -" 52 94 153 345e99\n" -" 73 110 162 496ea2\n" -" 91 124 172 5b7cac\n" -"108 136 180 6c88b4\n" -"120 146 186 7892ba\n" -"131 158 193 839ec1\n" -"255 255 255 ffffff\n" -"146 170 200 92aac8\n" -"162 182 209 a2b6d1\n" -"183 199 219 b7c7db\n" -"204 216 230 ccd8e6\n" -"221 229 238 dde5ee\n" -"235 241 245 ebf1f5\n" -"246 251 254 f6fbfe" -msgstr "" - -msgid "" -"Now that the palette has been created, you can set a path to palette-gpl variable. Even you can set path of " -"palette-gpl from GIMP's palettes " -"directory (~/.gimp-x.x/palettes/), it is much more " -"preferable that you copy the palette file from that location to the " -"configuration file's DIRECTORY inside the repository and put it under " -"version control, so others can take benefit of it. The palette file is an " -"integral part of color specific image reduction so it must be near the " -"configuration file you use for such actions." -msgstr "" - -msgid "Rendering Documentation Files" -msgstr "" - -msgid "" -"To render documentation files, the render-type variable must be set to “asciidoc” and the render-from variable must point to an Asciidoc file. When the " -"render module finds this information in " -"a section block, it takes the asciidoc file as source and transforms it into " -"a docbook file using the asciidoc " -"program. The docbook file is created temporarily for further format " -"transformations and removed later, once the final format has been rendered." -msgstr "" - -msgid "" -"When the render module creates the " -"intermediate docbook file, it considers the current locale information of " -"your environment (e.g., by reading the LANG environment variable). In case " -"the current locale information is different to English (e.g., the value of " -"LANG environment variable doesn't begin with the “en” characters), the " -"docbook file will be localized based on the translation file specified in " -"the locale-from variable, before " -"applying further format transformations to it. This way, further format " -"transformations from the temporarily docbook file will end up being " -"localized as well. If the locale-from " -"variable is not present in the section block, the intermediate docbook file " -"won't be localized which make the final result to be not localized either." -msgstr "" - -msgid "" -"When you set the render-type variable " -"to “asciidoc”, the section blocks need to have the render-flow variable set to “article”, “book” or “manpage”. " -"This information defines the way the intermediate docbook file is produced " -"from the asciidoc file and, by extension, the possible final results, too." -msgstr "" - -msgid "" -"When render-flow variable is set to " -"“article” or “book”, it is possible to produce final files in “xhtml” format " -"but not in “manpage” format. This is because man pages require a specific " -"document structure that both articles and books don't need to have. When " -"producing articles and books in XHTML format, you can use the render-page variable to control whether to produce the " -"entire book or article in just one file (“single”) or in separate files " -"linked one another (“chunks”)." -msgstr "" - -msgid "" -"When render-flow variable is set to " -"“manpage” it is possible to set the formats variable to either “manpage” or “xhtml” in order to render the " -"docbook file as man page or XHTML format, respectively. you are producing " -"man pages to a language different to English, these required in order for " -"man command to find the man pages in " -"different locales. The value of the man's volume section can be set using " -"the mansect variable. If this variable " -"is not set, the value of man's volume section will be 1." -msgstr "" - -msgid "" -"When render-flow variable is not set, " -"the “article” value is used as default value." -msgstr "" - -msgid "" -"When the formats variable has the " -"“xhtml” value, you need to set the images-from and styles-from variables " -"inside the related section block, no matter what the value of render-flow would be. The value of images-from and styles-from variables must point to a directory, inside the working copy, " -"containing the share images and CSS files used by XHTML documents, " -"respectively. If none of these two variables are set the directories them." -msgstr "" - -msgid "" -"When the formats variable is not set, " -"the “xhtml” value is used as default value." -msgstr "" - -msgid "Rendering Localized Images" -msgstr "" - -msgid "" -"To produce localized content, you need to set the locale-from variable in the section block you want to provide " -"translations and point its value to the translation file where string " -"translations will take place. Then, you need to check the value of LANG " -"environment variable to be sure it has the locale information you want to " -"translate messages for." -msgstr "" - -msgid "" -"If the LANG environment variable has the value you expect, run the locale module on the “DIRECTORY” you want to " -"locale content. This read the source files you specified in render-from variable and would create the translation " -"files (a.k.a., portable objects) you need to edit to provide the string " -"translations from one language to another. Verify the translation file exist " -"and edit it to provide the strings translations. Once the strings have been " -"translated, execute the render module " -"on the “DIRECTORY”." -msgstr "" - -msgid "" -"When the render module finds the " -"locale-from variable in a section " -"block, it uses the xml2po program to " -"create a localized instance of each source file it finds in render-from variable. Then, using the source files' " -"localized instances, it produces the final files based on render-type variable's value." -msgstr "" - -msgid "Examples" -msgstr "" - -msgid "" -"Here are some practical configuration examples you can use as reference to " -"create your own configuration files." -msgstr "" - -#, no-wrap -msgid "" -"[Xhtml-single]\n" -"render-type = \"asciidoc\"\n" -"render-flow = \"article\"\n" -"render-from = \"corporate.asciidoc\"\n" -"locale-from = \"${TCAR_SCRIPT_LANG_LC}/messages.po\"\n" -"images-from = \"${TCAR_BASEDIR}/Artworks/Icons/Webenv\"\n" -"styles-from = \"${TCAR_BASEDIR}/Artworks/Webenv/Docbook/1.69.1/Css\"\n" -"formats = \"xhtml\"\n" -"render-page = \"single\"" -msgstr "" - -msgid "" -"When the render module reads this " -"configuration file, it initiates the asscidoc module " -"which in turn initiates the xhtml module for transforming " -"the corporate.asciidoc file into corporate." -"docbook file using article as document type and " -"result, the render module produces the " -"directory of the configuration file as base directory." -msgstr "" - -#, no-wrap -msgid "" -"[centos-artwork.png]\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,artwork}.svgz\"\n" -"formats = \"xpm pdf jpg tif\"\n" -"heights = \"16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512\"\n" -"fgcolors = \"000000 ffffff\"\n" -"bgcolors = \"ffffff-0\"\n" -"command = \"/usr/bin/convert +append\"" -msgstr "" - -msgid "" -"When the render module reads this " -"configuration file, it takes the centos.svgz and " -"artwork.svgz files as source to produce the " -"centos.png and artwork.png files " -"considering the first value in the list of heights, background, foreground " -"colors specified in the configuration file. Then, it combines the results " -"horizontally to create the centos-artwork.png file. " -"Later, the centos-artwork.png file is converted to " -"produce one image file for each image format specified in the configuration " -"file. At this point, all the process repeats again but for the next height " -"and color values in the list." -msgstr "" - -#, no-wrap -msgid "" -"[syslinux-splash.png]\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Syslinux/syslinux-splash.svgz\"\n" -"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Default/Images/ffffff/ffffff-0/48/centos.png:x48+20+232\"\n" -"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/Images/ffffff/ffffff-0/96/5.png:x96+300+184\"\n" -"\n" -"[syslinux-splash.lss]\n" -"render-from = \"syslinux-splash.png\"\n" -"render-type = \"palette\"\n" -"palette-gpl = \"colors.gpl\"" -msgstr "" - -msgid "" -"When the render module reads this " -"configuration file," -msgstr "" - -#, no-wrap -msgid "" -"[screenshot.png]\n" -"render-type = \"svg\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/screenshot.svgz\"\n" -"render-flow = \"base\"\n" -"brand = \"${TCAR_BASEDIR}/Artworks/Brands/Symbols/Default/Images/ffffff/ffffff-0/16/centos.png:x16+5+5\"\n" -"\n" -"[800x600.tar.gz]\n" -"render-type = \"archive\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Motifs/${MOTIF}/Backgrounds/Images/800x600-final.png:background.png\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.desktop\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.xml\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-language.png\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-reboot.png\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-session.png\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-shutdown.png\"\n" -"render-from = \"screenshot.png\"\n" -"command = \"/bin/tar -czf\"\n" -"\n" -"[1360x768.tar.gz]\n" -"render-type = \"archive\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Motifs/${MOTIF}/Backgrounds/Images/1360x768-final.png:background.png\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.desktop\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/GdmGreeterTheme.xml\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-language.png\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-reboot.png\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-session.png\"\n" -"render-from = \"${TCAR_BASEDIR}/Artworks/Themes/Models/Distro/5/Gdm/icon-shutdown.png\"\n" -"render-from = \"screenshot.png\"\n" -"command = \"/bin/tar --remove-files -czf\"" -msgstr "" - -msgid "Bugs" -msgstr "" - -msgid "" -"The render module has some issues I " -"would like you to be aware of. Mainly, to see if you could help me find " -"better solutions for them ;)" -msgstr "" - -msgid "" -"The process implemented to reduce image colors through GIMP's palettes " -"involves too much user intervention compared with ImageMagick's --colors " -"option that reduces image colors instantly without user intervention. " -"Nevertheless, the procedure of reducing color through GIMP's palettes " -"provides more quality to final images than ImageMagic's --colors option " -"does. Also, using GIMP's palettes let us create LSS images from PNG images " -"using the same exact information we used to reduce colors on PNG images. " -"This is very important in order to have the same result in both image types. " -"Because of these reasons I prefer GIMP's palettes procedure against others " -"methods like it is the case of ImageMagick's for producing images with " -"reduced number of colors." -msgstr "" - -msgid "Rendering PDF Files From Localized Docbook Files" -msgstr "" - -msgid "" -"Even it is possible to produce PDF files from Docbook files using current " -"applications inside CentOS-5, there are some production issues when we use " -"localized docbook files as source to produce localized PDF files that made " -"me not to implement them as part of centos-art.sh script by now." -msgstr "" - -msgid "" -"When using the XML(DocBook)->XML(FO)->PDF transformation chain, the " -"result produced by docbook-style-xsl-1.69.1-5.1 and " -"passivetex-1.25-5.1.1 doesn't render heading boxes very " -"well on page's top and page's bottom. The text put inside these boxes seem " -"to have not enough space in their respective areas." -msgstr "" - -msgid "" -"Tried using dblatex-0.2.8-2.el5 but didn't work for " -"localized docbook files (i.e., those who has the lang=\"lang\" string in their root element). If you just remove the language " -"specification string it just work. We need the language specification in " -"order for internal document strings like Abstract and " -"Table of contents to be automatically translated. When " -"the language specific attribute is present in the root element, dblatex " -"outputs the following:" -msgstr "" - -#, no-wrap -msgid "" -"Build the listings...\n" -"XSLT stylesheets DocBook - LaTeX 2e (0.2.8)\n" -"===================================================\n" -"Processing Revision History\n" -"Build 2912-corporate.docbook.pdf\n" -"This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)\n" -"entering extended mode\n" -"pdflatex failed\n" -"/usr/share/texmf/tex/latex/dblatex/docbook.sty:160: No counter 'chapter' defined.\n" -"/usr/share/texmf/tex/latex/dblatex/docbook.sty:160: leading text: \\newfloat{example}{htb}{loe}[chapter]\n" -"/usr/share/texmf/tex/latex/dblatex/docbook.sty:164: No counter 'chapter' defined.\n" -"/usr/share/texmf/tex/latex/dblatex/docbook.sty:164: leading text: \\newfloat{dbequation}{htb}{loe}[chapter]\n" -"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" -"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" -"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" -"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" -"2912-corporate.docbook_tmp.tex:62: Illegal parameter number in definition of \\@the@H@page.\n" -"2912-corporate.docbook_tmp.tex:62: leading text: \\maketitle\n" -"Error: pdflatex compilation failed" -msgstr "" - -msgid "Reporting Bugs" -msgstr "" - -msgid "" -"Report bugs on the automation category " -"of centos-artwork project at the The CentOS Bugs website." -msgstr "" - -msgid "Author" -msgstr "" - -msgid "" -"Written by Alain Reguera Delgado, 2009-2013" -msgstr "" - -msgid "Copyright" -msgstr "" - -msgid "Copyright © 2009-2013 The CentOS Project" -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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., 675 Mass " -"Ave, Cambridge, MA 02139, USA." -msgstr "" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "" diff --git a/Automation/Modules/Render/Manuals/render.conf b/Automation/Modules/Render/Manuals/render.conf index 053718c..3e6916b 100644 --- a/Automation/Modules/Render/Manuals/render.conf +++ b/Automation/Modules/Render/Manuals/render.conf @@ -2,6 +2,6 @@ render-type = "asciidoc" render-flow = "manpage" render-from = "render.asciidoc" -locale-from = "${TCAR_SCRIPT_LANG_LC}/render.asciidoc.po" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/render.asciidoc.po" formats = "xhtml manpage" mansect = "1" diff --git a/Automation/Modules/Tuneup/Manuals/Locales/en_US/tuneup.asciidoc.po b/Automation/Modules/Tuneup/Manuals/Locales/en_US/tuneup.asciidoc.po new file mode 100644 index 0000000..b164488 --- /dev/null +++ b/Automation/Modules/Tuneup/Manuals/Locales/en_US/tuneup.asciidoc.po @@ -0,0 +1,392 @@ +msgid "" +msgstr "" +"Project-Id-Version: tuneup.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-07 15:18-0500\n" +"PO-Revision-Date: 2013-11-07 15:18-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "tuneup" +msgstr "tuneup" + +msgid "1" +msgstr "1" + +msgid "" +"Standardizes source code maintenance tasks inside the repository." +msgstr "" +"Standardizes source code maintenance tasks inside the repository." + +msgid "centos-art.sh tuneup [FILE …|DIRECTORY …] [--filter=\"REGEX\"]" +msgstr "" +"centos-art.sh tuneup [FILE …|DIRECTORY …] [--filter=\"REGEX\"]" + +msgid "Execute source code maintenance tasks." +msgstr "Execute source code maintenance tasks." + +msgid "Description" +msgstr "Description" + +msgid "" +"When you run the tuneup module " +"it may enter into either file or directory processing, based on " +"whether you provide a file or directory as argument for processing " +"in the command-line. When you provide a file as argument to " +"tuneup module, it uses the " +"file's extension as reference for applying maintenance tasks on " +"that file as described in . When you provide a directory as argument, tuneup looks for all files with supported " +"extensions inside that directory and then process them, one by one." +msgstr "" +"When you run the tuneup module " +"it may enter into either file or directory processing, based on " +"whether you provide a file or directory as argument for processing " +"in the command-line. When you provide a file as argument to " +"tuneup module, it uses the " +"file's extension as reference for applying maintenance tasks on " +"that file as described in . When you provide a directory as argument, tuneup looks for all files with supported " +"extensions inside that directory and then process them, one by one." + +msgid "" +"The tuneup module exists to " +"automate frequent tasks related to code maintenance, inside the " +"repository (see ). It is advisable to " +"run tuneup module over your " +"files from time to time so they all have a common look and feel." +msgstr "" +"The tuneup module exists to " +"automate frequent tasks related to code maintenance, inside the " +"repository (see ). It is advisable to " +"run tuneup module over your " +"files from time to time so they all have a common look and feel." + +msgid "Supported File Extensions" +msgstr "Supported File Extensions" + +msgid "" +"The tuneup module supports " +"maintenance tasks for the following file extensions:" +msgstr "" +"The tuneup module supports " +"maintenance tasks for the following file extensions:" + +msgid ".svgz, .svg" +msgstr ".svgz, .svg" + +msgid "Provides maintenance tasks for Scalable Vector Graphics (SVG)." +msgstr "" +"Provides maintenance tasks for Scalable Vector Graphics (SVG)." + +msgid "" +"When processing svg files, tuneup uses the inkscape's --vaccumm option to cleanup source " +"code and applies few sed commands to modify inkscape's metadata " +"using dynamic information like document title, date, copyright " +"information, urls, and locale information retrieved from from " +"centos-art.sh script and the file location inside the repository." +msgstr "" +"When processing svg files, tuneup uses the inkscape's --vaccumm option to cleanup source " +"code and applies few sed commands to modify inkscape's metadata " +"using dynamic information like document title, date, copyright " +"information, urls, and locale information retrieved from from " +"centos-art.sh script and the file location inside the repository." + +msgid "" +"Each time you create a new svg file or change one, it is advisable " +"to run tuneup module over it." +msgstr "" +"Each time you create a new svg file or change one, it is advisable " +"to run tuneup module over it." + +msgid ".xhtml, .html, .htm" +msgstr ".xhtml, .html, .htm" + +msgid "" +"Provides maintenance tasks for HyperText Markup Language (HTML)." +msgstr "" +"Provides maintenance tasks for HyperText Markup Language (HTML)." + +msgid "" +"When processing html-like files, tuneup changes each file to create a table of contents for each " +"heading constructions (see below) first and then transforms the " +"(probably malformed) HTML markup into valid XHTML documents using " +"xmllint(1) program." +msgstr "" +"When processing html-like files, tuneup changes each file to create a table of contents for each " +"heading constructions (see below) first and then transforms the " +"(probably malformed) HTML markup into valid XHTML documents using " +"xmllint(1) program." + +msgid "" +"In order for tuneup to create " +"the table of contents correctly, the heading construction inside " +"the HTML document must comply the following restrictions:" +msgstr "" +"In order for tuneup to create " +"the table of contents correctly, the heading construction inside " +"the HTML document must comply the following restrictions:" + +msgid "Headings must have one of the following forms:" +msgstr "Headings must have one of the following forms:" + +#, no-wrap +msgid "" +"<h1><a name=\"\">Title</a></h1>\n" +"<h1><a href=\"\">Title</a></h1>\n" +"<h1><a name=\"\" href=\"\">Title</a></h1>" +msgstr "" +"<h1><a name=\"\">Title</a></h1>\n" +"<h1><a href=\"\">Title</a></h1>\n" +"<h1><a name=\"\" href=\"\">Title</a></h1>" + +msgid "" +"In these constructions, the heading level may vary from h1 to h6 " +"but the heading content (e.g., “Title”) must not be empty." +msgstr "" +"In these constructions, the heading level may vary from h1 to h6 " +"but the heading content (e.g., “Title”) must not be empty." + +msgid "" +"When producing table of contents through tuneup module, both `name' and `href' attributes in " +"the anchor element of each heading will be reset dynamically using " +"a md5 string. The md5 string used in these cases is based on the " +"heading content (i.e., the text shown as heading when the page is " +"rendered in a browser) and won't change until you change the " +"heading content and run tuneup " +"module over it again." +msgstr "" +"When producing table of contents through tuneup module, both `name' and `href' attributes in " +"the anchor element of each heading will be reset dynamically using " +"a md5 string. The md5 string used in these cases is based on the " +"heading content (i.e., the text shown as heading when the page is " +"rendered in a browser) and won't change until you change the " +"heading content and run tuneup " +"module over it again." + +msgid "" +"The final table of contents will be expanded wherever you set the " +"<div class=\"toc\"></div> HTML " +"construction as a line of its own inside the file being processed." +msgstr "" +"The final table of contents will be expanded wherever you set the " +"<div class=\"toc\"></div> HTML " +"construction as a line of its own inside the file being processed." + +msgid ".sh" +msgstr ".sh" + +msgid "Provides maintenance tasks for Bash scripts." +msgstr "Provides maintenance tasks for Bash scripts." + +msgid "" +"When processing sh files, tuneup changes the file to update the written by section, " +"copyright year and license information inside shell scripts' top " +"comment. Later, it corrects variable name's references to be all " +"written in upper-case between brackets (e.g.," +msgstr "" +"When processing sh files, tuneup changes the file to update the written by section, " +"copyright year and license information inside shell scripts' top " +"comment. Later, it corrects variable name's references to be all " +"written in upper-case between brackets (e.g.," + +msgid "" +"In order for tuneup module to " +"update the top comment of your shell scripts correctly, it is " +"necessary that your top comments have one written by line followed by a line of 70 number-sign (#) characters, " +"as illustrated in This is the basic " +"construction. Everything between the written by " +"line and the last line of 70 number-sign characters will be " +"replaced by tuneup module top-" +"comment template which includes people names, copyright and license " +"information. Everything else does remain untouched." +msgstr "" +"In order for tuneup module to " +"update the top comment of your shell scripts correctly, it is " +"necessary that your top comments have one written by line followed by a line of 70 number-sign (#) characters, " +"as illustrated in This is the basic " +"construction. Everything between the written by " +"line and the last line of 70 number-sign characters will be " +"replaced by tuneup module top-" +"comment template which includes people names, copyright and license " +"information. Everything else does remain untouched." + +msgid "Top-comment convention used by tuneup module." +msgstr "Top-comment convention used by tuneup module." + +#, no-wrap +msgid "" +"#!/bin/bash\n" +"######################################################################\n" +"#\n" +"# ${FILE}.sh -- ${DESCRIPTION}\n" +"#\n" +"# Written by:\n" +"#\n" +"######################################################################" +msgstr "" +"#!/bin/bash\n" +"######################################################################\n" +"#\n" +"# ${FILE}.sh -- ${DESCRIPTION}\n" +"#\n" +"# Written by:\n" +"#\n" +"######################################################################" + +msgid "Options" +msgstr "Options" + +msgid "--help" +msgstr "--help" + +msgid "Print module's documentation." +msgstr "Print module's documentation." + +msgid "--version" +msgstr "--version" + +msgid "Print module's version." +msgstr "Print module's version." + +msgid "--filter=\"REGEX\"" +msgstr "--filter=\"REGEX\"" + +msgid "" +"This option let you reduce the number of files you want to process " +"by applying a (POSIX-egrep) regular expression to the list of file " +"paths returned for processing. This option is specially useful when " +"you need to process files inside a directory structure based on a " +"specific name patterns." +msgstr "" +"This option let you reduce the number of files you want to process " +"by applying a (POSIX-egrep) regular expression to the list of file " +"paths returned for processing. This option is specially useful when " +"you need to process files inside a directory structure based on a " +"specific name patterns." + +msgid "Examples" +msgstr "Examples" + +msgid "centos-art.sh tuneup Automation/Scripts" +msgstr "centos-art.sh tuneup Automation/Scripts" + +msgid "" +"This command updates the top comment and variable name references " +"of all files inside the Automation/Scripts directory, recursively." +msgstr "" +"This command updates the top comment and variable name references " +"of all files inside the Automation/Scripts directory, recursively." + +msgid "centos-art.sh tuneup Automation/Scripts/tcar_printVersion.sh" +msgstr "centos-art.sh tuneup Automation/Scripts/tcar_printVersion.sh" + +msgid "" +"This commands updates the top comment and variable name references " +"inside the tcar_printVersion.sh file only." +msgstr "" +"This commands updates the top comment and variable name references " +"inside the tcar_printVersion.sh file only." + +msgid "" +"centos-art.sh tuneup Automation/Scripts --filter=\"tcar_print.+\\.sh" +"$\"" +msgstr "" +"centos-art.sh tuneup Automation/Scripts --filter=\"tcar_print.+\\.sh" +"$\"" + +msgid "" +"This command updates the top comment and variable name refrences " +"inside files which name only begins with “tcar_print” followed by " +"any character and ends with “.sh”. All other files won't be touched." +msgstr "" +"This command updates the top comment and variable name refrences " +"inside files which name only begins with “tcar_print” followed by " +"any character and ends with “.sh”. All other files won't be touched." + +msgid "Author" +msgstr "Author" + +msgid "" +"The tuneup module has received " +"contributions from the following people:" +msgstr "" +"The tuneup module has received " +"contributions from the following people:" + +msgid "" +"Alain Reguera Delgado, =COPYRIGHT_YEAR_FIRST=-=COPYRIGHT_YEAR_LAST=" +msgstr "" +"Alain Reguera Delgado, =COPYRIGHT_YEAR_FIRST=-=COPYRIGHT_YEAR_LAST=" + +msgid "Copyright" +msgstr "Copyright" + +msgid "" +"Copyright © =COPYRIGHT_YEAR_FIRST=-=COPYRIGHT_YEAR_LAST= " +"=COPYRIGHT_HOLDER=" +msgstr "" +"Copyright © =COPYRIGHT_YEAR_FIRST=-=COPYRIGHT_YEAR_LAST= " +"=COPYRIGHT_HOLDER=" + +msgid "" +"The tuneup module 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." +msgstr "" +"The tuneup module 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." + +msgid "" +"Tue tuneup module 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." +msgstr "" +"Tue tuneup module 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." + +msgid "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." +msgstr "" +"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., 675 Mass Ave, Cambridge, MA 02139, USA." + +msgid "See Also" +msgstr "See Also" + +msgid "centos-art.sh(1), xmllint(1)" +msgstr "centos-art.sh(1), xmllint(1)" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Modules/Tuneup/Manuals/render.conf b/Automation/Modules/Tuneup/Manuals/render.conf index a064bdf..3694c89 100644 --- a/Automation/Modules/Tuneup/Manuals/render.conf +++ b/Automation/Modules/Tuneup/Manuals/render.conf @@ -1,15 +1,7 @@ -# -# This files contains the configuration options the render module -# needs to generate both manpage and xhtml files from asciidoc files. -# [tuneup] render-type = "asciidoc" render-flow = "manpage" render-from = "tuneup.asciidoc" -tuneup-from = "${TCAR_SCRIPT_LANG_LC}/tuneup.asciidoc.po" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/tuneup.asciidoc.po" formats = "xhtml manpage" mansect = "1" - -# -# Add configuration to module's sh files, as well. -#