msgid ""

msgstr ""

"Project-Id-Version: centos-art (es_ES)\n"

"Report-Msgid-Bugs-To: CentOS Documentation SIG <centos-docs@centos.org>\n"

"POT-Creation-Date: 2011-06-16 22:57-0400\n"

"PO-Revision-Date: 2011-06-09 19:20-0400\n"

"Last-Translator: CentOS Documentation SIG <centos-docs@centos.org>\n"

"Language-Team: Español\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Front matter

msgid "The CentOS Artwork Repository"

msgstr ""

msgid "User's Guide"

msgstr ""

msgid "Alain"

msgstr ""

msgid "Reguera Delgado"

msgstr ""

msgid "2009"

msgstr ""

msgid "2010"

msgstr ""

msgid "2011"

msgstr ""

msgid "The CentOS Artwork SIG"

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 the section entitled 

">."

msgstr ""

msgid "Jun, 2011"

msgstr ""

msgid ""

"This manuals documents relevant information regarding the deployment, "

"organization, and administration of CentOS Artwork Repository."

msgstr ""

"Este manual documenta información relevante relacionada al desempeño, "

"organización y administración del repository de los trabjajos artísticos de "

"El Proyecto CentOS."

msgid "Introduction"

msgstr "Introducción"

msgid "Welcome to <emphasis>The CentOS Artwork Repository Manual</emphasis>."

msgstr ""

"Bienvenido al <emphasis>Manual del Repositorio Artístico CentOS</emphasis>."

msgid ""

"The CentOS Artwork Repository Manual describes how The CentOS Project "

"corporate visual identity is organized and produced inside the CentOS "

"Artwork Repository (

">). If you are looking for a comprehensive, task-oriented guide for "

"understanding how The CentOS Project corporate visual identity is produced, "

"this is the manual for you."

msgstr ""

msgid ""

"This guide assumes you have a basic understanding of The CentOS "

"Distribution. If you need help with CentOS, refer to the help page on The "

"CentOS Wiki (<ulink url=\"http://wiki.centos.org/Help\"/>) for a list of "

"different places you can find help."

msgstr ""

msgid "History"

msgstr ""

msgid ""

"The CentOS Artwork Repository started during a discussion about how to "

"automate the slide images of Anaconda, at CentOS Developers mailing list "

"(<ulink url=\"mailto:centos-devel@centos.org\">centos-devel@centos.org</"

"ulink>) around 2008. 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 ""

"Karanbirn Sighn considered the idea intresting and provided the "

"infrastructure necessary to support the effort. This way the 

"\"https://projects.centos.org/trac/artwork/\">CentOS Artwork SIG</ulink> and "

"the <ulink url=\"https://projects.centos.org/svn/artwork/\">CentOS Artwork "

"Repository</ulink> were officially created."

msgstr ""

msgid ""

"Once the CentOS Artwork Repository was available, Alain Reguera Delgado "

"uploaded the bash script for rendering Anaconda slides; Ralph Angenendt "

"documented it very well; and people started to download working copies of "

"CentOS Artwork Repository to produce slide images in their own languages."

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."

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 artwork that needed to be "

"produced. In this configuration, if you would want to produce the same "

"artwork 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."

msgstr ""

msgid ""

"Corporate identity concepts began to be considered. As referece, it was used "

"the book \"Corporate Identity\" by Wally Olins (1989) and 

"\"http://en.wikipedia.org/Corporate_identity\">Wikipedia</ulink> related "

"links. This way, the rendition script main's goal becomes into: "

"<emphasis>automating production of a monolithic corporate visual identity "

"structure, based on the mission and the release schema of The CentOS "

"Project</emphasis>."

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 \"The CentOS Artwork Repository\" documentation "

"manual is initiated."

msgstr ""

msgid "2010's"

msgstr ""

msgid ""

"Around 2010, the rendition script changed its name from <command>render.sh</"

