From 708c99b6fc106da637ca88673f28758abe350f2f Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: Jul 03 2011 02:13:52 +0000 Subject: Update tcar-ug es_ES translation messages ids. --- diff --git a/L10n/Manuals/TCAR-UG/Docbook/es_ES/messages.po b/L10n/Manuals/TCAR-UG/Docbook/es_ES/messages.po index 864a74b..dfb7524 100644 --- a/L10n/Manuals/TCAR-UG/Docbook/es_ES/messages.po +++ b/L10n/Manuals/TCAR-UG/Docbook/es_ES/messages.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: centos-art (es_ES)\n" "Report-Msgid-Bugs-To: CentOS Documentation SIG \n" -"POT-Creation-Date: 2011-06-17 14:25-0400\n" +"POT-Creation-Date: 2011-07-02 22:10-0400\n" "PO-Revision-Date: 2011-06-09 19:20-0400\n" "Last-Translator: CentOS Documentation SIG \n" "Language-Team: Español\n" @@ -11,6 +11,13 @@ msgstr "" "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: '/home/centos/artwork/trunk/Identity/Images/Manuals/Corporate/" +"monolithic.png'; md5=ff182c5fc417f433bebbe134e5fb9c0f" +msgstr "" + #. Front matter msgid "The CentOS Artwork Repository" msgstr "El Repositorio Artístico de CentOS" @@ -37,57 +44,1366 @@ 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 ." +"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 "5.5-1" +msgstr "" + +msgid "Fri Jun 24, 2011" +msgstr "" + +msgid "..." +msgstr "" + +#, fuzzy +msgid "" +"This manuals documents relevant information regarding the deployment, " +"organization, and administration of The 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 The CentOS Artwork Repository User's Guide." +msgstr "" + +msgid "" +"The " +"CentOS Artwork Repository User's Guide 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 Identity is produced, this is the manual " +"for you." +msgstr "" + +msgid "This manual is divided in the following categories:" +msgstr "" + +msgid "Repository" +msgstr "Repositorio" + +#, fuzzy +msgid "Corporate Identity" +msgstr "Identidad visual" + +msgid "Localization" +msgstr "Localización" + +msgid "Documentation" +msgstr "Documentación" + +msgid "Automation" +msgstr "" + +msgid "This manual discusses the following topics:" +msgstr "" + +msgid "" +"The " +"CentOS Artwork Repository, what it is, how it is organized, the " +"things you can achieve inside it and how you can do such things." +msgstr "" + +msgid "" +"The CentOS Project as organization and the components that define its visual identity. " +"Here we dig in the ground and climb up to the sky, looking for the roots, " +"flowers and thorns The " +"CentOS Project is made of." +msgstr "" + +msgid "" +"This manual assumes you have a basic understanding of The CentOS " +"Distribution. If you need help with it, refer to the help page on The CentOS Wiki for a list of " +"different places you can find help." +msgstr "" + +#, fuzzy +msgid "Document Convenctions" +msgstr "Convenciones del documento" + +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 "" + +#, fuzzy +msgid "combination" +msgstr "Documentación" + +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 "" + +#, fuzzy +msgid "Send in Your Feedback" +msgstr "Envíe sus comentarios" + +msgid "" +"If you find an error in the The CentOS Artwork Repository, or if you " +"have thought of a way to make this manual better, we would like to hear from " +"you! Share your suggestions in The CentOS Artwork Mailing List." +msgstr "" + +msgid "" +"When you make suggestion, try to be as specific as possible. For example, if " +"you have found an error in the manual, include the section number and some " +"of the surrounding text so we can find it easily." +msgstr "" + +#, fuzzy +msgid "Repository Convenctions" +msgstr "Organización del repositorio" + +#, fuzzy +msgid "Repository Mission" +msgstr "Repositorio" + +msgid "" +"The " +"CentOS Artwork Repository exists to oraganize the files related to " +"The CentOS Project Corporate Visual Identity." +msgstr "" + +#, fuzzy +msgid "Repository Layout" +msgstr "Organización del repositorio" + +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 in the repository provides organization " +"through a convenctional trunk, branches and " +"tags layout. In this configuration the trunk directory is where main changes take place, " +"the tags directory is where frozen " +"copies of trunk changes are placed " +"in for releasing, and the branches " +"directory is an intermediate place between trunk and tags states " +"where changes take place before being merged into trunk and finally released into tags." +msgstr "" + +msgid "" +"The second level of directories in the repository provides organization for " +"repository work lines, as described in ." +msgstr "" + +msgid "" +"All other subsequent levels of directories in the repository, from third " +"level on, are created to organize specific concepts related to the work line " +"they are in." +msgstr "" + +#, fuzzy +msgid "Repository Work Lines" +msgstr "Repositorio" + +msgid "" +"To organize content production inside The CentOS Artwork Repository, " +"production has been divided into individual work lines that relate one " +"another based on the idea of doing one thing well. Later, the results " +"produced individually by each work line are combined to achieve a higher " +"purpose. Work lines, as conceived here, provide the relayable output " +"components the production cycle inside The CentOS Artwork Repository " +"needs to let everyone to work syncronized in a descentralized environment." +msgstr "" + +msgid "Visual Identity" +msgstr "Identidad visual" + +msgid "" +"In the production cycle, the first step takes place through graphic design. " +"It is focused on preparing design models for all the visual manifestation " +"The CentOS Project is made of. Here, graphic designers describe the visual " +"characteristics of each visual manifestation (e.g., image dimensions, " +"position of text in the visible area, translation markers, etc.). Later, " +"once design models have been defined, graphic designers take care of " +"artistic motifs to define the visual style of those design models already " +"created (e.g., how they look and feel)." +msgstr "" + +msgid "" +"Finally, graphic designers use the render functionality " +"of centos-art.sh script to combine both design models and " +"artistic motifs in order to produce the final images required by each visual " +"manifestaions." +msgstr "" + +msgid "" +"The second step in the production cycle is to localize source files (e.g., " +"SVG, DocBook, Shell scripts). This step makes possible to produce localized " +"images, localized documentation and localized automation scripts." +msgstr "" + +msgid "" +"The localization tasks are carried on by translators using the " +"locale functionality of the centos-art.sh script which take 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 third step in the production cycle is to document The CentOS Artwork " +"Repository, what it is and how to use it. This step provides the " +"conceptual ideas used as base to edificate The CentOS Project Corporate Visual Identity and is " +"implemented through The CentOS Artwork Repository User's Guide." +msgstr "" + +msgid "" +"To write documentation, documentors use the help " +"functionality of centos-art.sh script which provide an " +"consistent interface for building documentation through different " +"documentation backends (e.g., Texinfo and DocBook)." +msgstr "" + +msgid "" +"The fourth step in the production cycle is to automate frequent tasks inside " +"The " +"CentOS Artwork Repository. This step closes the production cycle and " +"provides the production standards needed by all different work lines to " +"coexist together. Here is where the centos-art.sh script " +"and all its functionalities (e.g., render for " +"rendition, help for documentation, locale for localization, etc.) are developed." +msgstr "" + +msgid "" +"At this point it should be obvious, but we consider worth to remember that: " +"there is no need to type several tasks, time after time, if they can be " +"programmed into just one executable script." +msgstr "" + +#, fuzzy +msgid "Repository File Names" +msgstr "Organización del repositorio" + +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.)." +msgstr "" + +msgid "" +"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 "" + +#, fuzzy +msgid "Repository Path Types" +msgstr "Organización del repositorio" + +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: " +"trunk/Identity/" +"Models/Brandstrunk/Manuals/Repository/Docbooktrunk/Identity/Models/" +"Themes/Default/Distro/5/Anaconda" +msgstr "" + +msgid "Auxiliar paths" +msgstr "" + +msgid "" +"An auxiliar path refers a directory inside the repository considered " +"auxiliar for the 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 is rendered by automation scripts. Examples of " +"auxiliar paths inside the repository include: " +"trunk/Identity/" +"Images/Brandstrunk/Manuals/Repository/Docbook/es_EStrunk/Locales/Manuals/" +"Repository/Docbook/es_EStrunk/Identity/Images/" +"Themes/Flame/3/Distro/5/Anaconda/es_EStrunk/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/Repository/Docbook " +"master path as argument, it will produce The CentOS Artwork " +"Repository User's Guide in Spanish language using " +"translation messages from trunk/Locales/" +"Manuals/Repository/Docbook/es_ES auxiliar path and saving output " +"files inside trunk/Manuals/Repository/Docbook/" +"es_ES auxiliar path." +msgstr "" + +#, fuzzy +msgid "Syncronizing Repository Paths" +msgstr "Sincronización de caminos" + +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. Path syncronization is the " +"way we use through to organize and extend the information stored in the " +"repository." +msgstr "" + +msgid "" +"Path syncronization involves 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 movement." +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. Otherwise, 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 is no full implementation of path syncronization " +"process inside centos-art.sh script and it is somthing we " +"need to do oursleves. However, the texinfo backend of " +"help functionality which provides a restricted implementation " +"of path syncronization to this specific area of documentation through the " +", and