diff --git a/Locales/Documentation/Models/Docbook/Tcar-ug/es_ES/messages.po b/Locales/Documentation/Models/Docbook/Tcar-ug/es_ES/messages.po index 408b5f1..3f5e3d8 100644 --- a/Locales/Documentation/Models/Docbook/Tcar-ug/es_ES/messages.po +++ b/Locales/Documentation/Models/Docbook/Tcar-ug/es_ES/messages.po @@ -1,8 +1,8 @@ msgid "" msgstr "" -"Project-Id-Version: centos-art-0.0.3\n" -"POT-Creation-Date: 2012-09-16 11:53-0400\n" -"PO-Revision-Date: 2012-11-03 14:11-0500\n" +"Project-Id-Version: centos-art-0.4\n" +"POT-Creation-Date: 2013-06-10 16:05-0400\n" +"PO-Revision-Date: 2013-06-10 16:05-0400\n" "Last-Translator: Documentation SIG\n" "Language-Team: Español\n" "MIME-Version: 1.0\n" @@ -13,8 +13,8 @@ msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for you. #. It doesn't matter what you translate it to: it's not used at all. msgid "" -"@@image: 'Images/Manuals/Corporate/monolithic.png'; " -"md5=6d128a567333d3f96ff0fd5e4c49abf6" +"@@image: 'Images/Manuals/Corporate/monolithic.png'; md5=THIS FILE " +"DOESN'T EXIST" msgstr "" #. Front matter @@ -42,17 +42,21 @@ msgstr "" msgid "2012" msgstr "" +msgid "2013" +msgstr "" + msgid "" -"The CentOS Project. All rights reserved." +"The CentOS " +"Project. All rights reserved." msgstr "" msgid "" -"Permission is granted to copy, distribute and/or modify this document under " -"the terms of the GNU Free Documentation License, Version 1.2 or any later " -"version published by the Free Software Foundation; with no Invariant " -"Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the " -"license is included in ." +"Permission is granted to copy, distribute and/or modify this " +"document under the terms of the GNU Free Documentation License, " +"Version 1.2 or any later version published by the Free Software " +"Foundation; with no Invariant Sections, no Front-Cover Texts, and " +"no Back-Cover Texts. A copy of the license is included in ." msgstr "" msgid "1.0" @@ -73,83 +77,87 @@ msgstr "" msgid "" "Welcome to The CentOS Artwork Repository User's Guide, the official documentation of The CentOS Artwork Repository." +"\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " +"Repository." msgstr "" msgid "" -"This book describes the corporate visual identity of The CentOS Project and the way it is " -"produced. If you are interested in making The CentOS Project a more beautiful project, this " -"book is definitly for you." +"This book describes the corporate visual identity of The CentOS Project " +"and the way it is produced. If you are interested in making The CentOS Project a more beautiful project, this book is definitly for you." msgstr "" msgid "" -"To make the information in this book managable, it has been organized in the " -"following parts:" +"To make the information in this book managable, it has been " +"organized in the following parts:" msgstr "" msgid "" -" describes the convenctions you should follow to " -"keep everything organized and consistent inside the repository directory " -"structure, how to to install and configure a working copy inside your " -"workstation. At the end of this part you will find a history of most " -"relevant changes committed to the repository along the years." +" describes the convenctions you should " +"follow to keep everything organized and consistent inside the " +"repository directory structure, how to to install and configure a " +"working copy inside your workstation. At the end of this part you " +"will find a history of most relevant changes committed to the " +"repository along the years." msgstr "" msgid "" -" describes the corporate visual identity of the " -"organization known as The " -"CentOS Project and the production tasks related to image rendition " -"inside The CentOS Artwork Repository. If you are a graphic designer, " +" describes the corporate visual " +"identity of the organization known as The CentOS Project and the " +"production tasks related to image rendition inside The " +"CentOS Artwork Repository. If you are a graphic designer, " "this part of the book might result interesting to you." msgstr "" msgid "" -" describes production tasks related to content " -"internationalization and localization inside The CentOS Artwork Repository. If you are a translator, this part of the book might result " -"interesting to you." +" describes production tasks related to " +"content internationalization and localization inside The " +"CentOS Artwork Repository. If you are a translator, this " +"part of the book might result interesting to you." msgstr "" msgid "" -" describes production tasks related to content " -"documentation inside The CentOS Artwork Repository. If you are a " -"documentor, this part of the book might result interesting to you." +" describes production tasks related to " +"content documentation inside The CentOS Artwork Repository. If you are a documentor, this part of the book might result " +"interesting to you." msgstr "" msgid "" -" describes automation of production tasks inside " -"The " -"CentOS Artwork Repository. If you are a programmer, this part of the " -"book might result interesting to you." +" describes automation of production " +"tasks inside The CentOS Artwork Repository. If you are " +"a programmer, this part of the book might result interesting to you." msgstr "" msgid "" -" organizes the licenses mentioned in this book." +" organizes the licenses mentioned in " +"this book." msgstr "" msgid "" -"This book assumes you have a basic understanding of The CentOS Distribution. " -"If you need help with it, go to the Help page inside The CentOS Wiki for or a list of different places you can " -"find help." +"This book assumes you have a basic understanding of The CentOS " +"Distribution. If you need help with it, go to the Help page inside The CentOS Wiki for or a list of different places you can find help." msgstr "" msgid "Document Convenctions" msgstr "" msgid "" -"In this manual, certain words are represented in different fonts, typefaces, " -"sizes, and weights. This highlighting is systematic; different words are " -"represented in the same style to indicate their inclusion in a specific " -"category. The types of words that are represented this way include the " -"following:" +"In this manual, certain words are represented in different fonts, " +"typefaces, sizes, and weights. This highlighting is systematic; " +"different words are represented in the same style to indicate their " +"inclusion in a specific category. The types of words that are " +"represented this way include the following:" msgstr "" msgid "command" @@ -157,39 +165,43 @@ msgstr "" msgid "" "Linux commands (and other operating system commands, when used) are " -"represented this way. This style should indicate to you that you can type " -"the word or phrase on the command line and press Enter to " -"invoke a command. Sometimes a command contains words that would be displayed " -"in a different style on their own (such as file names). In these cases, they " -"are considered to be part of the command, so the entire phrase is displayed " -"as a command. For example:" +"represented this way. This style should indicate to you that you " +"can type the word or phrase on the command line and press " +"Enter to invoke a command. Sometimes a command " +"contains words that would be displayed in a different style on " +"their own (such as file names). In these cases, they are considered " +"to be part of the command, so the entire phrase is displayed as a " +"command. For example:" msgstr "" msgid "" -"Use the centos-art render trunk/Identity/Images/Themes/TreeFlower/4/" -"Distro/5/Anaconda --filter=\"01-welcome\" command to produce the " -"first slide image used by Anaconda in the branch 5 of The CentOS " -"Distribution using the version 4 of TreeFlower artistic motif." +"Use the centos-art render Identity/Images/Themes/" +"TreeFlower/4/Distro/5/Anaconda --filter=\"01-welcome\" " +"command to produce the first slide image used by Anaconda in the " +"branch 5 of The CentOS Distribution using the version 4 of " +"TreeFlower artistic motif." msgstr "" msgid "file name" msgstr "" msgid "" -"File names, directory names, paths, and RPM package names are represented " -"this way. This style indicates that a particular file or directory exists " -"with that name on your system. Examples:" +"File names, directory names, paths, and RPM package names are " +"represented this way. This style indicates that a particular file " +"or directory exists with that name on your system. Examples:" msgstr "" msgid "" -"The init.sh file in trunk/" -"Scripts/Bash/Cli/ directory is the initialization script, written " -"in Bash, used to automate most of tasks in the repository." +"The init.sh file in Scripts/Bash/Cli/ directory is the initialization " +"script, written in Bash, used to automate most of tasks in the " +"repository." msgstr "" msgid "" -"The centos-art command uses the ImageMagick RPM package to convert images from PNG format to other formats." +"The centos-art command uses the " +"ImageMagick RPM package to convert images from " +"PNG format to other formats." msgstr "" msgid "key" @@ -199,23 +211,25 @@ msgid "A key on the keyboard is shown in this style. For example:" msgstr "" msgid "" -"To use Tab completion to list particular files in a " -"directory, type ls, then a character, and finally the " -"Tab key. Your terminal displays the list of files in the " -"working directory that begin with that character." +"To use Tab completion to list particular files in " +"a directory, type ls, then a character, and " +"finally the Tab key. Your terminal displays the " +"list of files in the working directory that begin with that " +"character." msgstr "" msgid "combination" msgstr "" -msgid "A combination of keystrokes is represented in this way. For example:" +msgid "" +"A combination of keystrokes is represented in this way. For example:" msgstr "" msgid "" "The CtrlAltBackspace key combination exits your " -"graphical session and returns you to the graphical login screen or the " -"console." +"keycap>Backspace key combination exits " +"your graphical session and returns you to the graphical login " +"screen or the console." msgstr "" #, no-wrap @@ -223,9 +237,10 @@ msgid "computer output" msgstr "" msgid "" -"Text in this style indicates text displayed to a shell prompt such as error " -"messages and responses to commands. For example, the ls " -"command displays the contents of a directory using this style:" +"Text in this style indicates text displayed to a shell prompt such " +"as error messages and responses to commands. For example, the " +"ls command displays the contents of a directory " +"using this style:" msgstr "" #, no-wrap @@ -237,16 +252,16 @@ msgid "" msgstr "" msgid "" -"The output returned in response to the command (in this case, the contents " -"of the directory) is shown in this style." +"The output returned in response to the command (in this case, the " +"contents of the directory) is shown in this style." msgstr "" msgid "prompt" msgstr "" msgid "" -"A prompt, which is a computer's way of signifying that it is ready for you " -"to input something, is shown in this style. Examples:" +"A prompt, which is a computer's way of signifying that it is ready " +"for you to input something, is shown in this style. Examples:" msgstr "" msgid "$" @@ -266,526 +281,711 @@ msgid "user input" msgstr "" msgid "" -"Text that the user types, either on the command line or into a text box on a " -"GUI screen, is displayed in this style. In the following example, " -"text is displayed in this style: To boot your system " -"into the text based installation program, you must type in the " -"text command at the boot: prompt." +"Text that the user types, either on the command line or into a text " +"box on a GUI screen, is displayed in this style. In the following " +"example, text is displayed in this style: To " +"boot your system into the text based installation program, you must " +"type in the text command at the boot:" +" prompt." msgstr "" msgid "replaceable" msgstr "" msgid "" -"Text used in examples that is meant to be replaced with data provided by the " -"user is displayed in this style. In the following example, " -"version-number is displayed in this style: The " -"directory for the kernel source is /usr/src/" -"kernels/version-number/, where " -"version-number is the version and type of kernel " -"installed on this system." +"Text used in examples that is meant to be replaced with data " +"provided by the user is displayed in this style. In the following " +"example, version-number is displayed in " +"this style: The directory for the kernel source is /usr/src/kernels/version-number/, where version-number is the version and type of kernel installed on this " +"system." msgstr "" msgid "" -"Additionally, we use several different strategies to draw your attention to " -"certain pieces of information. In order of urgency, these items are marked " -"as a note, tip, important, caution, or warning. For example:" +"Additionally, we use several different strategies to draw your " +"attention to certain pieces of information. In order of urgency, " +"these items are marked as a note, tip, important, caution, or " +"warning. For example:" msgstr "" msgid "" -"Remember that Linux is case sensitive. In other words, a rose is not a ROSE " -"is not a rOsE." +"Remember that Linux is case sensitive. In other words, a rose is " +"not a ROSE is not a rOsE." msgstr "" msgid "" -"The directory /usr/share/doc/ " -"contains additional documentation for packages installed on your system." +"The directory /usr/share/doc/ contains additional documentation for packages installed " +"on your system." msgstr "" msgid "" -"If you modify the DHCP configuration file, the changes do not take effect " -"until you restart the DHCP daemon." +"If you modify the DHCP configuration file, the changes do not take " +"effect until you restart the DHCP daemon." msgstr "" msgid "" -"Do not perform routine tasks as root — use a regular user account unless you " -"need to use the root account for system administration tasks." +"Do not perform routine tasks as root — use a regular user account " +"unless you need to use the root account for system administration " +"tasks." msgstr "" msgid "" "Be careful to remove only the necessary partitions. Removing other " -"partitions could result in data loss or a corrupted system environment." +"partitions could result in data loss or a corrupted system " +"environment." msgstr "" msgid "Send In Your Feedback" msgstr "" msgid "" -"If you find a bug in The CentOS Artwork Repository or this manual, we would " -"like to hear about it. To report bugs related to this manual, send an e-mail " -"to the centos-devel@centos.org mailing list. When you write " -"the bug report, take care of being specific about the problem you are " -"reporting on (e.g., where it is, the section number, etc.) so we can found " -"it easily." +"If you find a bug in The CentOS Artwork Repository or " +"this manual, we would like to hear about it. To report bugs related " +"to this manual, send an e-mail to the centos-devel@centos." +"org mailing list. When you write the bug report, take care " +"of being specific about the problem you are reporting on (e.g., " +"where it is, the section number, etc.) so we can found it easily." msgstr "" msgid "Repository" msgstr "" -msgid "Repository Convenctions" +msgid "Repository Conventions" msgstr "" msgid "Repository Mission" msgstr "" msgid "" -"The " -"CentOS Artwork Repository exists to produce The CentOS Project corporate visual " -"identity." +"The CentOS Artwork Repository exists to produce The CentOS Project corporate visual identity." msgstr "" msgid "Repository Layout" msgstr "" msgid "" -"The " -"CentOS Artwork Repository is supported by Subversion, a version control system which " -"allows you to keep old versions of files and directories (usually source " -"code), keep a log of who, when, and why changes occurred, etc., like CVS, " -"RCS or SCCS." +"The CentOS Artwork Repository is made of one " +"central repository and many working copies of that central repository. The working copies are " +"independent one another, can be distributed all around the world " +"and provide a local place for designers, documenters, translators " +"and programmers to perform their work in a decentralized way. The " +"central repository, on the other hand, provides a common place for " +"all independent working copies to interchange data in the community." msgstr "" msgid "" -"The " -"CentOS Artwork Repository is made of one source repository and many working copies of that source repository. The " -"working copies are independent one another, can be distributed all around " -"the world and provide a local place for designers, documentors, translators " -"and programmers to perform their work in a descentralized way. The source " -"repository, on the other hand, provides a central place for all independent " -"working copies to interchange data and provides the information required to " -"permit extracting previous versions of files at any time." +"The current infrastructure that holds The CentOS Artwork " +"Repository is supported by Subversion, a version control system which " +"allows you to keep old versions of files and directories (usually " +"source code), keep a log of who, when, and why changes occurred, " +"etc., like CVS, RCS or SCCS and Trac, a web-based software project management and " +"bug/issue tracking system emphasizing ease of use and low ceremony." msgstr "" msgid "" -"The first level of directories inside The CentOS Artwork Repository " -"provides organization through a convenctional trunk/, branches/ and " -"tags/ layout. As proposition we are " -"assuming that:" +"In addition to current Subversion infrastructure, we are working on " +"a Git infrastructure with the intention of migrating the central " +"repository to it, progressively. Here we use Gitolite to manage Git " +"repositories, Gitweb to make changes browsable through the web and " +"Mantis to track repository issues. The main reason for this " +"migration is to take advantage of distributed version control " +"system inside The CentOS Artwork Repository. It also " +"let people to commit changes locally, without any network access, " +"and later push local commits up to central repository, when the " +"network access be re-established. This could be very useful in very " +"different kind of situations." msgstr "" -msgid "" -"The trunk/ directory is where " -"development changes take place." +msgid "Subversion" msgstr "" msgid "" -"The branches/ directory is where " -"maintainance changes take place." +"In this layout, the first level of directories inside The " +"CentOS Artwork Repository provides the Subversion's " +"standard trunk-branches-tags layout. The second level of " +"directories provides organization for different work lines, as " +"described in . All other " +"subsequent directory levels from second level on exist to organize " +"specific concepts related to the work line they belong to." msgstr "" -msgid "" -"The tags/ directory is where final " -"releases take place." +msgid "Git" msgstr "" msgid "" -"The second level of directories inside The CentOS Artwork Repository " -"provides organization for different work lines, as described in . All other subsequent directory levels " -"from third level on exist to organize specific concepts related to the work " -"line they belong to." +"In this layout, the first level of directories provides " +"organization for different work lines, as described in . All other subsequent directory " +"levels from second level on exist to organize specific concepts " +"related to the work line they belong to." msgstr "" msgid "Repository Work Lines" msgstr "" msgid "" -"The content production inside The CentOS Artwork Repository has been " -"divided into individual work lines that relate one another based on the idea " -"of doing one thing well. In this model, the content produced individually by " -"each work line is combined one another later to achieve higher purposes (e." -"g., corporate identity for The CentOS Project). The repository work lines, as conceived " -"here, provide a relaible environment for people to work syncronized and " +"The content production inside The CentOS Artwork Repository has been divided into individual work lines that relate one " +"another based on the idea of doing one thing well. In this model, " +"the content produced individually by each work line is combined one " +"another later to achieve higher purposes (e.g., corporate identity " +"for The CentOS " +"Project). The repository work lines, as conceived here, " +"provide a relaible environment for people to work syncronized and " "descentralized." msgstr "" msgid "" "The action of combining work lines inside The CentOS Artwork Repository is known as the corporate identity production cycle. The rest of this " -"section describes the work lines available in the repository and how they " -"fit inside the corporate identity production cycle." +"\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " +"Repository is known as the corporate identity production " +"cycle. The rest of this section describes the work lines available " +"in the repository and how they fit inside the corporate identity " +"production cycle." msgstr "" msgid "Visual Identity" msgstr "" msgid "" -"The visual identity is the first component we work out in order to produce a " -"new corporate identity. Through this work line, graphic designers create " -"models and motifs for all the visual " -"manifestation The CentOS " -"Project is made of. Once design models and artistic motifs are set " -"in place, graphic designers use the render " -"functionality described in to " -"combine both design models and artistic motifs into final images." +"The visual identity is the first component we work out in order to " +"produce a new corporate identity. Through this work line, graphic " +"designers create models and motifs " +"for all the visual manifestation The CentOS Project is made of. Once design " +"models and artistic motifs are set in place, graphic designers use " +"the render functionality described in to combine both design models and " +"artistic motifs into final images." msgstr "" msgid "" -"The main purposes of this work line is define all the visual manifestations " -"the The CentOS Project is made of and provide design models and artistic motifs for them in " -"order to render the set of images required to transmit the visual style that " -"identifies The CentOS " -"Project as unique organization. To know more about The CentOS Project Corporate Visual " -"Identity, read ." +"The main purposes of this work line is define all the visual " +"manifestations the The CentOS Project is made of and provide design models " +"and artistic motifs for them in order to render the set of images " +"required to transmit the visual style that identifies The CentOS Project " +"as unique organization. To know more about The CentOS Project Corporate " +"Visual Identity, read ." msgstr "" msgid "" -"The visual identity work line takes palce in the trunk/Identity directory." +"The visual identity work line takes palce in the Identity directory." msgstr "" msgid "Localization" msgstr "" msgid "" -"The content localization is the second component that must be worked out in " -"the corporate identity production cycle. Through this work line translators " -"localize source files (e.g., SVG, DocBook, Shell scripts) which are later " -"use to produce localized images, localized documentation and localized " -"automation scripts. To localize source files, translators use the " -"locale functionality described in which takes care of retriving translatable strings " -"from source files and provide a consistent localization interface based on " -"GNU gettext multi-lingual message production tool " -"set and xml2po command." +"The content localization is the second component that must be " +"worked out in the corporate identity production cycle. Through this " +"work line translators localize source files (e.g., SVG, DocBook, " +"Shell scripts) which are later use to produce localized images, " +"localized documentation and localized automation scripts. To " +"localize source files, translators use the locale functionality described in which takes care of retriving translatable strings from " +"source files and provide a consistent localization interface based " +"on GNU gettext multi-lingual message " +"production tool set and xml2po command." msgstr "" msgid "" -"The main purpose of this work line is extend the visual identity (produced " -"in English language) to as many native languages as possible in order for " -"people which doesn't understand English languague to feel more confortable " -"with The CentOS Project and its messages. To know more about the specific localization " -"process read ." +"The main purpose of this work line is extend the visual identity " +"(produced in English language) to as many native languages as " +"possible in order for people which doesn't understand English " +"languague to feel more confortable with The CentOS Project and its " +"messages. To know more about the specific localization process read " +"." msgstr "" msgid "" -"The localization work line takes palce in the trunk/" -"Locales directory." +"The localization work line takes palce in the Locales directory." msgstr "" -#, fuzzy msgid "Documentation" -msgstr "Licencia de Documentación Libre de GNU" +msgstr "" msgid "" -"The documentation work line is the third component that must be worked out " -"in the corporate identity production cycle. Through this work line " -"documentors settle down the conceptual and practical used to edificate " -"The " -"CentOS Artwork Repository. To write documentation, documentors use " -"the help functionality described in which provides a consistent interface for building " -"documentation through different documentation backends (e.g., Texinfo, " -"DocBook, LaTeX, etc.)." +"The documentation work line is the third component that must be " +"worked out in the corporate identity production cycle. Through this " +"work line documentors settle down the conceptual and practical used " +"to edificate The CentOS Artwork Repository. To write " +"documentation, documentors use the help " +"functionality described in " +"which provides a consistent interface for building documentation " +"through different documentation backends (e.g., Texinfo, DocBook, " +"LaTeX, etc.)." msgstr "" msgid "" -"The main purpose of this work line is describe the standard procedures " -"The " -"CentOS Artwork Repository realies on, as well as conceive a place to " -"help you understand what The CentOS Artwork Repository is and what can you " -"do with it." +"The main purpose of this work line is describe the standard " +"procedures The CentOS Artwork Repository realies on, as " +"well as conceive a place to help you understand what The " +"CentOS Artwork Repository is and what can you do with it." msgstr "" msgid "" -"The documentation work line takes palce in the trunk/" -"Manuals directory." +"The documentation work line takes palce in the Manuals directory." msgstr "" msgid "Packaging" msgstr "" msgid "" -"The packaging work line is the fourth component that must be worked out in " -"the corporate identity production cycle. Through this work line packager " -"gather final images, final translations and final documentation related to " -"art works and put all together inside RPM packages. For this purpose, " -"packagers use the pack describe in which provides a consistent interface for building " -"packages inside the repository." +"The packaging work line is the fourth component that must be worked " +"out in the corporate identity production cycle. Through this work " +"line packager gather final images, final translations and final " +"documentation related to art works and put all together inside RPM " +"packages. For this purpose, packagers use the pack describe in which " +"provides a consistent interface for building packages inside the " +"repository." msgstr "" msgid "" -"The main purpose of this work line is pack all the information The CentOS Project requires " -"to rebrand The CentOS Distribution according Red Hat redistribution " -"guidelines." +"The main purpose of this work line is pack all the information " +"The CentOS " +"Project requires to rebrand The CentOS Distribution " +"according Red Hat redistribution guidelines." msgstr "" msgid "" -"The packaging work line takes palce in the trunk/" -"Packages directory." +"The packaging work line takes palce in the Packages directory." msgstr "" msgid "Automation" msgstr "" msgid "" -"The automation work line is the fifth and last component that must be worked " -"out in the corporate identity production cycle. This work line closes the " -"production cycle and provides the production standards graphic designers, " -"documentors, translators and packagers need to make their work consistent " -"and reusable. For this purpose, programmers develop the centos-art." -"sh script described in ." +"The automation work line is the fifth and last component that must " +"be worked out in the corporate identity production cycle. This work " +"line closes the production cycle and provides the production " +"standards graphic designers, documentors, translators and packagers " +"need to make their work consistent and reusable. For this purpose, " +"programmers develop the centos-art.sh script " +"described in ." msgstr "" msgid "" -"The main purpose of this work line is standardize the interaction of work " -"lines in a reliable way." +"The main purpose of this work line is standardize the interaction " +"of work lines in a reliable way." msgstr "" msgid "" -"The automation work line takes palce in the trunk/" -"Scripts directory." +"The automation work line takes palce in the Scripts directory." msgstr "" msgid "Repository File Names" msgstr "" +msgid "Regular Files" +msgstr "" + +msgid "" +"Inside The CentOS Artwork Repository, file names are " +"always written in lowercase. Digits (e.g., 0, 1, 2), hyphen (-" +"), dot (.) and low line (_) " +"characters are also accepted. In case you use hyphen and dot " +"characters, don't use them as first character in the file name." +msgstr "" + +msgid "Files Written Correctly" +msgstr "" + +msgid "The following file names are written correctly:" +msgstr "" + +msgid "01-welcome.png" +msgstr "" + +msgid "splash.png" +msgstr "" + +msgid "anaconda_header.png" +msgstr "" + +msgid "Files Written Incorrectly" +msgstr "" + +msgid "The following file names are written incorrectly:" +msgstr "" + +msgid "01-Welcome.png" +msgstr "" + +msgid "-welcome.png" +msgstr "" + +msgid "Splash.png" +msgstr "" + +msgid "AnacondaHeader.png" +msgstr "" + +msgid "Exceptions" +msgstr "" + +msgid "When you name files, consider the following exceptions:" +msgstr "" + msgid "" -"Inside The CentOS Artwork Repository, file names are all written in " -"lowercase (e.g., 01-welcome.png, splash.png, anaconda_header.png, etc.) and directory " -"names are all written capitalized (e.g., Identity, Themes, " -"Motifs) and sometimes in cammel case " -"(e.g., TreeFlower, etc.). In the " -"very specific case of repository documentation entries, file names follow " -"the directory naming convenction. This is because they are documenting " -"directories and that is something we want to remark. So, to better describe " -"what we are documenting, documentation entries follow the name convenction " -"used by the item they document." +"In the very specific case of repository documentation entries " +"written in Texinfo format, file names follow the directory " +"structure naming convenction. This is because they are documenting " +"directories and that is something we want to remark. So, to better " +"describe what we are documenting, files related to documentation " +"entries follow the name convenction used by the item they document." msgstr "" -msgid "Repository Path Types" +msgid "Symbolic Links" msgstr "" msgid "" -"In order for automation scripts to produce content inside a working copy of " -"The " -"CentOS Artwork Repository, it is required that all work lines be " -"related somehow. The relation between work lines is used by automation " -"scripts to know where to retrive the information they need to work with (e." -"g., input files, translation messages, output locations, etc.). This kind of " -"relation is built using two path constructions known as master " -"paths and auxiliar paths." +"Inside The CentOS Artwork Repository, symbolic link " +"names follow the same convenctions described in ." msgstr "" -msgid "Master Paths" +msgid "Directories" msgstr "" msgid "" -"A master path refers to a directory inside the repository that contain input " -"files required to produce output files through automation scripts. Examples " -"of master paths inside the repository include:" +"Inside The CentOS Artwork Repository, directory names " +"are all written capitalized and sometimes in cammel case. Digits (e." +"g., 0, 1, 2), hyphen (-), dot (.) and low " +"line (_) characters are also accepted. In case you use " +"hyphen and dot characters, don't use them as first character in the " +"directory name." msgstr "" -msgid "trunk/Identity/Models/Brands" +msgid "Directories Written Correctly" msgstr "" -msgid "trunk/Manuals/Tcar-ug" +msgid "The following directory names are written correctly:" msgstr "" -msgid "trunk/Identity/Models/Themes/Default/Distro/5/Anaconda" +msgid "" +"Identity, Themes, Motifs, TreeFlower" +msgstr "" + +msgid "Tcar-ug" +msgstr "" + +msgid "" +"0.0.1, 0.0.1-35" +msgstr "" + +msgid "Directories Written Incorrectly" msgstr "" -msgid "Auxiliar Paths" +msgid "The following directory names are written incorrectly:" msgstr "" msgid "" -"An auxiliar path refers to directories inside the repository considered " -"auxiliar for one single master path. Auxiliar path can be either for output " -"or localization. Assuming the master path provides the input information, " -"the auxiliar paths provide the auxiliar information which describes how and " -"where that input information must be rendered by automation scripts. " -"Examples of auxiliar paths inside the repository include:" +"identitY, theMes, MOTIFS, treeFlower" msgstr "" -msgid "trunk/Identity/Images/Brands" +msgid "tcar-ug" msgstr "" -msgid "trunk/Manuals/Tcar-ug/es_ES" +msgid "" +".0.1, .0.1-35" msgstr "" -msgid "trunk/Locales/Manuals/Tcar-ug/es_ES" +msgid "When you name directories, consider the following exceptions:" msgstr "" -msgid "trunk/Identity/Images/Themes/Flame/3/Distro/5/Anaconda/es_ES" +msgid "No one so far." msgstr "" -msgid "trunk/Locales/Identity/Models/Default/Distro/5/Anaconda/es_ES" +msgid "Repository Path Relations" msgstr "" msgid "" -"The relationship between master and auxiliar paths is built by combining the " -"second directory level of master paths with directories in the second " -"directory level of repository layout. In the second directory level of " -"repository layout, the Identity, " -"Manuals and Scripts directories are always used to create the " -"master paths and the output auxiliar paths. The Locales directory, on the other hand, is always used to create " -"localization auxiliar paths for all the master paths available under " -"Identity, Manuals and Scripts " -"directories." +"In order for automation scripts to produce content inside a working " +"copy of The CentOS Artwork Repository, it is required " +"that all work lines be related somehow. The automation scripts take " +"the relation between work lines as reference to determine the place " +"the information they will work with will be retrieve from (e.g., " +"scalable vector graphics, documentation, translations, etc.), as " +"well as the place where it will store the final files produced as " +"result of automation process (e.g., portable network graphics, " +"documentation ready for printing and reading online, etc.)." +msgstr "" + +msgid "" +"In order to implement the relation between work lines it is " +"required to establish a path name convenction, so we can " +"conceptually organize different components and relate them one " +"another using predictable path constructions in a scalable way. " +"Based on this need, we identify three different path types inside " +"The CentOS Artwork Repository. These path types are: " +"Output Paths, Input Paths, and Auxiliary Paths." +msgstr "" + +msgid "Output Paths" msgstr "" msgid "" -"For example, if the LANG environment variable is set to " -"es_ES.UTF-8 and you execute the render " -"functionality of centos-art.sh script with the trunk/Manuals/Tcar-ug master path as " -"argument, it will produce The CentOS Artwork Repository User's " -"Guide in Spanish language using translation messages from " -"trunk/Locales/Manuals/Tcar-ug/es_ES auxiliar path and " -"would save final documentation output files under trunk/Manuals/Tcar-ug/es_ES auxiliar path." +"The output paths point to directories inside the working copy which " +"contain files produced from files inside the input paths. For " +"example, the following paths are consider as output paths:" +msgstr "" + +msgid "Identity/Images/Brands/" +msgstr "" + +msgid "Documentation/Manuals/Tcar-ug/" +msgstr "" + +msgid "Identity/Images/Themes/Modern/2/Distro/5/Anaconda/" +msgstr "" + +msgid "" +"Output paths are also known as Render-able " +"Directories because they are the type of path " +"you should provide as argument to functionality so as to produce content through it." +msgstr "" + +msgid "Input Paths" +msgstr "" + +msgid "" +"The input paths point to a directories inside the working copy " +"which contain files used to produce files inside output paths. For " +"example, the following paths are considered as input paths:" +msgstr "" + +msgid "Identity/Models/Brands/" +msgstr "" + +msgid "Documentation/Models/Tcar-ug/" +msgstr "" + +msgid "Identity/Models/Themes/Default/Distro/5/Anaconda/" +msgstr "" + +msgid "Auxiliary Paths" +msgstr "" + +msgid "" +"The auxiliary paths point to directories inside the working copy " +"which contain files used to create modified instances of inside " +"input paths which are use in turn to produce files inside output " +"paths. For example, the following paths are considered as auxiliary " +"paths:" +msgstr "" + +msgid "Locales/Documentation/Models/Docbook/Tcar-ug/es_ES/" +msgstr "" + +msgid "" +"Locales/Identity/Models/Themes/Default/Distro/5/Anaconda/es_ES/" +msgstr "" + +msgid "" +"The relationship between input, output and auxiliary paths is " +"created by combining the first directory level of input paths with " +"the first directory level in the repository directory layout. In " +"the repository directory layout, the first level includes the " +"Identity, Documentation and Scripts directories. These directories are " +"always used to create input and output paths. The Locales directory, on the other hand, is " +"always used to create auxiliary paths only for input paths " +"available under Identity, " +"Documentation and " +"Scripts directories." +msgstr "" + +msgid "" +"For example, if the LANG environment variable is " +"set to es_ES.UTF-8 and you execute the functionality of centos-art.sh script with the Documentation/Manuals/Docbook/Tcar-ug/ input path as " +"argument, it will produce The CentOS Artwork Repository " +"User's Guide in Spanish language using translation " +"messages from Locales/Documentation/Models/Docbook/Tcar-" +"ug/es_ES/ auxiliary path and would save final " +"documentation files under Documentation/Manuals/Docbook/Tcar-ug/es_ES/ output " +"path." msgstr "" msgid "Syncronizing Repository Paths" msgstr "" msgid "" -"Once both master and auxiliar paths have been related in the repository, " -"they shouldn't be changed except you absolutly need to do so. In this cases, " -"when you need to change master or auxiliar paths, it is required that you " -"also change the relation between them so as to retain their bond. This " -"process of keeping master and auxiliar paths connected " -"between themselves is known as path syncronization." +"Once both master and auxiliar paths have been related in the " +"repository, they shouldn't be changed except you absolutly need to " +"do so. In this cases, when you need to change master or auxiliar " +"paths, it is required that you also change the relation between " +"them so as to retain their bond. This process of keeping master and " +"auxiliar paths connected between themselves is known " +"as path syncronization." msgstr "" msgid "" -"Path syncronization is required for automation scripts to know where to " -"store final output, where to retrive translation messages from, and whatever " -"information you might need to count with. If the relation between master " -"paths and auxiliar paths is lost, there is no way for automation scripts to " -"know where to retrive the information they need to work with or where to " -"store the output information produced from it. Through path syncronization " -"we organize and extend the content production inside the repository." +"Path syncronization is required for automation scripts to know " +"where to store final output, where to retrive translation messages " +"from, and whatever information you might need to count with. If the " +"relation between master paths and auxiliar paths is lost, there is " +"no way for automation scripts to know where to retrive the " +"information they need to work with or where to store the output " +"information produced from it. Through path syncronization we " +"organize and extend the content production inside the repository." msgstr "" msgid "" -"Path syncronization affects both movement of files and replacement of " -"content inside files. Movement of files is related to actions like renaming " -"files and directories inside the repository. Replacement of content inside " -"files is related to actions like replacing information (e.g., paths " -"information) inside files in order to keep file contents and file locations " -"consistent one another after a file has been moved." +"Path syncronization affects both movement of files and replacement " +"of content inside files. Movement of files is related to actions " +"like renaming files and directories inside the repository. " +"Replacement of content inside files is related to actions like " +"replacing information (e.g., paths information) inside files in " +"order to keep file contents and file locations consistent one " +"another after a file has been moved." msgstr "" msgid "" -"The order followed to syncronize path information is very important because " -"the versioned nature of the files we are working with. When a renaming " -"action needs to be performed inside the repository, we avoid making " -"replacements inside files first and file movements later. This would demand " -"two commit actions: one for the files' internal changes and another for the " -"file movement itself. Instead, we prefer to perform file movements first and " -"files' internal replacements later. This way it is possible to commit both " -"changes as if they were just one." +"The order followed to syncronize path information is very important " +"because the versioned nature of the files we are working with. When " +"a renaming action needs to be performed inside the repository, we " +"avoid making replacements inside files first and file movements " +"later. This would demand two commit actions: one for the files' " +"internal changes and another for the file movement itself. Instead, " +"we prefer to perform file movements first and files' internal " +"replacements later. This way it is possible to commit both changes " +"as if they were just one." msgstr "" msgid "" -"There is no support for URLs actions inside centos-art.sh " -"script. The centos-art.sh script is designed to work with " -"local files inside the working copy only. If you need to perform URL actions " -"directly, use Subversion's commands instead." +"There is no support for URLs actions inside centos-art.sh script. The centos-art.sh script is " +"designed to work with local files inside the working copy only. If " +"you need to perform URL actions directly, use Subversion's commands " +"instead." msgstr "" msgid "" -"At this moment there isn't full implementation of path syncronization inside " -"centos-art.sh script and that is somthing we need to do " -"oursleves. However, the texinfo backend inside the " -"help functionality does provide a restricted " -"implementation of path syncronization to documentation area through the " -", and and " +"options. You can read this implementation and use it as reference " +"to implement path syncronization in other areas." msgstr "" msgid "" "The plan for a full implementation of path syncronization inside " -"centos-art.sh script would be to create individual " -"restricted implementations like the one in texinfo backend " -"for other areas that demand it and then, create a higher implmentation that " -"combines them all as needed. This way, if we try to rename a repository " -"directory, the higher action can know which are all the restricted actions " -"that should be performed in order to make the full path syncronization." +"centos-art.sh script would be to create " +"individual restricted implementations like the one in " +"texinfo backend for other areas that demand it and " +"then, create a higher implmentation that combines them all as " +"needed. This way, if we try to rename a repository directory, the " +"higher action can know which are all the restricted actions that " +"should be performed in order to make the full path syncronization." msgstr "" msgid "" -"For example, if the directory we are renaming is a master path, it is " -"required to syncronize the related output and localization auxiliar paths. " -"On the other hand, if the directory we are renaming through full path " -"syncronization is an auxiliar path, it is required to determine first what " -"is the related master path and later, perform the syncronization from master " -"path to auxiliar paths as if the path provided would be the master path not " -"the auxiliar path." +"For example, if the directory we are renaming is a master path, it " +"is required to syncronize the related output and localization " +"auxiliar paths. On the other hand, if the directory we are renaming " +"through full path syncronization is an auxiliar path, it is " +"required to determine first what is the related master path and " +"later, perform the syncronization from master path to auxiliar " +"paths as if the path provided would be the master path not the " +"auxiliar path." msgstr "" msgid "Extending Repository Layout" msgstr "" msgid "" -"Occasionly, you may find that new components of The CentOS Project Corporate Visual " -"Identity need to be added to the repository in order to work them out. If " -"that is the case, the first question we need to ask ourselves, before " -"starting to create directories blindly all over, is: What is the " -"right place to store it?" +"Occasionly, you may find that new components of The CentOS Project " +"Corporate Visual Identity need to be added to the repository in " +"order to work them out. If that is the case, the first question we " +"need to ask ourselves, before starting to create directories " +"blindly all over, is: What is the right place to store it?" +"" msgstr "" msgid "" -"To build a directory structure inside the repository you need to define the " -"concept behind it first. Later you need to create a new directory inside the " -"repository, remembering that there are locations inside the repository that " -"already define concepts you probably would prefer to reuse. For example, the " -"trunk/Identity/Images/Themes " -"directory stores artistic motifs of different themes, the trunk/Identity/Models/Themes directory stores " -"design models for themes, the trunk/Manuals directory stores documentation, the trunk/Locales stores translation messages, and the trunk/Scripts stores automation scripts." +"To build a directory structure inside the repository you need to " +"define the concept behind it first. Later you need to create a new " +"directory inside the repository, remembering that there are " +"locations inside the repository that already define concepts you " +"probably would prefer to reuse. For example, the Identity/Images/Themes directory stores " +"artistic motifs of different themes, the Identity/Models/Themes directory stores design models " +"for themes, the Manuals " +"directory stores documentation, the Locales stores translation messages, and the " +"Scripts stores automation " +"scripts." msgstr "" msgid "" -"The best suggestion we can probably give you would be to send a mail with " -"your questions to the CentOS " -"developers mailing list (centos-devel@centos.org). This is the place where development of " -"The " -"CentOS Artwork Repository takes place and surely, in community, it " +"The best suggestion we can probably give you would be to send a " +"mail with your questions to the CentOS developers mailing list (centos-devel@centos.org). This is the place where development of The CentOS " +"Artwork Repository takes place and surely, in community, it " "will be possible to find a place for your new component inside the " "repository." msgstr "" @@ -794,158 +994,170 @@ msgid "Repository Publishing" msgstr "" msgid "" -"When you perform changes inside your working copy, those changes are local " -"to your working copy only. In order for you to share your changes with " -"others, you need to commit them up to the central repository the working " -"copy you are using was initially downloaded from. To commit your changes up " -"to the central repository you use the commit command from " -"the Subversion's client you've installed in your workstation." +"When you perform changes inside your working copy, those changes " +"are local to your working copy only. In order for you to share your " +"changes with others, you need to commit them up to the central " +"repository the working copy you are using was initially downloaded " +"from. To commit your changes up to the central repository you use " +"the commit command from the Subversion's client " +"you've installed in your workstation." msgstr "" msgid "" "Initially, when you get registered inside The CentOS Artwork Repository, you won't be able to publish your changes to The CentOS Artwork " -"Repository immediatly. It is necessary that you prove your interest " -"in contributing first sending a mail to the CentOS Developers mailing list " -"(centos-devel@centos.org), preferably in conjunction with a description of the changes you " -"pretend to commit. This restriction is necessary in order to protect the " -"source repository from spammers." +"\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " +"Repository, you won't be able to publish your changes to " +"The CentOS Artwork Repository immediatly. It is " +"necessary that you prove your interest in contributing first " +"sending a mail to the CentOS Developers mailing list " +"(centos-devel@centos." +"org), preferably in conjunction with a description of the " +"changes you pretend to commit. This restriction is necessary in " +"order to protect the source repository from spammers." msgstr "" msgid "" -"Once you've received access to publish your changes, they will remain valid " -"to you and there is no need for you to request permission to publish new " -"changes as long as you behave as a good cooperating citizen." +"Once you've received access to publish your changes, they will " +"remain valid to you and there is no need for you to request " +"permission to publish new changes as long as you behave as a good " +"cooperating citizen." msgstr "" msgid "" -"As a good cooperating citizen one understand of a person who respects the " -"work already done by others and share ideas with authors before changing " -"relevant parts of their work, specially in situations when the access " -"required to realize the changes has been granted already. Of course, there " -"is a time when conversation has taken place, the paths has been traced and " -"changing the work is so obvious that there is no need for you to talk about " -"it; that's because you already did, you already built the trust to keep " -"going. As complement, the mailing list mentioned above is available for " -"sharing ideas in a way that good relationship between community citizens " -"could be constantly balanced." +"As a good cooperating citizen one understand of a person who " +"respects the work already done by others and share ideas with " +"authors before changing relevant parts of their work, specially in " +"situations when the access required to realize the changes has been " +"granted already. Of course, there is a time when conversation has " +"taken place, the paths has been traced and changing the work is so " +"obvious that there is no need for you to talk about it; that's " +"because you already did, you already built the trust to keep going. " +"As complement, the mailing list mentioned above is available for " +"sharing ideas in a way that good relationship between community " +"citizens could be constantly balanced." msgstr "" msgid "" -"The relationship between community citizens is monitored by repository " -"administrators. Repository administrators are responsible of granting that " -"everything goes the way it needs to go in order for The CentOS Artwork " -"Repository to accomplish its mission (see )." +"The relationship between community citizens is monitored by " +"repository administrators. Repository administrators are " +"responsible of granting that everything goes the way it needs to go " +"in order for The CentOS Artwork Repository to " +"accomplish its mission (see )." msgstr "" msgid "Repository Authoring" msgstr "" msgid "" -"The content produced inside The CentOS Artwork Repository is copyright " -"of The CentOS Project. This is something you, as author, should be aware of because you are " -"contributing your creation's rights to someone else; The CentOS Project in this case. This " -"way, your work is distributed using The CentOS Project as copyright holder, not " -"your name (even you remain as natural author of the work). Because The CentOS Project is " -"the copyright holder, is the license chosen by The CentOS Project the one applied to your " -"work, so it is the one you need to agree with before making a creation " -"inside The CentOS Artwork Repository is copyright of The CentOS Project. This is something you, as author, " +"should be aware of because you are contributing your creation's " +"rights to someone else; The CentOS Project in this case. This way, " +"your work is distributed using The CentOS Project as " +"copyright holder, not your name (even you remain as natural author " +"of the work). Because The CentOS Project is the copyright holder, is the " +"license chosen by The CentOS Project the one applied to your work, so it " +"is the one you need to agree with before making a creation inside " +"The CentOS Artwork Repository." msgstr "" msgid "" -"The CentOS Project is a community project controlled by its own community of users. " -"Inside the community, The CentOS Administrators group is the higher " -"authority and the only one able to set core desition like the kind of " -"license used inside the project and subprojects like The CentOS Artwork " -"Repository." +"The CentOS " +"Project is a community project controlled by its own " +"community of users. Inside the community, The CentOS Administrators " +"group is the higher authority and the only one able to set core " +"desition like the kind of license used inside the project and " +"subprojects like The CentOS Artwork Repository." msgstr "" msgid "" -"The redistribution conditions of The CentOS Artwork Repository are " -"described in ." +"The redistribution conditions of The CentOS Artwork " +"Repository are described in ." msgstr "" msgid "Repository Copying Conditions" msgstr "" msgid "" -"The CentOS Project uses The CentOS Artwork Repository to produce The CentOS Project corporate visual " -"identity." +"The CentOS " +"Project uses The CentOS Artwork Repository to " +"produce The " +"CentOS Project corporate visual identity." msgstr "" msgid "" -"The The CentOS Artwork Repository is not in the public domain; it is " -"copyrighted and there are restrictions on their distribution, but these " -"restrictions are designed to permit everything that a good cooperating " -"citizen would want to do. What is not allowed is to try to prevent others " -"from further sharing any version of this work that they might get from you." +"The The CentOS Artwork Repository is not in the " +"public domain; it is copyrighted and there are restrictions on " +"their distribution, but these restrictions are designed to permit " +"everything that a good cooperating citizen would want to do. What " +"is not allowed is to try to prevent others from further sharing any " +"version of this work that they might get from you." msgstr "" msgid "" -"Specifically, we want to make sure that you have the right to give away " -"copies of The CentOS Artwork Repository, that you receive source code or " -"else can get it if you want it, that you can change this work or use pieces " -"of it in new free works, and that you know you can do these things." +"Specifically, we want to make sure that you have the right to give " +"away copies of The CentOS Artwork Repository, that you " +"receive source code or else can get it if you want it, that you can " +"change this work or use pieces of it in new free works, and that " +"you know you can do these things." msgstr "" msgid "" -"To make sure that everyone has such rights, we have to forbid you to deprive " -"anyone else of these rights. For example, if you distribute copies of the " -"The " -"CentOS Artwork Repository, you must give the recipients all the " -"rights that you have. You must make sure that they, too, receive or can get " -"the source code. And you must tell them their rights." +"To make sure that everyone has such rights, we have to forbid you " +"to deprive anyone else of these rights. For example, if you " +"distribute copies of the The CentOS Artwork Repository, you must give the recipients all the rights that you have. " +"You must make sure that they, too, receive or can get the source " +"code. And you must tell them their rights." msgstr "" msgid "" -"Also, for our own protection, we must make certain that everyone finds out " -"that there is no warranty for the The CentOS Artwork Repository. If " -"this work is modified by someone else and passed on, we want their " -"recipients to know that what they have is not what we distributed, so that " -"any problems introduced by others will not reflect on our reputation." +"Also, for our own protection, we must make certain that everyone " +"finds out that there is no warranty for the The CentOS Artwork " +"Repository. If this work is modified by someone else and " +"passed on, we want their recipients to know that what they have is " +"not what we distributed, so that any problems introduced by others " +"will not reflect on our reputation." msgstr "" msgid "" -"The The CentOS Artwork Repository is released as a GPL work. " -"Individual packages used by The CentOS Artwork Repository include their " -"own licenses and the The CentOS Artwork Repository license applies to all " -"packages that it does not clash with. If there is a clash between the The CentOS " -"Artwork Repository license and individual package licenses, the " -"individual package license applies instead." +"The The CentOS Artwork Repository is released as a " +"GPL work. Individual packages used by The CentOS Artwork " +"Repository include their own licenses and the The " +"CentOS Artwork Repository license applies to all packages " +"that it does not clash with. If there is a clash between the The " +"CentOS Artwork Repository license and individual package " +"licenses, the individual package license applies instead." msgstr "" msgid "" -"The precise conditions of the license for the The CentOS Artwork Repository are found in . This manual " -"specifically is covered by the conditions found in ." +"The precise conditions of the license for the The CentOS Artwork " +"Repository are found in . " +"This manual specifically is covered by the conditions found in " +"." msgstr "" msgid "Preparing Your Workstation" @@ -955,28 +1167,30 @@ msgid "Introduction" msgstr "" msgid "" -"The workstation is the machine you use to store your working copy of The CentOS " -"Artwork Repository. The working copy is an ordinary directory tree " -"on your workstation, containing a collection of files that you can edit " -"however you wish. The working copy is your own private work area related to " -"The " -"CentOS Artwork Repository where you perform changes and receive " -"changes from others." +"The workstation is the machine you use to store your working copy " +"of The CentOS Artwork Repository. The working copy " +"is an ordinary directory tree on your workstation, containing a " +"collection of files that you can edit however you wish. The working " +"copy is your own private work area related to The CentOS Artwork " +"Repository where you perform changes and receive changes " +"from others." msgstr "" msgid "" -"In order to make your workstation completely functional, it is necessary " -"that you install it and configure it to satisfy the needs demanded by the " -"working copy of The CentOS Artwork Repository you later download in it." +"In order to make your workstation completely functional, it is " +"necessary that you install it and configure it to satisfy the needs " +"demanded by the working copy of The CentOS Artwork Repository you later download in it." msgstr "" msgid "" -"This chapter describes the steps you need to follow in order to install and " -"configure a workstation for using a working copy of The CentOS Artwork " -"Repository in all its extention." +"This chapter describes the steps you need to follow in order to " +"install and configure a workstation for using a working copy of " +"The CentOS Artwork Repository in all its extention." msgstr "" msgid "Installing Your Workstation" @@ -984,21 +1198,22 @@ msgstr "" msgid "" "To install your workstation use The CentOS Distribution default " -"configuration as proposed by The CentOS Distribution installer. This " -"includes default partitioning and packages. The CentOS Artwork Repository is been completly develop upon The CentOS Distribution and realies on " -"such environment to achieve most automation tasks. In order to get a " -"reproducable environment, it is convenient that you, too, use the same " -"operating system that we do." +"configuration as proposed by The CentOS Distribution installer. " +"This includes default partitioning and packages. The CentOS " +"Artwork Repository is been completly develop upon The " +"CentOS Distribution and realies on such environment to achieve most " +"automation tasks. In order to get a reproducable environment, it is " +"convenient that you, too, use the same operating system that we do." msgstr "" msgid "Supported Platforms" msgstr "" msgid "" -"The " -"CentOS Artwork Repository has been tested in the following platforms:" +"The CentOS Artwork Repository has been tested in the " +"following platforms:" msgstr "" msgid "" @@ -1007,226 +1222,244 @@ msgid "" msgstr "" msgid "" -"In case you be using a working copy of The CentOS Artwork Repository in a " -"different platform from those listed here, please send a mail to centos-devel@centos.org notifying " -"it. It is our intention to make The CentOS Artwork Repository as portable " -"as possible through different major releases of The CentOS Distribution." +"In case you be using a working copy of The CentOS Artwork " +"Repository in a different platform from those listed here, " +"please send a mail to centos-devel@centos.org notifying it. It is our " +"intention to make The CentOS Artwork Repository as " +"portable as possible through different major releases of The CentOS " +"Distribution." msgstr "" msgid "Configuring Your Workstation" msgstr "" msgid "" -"Once your workstation has been installed, it is time for you to configure " -"it. The configuration of your workstation consists on defining your " -"workplace, download a working copy from The CentOS Artwork Repository and " -"finally, run the prepare functionality of " -"centos-art.sh script to install/update the software " -"needed, render images, create links, and anything else needed." +"Once your workstation has been installed, it is time for you to " +"configure it. The configuration of your workstation consists on " +"defining your workplace, download a working copy from The " +"CentOS Artwork Repository and finally, run the " +"prepare functionality of centos-art." +"sh script to install/update the software needed, render " +"images, create links, and anything else needed." msgstr "" msgid "Define Your Workplace" msgstr "" msgid "" -"Once you've installed the workstation and it is up and running, you need to " -"register the user name you'll use for working. In this task you need to use " -"the commands useradd and passwd to " -"create the user name and set a password for it, respectively. These commands " -"require administrative privileges to be executed, so you need to login as " +"Once you've installed the workstation and it is up and running, you " +"need to register the user name you'll use for working. In this task " +"you need to use the commands useradd and " +"passwd to create the user name and set a " +"password for it, respectively. These commands require " +"administrative privileges to be executed, so you need to login as " "root superuser for doing so." msgstr "" msgid "" -"Do not use the root username for regular tasks inside your " -"working copy of The CentOS Artwork Repository. This is dangerous and might " -"provoke unreversable damages to your workstation." +"Do not use the root username for regular tasks " +"inside your working copy of The CentOS Artwork Repository. This is dangerous and might provoke unreversable damages to " +"your workstation." msgstr "" msgid "" -"When you've registered your user name in the workstation, it provides an " -"identifier for you to open a user's session in the workstation and a place " -"to store the information you produce, as well. This place is known as your " -"home directory and is unique for each user registered in the workstation. " -"For example, if you register the user name john in your workstation, your " -"home directory would be located at /home/john/" -"." +"When you've registered your user name in the workstation, it " +"provides an identifier for you to open a user's session in the " +"workstation and a place to store the information you produce, as " +"well. This place is known as your home directory and is unique for " +"each user registered in the workstation. For example, if you " +"register the user name john in your workstation, your home " +"directory would be located at /home/" +"john/." msgstr "" msgid "" -"At this point it is important to define where to download the working copy " -"of The " -"CentOS Artwork Repository inside your home directory. This desition " -"deserves special attention and should be implemented carefully in order to " -"grant a standard environment that could be distributed. Let's see some " -"alternatives." +"At this point it is important to define where to download the " +"working copy of The CentOS Artwork Repository inside your " +"home directory. This desition deserves special attention and should " +"be implemented carefully in order to grant a standard environment " +"that could be distributed. Let's see some alternatives." msgstr "" msgid "Different absolute paths" msgstr "" msgid "" -"Consider that you store your working copy under /home/john/Projects/artwork/ and I store mine under /home/al/Projects/artwork/, we'll end up " -"refering the same files inside our working copies through different absolute " -"paths. This alternative generates a contradiction when files which hold path " -"information inside are committed up to the central repository from different " -"working copies. The contradiction comes from the question: which is the " -"correct absolute path to use inside such files, yours or mine? (None of them " -"is, of course.)" +"Consider that you store your working copy under /home/john/Projects/artwork/ and I store " +"mine under /home/al/Projects/artwork/" +", we'll end up refering the same files inside our " +"working copies through different absolute paths. This alternative " +"generates a contradiction when files which hold path information " +"inside are committed up to the central repository from different " +"working copies. The contradiction comes from the question: which is " +"the correct absolute path to use inside such files, yours or mine? " +"(None of them is, of course.)" msgstr "" msgid "One unique absolute path" msgstr "" msgid "" -"Another case would be that where you and I ourselves use one unique home " -"directory (e.g., /home/centos/Projects/artwork/" -") to store the working copy of The CentOS Artwork Repository in our own workstations, but configure the subversion client to use " -"different user names to commit changes up from the working copy to the " -"central repository. This alternative might be not so good in situations " -"where you and I have to share the same workstation. In such cases, it would " -"be required that we both share the password information of the same system " -"user (the centos user in our example) which, in addition, " -"gives access to that user's subversion client configuration and this way " -"provokes the whole sense of using different subversion credentials for " -"committing changes to be lost." +"Another case would be that where you and I ourselves use one unique " +"home directory (e.g., /home/centos/" +"Projects/artwork/) to store the working copy of The " +"CentOS Artwork Repository in our own workstations, but " +"configure the subversion client to use different user names to " +"commit changes up from the working copy to the central repository. " +"This alternative might be not so good in situations where you and I " +"have to share the same workstation. In such cases, it would be " +"required that we both share the password information of the same " +"system user (the centos user in our example) which, " +"in addition, gives access to that user's subversion client " +"configuration and this way provokes the whole sense of using " +"different subversion credentials for committing changes to be lost." msgstr "" msgid "Different absolute paths through dynamic expansion" msgstr "" msgid "" -"Most of the absolute paths we use inside the working copy are made of two " -"parts, one dynamic and one relative fixed. The dynamic part is the home " -"directory of the current user and its value can be retrived from the " -"$HOME environment variable. The fixed part of the path is the one we " -"set inside the repositroy structure itself as a matter of organization. What " -"we need here is to find a way to expand variables inside files that don't " -"support variable expansion. This alternative had worked rather fine when we " -"produce produce PNG files from SVG files and XTHML from DocBook files, but " -"the same is not true for absolute paths inside files that are used as in " -"their permanent state inside the repository (e.g., CSS files and other files " -"similar in purpose)." -msgstr "" - -msgid "" -"Different absolute paths, dynamic expansion, symbolic links, relative links, " -"and environment variables" -msgstr "" - -msgid "" -"With this solution it is possible to store working copies of The CentOS Artwork " -"Repository on different locations inside the same workstation " -"without lose relation between files. Here we use the TCAR_WORKDIR " -"environment variable to set the location of the working copy inside the " -"workstation. Later the centos-art.sh scripts uses this value as reference to " -"determine where the working copy is. This value is also the one used for " -"dynamic expansion inside design models and other similar files. In the case " -"of web projects where different components are required to produce the final " -"content, we create symbolic links between them and use relative paths so it " -"is possible to reuse them and retain the relation between them in different " -"contexts." -msgstr "" - -msgid "" -"For example, lets consider the organization of XHTML manuals rendered from " -"DocBook source files. When you render a DocBook manual inside The CentOS Artwork " -"Repository it creates XHTML files. This XHTML files use images and " -"common style sheets for better presentation. Both of these images and styles " -"components live outside the XHTML structure so, in order to make them " -"available relatively to the XHTML structure, we created symbolic links from " -"the XHTML structure to the outside location where they are in. The creation " -"of symbolic links takes place automatically when each DockBook manual is " -"rendered through centos-art.sh, which uses the value of " -"TCAR_WORKDIR environment variable as reference to determine the absolute " -"path of the working copy." +"Most of the absolute paths we use inside the working copy are made " +"of two parts, one dynamic and one relative fixed. The dynamic part " +"is the home directory of the current user and its value can be " +"retrived from the $HOME environment variable. The " +"fixed part of the path is the one we set inside the repositroy " +"structure itself as a matter of organization. What we need here is " +"to find a way to expand variables inside files that don't support " +"variable expansion. This alternative had worked rather fine when we " +"produce produce PNG files from SVG files and XTHML from DocBook " +"files, but the same is not true for absolute paths inside files " +"that are used as in their permanent state inside the repository (e." +"g., CSS files and other files similar in purpose)." +msgstr "" + +msgid "" +"Different absolute paths, dynamic expansion, symbolic links, " +"relative links, and environment variables" +msgstr "" + +msgid "" +"With this solution it is possible to store working copies of The " +"CentOS Artwork Repository on different locations inside the " +"same workstation without lose relation between files. Here we use " +"the TCAR_WORKDIR environment variable to set the location of the " +"working copy inside the workstation. Later the centos-art.sh " +"scripts uses this value as reference to determine where the working " +"copy is. This value is also the one used for dynamic expansion " +"inside design models and other similar files. In the case of web " +"projects where different components are required to produce the " +"final content, we create symbolic links between them and use " +"relative paths so it is possible to reuse them and retain the " +"relation between them in different contexts." +msgstr "" + +msgid "" +"For example, lets consider the organization of XHTML manuals " +"rendered from DocBook source files. When you render a DocBook " +"manual inside The CentOS Artwork Repository it creates " +"XHTML files. This XHTML files use images and common style sheets " +"for better presentation. Both of these images and styles components " +"live outside the XHTML structure so, in order to make them " +"available relatively to the XHTML structure, we created symbolic " +"links from the XHTML structure to the outside location where they " +"are in. The creation of symbolic links takes place automatically " +"when each DockBook manual is rendered through centos-art." +"sh, which uses the value of TCAR_WORKDIR environment " +"variable as reference to determine the absolute path of the working " +"copy." msgstr "" msgid "" -"Bacause absolute paths are no longer stored inside permanent files and " -"centos-art.sh script uses the TCAR_WORKDIR environment " -"variable to determine where the working copy is stored in the workstation, " -"it should be safe to download working copies of The CentOS Artwork Repository anywhere in the workstation. One just have to be sure that the value " -"of TCAR_WORKDIR environment variable does match the location of the working " -"copy you are using." +"Bacause absolute paths are no longer stored inside permanent files " +"and centos-art.sh script uses the TCAR_WORKDIR " +"environment variable to determine where the working copy is stored " +"in the workstation, it should be safe to download working copies of " +"The CentOS Artwork Repository anywhere in the " +"workstation. One just have to be sure that the value of " +"TCAR_WORKDIR environment variable does match the location of the " +"working copy you are using." msgstr "" msgid "Download Your Working Copy" msgstr "" msgid "" -"In order to use The CentOS Artwork Repository you need to download a " -"working copy from the central repository into your workstation. To download " -"such working copy use the following command:" +"In order to use The CentOS Artwork Repository you need to " +"download a working copy from the central repository into your " +"workstation. To download such working copy use the following " +"command:" msgstr "" #, no-wrap -msgid "svn co https://projects.centos.org/svn/artwork ~/" +msgid "git clone https://projects.centos.org/~al/artwork.git" msgstr "" msgid "" -"This command will create your working copy inside your home directory, " -"specifically in a directory named artwork. Inside this directory you will find all the files you need to " -"work with inside The CentOS Artwork Repository. If you want to have your " -"working copy in a location different to that one shown above, see artwork.git. Inside this directory you " +"will find all the files you need to work with inside The " +"CentOS Artwork Repository. If you want to have your working " +"copy in a location different to that one shown above, see ." msgstr "" msgid "" -"The first time you download the working copy it contains no image files, nor " -"documentation, or localized content inside it. This is because all the files " -"provided in the working copy are source files (e.g., the files needed to " -"produce other files) and it is up to you to render them in order to produce " -"the final files (e.g., images and documentation) used to implement The CentOS Project " -"Corporate Visual Identity." +"The first time you download the working copy it contains no image " +"files, nor documentation, or localized content inside it. This is " +"because all the files provided in the working copy are source files " +"(e.g., the files needed to produce other files) and it is up to you " +"to render them in order to produce the final files (e.g., images " +"and documentation) used to implement The CentOS Project Corporate " +"Visual Identity." msgstr "" msgid "Configure Administrative Tasks" msgstr "" msgid "" -"Most of the administrative tasks you need to perform in your working copy of " -"The " -"CentOS Artwork Repository are standardized inside the " -"prepare functionality of centos-art.sh script. Inside centos-art.sh script, all " -"administrative task are invoked through the sudo command. " -"Thus, in order for the centos-art.sh script to perform " -"administrative tasks, you need to update the sudo's " +"Most of the administrative tasks you need to perform in your " +"working copy of The CentOS Artwork Repository are " +"standardized inside the prepare functionality " +"of centos-art.sh script. Inside centos-" +"art.sh script, all administrative task are invoked " +"through the sudo command. Thus, in order for the " +"centos-art.sh script to perform administrative " +"tasks, you need to update the sudo's " "configuration in a way that such administrative actions be allowed." msgstr "" msgid "" "At time of this writing the centos-art.sh script " -"implements just one administrative task, that is package management. " -"Nevertheless, in the future, other administrative tasks might be included as " -"well (e.g., installing themes locally from the working copy for testing " -"purposes.)." +"implements just one administrative task, that is package " +"management. Nevertheless, in the future, other administrative tasks " +"might be included as well (e.g., installing themes locally from the " +"working copy for testing purposes.)." msgstr "" msgid "" "To update the sudo's configuration, execute the " -"visudo command as root. Later, uncoment " -"the Cmnd_Alias related to SOFTWARE and add " -"a line for your username allowing software commands. This configuration is " -"illustrated in ." +"visudo command as root. Later, " +"uncoment the Cmnd_Alias related to " +"SOFTWARE and add a line for your username allowing " +"software commands. This configuration is illustrated in ." msgstr "" msgid "The /etc/sudoers configuration file" @@ -1262,263 +1495,281 @@ msgid "Run Preparation Tool" msgstr "" msgid "" -"Once you've both downloaded a working copy from The CentOS Artwork Repository and configured the sudo's configuration file " -"successfully, run the prepare functionality of " -"centos-art.sh script to complete the configuration " -"process using the following command:" +"Once you've both downloaded a working copy from The CentOS " +"Artwork Repository and configured the sudo's configuration file successfully, run the " +"prepare functionality of centos-art." +"sh script to complete the configuration process using the " +"following command:" msgstr "" #, no-wrap -msgid "~/artwork/trunk/Scripts/Bash/centos-art.sh prepare" +msgid "~/artwork/Scripts/Bash/centos-art.sh prepare" msgstr "" msgid "" -"To know more about the prepare functionality of " -"centos-art.sh script, see ." +"To know more about the prepare functionality " +"of centos-art.sh script, see ." msgstr "" msgid "Changing Your Working Copy Default Path" msgstr "" msgid "" -"By default your working copy should be store in your home directory, " -"specifically in the location ~/artwork. This location may not be the final location where you want to " -"have your working copy in situations where you are working on several " -"projects at the same time or you already have a define location to organize " -"your projects inside your home directory. Thus, you may need to change the " -"default location of your working copy to a more appropriate location." +"By default your working copy should be store in your home " +"directory, specifically in the location ~/artwork. This location may not be the final " +"location where you want to have your working copy in situations " +"where you are working on several projects at the same time or you " +"already have a define location to organize your projects inside " +"your home directory. Thus, you may need to change the default " +"location of your working copy to a more appropriate location." msgstr "" msgid "" "The default path to your working copy is controlled by the " -"TCAR_WORKDIR environment variable. This variable is firstly " -"defined in your personal profile after running the prepare functionality of " -"centos-art.sh script. So, to change the path of your " -"working copy correctly, do the following:" +"TCAR_WORKDIR environment variable. This variable is " +"firstly defined in your personal profile after running the prepare " +"functionality of centos-art.sh script. So, to " +"change the path of your working copy correctly, do the following:" msgstr "" msgid "" -"Create the parent directory you will use to store your working copy. For " -"example: mkdir -p ~/Projects/CentOS" +"Create the parent directory you will use to store your working " +"copy. For example: mkdir -p ~/Projects/CentOS" msgstr "" msgid "" -"Move the currently downloaded working copy from ~/artwork to your new " -"location. For example: mv ~/artwork ~/Projects/CentOS/" +"Move the currently downloaded working copy from ~/artwork to your " +"new location. For example: mv ~/artwork ~/Projects/CentOS/" msgstr "" msgid "" -"Edit ~/.bash_profile file to set the new location " -"(without trailing slash) of your working copy as value of TCAR_WORKDIR " -"environment variable. For example: TCAR_WORKDIR=${HOME}/Projects/" -"CentOS/artwork" +"Update the environment variables set in ~/.bash_profile by running the centos-art.sh script " +"from the new location. For example: ~/Projects/CentOS/" +"artwork/Scripts/Bash/centos-art.sh prepare --set-environment" msgstr "" msgid "" -"Do log out from your active user's seesion and do log in again so the " -"environment changes take effect. Or just update the current environment " -"information by running the following command: . ~/.bash_profile" +"Do log out from your active user's seesion and do log in again so " +"the environment changes take effect. Or just update the current " +"environment information by running the following command: . " +"~/.bash_profile" msgstr "" msgid "" -"Update internal links by running the following command: " -"${TCAR_WORKDIR}/trunk/Scripts/Bash/centos-art.sh prepare --links" +"Update internal links by running the centos-art.sh script. For example: ${TCAR_WORKDIR}/Scripts/Bash/" +"centos-art.sh prepare --links" msgstr "" msgid "Repository History" msgstr "" msgid "" -"This chapter summarizes relevant changes committed to The CentOS Artwork " -"Repository along the years." +"This chapter summarizes relevant changes committed to The " +"CentOS Artwork Repository along the years." msgstr "" msgid "2008's" msgstr "" msgid "" -"The " -"CentOS Artwork Repository started at The CentOS Developers Mailing List around 2008, " -"on a discussion about how to automate slide images used by Anaconda (The " -"CentOS Distribution installer). In such discussion, Ralph Angenendt rose up his hand to ask —" +"The CentOS Artwork Repository started at The CentOS Developers Mailing " +"List around 2008, on a discussion about how to automate " +"slide images used by Anaconda (The CentOS Distribution installer). " +"In such discussion, Ralph Angenendt rose up his hand to ask —" "Do you have something to show?—." msgstr "" msgid "" "To answer the question, Alain Reguera Delgado suggested a bash script " -"which combined SVG and SED files in order to produce PNG images in different " -"languages —in conjunction with the proposition of creating a Subversion " -"repository where translations and image production could be distributed " -"inside The CentOS Community—." -msgstr "" - -msgid "" -"Karanbir Singh " -"considered the idea intresting and provided the infrastructure necessary to " -"support the effort. This way, The CentOS Artwork SIG and The CentOS Artwork " -"Repository were officially created and made world wide available. In " +"AlainRegueraDelgado\">Alain Reguera Delgado suggested a " +"bash script which combined SVG and SED files in order to produce " +"PNG images in different languages —in conjunction with the " +"proposition of creating a Subversion repository where translations " +"and image production could be distributed inside The CentOS " +"Community—." +msgstr "" + +msgid "" +"Karanbir Singh considered the idea intresting and provided the " +"infrastructure necessary to support the effort. This way, The " +"CentOS Artwork SIG and The CentOS Artwork Repository were officially created and made world wide available. In " "this configuration, users were able to register themselves and " -"administrators were able to assign access rights to registered users inside " -"The " -"CentOS Artwork Repository, both using a web interface." +"administrators were able to assign access rights to registered " +"users inside The CentOS Artwork Repository, both using " +"a web interface." msgstr "" msgid "" -"Once The CentOS Artwork Repository was available, Alain Reguera " -"Delgado uploaded the bash script used to produce the Anaconda slides;" -"See Ralph Angenendt " -"documented it very well;See and people started to download working copies of The CentOS " -"Artwork Repository to produce slide images in their own languages." -"See the following Google search." +"Once The CentOS Artwork Repository was available, " +"Alain Reguera Delgado uploaded the bash script used to produce the " +"Anaconda slides;See Ralph Angenendt documented it very well;" +"See and people started to download working copies of The " +"CentOS Artwork Repository to produce slide images in their " +"own languages.See the following Google search." msgstr "" msgid "" -"From this time on The CentOS Artwork Repository has been evolving into " -"an automated production environment where The CentOS Community can conceive " -"The CentOS Project corporate visual identity." +"From this time on The CentOS Artwork Repository has " +"been evolving into an automated production environment where The " +"CentOS Community can conceive The CentOS Project corporate visual identity." msgstr "" msgid "" -"The exact changes commited to The CentOS Artwork Repository through " -"history can be found in the repository logs so you can know the real history " -"about it. For those of you who just want to get a glance of changes " -"committed, see ." +"The exact changes commited to The CentOS Artwork Repository through history can be found in the repository logs " +"so you can know the real history about it. For those of you who " +"just want to get a glance of changes committed, see ." msgstr "" msgid "2009's" msgstr "" msgid "" -"Around 2009, the rendition script was at a very rustic state where only " -"slide images could be produced, so it was redesigned to extend the image " -"production to other areas, different from slide images. In this " -"configuration, one SVG file was used as input to produce a translated " -"instance of it which, in turn, was used to produce one translated PNG image " -"as output. The SVG translated instance was created through SED replacement " -"commands. The translated PNG image was created from the SVG translated " -"instance using Inkscape command-line interface." +"Around 2009, the rendition script was at a very rustic state where " +"only slide images could be produced, so it was redesigned to extend " +"the image production to other areas, different from slide images. " +"In this configuration, one SVG file was used as input to produce a " +"translated instance of it which, in turn, was used to produce one " +"translated PNG image as output. The SVG translated instance was " +"created through SED replacement commands. The translated PNG image " +"was created from the SVG translated instance using Inkscape command-" +"line interface." msgstr "" msgid "" -"The repository directory structure was prepared to receive the rendition " -"script using design templates and translation files in the same location. " -"There was one directory structure for each art work that needed to be " -"produced. In this configuration, if you would want to produce the same art " -"work with a different visual style or structure, it was needed to create a " -"new directory structure for it because both the image structure and the " -"image visual style were together in the design template." +"The repository directory structure was prepared to receive the " +"rendition script using design templates and translation files in " +"the same location. There was one directory structure for each art " +"work that needed to be produced. In this configuration, if you " +"would want to produce the same art work with a different visual " +"style or structure, it was needed to create a new directory " +"structure for it because both the image structure and the image " +"visual style were together in the design template." msgstr "" msgid "" -"The rendition script was moved to a common place and linked from different " -"directory structures. There was no need to have the same code in different " -"directory structures if it could be in just one place and then be linked " -"from different locations." +"The rendition script was moved to a common place and linked from " +"different directory structures. There was no need to have the same " +"code in different directory structures if it could be in just one " +"place and then be linked from different locations." msgstr "" msgid "" -"Corporate identity concepts began to be considered. As referece, it was used " -"the book \"Corporate Identity\" by Wally Olins (1989) and Wikipedia related links. This way, the rendition script main's goal becomes to: " -"automate the production process of a monolithic corporate visual " -"identity structure, based on the mission and the release schema of The " -"CentOS Project." +"Corporate identity concepts began to be considered. As referece, it " +"was used the book \"Corporate Identity\" by Wally Olins (1989) and " +"Wikipedia " +"related links. This way, the rendition script main's goal " +"becomes to: automate the production process of a " +"monolithic corporate visual identity structure, based on the " +"mission and the release schema of The CentOS Project." msgstr "" msgid "" -"The repository directory structures began to be documented by mean of flat " -"text files. Later, documentation in flat text files was moved onto LaTeX " -"format and this way The CentOS Artwork Repository User's Guide was initiated." +"The repository directory structures began to be documented by mean " +"of flat text files. Later, documentation in flat text files was " +"moved onto LaTeX format and this way The CentOS Artwork " +"Repository User's Guide was initiated." msgstr "" msgid "2010's" msgstr "" msgid "" -"Around 2010, the rendition script changed its name from render.sh to centos-art.sh and became a collection of " -"functionalities where rendition was just one among others (e.g., " -"documentation and localization)." +"Around 2010, the rendition script changed its name from " +"render.sh to centos-art.sh " +"and became a collection of functionalities where rendition was just " +"one among others (e.g., documentation and localization)." msgstr "" msgid "" -"The centos-art.sh was initially conceived to automate " -"frequent tasks inside the repository based in the idea of Unix toolbox: to " -"create small and specialized tools that do one thing well. This way, " -"functionalities inside centos-art.sh began to be " -"identified and separated one another. For example, when images were " -"rendered, there was no need to load functionalities related to documentation " -"manual. This layout moved us onto common functionalities and " -"specific functionalities inside centos-art.sh script. Common functionalities are loaded when centos-art." +"The centos-art.sh was initially conceived to " +"automate frequent tasks inside the repository based in the idea of " +"Unix toolbox: to create small and specialized tools that do one " +"thing well. This way, functionalities inside centos-art." +"sh began to be identified and separated one another. For " +"example, when images were rendered, there was no need to load " +"functionalities related to documentation manual. This layout moved " +"us onto common functionalities and specific " +"functionalities inside centos-art.sh " +"script. Common functionalities are loaded when centos-art." "sh script is initiated and are available to specific " "functionalities." msgstr "" msgid "" -"Suddenly, no need was found to keep all the links spreaded around the " -"repository in order to execute the centos-art.sh script " -"from different locations. The centos-art command-line " -"interface was used instead. The centos-art command-line " -"interface is a symbolic link stored inside the ~/bin directory pointing to centos-art.sh " -"script. As default configuration, inside The CentOS Distribution, the path " -"to ~/bin is included in the search " -"path for commands (see PATH environment variable). This way, " -"using the centos-art command-line interface, it is " -"possible to execute the centos-art.sh script from " -"virtually anywhere inside the workstation, just as we frequently do with " -"regular commands." +"Suddenly, no need was found to keep all the links spreaded around " +"the repository in order to execute the centos-art.sh script from different locations. The centos-art command-line interface was used instead. The " +"centos-art command-line interface is a symbolic " +"link stored inside the ~/bin directory pointing to centos-art.sh " +"script. As default configuration, inside The CentOS Distribution, " +"the path to ~/bin is " +"included in the search path for commands (see PATH " +"environment variable). This way, using the centos-art command-line interface, it is possible to execute the " +"centos-art.sh script from virtually anywhere " +"inside the workstation, just as we frequently do with regular " +"commands." msgstr "" msgid "" -"Start using GNU getopt as default option parser inside the centos-" -"art.sh script." +"Start using GNU getopt as default option parser inside the " +"centos-art.sh script." msgstr "" msgid "" -"The repository directory structure was updated to improve the implementation " -"of corporate visual identity concepts. Specially in the area related to " -"themes. Having both structure and style in the same file introduced content " -"duplication when producing art works. Because of this reason, they were " -"separated into two different directory structures: the design models and the " -"artistic motifs directory structures. From this point on, the " -"centos-art.sh was able to produce themes as result of " -"arbitrary combinations between design models (structure) and artistic motifs " +"The repository directory structure was updated to improve the " +"implementation of corporate visual identity concepts. Specially in " +"the area related to themes. Having both structure and style in the " +"same file introduced content duplication when producing art works. " +"Because of this reason, they were separated into two different " +"directory structures: the design models and the artistic motifs " +"directory structures. From this point on, the centos-art." +"sh was able to produce themes as result of arbitrary " +"combinations between design models (structure) and artistic motifs " "(visual styles)." msgstr "" msgid "" -"In the documentation area, the documents in LaTeX format were migrated to " -"Texinfo format. In this configuration, each directory structure in the " -"repository has a documentation entry associated in a Texinfo structure which " -"can be read, edited and administered (e.g., renamed, deleted and copied) " -"interactively through centos-art.sh script. Additionally, " -"the texi2html program was used to produced customized XHTML output in " +"In the documentation area, the documents in LaTeX format were " +"migrated to Texinfo format. In this configuration, each directory " +"structure in the repository has a documentation entry associated in " +"a Texinfo structure which can be read, edited and administered (e." +"g., renamed, deleted and copied) interactively through " +"centos-art.sh script. Additionally, the " +"texi2html program was used to produced customized XHTML output in " "conjunction with CSS from The CentOS Web." msgstr "" @@ -1526,117 +1777,127 @@ msgid "2011's" msgstr "" msgid "" -"Around 2011, the centos-art.sh script was redesigned to " -"start translating XML-based files (e.g., SVG and Docbook files) through " -"xml2po program and shell scripts (e.g., Bash scripts) " -"through GNU gettext tools. This configuration provided a stronger " -"localization interface for graphic designers, translators and programmers. " -"The SED replacement files are no longer used to handle localization." +"Around 2011, the centos-art.sh script was " +"redesigned to start translating XML-based files (e.g., SVG and " +"Docbook files) through xml2po program and shell " +"scripts (e.g., Bash scripts) through GNU gettext tools. This " +"configuration provided a stronger localization interface for " +"graphic designers, translators and programmers. The SED replacement " +"files are no longer used to handle localization." msgstr "" msgid "" "The render, help and " -"locale functionalities consolidated themselves as the " -"most frequent tasks performed in The CentOS Artwork Repository " -"working copy. Additionally, the prepare and " -"tuneup functionalities were also maintained as useful " -"tasks." +"locale functionalities consolidated themselves " +"as the most frequent tasks performed in The CentOS Artwork " +"Repository working copy. Additionally, the " +"prepare and tuneup " +"functionalities were also maintained as useful tasks." msgstr "" msgid "" -"In the documentation area, it was introduced the transformation of localized " -"DocBook XML DTD instances through the render and " -"locale functionalities. In this configuration, you use " -"locale functionality to localize DocBook source files " -"to your prefered language and later, using the render " -"functionality, you can produce the localized XTHML and PDF output as " -"specified in a XSLT layer. Unfortunly, the transformation DocBook XML -> " -"FO -> PDF (through PassiveTex) seems to be buggy inside CentOS 5.5, so it " -"was commented inside the centos-art.sh script. Most " -"documentation is now organized in DocBook format, even Texinfo format " -"remains as the only format with automated production tasks." +"In the documentation area, it was introduced the transformation of " +"localized DocBook XML DTD instances through the render and locale functionalities. In this " +"configuration, you use locale functionality to " +"localize DocBook source files to your prefered language and later, " +"using the render functionality, you can " +"produce the localized XTHML and PDF output as specified in a XSLT " +"layer. Unfortunly, the transformation DocBook XML -> FO -> " +"PDF (through PassiveTex) seems to be buggy inside CentOS 5.5, so it " +"was commented inside the centos-art.sh script. " +"Most documentation is now organized in DocBook format, even Texinfo " +"format remains as the only format with automated production tasks." msgstr "" msgid "" "In the automation area, the centos-art.sh script " -"introduced the capability of reading configuration files. The main goal here " -"was moving some command-line options from functionalities onto a more " -"persistent medium. Most configuration files were set to define the position " -"of brands inside images and documentation manual specific options." +"introduced the capability of reading configuration files. The main " +"goal here was moving some command-line options from functionalities " +"onto a more persistent medium. Most configuration files were set to " +"define the position of brands inside images and documentation " +"manual specific options." msgstr "" msgid "2012's" msgstr "" msgid "" -"The " -"CentOS Artwork Repository development was eventually stopped at " -"November 2011 until July 2012 when we needed to make the centos-art." -"sh script a bit more customizable than it presently was. For " -"example, it was considered as a need that functionalities inside the " -"centos-art.sh script must be not just conceived " -"independent one another but reusable in different contexts as well." +"The CentOS Artwork Repository development was eventually " +"stopped at November 2011 until July 2012 when we needed to make the " +"centos-art.sh script a bit more customizable " +"than it presently was. For example, it was considered as a need " +"that functionalities inside the centos-art.sh " +"script must be not just conceived independent one another but " +"reusable in different contexts as well." msgstr "" msgid "" -"Make Localization Of centos-art.sh Script Specific To " -"Different Contexts" +"Make Localization Of centos-art.sh Script " +"Specific To Different Contexts" msgstr "" msgid "" -"The procedure used to locale messages inside the centos-art.sh script had to be re-designed in order to accept such pluggable " -"behavior into the script. We couldn't publish unique centos-art.sh." -"po and centos-art.sh.mo files because they " -"may contain different information in different contexts. For example, if you " -"are using the render and help " -"functionalities you only need translation messages for them and not those " -"from other functionalities that may exist in the central repository but you " -"didn't download nor use into your working copy." +"The procedure used to locale messages inside the centos-" +"art.sh script has to be re-designed in order to accept " +"such pluggable behavior into the script. We couldn't publish unique " +"centos-art.sh.po and centos-art.sh." +"mo files because they may contain different information " +"in different contexts. For example, if you are using the " +"render and help " +"functionalities you only need translation messages for them and not " +"those from other functionalities that may exist in the central " +"repository but you didn't download nor use into your working copy." msgstr "" msgid "" -"One solution for this could be to have independent PO files for each " -"functionality of centos-art.sh script which are combined " -"to create the final PO and MO files that gettext " -"uses to retrive translated strings when centos-art.sh " -"script is running. For this solution to be effective, you must be selective " -"about the functionalities and locales directories you download into your " -"working copy. For example, if you want to use the render functionality and " -"its locale messages only, you must download the required directories and " -"exclude others." +"One solution for this could be to have independent PO files for " +"each functionality of centos-art.sh script which " +"are combined to create the final PO and MO files that " +"gettext uses to retrive translated " +"strings when centos-art.sh script is running. " +"For this solution to be effective, you must be selective about the " +"functionalities and locales directories you download into your " +"working copy. For example, if you want to use the render " +"functionality and its locale messages only, you must download the " +"required directories and exclude others." msgstr "" msgid "" -"In case you don't want to be selective and download the whole repository, " -"the creation of the centos-art.sh.po, centos-" -"art.sh.pot and centos-art.sh.mo files will " -"occur automatically the first time you run the prepare " -"functionality (which require the locale functionality " -"to be available), or later, by running the following command: centos-" -"art locale trunk/Scripts/Bash --update" +"In case you don't want to be selective and download the whole " +"repository, the creation of the centos-art.sh.po, centos-art.sh.pot and " +"centos-art.sh.mo files will occur " +"automatically the first time you run the prepare functionality (which require the locale functionality to be available), or later, by running the " +"following command: centos-art locale Scripts/Bash --update" msgstr "" msgid "" "For more information about the prepare and " -"locale functionalities, see and respectively." +"locale functionalities, see and respectively." msgstr "" msgid "" "As shown in , both " "Commons and Locales " -"functionalities will always be required directories. The Commons directory contains the common functionalities and the " -"Locales directory contains the standard procedures you " -"need to run in order to build the final centos-art.sh.mo file used by gettext to retrive " -"translation strings when the centos-art.sh script is " -"running. Remember that centos-art.sh.pot, " -"centos-art.sh.po files aren't under version control and " -"they are built by combining each funtionality message.po file into a PO and " -"later a MO file." +"functionalities will always be required directories. The " +"Commons directory contains the common " +"functionalities and the Locales directory " +"contains the standard procedures you need to run in order to build " +"the final centos-art.sh.mo file used by " +"gettext to retrive translation strings " +"when the centos-art.sh script is running. " +"Remember that centos-art.sh.pot, " +"centos-art.sh.po files aren't under version " +"control and they are built by combining each funtionality message." +"po file into a PO and later a MO file." msgstr "" msgid "Directory structure of a rendering-only context" @@ -1645,7 +1906,7 @@ msgstr "" #, no-wrap msgid "" "\n" -"/home/centos/Projects/artwork/trunk/\n" +"/home/centos/Projects/artwork/\n" "|-- Locales/\n" "| `-- Scripts/\n" "| `-- Bash/\n" @@ -1674,31 +1935,34 @@ msgid "" msgstr "" msgid "" -"A practical example of using the solution described above may be found when " -"you are working on the corporate identity of The CentOS Project and then need to start " -"a new corporate identity project for another organization. You want to keep " -"the directory structure of The CentOS Artwork Repository and its " -"automation tool, the centos-art.sh script. Your new " -"project requires you to introduce new functionalities to centos-art." -"sh which don't fit the needs of The CentOS Project (e.g., you want to introduce a " -"report functionality to mesure how much connect time do " -"you consume through your PPP internface.) or you just want to keep the " -"directory structure of your new project as simple as possible." -msgstr "" - -msgid "" -"To go through this it is possible to mix specific parts of different central " -"repositories into one single working copy. This is the working copy you'll " -"use to manage your new project. In , we see how the Render, " -"Locales and Commons directories which come from the The CentOS Artwork " -"Repository has been integrated into the working copy of your new " -"project." +"A practical example of using the solution described above may be " +"found when you are working on the corporate identity of The CentOS Project " +"and then need to start a new corporate identity project for another " +"organization. You want to keep the directory structure of The " +"CentOS Artwork Repository and its automation tool, the " +"centos-art.sh script. Your new project requires " +"you to introduce new functionalities to centos-art.sh which don't fit the needs of The CentOS Project (e.g., you " +"want to introduce a report functionality to " +"mesure how much connect time do you consume through your PPP " +"internface.) or you just want to keep the directory structure of " +"your new project as simple as possible." +msgstr "" + +msgid "" +"To go through this it is possible to mix specific parts of " +"different central repositories into one single working copy. This " +"is the working copy you'll use to manage your new project. In , we see how the Render, Locales and Commons directories which come from the The CentOS Artwork " +"Repository has been integrated into the working copy of " +"your new project." msgstr "" msgid "Mixing automation functionalities." @@ -1707,7 +1971,7 @@ msgstr "" #, no-wrap msgid "" "\n" -"/home/al/Projects/Myapp/trunk/\n" +"/home/al/Projects/Myapp/\n" "|-- Locales/ \n" "| `-- Scripts/\n" "| `-- Bash/ \n" @@ -1740,81 +2004,375 @@ msgid "" msgstr "" msgid "" -"At this point, your working copy contains files from two different central " -"repositories. One repository provides the files of your new organization " -"project and the other one provides the files related to the " -"render functionality from The CentOS Artwork Repository. In this environment, all updates commited to the Render, Locales and Commons directories " -"at The " -"CentOS Artwork Repository will be available to you too, the next " -"time you update your working copy. Likewise, if you change something in any " -"of these directories and commit your changes, your changes will be available " -"to poeple working in The CentOS Artwork Repository the next time they " -"update their working copies." -msgstr "" - -msgid "" -"Understanding the need of mixing different central repositories into a " -"single working copy is an important step for reusing the functionalities " -"that come with centos-art.sh script, but it is not enough if you want to " -"customize the information produced by it. By default, the centos-art.sh " -"script uses information related to The CentOS Project. You probably need to change this if " -"you are producing images to a different organization than The CentOS Project. For example, " -"some of the information you might need to change would be the copyright " -"holder, brands, domain names, mailing lists, and so forth. To change this " -"information you need to duplicate the file centos-art.sh and rename it to something else. Later, you need to edit the " -"renamed version and change variables inside according your needs. In , we used the name myapp.sh instead of centos-art.sh so the information we " -"set inside it could reflect the specific needs that motivated the creation " -"of a new project without affecting those from render functionality from The " +"CentOS Artwork Repository. In this environment, all updates " +"commited to the Render, " +"Locales and Commons directories at The " +"CentOS Artwork Repository will be available to you too, the " +"next time you update your working copy. Likewise, if you change " +"something in any of these directories and commit your changes, your " +"changes will be available to poeple working in The CentOS " +"Artwork Repository the next time they update their working " +"copies." +msgstr "" + +msgid "" +"Understanding the need of mixing different central repositories " +"into a single working copy is an important step for reusing the " +"functionalities that come with centos-art.sh script, but it is not " +"enough if you want to customize the information produced by it. By " +"default, the centos-art.sh script uses information related to " +"The CentOS " +"Project. You probably need to change this if you are " +"producing images to a different organization than The CentOS Project. For " +"example, some of the information you might need to change would be " +"the copyright holder, brands, domain names, mailing lists, and so " +"forth. To change this information you need to duplicate the file " +"centos-art.sh and rename it to something else. " +"Later, you need to edit the renamed version and change variables " +"inside according your needs. In , we used the name myapp.sh instead of " +"centos-art.sh so the information we set inside " +"it could reflect the specific needs that motivated the creation of " +"a new project without affecting those from The CentOS Project." msgstr "" msgid "" -"Most of the information you need to change in your duplicated version of " -"centos-art.sh file is controlled by a set of read-only " -"variables. You modify these variables here and they will be available all " -"along the script execution time. For example, you can change the value of " -"CLI_WRKCOPY variable inside your duplicated version of " -"centos-art.sh to change the absolute path you use to " -"store your working copy." +"Most of the information you need to change in your duplicated " +"version of centos-art.sh file is controlled by " +"a set of read-only variables. You modify these variables here and " +"they will be available all along the script execution time. For " +"example, you can change the value of CLI_WRKCOPY " +"variable inside your duplicated version of centos-art.sh to change the absolute path you use to store your working " +"copy." msgstr "" -msgid "Update DocBook Documentation Structure And Processing" +msgid "Enhance The CentOS Logo Construction" msgstr "" -msgid "..." +msgid "" +"The CentOS Logo is made of two different components known as The " +"CentOS Symbol and The CentOS Type. Presently (at the end of " +"September), to produce these components, we create one " +"SVG image for each PNG image we want to produce, " +"store it in Identity/Models/Brands/" +"Logos directory structure and run the command:" +msgstr "" + +msgid "centos-art render Identity/Images/Brands/Logos" +msgstr "" + +msgid "" +"This model works and scales well in situations when there isn't a " +"need to reuse final images among themselves. However, when you need " +"to reuse images among themselves, a better solution is required. " +"The goal here would be: don't create SVG images " +"for PNG images you can build based on other PNG images." +msgstr "" + +msgid "This might be achieved through one of the following ways:" +msgstr "" + +msgid "" +"Create a new specific functionality to achieved the goal. Needed " +"because the specific " +"functionality uses SVG files as reference to " +"build images (i.e., one SVG image produces one " +"PNG image)." +msgstr "" + +msgid "" +"Modify functionality to " +"work in different modes based on file type or file extension. The " +"first mode would use SVG files as reference to " +"build PNG images (just as it was doing so far). The second mode " +"would use a configuration file named render.conf as reference inside the design models directory you want " +"to produce images for so as to build the related PNG images. In " +"this second case, the configuration file specifies how final PNG " +"images will be produced (e.g., by appending or overlapping them one " +"another)." +msgstr "" + +msgid "For example, consider the following command-line:" +msgstr "" + +msgid "" +"This command should evaluate which type of rendition will be done, " +"based on whether the source file is a scalable vector graphic " +"(SVG) or a configuration file. To make this " +"decision, the centos-art.sh script looks for " +"SVG files first, and configuration files later. " +"When SVG files are found, the centos-" +"art.sh script uses a list of SVG files " +"and process them one by one excluding any related configuration " +"file that could exist. On the other hand, if no SVG file is found inside the related design model directory " +"structure, the centos-art.sh script will use the " +"configuration file with the name render.conf " +"to create images as specified inside it. When neither a " +"SVG or a configuration file is found inside the " +"design model directory structure, the centos-art.sh script finishes its execution without any error message. " +"For example, if no SVG file is found inside " +"Identity/Models/Brands/Logos/ directory and the Identity/Models/Brands/Logos/" +"images.conf configuration file exists therein with the " +"following content:" +msgstr "" + +#, no-wrap +msgid "" +"\n" +"[centos.png]\n" +"models = \"Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz\"\n" +"formats = \"xpm jpg\"\n" +"heights = \"48 78\"\n" +"fgcolor = \"000000 ffffff\"\n" +"bgcolor = \"ffffff-0\"\n" +"command = \"/usr/bin/convert +append\"\n" +"\n" +"[centos-artwork.png]\n" +"models = \"Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz Identity/Models/Brands/Types/artwork.svgz\"\n" +"formats = \"xpm jpg\"\n" +"heights = \"48 78\"\n" +"fgcolor = \"000000 ffffff\"\n" +"bgcolor = \"ffffff-0\"\n" +"command = \"/usr/bin/convert +append\"\n" +msgstr "" + +msgid "" +"The centos-art.sh script should produce the " +"following image files:" +msgstr "" + +#, no-wrap +msgid "" +"\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.jpg\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.png\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.xpm\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.png\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.jpg\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.xmp\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.jpg\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.png\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.xpm\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.png\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.jpg\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.xmp\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.jpg\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.png\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.xpm\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.png\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.jpg\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.xmp\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.jpg\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.png\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.xpm\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.png\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.jpg\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.xmp\n" +msgstr "" + +msgid "" +"The final location for storing images output inside the repository " +"is determined by using the design model directory provided as " +"argument. Basically, the centos-art.sh script " +"changes the path components from Models to Images and adds " +"foreground color, background color, height value and image name to " +"it to differentiate rendered images." +msgstr "" + +msgid "" +"In case you need to restrict the amount of files you want to " +"produce including their formats, heights, colors and commands, you " +"need to modify the content of the related render.conf configuration file. There is not any command-line option " +"available for such tasks. The most command-line options can do for you " +"is when there are more than one configuration file inside the same " +"design model directory and you need to specify which one of them " +"will be used as reference. In such case you can use the option." +msgstr "" + +msgid "" +"When images are produced through configuration files, the " +"centos-art.sh script takes the order provided in " +"the list of design models to build the list of images you will work " +"with through the command specified. For example, the order in which " +"images will be appended or overlapped." +msgstr "" + +msgid "" +"Localization of logo images will not be and must not be supported " +"in any way. That would bring disastrous confusion in the area of " +"visual recognition." +msgstr "" + +msgid "2013's" +msgstr "" + +msgid "" +"The CentOS Artwork Repository development was eventually " +"stopped at November, 2012, when I moved myself from Cienfuegos to " +"Havana city for working The first months were very difficult, " +"specially at the moment of finding a stable place to set my " +"personal desktop (I was moving myself from one apartment to " +"another, frequently)." +msgstr "" + +msgid "" +"On May 14th, the work in Havana ends for me and I have to return to " +"Cienfuegos city. I tried to take advantage of the situation " +"dedicating more work and study hours to The CentOS Artwork " +"Repository and the related automation scripts once again. " +"At this point I consider a Git+Gitolite+Gitweb+MantisBT " +"infrastructure for The CentOS Artwork Repository and " +"start working on it in my workstation. This, in order to implement " +"a distributed work flow for The CentOS Artwork Repository based on Git version control system." +msgstr "" + +msgid "Update Version Control Environment" +msgstr "" + +msgid "" +"The function environment related to version control tasks was " +"renamed from svn to in order to handle both Subversion and Git working copies of " +"The CentOS Artwork Repository. This change prepares the " +"centos-art.sh script to follow the suggestion of " +"a complete migration from Subversion to " +"Git, at some point." +msgstr "" + +msgid "" +"Because the Subversion infrastructure is " +"the one in place right now and it is the one with most artwork " +"history, it will be Subversion the " +"version control system we are using as default in centos-" +"art.sh. However this will surely change as soon as a " +"Git infrastructure be approved for " +"The CentOS Artwork Repository and everything could be " +"moved there." +msgstr "" + +msgid "Start Using The centos-art.conf File" +msgstr "" + +msgid "" +"Based on the need of supporting more than one application to handle " +"version control tasks, it was added the centos-art.conf file into the Scripts/Bash directory. This file exists to customize specific " +"behaviours of centos-art.sh script once it has " +"been executed (e.g., what kind of application will be used as " +"default for doing version control, or even if the actions related " +"to version control will be performed or not)." +msgstr "" + +msgid "Update Repository Directories Structure" +msgstr "" + +msgid "" +"I face the following situation: I am working on a documentation " +"project named solinfo-network. While I was " +"organizing it, I found that the directory structure of The " +"CentOS Artwork Repository fits quite well the needs of " +"solinfo-network documentation project. However, I " +"don't want to duplicate automation scripts in two separate " +"projects, but share them between themselves (i.e., changes " +"committed to automation scripts are pushed to one single place, not " +"two.)." +msgstr "" + +msgid "" +"When we use Subversion repositories, it is possible to checkout " +"specific parts of different repositories into a new repository. " +"This is very useful if we need to create several projects that " +"share the same component and we don't want to duplicate the common " +"component in two or more different projects but share it between them. See ." +msgstr "" + +msgid "" +"When we use Git repository, it is not possible to checkout specific " +"parts of a repository but the complete tree. So, in order to share " +"common components of a repository we need to create one repository " +"for each common component we want to share and then use Git " +"submodulessee progit-book, page 152. This " +"requires that brand new repositories be created for each component " +"we want to share." +msgstr "" + +msgid "" +"In both situations, including Git and Subversion repositories, it " +"is necessary that we define very well the structure of each " +"component we want to share, so it can be plugged " +"nicely into other projects. Likewise, other projects must have the " +"same directory structure the pluggable component was design to fit " +"in. If these two conditions can be reached, it would be possible to " +"reuse repositories components and concentrate efforts. The current " +"directory structure The CentOS Artwork Repository is " +"set in allows components inside Subversion repositories to be " +"reused by related working copies. However, we cannot do the same if " +"it is stored in a Git repository. In order for Git repositories to " +"be able to share components with other Git repositories, The " +"CentOS Artwork Repository directory structure needs to be " +"reorganized to better delineate each component the repository is " +"made of." +msgstr "" + +msgid "For more information see ." msgstr "" msgid "Corporate Visual Identity" msgstr "" +msgid "..." +msgstr "" + msgid "The CentOS Project" msgstr "" msgid "" -"The CentOS Project Corporate Identity is the persona of the " -"organization known as The CentOS Project. The CentOS Project Corporate " -"Identity plays a significant role in the way The CentOS Project, as " -"organization, presents itself to both internal and external stakeholders. In " -"general terms, The CentOS Project Corporate Identity expresses the values " -"and ambitions of The CentOS Project organization, its business, and its " -"characteristics." +"The CentOS Project Corporate Identity is the persona " +"of the organization known as The CentOS Project. The CentOS Project " +"Corporate Identity plays a significant role in the way The CentOS " +"Project, as organization, presents itself to both internal and " +"external stakeholders. In general terms, The CentOS Project " +"Corporate Identity expresses the values and ambitions of The CentOS " +"Project organization, its business, and its characteristics." msgstr "" msgid "" -"The CentOS Project Corporate Identity provides visibility, recognizability, " -"reputation, structure and identification to The CentOS Project organization " -"by means of Corporate Design, Corporate Communication, and Corporate " -"Behaviour." +"The CentOS Project Corporate Identity provides visibility, " +"recognizability, reputation, structure and identification to The " +"CentOS Project organization by means of Corporate Design, Corporate " +"Communication, and Corporate Behaviour." msgstr "" msgid "The CentOS Project Corporate Identity." @@ -1824,163 +2382,172 @@ msgid "Corporate Mission" msgstr "" msgid "" -"The CentOS Project exists to produce The CentOS Distribution, an Enterprise-class Linux " -"Distribution derived from sources freely provided to the public by a " -"prominent North American Enterprise Linux vendor. The CentOS Distribution " -"conforms fully with the upstream vendors redistribution policy and aims to " -"be 100% binary compatible. (The CentOS Distribution mainly changes packages " -"to remove upstream vendor branding and artwork.)." +"The CentOS " +"Project exists to produce The CentOS Distribution, an " +"Enterprise-class Linux Distribution derived from sources freely " +"provided to the public by a prominent North American Enterprise " +"Linux vendor. The CentOS Distribution conforms fully with the " +"upstream vendors redistribution policy and aims to be 100% binary " +"compatible. (The CentOS Distribution mainly changes packages to " +"remove upstream vendor branding and artwork.)." msgstr "" msgid "" -"The CentOS Distribution is developed by a small but growing team of core " -"developers. In turn the core developers are supported by an active user " -"community including system administrators, network administrators, " -"enterprise users, managers, core Linux contributors and Linux enthusiasts " -"from around the world." +"The CentOS Distribution is developed by a small but growing team of " +"core developers. In turn the core developers are supported by an " +"active user community including system administrators, network " +"administrators, enterprise users, managers, core Linux contributors " +"and Linux enthusiasts from around the world." msgstr "" msgid "" -"The CentOS Distribution has numerous advantages including: an active and " -"growing user community, quickly rebuilt, tested, and QA'ed errata packages, " -"an extensive mirror network, developers who are contactable and responsive " -"of a reliable Enterprise-class Linux Distribution, multiple free support " -"avenues including a Wiki, IRC Chat, Email Lists, Forums, and a dynamic " -"FAQ." +"The CentOS Distribution has numerous advantages including: an " +"active and growing user community, quickly rebuilt, tested, and " +"QA'ed errata packages, an extensive mirror network, developers who " +"are contactable and responsive of a reliable Enterprise-class Linux " +"Distribution, multiple free support avenues including a Wiki, IRC Chat, Email Lists, Forums, and a " +"dynamic FAQ." msgstr "" msgid "Corporate Graphic Design" msgstr "" msgid "" -"The corporate design is focused on the effective presentation of corporate " -"messages. As corporate messages we understand all the information emitted " -"from the organization; and when we say all we mean " -"everything that can be perceived through the human senses. The corporate " -"design takes care of defining what this information is and controlling the " -"way it goes out the organization producing it." +"The corporate design is focused on the effective presentation of " +"corporate messages. As corporate messages we understand all the " +"information emitted from the organization; and when we say " +"all we mean everything that can be perceived " +"through the human senses. The corporate design takes care of " +"defining what this information is and controlling the way it goes " +"out the organization producing it." msgstr "" msgid "" -"When the organization doesn't take control over the corporate messages it " -"produces, the organization is letting that area of its identity to the " -"unknown and the results might be good or not so good, it is hard to know. " -"The issue to see here is that even the organization doesn't take control " -"over its corporate messages, they are always talking about the organization. " -"Taking control of corporate messages is a decition the organization needs to " -"take by itself, based on its need of better describe what it is." +"When the organization doesn't take control over the corporate " +"messages it produces, the organization is letting that area of its " +"identity to the unknown and the results might be good or not so " +"good, it is hard to know. The issue to see here is that even the " +"organization doesn't take control over its corporate messages, they " +"are always talking about the organization. Taking control of " +"corporate messages is a decition the organization needs to take by " +"itself, based on its need of better describe what it is." msgstr "" msgid "" -"In the very specific case of The CentOS Project, we'll concentrate our attention on corporate " -"messages that reach us through the visual sense. This is, all the visual " -"manifestations The CentOS " -"Project is made of. As visual manifestaions we understand all the " -"visible media The CentOS " -"Project uses to manifest its existence on. At this point it is " -"necessary to consider what The CentOS Project is, what its mission is and what it is " -"producing. This, in order to identify which visual manifestations the " -"organization is demanding attention of corporate design for." +"In the very specific case of The CentOS Project, we'll concentrate our " +"attention on corporate messages that reach us through the visual " +"sense. This is, all the visual manifestations The CentOS Project is made " +"of. As visual manifestaions we understand all the visible media " +"The CentOS " +"Project uses to manifest its existence on. At this point it " +"is necessary to consider what The CentOS Project is, what its mission is and " +"what it is producing. This, in order to identify which visual " +"manifestations the organization is demanding attention of corporate " +"design for." msgstr "" msgid "" -"Inside The CentOS " -"Project we identify and apply corporate design to the following " -"visual manifestations:" +"Inside The " +"CentOS Project we identify and apply corporate design to " +"the following visual manifestations:" msgstr "" msgid "" -"The CentOS Distribution — This visual manifestation exists to cover all " -"actions related to artwork production and rebranding, required by The CentOS " -"Distribution in order to comply with upstream's redistribution guidelines. " -"This visual manifestation is described in ." +"The CentOS Distribution — This visual manifestation exists to cover " +"all actions related to artwork production and rebranding, required " +"by The CentOS Distribution in order to comply with upstream's " +"redistribution guidelines. This visual manifestation is described " +"in ." msgstr "" msgid "" -"The CentOS Web — This visual manifestation exists to cover all actions " -"related to artwork production required by The CentOS Project to manifest its existence in the " -"World Wide Web medium. This visual manifestation is described in ." +"The CentOS Web — This visual manifestation exists to cover all " +"actions related to artwork production required by The CentOS Project to " +"manifest its existence in the World Wide Web medium. This visual " +"manifestation is described in ." msgstr "" msgid "" -"The CentOS Showroom — This visual manifestation exists to cover all actions " -"related to artwork production required by The CentOS Project to manifest its existence " -"through media produced industrially (e.g., stationery, clothes, CDs, DVDs, " -"etc.). This visual manifestation is described in ." +"The CentOS Symbol — This visual manifestation exists to cover all " +"actions related to artwork production required by The CentOS Project to " +"manifest its existence through media produced industrially (e.g., " +"stationery, clothes, CDs, DVDs, etc.). This visual manifestation is " +"described in ." msgstr "" msgid "" -"The visual manifestations identified above seem to cover most media required " -"by The CentOS Project, as organization, to show its existence. However, other visual " -"manifestations could be added in the future, as long as they be needed, to " -"cover different areas like stands, buildings, offices, road transportation " -"or whaterver visual manifestation The CentOS Project thouches to show its existence." +"The visual manifestations identified above seem to cover most media " +"required by The " +"CentOS Project, as organization, to show its existence. " +"However, other visual manifestations could be added in the future, " +"as long as they be needed, to cover different areas like stands, " +"buildings, offices, road transportation or whaterver visual " +"manifestation The CentOS Project thouches to show its existence." msgstr "" msgid "" -"Once all visual manifestations have been identified and defined through " -"design models, it is time to visually remark their connection with The CentOS Project. This " -"kind of connection is realized by applying The CentOS Brand to design models " -"inside visual manifestations supported through corporate design." +"Once all visual manifestations have been identified and defined " +"through design models, it is time to visually remark their " +"connection with The CentOS Project. This kind of connection is realized " +"by applying The CentOS Brand to design models inside visual " +"manifestations supported through corporate design." msgstr "" msgid "Corporate Communication" msgstr "" msgid "" -"The CentOS Project corporate communication is focused on the effective propagation of " -"corporate messages. Propagation of corporate messages is closely related to " -"the media the organization uses as vehicle to distribute its corporate " -"messages." +"The CentOS " +"Project corporate communication is focused on the effective " +"propagation of corporate messages. Propagation of corporate " +"messages is closely related to the media the organization uses as " +"vehicle to distribute its corporate messages." msgstr "" msgid "" -"The CentOS Project corporate communication takes place through the following visual " -"manifestations:" +"The CentOS " +"Project corporate communication takes place through the " +"following visual manifestations:" msgstr "" msgid "The CentOS Distribution" msgstr "" msgid "" -"This visual manifestation communicates its existence through software " -"packages. There are packages that make a remarkable use of images, packages " -"that make a moderate use of images, and packages that don't use images at " -"all. This visual manifestation is focused on providing The CentOS Project images required by " -"software packages that do use images in a remarkable way, specially those " -"holding the upstream brand (e.g., anaconda, " -"grub, syslinux, gdm, kdebase)." +"This visual manifestation communicates its existence through " +"software packages. There are packages that make a remarkable use of " +"images, packages that make a moderate use of images, and packages " +"that don't use images at all. This visual manifestation is focused " +"on providing The " +"CentOS Project images required by software packages that do " +"use images in a remarkable way, specially those holding the " +"upstream brand (e.g., anaconda, grub, syslinux, gdm, " +"kdebase)." msgstr "" msgid "" -"The Community Enterprise Operating System itself (communicates the essense " -"of The CentOS Project existence.)." +"The Community Enterprise Operating System itself (communicates the " +"essense of The " +"CentOS Project existence.)." msgstr "" msgid "" -"Release Schema (Lifetime) and all the stuff related (e.g., Release Notes, " -"Documentation, Erratas, etc.)." +"Release Schema (Lifetime) and all the stuff related (e.g., Release " +"Notes, Documentation, Erratas, etc.)." msgstr "" msgid "The CentOS Web" @@ -1988,12 +2555,13 @@ msgstr "" msgid "" "This visual manifestation communicates its existence through web " -"applications. These web applications are free software and come from " -"different providers which distribute their work with predefined visual " -"styles. Frequently, these predefined visual styles have no visual relation " -"among themselves and introduce some visual contraditions when they all are " -"put together. Removing these visual contraditions is object of work for this " -"visual manifestation." +"applications. These web applications are free software and come " +"from different providers which distribute their work with " +"predefined visual styles. Frequently, these predefined visual " +"styles have no visual relation among themselves and introduce some " +"visual contraditions when they all are put together. Removing these " +"visual contraditions is object of work for this visual " +"manifestation." msgstr "" msgid "The CentOS Chat." @@ -2015,21 +2583,23 @@ msgid "Social Events, Interviews, Conferences, etc." msgstr "" msgid "" -"The extensive network of mirrors available for downloading ISO files as well " -"as RPMs and SRPMs used to build them up in different architectures." +"The extensive network of mirrors available for downloading ISO " +"files as well as RPMs and SRPMs used to build them up in different " +"architectures." msgstr "" -msgid "The CentOS Showroom" +msgid "The CentOS Symbol" msgstr "" msgid "" -"This visual manifestation communicates its existence through production of " -"industrial objects carrying The CentOS Brand. These branded objects are " -"directed to be distributed on social events and/or shops. They provide a way " -"of promotion and commercialization that may help to reduce The CentOS Project expenses (e.g., " -"electrical power, hosting, servers, full-time-developers, etc.), in a " -"similar way as donations may do." +"This visual manifestation communicates its existence through " +"production of industrial objects carrying The CentOS Brand. These " +"branded objects are directed to be distributed on social events and/" +"or shops. They provide a way of promotion and commercialization " +"that may help to reduce The CentOS Project expenses (e.g., electrical " +"power, hosting, servers, full-time-developers, etc.), in a similar " +"way as donations may do." msgstr "" msgid "Stationery (e.g., Posters, Stickers, CD Lables and Sleeves)." @@ -2045,120 +2615,130 @@ msgid "Corporate Behaviour" msgstr "" msgid "" -"The CentOS Project corporate behaviour is focused on the effective interaction of each " -"member involved in the organization (e.g., core developers, community " -"members, etc.). It is related to ethics and politics used to do the things " -"inside the organization. It is related to the sense of direction chosen by " -"the organization and they way the organization projects itself to achieve it." +"The CentOS " +"Project corporate behaviour is focused on the effective " +"interaction of each member involved in the organization (e.g., core " +"developers, community members, etc.). It is related to ethics and " +"politics used to do the things inside the organization. It is " +"related to the sense of direction chosen by the organization and " +"they way the organization projects itself to achieve it." msgstr "" msgid "" -"The CentOS Project corporate behaviour takes place through The CentOS Project corporate " -"communication, as described in ." +"The CentOS " +"Project corporate behaviour takes place through The CentOS Project " +"corporate communication, as described in ." msgstr "" msgid "Corporate Structure" msgstr "" msgid "" -"The CentOS Project corporate structure is based on a Monolithic Corporate Visual " -"Identity Structure. In this configuration, one unique name and one unique " -"visual style is used in all visual manifestation The CentOS Project is made of." +"The CentOS " +"Project corporate structure is based on a Monolithic " +"Corporate Visual Identity Structure. In this configuration, one " +"unique name and one unique visual style is used in all visual " +"manifestation The CentOS Project is made of." +msgstr "" + +msgid "" +"In a monolithic corporate visual identity structure, internal and " +"external stakeholders use to feel a strong sensation of uniformity, " +"orientation, and identification with the organization. No matter if " +"you are visiting web sites, using the distribution, or acting on " +"social events, the one unique name and one unique visual style " +"connects them all to say: Hey! we are all part of The CentOS Project." msgstr "" msgid "" -"In a monolithic corporate visual identity structure, internal and external " -"stakeholders use to feel a strong sensation of uniformity, orientation, and " -"identification with the organization. No matter if you are visiting web " -"sites, using the distribution, or acting on social events, the one unique " -"name and one unique visual style connects them all to say: Hey! we are all " -"part of The CentOS " -"Project." +"Other corporate structures for The CentOS Project have been considered as " +"well. Such is the case of producing one different visual style for " +"each major release of The CentOS Distribution. This structure isn't " +"inconvenient at all, but some visual contradictions could be " +"introduced if it isn't applied correctly and we need to be aware of " +"it. To apply it correctly, we need to know what The CentOS Project is made " +"of." msgstr "" msgid "" -"Other corporate structures for The CentOS Project have been considered as well. Such is the " -"case of producing one different visual style for each major release of The " -"CentOS Distribution. This structure isn't inconvenient at all, but some " -"visual contradictions could be introduced if it isn't applied correctly and " -"we need to be aware of it. To apply it correctly, we need to know what " -"The CentOS Project is made of." +"The CentOS " +"Project, as organization, is mainly made of (but not " +"limited to) three visual manifestions: The CentOS Distribution, The " +"CentOS Web and The CentOS Symbol. Inside The CentOS Distribution " +"visual manifestations, The CentOS Project maintains near to four different " +"major releases of The CentOS Distribution, parallely in time. " +"However, inside The CentOS Web visual manifestations, the content " +"is produced for no specific release information (e.g., there is no " +"a complete web site for each major release of The CentOS " +"Distribution individually, but one web site to cover them all). " +"Likewise, the content produced in The CentOS Symbol is industrially " +"created for no specific release, but The CentOS Project in general." msgstr "" msgid "" -"The CentOS Project, as organization, is mainly made of (but not limited to) three visual " -"manifestions: The CentOS Distribution, The CentOS Web and The CentOS " -"Showroom. Inside The CentOS Distribution visual manifestations, The CentOS Project maintains " -"near to four different major releases of The CentOS Distribution, parallely " -"in time. However, inside The CentOS Web visual manifestations, the content " -"is produced for no specific release information (e.g., there is no a " -"complete web site for each major release of The CentOS Distribution " -"individually, but one web site to cover them all). Likewise, the content " -"produced in The CentOS Showroom is industrially created for no specific " -"release, but The CentOS " -"Project in general." +"In order to produce the The CentOS Project Monolithic Corporate Visual " +"Identity Structure correctly, we need to concider all the visual " +"manifestations The CentOS Project is made of, not just one of them. If " +"one different visual style is implemented for each major release of " +"The CentOS Distribution, which one of those different visual styles " +"would be used to cover the remaining visual manifestations The CentOS Project is made of (e.g., The CentOS Web and The CentOS Symbol)?" msgstr "" msgid "" -"In order to produce the The CentOS Project Monolithic Corporate Visual Identity Structure " -"correctly, we need to concider all the visual manifestations The CentOS Project is made " -"of, not just one of them. If one different visual style is implemented for " -"each major release of The CentOS Distribution, which one of those different " -"visual styles would be used to cover the remaining visual manifestations " -"The CentOS Project is made of (e.g., The CentOS Web and The CentOS Showroom)?" +"Probably you are thinking: yes, I see your point, but The CentOS " +"Brand connects them all already, why would we need to join them up " +"into the same visual style too, isn't it more work to do, and " +"harder to maintain?" msgstr "" msgid "" -"Probably you are thinking: yes, I see your point, but The CentOS Brand " -"connects them all already, why would we need to join them up into the same " -"visual style too, isn't it more work to do, and harder to maintain?" +"Harder to maintain, more work to do, probably. Specially when you " +"consider that The CentOS Project has proven stability and consistency " +"through time and, that, certainly, didn't come through swinging " +"magical wands or something but hardly working out to automate tasks " +"and providing maintainance through time. With that in mind, we " +"consider The " +"CentOS Project Corporate Visual Identity Structure must be " +"consequent with such stability and consistency tradition. It is " +"true that The CentOS Brand does connect all the visual " +"manifestations it is present on, but that connection is " +"strengthened if one unique visual style backups it. In fact, " +"whatever thing you do to strength the visual connection among " +"The CentOS " +"Project visual manifestations would be very good in favor " +"of The CentOS " +"Project recognition." msgstr "" msgid "" -"Harder to maintain, more work to do, probably. Specially when you consider " -"that The CentOS Project has proven stability and consistency through time and, that, " -"certainly, didn't come through swinging magical wands or something but " -"hardly working out to automate tasks and providing maintainance through " -"time. With that in mind, we consider The CentOS Project Corporate Visual Identity Structure " -"must be consequent with such stability and consistency tradition. It is true " -"that The CentOS Brand does connect all the visual manifestations it is " -"present on, but that connection is strengthened if one unique visual style " -"backups it. In fact, whatever thing you do to strength the visual connection " -"among The CentOS Project visual manifestations would be very good in favor of The CentOS Project " -"recognition." -msgstr "" - -msgid "" -"Obviously, having just one visual style in all visual manifestations for " -"eternity would be a very boring thing and would give the idea of a visually " -"dead project. So, there is no problem on creating a brand new visual style " -"for each new major release of The CentOS Distribution, in order to refresh " -"The CentOS Distribution visual style; the problem itself is in not " -"propagating the brand new visual style created for the new release of The " -"CentOS Distribution to all other visual manifestations The CentOS Project is made of, in a " -"way The CentOS Project could be recognized no matter what visual manifestation be in front " -"of us. Such lack of uniformity is what introduces the visual contradition we " -"are precisely trying to solve by mean of themes production in The CentOS Artwork " +"is made of, in a way The CentOS Project could be recognized no matter what " +"visual manifestation be in front of us. Such lack of uniformity is " +"what introduces the visual contradition we are precisely trying to " +"solve by mean of themes production in The CentOS Artwork " "Repository." msgstr "" @@ -2166,81 +2746,130 @@ msgid "The CentOS Brand" msgstr "" msgid "" -"The CentOS Brand is the main visual manifestaion of The CentOS Project. The CentOS Project uses The CentOS " -"Brand to connect all the visual manifestions it is made of (e.g., GNU/Linux " -"Distributions, Web sites, Stationery, etc.) and, this way, provides " -"recognition ... just as a GPG signature might do for RPM " -"packages. among similar projects available on the " -"Internet. The CentOS Brand is made of a graphical component () and a typographical component () that, when put together, make . The components that make The CentOS Brand can be " -"used together or separately, considering that, in hierarchy order, is rather prefered than , as well as is rather prefered than ." +"The CentOS Brand is the main visual manifestaion of The CentOS Project. " +"The CentOS " +"Project uses The CentOS Brand to connect all the visual " +"manifestions it is made of (e.g., GNU/Linux Distributions, Web " +"sites, Stationery, etc.) and, this way, provides recognition " +" ... just as a GPG signature might do for RPM " +"packages. among similar projects available on " +"the Internet. The CentOS Brand is made of a graphical component " +"() and a typographical " +"component () that, when put " +"together, make . The " +"components that make The CentOS Brand can be used together or " +"separately, considering that, in hierarchy order, is rather prefered than , as well as is rather prefered than ." msgstr "" msgid "" -"In addition to those components mentioned above, The CentOS Brand includes " -"another component named . is mainly used as background on images " -"and is directly related to the look and feel of all visual manifestations " -"The CentOS Project shows its existence on. In contrast with , and ; might " -"change from time to time providing a vehicle to refresh how " -"The CentOS Project looks and feels." +"In addition to those components mentioned above, The CentOS Brand " +"includes another component named . is mainly used " +"as background on images and is directly related to the look and " +"feel of all visual manifestations The CentOS Project shows its existence on. " +"In contrast with , and ; might " +"change from time to time providing a vehicle to refresh how The " +"CentOS Project looks and feels." msgstr "" msgid "" -"The CentOS Brand and all the visual manifestations derivated from it are " -"available for you to study and propose improvement around a good citizen's " -"will inside The CentOS Community, but you are not allowed to redistribute " -"them elsewhere, without the given permission of The CentOS Project." +"The CentOS Brand and all the visual manifestations derivated from " +"it are available for you to study and propose improvement around a " +"good citizen's will inside The CentOS Community, but you are not " +"allowed to redistribute them elsewhere, without the given " +"permission of The CentOS Project." msgstr "" msgid "" -"If you need to redistribute either " -"or any visual manifestation derived from it, write your intentions to the " -"The CentOS Developers mailing list (centos-devel@centos.org)." +"If you need to redistribute either or any visual manifestation derived from it, write your " +"intentions to the The CentOS Developers mailing list (centos-devel@centos.org)." msgstr "" -msgid "The CentOS Symbol" +msgid "" +"The CentOS Symbol is the graphical part of The CentOS Logo. As The " +"CentOS Logo, The CentOS Symbol is used to brand " +"images produced by The CentOS Project and provide a visual connection " +"between images so they can be monolithically recognized as part of " +"The CentOS " +"Project. The CentOS Symbol must be exactly the same every " +"time it is printed out and a route to reproduce it in such a way " +"must be available so as to avoid reproduction mistakes when images " +"are branded with it." msgstr "" msgid "The CentOS Type" msgstr "" +msgid "" +"The CentOS Type is the typographical part of The CentOS Logo. " +"Comparing with both The CentOS Logo and The CentOS Symbol, The " +"CentOS Type by its own, provides poor visual connection between " +"images that intend to be recognized as a monolithic part of The CentOS Project and shouldn't be used alone. Instead, The CentOS Logo or The " +"CentOS Symbol are preferred. The CentOS Symbol must be exactly the " +"same every time it is printed out and a route to reproduce it in " +"such a way must be available so as to avoid reproduction mistakes " +"when images are branded with it." +msgstr "" + msgid "The CentOS Logo" msgstr "" +msgid "" +"The CentOS Logo is a construction made of The CentOS Symbol and The " +"CentOS Type. The CentOS Symbol and The CentOS Logo are the main " +"visual manifestations of the organization known as The CentOS Project. " +"As The CentOS Symbol, The CentOS Logo is used to brand images produced by The CentOS Project and provide a visual " +"connection between images so they can be monolithically recognized " +"as part of The " +"CentOS Project. The CentOS Logo must be exactly the same " +"every time it is printed out and a route to reproduce it in such a " +"way must be available so as to avoid reproduction mistakes when " +"images are branded with it." +msgstr "" + msgid "The CentOS Motif" msgstr "" msgid "Release Schema" msgstr "" +msgid "The CentOS Showroom" +msgstr "" + msgid "" -"The " -"CentOS Artwork Repository documentation work line is implemented " -"through documentation manuals. Documentation manuals are implemented through " -"different documentation formats provided inside The CentOS Distribution (e." -"g., Docbook, Texinfo, " -"LaTeX, etc.). Structuring tasks related to " -"documentation systems (e.g., creating, editing, deleting, copying, renaming, " -"etc.) are standardized through the help functionality of " -"centos-art.sh script, as described in . This way, people writting documentation don't need " -"to deal with underlaying tasks like creating files, updating menus, nodes, " -"cross references and wondering where to put everything in The CentOS Artwork " +"The CentOS Artwork Repository documentation work line is " +"implemented through documentation manuals. Documentation manuals " +"are implemented through different documentation formats provided " +"inside The CentOS Distribution (e.g., Docbook, Texinfo, " +"LaTeX, etc.). Structuring tasks related " +"to documentation systems (e.g., creating, editing, deleting, " +"copying, renaming, etc.) are standardized through the help functionality of centos-art.sh script, as " +"described in . This way, " +"people writting documentation don't need to deal with underlaying " +"tasks like creating files, updating menus, nodes, cross references " +"and wondering where to put everything in The CentOS Artwork " "Repository." msgstr "" @@ -2248,397 +2877,329 @@ msgid "Documentation Production Cycle" msgstr "" msgid "" -"This chapter describes the procedure you should follow to create and " -"maintain documentation manuals inside The CentOS Artwork Repository." +"This chapter describes the procedure you should follow to create " +"and maintain documentation manuals inside The CentOS Artwork " +"Repository." msgstr "" msgid "" -"This chapter describes general concepts that can be applied through the " -"documentation formats supported inside the help " -"functionality of centos-art.sh script. To illustrate the " -"production process related to documentation manuals inside The CentOS Artwork " -"Repository, this chapter uses the The CentOS Artwork " -"Repository File System (TCAR-FS) documentation manual as example." +"This chapter describes general concepts that can be applied through " +"the documentation formats supported inside the help functionality of centos-art.sh script. " +"To illustrate the production process related to documentation " +"manuals inside The CentOS Artwork Repository, this " +"chapter uses the The CentOS Artwork Repository File " +"System (TCAR-FS) documentation manual as example." msgstr "" msgid "Identifying Document Goals" msgstr "" msgid "" -"The first step in producing a documentation manual is to clearly understand " -"what you exactly need to document and why you need to do so. The obvious " -"answer to this question would be to describe the basic ideas behind an " -"implementation so it can be useful once published. It is important that you " -"find out the reasons you need to do what you are doing and, also, those " -"helping you to retain the motivation to keep doing it in the future. " -"Otherwise, without such foundations, you'll surely end up leaving the effort " -"soon enough to make a lost cause from your initial work." +"The first step in producing a documentation manual is to clearly " +"understand what you exactly need to document and why you need to do " +"so. The obvious answer to this question would be to describe the " +"basic ideas behind an implementation so it can be useful once " +"published. It is important that you find out the reasons you need " +"to do what you are doing and, also, those helping you to retain the " +"motivation to keep doing it in the future. Otherwise, without such " +"foundations, you'll surely end up leaving the effort soon enough to " +"make a lost cause from your initial work." msgstr "" msgid "" -"Before The CentOS Artwork Repository File System " -"documentation manual exist, there was an emerging need to understand what " -"each directory inside the growing directory layout was for, how they could " -"be used and how they could be connected one another. At that moment, the " -"directory layout was very unstable and explaining the whole idea behind it " -"was not possible, there were too many changing concepts floating around " -"which needed to be considered in the same changing way. So, to understand " -"what was happening, the The CentOS Artwork Repository File " -"System documentation manual was created." +"Before The CentOS Artwork Repository File System documentation manual would exist, there was an emerging " +"need to understand what each directory inside the growing directory " +"layout was for, how it could be used and each directory could be " +"connected one another. At that moment, the directory layout was " +"very unstable and explaining the whole idea behind it was not " +"possible, there were too many changing concepts floating around " +"which needed to be considered in the same changing way. So, to " +"understand what was happening, the The CentOS Artwork " +"Repository File System documentation manual was created." msgstr "" msgid "" -"The The CentOS Artwork Repository File System manual " -"was conceived based on the idea of individually documenting each directory " -"inside the repository and, later, by considering all directory " -"documentations together, it would be (hypothetically) possible to correct " -"the whole idea through an improvement cycle that would consolidate the final " -"idea we try to implement." +"The The CentOS Artwork Repository File System manual was conceived based on the idea of documenting " +"each directory inside the repository individually and, later, by " +"considering all directory documentations altogether, it would be " +"(hypothetically) possible to correct the whole idea through an " +"improvement cycle that would consolidate the final idea we were " +"trying to implement." msgstr "" msgid "" -"Other documentation manuals can be based on reasons different from those " -"described above, however, no matter what those reasons be, it will be " -"helpful to make yourself a clean idea about what you are going to document " -"exactly before putting your hands on it." +"Other documentation manuals can be based on reasons different from " +"those described above, however, no matter what those reasons are, " +"it will be helpful to make yourself a clean idea about what you are " +"going to document exactly before putting your hands on it." msgstr "" msgid "Identifying Document Title" msgstr "" msgid "" -"Once you've make yourself an clean idea of what the documentation manual is " -"for and the needs behind, it is time for you to define the manual's title " -"and the manual's directory name. Both manuals' title and manual's directory " -"name describe what the documentation manual is about. The manual's title is " -"used inside the documentation while the manual's directory name is used to " -"store the related source files inside The CentOS Artwork Repository " -"directory structure. Generally, the manual's title is a phrase of few words " -"and the manual's directory name is the abbreviation of that phrase set as " -"manual's title." +"Once you've make yourself an clean idea of what the documentation " +"manual is for and the needs behind it, it is time for you to define " +"the manual's title and the manual's directory name. Both manuals' " +"title and manual's directory name describe what the documentation " +"manual is about. The manual's title is used inside the " +"documentation while the manual's directory name is used to store " +"the related source files inside The CentOS Artwork Repository directory structure. Generally, the manual's title is a " +"phrase of few words and the manual's directory name is the " +"abbreviation of that phrase set as manual's title." msgstr "" msgid "" -"Following with our example, the manual's title chosen was The " -"CentOS Artwork Repository File System and its directory name was " -"set to Tcar-fs to comply with the file " -"name convenctions described at ." +"Following with our example, the manual's title chosen was " +"The CentOS Artwork Repository File System " +"and its directory name was set to Tcar-fs to comply with the file name convenctions " +"described at ." msgstr "" msgid "Identifying Document Structure" msgstr "" msgid "" -"Once both the manual's title and the manual's directory name have been " -"defined, it is time for you to plan the document structure through which the " -"manual's content will be organized." +"Once both the manual's title and the manual's directory name have " +"been defined, it is time for you to plan the document structure " +"through which the manual's content will be organized." +msgstr "" + +msgid "" +"The specific document structure you choose for a documentation " +"manuals is affected by the documentation format you use to write " +"documentation source files. Nevertheless, no matter what the " +"documentation format be, the document structure produced from the " +" functionality will always " +"follow and upside-down tree configuration for document structures. " +"In this configuration, documentation manuals can be organized " +"through different structural levels (e.g., parts, chapters, " +"sections, subsection, etc.) based on the support provided by the " +"documentation format you chose." msgstr "" msgid "" -"The document structure of documentation manuals is specific to that " -"documentation format used to write documentation source files. Nevertheless, " -"no matter what the documentation format be, the document structure produce " -"produced from the help functionality of centos-" -"art.sh script follows and upside-down tree configuration. In this " -"configuration, documentation manuals can be organized through parts, " -"chapters, sections, and several subsection levels based in whether the " -"chosen documentation format supports them or not." +"The The CentOS Artwork Repository File System documentation manual was conceived to document each " +"directory structure The CentOS Artwork Repository is " +"made of, using Texinfo as main documentation format." msgstr "" msgid "" -"Considering the The CentOS Artwork Repository File System documentation manual, we already know that it was conceived to " -"document each directory structure The CentOS Artwork Repository is " -"made of using Texinfo format and the sectioning levels supported by it. At " -"this point we phase that The CentOS Artwork Repository has more levels deep " -"than sectioning commands available inside Texinfo formats. This way it is " -"not possible to use one sectioning command for each directory level inside " -"the repository directory structure we need to document. Based on these " -"issues, it is imperative to reaccomodate the document structure in order to " -"be able of documenting every directory The CentOS Artwork Repository is " -"made of, using the sectioning levels supported by most documentation formats " -"inside The CentOS Distribution, no matter how many levels deep the " -"repository directory structure has." +"At this point we find that The CentOS Artwork Repository had more levels deep than sectioning commands available " +"inside documentation format. This way it is not possible to use one " +"sectioning command for each directory level inside the repository " +"directory structure we need to document. Based on these issues, it " +"is imperative to re-accommodate the document structure in order to " +"be able of documenting every directory The CentOS Artwork " +"Repository is made of, using the sectioning levels " +"supported by that documentation format we chose, no matter how many " +"levels deep the repository directory structure had." msgstr "" msgid "" -"As consequence, The CentOS Artwork Repository File System ended up being organized through the following documentation " -"structure:" +"As consequence, The CentOS Artwork Repository File " +"System ended up being organized through the following " +"documentation structure:" msgstr "" -msgid "Chapter 1. The trunk Directory" +msgid "" +"Chapter 1. The trunk " +"Directory" msgstr "" msgid "" -"This chapter describes the trunk " -"directory inside the repository and all subdirectories inside it. The first " -"level of directories (i.e., the trunk directory itself) is described inside the chapter entry. Deeper " -"directory levels are all documented through sections and have a file for " -"their own. It is also possible to write subsections and subsubsections, " -"however, they don't have a file for their own as sections do. Subsections " -"and Subsubsections should be written as part of section files (i.e., when " -"writting sections)." +"This chapter describes the trunk directory inside the repository and all subdirectories " +"inside it. The first level of directories (i.e., the trunk directory itself) is described " +"inside the chapter entry. Deeper directory levels are all " +"documented through sections and have a file for their own. It is " +"also possible to write subsections and subsubsections, however, " +"they don't have a file for their own as sections do. Subsections " +"and Subsubsections should be written as part of section files (i." +"e., when writting sections)." msgstr "" msgid "" -"Chapter 2. The branches Directory" +"Chapter 2. The branches " +"Directory" msgstr "" msgid "" -"This chapter describes the branches " -"directory and all directories inside it following the same structure " -"described for trunk directory above." +"This chapter describes the branches directory and all directories inside it following the " +"same structure described for trunk directory above." msgstr "" -msgid "Chapter 3. The tags Directory" +msgid "" +"Chapter 3. The tags " +"Directory" msgstr "" msgid "" -"This chapter describes the tags " -"directory and all directories inside it following the same structure " -"described for trunk directory above." +"This chapter describes the tags directory and all directories inside it following the " +"same structure described for trunk directory above." msgstr "" msgid "Appendix A. Licenses" msgstr "" msgid "" -"This appendix is confined to organize licenses mentioned in the manual. The " -"content of this appendix is out of documenatation manual scope itself and is " -"shared among all documentation manuals written through the help of centos-art.sh script inside The CentOS Artwork " -"Repository." +"This appendix is confined to organize licenses mentioned in the " +"manual. The content of this appendix is out of documenatation " +"manual scope itself and is shared among all documentation manuals " +"written through the " +"functionality." msgstr "" msgid "Index" msgstr "" msgid "" -"This chapter organizes links to those index definitions you defined inside " -"the documentation manual. The index information displayed by this chapter is " -"auto-generated each time the manual's output files are created so this " -"chapter is not editable." +"This chapter organizes links to those index definitions you defined " +"inside the documentation manual. The index information displayed by " +"this chapter is auto-generated each time the manual's output files " +"are created so this chapter is not editable." msgstr "" msgid "" -"The document structure illustrated above is also considered the default " -"document structure used by the help functionality of " -"centos-art.sh script when you produce new documentation " -"manuals inside The CentOS Artwork Repository. In contrast with document " +"The document structure illustrated above is also considered the " +"default document structure used by the functionality of centos-art.sh script " +"when you produce new documentation manuals inside The " +"CentOS Artwork Repository. In contrast with document " "structure illustrated above, the default document structure used by " -"help functionality doesn't include sectioning " -"constructions like parts, chapters, sections, subsections and the like. Such " -"structuring constructions should be specified by you when building the " -"documentation manual. The only exceptions to this restriction are sectioning " -"structures used to organize contents like Index and " -"Licenses, which are considered inseparable components of " -"documentation manuals stored inside The CentOS Artwork Repository." +" functionality doesn't include " +"sectioning constructions like parts, chapters, sections, " +"subsections and the like in the document structure created. Such " +"structuring constructions should be specified by you when building " +"the documentation manual. The only exceptions to this restriction " +"are sectioning structures used to organize contents like " +"Index and Licenses, which are " +"considered inseparable components of documentation manuals stored " +"inside The CentOS Artwork Repository." msgstr "" msgid "Implementing Document Structure" msgstr "" msgid "" -"This section describes the steps you should follow to implement document " -"structures like that one described in ." +"The document structure implementation is automated by the functionality, as described in " +"." msgstr "" -msgid "Creating Document Structure" +msgid "Maintaining Document Structure" msgstr "" msgid "" -"To create new documentation manuals inside The CentOS Artwork Repository you need to use the help functionality of " -"centos-art.sh script, as shown in the following command:" +"The document structure maintenance is implemented by the functionality, as described in " +"." msgstr "" -#, no-wrap -msgid "centos-art help --edit \"manual-name\"" +msgid "Documentation Formats" msgstr "" msgid "" -"The first time you execute this command, you will be prompted to enter " -"manual specific information like document format, document title, document " -"subtitle, document author, etc. Once this information has been collected the " -"help functionality performs some repository " -"verifications and creates the manual source files inside the manual's " -"directory name you specified as manual-name." +"The CentOS Distribution provides support for different " +"documentation formats, including Texinfo, LaTeX, DocBook and " +"LinuxDoc. These formats have their own specifications and " +"requirements to create and maintain documentation manuals written " +"through them. Inside The CentOS Artwork Repository, the " +" functionality provides the " +"interface you use to create and maintain documentation manuals " +"without needing to take care the underlaying structuring tasks." msgstr "" msgid "" -"When you create new documentation manuals, take care of the locale " -"information you are currently using. This information is generally set in " -"the LANG environment variable and is used by the " -"help functionality of centos-art.sh " -"script to define the language of new documentation manual and the document " -"template used to build it, as well." +"This chapter describes how the functionality implements the different documentation source " +"formats available inside The CentOS Distribution, and the " +"internationalization issues related to documentation manuals " +"produced through them." +msgstr "" + +msgid "Texinfo" msgstr "" msgid "" -"Once the documentation structure has been created this way, the recently " -"created documentation manual is ready to receive new chapters and sections " -"as it is described in ." -msgstr "" - -msgid "Maintaining Document Structure" -msgstr "" - -msgid "" -"This section describes the steps you should follow to maintain documentation " -"structures like that one described in ." -msgstr "" - -msgid "Editing Document Structure" -msgstr "" - -msgid "centos-art help --edit \"tcar-fs::trunk\"" -msgstr "" - -msgid "" -"This command creates the base structure for the trunk chapter " -"and opens its main definition file with your favorite text editor so you can " -"update the chapter introduction. This very same procedure is used to create " -"branches and tags chapters, just be sure to " -"change the chapter field accordingly." -msgstr "" - -msgid "centos-art help --edit \"tcar-fs::trunk:identity\"" -msgstr "" - -msgid "" -"This command creates the identity section inside the " -"trunk chapter. If the chapter doesn't exist it will be " -"created first. In this command, the identity section refers " -"to trunk/Identity directory inside " -"The " -"CentOS Artwork Repository. In order to document other directories, " -"follow the same procedure but using minus signs to separate directories. For " -"example, to document the trunk/Identity/" -"Models/Themes directory you should use the " -"tcar-fs::trunk:identity-models-themes " -"documentation entry." -msgstr "" - -msgid "" -"In the very specific case of TCAR-FS manual, it is " -"also possible to refer chapters and sections using a path/to/dir format. For example, the " -"reference tcar-fs::trunk:identity-models-themes " -"can be also specified as trunk/Identity/" -"Models/Themes, in case you feel more confortable with it " -"than the former one." -msgstr "" - -msgid "Copying Document Structure" -msgstr "" - -msgid "Deleting Document Structure" -msgstr "" - -msgid "Renaming Document Structure" -msgstr "" - -msgid "Updating Document Structure" -msgstr "" - -msgid "Documentation Formats" -msgstr "" - -msgid "" -"The CentOS Distribution provides support for different documentation " -"formats, including Texinfo, LaTeX, DocBook and LinuxDoc. These formats have " -"their own specifications and requirements to create and maintain " -"documentation manuals written through them. Inside The CentOS Artwork Repository, the help functionality of centos-art." -"sh script provides an interface where documentation format " -"specifications have been already considered for you to be able of creating " -"and maintaining documentation manuals without needing to take care of those " -"underlaying structuring tasks." -msgstr "" - -msgid "" -"This chapter describes how the help functionality of " -"centos-art.sh script implements the different " -"documentation source formats available inside The CentOS Distribution, and " -"the internationalization issues related to documentation manuals produced " -"through them." -msgstr "" - -msgid "Texinfo" -msgstr "" - -msgid "" -"This section describes the implementation of Texinfo documentation format " -"inside the help functionality of centos-art." -"sh script described in . In " -"this section we assume you have a basic understanding of Texinfo " -"documentation system. Otherwise, if you don't know what Texinfo " -"documentation system is, read the Texinfo manual first (e.g., by running the " -"info texinfo command) and then, come back here." +"This section describes the implementation of Texinfo documentation " +"format inside the " +"functionality of centos-art.sh script. In this " +"section we assume you have a basic understanding of Texinfo " +"documentation system. Otherwise, if you don't know what Texinfo " +"documentation system is, read the Texinfo manual first (e.g., by " +"running the info texinfo command) and then, come " +"back here." msgstr "" msgid "Document Structure" msgstr "" msgid "" -"The help functionality of centos-art.sh provides a document structure that makes documentation manuals " -"created through it to be scalable and maintainable through time. This " -"document structure follows the idea of an upside-down tree to organize " -"chapters, sections, subsections and the like, as described in ." +"The functionality of " +"centos-art.sh provides a document structure that " +"makes documentation manuals created through it to be scalable and " +"maintainable through time. This document structure follows the idea " +"of an upside-down tree to organize chapters, sections, subsections " +"and the like, as described in ." msgstr "" msgid "" -"The first time you use the help functionality to create " -"a documentation manual in Texinfo format, the help " -"functionality considers the working directory you are placed in to determine " -"where to store the documentation manual source files. When the current " -"working directory is branches/Manuals/Texinfo, the documentation manual directory is created therein. On all " -"other situations, the documentation manual directory is created under " -"trunk/Manuals directory. Once the " -"documentation manual directory has been created, the help functionality creates the related definition files using Texinfo " -"documentation templates, as described in ." +"The functionality creates " +"documentation manuals source files in the Documentation/Models/Texinfo/ directory " +"and saves output produced from them in the Documentation/Manuals/Texinfo/ directory. " +"To produce documentation manuals initial source files, the functionality uses Texinfo " +"documentation templates, as described in ." msgstr "" msgid "" -"Inside the documentation manual directory, source files are stored inside " -"language-specific directories. The language-specific directories are " -"necessary to implement internationalization of Texinfo source files, as " -"described in ." +"Inside the documentation models directory, source files are stored " +"inside language-specific directories. The language-specific " +"directories are necessary to implement internationalization of " +"Texinfo source files, as described in ." msgstr "" msgid "" -"Inside the language-specific directory, the following files exist to store " -"the manual's main definitions (e.g., title, subtitle, author, copyright " -"notice, chapters, appendixes, indexes and all the similar stuff a " -"documentation manual would have). In addition to these files, there is one " -"directory for each chapter created inside the manual. Inside each chapter " -"directory, you'll found the files controlling the section definitions " -"related to that chapter they belong to. The section files (a.k.a. " -"documentation entries) are suffixed with a texinfo extension and named arbitrarily, as it is " -"illustrated in . Inside section files it is where you write the manual's content itself." +"Inside the language-specific directory, the following files exist " +"to store the manual's main definitions (e.g., title, subtitle, " +"author, copyright notice, chapters, appendixes, indexes and all " +"similar stuff a documentation manual usually has). In addition to " +"these files, there is one directory for each chapter created inside " +"the manual. Inside each chapter directory, you'll find the files " +"controlling the section definitions related each chapter they " +"belong to. The section files (a.k.a. documentation entries) are suffixed with a texinfo extension and named arbitrarily, as it is illustrated in " +". " +"Inside section files it is where you write the manual's content " +"itself." msgstr "" msgid "Texinfo document structure" @@ -2646,17 +3207,17 @@ msgstr "" #, no-wrap msgid "" -"trunk/Manuals/${MANUAL_NAME}\n" +"Documentation/Models/Texinfo/${MANUAL_NAME}\n" "`-- ${LANG}\n" -" |-- ${CHAPTER_NAME}\n" -" | |-- chapter-menu.texinfo\n" -" | |-- chapter-nodes.texinfo\n" -" | |-- chapter.texinfo\n" +" |-- ${CHAPTER_NAME}/\n" " | `-- ${SECTION_NAME}.texinfo\n" -" |-- Licenses\n" -" | |-- chapter-menu.texinfo\n" -" | |-- chapter-nodes.texinfo\n" -" | `-- chapter.texinfo\n" +" |-- ${CHAPTER_NAME}-menu.texinfo\n" +" |-- ${CHAPTER_NAME}-nodes.texinfo\n" +" |-- ${CHAPTER_NAME}.texinfo\n" +" |-- Licenses -> Documentation/Models/Texinfo/Default/${LANG}/Licenses\n" +" |-- Licenses-menu.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses-menu.texinfo\n" +" |-- Licenses-nodes.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses-nodes.texinfo\n" +" |-- Licenses.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses.texinfo\n" " |-- ${MANUAL_NAME}.conf\n" " |-- ${MANUAL_NAME}-index.texinfo\n" " |-- ${MANUAL_NAME}-menu.texinfo\n" @@ -2665,232 +3226,253 @@ msgid "" msgstr "" msgid "" -"Texinfo (as in texinfo-4.8-14.el5) doesn't support part " -"sectioning inside documentation manuals, so neither does the help functionality of centos-art.sh script. " +"Texinfo (as in texinfo-4.8-14.el5) doesn't " +"support part sectioning inside documentation manuals, so neither " +"the functionality does. " "Nevertheless, you can create several documentation manuals and " -"considered them as part of a bigger documentation " -"manual to workaround this issue." +"consider them as part of a bigger documentation manual to " +"workaround this issue." msgstr "" msgid "" -"In this document structure, the creation of documentation manuals, chapters " -"and sections is not limitted. You can create as many documenation manuals, " -"chapters and sections as you need. The only limitation would be the amount " -"of free space required to store the Texinfo source files and the output " -"files produced from them." +"In this document structure, the creation of documentation manuals, " +"chapters and sections is not limitted. You can create as many " +"documenation manuals, chapters and sections as you need. The only " +"limitation would be the amount of free space required to store the " +"Texinfo source files and the output files produced from them in " +"your workstation." msgstr "" msgid "Document Templates" msgstr "" msgid "" -"Texinfo document templates provide the initial state the help functionality of centos-art.sh script needs in " -"order to create and maintain document structures, as that one described in " +"Texinfo document templates provide the initial document structure " +"the functionality needs in " +"order to create and maintain document structures, as described in " "." msgstr "" msgid "" -"Texinfo document templates are language-specific. This means that there is " -"(or, at least, must be) one Texinfo document template for each language you " -"plan to support documentation manuals for. By default, The CentOS Artwork " -"Repository provides a default Texinfo document template under " -"en_US directory. This template " -"structure is used when your current locale is English language or when you " -"are creating/editing a documentation manual in a language other than " -"English, but no language-specific document template for that language exists " -"in the directory:" -msgstr "" - -#, no-wrap -msgid "" -"\n" -"trunk/Scripts/Bash/Functions/Help/Texinfo/Templates" +"Texinfo document templates are language-specific. This means that " +"there is (or, at least, must be) one Texinfo document template for " +"each language you plan to support documentation manuals for. By " +"default, The CentOS Artwork Repository provides a " +"default Texinfo document template under en_US directory. This template structure is used when " +"your current locale is English language or when you are creating/" +"editing a documentation manual in a language other than English, " +"but no language-specific document template for that language exists " +"in the Scripts/Documentation/Models/" +"Texinfo/Default/ directory." msgstr "" msgid "" -"This directory organizes all Texinfo document templates using the format " -"LL_CC, where LL is the language code (as in ISO-639) and CC the country code " -"(as in ISO-3166). The directory structure of Texinfo document templates is " -"illustrated in the and implemented through the following files:" +"The Scripts/Documentation/Models/" +"Texinfo/Default/ directory organizes all Texinfo " +"document templates using the format LL_CC, where LL is the language " +"code (as in ISO-639) and CC the country code (as in ISO-3166). The " +"directory structure of Texinfo document templates is illustrated in " +"the " +"and implemented through the following files:" msgstr "" msgid "manual.texinfo" msgstr "" msgid "" -"This file can be found inside the language-specific directory and contains " -"the manual's main definitions (e.g., document title, document language, " -"document authors, copyright notice, etc.)." +"This file can be found inside the language-specific directory and " +"contains the manual's main definitions (e.g., document title, " +"document language, document authors, copyright notice, etc.)." msgstr "" msgid "manual-menu.texinfo" msgstr "" msgid "" -"This file can be found inside the language-specific directory and contains " -"the menu definitions of chapters inside the manual. Menu definitions in this " -"file are automatically updated when a new chapter is created or deleted " -"through the help functionality of centos-art." -"sh script. Generally, you don't need to edit this file once the " +"This file can be found inside the language-specific directory and " +"contains the menu definitions of chapters inside the manual. When " +" functionality creates " +"instances of this file, menu definitions inside it are " +"automatically updated when a new chapter is created or deleted " +"through the functionality. " +"Generally, you don't need to edit instances of this file once the " "documentation manual has been created." msgstr "" msgid "" -"When a documentation manual is created for first time, this file is copied " -"from Texinfo document template directory structure to the documentation " -"manual being currently created. At this specific moment, this file contains " -"the following Texinfo menu definition:" +"When a documentation manual is created for first time, this file is " +"copied from Texinfo document template directory structure to the " +"documentation manual being currently created. At this specific " +"moment, the instance created contains the following Texinfo menu " +"definition:" msgstr "" #, no-wrap msgid "" +"\n" "@menu\n" "* Licenses::\n" "* Index::\n" -"@end menu" +"@end menu\n" msgstr "" msgid "" -"Later, when chapters are added to or deleted from the documentation manual, " -"the content of this file varies adding or deleting menu entries accordingly. " -"Nevertheless, the two entries shown above are ignored when new chapters are " -"added to or removed from the list, so they will always be present in this " -"file. To preserve the manual consistency, the help " -"functionality prevents you from deleting any of these chapters once the " -"documentation manual has been created." +"Later, when chapters are added to or deleted from the documentation " +"manual, the content of this file varies adding or deleting menu " +"entries accordingly. Nevertheless, the two entries shown above are " +"ignored when new chapters are added to or removed from the list, so " +"they will always be present in instances of this file. To preserve " +"the manual consistency, the " +"functionality prevents you from deleting any of these chapters once " +"the documentation manual has been created." msgstr "" msgid "manual-nodes.texinfo" msgstr "" msgid "" -"This file can be found inside the language-specific directory and contains " -"the node definitions of all chapters inside the manual. Node definitions in " -"this file are automatically created based on menu definitions (see " -"manual-menu.texinfo file above) and they don't include " -"any content here. Instead, as part of the node definition, the " -"@include command is used to connect each node with its content. " -"Generally, you don't need to edit this file once the documentation manual " -"has been created." +"This file can be found inside the language-specific directory and " +"contains the node definitions of all chapters inside the manual. " +"When functionality creates " +"instances of this file, node definitions inside it are " +"automatically created based on menu definitions (see " +"manual-menu.texinfo file above) and they don't " +"include any content here. Instead, as part of the node definition, " +"the @include command is used to connect each node with " +"its content. Generally, you don't need to edit instances of this " +"file once the documentation manual has been created." msgstr "" msgid "manual-index.texinfo" msgstr "" msgid "" -"This file can be found inside the language-specific directory and contains " -"the Texinfo commands used to generated an organized view of all indexes you " -"defined inside documentation entries so they can be quickly accessed. " -"Generally, you don't need to edit this file once the documentation manual " -"has been created." +"This file can be found inside the language-specific directory and " +"contains the Texinfo commands used to generated an organized view " +"of all indexes you defined inside documentation entries so they can " +"be quickly accessed. Generally, you don't need to edit instnaces of " +"this file once the documentation manual has been created." msgstr "" msgid "manual.conf" msgstr "" msgid "" -"This file contains the initial configuration of documentation manuals " -"written in Texinfo format. When a documentation manual is created for first " -"time, this file is copied into its target directory so you be able of later " -"customizing specific information like menu order, title styles and template " -"assignments. The content of this file is described in ." +"This file contains the initial configuration of documentation " +"manuals written in Texinfo format. When a documentation manual is " +"created for first time, this file is copied into its target " +"directory so you be able to customize specific information like " +"menu order, title styles and template assignments therein. The " +"content of this file is described in ." +msgstr "" + +msgid "Chapters.texinfo" msgstr "" -msgid "chapter.texinfo" +msgid "" +"This file contains Texinfo's main chapter definition used by functionality when new chapters are " +"created inside documentation manuals. When chapters are created for " +"first time, they come without any introduction or documentation " +"entry inside." msgstr "" msgid "" -"This file contains the Texinfo's main chapter definition used by " -"help functionality when new chapters are created inside " -"documentation manuals. When chapters are created for first time, they come " -"without any introduction or documentation entry inside. If you want to add/" -"update any information inside the chapter definition itself, edit the " -"related chapter file inside the documentation manual you are working on, not " -"the template file used to create it." +"In case you need to add/update the chapters definition files, edit " +"the related chapter definition file inside the documentation manual " +"you are working on, not the template file used to create it. To " +"edit the chapter definition file, don't provide any section " +"information in the documentation entry. For example, if you want to " +"update the chapter introduction related to trunk " +"chapter inside tcar-fs documentation manual, use the " +"tcar-fs::trunk: documentation entry." msgstr "" -msgid "chapter-menu.texinfo" +msgid "Chapters-menu.texinfo" msgstr "" msgid "" -"This file is part of Texinfo's main chapter definition and should be " -"initially empty. Later, when chapters are created for first time, this file " -"is copied as it is (i.e., empty) into the documentation manual to store the " -"Texinfo menu entries related to all documentation entries created inside the " -"chapter. The Texinfo menu entries related to documentation entries are " -"automatically created using Texinfo source files as reference." +"This file is part of Texinfo's main chapter definition and should " +"be initially empty. Later, when chapters are created for first " +"time, this file is copied as it is (i.e., empty) into the " +"documentation manual to store the Texinfo menu entries related to " +"all documentation entries created inside the chapter. The Texinfo " +"menu entries related to documentation entries are automatically " +"created using Texinfo source files as reference." msgstr "" -msgid "chapter-nodes.texinfo" +msgid "Chapters-nodes.texinfo" msgstr "" msgid "" -"This file is part of Texinfo's main chapter definition and contains the node " -"definition the help functionality uses as reference to " -"create the list of Texinfo nodes related to all documentation entries " -"created inside the chapter. The node definition of documentation entries is " -"automatically created from the menu definition of documentation entries (see " -"chapter-menu.texinfo file above), once it has been " -"updated from Texinfo source files." +"This file is part of Texinfo's main chapter definition and contains " +"the node definition the " +"functionality uses as reference to create the list of Texinfo nodes " +"related to all documentation entries created inside the chapter. " +"The node definition of documentation entries is automatically " +"created from the menu definition of documentation entries (see " +"Chapters-menu.texinfo file above), once it has " +"been updated from Texinfo source files." msgstr "" msgid "section.texinfo" msgstr "" msgid "" -"This file contains the Texinfo section definition used by help functionality when new documentation entries are created inside " -"the chapters of a documentation manual. When documentation entries are " -"created for first time, they are created as empty documentation entries that " -"you need to fill up with content. Again, if you want to update the content " -"of sections inside the documentation manual, update the related " -"documentation entry inside the documentation manual, not the template file " -"used to create it." +"This file contains the Texinfo section definition used by functionality when new " +"documentation entries are created inside chapters of documentation " +"manuals. When documentation entries are created for first time, " +"they are created as empty documentation entries that you need to " +"fill up with content. Again, if you want to update the content of " +"sections inside the documentation manual, update the related " +"documentation entry inside the documentation manual, not the " +"template file used to create it." msgstr "" msgid "" -"The creation of documentation entries inside the documentation manual is " -"represented by the ${SECTION_NAME}.texinfo file, as " -"described in . " -"In this example, ${SECTION_NAME} is a variable string refering " -"the file name of documentaiton entries. The file names of documentation " -"entries is made of letters, numbers and the minus sign (which is generally " -"used to separate words)." +"The creation of documentation entries inside the documentation " +"manual is represented by the ${SECTION_NAME}.texinfo file, as described in . In this example, " +"${SECTION_NAME} is a variable string referring the file name " +"of documentation entries. The file names of documentation entries " +"are made of letters, numbers and the minus sign (which is generally " +"used as word separator)." msgstr "" msgid "" -"Documentation entries are not limited inside a documentation manual. You can " -"create as many documentation entries as you need to describe the content of " -"your manual." +"Documentation entries are not limited inside chapters of " +"documentation manuals. You can create as many documentation entries " +"as you need to describe the content of your manual." msgstr "" msgid "" -"There are other files which aren't related to manual's source files, but to " -"manual's output files. Such files are described below and can be found " -"either inside or outside the language-specific directories so you can " -"control common and specific output settings through them. These files aren't " -"copied into the directory structure of new documentation manuals created " -"through the help functionality of centos-art." -"sh script. Instead, they remain inside the template directory " -"structure so as to be reused each time the output of documentation manuals " -"is rendered." +"There are other files which aren't related to manual's source " +"files, but to manual's output files. Such files are described below " +"and can be found either inside or outside the language-specific " +"directories so you can control common and specific output settings " +"through them. These files aren't copied into the directory " +"structure of new documentation manuals created through the functionality. Instead, they remain " +"inside the template directory structure so as to be reused each " +"time the output of documentation manuals is rendered." msgstr "" msgid "manual-init.pl" msgstr "" msgid "" -"This file can be found inside and outside language-specific directories and " -"contains the Texi2html initialization script. When this file is outside the " -"language-specific directory, it contains common customizations to all " -"language-specific outputs (e.g., changing the output DTD). When this file is " -"inside the language-specific directory, it contains translations for that " -"language-specific output (e.g., special words like See, Index, Contents, " +"This file can be found inside and outside language-specific " +"directories and contains the Texi2html initialization script. When " +"this file is outside the language-specific directory, it contains " +"common customizations to all language-specific outputs (e.g., " +"changing the output DTD). When this file is inside the language-" +"specific directory, it contains translations for that language-" +"specific output (e.g., special words like See, Index, Contents, " "Top, etc., are localized here)." msgstr "" @@ -2898,35 +3480,38 @@ msgid "manual.sed" msgstr "" msgid "" -"This file can be found inside and outside language-specific directories and " -"contain special transformations for Texi2html output. Again, when this file " -"is inside language-specific directories the transformation have are applied " -"to that language-specific XHTML output and when it is outside language-" -"specific directories the transformations are applied to all language-" -"specific XHTML outputs. Most transformations achived through this file are " -"to produce admonitions since Texinfo documentation format (as in " -"texinfo-4.8-14.el5) doesn't have an internal command to " -"build them." +"This file can be found inside and outside language-specific " +"directories and contains special transformations for Texi2html " +"output. Again, when this file is inside language-specific " +"directories the transformation are applied to that language-" +"specific XHTML output and when it is outside language-specific " +"directories the transformations are applied to all language-" +"specific XHTML outputs. Most transformations achieved through this " +"file are to produce admonitions since Texinfo documentation format " +"(as in texinfo-4.8-14.el5) doesn't have an " +"internal command to build them." msgstr "" -msgid "Texinfo document template" +msgid "Template for texinfo document structures" msgstr "" #, no-wrap msgid "" -"trunk/Scripts/Bash/Functions/Help/Texinfo/Templates\n" -"|-- ${LANG}\n" -"| |-- Chapters\n" -"| | |-- chapter-menu.texinfo\n" -"| | |-- chapter-nodes.texinfo\n" -"| | |-- chapter.texinfo\n" -"| | `-- section.texinfo\n" -"| |-- Licenses\n" +"\n" +"Documentation/Models/Texinfo/Default/\n" +"|-- ${LANG}/\n" +"| |-- Chapters/\n" +"| | |-- section.texinfo\n" +"| | `-- section-functions.texinfo\n" +"| |-- Chapters-menu.texinfo\n" +"| |-- Chapters-nodes.texinfo\n" +"| |-- Chapters.texinfo\n" +"| |-- Licenses/\n" "| | |-- GFDL.texinfo\n" -"| | |-- GPL.texinfo\n" -"| | |-- chapter-menu.texinfo\n" -"| | |-- chapter-nodes.texinfo\n" -"| | `-- chapter.texinfo\n" +"| | `-- GPL.texinfo\n" +"| |-- Licenses-menu.texinfo\n" +"| |-- Licenses-nodes.texinfo\n" +"| |-- Licenses.texinfo\n" "| |-- manual-index.texinfo\n" "| |-- manual-init.pl\n" "| |-- manual-menu.texinfo\n" @@ -2935,30 +3520,39 @@ msgid "" "| |-- manual.sed\n" "| `-- manual.texinfo\n" "|-- manual-init.pl\n" -"`-- manual.sed" +"`-- manual.sed\n" +msgstr "" + +msgid "" +"Inside the directory structure of Texinfo document templates, the " +"Chapters directory stores " +"section specific models used to create and maintain section files " +"inside manuals. File names beginning with Chapters, " +"at the same level of Chapters directory, are used to create chapter specific files " +"inside manuals." msgstr "" msgid "" -"Inside the directory structure of Texinfo document templates, the Chapters directory organizes chapter specific " -"models used to create and maintain both chapter and sections files inside " -"manuals. On the other hand, the Licenses directory organizes the license information linked from all " -"manuals. Notice the license information is not copied into documentation " -"manuals when they are created, but refered from this location where they are " -"maintained. This configuration permites that all documentation manuals " -"written in Texinfo format inside The CentOS Artwork Repository do " -"use the same license information and if a change is committed to the license " -"files, such changes be immediatly propagated to documentation manuals the " -"next time their output files be updated." +"The Licenses directory " +"organizes the license information linked from all manuals. Notice " +"the license information is not copied into documentation manuals " +"when they are created, but referred from models location where they " +"are maintained. This configuration permits all documentation " +"manuals written in Texinfo format inside The CentOS Artwork " +"Repository to use the same license information. This way, " +"if a change is committed to license files, it will be immediately " +"propagated to all documentation manuals the next time their output " +"files be updated." msgstr "" msgid "Document Expansions" msgstr "" msgid "" -"The document expansions are special constructions used to generate content " +"The document expansions are special constructions the functionality provides to generate content " "dynamically inside Texinfo source files." msgstr "" @@ -2966,11 +3560,12 @@ msgid "The SeeAlso Expansion" msgstr "" msgid "" -"This expansion creates a list of links with section entries one level ahead " -"from the section entry being currently processed. In this construction, the " -"TYPE variable can be either itemize, enumerate " -"or menu. When no TYPE variable is provided, the " -"itemize value is considered as default." +"This expansion creates a list of links with section entries one " +"level ahead from the section entry being currently processed. In " +"this construction, the TYPE variable can be either itemize, enumerate or menu. When no " +"TYPE variable is provided, the itemize value is " +"considered as default." msgstr "" #, no-wrap @@ -2980,12 +3575,13 @@ msgid "" msgstr "" msgid "" -"This expansion might result useful when you are documenting the repository " -"file system. For example, if you are currently editing the documentation " -"entry related to trunk/Identity " -"directory and want to create a linkable list of all documentation entries in " -"the first level under it, the code you'll have once the construction be " -"expanded would look like the following:" +"This expansion might result useful when you are documenting the " +"repository file system. For example, if you are currently editing " +"the documentation entry related to Identity directory and want to create a linkable list " +"of all documentation entries in the first level under it, the code " +"you'll have once the construction be expanded would look like the " +"following:" msgstr "" #, no-wrap @@ -3005,34 +3601,36 @@ msgid "" msgstr "" msgid "" -"An interesting thing to notice here is that document expansions are executed " -"each time the related documentation entry is edited or updated. Following " -"with the example above, if the documentation entries related to directories " -"under trunk/Identity changes for " -"some reason (e.g., they are removed from documentation manual), the list " -"generated as result of document expansion will be updated automatically " -"after editing the documentation entry or updating the documentation manual " -"structure." +"An interesting thing to notice here is that document expansions are " +"executed each time the related documentation entry is edited or " +"updated. Following with the example above, if the documentation " +"entries related to directories under Identity changes for some reason (e.g., they are " +"removed from documentation manual), the list generated as result of " +"document expansion will be updated automatically after editing the " +"documentation entry or updating the documentation manual structure." msgstr "" msgid "Document Configuration" msgstr "" msgid "" -"The document configuration is stored in the ${MANUAL_NAME}.conf file, inside the documentation manual directory structure. This " -"file is originally copied from manual.conf template " -"file when the documentation manual is created for first time. The content of " -"${MANUAL_NAME}.conf file is organized in sections. Each " -"section here is written in one line of its own and have the form " -"[section_name]. Under sections, the configuration settings take place " -"through name=\"value\" pairs set in one line each. Notice that " -"quotation marks around the option_value are required. Comments are also " -"possible using the # character at the begining of lines. " -"Comments and empty lines (including tabs and white spaces) are ignored. In " -"case more than one section or option appear with the same name inside the " -"configuration file, the first one found will be used. Nested section " -"definitions are not supported." +"The document configuration is stored in the " +"${MANUAL_NAME}.conf file, inside the documentation " +"manual directory structure. This file is originally copied from " +"manual.conf template file when the " +"documentation manual is created for first time. The content of " +"${MANUAL_NAME}.conf file is organized in " +"sections. Each section here is written in one line of its own and " +"have the form [section_name]. Under sections, the " +"configuration settings take place through name=\"value\" pairs set in one line each. Notice that quotation marks " +"around the option_value are required. Comments are also possible " +"using the # character at the begining of lines. " +"Comments and empty lines (including tabs and white spaces) are " +"ignored. In case more than one section or option appear with the " +"same name inside the configuration file, the first one found will " +"be used. Nested section definitions are not supported." msgstr "" #, no-wrap @@ -3043,32 +3641,33 @@ msgid "" msgstr "" msgid "" -"The ${MANUAL_NAME}.conf file is specific to document " -"templates. If you are using Texinfo document template to create " -"documentation manuals, then the default configuration file for that " -"documentation manual is taken from Texinfo document template directory " -"structure. However, if you are using a document template different to " -"Texinfo document template, the default configuration file will be taken from " -"the related document template directory structure you are creating the " -"documentation manual from." +"The ${MANUAL_NAME}.conf file is specific to " +"document templates. If you are using Texinfo document template to " +"create documentation manuals, then the default configuration file " +"for that documentation manual is taken from Texinfo document " +"template directory structure. However, if you are using a document " +"template different to Texinfo document template, the default " +"configuration file will be taken from the related document template " +"directory structure you are creating the documentation manual from." msgstr "" msgid "The [main] Section" msgstr "" msgid "" -"The [main] section organizes settings that let you customize " -"the way sections and menu definitions are created inside the documentation " -"manual. The following options are available in this section:" +"The [main] section organizes settings that let you " +"customize the way sections and menu definitions are created inside " +"the documentation manual. The following options are available in " +"this section:" msgstr "" msgid "manual_format" msgstr "" msgid "" -"This option specifies the documentation format used by manual. To write " -"documentation manuals in Texinfo format, the value of this option must " -"always be:" +"This option specifies the documentation format used by manual. To " +"write documentation manuals in Texinfo format, the value of this " +"option must always be:" msgstr "" #, no-wrap @@ -3076,20 +3675,23 @@ msgid "manual_format = \"texinfo\"" msgstr "" msgid "" -"Once the documentation manual has been created, you must not change the " -"value of option. This will produce an error." +"Once the documentation manual has been created, you must not change " +"the value of option. This will " +"produce an error because there is not a migration feature available " +"yet. In the future, when you change this value, it must be possible " +"to transform documentation manuals from one format to another." msgstr "" msgid "manual_section_style" msgstr "" msgid "" -"This option specifies the title style used by sections inside the manual. " -"Possible values to this option are `cap-each-word' to capitalize each word " -"in the section title, `cap-first-word' to capitalize the first word in the " -"section title only and `directory' to transform each word in the section " -"title into a directory path. From all these options, `cap-each-word' is the " -"one used as default." +"This option specifies the title style used by sections inside the " +"manual. Possible values to this option are `cap-each-word' to " +"capitalize each word in the section title, `cap-first-word' to " +"capitalize the first word in the section title only and `directory' " +"to transform each word in the section title into a directory path. " +"From all these options, `cap-each-word' is the one used as default." msgstr "" #, no-wrap @@ -3100,955 +3702,2495 @@ msgid "manual_section_order" msgstr "" msgid "" -"This option specifies the order used by sections inside the manual. By " -"default new sections added to the manual are put on the end to follow the " -"section order in which they were `created'. Other possible values to this " -"option are `ordered' and `reversed' to sort the list of sections " -"alphabetically from A-Z and Z-A, respectively." +"This option specifies the order used by sections inside the manual. " +"By default new sections added to the manual are put on the end to " +"follow the section order in which they were `created'. Other " +"possible values to this option are `ordered' and `reversed' to sort " +"the list of sections alphabetically from A-Z and Z-A, respectively." msgstr "" #, no-wrap msgid "manual_section_order = \"created\"" msgstr "" -msgid "The [templates] Section" +msgid "The [templates] Section" +msgstr "" + +msgid "" +"The [templates] section provides the assignment " +"relation between template files and documentation entry files " +"inside the manual. The template definition is set on the left side " +"using relative path and the documentation entry files are described " +"on the right side using a regular expression. The first match wins." +msgstr "" + +#, no-wrap +msgid "Chapters/section.texinfo = \"^.+\\.texinfo$\"" +msgstr "" + +msgid "Document Localization" +msgstr "" + +msgid "" +"To produce localized documentation manuals through Texinfo " +"documentation format it is necessary to create one documentation " +"manual for each language it is desired to support documentation " +"for. Documentation manuals created in this configuration don't have " +"a direct relation among themselves except that one adopted by " +"people writting them to keep their content syncronized. In this " +"configuration translators take one documentation manual as " +"reference (a.k.a. the source manual) and produce several translated " +"manuals based on its content. To keep track of changes inside the " +"source manual, the underlaying version control system must be used " +"considering that there is no direct way to apply gettext The gettext program " +"translates a natural language message into the user's language, by " +"looking up the translation in a message catalog. For more " +"information about the gettext program, run " +"info gettext. procedures to " +"Texinfo source files." +msgstr "" + +msgid "" +"In order to maintain localization of Texinfo source files through " +"gettext procedures, it is necessary to convert " +"the Texinfo source files into XML format first. This way it would " +"be possible to make use of " +"and functionalities to " +"maintain translation messages in different languages through " +"portable objects and producing localized XML files based on such " +"portable objects, respectively. Once the localized XML file is " +"available, it would be a matter of using an XSLT processor (see the " +"xsltproc command) to realize the convertion from " +"XML to a localize Texinfo (or possible other) format. Nevertheless, " +"this workaround fails because the Document Type Definition (DTD) " +"required to validate the XML file produced from makeinfo (as in texinfo-4.8-14.el5) is not " +"availabe inside The CentOS Distribution (release 5.5), nor it is " +"the XSLT files required to realize the transformation itself for " +"such DTD." +msgstr "" + +msgid "" +"Another similar approach to maintain localization of Texinfo source " +"files through gettext procedures would be to " +"convert Texinfo source file to DocBook format; for who the required " +"DTD and XSLT files are available inside The CentOS Distribution. " +"This way, following a procedure similar to that one describe for " +"XML files above, it would be possible to end up having localized " +"DocBook files that can be used as source to produce localized " +"output for both online and printing media. However, the DocBook " +"output produced from makeinfo command (as in " +"texinfo-4.8-14.el5) isn't a valid DocBook " +"document according to DocBook DTDs available inside The CentOS " +"Distribution (release 5.5) thus provoking the validation and " +"transformation of such a malformed document to fail." +msgstr "" + +msgid "Document Language" +msgstr "" + +msgid "" +"The language information of those documentation manuals produced " +"through Texinfo documentation format is declared by Texinfo's " +"@documentlanguage command. This command receives one " +"argument refering the language code (as in ISO-639 standard) and " +"must be set inside the manual's main definition file. Generally, " +"there is no need to change the document language declaration once " +"it has been created by the " +"functionality; unless you mistakently create the manual for a " +"locale code different to that one you previously pretended to do in " +"first place, of course." +msgstr "" + +msgid "" +"The language information used in both Texinfo source files and " +"XHTML output produced by the " +"functionality is determined by the user's session LANG environment variable. This variable can be customized in the " +"graphical login screen before login, or once you've login by " +"explicitly setting the value of LANG environment " +"variable inside the ~/.bash_profile file." +msgstr "" + +msgid "" +"To create documentation manuals in English language the " +"LANG environment variable must be set to en_US." +"UTF-8 or something similar. Likewise, if you want to create " +"documentation manuals in a language other than English, be sure the " +"LANG environment variable is set to the appropriate " +"locale code. The appropriate locale code to set " +"here can be found in the output produced by the locale -a " +"| less command. " +msgstr "" + +msgid "" +"When producing output from Texinfo source files using the " +"makeinfo command (as in the texinfo-4.8-" +"14.el5 package), the language information set by " +"@documentlanguage is ignored in Info and HTML output, " +"but cosidered by Tex program to redefine various English words used " +"in the PDF output (e.g., Chapters, Index, See, and so on) based on the current " +"language set in." +msgstr "" + +msgid "Document Encoding" +msgstr "" + +msgid "" +"The encoding information of documentation manuals produced through " +"Texinfo documentation format is declared by Texinfo's " +"@documentencoding command and can take either US-" +"ASCII, ISO-8859-1, ISO-8859-15 or " +"ISO-8859-2 as argument. Nevertheless, you should be " +"aware that the functionality " +"doesn't declare the @documentencoding inside Texinfo " +"source files. Let's see why." +msgstr "" + +msgid "" +"When the @documentencoding command is set in Texinfo " +"source files, the terminal encoding you use to read the Info output " +"produced from such files must be set to that encoding information " +"you provided as argument to @documentencoding command; " +"this, before using an Info reader to open the Info output file in " +"the terminal. Otherwise, when the terminal and the Texinfo source " +"files encoding definition differ one another, characters defined " +"through Texinfo's special way of producing floating accents won't " +"be displayed as expected (even when the script had to be re-designed in order to accept " +"art.sh script has to be re-designed in order to accept " "such pluggable behavior into the script. We couldn't publish unique " "centos-art.sh.po and centos-art.sh." "mo files because they may contain different information " @@ -1718,8 +1872,8 @@ msgid "" "automatically the first time you run the prepare functionality (which require the locale functionality to be available), or later, by running the " -"following command: centos-art locale trunk/Scripts/Bash --" -"update" +"following command: centos-art locale Scripts/Bash --update" msgstr "" msgid "" @@ -1751,7 +1905,7 @@ msgstr "" #, no-wrap msgid "" "\n" -"/home/centos/Projects/artwork/trunk/\n" +"/home/centos/Projects/artwork/\n" "|-- Locales/\n" "| `-- Scripts/\n" "| `-- Bash/\n" @@ -1816,7 +1970,7 @@ msgstr "" #, no-wrap msgid "" "\n" -"/home/al/Projects/Myapp/trunk/\n" +"/home/al/Projects/Myapp/\n" "|-- Locales/ \n" "| `-- Scripts/\n" "| `-- Bash/ \n" @@ -1902,15 +2056,304 @@ msgid "" "copy." msgstr "" -msgid "Update DocBook Documentation Structure And Processing" +msgid "Enhance The CentOS Logo Construction" msgstr "" -msgid "..." +msgid "" +"The CentOS Logo is made of two different components known as The " +"CentOS Symbol and The CentOS Type. Presently (at the end of " +"September), to produce these components, we create one " +"SVG image for each PNG image we want to produce, " +"store it in Identity/Models/Brands/" +"Logos directory structure and run the command:" +msgstr "" + +msgid "centos-art render Identity/Images/Brands/Logos" +msgstr "" + +msgid "" +"This model works and scales well in situations when there isn't a " +"need to reuse final images among themselves. However, when you need " +"to reuse images among themselves, a better solution is required. " +"The goal here would be: don't create SVG images " +"for PNG images you can build based on other PNG images." +msgstr "" + +msgid "This might be achieved through one of the following ways:" +msgstr "" + +msgid "" +"Create a new specific functionality to achieved the goal. Needed " +"because the specific " +"functionality uses SVG files as reference to " +"build images (i.e., one SVG image produces one " +"PNG image)." +msgstr "" + +msgid "" +"Modify functionality to " +"work in different modes based on file type or file extension. The " +"first mode would use SVG files as reference to " +"build PNG images (just as it was doing so far). The second mode " +"would use a configuration file named render.conf as reference inside the design models directory you want " +"to produce images for so as to build the related PNG images. In " +"this second case, the configuration file specifies how final PNG " +"images will be produced (e.g., by appending or overlapping them one " +"another)." +msgstr "" + +msgid "For example, consider the following command-line:" +msgstr "" + +msgid "" +"This command should evaluate which type of rendition will be done, " +"based on whether the source file is a scalable vector graphic " +"(SVG) or a configuration file. To make this " +"decision, the centos-art.sh script looks for " +"SVG files first, and configuration files later. " +"When SVG files are found, the centos-" +"art.sh script uses a list of SVG files " +"and process them one by one excluding any related configuration " +"file that could exist. On the other hand, if no SVG file is found inside the related design model directory " +"structure, the centos-art.sh script will use the " +"configuration file with the name render.conf " +"to create images as specified inside it. When neither a " +"SVG or a configuration file is found inside the " +"design model directory structure, the centos-art.sh script finishes its execution without any error message. " +"For example, if no SVG file is found inside " +"Identity/Models/Brands/Logos/ directory and the Identity/Models/Brands/Logos/" +"images.conf configuration file exists therein with the " +"following content:" +msgstr "" + +#, no-wrap +msgid "" +"\n" +"[centos.png]\n" +"models = \"Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz\"\n" +"formats = \"xpm jpg\"\n" +"heights = \"48 78\"\n" +"fgcolor = \"000000 ffffff\"\n" +"bgcolor = \"ffffff-0\"\n" +"command = \"/usr/bin/convert +append\"\n" +"\n" +"[centos-artwork.png]\n" +"models = \"Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz Identity/Models/Brands/Types/artwork.svgz\"\n" +"formats = \"xpm jpg\"\n" +"heights = \"48 78\"\n" +"fgcolor = \"000000 ffffff\"\n" +"bgcolor = \"ffffff-0\"\n" +"command = \"/usr/bin/convert +append\"\n" +msgstr "" + +msgid "" +"The centos-art.sh script should produce the " +"following image files:" +msgstr "" + +#, no-wrap +msgid "" +"\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.jpg\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.png\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.xpm\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.png\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.jpg\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.xmp\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.jpg\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.png\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.xpm\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.png\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.jpg\n" +"Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.xmp\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.jpg\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.png\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.xpm\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.png\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.jpg\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.xmp\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.jpg\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.png\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.xpm\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.png\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.jpg\n" +"Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.xmp\n" +msgstr "" + +msgid "" +"The final location for storing images output inside the repository " +"is determined by using the design model directory provided as " +"argument. Basically, the centos-art.sh script " +"changes the path components from Models to Images and adds " +"foreground color, background color, height value and image name to " +"it to differentiate rendered images." +msgstr "" + +msgid "" +"In case you need to restrict the amount of files you want to " +"produce including their formats, heights, colors and commands, you " +"need to modify the content of the related render.conf configuration file. There is not any command-line option " +"available for such tasks. The most command-line options can do for you " +"is when there are more than one configuration file inside the same " +"design model directory and you need to specify which one of them " +"will be used as reference. In such case you can use the option." +msgstr "" + +msgid "" +"When images are produced through configuration files, the " +"centos-art.sh script takes the order provided in " +"the list of design models to build the list of images you will work " +"with through the command specified. For example, the order in which " +"images will be appended or overlapped." +msgstr "" + +msgid "" +"Localization of logo images will not be and must not be supported " +"in any way. That would bring disastrous confusion in the area of " +"visual recognition." +msgstr "" + +msgid "2013's" +msgstr "" + +msgid "" +"The CentOS Artwork Repository development was eventually " +"stopped at November, 2012, when I moved myself from Cienfuegos to " +"Havana city for working The first months were very difficult, " +"specially at the moment of finding a stable place to set my " +"personal desktop (I was moving myself from one apartment to " +"another, frequently)." +msgstr "" + +msgid "" +"On May 14th, the work in Havana ends for me and I have to return to " +"Cienfuegos city. I tried to take advantage of the situation " +"dedicating more work and study hours to The CentOS Artwork " +"Repository and the related automation scripts once again. " +"At this point I consider a Git+Gitolite+Gitweb+MantisBT " +"infrastructure for The CentOS Artwork Repository and " +"start working on it in my workstation. This, in order to implement " +"a distributed work flow for The CentOS Artwork Repository based on Git version control system." +msgstr "" + +msgid "Update Version Control Environment" +msgstr "" + +msgid "" +"The function environment related to version control tasks was " +"renamed from svn to in order to handle both Subversion and Git working copies of " +"The CentOS Artwork Repository. This change prepares the " +"centos-art.sh script to follow the suggestion of " +"a complete migration from Subversion to " +"Git, at some point." +msgstr "" + +msgid "" +"Because the Subversion infrastructure is " +"the one in place right now and it is the one with most artwork " +"history, it will be Subversion the " +"version control system we are using as default in centos-" +"art.sh. However this will surely change as soon as a " +"Git infrastructure be approved for " +"The CentOS Artwork Repository and everything could be " +"moved there." +msgstr "" + +msgid "Start Using The centos-art.conf File" +msgstr "" + +msgid "" +"Based on the need of supporting more than one application to handle " +"version control tasks, it was added the centos-art.conf file into the Scripts/Bash directory. This file exists to customize specific " +"behaviours of centos-art.sh script once it has " +"been executed (e.g., what kind of application will be used as " +"default for doing version control, or even if the actions related " +"to version control will be performed or not)." +msgstr "" + +msgid "Update Repository Directories Structure" +msgstr "" + +msgid "" +"I face the following situation: I am working on a documentation " +"project named solinfo-network. While I was " +"organizing it, I found that the directory structure of The " +"CentOS Artwork Repository fits quite well the needs of " +"solinfo-network documentation project. However, I " +"don't want to duplicate automation scripts in two separate " +"projects, but share them between themselves (i.e., changes " +"committed to automation scripts are pushed to one single place, not " +"two.)." +msgstr "" + +msgid "" +"When we use Subversion repositories, it is possible to checkout " +"specific parts of different repositories into a new repository. " +"This is very useful if we need to create several projects that " +"share the same component and we don't want to duplicate the common " +"component in two or more different projects but share it between them. See ." +msgstr "" + +msgid "" +"When we use Git repository, it is not possible to checkout specific " +"parts of a repository but the complete tree. So, in order to share " +"common components of a repository we need to create one repository " +"for each common component we want to share and then use Git " +"submodulessee progit-book, page 152. This " +"requires that brand new repositories be created for each component " +"we want to share." +msgstr "" + +msgid "" +"In both situations, including Git and Subversion repositories, it " +"is necessary that we define very well the structure of each " +"component we want to share, so it can be plugged " +"nicely into other projects. Likewise, other projects must have the " +"same directory structure the pluggable component was design to fit " +"in. If these two conditions can be reached, it would be possible to " +"reuse repositories components and concentrate efforts. The current " +"directory structure The CentOS Artwork Repository is " +"set in allows components inside Subversion repositories to be " +"reused by related working copies. However, we cannot do the same if " +"it is stored in a Git repository. In order for Git repositories to " +"be able to share components with other Git repositories, The " +"CentOS Artwork Repository directory structure needs to be " +"reorganized to better delineate each component the repository is " +"made of." +msgstr "" + +msgid "For more information see ." msgstr "" msgid "Corporate Visual Identity" msgstr "" +msgid "..." +msgstr "" + msgid "The CentOS Project" msgstr "" @@ -2034,7 +2477,7 @@ msgid "" msgstr "" msgid "" -"The CentOS Showroom — This visual manifestation exists to cover all " +"The CentOS Symbol — This visual manifestation exists to cover all " "actions related to artwork production required by The CentOS Project to " "manifest its existence through media produced industrially (e.g., " @@ -2144,7 +2587,7 @@ msgid "" "architectures." msgstr "" -msgid "The CentOS Showroom" +msgid "The CentOS Symbol" msgstr "" msgid "" @@ -2226,7 +2669,7 @@ msgid "" "The CentOS " "Project, as organization, is mainly made of (but not " "limited to) three visual manifestions: The CentOS Distribution, The " -"CentOS Web and The CentOS Showroom. Inside The CentOS Distribution " +"CentOS Web and The CentOS Symbol. Inside The CentOS Distribution " "visual manifestations, The CentOS Project maintains near to four different " "major releases of The CentOS Distribution, parallely in time. " @@ -2234,10 +2677,9 @@ msgid "" "is produced for no specific release information (e.g., there is no " "a complete web site for each major release of The CentOS " "Distribution individually, but one web site to cover them all). " -"Likewise, the content produced in The CentOS Showroom is " -"industrially created for no specific release, but The CentOS Project in " -"general." +"Likewise, the content produced in The CentOS Symbol is industrially " +"created for no specific release, but The CentOS Project in general." msgstr "" msgid "" @@ -2250,7 +2692,7 @@ msgid "" "The CentOS Distribution, which one of those different visual styles " "would be used to cover the remaining visual manifestations The CentOS Project is made of (e.g., The CentOS Web and The CentOS Showroom)?" +"ulink> is made of (e.g., The CentOS Web and The CentOS Symbol)?" msgstr "" msgid "" @@ -2354,21 +2796,63 @@ msgid "" "\"mailto:centos-devel@centos.org\">centos-devel@centos.org)." msgstr "" -msgid "The CentOS Symbol" +msgid "" +"The CentOS Symbol is the graphical part of The CentOS Logo. As The " +"CentOS Logo, The CentOS Symbol is used to brand " +"images produced by The CentOS Project and provide a visual connection " +"between images so they can be monolithically recognized as part of " +"The CentOS " +"Project. The CentOS Symbol must be exactly the same every " +"time it is printed out and a route to reproduce it in such a way " +"must be available so as to avoid reproduction mistakes when images " +"are branded with it." msgstr "" msgid "The CentOS Type" msgstr "" +msgid "" +"The CentOS Type is the typographical part of The CentOS Logo. " +"Comparing with both The CentOS Logo and The CentOS Symbol, The " +"CentOS Type by its own, provides poor visual connection between " +"images that intend to be recognized as a monolithic part of The CentOS Project and shouldn't be used alone. Instead, The CentOS Logo or The " +"CentOS Symbol are preferred. The CentOS Symbol must be exactly the " +"same every time it is printed out and a route to reproduce it in " +"such a way must be available so as to avoid reproduction mistakes " +"when images are branded with it." +msgstr "" + msgid "The CentOS Logo" msgstr "" +msgid "" +"The CentOS Logo is a construction made of The CentOS Symbol and The " +"CentOS Type. The CentOS Symbol and The CentOS Logo are the main " +"visual manifestations of the organization known as The CentOS Project. " +"As The CentOS Symbol, The CentOS Logo is used to brand images produced by The CentOS Project and provide a visual " +"connection between images so they can be monolithically recognized " +"as part of The " +"CentOS Project. The CentOS Logo must be exactly the same " +"every time it is printed out and a route to reproduce it in such a " +"way must be available so as to avoid reproduction mistakes when " +"images are branded with it." +msgstr "" + msgid "The CentOS Motif" msgstr "" msgid "Release Schema" msgstr "" +msgid "The CentOS Showroom" +msgstr "" + msgid "" "The CentOS Artwork Repository documentation work line is " @@ -2426,9 +2910,9 @@ msgstr "" msgid "" "Before The CentOS Artwork Repository File System documentation manual exist, there was an emerging need " -"to understand what each directory inside the growing directory " -"layout was for, how they could be used and how they could be " +"citetitle> documentation manual would exist, there was an emerging " +"need to understand what each directory inside the growing directory " +"layout was for, how it could be used and each directory could be " "connected one another. At that moment, the directory layout was " "very unstable and explaining the whole idea behind it was not " "possible, there were too many changing concepts floating around " @@ -2439,18 +2923,18 @@ msgstr "" msgid "" "The The CentOS Artwork Repository File System manual was conceived based on the idea of individually " -"documenting each directory inside the repository and, later, by " -"considering all directory documentations together, it would be " +"citetitle> manual was conceived based on the idea of documenting " +"each directory inside the repository individually and, later, by " +"considering all directory documentations altogether, it would be " "(hypothetically) possible to correct the whole idea through an " -"improvement cycle that would consolidate the final idea we try to " -"implement." +"improvement cycle that would consolidate the final idea we were " +"trying to implement." msgstr "" msgid "" "Other documentation manuals can be based on reasons different from " -"those described above, however, no matter what those reasons be, it " -"will be helpful to make yourself a clean idea about what you are " +"those described above, however, no matter what those reasons are, " +"it will be helpful to make yourself a clean idea about what you are " "going to document exactly before putting your hands on it." msgstr "" @@ -2459,7 +2943,7 @@ msgstr "" msgid "" "Once you've make yourself an clean idea of what the documentation " -"manual is for and the needs behind, it is time for you to define " +"manual is for and the needs behind it, it is time for you to define " "the manual's title and the manual's directory name. Both manuals' " "title and manual's directory name describe what the documentation " "manual is about. The manual's title is used inside the " @@ -2489,36 +2973,39 @@ msgid "" msgstr "" msgid "" -"The document structure of documentation manuals is specific to that " -"documentation format used to write documentation source files. " -"Nevertheless, no matter what the documentation format be, the " -"document structure produce produced from the help functionality of centos-art.sh script " -"follows and upside-down tree configuration. In this configuration, " -"documentation manuals can be organized through parts, chapters, " -"sections, and several subsection levels based in whether the chosen " -"documentation format supports them or not." +"The specific document structure you choose for a documentation " +"manuals is affected by the documentation format you use to write " +"documentation source files. Nevertheless, no matter what the " +"documentation format be, the document structure produced from the " +" functionality will always " +"follow and upside-down tree configuration for document structures. " +"In this configuration, documentation manuals can be organized " +"through different structural levels (e.g., parts, chapters, " +"sections, subsection, etc.) based on the support provided by the " +"documentation format you chose." msgstr "" msgid "" -"Considering the The CentOS Artwork Repository File " -"System documentation manual, we already know that it " -"was conceived to document each directory structure The " -"CentOS Artwork Repository is made of using Texinfo format " -"and the sectioning levels supported by it. At this point we phase " -"that The CentOS Artwork Repository has more levels " -"deep than sectioning commands available inside Texinfo formats. " -"This way it is not possible to use one sectioning command for each " -"directory level inside the repository directory structure we need " -"to document. Based on these issues, it is imperative to " -"reaccomodate the document structure in order to be able of " -"documenting every directory The CentOS Artwork Repository File System documentation manual was conceived to document each " +"directory structure The CentOS Artwork Repository is " +"made of, using Texinfo as main documentation format." +msgstr "" + +msgid "" +"At this point we find that The CentOS Artwork Repository is made of, using the sectioning levels supported by most " -"documentation formats inside The CentOS Distribution, no matter how " -"many levels deep the repository directory structure has." +"ulink> had more levels deep than sectioning commands available " +"inside documentation format. This way it is not possible to use one " +"sectioning command for each directory level inside the repository " +"directory structure we need to document. Based on these issues, it " +"is imperative to re-accommodate the document structure in order to " +"be able of documenting every directory The CentOS Artwork " +"Repository is made of, using the sectioning levels " +"supported by that documentation format we chose, no matter how many " +"levels deep the repository directory structure had." msgstr "" msgid "" @@ -2576,10 +3063,8 @@ msgid "" "This appendix is confined to organize licenses mentioned in the " "manual. The content of this appendix is out of documenatation " "manual scope itself and is shared among all documentation manuals " -"written through the help of centos-" -"art.sh script inside The CentOS Artwork Repository." +"written through the " +"functionality." msgstr "" msgid "Index" @@ -2594,14 +3079,15 @@ msgstr "" msgid "" "The document structure illustrated above is also considered the " -"default document structure used by the help " -"functionality of centos-art.sh script when you " -"produce new documentation manuals inside The CentOS Artwork " -"Repository. In contrast with document structure illustrated " -"above, the default document structure used by help functionality doesn't include sectioning constructions " -"like parts, chapters, sections, subsections and the like. Such " +"default document structure used by the functionality of centos-art.sh script " +"when you produce new documentation manuals inside The " +"CentOS Artwork Repository. In contrast with document " +"structure illustrated above, the default document structure used by " +" functionality doesn't include " +"sectioning constructions like parts, chapters, sections, " +"subsections and the like in the document structure created. Such " "structuring constructions should be specified by you when building " "the documentation manual. The only exceptions to this restriction " "are sectioning structures used to organize contents like " @@ -2615,226 +3101,122 @@ msgid "Implementing Document Structure" msgstr "" msgid "" -"This section describes the steps you should follow to implement " -"document structures like that one described in ." +"The document structure implementation is automated by the functionality, as described in " +"." msgstr "" -msgid "Creating Document Structure" +msgid "Maintaining Document Structure" msgstr "" msgid "" -"To create new documentation manuals inside The CentOS Artwork " -"Repository you need to use the help " -"functionality of centos-art.sh script, as shown " -"in the following command:" +"The document structure maintenance is implemented by the functionality, as described in " +"." msgstr "" -#, no-wrap -msgid "centos-art help --edit \"manual-name\"" -msgstr "" - -msgid "" -"The first time you execute this command, you will be prompted to " -"enter manual specific information like document format, document " -"title, document subtitle, document author, etc. Once this " -"information has been collected the help " -"functionality performs some repository verifications and creates " -"the manual source files inside the manual's directory name you " -"specified as manual-name." +msgid "Documentation Formats" msgstr "" msgid "" -"When you create new documentation manuals, take care of the locale " -"information you are currently using. This information is generally " -"set in the LANG environment variable and is used by " -"the help functionality of centos-art." -"sh script to define the language of new documentation " -"manual and the document template used to build it, as well." +"The CentOS Distribution provides support for different " +"documentation formats, including Texinfo, LaTeX, DocBook and " +"LinuxDoc. These formats have their own specifications and " +"requirements to create and maintain documentation manuals written " +"through them. Inside The CentOS Artwork Repository, the " +" functionality provides the " +"interface you use to create and maintain documentation manuals " +"without needing to take care the underlaying structuring tasks." msgstr "" msgid "" -"Once the documentation structure has been created this way, the " -"recently created documentation manual is ready to receive new " -"chapters and sections as it is described in ." +"This chapter describes how the functionality implements the different documentation source " +"formats available inside The CentOS Distribution, and the " +"internationalization issues related to documentation manuals " +"produced through them." msgstr "" -msgid "Maintaining Document Structure" +msgid "Texinfo" msgstr "" msgid "" -"This section describes the steps you should follow to maintain " -"documentation structures like that one described in ." -msgstr "" - -msgid "Editing Document Structure" +"This section describes the implementation of Texinfo documentation " +"format inside the " +"functionality of centos-art.sh script. In this " +"section we assume you have a basic understanding of Texinfo " +"documentation system. Otherwise, if you don't know what Texinfo " +"documentation system is, read the Texinfo manual first (e.g., by " +"running the info texinfo command) and then, come " +"back here." msgstr "" -msgid "centos-art help --edit \"tcar-fs::trunk\"" +msgid "Document Structure" msgstr "" msgid "" -"This command creates the base structure for the trunk chapter and opens its main definition file with your " -"favorite text editor so you can update the chapter introduction. " -"This very same procedure is used to create branches " -"and tags chapters, just be sure to change the " -"chapter field accordingly." -msgstr "" - -msgid "centos-art help --edit \"tcar-fs::trunk:identity\"" +"The functionality of " +"centos-art.sh provides a document structure that " +"makes documentation manuals created through it to be scalable and " +"maintainable through time. This document structure follows the idea " +"of an upside-down tree to organize chapters, sections, subsections " +"and the like, as described in ." msgstr "" msgid "" -"This command creates the identity section inside the " -"trunk chapter. If the chapter doesn't exist it will " -"be created first. In this command, the identity " -"section refers to trunk/Identity directory inside The CentOS Artwork Repository. In order to document other directories, follow the same " -"procedure but using minus signs to separate directories. For " -"example, to document the trunk/" -"Identity/Models/Themes directory you should use " -"the tcar-fs::trunk:identity-models-themes documentation entry." +"The functionality creates " +"documentation manuals source files in the Documentation/Models/Texinfo/ directory " +"and saves output produced from them in the Documentation/Manuals/Texinfo/ directory. " +"To produce documentation manuals initial source files, the functionality uses Texinfo " +"documentation templates, as described in ." msgstr "" msgid "" -"In the very specific case of TCAR-FS manual, " -"it is also possible to refer chapters and sections using a " -"path/to/dir " -"format. For example, the reference tcar-fs::trunk:" -"identity-models-themes can be also specified as " -"trunk/Identity/Models/Themes, in case you feel more confortable with it than " -"the former one." +"Inside the documentation models directory, source files are stored " +"inside language-specific directories. The language-specific " +"directories are necessary to implement internationalization of " +"Texinfo source files, as described in ." msgstr "" -msgid "Copying Document Structure" +msgid "" +"Inside the language-specific directory, the following files exist " +"to store the manual's main definitions (e.g., title, subtitle, " +"author, copyright notice, chapters, appendixes, indexes and all " +"similar stuff a documentation manual usually has). In addition to " +"these files, there is one directory for each chapter created inside " +"the manual. Inside each chapter directory, you'll find the files " +"controlling the section definitions related each chapter they " +"belong to. The section files (a.k.a. documentation entries) are suffixed with a texinfo extension and named arbitrarily, as it is illustrated in " +". " +"Inside section files it is where you write the manual's content " +"itself." msgstr "" -msgid "Deleting Document Structure" -msgstr "" - -msgid "Renaming Document Structure" -msgstr "" - -msgid "Updating Document Structure" -msgstr "" - -msgid "Documentation Formats" -msgstr "" - -msgid "" -"The CentOS Distribution provides support for different " -"documentation formats, including Texinfo, LaTeX, DocBook and " -"LinuxDoc. These formats have their own specifications and " -"requirements to create and maintain documentation manuals written " -"through them. Inside The CentOS Artwork Repository, the " -"help functionality of centos-art.sh script provides an interface where documentation format " -"specifications have been already considered for you to be able of " -"creating and maintaining documentation manuals without needing to " -"take care of those underlaying structuring tasks." -msgstr "" - -msgid "" -"This chapter describes how the help " -"functionality of centos-art.sh script implements " -"the different documentation source formats available inside The " -"CentOS Distribution, and the internationalization issues related to " -"documentation manuals produced through them." -msgstr "" - -msgid "Texinfo" -msgstr "" - -msgid "" -"This section describes the implementation of Texinfo documentation " -"format inside the help functionality of " -"centos-art.sh script described in . In this section we assume you have a basic " -"understanding of Texinfo documentation system. Otherwise, if you " -"don't know what Texinfo documentation system is, read the Texinfo " -"manual first (e.g., by running the info texinfo " -"command) and then, come back here." -msgstr "" - -msgid "Document Structure" -msgstr "" - -msgid "" -"The help functionality of centos-art." -"sh provides a document structure that makes documentation " -"manuals created through it to be scalable and maintainable through " -"time. This document structure follows the idea of an upside-down " -"tree to organize chapters, sections, subsections and the like, as " -"described in ." -msgstr "" - -msgid "" -"The first time you use the help functionality " -"to create a documentation manual in Texinfo format, the " -"help functionality considers the working " -"directory you are placed in to determine where to store the " -"documentation manual source files. When the current working " -"directory is branches/Manuals/" -"Texinfo, the documentation manual directory is created " -"therein. On all other situations, the documentation manual " -"directory is created under trunk/" -"Manuals directory. Once the documentation manual " -"directory has been created, the help " -"functionality creates the related definition files using Texinfo " -"documentation templates, as described in ." -msgstr "" - -msgid "" -"Inside the documentation manual directory, source files are stored " -"inside language-specific directories. The language-specific " -"directories are necessary to implement internationalization of " -"Texinfo source files, as described in ." -msgstr "" - -msgid "" -"Inside the language-specific directory, the following files exist " -"to store the manual's main definitions (e.g., title, subtitle, " -"author, copyright notice, chapters, appendixes, indexes and all the " -"similar stuff a documentation manual would have). In addition to " -"these files, there is one directory for each chapter created inside " -"the manual. Inside each chapter directory, you'll found the files " -"controlling the section definitions related to that chapter they " -"belong to. The section files (a.k.a. documentation entries) are suffixed with a texinfo extension and named arbitrarily, as it is illustrated in " -". " -"Inside section files it is where you write the manual's content " -"itself." -msgstr "" - -msgid "Texinfo document structure" +msgid "Texinfo document structure" msgstr "" #, no-wrap msgid "" -"trunk/Manuals/${MANUAL_NAME}\n" +"Documentation/Models/Texinfo/${MANUAL_NAME}\n" "`-- ${LANG}\n" -" |-- ${CHAPTER_NAME}\n" -" | |-- chapter-menu.texinfo\n" -" | |-- chapter-nodes.texinfo\n" -" | |-- chapter.texinfo\n" +" |-- ${CHAPTER_NAME}/\n" " | `-- ${SECTION_NAME}.texinfo\n" -" |-- Licenses\n" -" | |-- chapter-menu.texinfo\n" -" | |-- chapter-nodes.texinfo\n" -" | `-- chapter.texinfo\n" +" |-- ${CHAPTER_NAME}-menu.texinfo\n" +" |-- ${CHAPTER_NAME}-nodes.texinfo\n" +" |-- ${CHAPTER_NAME}.texinfo\n" +" |-- Licenses -> Documentation/Models/Texinfo/Default/${LANG}/Licenses\n" +" |-- Licenses-menu.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses-menu.texinfo\n" +" |-- Licenses-nodes.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses-nodes.texinfo\n" +" |-- Licenses.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses.texinfo\n" " |-- ${MANUAL_NAME}.conf\n" " |-- ${MANUAL_NAME}-index.texinfo\n" " |-- ${MANUAL_NAME}-menu.texinfo\n" @@ -2845,10 +3227,10 @@ msgstr "" msgid "" "Texinfo (as in texinfo-4.8-14.el5) doesn't " "support part sectioning inside documentation manuals, so neither " -"does the help functionality of centos-" -"art.sh script. Nevertheless, you can create several " -"documentation manuals and considered them as " -"part of a bigger documentation manual to workaround this issue." +"the functionality does. " +"Nevertheless, you can create several documentation manuals and " +"consider them as part of a bigger documentation manual to " +"workaround this issue." msgstr "" msgid "" @@ -2856,18 +3238,18 @@ msgid "" "chapters and sections is not limitted. You can create as many " "documenation manuals, chapters and sections as you need. The only " "limitation would be the amount of free space required to store the " -"Texinfo source files and the output files produced from them." +"Texinfo source files and the output files produced from them in " +"your workstation." msgstr "" msgid "Document Templates" msgstr "" msgid "" -"Texinfo document templates provide the initial state the " -"help functionality of centos-art.sh script needs in order to create and maintain document " -"structures, as that one described in ." +"Texinfo document templates provide the initial document structure " +"the functionality needs in " +"order to create and maintain document structures, as described in " +"." msgstr "" msgid "" @@ -2881,22 +3263,18 @@ msgid "" "your current locale is English language or when you are creating/" "editing a documentation manual in a language other than English, " "but no language-specific document template for that language exists " -"in the directory:" -msgstr "" - -#, no-wrap -msgid "" -"\n" -"trunk/Scripts/Bash/Functions/Help/Texinfo/Templates" +"in the Scripts/Documentation/Models/" +"Texinfo/Default/ directory." msgstr "" msgid "" -"This directory organizes all Texinfo document templates using the " -"format LL_CC, where LL is the language code (as in ISO-639) and CC " -"the country code (as in ISO-3166). The directory structure of " -"Texinfo document templates is illustrated in the and implemented " -"through the following files:" +"The Scripts/Documentation/Models/" +"Texinfo/Default/ directory organizes all Texinfo " +"document templates using the format LL_CC, where LL is the language " +"code (as in ISO-639) and CC the country code (as in ISO-3166). The " +"directory structure of Texinfo document templates is illustrated in " +"the " +"and implemented through the following files:" msgstr "" msgid "manual.texinfo" @@ -2913,27 +3291,30 @@ msgstr "" msgid "" "This file can be found inside the language-specific directory and " -"contains the menu definitions of chapters inside the manual. Menu " -"definitions in this file are automatically updated when a new " -"chapter is created or deleted through the help " -"functionality of centos-art.sh script. " -"Generally, you don't need to edit this file once the documentation " -"manual has been created." +"contains the menu definitions of chapters inside the manual. When " +" functionality creates " +"instances of this file, menu definitions inside it are " +"automatically updated when a new chapter is created or deleted " +"through the functionality. " +"Generally, you don't need to edit instances of this file once the " +"documentation manual has been created." msgstr "" msgid "" "When a documentation manual is created for first time, this file is " "copied from Texinfo document template directory structure to the " "documentation manual being currently created. At this specific " -"moment, this file contains the following Texinfo menu definition:" +"moment, the instance created contains the following Texinfo menu " +"definition:" msgstr "" #, no-wrap msgid "" +"\n" "@menu\n" "* Licenses::\n" "* Index::\n" -"@end menu" +"@end menu\n" msgstr "" msgid "" @@ -2941,10 +3322,10 @@ msgid "" "manual, the content of this file varies adding or deleting menu " "entries accordingly. Nevertheless, the two entries shown above are " "ignored when new chapters are added to or removed from the list, so " -"they will always be present in this file. To preserve the manual " -"consistency, the help functionality prevents " -"you from deleting any of these chapters once the documentation " -"manual has been created." +"they will always be present in instances of this file. To preserve " +"the manual consistency, the " +"functionality prevents you from deleting any of these chapters once " +"the documentation manual has been created." msgstr "" msgid "manual-nodes.texinfo" @@ -2953,12 +3334,14 @@ msgstr "" msgid "" "This file can be found inside the language-specific directory and " "contains the node definitions of all chapters inside the manual. " -"Node definitions in this file are automatically created based on " -"menu definitions (see manual-menu.texinfo file " -"above) and they don't include any content here. Instead, as part of " -"the node definition, the @include command is used to " -"connect each node with its content. Generally, you don't need to " -"edit this file once the documentation manual has been created." +"When functionality creates " +"instances of this file, node definitions inside it are " +"automatically created based on menu definitions (see " +"manual-menu.texinfo file above) and they don't " +"include any content here. Instead, as part of the node definition, " +"the @include command is used to connect each node with " +"its content. Generally, you don't need to edit instances of this " +"file once the documentation manual has been created." msgstr "" msgid "manual-index.texinfo" @@ -2968,8 +3351,8 @@ msgid "" "This file can be found inside the language-specific directory and " "contains the Texinfo commands used to generated an organized view " "of all indexes you defined inside documentation entries so they can " -"be quickly accessed. Generally, you don't need to edit this file " -"once the documentation manual has been created." +"be quickly accessed. Generally, you don't need to edit instnaces of " +"this file once the documentation manual has been created." msgstr "" msgid "manual.conf" @@ -2979,27 +3362,35 @@ msgid "" "This file contains the initial configuration of documentation " "manuals written in Texinfo format. When a documentation manual is " "created for first time, this file is copied into its target " -"directory so you be able of later customizing specific information " -"like menu order, title styles and template assignments. The content " -"of this file is described in ." +"directory so you be able to customize specific information like " +"menu order, title styles and template assignments therein. The " +"content of this file is described in ." msgstr "" -msgid "chapter.texinfo" +msgid "Chapters.texinfo" msgstr "" msgid "" -"This file contains the Texinfo's main chapter definition used by " -"help functionality when new chapters are " +"This file contains Texinfo's main chapter definition used by functionality when new chapters are " "created inside documentation manuals. When chapters are created for " "first time, they come without any introduction or documentation " -"entry inside. If you want to add/update any information inside the " -"chapter definition itself, edit the related chapter file inside the " -"documentation manual you are working on, not the template file used " -"to create it." +"entry inside." +msgstr "" + +msgid "" +"In case you need to add/update the chapters definition files, edit " +"the related chapter definition file inside the documentation manual " +"you are working on, not the template file used to create it. To " +"edit the chapter definition file, don't provide any section " +"information in the documentation entry. For example, if you want to " +"update the chapter introduction related to trunk " +"chapter inside tcar-fs documentation manual, use the " +"tcar-fs::trunk: documentation entry." msgstr "" -msgid "chapter-menu.texinfo" +msgid "Chapters-menu.texinfo" msgstr "" msgid "" @@ -3012,33 +3403,33 @@ msgid "" "created using Texinfo source files as reference." msgstr "" -msgid "chapter-nodes.texinfo" +msgid "Chapters-nodes.texinfo" msgstr "" msgid "" "This file is part of Texinfo's main chapter definition and contains " -"the node definition the help functionality " -"uses as reference to create the list of Texinfo nodes related to " -"all documentation entries created inside the chapter. The node " -"definition of documentation entries is automatically created from " -"the menu definition of documentation entries (see chapter-" -"menu.texinfo file above), once it has been updated from " -"Texinfo source files." +"the node definition the " +"functionality uses as reference to create the list of Texinfo nodes " +"related to all documentation entries created inside the chapter. " +"The node definition of documentation entries is automatically " +"created from the menu definition of documentation entries (see " +"Chapters-menu.texinfo file above), once it has " +"been updated from Texinfo source files." msgstr "" msgid "section.texinfo" msgstr "" msgid "" -"This file contains the Texinfo section definition used by " -"help functionality when new documentation " -"entries are created inside the chapters of a documentation manual. " -"When documentation entries are created for first time, they are " -"created as empty documentation entries that you need to fill up " -"with content. Again, if you want to update the content of sections " -"inside the documentation manual, update the related documentation " -"entry inside the documentation manual, not the template file used " -"to create it." +"This file contains the Texinfo section definition used by functionality when new " +"documentation entries are created inside chapters of documentation " +"manuals. When documentation entries are created for first time, " +"they are created as empty documentation entries that you need to " +"fill up with content. Again, if you want to update the content of " +"sections inside the documentation manual, update the related " +"documentation entry inside the documentation manual, not the " +"template file used to create it." msgstr "" msgid "" @@ -3046,16 +3437,16 @@ msgid "" "manual is represented by the ${SECTION_NAME}.texinfo file, as described in . In this example, " -"${SECTION_NAME} is a variable string refering the file name " -"of documentaiton entries. The file names of documentation entries " -"is made of letters, numbers and the minus sign (which is generally " -"used to separate words)." +"${SECTION_NAME} is a variable string referring the file name " +"of documentation entries. The file names of documentation entries " +"are made of letters, numbers and the minus sign (which is generally " +"used as word separator)." msgstr "" msgid "" -"Documentation entries are not limited inside a documentation " -"manual. You can create as many documentation entries as you need to " -"describe the content of your manual." +"Documentation entries are not limited inside chapters of " +"documentation manuals. You can create as many documentation entries " +"as you need to describe the content of your manual." msgstr "" msgid "" @@ -3064,11 +3455,10 @@ msgid "" "and can be found either inside or outside the language-specific " "directories so you can control common and specific output settings " "through them. These files aren't copied into the directory " -"structure of new documentation manuals created through the " -"help functionality of centos-art.sh script. Instead, they remain inside the template directory " -"structure so as to be reused each time the output of documentation " -"manuals is rendered." +"structure of new documentation manuals created through the functionality. Instead, they remain " +"inside the template directory structure so as to be reused each " +"time the output of documentation manuals is rendered." msgstr "" msgid "manual-init.pl" @@ -3090,35 +3480,37 @@ msgstr "" msgid "" "This file can be found inside and outside language-specific " -"directories and contain special transformations for Texi2html " +"directories and contains special transformations for Texi2html " "output. Again, when this file is inside language-specific " -"directories the transformation have are applied to that language-" +"directories the transformation are applied to that language-" "specific XHTML output and when it is outside language-specific " "directories the transformations are applied to all language-" -"specific XHTML outputs. Most transformations achived through this " +"specific XHTML outputs. Most transformations achieved through this " "file are to produce admonitions since Texinfo documentation format " "(as in texinfo-4.8-14.el5) doesn't have an " "internal command to build them." msgstr "" -msgid "Texinfo document template" +msgid "Template for texinfo document structures" msgstr "" #, no-wrap msgid "" -"trunk/Scripts/Bash/Functions/Help/Texinfo/Templates\n" -"|-- ${LANG}\n" -"| |-- Chapters\n" -"| | |-- chapter-menu.texinfo\n" -"| | |-- chapter-nodes.texinfo\n" -"| | |-- chapter.texinfo\n" -"| | `-- section.texinfo\n" -"| |-- Licenses\n" +"\n" +"Documentation/Models/Texinfo/Default/\n" +"|-- ${LANG}/\n" +"| |-- Chapters/\n" +"| | |-- section.texinfo\n" +"| | `-- section-functions.texinfo\n" +"| |-- Chapters-menu.texinfo\n" +"| |-- Chapters-nodes.texinfo\n" +"| |-- Chapters.texinfo\n" +"| |-- Licenses/\n" "| | |-- GFDL.texinfo\n" -"| | |-- GPL.texinfo\n" -"| | |-- chapter-menu.texinfo\n" -"| | |-- chapter-nodes.texinfo\n" -"| | `-- chapter.texinfo\n" +"| | `-- GPL.texinfo\n" +"| |-- Licenses-menu.texinfo\n" +"| |-- Licenses-nodes.texinfo\n" +"| |-- Licenses.texinfo\n" "| |-- manual-index.texinfo\n" "| |-- manual-init.pl\n" "| |-- manual-menu.texinfo\n" @@ -3127,33 +3519,40 @@ msgid "" "| |-- manual.sed\n" "| `-- manual.texinfo\n" "|-- manual-init.pl\n" -"`-- manual.sed" +"`-- manual.sed\n" msgstr "" msgid "" "Inside the directory structure of Texinfo document templates, the " -"Chapters directory " -"organizes chapter specific models used to create and maintain both " -"chapter and sections files inside manuals. On the other hand, the " -"Licenses directory " +"Chapters directory stores " +"section specific models used to create and maintain section files " +"inside manuals. File names beginning with Chapters, " +"at the same level of Chapters directory, are used to create chapter specific files " +"inside manuals." +msgstr "" + +msgid "" +"The Licenses directory " "organizes the license information linked from all manuals. Notice " "the license information is not copied into documentation manuals " -"when they are created, but refered from this location where they " -"are maintained. This configuration permites that all documentation " +"when they are created, but referred from models location where they " +"are maintained. This configuration permits all documentation " "manuals written in Texinfo format inside The CentOS Artwork " -"Repository do use the same license information and if a " -"change is committed to the license files, such changes be " -"immediatly propagated to documentation manuals the next time their " -"output files be updated." +"Repository to use the same license information. This way, " +"if a change is committed to license files, it will be immediately " +"propagated to all documentation manuals the next time their output " +"files be updated." msgstr "" msgid "Document Expansions" msgstr "" msgid "" -"The document expansions are special constructions used to generate " -"content dynamically inside Texinfo source files." +"The document expansions are special constructions the functionality provides to generate content " +"dynamically inside Texinfo source files." msgstr "" msgid "The SeeAlso Expansion" @@ -3178,10 +3577,10 @@ msgid "" "This expansion might result useful when you are documenting the " "repository file system. For example, if you are currently editing " "the documentation entry related to trunk/Identity directory and want to create a " -"linkable list of all documentation entries in the first level under " -"it, the code you'll have once the construction be expanded would " -"look like the following:" +"\">Identity directory and want to create a linkable list " +"of all documentation entries in the first level under it, the code " +"you'll have once the construction be expanded would look like the " +"following:" msgstr "" #, no-wrap @@ -3205,11 +3604,10 @@ msgid "" "executed each time the related documentation entry is edited or " "updated. Following with the example above, if the documentation " "entries related to directories under trunk/Identity changes for some reason (e.g., they " -"are removed from documentation manual), the list generated as " -"result of document expansion will be updated automatically after " -"editing the documentation entry or updating the documentation " -"manual structure." +"\">Identity changes for some reason (e.g., they are " +"removed from documentation manual), the list generated as result of " +"document expansion will be updated automatically after editing the " +"documentation entry or updating the documentation manual structure." msgstr "" msgid "Document Configuration" @@ -3278,7 +3676,9 @@ msgstr "" msgid "" "Once the documentation manual has been created, you must not change " "the value of option. This will " -"produce an error." +"produce an error because there is not a migration feature available " +"yet. In the future, when you change this value, it must be possible " +"to transform documentation manuals from one format to another." msgstr "" msgid "manual_section_style" @@ -3327,7 +3727,7 @@ msgstr "" msgid "Chapters/section.texinfo = \"^.+\\.texinfo$\"" msgstr "" -msgid "Document Internationalization" +msgid "Document Localization" msgstr "" msgid "" @@ -3341,47 +3741,46 @@ msgid "" "reference (a.k.a. the source manual) and produce several translated " "manuals based on its content. To keep track of changes inside the " "source manual, the underlaying version control system must be used " -"considering that there is no direct way to apply " -"gettext The " -"gettext program translates a natural " -"language message into the user's language, by looking up the " -"translation in a message catalog. For more information about the " -"gettext program, run info " -"gettext. procedures to Texinfo source " -"files." +"considering that there is no direct way to apply gettext The gettext program " +"translates a natural language message into the user's language, by " +"looking up the translation in a message catalog. For more " +"information about the gettext program, run " +"info gettext. procedures to " +"Texinfo source files." msgstr "" msgid "" "In order to maintain localization of Texinfo source files through " -"gettext procedures, it is necessary to " -"convert the Texinfo source files into XML format first. This way it " -"would be possible to make use of locale and " -"render functionalities from centos-" -"art.sh script to maintain translation messages in " -"different languages through portable objets and producing localized " -"XML files based on such portable objects, respectively. Once the " -"localized XML file is available, it would be a matter of using an " -"XSLT processor (see the xsltproc command) to " -"realize the convertion from XML to a localize Texinfo (or possible " -"other) format. Nevertheless, this workaround fails because the " -"Document Type Definition (DTD) required to validate the XML file " -"produced from makeinfo (as in texinfo-" -"4.8-14.el5) is not availabe inside The CentOS " -"Distribution (release 5.5), nor it is the XSLT files required to " -"realize the transformation itself for such DTD." +"gettext procedures, it is necessary to convert " +"the Texinfo source files into XML format first. This way it would " +"be possible to make use of " +"and functionalities to " +"maintain translation messages in different languages through " +"portable objects and producing localized XML files based on such " +"portable objects, respectively. Once the localized XML file is " +"available, it would be a matter of using an XSLT processor (see the " +"xsltproc command) to realize the convertion from " +"XML to a localize Texinfo (or possible other) format. Nevertheless, " +"this workaround fails because the Document Type Definition (DTD) " +"required to validate the XML file produced from makeinfo (as in texinfo-4.8-14.el5) is not " +"availabe inside The CentOS Distribution (release 5.5), nor it is " +"the XSLT files required to realize the transformation itself for " +"such DTD." msgstr "" msgid "" "Another similar approach to maintain localization of Texinfo source " -"files through gettext procedures would " -"be to convert Texinfo source file to DocBook format; for who the " -"required DTD and XSLT files are available inside The CentOS " -"Distribution. This way, following a procedure similar to that one " -"describe for XML files above, it would be possible to end up having " -"localized DocBook files that can be used as source to produce " -"localized output for both online and printing media. However, the " -"DocBook output produced from makeinfo command " -"(as in texinfo-4.8-14.el5) isn't a valid DocBook " +"files through gettext procedures would be to " +"convert Texinfo source file to DocBook format; for who the required " +"DTD and XSLT files are available inside The CentOS Distribution. " +"This way, following a procedure similar to that one describe for " +"XML files above, it would be possible to end up having localized " +"DocBook files that can be used as source to produce localized " +"output for both online and printing media. However, the DocBook " +"output produced from makeinfo command (as in " +"texinfo-4.8-14.el5) isn't a valid DocBook " "document according to DocBook DTDs available inside The CentOS " "Distribution (release 5.5) thus provoking the validation and " "transformation of such a malformed document to fail." @@ -3397,21 +3796,20 @@ msgid "" "argument refering the language code (as in ISO-639 standard) and " "must be set inside the manual's main definition file. Generally, " "there is no need to change the document language declaration once " -"it has been created by the help functionality " -"of centos-art.sh script; unless you mistakently " -"create the manual for a locale code different to that one you " -"previously pretended to do in first place, of course." +"it has been created by the " +"functionality; unless you mistakently create the manual for a " +"locale code different to that one you previously pretended to do in " +"first place, of course." msgstr "" msgid "" "The language information used in both Texinfo source files and " -"XHTML output produced by the help " -"functionality of centos-art.sh script is " -"determined by the user's session LANG environment " -"variable. This variable can be customized in the graphical login " -"screen before login, or once you've login by explicitly setting the " -"value of LANG environment variable inside the " -"~/.bash_profile file." +"XHTML output produced by the " +"functionality is determined by the user's session LANG environment variable. This variable can be customized in the " +"graphical login screen before login, or once you've login by " +"explicitly setting the value of LANG environment " +"variable inside the ~/.bash_profile file." msgstr "" msgid "" @@ -3431,7 +3829,7 @@ msgid "" "14.el5 package), the language information set by " "@documentlanguage is ignored in Info and HTML output, " "but cosidered by Tex program to redefine various English words used " -"in the PDF output (e.g., Chapter, IndexChapters, Index, See, and so on) based on the current " "language set in." msgstr "" @@ -3445,10 +3843,9 @@ msgid "" "@documentencoding command and can take either US-" "ASCII, ISO-8859-1, ISO-8859-15 or " "ISO-8859-2 as argument. Nevertheless, you should be " -"aware that the help functionality of centos-" -"art.sh script doesn't declare the " -"@documentencoding inside Texinfo source files. Let's " -"see why." +"aware that the functionality " +"doesn't declare the @documentencoding inside Texinfo " +"source files. Let's see why." msgstr "" msgid "" @@ -3481,8 +3878,8 @@ msgid "" "that that construction puts the accentuation mark over the i letter's dot, instead of removing the " "i letter's dot and put the accentuation mark on its " -"place. In the case of XHTML output, however, it possible to produce " -"well localized XHTML output by setting" +"place. In the case of XHTML output, however, it is possible to " +"produce well localized XHTML output by setting" msgstr "" #, no-wrap @@ -3499,16 +3896,39 @@ msgstr "" msgid "" "These contradictions provide the reasons over which it was decided " "not to set the @documentencoding in those Texinfo " -"source files produced by the help functionality of " -"centos-art.sh script. Now, considering them, we " -"can conclude that it is no viable way to localize Texinfo source " -"files through gettext procedures so one " -"documentation manual must be created for each language we desire to " -"support documentation for. In this configuration, it is difficult " -"the production of well localized PDF output, but it is possible to " -"produce well localized Info, Text, and XHTML outputs as long as no " -"document encoding be explicitly set inside Texinfo source files and " -"UTF-8 be used as default terminal character encoding." +"source files produced by the " +"functionality." +msgstr "" + +msgid "Conclusions" +msgstr "" + +msgid "" +"Texinfo documentation format is very good producing online " +"documentation for reading text terminals. It provides feautres to " +"export source files to different output formats both for reading " +"online and paper. However, localized documents becomes hard to " +"maintain because it is required one document structure for each " +"language you want to produce documentation for." +msgstr "" + +msgid "" +"Intermediate formats like XML and Docbook provide an alternative to " +"centralize localization of Texinfo document source files, but there " +"is no supported way inside The CentOS Distribution to transformed a " +"localized XML file back into texinfo format, nor a way of producing " +"well formed Docbook documents from Texinfo source files. Thus, one " +"Texinfo source structure for each language to support is the " +"solution adopted by " +"functionality." +msgstr "" + +msgid "" +"When using Texinfo documentation format it is difficult to produce " +"well localized PDF outputs, but it is possible to produce well " +"localized Info, Text, and XHTML outputs as long as no document " +"encoding be explicitly set inside Texinfo source files and UTF-8 be " +"used as default terminal character encoding." msgstr "" msgid "DocBook" @@ -3516,10 +3936,12 @@ msgstr "" msgid "" "This section describes the implementation of DocBook documentation " -"format inside the help functionality of centos-" -"art.sh script described in . " -"In this section we assume you have a basic understanding of DocBook " -"documentation system." +"format inside the " +"functionality of centos-art.sh script. In this " +"section we assume you have a basic understanding of DocBook " +"documentation format. Otherwise, if you don't know what DocBook " +"documentation format is, take a look at DocBook website and then, come back here." msgstr "" msgid "LaTeX" @@ -3543,559 +3965,2079 @@ msgid "" "centos-art.sh script and its functionalities. " "The main purpose of this work line is standardize the interaction " "of work lines in a reliable way. The automation work line takes " -"place in the trunk/Scripts directory." +"place in the Scripts directory." +msgstr "" + +msgid "The centos-art.sh Reference" msgstr "" -msgid "The Bash Script (centos-art.sh)" +msgid "Version 0.4" msgstr "" msgid "" -"This chapter describes the centos-art.sh script, " -"its environments, variables, functions and command-line. The " -"centos-art.sh script is written in Bash and its " -"main goal is to automate frequent tasks inside The CentOS " -"Artwork Repository. The centos-art.sh " -"script is organized by independent functions which try to do just " -"one thing and do it well." +"This reference covers the centos-art.sh script " +"mission, name convenctions, command-line interface and execution " +"environments. You can use this reference to understand how the " +"centos-art.sh script works." +msgstr "" + +msgid "Mission" +msgstr "" + +msgid "" +"The centos-art.sh script exists to automate " +"frequent tasks inside The CentOS Artwork Repository." +msgstr "" + +msgid "Convenctions" +msgstr "" + +msgid "Variable Names" +msgstr "" + +msgid "Function Names" +msgstr "" + +msgid "Exit Status" msgstr "" -msgid "Execution Environments" +msgid "" +"The centos-art.sh script has the following exit " +"status:" msgstr "" msgid "" -"When you execute the centos-art.sh script in a " -"command-line terminal (shell), the command-line interpreter behind " -"it (e.g., Bash) creates a new execution environment for it. This " -"new execution environment inherits all the variables and functions " -"set in the shell environment and those exported to it through the " -"~/.bash_profile file, as well." +"0 — The script completed successfully without error." msgstr "" msgid "" -"The centos-art.sh script uses the ~/." -"bash_profile file to implement per-user customizations. " -"For example, you can use this file to set the location of your " -"working copy through the TCAR_WORKDIR enviroment " -"variable. By default this variable is set to ${HOME}/artwork, but you can reset to " -"something different to fit your needs. See ." +"1 — The script didn't complete successfully because " +"something went wrong. This error status is generally produced by " +"cli_printMessage functionality, when you use " +"it with the option as second " +"argument." +msgstr "" + +msgid "Command-line Interface" msgstr "" msgid "" -"Once the centos-art.sh script has been executed, " -"it creates different levels of execution environments inside the " -"one created by the script itself on the shell. This different " -"levels can be seen as a tree of execution environments which " -"inherit one another, as illustrated in . These different levels of execution evironments " -"are where the centos-art.sh script is developed " -"in." +"The centos-art.sh script follows a conventional " +"GNU/Linux command-line interface where there might be options and " +"non-option arguments in it. As convention to centos-art." +"sh, the first non-option argument passed through the " +"command-line will be the name of the specific function you want to " +"execute (e.g., , , , etc.). This first argument will be immediately removed from " +"the list of arguments passed to centos-art.sh " +"script leaving just the remaining options and non-option arguments " +"passed to it. From this point on, the centos-art.sh script uses the getopt command to " +"retrieve option arguments and remove them from the list of " +"arguments passed to centos-art.sh script." msgstr "" msgid "" -"This section is a reference for developers who want to know which " -"functions and variables are available in the first two execution " -"environments levels of centos-art.sh script and " -"provides links to find out information about deeper execution " -"environment levels." +"To better understand the centos-art.sh command-" +"line interface, consider the command shown in . This example shows the entire " +"command as a list of space-separated arguments. Each argument " +"passed in the command-line can be reached using positional " +"variables as described in ." msgstr "" -msgid "Execution environments" +msgid "The command-line interface" msgstr "" #, no-wrap msgid "" "\n" -"----------------------------------------------------------\n" -"Shell execution environment\n" -"----|-------------------|---------------------------------\n" -". |-- TCAR_WORKDIR |-- EDITOR .\n" -". |-- LANG |-- HOME .\n" -". `-- centos-art.sh `-- ... .\n" -". ----|------------------------------------------- .\n" -". centos-art.sh script execution environment .\n" -". ----|--------------------|---------------------- .\n" -". . |-- CLI_NAME `-- cli() . .\n" -". . |-- CLI_VERSION |-- render() . .\n" -". . |-- CLI_BASEDIR | |-- svg() . .\n" -". . |-- CLI_FUNCDIR | `-- docbook() . .\n" -". . |-- TMPDIR |-- help() . .\n" -". . `-- ... | |-- docbook() . .\n" -". . | `-- texinfo() . .\n" -". . |-- locale() . .\n" -". . `-- ... . .\n" -". ................................................ .\n" -"..........................................................\n" +"centos-art render Identity/Images/Themes --with-brands\n" msgstr "" -msgid "Shell Execution Environment" +msgid "Option Arguments" msgstr "" msgid "" -"The centos-art.sh script uses the following variables from the " -"shell execution environment:" +"As convention inside the centos-art.sh, all " +"specific function environments should provide support for the " +"following option arguments:" msgstr "" -msgid "PATH" +msgid " | " msgstr "" msgid "" -"The PATH environment variable is specific to the " -"operating system and provides search paths for command execution. " -"By default, the centos-art.sh script links executable scripts from " -"the ~/bin directory which " -"is one of the locations used as search path in this variable. This " -"is how we create the centos-art command from the " -"centos-art.sh script inside your working copy." +"This option makes centos-art.sh to shows " +"information about the specific function environment (e.g., how to " +"execute it, available options, etc.) set as first non-option " +"argument. For example, if you provide the centos-art " +"render --help, the centos-art.sh " +"script will display to you the information related to functionality." msgstr "" -msgid "EDITOR" +msgid "" +"This information is retrieved from The CentOS Artwork " +"Repository File System (tcar-fs) documentation manual. This " +"manual is written in Texinfo format and provides a quick way for " +"you to read and browse documentation related to each directory " +"inside The CentOS Artwork Repository as you work with it " +"from a text terminal." msgstr "" -msgid "" -"The EDITOR environment variable is specific to the " -"operating system and provides the path to your default text editor. " -"The centos-art.sh script uses the default text " -"editor to edit subversion pre-commit messages, translation files, " -"documentation files, script files, and similar text-based files. If " -"EDITOR environment variable is not set, " -"centos-art.sh script uses /usr/bin/vim as default text editor. " -"Otherwise, the following values are recognized by centos-" -"art.sh script:" +msgid " | " msgstr "" -msgid "/usr/bin/vim" +msgid "" +"This option makes the centos-art.sh script to " +"suppress messages sent to standard output. This option doesn't " +"suppress error messages, nor questions related to script execution." msgstr "" -msgid "/usr/bin/emacs" +msgid "" +"The specific option arguments used by function environments are " +"described individually, as part of each function environment " +"documentation. To know more about the specific options used by " +"function environments, see and ." msgstr "" -msgid "/usr/bin/nano" +msgid "Specific functions environment" msgstr "" -msgid "" -"If none of these values is set in the EDITOR " -"environment variable, the centos-art.sh script " -"uses /usr/bin/vim text " -"editor, the one installed by default in The CentOS Distribution." +msgid "Name" msgstr "" -msgid "TCAR_WORKDIR" +msgid "Description" msgstr "" msgid "" -"The TCAR_WORKDIR environment variable is specific to " -"centos-art.sh script and controls the working " -"copy default location in the workstation. This variable doesn't " -"exist just after installing your workstation. In order for this " -"variable to be customizable you need to configure your workstation " -"first, as described in ." +"Standardize configuration tasks inside The CentOS Artwork " +"Repository" msgstr "" msgid "" -"By default, when this variable hadn't been set, the centos-art.sh " -"script assumes the ${HOME}/artwork path as default location for your working copy." +"Standardize rendition tasks inside The CentOS Artwork " +"Repository" msgstr "" msgid "" -"Besides these variables, the centos-art.sh script uses the " -"following environment variables which you don't need to customize " -"in your ~/.bash_profile file. These variables are configured when " -"you installed your workstation and can be changed later, using the " -"system configuration tools." +"Standardize localization tasks inside The CentOS Artwork " +"Repository" msgstr "" -msgid "LANG" +msgid "" +"Standardize documentation tasks inside The CentOS Artwork " +"Repository" msgstr "" msgid "" -"The LANG environment variable is specific to the " -"operating system and controls the default locale information of it. " -"The centos-art.sh script use the LANG environment variable to determine what language to use for " -"printing output messages from the script itself, as well as the " -"portable objects locations that need to be updated or edited when " -"you localize directory structures inside the working copy of The " -"CentOS Artwork Repository." +"Standardize packing tasks inside The CentOS Artwork " +"Repository" msgstr "" msgid "" -"The LANG environment variable is initially set in " -"the installation process of The CentOS Distribution, specifically " -"in the Language step. Generally, there is no " -"need to customize this variable in your personal profile. If you " -"need to change the value of this environment variable do it through " -"the login screen of GNOME Desktop Environment or the " -"system-config-language command, or even " -"resetting the variable before executing the centos-art.sh script." +"Standardize maintainance tasks inside The CentOS Artwork " +"Repository" msgstr "" msgid "" -"There are more variables set in a shell execution environment than " -"those expossed here. To know all the variables available in the " -"shell execution environment you can run the following command:" +"Standardize version control tasks inside The CentOS Artwork " +"Repository" msgstr "" -#, no-wrap -msgid "printenv" +msgid "Common functions environment" msgstr "" -msgid "Script Specific Environment" +msgid "cli_checkFiles" msgstr "" msgid "" -"Once the centos-art.sh script has been executed from the command " -"line, it calls the Functions/Common/cli.sh " -"file. This file initializes variables and functions used along the " -"script execution environment. These variables and functions are " -"described in and , respectively." +"Standardize conditional expressions applied to files (including " +"links and directories) inside the centos-art.sh " +"script." msgstr "" -msgid "Script Specific Environment Variables" +msgid "cli_checkRepoDirSource" msgstr "" msgid "" -"Once you run the centos-art.sh script, in addition to variables " -"from shell execution environment, the following variables will be " -"always available inside it:" +"Standardize directories' path construction inside the working copy, " +"using absolute paths." +msgstr "" + +msgid "cli_expandTMarkers" msgstr "" -msgid "CLI_NAME" +msgid "" +"Standardize translation markers construction and their related " +"expansion." msgstr "" -msgid "Script Specific Environment Functions" +msgid "cli_exportFunctions" msgstr "" msgid "" -"Once you run the centos-art.sh script, in addition to variables " -"from shell execution environment, the following functions will be " -"always available inside it:" +"Standardize the way specific functionalities are exported to " +"centos-art.sh script environment." +msgstr "" + +msgid "cli_getConfigLines" msgstr "" msgid "" -"cli_checkFiles FILE..." +"Standardize the way configuration lines are retrieved form " +"configuration files." +msgstr "" + +msgid "cli_getConfigSectionNames" msgstr "" msgid "" -"cli_printMessage MESSAGETYPE" +"Standardize the way section names are retrieved from configuration " +"files." +msgstr "" + +msgid "cli_getConfigValue" msgstr "" -msgid "cli_exportFunctions PATH" +msgid "" +"Standardize the way configuration values are retrieved from " +"configuration files." msgstr "" -msgid "Standardizing Configuration Tasks" +msgid "cli_getFilesList" msgstr "" msgid "" -"The prepare functionality is the interface the " -"centos-art.sh script provides to standardize the " -"content production tasks inside the working copy." +"Standardize the way list of files are built inside centos-" +"art.sh script." msgstr "" -msgid "Syntax" +msgid "cli_getPathComponent" msgstr "" msgid "" -"Assuming this is the very first time you run the centos-" -"art command, you'll find that there isn't such a command " -"in your workstation. This is correct because you haven't created " -"the symbolic link that makes it available in your execution path, " -"yet. In order to make the centos-art command " -"available in the execution path of your workstation, you need to " -"run the centos-art.sh script using its absolute " -"path first:" +"Standardize the way directory structures are organized inside the " +"working copy of The CentOS Artwork Repository." msgstr "" -#, no-wrap -msgid "~/artwork/trunk/Scripts/Bash/centos-art.sh prepare [OPTIONS]" +msgid "cli_getRepoName" msgstr "" msgid "" -"Later, once the centos-art command is available " -"in your execution path, there is no need for you to use any " -"absolute path again. From this time on, you can use the " -"centos-art command-line interface directly, as " -"the following example describes:" +"Standardize files and directories name convection inside the " +"working copy of The CentOS Artwork Repository." msgstr "" -#, no-wrap -msgid "centos-env prepare [OPTIONS]" +msgid "cli_getTemporalFile" msgstr "" -msgid "Options" +msgid "Standardize temporal files creation." +msgstr "" + +msgid "cli_parseArgumentsReDef" msgstr "" msgid "" -"When the centos-art command is executed with the " -"prepare functionality, it accepts the " -"following options:" +"Initiate/reset and sanitize positional parameters passed to this " +"function and creates the list of arguments that getopt will process." msgstr "" -msgid "--quiet" +msgid "cli_parseArguments" msgstr "" msgid "" -"Supress all output messages except error messages. When this option " -"is passed, all confirmation requests are supressed and a possitive " -"answer is assumed for them, just as if the " +"inside My Zoo documentation manual, run the " +"following command:" +msgstr "" + +msgid "" +"centos-art help --edit --format=\"texinfo\" \"myzoo::turtles:\"" +msgstr "" + +#, no-wrap +msgid "" +"\n" +"The following documentation chapter doesn't exist:\n" +"--> Documentation/Models/Texinfo/Myzoo/en_US/Turtles\n" +"Do you want to create it now? [yes/no]: yes\n" +"Enter chapter's title: Turtles\n" +"Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles\n" +"Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter-menu.texinfo\n" +"Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter-nodes.texinfo\n" +"Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter.texinfo\n" +"Updating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-menu.texinfo\n" +"Updating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-nodes.texinfo\n" +"Updating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter.texinfo\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2\n" +msgstr "" + +msgid "" +"Once chapters have been created it is possible to create sections " +"inside them. For example, if you want to create a section for " +"describing the life of a turtle named Longneck, run the following " +"command:" +msgstr "" + +msgid "" +"centos-art help --edit --format=\"texinfo\" \"myzoo::turtles:" +"longneck\"" +msgstr "" + +#, no-wrap +msgid "" +"\n" +"The following documentation section doesn't exist:\n" +"--> Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo\n" +"Do you want to create it now? [yes/no]: yes\n" +"Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2\n" +msgstr "" + +msgid "Editing Document Structures" +msgstr "" + +msgid "" +"To edit documentation entries you can follow the same procedure " +"described above. Just keep in mind the following rules:" +msgstr "" + +msgid "" +"When the entry you want to edit already exist it will be edited." +msgstr "" + +msgid "" +"When the entry you want to edit doesn't exist it will be created " +"first and edited later." +msgstr "" + +msgid "Copying Document Structures" +msgstr "" + +msgid "" +"Consider a new turtle named Slowfeet has arrived to your home and " +"you want to duplicate Longneck's section for it (they both are " +"turtles and have similar requirements, squedules, etc.). To copy " +"documentation entries you use the option " +"with two documentation entries, where the first one is the source " +"location and the second one the target location. To do this, run " +"the following command:" +msgstr "" + +msgid "" +"centos-art help --copy --format=\"texinfo\" \"myzoo::turtles:" +"longneck\" \"myzoo::turtles:slowfeet\"" +msgstr "" + +#, no-wrap +msgid "" +"\n" +"Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/slowfeet.texinfo\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf\n" +"Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2\n" +msgstr "" + +msgid "Renaming Document Structures" +msgstr "" + +msgid "" +"Consider you've created the section of Longneck turtle using the " +"following documentation entry format myzoo::turtles:longnek, but you didn't notice the typo in it. You've made cross " +"references to the misspelled section in a few pages inside the " +"My Zoo documentation manual and some time later you " +"realize the section name has a spelling problem. To fix such a " +"problem you can rename the misspelled section with the correct one " +"running the following command:" +msgstr "" + +msgid "" +"centos-art help --rename --format=\"texinfo\" \"myzoo::turtles:" +"longnek\" \"myzoo::turtles:longneck\"" +msgstr "" + +#, no-wrap +msgid "" +"\n" +"Creating Documentation/Models/Texinfo/MyZoo/en_US/Turtles/longneck.texinfo\n" +"Deleting Documentation/Models/Texinfo/MyZoo/en_US/Turtles/longnek.texinfo\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.info.bz2\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xhtml.tar.bz2\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xml\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.docbook\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.pdf\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.txt.bz2\n" +msgstr "" + +msgid "Deleting Document Structures" +msgstr "" + +msgid "" +"Consider you gift the turtle named Longneck to a friend and you " +"want to delete its section from the My Zoo " +"documentation manual. To do so, run the following command:" +msgstr "" + +msgid "" +"centos-art help --delete --format=\"texinfo\" \"myzoo::turtles:" +"longneck\"" +msgstr "" + +#, no-wrap +msgid "" +"\n" +"Deleting Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.info.bz2\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xhtml.tar.bz2\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xml\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.docbook\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.pdf\n" +"Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.txt.bz2\n" +msgstr "" + +msgid "" +"To report bugs related to this function, please create a new ticket " +"here refering the specific problems you " +"found in it. For example, it would be useful if you copy and paste " +"any error output from centos-art.sh script." +msgstr "" + +msgid "Copyright © =COPYRIGHT_YEAR_LIST= The CentOS Project" +msgstr "" + +msgid "render" +msgstr "" + +msgid "" +"Standardize rendition tasks inside The CentOS Artwork " -"Repository, where the files you want to process are stored " -"in. This paramter can be provided more than once in order to " -"process more than one directory path in a single command execution. " -"When this parameter is not provided, the current directory path " -"where the command was called from is used instead." +"Repository." +msgstr "" + +msgid "--filter=\"REGEX\"" +msgstr "" + +msgid "--dont-dirspecific" +msgstr "" + +msgid "--releasever=\"RELEASEVER\"" +msgstr "" + +msgid "--basearch=\"BASEARCH\"" +msgstr "" + +msgid "--post-rendition=\"COMMAND\"" +msgstr "" + +msgid "--last-rendition=\"COMMAND\"" +msgstr "" + +msgid "--theme-model=\"MODELNAME\"" +msgstr "" + +msgid "--with-brands" +msgstr "" + +msgid "" +"The render functionality exists to automate " +"content rendition inside The CentOS Artwork Repository. The content rendition process itself takes place through " +"the following rendition modes:" +msgstr "" + +msgid "" +"svg — This modes works with both gzip-compressed " +"(.svgz) or uncompressed " +"(.svg) scalable vector " +"graphics as source files and produces portable network graphics as " +"main output." +msgstr "" + +msgid "" +"docbook — This mode works with DocBook source " +"files and produces XHTML as main output. It is also possible to " +"produce PDF output from DocBook source files, however PDF output is " +"commented because its production fails trying to create indexes." +msgstr "" + +msgid "" +"conf — This mode works with one or more " +"configuration files as source and produces portable network " +"graphics as main output. The format used in these configuration " +"files is described in ." +msgstr "" + +msgid "" +"To determine the rendition mode, the render " +"functionality uses the path provided as LOCATION argument and the path name convention described in " +"." +msgstr "" + +msgid "Render-able Directories" +msgstr "" + +msgid "" +"The render-able directories are conventional locations inside the " +"working copy where you can find final output files. The final " +"output files are produced from source files and auxiliary files. " +"Auxiliary files are frequently used to create localized instances " +"of source files which are, in turn, used to create final output " +"files in different forms (e.g., in a different language)." +msgstr "" + +msgid "" +"Inside the working copy of The CentOS Artwork Repository, the following directory structures are considered render-" +"able directories:" +msgstr "" + +msgid "" +"Identity/Images/ — This " +"directory structure organizes final image files in different " +"formats. It also includes source files for producing the " +"backgrounds of themes. Related design models for all these files " +"are under Identity/Models/ " +"directory structure." +msgstr "" + +msgid "" +"Don't move any source file related to theme backgrounds from render-" +"able directories to theme design models directory structure. The " +"source files related to theme backgrounds are specific to each " +"theme and cannot be shared among different themes. The directory " +"structure related to theme design models is reserved for files " +"shared by all themes." +msgstr "" + +msgid "" +"Documentation/Manuals/ — " +"This directory structure organizes final documentation files. " +"Design models for all these files are organized under Documentation/Models/ directory " +"structure." +msgstr "" + +msgid "" +"Inside render-able directories the rendition process is performed " +"through different rendition flows known as theme-rendition, base-" +"rendition, post-rendition and last-rendition." +msgstr "" + +msgid "Theme-Rendition Flow" +msgstr "" + +msgid "" +"The theme-rendition flow exists to produce content inside " +"Identity/Images/Themes/ directory structure. " +"This rendition flow identifies which directories are render-able " +"and uses the base-rendition on them, one by one." +msgstr "" + +msgid "" +"The theme-rendition flow exists to support massive rendition of " +"themes through the following command:" +msgstr "" + +msgid "centos-art render Identity/Images/Themes" +msgstr "" + +msgid "" +"In case you need to limit the amount of themes or components inside " +"themes you want to render, you can be more specific about the " +"LOCATION you passed as argument and use " +"the " +"to specify the file you want to render. For example, if you only " +"want to render the 01-welcome.png Anaconda " +"file for CentOS-5 distribution based on version 2 of Modern " +"artistic motif, then you can run the following command:" +msgstr "" + +msgid "" +"centos-art render Identity/Images/Themes/Modern/2/Distro/5/Anaconda " +"--filter=\"01-welcome\"" +msgstr "" + +msgid "" +"Notice that you can reach the same result in different ways here by " +"creating combinations between the path you provide as " +"LOCATION and the option would have been provided." +"You can use whatever combination you like whenever it matches a " +"valid render-able directory inside the working copy. But it seems " +"to be an acceptable practice to use the LOCATION argument to specify the render-able directory path " +"inside the Identity/Images/Themes directory which images need to be rendered for and the " +" option only when it is needed to restrict " +"rendition to a specific file inside the directory provided as " +"LOCATION." msgstr "" -msgid "--filter=\"REGEX\"" +msgid "Base-Rendition Flow" msgstr "" -msgid "" -"This option reduces the list of files to process inside " -"DIRECTORY using REGEX as " -"pattern. You can use this option to control the amount of files you " -"want to render. The deeper you go into the directory structure the " -"more specific you'll be about the files you want to render. When " -"you cannot go deeper into the directory structure through " -"DIRECTORY specification, use this option to " -"reduce the list of files therein." +msgid "Post-Rendition Flow" +msgstr "" + +msgid "Last-Rendition Flow" msgstr "" -msgid "--dont-commit-changes" +msgid "Configuration Files (render.conf)" msgstr "" msgid "" -"This option supresses all commit and update actions realized over " -"files, before and after the action itself had took place over files " -"in the working copy." +"This option reduces the list of files to process inside " +"LOCATION using REGEX as REGUEX using " +"REGEX as files you want to render. The " +"deeper you go into the directory structure the more specific you'll " +"be about the files you want to render. When you cannot go deeper " +"into the directory structure through LOCATION specification, use this option to reduce the list of " +"files therein." msgstr "" -msgid "--releasever=\"NUMBER\"" +msgid "--releasever=\"RELEASE\"" msgstr "" msgid "" "This option expands the =\\RELEASE=, =" "\\MAJOR_RELEASE=, and =\\MINOR_RELEASE= " -"translation makers based on NUMBER value. Notice " -"that translation markers here were escaped using a backslash (" -"\\) in order to prevent their expansion. Use this option " -"when you need to produce release-specific contents, but no release " -"information can be retrived from the directory path you are " -"currently rendering." -msgstr "" - -msgid "--basearch=\"ARCH\"" +"translation makers based on NUMBER " +"value. Notice that translation markers here were escaped using a " +"backslash (\\) in order to prevent their expansion. " +"Use this option when you need to produce release-specific contents, " +"but no release information can be retrived from the directory path " +"you are currently rendering." msgstr "" msgid "" "This option expands the =\\ARCHITECTURE=, translation " -"makers based on ARHC value. Notice that " +"makers based on ARHC value. Notice that " "translation markers here were escaped using a backslash (\\) in order to prevent their expansion. Use this option when " "you need to produce architecture-sepecific contents but no " @@ -4103,110 +6045,60 @@ msgid "" "you are currently rendering." msgstr "" -msgid "--theme-model=\"NAME\"" -msgstr "" - msgid "" "This option specifies the name of theme model you want to use when " "producing theme artistic motifs. By default, if this option is not " "provided, the Default theme model is used as " -"reference to produce theme artistic motifs. To know what values " -"does the NAME variable can have, run ls " -"~/artwork/trunk/Identity/Models/Themes command." +"reference to produce theme artistic motifs. To know what values can " +"be passed as MODELNAME, run the " +"following command:" msgstr "" -msgid "--post-rendition=\"COMMAND\"" +msgid "ls ${TCAR_WORKDIR}/Identity/Models/Themes" msgstr "" msgid "" "This option lets you apply a command as post-rendition action. In " -"this case, the COMMAND represents the command-" -"line you want to execute in order to perform in-place modifications " -"to base-rendition output." -msgstr "" - -msgid "--last-rendition=\"COMMAND\"" +"this case, the COMMAND represents the " +"command-line you want to execute in order to perform in-place " +"modifications to base-rendition output." msgstr "" msgid "" "This option lets you apply a command as last-rendition action. In " -"this case, the COMMAND argument represents the " -"command string you want to execute in order to perform in-place " -"modifications to base-rendition, post-rendition and directory-" -"specific rendition outputs." -msgstr "" - -msgid "" -"Inside the working copy of The CentOS Artwork Repository, rendition tasks take place inside renderable directories. " -"The rendition itself is performed through a serie of rendition " -"flows named base-rendition, post-rendition, last-rendition and " -"directory-specific rendition." -msgstr "" - -msgid "" -"Renderable directories are convenctional locations inside the " -"working copy where you can find source files, output files and " -"auxiliar files. Source files are used to produce output files. " -"Auxiliar files are used to modify the way output files are produced " -"from source files (e.g., to produce localized output). Auxiliar " -"files are optionals." -msgstr "" - -msgid "" -"Renderable directories are made of several directories but only the " -"output dirctory path is passed to render " -"functionality as DIRECTORY parameter in the " -"command-line. The directories related to source and auxiliar files " -"are automatically constructed based on a directory organization " -"convenction. This way, the render " -"functionality collects all the information it needs to work with." +"this case, the COMMAND argument " +"represents the command string you want to execute in order to " +"perform in-place modifications to base-rendition, post-rendition " +"and directory-specific rendition outputs." msgstr "" msgid "" -"Inside the working copy, renderable directories are divided in two " -"categories in a way differences between them can be preserved. " -"These categories are named direct production and " -"theme production. These categories provide the file " -"organization convenction the render " -"functionality needs, to produce content based on rendition flows." -msgstr "" - -msgid "Direct Production" -msgstr "" - -msgid "Theme Production" -msgstr "" - -msgid "Base Rendition Flow" -msgstr "" - -msgid "Post Rendition Flow" -msgstr "" - -msgid "Last Rendition Flow" +"To report bugs related to this function, please create a new ticket " +"here refering the specific problems you " +"found in it. For example, it would be useful if you copy and paste " +"any error output from centos-art.sh script." msgstr "" -msgid "Directory-Specific Rendition Flow" +msgid "locale" msgstr "" msgid "" -"The following people have worked in the render " -"functionality:" -msgstr "" - -msgid "Standardizing Content Localization" +"Standardize translation tasks inside The CentOS Artwork " +"Repository" msgstr "" msgid "" -"The locale functionality is the interface the " -"centos-art.sh script provides to standardize " -"localization tasks inside the working copy." -msgstr "" - -#, no-wrap -msgid "centos-art locale [OPTIONS] [DIRECTORY]" +"The DIRECTORY parameter specifies the directory " +"path, inside the working copy of The CentOS Artwork " +"Repository, where the files you want to process are stored " +"in. This paramter can be provided more than once in order to " +"process more than one directory path in a single command execution. " +"When this parameter is not provided, the current directory path " +"where the command was called from is used instead." msgstr "" msgid "" @@ -4214,6 +6106,9 @@ msgid "" "options:" msgstr "" +msgid "--quiet" +msgstr "" + msgid "" "Supress all output messages except error messages. When this option " "is passed, all confirmation requests are supressed and a possitive " @@ -4221,6 +6116,9 @@ msgid "" "option> option would have been provided." msgstr "" +msgid "--filter=\"REGEX\"" +msgstr "" + msgid "" "Reduce the list of files to process inside DIRECTORY using REGEX as pattern. You can use " @@ -4231,12 +6129,6 @@ msgid "" "specification, use this option to reduce the list of files therein." msgstr "" -msgid "" -"Supress all commit and update actions realized over files, before " -"and after the actions themselves had took place over files in the " -"working copy." -msgstr "" - msgid "--update" msgstr "" @@ -4246,9 +6138,6 @@ msgid "" "the source files." msgstr "" -msgid "--edit" -msgstr "" - msgid "" "This option edits the portable object related to source files. When " "you provide this option, your default text editor is used to open " @@ -4260,9 +6149,6 @@ msgid "" "when it is executed." msgstr "" -msgid "--delete" -msgstr "" - msgid "" "This option unlocalizes source files. When you provide this option, " "the localization directory related to source files is removed from " @@ -4379,180 +6265,18 @@ msgid "" "for, run the following command: locale -a | less." msgstr "" -msgid "" -"The following people have worked in the locale " -"functionality:" -msgstr "" - -msgid "Standardizing Documentation Tasks" -msgstr "" - -msgid "" -"The help functionality is the interface the " -"centos-art.sh script provides to standardize " -"frequent documentation tasks, based on specific documentation " -"formats, as described in ." -msgstr "" - -#, no-wrap -msgid "centos-art help [OPTIONS] [DOCENTRY]" -msgstr "" - -msgid "" -"The DOCENTRY parameter specifies the " -"documentation entry you want to process. It can be provided one or " -"more times in the form MANUAL:PART:CHAPTER:SECTION or " -"MANUAL::CHAPTER:SECTION based on whether the manual " -"documentation backend you are using supports structuring through " -"parts or not. When DOCENTRY parameter is not " -"provided, The CentOS Artwork Repository " -"Repository File System documentation manual is used as " -"default value." -msgstr "" - -msgid "" -"To determine the documentation format to use, when new " -"documentation manuals are created and no configuration file is " -"available, the help functionality request you " -"to enter one of the supported documentation formats and then, uses " -"it to create the documentation manual. Once the documentation " -"manual is created, the document configuration file is available " -"inside the manual directory structure and used to retrive the " -"document format information, instead." -msgstr "" - -msgid "" -"The help functionality accepts the following " -"options:" -msgstr "" - -msgid "" -"Supress all commit and update actions realized over files, before " -"and after the action itself had took place over files in the " -"working copy." -msgstr "" - -msgid "--search=\"KEYWORD\"" -msgstr "" - -msgid "" -"This option looks for KEYWORD inside the manual " -"specified in the documentation entry and display related " -"information you to read." -msgstr "" - -msgid "" -"Edit documentation entry related to path specified by " -"DOCENTRY parameter." -msgstr "" - -msgid "" -"The DOCENTRY parameter must point to any " -"directory inside the working copy. When more than one " -"DOCENTRY are passed as non-option arguments to " -"the centos-art.sh script command-line, they are " -"queued for further edition. The edition itself takes place through " -"your default text editor (e.g., the one you specified in the " -"EDITOR environment variable) and the text editor " -"opens one file at time (i.e., the queue of files to edit is not " -"loaded in the text editor.)." -msgstr "" - -msgid "--read" -msgstr "" - -msgid "" -"Read documentation entry specified by DOCENTRY " -"path. This option is used internally by centos-art.sh script to refer documentation based on errors, so you can " -"know more about them and the causes that could have provoked them." -msgstr "" - -msgid "" -"Update output files rexporting them from the specified backend " -"source files." -msgstr "" - -msgid "--copy" -msgstr "" - -msgid "Duplicate documentation entries inside the working copy." -msgstr "" - -msgid "" -"When documentation entries are copied, it is required to pass two " -"non-option parameters in the command-line. The first non-option " -"parameter is considered the source location and the second one the " -"target location. Both source location and target location must " -"point to a directory under the working copy." -msgstr "" - -msgid "" -"Delete documentation entries specified by DOCENTRY inside the working copy. It is possible to delete more " -"than one documentation entry by specifying more DOCENTRY parameters in the command-line." -msgstr "" - -msgid "--rename" -msgstr "" - -msgid "Rename documentation entries inside the working copy." -msgstr "" - -msgid "" -"When documentation entries are renamed, it is required to pass only " -"two non-option parameters to the command-line. The first non-option " -"parameter is considered the source location and the second one the " -"target location. Both source location and target location must " -"point to a directory under the working copy." -msgstr "" - -msgid "" -"When documentation entries are removed (e.g., through or options), the " -"help functionality takes care of updating " -"nodes, menus and cross references related to documentation entries " -"in order to keep the manual structure in a consistent state." +msgid "Function Specific Environment" msgstr "" msgid "" -"The following people have worked in the help " +"The following people have worked in the locale " "functionality:" msgstr "" -msgid "Standardizing Packaging Tasks" +msgid "pack" msgstr "" -msgid "Standardizing File Maintainance" -msgstr "" - -msgid "" -"The tuneup functionality is the interface the " -"centos-art.sh script provides to standardize the " -"maintainance tasks related to individual files inside the working " -"copy." -msgstr "" - -#, no-wrap -msgid "centos-art tuneup [OPTIONS] [DIRECTORY]" -msgstr "" - -msgid "" -"The tuneup functionality accepts the following " -"options:" -msgstr "" - -msgid "" -"Reduce the list of files to process inside path/to/" -"dir using REGEX as " -"pattern. You can use this option to control the amount of files you " -"want to tuneup. The deeper you go into the directory structure the " -"more specific you'll be about the files you want to tuneup. When " -"you cannot go deeper into the directory structure through " -"path/to/dir specification, use this " -"option to reduce the list of files therein." +msgid "tuneup" msgstr "" msgid "" @@ -4572,16 +6296,16 @@ msgid "" "\"extension\">.svg and ." "xhtml) in the directory specified, builds a list with " "them and applies the maintainance tasks using file extensions as " -"reference." +"refentry." msgstr "" msgid "" "When shell scripts are found, the tuneup " "functionality of centos-art.sh script reads a comment template from " -"trunk/Scripts/Functions/Tuneup/Shell/Config/topcomment." -"sed and applies it to all shell scripts found, one by " -"one. As result, all shell scripts will end up having the same " -"copyright and license information the comment template does." +"Scripts/Functions/Tuneup/Shell/Config/topcomment.sed and applies it to all shell scripts found, one by one. As " +"result, all shell scripts will end up having the same copyright and " +"license information the comment template does." msgstr "" msgid "" @@ -4623,11 +6347,11 @@ msgstr "" msgid "" "When scalable vector graphics are found, the tuneup functionality " -"reads a SVG metadata template from trunk/Scripts/" -"Functions/Tuneup/Svg/Config/metadata.sed and applies it " -"to all files found, one by one. Immediatly after the metadata " -"template has been applied and, before passing to next file, all " -"unused definition are removed from the file, too." +"reads a SVG metadata template from Scripts/Functions/" +"Tuneup/Svg/Config/metadata.sed and applies it to all " +"files found, one by one. Immediatly after the metadata template has " +"been applied and, before passing to next file, all unused " +"definition are removed from the file, too." msgstr "" msgid "" @@ -4635,7 +6359,7 @@ msgid "" "dynamicaly combining the absolute path of the file being currently " "modified, the workstation's date information, the centos-" "art.sh script copyright holder (e.g., =COPYRIGHT_HOLDER=) " -"as reference and the Creative Common Distribution-ShareAlike 3.0 " +"as refentry and the Creative Common Distribution-ShareAlike 3.0 " "License as default license to release SVG files." msgstr "" @@ -4669,7 +6393,7 @@ msgid "" "set dynamically using the md5sum output of combining the page " "location, the head- string and the heading " "content itself. If any of the components used to build the heading " -"reference changes, you need to run the the tuneup functionality of " +"refentry changes, you need to run the the tuneup functionality of " "centos-art.sh script in order for the anchor " "elements to use the correct information." msgstr "" @@ -4701,10 +6425,189 @@ msgid "" msgstr "" msgid "" +"The tuneup functionality accepts the following " +"options:" +msgstr "" + +msgid "" +"Reduce the list of files to process inside path/to/" +"dir using REGEX as " +"pattern. You can use this option to control the amount of files you " +"want to tuneup. The deeper you go into the directory structure the " +"more specific you'll be about the files you want to tuneup. When " +"you cannot go deeper into the directory structure through " +"path/to/dir specification, use this " +"option to reduce the list of files therein." +msgstr "" + +msgid "" "The following people have worked in the tuneup " "functionality:" msgstr "" +msgid "vcs" +msgstr "" + +msgid "1" +msgstr "" + +msgid "Standardize constructions for file verifications" +msgstr "" + +msgid "Standardize constructions for file verifications." +msgstr "" + +msgid "-d" +msgstr "" + +msgid "-e" +msgstr "" + +msgid "-f" +msgstr "" + +msgid "-h" +msgstr "" + +msgid "-x" +msgstr "" + +msgid "" +"The cli_checkFiles exists to answer basic " +"questions like Is LOCATION is a " +"regular file? and Is LOCATION a directory?. The answer to such questions " +"affects the script execution flow in the following way: when the " +"answer positive (e.g., LOCATION is a " +"regular file), the script passes the test silently and continues " +"its execution. When the answer is negative(e.g., " +"LOCATION is not a regular file), the " +"script finishes its execution immediately with an error message." +msgstr "" + +msgid "" +"The cli_checkFiles function is exported to " +"centos-art.sh script environment in the very " +"beginning of its execution and will be available all along its " +"execution lifetime. You can use this function inside common and " +"specific functions whenever you need to verify files inside the " +"The CentOS Artwork Repository." +msgstr "" + +msgid "" +"The cli_checkFiles function is available " +"inside the centos-art.sh script only as part of " +"its execution environment. This function is exported to " +"centos-art.sh script just after executing the " +"script from the command-line and will be available all along the " +"script lifetime. So, you can use this function both in common and " +"specific functionalities of centos-art.sh script." +msgstr "" + +msgid "" +"The cli_checkFiles function doesn't create " +"subsequent execution environments." +msgstr "" + +msgid "" +"Use the cli_checkFiles function inside " +"centos-art.sh script whenever you need to " +"control the script execution flow based on file type (e.g., regular " +"files, directories, links, etc.) verifications." +msgstr "" + +msgid "" +"The cli_checkFiles function accepts the " +"following options:" +msgstr "" + +msgid "" +"Verifies whether LOCATION exists and is " +"a directory. If it doesn't exists or isn't a directory, an error " +"message is printed and the script finishes its execution. " +"Otherwise, if it exists and is a directory, the script continues " +"its execution normally." +msgstr "" + +msgid "" +"Verifies whether LOCATION exists or not. " +"If it doesn't exist, an error message is printed and the script " +"finishes its execution. Otherwise, if it does exists, the script " +"continues its execution normally." +msgstr "" + +msgid "" +"Verifies whether LOCATION exists and is " +"a regular file. If it doesn't exists or isn't a regular file, an " +"error message is printed and the script finishes its execution. " +"Otherwise, if it exists and is a regular file, the script continues " +"its execution normally." +msgstr "" + +msgid "" +"Verifies whether LOCATION exists and is " +"a symbolic link. If it doesn't exists or isn't a symbolic link, an " +"error message is printed and the script finishes its execution " +"immediately. Otherwise, if it does exist and is a symbolic link, " +"the script continue its execution normally." +msgstr "" + +msgid "" +"Verifies whether LOCATION exists and " +"execution permission is granted. If it doesn't exist or hasn't " +"execution permission, the script finishes its execution " +"immediately. Otherwise, if it exists and has execution permissions, " +"the script continues its execution normally." +msgstr "" + +msgid "" +"The value of the LOCATION argument must " +"be an absolute path to the file you want to verify. If such file " +"doesn't exists in any supported form, the script finishes its " +"execution with an error message." +msgstr "" + +msgid "" +"The following example was taken from centos-art.sh script initialization phase. Notice the position of " +"cli_checkFiles function inside the loop. If " +"some of the function files we need to export doesn't have execution " +"rights, cli_checkFiles will finish the script " +"execution immediately with an error message." +msgstr "" + +#, no-wrap +msgid "" +"\n" +"# Process the list of files.\n" +"for FUNCFILE in $FUNCFILES;do\n" +"\n" +" # Verify the execution rights for function file.\n" +" cli_checkFiles -x ${FUNCFILE}\n" +" \n" +" # Initialize the function file.\n" +" . ${FUNCFILE}\n" +" \n" +" # Export the function names inside the file to current shell\n" +" # script environment.\n" +" export -f $(egrep \"${PATTERN}\" ${FUNCFILE} | gawk '{ print $2 }')\n" +" \n" +"done\n" +msgstr "" + +msgid "" +"To report bugs related to this function, please create a new ticket " +"at " +"refering the name of this function clearly and the specific " +"problems you found in it." +msgstr "" + +msgid "" +"Alain Reguera Delgado alain.reguera@gmail.com, " +"=COPYRIGHT_YEAR_LIST=" +msgstr "" + msgid "Licencias" msgstr "" diff --git a/Scripts/Bash/Functions/Commons/cli_getPathComponent.sh b/Scripts/Bash/Functions/Commons/cli_getPathComponent.sh index 4a60059..4c21378 100755 --- a/Scripts/Bash/Functions/Commons/cli_getPathComponent.sh +++ b/Scripts/Bash/Functions/Commons/cli_getPathComponent.sh @@ -35,7 +35,7 @@ function cli_getPathComponent { local ARGSL='release,release-major,release-minor,release-pattern,architecture,architecture-pattern,motif,motif-name,motif-release,motif-pattern' # Define release pattern. - local RELEASE="(([[:digit:]]+)(\.([[:digit:]]+)){0,1})" + local RELEASE="(([[:digit:]]+)(\.([[:digit:]]+))?)" # Define architecture pattern. Make it match the architectures the # CentOS distribution is able to be installed on. diff --git a/Scripts/Bash/Functions/Commons/cli_printMessage.sh b/Scripts/Bash/Functions/Commons/cli_printMessage.sh index 6134959..94e54b4 100755 --- a/Scripts/Bash/Functions/Commons/cli_printMessage.sh +++ b/Scripts/Bash/Functions/Commons/cli_printMessage.sh @@ -85,6 +85,27 @@ function cli_printMessage { exit 1 ;; + --as-suggestion-line ) + + # Define where the error was originated inside the + # centos-art.sh script. Print out the function name and + # line from the caller. + local ORIGIN="$(caller 1 | gawk '{ print $2 " L." $1 }')" + + # Build the error message. + cli_printMessage "${CLI_NAME} (${ORIGIN}):" --as-stdout-line + cli_printMessage "`gettext "The path provided cannot be processed the way you entered it."`" --as-stdout-line + cli_printMessage "`gettext "Instead, try the following equivalence:"`" --as-stdout-line + cli_printMessage "${MESSAGE}" --as-response-line + cli_printMessage "${CLI_FUNCNAME}" --as-toknowmore-line + + # Finish script execution with exit status 1 (SIGHUP) to + # imply the script finished because an error. We are + # using this as convention to finish the script execution. + # So, don't remove the following line, please. + exit 1 + ;; + --as-toknowmore-line ) cli_printMessage '-' --as-separator-line cli_printMessage "`gettext "To know more, run"` ${CLI_NAME} ${MESSAGE} --help" --as-stdout-line diff --git a/Scripts/Bash/Functions/Locale/locale.sh b/Scripts/Bash/Functions/Locale/locale.sh index c812432..58e2375 100755 --- a/Scripts/Bash/Functions/Locale/locale.sh +++ b/Scripts/Bash/Functions/Locale/locale.sh @@ -69,28 +69,25 @@ function locale { # through its command-line. for ACTIONVAL in "$@";do - # Print action message. - cli_printMessage "${ACTIONVAL}" --as-processing-line + # Don't call locale_isLocalizable function here. Remember that + # this function (i.e., locale) is called from other functions + # using the cli_runFnEnvironment function to determine whether + # a location can accept or not localized messages. If you put + # the locale_isLocalizable function here, you would be + # duplicating its execution. # Sanitate non-option arguments to be sure they match the # directory conventions established by centos-art.sh script # against source directory locations in the working copy. ACTIONVAL=$(cli_checkRepoDirSource ${ACTIONVAL}) - # Verify directory passed as non-option argument to be sure it - # supports localization. - locale_isLocalizable "${ACTIONVAL}" - if [[ $? -ne 0 ]];then - cli_printMessage "`gettext "The path provided does not support localization."`" --as-error-line - fi - # Verify non-option arguments passed to centos-art.sh # command-line. It should point to an existent directory under # version control inside the working copy. Otherwise, if it # doesn't point to a directory under version control, finish # the script execution with an error message. cli_checkFiles ${ACTIONVAL} -d --is-versioned - + # Execute localization actions provided to centos-art.sh # script through its command-line. Notice that localization # actions will be executed in the same order they were diff --git a/Scripts/Bash/Functions/Locale/locale_editMessages.sh b/Scripts/Bash/Functions/Locale/locale_editMessages.sh index 195d3f4..5b942ee 100755 --- a/Scripts/Bash/Functions/Locale/locale_editMessages.sh +++ b/Scripts/Bash/Functions/Locale/locale_editMessages.sh @@ -25,6 +25,10 @@ function locale_editMessages { + # Verify directory passed as non-option argument to be sure it + # supports localization. + locale_isLocalizable "${ACTIONVAL}" + local PO_FILE='' local PO_FILES='' diff --git a/Scripts/Bash/Functions/Locale/locale_isLocalizable.sh b/Scripts/Bash/Functions/Locale/locale_isLocalizable.sh index 588875e..f59bbe3 100755 --- a/Scripts/Bash/Functions/Locale/locale_isLocalizable.sh +++ b/Scripts/Bash/Functions/Locale/locale_isLocalizable.sh @@ -1,10 +1,9 @@ #!/bin/bash # -# locale_isLocalizable.sh -- This function determines whether a file or -# directory can have translation messages or not. This is the way we -# standardize what locations can be localized and what cannot inside -# the repository. This function returns 0 when the path is localize -# able and 1 when it is not. +# locale_isLocalizable.sh -- This function determines whether a file +# or directory can have translation messages or not. This is the way +# we standardize what locations can and cannot be localized inside the +# repository. # # Copyright (C) 2009-2013 The CentOS Project # @@ -34,6 +33,10 @@ function locale_isLocalizable { # Initialize location will use as reference to determine whether # it can have translation messages or not. local LOCATION="$1" + + # Initialize answer value. By default all paths do not accept + # localization. + local L10N_ACCEPTED='no' # When no variable is passed to this function, use the action # value instead. @@ -50,13 +53,18 @@ function locale_isLocalizable { # Verify location existence. If it doesn't exist we cannot go on. cli_checkFiles -e $LOCATION + # Initialize possible messages this function would print out. + local -a MESSAGES + # Define regular expression list of all directories inside the - # repository that can have translation. - DIRS[++((${#DIRS[*]}))]="${TCAR_WORKDIR}/Identity/Models/Themes/[[:alnum:]-]+/(Distro/$(\ - cli_getPathComponent --release-pattern)/Anaconda|Concept|Posters|Media)" - DIRS[++((${#DIRS[*]}))]="${TCAR_WORKDIR}/Documentation/Models/Docbook/[[:alnum:]-]+$" - DIRS[++((${#DIRS[*]}))]="${TCAR_WORKDIR}/Documentation/Models/Svg/[[:alnum:]-]+$" - DIRS[++((${#DIRS[*]}))]="${TCAR_WORKDIR}/Scripts/Bash$" + # repository that can have translation. Try to keep regular + # expressions as simple as possible, so they can be understood by + # sed program. + DIRS[++((${#DIRS[*]}))]="${TCAR_WORKDIR}/Identity/Models/Themes/[[:alnum:]-]+/Distro/$(\ + cli_getPathComponent --release-pattern)/(Anaconda|Concept|Posters|Media)" + DIRS[++((${#DIRS[*]}))]="${TCAR_WORKDIR}/Documentation/Models/Docbook/[[:alnum:]-]+" + DIRS[++((${#DIRS[*]}))]="${TCAR_WORKDIR}/Documentation/Models/Svg/[[:alnum:]-]+" + DIRS[++((${#DIRS[*]}))]="${TCAR_WORKDIR}/Scripts/Bash" # Verify location passed as first argument against the list of # directories that can have translation messages. By default, the @@ -64,12 +72,45 @@ function locale_isLocalizable { # that cannot have translation messages until a positive answer # says otherwise. for DIR in ${DIRS[@]};do - if [[ $LOCATION =~ $DIR ]];then - return 0 + + # Define the path part which is not present in the + # localizable directories. + local PATHDIFF=$(echo ${LOCATION} | sed -r "s,${DIR}/,,") + + # Define the path part that is present in the localizable + # directories. + local PATHSAME=$(echo ${LOCATION} | sed -r "s,/${PATHDIFF},,") + + # Initiate verification between location provided and + # localizable directories. + if [[ $LOCATION =~ "^$DIR$" ]];then + + # At this point the location provided is exactly the same + # that matches the localizable directories. There is + # nothing else to do here but return the script flow to + # this function caller. + L10N_ACCEPTED='yes' + break + + elif [[ ${PATHSAME} =~ "^${DIR}" ]] && [[ -d ${LOCATION} ]];then + + # At this point the location provided is a directory in + # the repository which doesn't match any localizable + # directory in the list, but it could be rendered if the + # --filter option is provided with the appropriate path + # argument. Print a suggestion about it. + cli_printMessage "${PATHSAME} --filter=\"$PATHDIFF\"" --as-suggestion-line + break + fi + done - # Output final answer to all verifications. - return 1 + # At this point, we are safe to say that the path provided isn't + # allow to have any localization for it. So, finish the script + # execution with an error message. + if [[ $L10N_ACCEPTED == 'no' ]];then + cli_printMessage "`gettext "The path provided doesn't support localization."`" --as-error-line + fi } diff --git a/Scripts/Bash/Functions/Locale/locale_updateMessageXmlDocbook.sh b/Scripts/Bash/Functions/Locale/locale_updateMessageXmlDocbook.sh index f54ddcc..b4301b5 100755 --- a/Scripts/Bash/Functions/Locale/locale_updateMessageXmlDocbook.sh +++ b/Scripts/Bash/Functions/Locale/locale_updateMessageXmlDocbook.sh @@ -43,7 +43,7 @@ function locale_updateMessageXmlDocbook { # Define absolute paths to Docbook main file. local TEMPLATE=$(cli_getFilesList ${ACTIONVAL} \ --maxdepth=1 --mindepth=1 --type='f' \ - --pattern="$(cli_getRepoName ${ACTIONVAL} -f)\.${EXTENSION}$") + --pattern=".+/$(cli_getRepoName ${ACTIONVAL} -f)\.${EXTENSION}$") # Verify existence of docbook's main template file. We cannot go # on without it. @@ -54,17 +54,14 @@ function locale_updateMessageXmlDocbook { # translation messages. local INSTANCE=$(cli_getTemporalFile "$(basename ${TEMPLATE})") - # Create instance from docbook's main file. - cp ${TEMPLATE} ${INSTANCE} + # Expand system entities definition. + cli_exportFunctions "Render/Docbook/docbook_doTranslation" + docbook_doTranslation # Expand translation markers inside instance. cli_expandTMarkers ${INSTANCE} # Expand system entities definition. - cli_exportFunctions "Render/Docbook/docbook_doTranslation" - docbook_doTranslation ${INSTANCE} - - # Expand system entities definition. cli_exportFunctions "Render/Docbook/docbook_expandSystemEntities" docbook_expandSystemEntities ${INSTANCE} @@ -84,7 +81,7 @@ function locale_updateMessageXmlDocbook { locale_prepareWorkingDirectory ${L10N_WORKDIR} # Create portable object template from instance. - xmllint --valid --noent ${INSTANCE} | xml2po -a - \ + xmllint --valid --noent ${INSTANCE} | xml2po -a -l ${CLI_LANG_LC} - \ | msgcat --output=${MESSAGES}.pot --width=70 --no-location - # Move out to initial location. @@ -97,5 +94,4 @@ function locale_updateMessageXmlDocbook { # object templates. locale_updateMessagePObjects "${MESSAGES}" - } diff --git a/Scripts/Bash/Functions/Locale/locale_updateMessages.sh b/Scripts/Bash/Functions/Locale/locale_updateMessages.sh index bbd8af1..32fd78d 100755 --- a/Scripts/Bash/Functions/Locale/locale_updateMessages.sh +++ b/Scripts/Bash/Functions/Locale/locale_updateMessages.sh @@ -29,6 +29,10 @@ function locale_updateMessages { + # Verify directory passed as non-option argument to be sure it + # supports localization. + locale_isLocalizable "${ACTIONVAL}" + # Prepare working directory to receive translation files. Don't # do this here. This location can be redefine later based on # deeper directory structures not provided as arguments to diff --git a/Scripts/Bash/Functions/Render/Docbook/docbook_doTranslation.sh b/Scripts/Bash/Functions/Render/Docbook/docbook_doTranslation.sh index 19036ce..b33a433 100755 --- a/Scripts/Bash/Functions/Render/Docbook/docbook_doTranslation.sh +++ b/Scripts/Bash/Functions/Render/Docbook/docbook_doTranslation.sh @@ -62,7 +62,7 @@ function docbook_doTranslation { # Define path to DocBook locales using models as reference. local DOCBOOK_LOCALES=$(echo $DOCBOOK_MODELS \ - | sed 's!^!Locales/!') + | sed "s!${TCAR_WORKDIR}/!${TCAR_WORKDIR}/Locales/!") # Define list of all locale files you want to combine. local DOCBOOK_PO_FILES="${DOCBOOK_LOCALES}/Gpl/${CLI_LANG_LC}/messages.po \ diff --git a/Scripts/Bash/Functions/Render/Docbook/docbook_expandSystemEntities.sh b/Scripts/Bash/Functions/Render/Docbook/docbook_expandSystemEntities.sh index 5246291..13cc248 100755 --- a/Scripts/Bash/Functions/Render/Docbook/docbook_expandSystemEntities.sh +++ b/Scripts/Bash/Functions/Render/Docbook/docbook_expandSystemEntities.sh @@ -32,7 +32,7 @@ function docbook_expandSystemEntities { # Define absolute path to both common and specific system # entities. - local ENTITIES_PATHS="$(cli_getFilesList ${DOCBOOK_MODELS}/Default/Book $(dirname ${TEMPLATE}) \ + local ENTITIES_PATHS="$(cli_getFilesList ${TCAR_WORKDIR}/Documentation/Models/Docbook/Default/Book $(dirname ${TEMPLATE}) \ --pattern='^.*/[[:alpha:]-]+\.ent$' --maxdepth=1 --mindepth=1 --type='f')" # Build definition of both common and specific system entities. diff --git a/Scripts/Bash/Functions/Render/render_doBaseActions.sh b/Scripts/Bash/Functions/Render/render_doBaseActions.sh index 8a0e4e0..af830a8 100755 --- a/Scripts/Bash/Functions/Render/render_doBaseActions.sh +++ b/Scripts/Bash/Functions/Render/render_doBaseActions.sh @@ -68,6 +68,14 @@ function render_doBaseActions { # centos-art.sh script as argument to. render_getDirTemplate + # Verify whether or not the source location of the path + # provided as argument to centos-art.sh script accepts or not + # localization messages. Don't produce localized content for + # repository components that don't accept it. + if [[ ! ${CLI_LANG_LC} =~ '^en' ]];then + cli_runFnEnvironment locale --is-localizable ${TEMPLATE} + fi + # Define the list of files to process. Use an array variable # to store the list of files to process. This make possible to # realize verifications like: is the current base directory @@ -130,7 +138,7 @@ function render_doBaseActions { # For all other cases, build a list of files to process # using the path value pass as argument. for FILE in $(cli_getFilesList ${TEMPLATE} \ - --pattern="^/.*${FLAG_FILTER}\.${RENDER_EXTENSION}$" \ + --pattern="^.+/${FLAG_FILTER}.*\.${RENDER_EXTENSION}$" \ --type="f");do FILES[((++${#FILES[*]}))]=$FILE done @@ -175,15 +183,15 @@ function render_doBaseActions { # Print action message. cli_printMessage "${FILE}" --as-template-line - # Define final location of output directory. - render_getDirOutput - # Define final location of translation file. TRANSLATION=$(dirname ${FILE} \ | sed -r 's!(Documentation|Identity)!Locales/\1!')/${CLI_LANG_LC}/messages.po # Define final location of template file. TEMPLATE=${FILE} + + # Define final location of output directory. + render_getDirOutput # Get relative path to file. The path string (stored in # FILE) has two parts: 1. the variable path and 2. the diff --git a/Scripts/Bash/Functions/Render/render_getDirOutput.sh b/Scripts/Bash/Functions/Render/render_getDirOutput.sh index 61faf77..fe6d470 100755 --- a/Scripts/Bash/Functions/Render/render_getDirOutput.sh +++ b/Scripts/Bash/Functions/Render/render_getDirOutput.sh @@ -72,10 +72,7 @@ function render_getDirOutput { # duplicating content (e.g., icons, brands, etc.) which doesn't # have any translation, nor any need to be translated. if [[ ! ${CLI_LANG_LC} =~ '^en' ]];then - cli_runFnEnvironment locale --is-localizable ${TEMPLATE} - if [[ $? -eq 0 ]];then - OUTPUT=${OUTPUT}/${CLI_LANG_LC} - fi + OUTPUT=${OUTPUT}/${CLI_LANG_LC} fi # Create final output directory, if it doesn't exist yet.