"command> to <command>centos-art.sh</command> and became a collection of "

"functionalities where rendition was just one among others (e.g., "

"documentation and localization)."

msgstr ""

msgid ""

"The <command>centos-art.sh</command> 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 <command>centos-art.sh</command> 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 <quote>common functionalities</quote> and "

"<quote>specific functionalities</quote> inside <command>centos-art.sh</"

"command> script. Common functionalities are loaded when <command>centos-art."

"sh</command> 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 <command>centos-art.sh</command> 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 <filename class=\"directory\">~/bin</filename> directory that "

"point to <command>centos-art.sh</command> script. As default configuration, "

"inside The CentOS Distribution, the path to <filename class=\"directory\">~/"

"bin</filename> is included in the search path for commands (see PATH "

"environment variable). This way, using the centos-art command-line "

"interface, it is possible for us to execute the <command>centos-art.sh</"

"command> 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 <command>centos-"

"art.sh</command> 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 "

"divided out to separate directory structures: the design models and artistic "

"motifs directory structures. From this point on, the <command>centos-art.sh</"

"command> is able to produce themes as result of arbitrary combinations "

"between design models (structures) 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 <command>centos-art.sh</command> script. Additionally, "

"the texi2html program was used to produced customized XHTML output in "

"conjunction with CSS from The CentOS Webenv."

msgstr ""

msgid "2011's"

msgstr ""

msgid ""

"Around 2011, the <command>centos-art.sh</command> script was redesigned to "

"start translating XML-based files (e.g., SVG and Docbook files) through "

"<command>xml2po</command> 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 were consolidated as the most frequent tasks performed "

"inside the repository. Additionally, the prepare and tuneup functionalities "

"are also maintained as useful tasks."

msgstr ""

msgid ""

"In the documentation area, support for producing localized transformations "

"of DocBook XML DTD instances was added through the render and "

"locale functionalities. The render functionality uses the "

"xsltproc command-line XSLT parser in conjunction with the "

"styles provided by the <package>docbook-style-xsl</package> package, both of "

"them included inside The CentOS Distribution. The locale functionality "

"creates the localized portable object (PO) the "

"render functionality needs to produce localized transformations "

"of DocBook XML DTD instances."

msgstr ""

msgid ""

"To build DocBook documentation, it was considered the idea of using concepts "

"behind repository directory structure as base, not the opposite (as I've "

"been doing with Texinfo backend, so far)."

msgstr ""

msgid ""

"Producing documentation through DocBook XML as default documentation backend "

"consolidates render and locale even more. In this "

"configuration, once the DocBook files are written, you use locale</"

"code> functionality to localize the DocBook files in your prefered language "

"and later, using render functionality, you produce the XTHML "

"and PDF outputs as specified in a XSLT or DSL customization layer."

msgstr ""

msgid "Copying conditions"

msgstr ""

msgid "Copyright © 2009, 2010, 2011 The CentOS Artwork SIG"

msgstr ""

msgid ""

"Everyone is permitted to copy and distribute verbatim copies of this license "

"document, but changing it is not allowed."

msgstr ""

msgid "Preamble"

msgstr ""

msgid ""

"The CentOS Artwork Repository organizes files in a very specific way to "

"implement The CentOS Project corporate visual identity. This very specific "

"organization of files must be considered part of <command>centos-art.sh</"

"command> script, a bash script that automate most of the frequent tasks "

"inside the repository."

msgstr ""

msgid ""

"The <command>centos-art.sh</command> script and the organization of files it "

"needs to work are not in the public domain; they are copyrighted and there "

"are restrictions on their distribution, but these restrictions are designed "

"to permit everything that a good cooperating citizen would want to do. What "

"is not allowed is to try to prevent others from further sharing any version "

"of this program that they might get from you."

msgstr ""

msgid ""

"Specifically, we want to make sure that you have the right to give away "

