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" "Last-Translator: Documentation SIG\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" #. 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" msgstr "" #. 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 "2012" msgstr "" msgid "" "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 ." msgstr "" msgid "1.0" msgstr "" msgid "Today" msgstr "" msgid "Under development." msgstr "" msgid "Preface" msgstr "" msgid "Overview" msgstr "" msgid "" "Welcome to The CentOS Artwork Repository User's Guide, the official documentation of 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." msgstr "" msgid "" "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." 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, " "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." 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." 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." msgstr "" msgid "" " 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." 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:" 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 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." 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 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." msgstr "" msgid "" "The centos-art command uses the ImageMagick 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 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:" msgstr "" msgid "" "The CtrlAltBackspace 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, the ls " "command displays the contents of a directory using this style:" msgstr "" #, no-wrap msgid "" "\n" "render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh\n" "render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh \n" "render_getDirOutput.sh render.sh\n" msgstr "" msgid "" "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:" msgstr "" msgid "$" msgstr "" msgid "#" msgstr "" msgid "[centos@projects centos]$" msgstr "" msgid "projects login:" msgstr "" #, no-wrap 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." 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." 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 /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." 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 "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." msgstr "" msgid "Repository" msgstr "" msgid "Repository Convenctions" msgstr "" msgid "Repository Mission" msgstr "" msgid "" "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." 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." 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:" msgstr "" msgid "" "The trunk/ directory is where " "development changes take place." msgstr "" msgid "" "The branches/ directory is where " "maintainance changes take place." msgstr "" msgid "" "The tags/ directory is where final " "releases take place." 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." 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 " "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." 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." 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 ." msgstr "" msgid "" "The visual identity work line takes palce in the trunk/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." 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 ." msgstr "" msgid "" "The localization work line takes palce in the trunk/" "Locales directory." msgstr "" #, fuzzy msgid "Documentation" msgstr "Licencia de Documentación Libre de GNU" 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.)." 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." msgstr "" msgid "" "The documentation work line takes palce in the trunk/" "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." 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." msgstr "" msgid "" "The packaging work line takes palce in the trunk/" "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 ." msgstr "" msgid "" "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." msgstr "" msgid "Repository File Names" 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." msgstr "" msgid "Repository Path Types" 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." msgstr "" msgid "Master Paths" 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:" msgstr "" msgid "trunk/Identity/Models/Brands" msgstr "" msgid "trunk/Manuals/Tcar-ug" msgstr "" msgid "trunk/Identity/Models/Themes/Default/Distro/5/Anaconda" msgstr "" msgid "Auxiliar Paths" 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:" msgstr "" msgid "trunk/Identity/Images/Brands" msgstr "" msgid "trunk/Manuals/Tcar-ug/es_ES" msgstr "" msgid "trunk/Locales/Manuals/Tcar-ug/es_ES" msgstr "" msgid "trunk/Identity/Images/Themes/Flame/3/Distro/5/Anaconda/es_ES" msgstr "" msgid "trunk/Locales/Identity/Models/Default/Distro/5/Anaconda/es_ES" 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." 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." 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." 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." 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." 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." 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." 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