"copies of <command>centos-art.sh</command> script and the organization of "

"files it needs to work, that you receive source code or else can get it if "

"you want it, that you can change this program or use pieces of it in new "

"free programs, and that you know you can do these things."

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 "

"<command>centos-art.sh</command> script, you must give the recipients all "

"the rights that you have. You must make sure that they, too, receive or can "

"get the source code. And you must tell them their rights."

msgstr ""

msgid ""

"Also, for our own protection, we must make certain that everyone finds out "

"that there is no warranty for the <command>centos-art.sh</command> script. "

"If this program 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 <command>centos-art.sh</command> script is released as a GPL work. "

"Individual packages used by <command>centos-art.sh</command> script include "

"their own licenses and the <command>centos-art.sh</command> script license "

"applies to all packages that it does not clash with. If there is a clash "

"between the <command>centos-art.sh</command> script license and individual "

"package licenses, the individual package license applies instead."

msgstr ""

msgid ""

"The precise conditions of the license for the <command>centos-art.sh</"

"command> script are found in the <xref linkend=\"licenses-gpl\"/>. This "

"manual specifically is covered by the <xref linkend=\"licenses-gfdl\"/>."

msgstr ""

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 its visual "

"manifestions (e.g., GNU/Linux Distributions, Websites, Stationery, etc.) "

"and, this way, it provides recognition among other similar projects "

"available on the Internet."

msgstr ""

msgid ""

"Both The CentOS Brand and all the visual manifestations that derivate from "

"it are available for you to study and propose improvement around a good "

"citizen's will at The CentOS Community environment, but you are not allowed "

"to redistribute them elsewhere, without the given permission of The CentOS "

"Project."

msgstr ""

msgid ""

"If you need to redistribute either The CentOS Brand or any visual "

"manifestation derived from it, write your intentions to the The CentOS "

"Developers mailing list (centos-devel@centos.org)."

msgstr ""

msgid "Document convenctions"

msgstr ""

msgid ""

"In this manual the personal pronoun <emphasis>we</emphasis> is used to "

"repesent <emphasis>The CentOS Artwork SIG</emphasis>, the group of persons "

"that build The CentOS Project corporate visual identity through the CentOS "

"Artwork Repository."

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:"

msgstr ""

msgid "command"

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:"

msgstr ""

msgid ""

"Use the <command>centos-art identity --render='path/to/dir'</command> "

"command to produce contents inside the <filename class=\"directory\">trunk/"

"Identity</filename> directory structure."

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:"

msgstr ""

msgid ""

"The <filename>init.sh</filename> file in <filename class=\"directory\">trunk/"

"Scripts/Bash/Cli/</filename> directory is the initialization script, written "

"in Bash, used to automate most of tasks in the repository."

msgstr ""

msgid ""

"The <command>centos-art</command> command uses the <package>ImageMagick</"

"package> RPM package to convert images from PNG format to other formats."

msgstr ""

msgid "key"

msgstr ""

msgid "A key on the keyboard is shown in this style. For example:"

msgstr ""

msgid ""

"To use <keycap>TAB</keycap> completion to list particular files in a "

"directory, type @command{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 "key-combination"

msgstr ""

msgid "A combination of keystrokes is represented in this way. For example:"

msgstr ""

msgid ""

"The <keycombo action=\"simul\"><keycap>Ctrl</keycap><keycap>Alt</"

"keycap><keycap>Backspace</keycap></keycombo> key combination exits your "

"graphical session and returns you to the graphical login screen or the "

"console."

msgstr ""

#, no-wrap

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:"

msgstr ""

msgid ""

"The <command>ls</command> command displays the contents of a directory. For "

"example: <programlisting>\n"

"Config                          help_renameEntry.sh\n"

"help_copyEntry.sh               help_restoreCrossReferences.sh\n"

"help_deleteCrossReferences.sh   help_searchIndex.sh\n"

"</programlisting> The output returned in response to the command (in this "

"case, the contents of the directory) is shown in this style."

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:"

msgstr ""

msgid ""

"Remember that Linux is case sensitive. In other words, a rose is not a ROSE "

"is not a rOsE."

msgstr ""

msgid ""

"The directory <filename class=\"directory\">/usr/share/doc/</filename> "

"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."

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."

msgstr ""

msgid ""

"Be careful to remove only the necessary partitions. Removing other "

"partitions could result in data loss or a corrupted system environment."

msgstr ""

msgid "Usage convenctions"

msgstr ""

msgid ""

"The CentOS Artwork Repository is supported by Subversion (http://subversion."

"tigris.org/), 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."

msgstr ""

msgid ""

"When using Subversion there is 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."

msgstr ""

msgid "Policy"

msgstr ""

msgid ""

"The CentOS Artwork Repository is a collaborative tool that anyone can have "

"access to. However, changing that tool in any form is something that should "

"be requested in the CentOS Developers mailing list (centos-devel@centos."

"org). Generally, people download working copies from CentOS Artwork "

"Repository, study the repository organization, make some changes in their "

"working copies, make some tests to verify such changes do work the way "

"expected and finally request access to commit them up to the CentOS Artwork "

"Repository (i.e., the source repository) for others to benefit from them."

msgstr ""

msgid ""

"Once you've received access to commit your changes, there is no need for you "

"to request permission again to commit other changes from your working copy "

"to CentOS Artwork Repository as long as you behave as a <emphasis>good "

"cooperating citizen</emphasis>. Otherwise, your rights to commit changes "

"might be temporarly revoked or permanently banished."

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. Anyway, 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 which is: to provide a colaborative "

"tool for The CentOS Community where The CentOS Project corporate visual "

"identity is built and maintained by The CentOS Community itself."

msgstr ""

msgid ""

"It is also important to remember that all the program and documentation "

"source files inside CentOS Artwork Repository must comply the terms of 

"linkend=\"licenses-gpl\"/> and <xref linkend=\"licenses-gfdl\"/> "

"respectively in order for them to remain inside the repository."

msgstr ""

msgid "Work lines"

msgstr ""

msgid ""

"Content production inside the repository is organized by <emphasis>work "

"lines</emphasis>. There are three major work lines of production inside The "

"CentOS Artwork Repository, which are: <emphasis>Graphic design</emphasis>, "

"<emphasis>Documentation</emphasis> and <emphasis>Localization</emphasis>. "

"The specific way of producing content inside each specific work line is "

"standardized by mean of <command>centos-art.sh</command> script (which in "

"turn, can be considered a work line by itself [e.g., the "

"<emphasis>Automation</emphasis> work line]). The <command>centos-art.sh</"

"command> script provides one specific functionality for automating each "

"major work line of content production (e.g., render for "

"producing images, help for manage documentation, and "

"locale for localizing contents)."

msgstr ""

msgid ""

"The graphic design work line exists to cover brand design, typography design "

"and themes design mainly. Additionally, some auxiliar areas like icon "

"design, illustration design, brushes design, patterns designs and palettes "

"of colors are also included here for completeness. The graphic design work "

"line is organized in the <filename class=\"directory\">trunk/Identity</"

"filename> directory."

msgstr ""

msgid ""

"The documentation work line exists to describe what each directory inside "

"the CentOS Artwork Repository is for, the conceptual ideas behind them and, "

"if possible, how automation scripts make use of them. The documentation work "

"line is organized in the <filename class=\"directory\">trunk/Manuals</"

"filename> directory."

msgstr ""

msgid ""

"The localization work line exists to provide the translation messages "

"required to produce content in different languages. Translation messages "

"inside the repository are stored as portable objects (e.g., .po, .pot) and "

"machine objects (.mo). The localization work line is organized in the "

"<filename class=\"directory\">trunk/Locales</filename> directory."

msgstr ""

msgid ""

"The automation work line exists to standardize content production inside the "

"working copies of CentOS Artwork Repository. Here is developed the "

"<command>centos-art.sh</command> script, a bash script specially designed to "

"automate most frequent tasks (e.g., rendition, documentation and "

"localization) inside the repository. There is no need to type several tasks, "

"time after time, if they can be programmed into just one executable script. "

"The automation work line is organized in the 

"\">trunk/Scripts</filename> directory."

msgstr ""

msgid "Relation between directories"

msgstr ""

msgid ""

"In order for automation scripts to produce content inside a working copy of "

"CentOS Artwork Repository, it is required that all work lines be related "

"somehow. The relation is used by automation scripts to know where to retrive "

"the information they need to work with (e.g., design model, translation "

"messages, output locations, etc.). This kind of relation is built using two "

"path constructions named <emphasis>master paths</emphasis> and "

"<emphasis>auxiliar paths</emphasis>."

msgstr ""

msgid ""

"The master path points only to directories that contain source files (e.g., "

"SVG files) required to produce output base content (e.g., PNG files) through "

"automation scripts. Each master path inside the repository may have several "

"auxiliar paths associated, but auxiliar paths can only have one master path "

"associated."

msgstr ""

msgid ""

"Master paths used for producing images through SVG rendition are organized "

"under <filename class=\"directory\">trunk/Identity/Models</filename> "

"directory structure and the auxiliar paths under 

"\">trunk/Identity/Images</filename>, <filename class=\"directory\">trunk/"

"Locales</filename> and <filename class=\"directory\">trunk/Manuals</"

"filename> directory structures."

msgstr ""

msgid ""

"Auxiliar paths can point either to directories or files. When an auxiliar "

"path points to a directory, that directory contains information that "

"modifies somehow the content produced from master paths (e.g., translation "

"messages) or provides the output information required to know where the "

"content produced from the master path should be stored. When an auxiliar "

"path points to a file, that file has no other purpose but to document the "

"master path it refers to."

msgstr ""

msgid ""

"Auxiliar paths should never be modified under any reason but to satisfy the "

"relationship with the master path. Liberal change of auxiliar paths may "

"suppress the conceptual idea they were initially created for; and certainly, "

"automation scripts may stop working as expected."

msgstr ""

msgid ""

"The relationship between auxiliar paths and master paths is built by "

"combining the master path and the second level directory structures of the "

"repository. The master path is considered the path identifier and the "

"repository second level directory structure is considered the common part of "

"the path where the path identifier is appended to. So, if we have the master "

"path <filename class=\"directory\">trunk/Identity/Models/Brands</filename>, "

"we'll end up having, at least, the <filename class=\"directory\">trunk/"

"Identity/Images/Brands</filename> auxiliar path for storing output files "

"and, optionally, one path under <filename class=\"directory\">trunk/Manuals</"

"filename> for storing documentation and one path under 

"\"directory\">trunk/Locales</filename> for storing localizations."

msgstr ""

msgid "Syncronizing paths"

msgstr ""

msgid ""

"Once both master paths and their auxiliar paths have been set, they "

"shouldn't be changed. Assuming one master path must be changed it is "

"required that all related auxiliar paths be changed, too. This is required "

"in order for master paths to retain their relation with auxiliar paths. This "

"process of keeping relation between master paths and auxiliar paths is known "

"as <emphasis>path syncronization</emphasis>."

msgstr ""

msgid ""

"Path syncronization is required for automation scripts to know where to "

"store final output, where to retrive translation messages, documentation, "

"and any information that might be desired. If the relation between master "

"paths and auxiliar paths is lost, there is no way for <command>centos-art."

"sh</command> script to know where to retrive the information it needs to "

"work with. Path syncronization is the way we use to organize and extend the "

"information stored in the repository."

msgstr ""

msgid ""

"Path syncronization may imply 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 "