| msgid "" |
| msgstr "" |
| "Project-Id-Version: PACKAGE VERSION\n" |
| "POT-Creation-Date: 2011-07-02 22:10-0400\n" |
| "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" |
| "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" |
| "Language-Team: LANGUAGE <LL@li.org>\n" |
| "MIME-Version: 1.0\n" |
| "Content-Type: text/plain; charset=UTF-8\n" |
| "Content-Transfer-Encoding: 8bit\n" |
| |
| |
| |
| msgid "" |
| "@@image: '/home/centos/artwork/trunk/Identity/Images/Manuals/" |
| "Corporate/monolithic.png'; md5=ff182c5fc417f433bebbe134e5fb9c0f" |
| msgstr "" |
| |
| |
| 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 <xref linkend=\"licenses-gfdl\"/>." |
| msgstr "" |
| |
| msgid "5.5-1" |
| msgstr "" |
| |
| msgid "Fri Jun 24, 2011" |
| msgstr "" |
| |
| msgid "..." |
| msgstr "" |
| |
| msgid "" |
| "This manuals documents relevant information regarding the " |
| "deployment, organization, and administration of <ulink type=\"https" |
| "\" url=\"https://projects.centos.org/svn/artwork\">The CentOS " |
| "Artwork Repository</ulink>" |
| msgstr "" |
| |
| msgid "Introduction" |
| msgstr "" |
| |
| msgid "" |
| "Welcome to <citetitle><ulink type=\"https\" url=\"https://projects." |
| "centos.org/svn/artwork\">The CentOS Artwork Repository</ulink> " |
| "User's Guide</citetitle>." |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> User's Guide describes how " |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> Corporate Visual Identity is organized and produced " |
| "inside <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink>. If you are looking " |
| "for a comprehensive, task-oriented guide for understanding how " |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> Corporate Identity is produced, this is the manual " |
| "for you." |
| msgstr "" |
| |
| msgid "This manual is divided in the following categories:" |
| msgstr "" |
| |
| msgid "Repository" |
| msgstr "" |
| |
| msgid "Corporate Identity" |
| msgstr "" |
| |
| msgid "Localization" |
| msgstr "" |
| |
| msgid "Documentation" |
| msgstr "" |
| |
| msgid "Automation" |
| msgstr "" |
| |
| msgid "This manual discusses the following topics:" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink>, what it is, how it is " |
| "organized, the things you can achieve inside it and how you can do " |
| "such things." |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> 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 <ulink type=\"http\" url=" |
| "\"http://www.centos.org\">The CentOS Project</ulink> 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 " |
| "<ulink url=\"http://wiki.centos.org/Help\">The CentOS Wiki</ulink> " |
| "for 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 " |
| "<keycap>Enter</keycap> 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 render trunk/Identity/Images/Themes/" |
| "TreeFlower/4/Distro/5/Anaconda --filter=\"01-welcome\"</command> " |
| "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 <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 " |
| "<filename>ImageMagick</filename> 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</command>, then a character, and " |
| "finally the <keycap>Tab</keycap> 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 <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 "" |
| |
| |
| 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 " |
| "<command>ls</command> command displays the contents of a directory " |
| "using this style:" |
| msgstr "" |
| |
| |
| 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 "" |
| |
| |
| 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, <userinput>text</userinput> is displayed in this style: To " |
| "boot your system into the text based installation program, you must " |
| "type in the <userinput>text</userinput> command at the <prompt>boot:" |
| "</prompt> 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, <replaceable>version-number</replaceable> is displayed in " |
| "this style: The directory for the kernel source is <filename class=" |
| "\"directory\">/usr/src/kernels/<replaceable>version-number</" |
| "replaceable>/</filename>, where <replaceable>version-number</" |
| "replaceable> 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 <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 "Send in Your Feedback" |
| msgstr "" |
| |
| msgid "" |
| "If you find an error in the <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink>, or if you have thought of a way to make this manual better, " |
| "we would like to hear from you! Share your suggestions in <ulink " |
| "type=\"http\" url=\"http://lists.centos.org/mailman/centos-artwork" |
| "\">The CentOS Artwork Mailing List</ulink>." |
| 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 "" |
| |
| msgid "Repository Convenctions" |
| msgstr "" |
| |
| msgid "Repository Mission" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> exists to oraganize the " |
| "files related to <ulink type=\"http\" url=\"http://www.centos.org" |
| "\">The CentOS Project</ulink> Corporate Visual Identity." |
| msgstr "" |
| |
| msgid "Repository Layout" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> is supported by <ulink url=" |
| "\"http://subversion.tigris.org/\">Subversion</ulink>, 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 "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> is made of one " |
| "<quote>source repository</quote> and many <quote>working copies</" |
| "quote> 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 <quote>trunk</quote>, " |
| "<quote>branches</quote> and <quote>tags</quote> layout. In this " |
| "configuration the <filename class=\"directory\">trunk</filename> " |
| "directory is where main changes take place, the <filename class=" |
| "\"directory\">tags</filename> directory is where frozen copies of " |
| "<filename class=\"directory\">trunk</filename> changes are placed " |
| "in for releasing, and the <filename class=\"directory\">branches</" |
| "filename> directory is an intermediate place between <filename " |
| "class=\"directory\">trunk</filename> and <filename class=\"directory" |
| "\">tags</filename> states where changes take place before being " |
| "merged into <filename class=\"directory\">trunk</filename> and " |
| "finally released into <filename class=\"directory\">tags</filename>." |
| msgstr "" |
| |
| msgid "" |
| "The second level of directories in the repository provides " |
| "organization for repository work lines, as described in <xref " |
| "linkend=\"repo-convs-worklines\"/>." |
| 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 "" |
| |
| msgid "Repository Work Lines" |
| msgstr "" |
| |
| msgid "" |
| "To organize content production inside <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>, 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 <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> needs to let everyone to work syncronized in a " |
| "descentralized environment." |
| msgstr "" |
| |
| msgid "Visual Identity" |
| msgstr "" |
| |
| 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 <ulink type=\"http\" url=\"http://www.centos.org" |
| "\">The CentOS Project</ulink> 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 <function>render</function> " |
| "functionality of <command>centos-art.sh</command> 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 " |
| "<function>locale</function> functionality of the <command>centos-" |
| "art.sh</command> script which take care of retriving translatable " |
| "strings from source files and provide a consistent localization " |
| "interface based on GNU <application>gettext</application> multi-" |
| "lingual message production tool set and <command>xml2po</command> " |
| "command." |
| msgstr "" |
| |
| msgid "" |
| "The third step in the production cycle is to document <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink>, what it is and how to use it. " |
| "This step provides the conceptual ideas used as base to edificate " |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> Corporate Visual Identity and is implemented " |
| "through <citetitle><ulink type=\"https\" url=\"https://projects." |
| "centos.org/svn/artwork\">The CentOS Artwork Repository</ulink> " |
| "User's Guide</citetitle>." |
| msgstr "" |
| |
| msgid "" |
| "To write documentation, documentors use the <function>help</" |
| "function> functionality of <command>centos-art.sh</command> 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 <ulink type=\"https\" url=\"https://projects.centos." |
| "org/svn/artwork\">The CentOS Artwork Repository</ulink>. This step " |
| "closes the production cycle and provides the production standards " |
| "needed by all different work lines to coexist together. Here is " |
| "where the <command>centos-art.sh</command> script and all its " |
| "functionalities (e.g., <function>render</function> for rendition, " |
| "<function>help</function> for documentation, <function>locale</" |
| "function> 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 "" |
| |
| msgid "Repository File Names" |
| msgstr "" |
| |
| msgid "" |
| "Inside <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink>, file names are all " |
| "written in lowercase (e.g., <filename>01-welcome.png</filename>, " |
| "<filename>splash.png</filename>, <filename>anaconda_header.png</" |
| "filename>, etc.) and directory names are all written capitalized (e." |
| "g., <filename role=\"directory\">Identity</filename>, <filename " |
| "role=\"directory\">Themes</filename>, <filename role=\"directory" |
| "\">Motifs</filename>) and sometimes in cammel case (e.g., <filename " |
| "role=\"directory\">TreeFlower</filename>, 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 "" |
| |
| msgid "Repository Path Types" |
| msgstr "" |
| |
| msgid "" |
| "In order for automation scripts to produce content inside a working " |
| "copy of <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink>, 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 <emphasis>master paths</" |
| "emphasis> and <emphasis>auxiliar paths</emphasis>." |
| 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: <itemizedlist><listitem><para><filename class=\"directory" |
| "\">trunk/Identity/Models/Brands</filename></para></" |
| "listitem><listitem><para><filename class=\"directory\">trunk/" |
| "Manuals/Repository/Docbook</filename></para></" |
| "listitem><listitem><para><filename class=\"directory\">trunk/" |
| "Identity/Models/Themes/Default/Distro/5/Anaconda</filename></para></" |
| "listitem></itemizedlist>" |
| 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: " |
| "<itemizedlist><listitem><para><filename class=\"directory\">trunk/" |
| "Identity/Images/Brands</filename></para></" |
| "listitem><listitem><para><filename class=\"directory\">trunk/" |
| "Manuals/Repository/Docbook/es_ES</filename></para></" |
| "listitem><listitem><para><filename class=\"directory\">trunk/" |
| "Locales/Manuals/Repository/Docbook/es_ES</filename></para></" |
| "listitem><listitem><para><filename class=\"directory\">trunk/" |
| "Identity/Images/Themes/Flame/3/Distro/5/Anaconda/es_ES</filename></" |
| "para></listitem><listitem><para><filename class=\"directory\">trunk/" |
| "Locales/Identity/Models/Default/Distro/5/Anaconda/es_ES</filename></" |
| "para></listitem></itemizedlist>" |
| 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 <filename " |
| "class=\"directory\">Identity</filename>, <filename class=\"directory" |
| "\">Manuals</filename> and <filename class=\"directory\">Scripts</" |
| "filename> directories are always used to create the master paths " |
| "and the output auxiliar paths. The <filename class=\"directory" |
| "\">Locales</filename> directory, on the other hand, is always used " |
| "to create localization auxiliar paths for all the master paths " |
| "available under <filename class=\"directory\">Identity</filename>, " |
| "<filename class=\"directory\">Manuals</filename> and <filename " |
| "class=\"directory\">Scripts directories</filename>." |
| msgstr "" |
| |
| msgid "" |
| "For example, if the <envar>LANG</envar> environment variable is set " |
| "to <literal>es_ES.UTF-8</literal> and you execute the " |
| "<function>render</function> functionality of <command>centos-art." |
| "sh</command> script with the <filename class=\"directory\">trunk/" |
| "Manuals/Repository/Docbook</filename> master path as argument, it " |
| "will produce <citetitle><ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> User's Guide</citetitle> in Spanish language using " |
| "translation messages from <filename class=\"directory\">trunk/" |
| "Locales/Manuals/Repository/Docbook/es_ES</filename> auxiliar path " |
| "and saving output files inside <filename class=\"directory\">trunk/" |
| "Manuals/Repository/Docbook/es_ES</filename> 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 <quote>connected</quote> between themselves 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 " |
| "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 <command>centos-art.sh</" |
| "command> script. The <command>centos-art.sh</command> 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 <command>centos-art.sh</command> " |
| "script and it is somthing we need to do oursleves. However, the " |
| "<quote>texinfo</quote> backend of <code>help</code> functionality " |
| "which provides a restricted implementation of path syncronization " |
| "to this specific area of documentation through the <option>--copy</" |
| "option>, <option>--delete</option> and <option>--rename</option> " |
| "options you can take as reference to implement it in other areas." |
| msgstr "" |
| |
| msgid "" |
| "The plan for a full implementation of path syncronization would be " |
| "to create individual restricted implementations like the one in " |
| "<quote>texinfo</quote> 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 will define 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." |
| msgstr "" |
| |
| msgid "Extending Repository Layout" |
| msgstr "" |
| |
| msgid "" |
| "Occasionly, you may find that new components of <ulink type=\"http" |
| "\" url=\"http://www.centos.org\">The CentOS Project</ulink> " |
| "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: <emphasis>What is the right place to store it?" |
| "</emphasis>" |
| msgstr "" |
| |
| msgid "" |
| "When the repository structure is extended, it is very useful to " |
| "bear in mind <ulink type=\"http\" url=\"http://www.centos.org\">The " |
| "CentOS Project</ulink> Corporate Visual Identity Structure, <ulink " |
| "url=\"http://mirrors.centos.org/\">The CentOS Mirrors</ulink> and " |
| "The CentOS Distribution Release Schema. The rest is a matter of " |
| "choosing appropriate names. It is also worth to know that each " |
| "directory in the repository responds to one or more concepts that " |
| "justify its existence." |
| msgstr "" |
| |
| msgid "" |
| "To build a directory structure inside the repository, you need to " |
| "define the concept behind it first and later create the directory, " |
| "remembering that there are locations inside the repository that " |
| "define concepts you probably would prefer to reuse. For example, " |
| "the <filename class=\"directory\">trunk/Identity/Images/Themes</" |
| "filename> directory stores artistic motifs of different themes, the " |
| "<filename class=\"directory\">trunk/Identity/Models/Themes</" |
| "filename> directory stores design models for themes, the <filename " |
| "class=\"directory\">trunk/Manuals</filename> directory stores " |
| "documentation, the <filename class=\"directory\">trunk/L10n</" |
| "filename> stores translation messages, and the <filename class=" |
| "\"directory\">trunk/Scripts</filename> stores automation scripts." |
| msgstr "" |
| |
| 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 <command>commit</command> command of Subversion's client " |
| "installed in your workstation." |
| msgstr "" |
| |
| msgid "" |
| "Initially, when you get registered inside <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>, you won't be able to publish your changes to " |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> immediatly. It is " |
| "necessary that you prove your interest in contributing first, " |
| "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." |
| 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." |
| 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 <ulink type=\"https\" url=\"https://projects.centos." |
| "org/svn/artwork\">The CentOS Artwork Repository</ulink> to " |
| "accomplish its mission." |
| msgstr "" |
| |
| msgid "Repository Authoring" |
| msgstr "" |
| |
| msgid "" |
| "The content produced inside <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> is copyright of <ulink type=\"https\" url=\"https://projects." |
| "centos.org/trac/artwork\">The CentOS Artwork SIG</ulink> and this " |
| "is something you, as author, need to be aware of because you are " |
| "giving part of your creation's rights to someone else; <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/trac/artwork\">The " |
| "CentOS Artwork SIG</ulink> for this matter. In this case, your work " |
| "is distributed using <ulink type=\"https\" url=\"https://projects." |
| "centos.org/trac/artwork\">The CentOS Artwork SIG</ulink> as " |
| "copyright holder not your name. Because <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/trac/artwork\">The CentOS Artwork " |
| "SIG</ulink> is the copyright holder, is the license chosen by " |
| "<ulink type=\"https\" url=\"https://projects.centos.org/trac/artwork" |
| "\">The CentOS Artwork SIG</ulink> the one applied to your work, so " |
| "it is the one you need to agree with before making a creation " |
| "inside <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink>." |
| msgstr "" |
| |
| msgid "Repository Copying Conditions" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/trac/artwork" |
| "\">The CentOS Artwork SIG</ulink> uses <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> to implement <ulink type=\"http\" url=\"http://" |
| "www.centos.org\">The CentOS Project</ulink> Corporate Visual " |
| "Identity. The implementation itself is controlled by the " |
| "<command>centos-art.sh</command> script." |
| msgstr "" |
| |
| msgid "" |
| "Both the <command>centos-art.sh</command> script and <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink>, 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 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 <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 " |
| "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 <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 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 <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 "Preparing Your Workstation" |
| msgstr "" |
| |
| msgid "Overview" |
| msgstr "" |
| |
| msgid "" |
| "The workstation is the machine you use to store your working copy " |
| "of <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink>. 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 <ulink type=\"https\" " |
| "url=\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> 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 <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> you lately 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 " |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> in all its extention." |
| msgstr "" |
| |
| msgid "Installing Your Workstation" |
| msgstr "" |
| |
| msgid "" |
| "In order to have a working copy of <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> in your workstation, the first step you need to " |
| "follow is pick up a computer and install an operating system in it. " |
| "This computer will be named the workstation from now on." |
| msgstr "" |
| |
| msgid "" |
| "At the moment of chosing which operating system to install in your " |
| "workstation, consider that <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> is completly built on The CentOS Distribution and realies on " |
| "it to achieve most automation tasks. At time of this writing the " |
| "major release 5 update 5 of The CentOS Distribution was used as " |
| "platform to support all work line development inside <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink>. To get the best of <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink>, it is necessary that you too, " |
| "use the same operating system we did to develop it." |
| msgstr "" |
| |
| msgid "" |
| "To install The CentOS Distribution you need to have access to the " |
| "installation media somehow (e.g., CDs, DVDs, Pendrives, etc.). If " |
| "you don't have the installation media of The CentOS Distribution, " |
| "you need to download the ISO files related to the installation " |
| "media you plan to use (e.g., CD or DVD) and then create the " |
| "installation media by yourself. The CentOS Distribution ISO files " |
| "can be downloaded from <ulink url=\"http://mirrors.centos.org/" |
| "\">The CentOS Mirrors</ulink>." |
| msgstr "" |
| |
| msgid "" |
| "Assuming you downloaded the DVD ISO of The CentOS Distribution, you " |
| "can burn it using the <application>K3B</application> application " |
| "and, this way, you are creating the installation media you are in " |
| "need of. Of course, in order to download the ISO files and create " |
| "the installation media, you need to have a workstation already " |
| "functionality where you can realized such tasks. If this is the " |
| "first time for you and see yourself into much troubles here, talk " |
| "to the guys in your nearest LUG, or simply send a mail to <ulink " |
| "type=\"http\" url=\"http://lists.centos.org/mailman/centos-info" |
| "\">The CentOS Mailing List</ulink> where you'll surely have the " |
| "answer you need." |
| msgstr "" |
| |
| msgid "" |
| "Once you have the installation media on your hands, the " |
| "installation process of The CentOS Distribution is rather " |
| "straightforward. To begin, you put the installation media in your " |
| "media reader, boot the computer from it, and follow the installer " |
| "intructions till it completes all the steps. That simple." |
| msgstr "" |
| |
| msgid "Partition Information" |
| msgstr "" |
| |
| msgid "" |
| "The partition information you set in your workstation is very " |
| "specific to your personal needs and the technical characteristics " |
| "of your machine. This information will also set the bases of all " |
| "deployment you reach to achieve inside the workstation. A well " |
| "partitioned workstation is crucial to garantee a well distribution " |
| "of space inside the worstation. In order to provide an idea of this " |
| "installation step, I'll describe the specific partitioning of the " |
| "machine I use to develop <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> right now. Remember that your needs might be differents and " |
| "so the partition layout you should implement." |
| msgstr "" |
| |
| msgid "" |
| "The machine of our example is isolated from Internet or any other " |
| "network. It has two hard drives of 256GB each, 2GB of RAM and a " |
| "2.80GHz Core 2 Duo processor. The main goal of this machine is " |
| "producing <ulink type=\"https\" url=\"https://projects.centos.org/" |
| "svn/artwork\">The CentOS Artwork Repository</ulink>. To represent " |
| "the real production environment of <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>, this machine was conceived to have two roles, " |
| "one as server —to store the source repository of <ulink type=\"https" |
| "\" url=\"https://projects.centos.org/svn/artwork\">The CentOS " |
| "Artwork Repository</ulink>— and one as client —to store a working " |
| "copy of the source repository—. From both hard drives available, " |
| "one is used as primary (<filename>/dev/sda</filename>) and the " |
| "other one as secondary (<filename>/dev/sdb</filename>) where the " |
| "secondary is used only to backup the information produced in the " |
| "primary by mean of backup scripts." |
| msgstr "" |
| |
| msgid "" |
| "The partition distribution of this machine implements the default " |
| "partinioning schema provided by The CentOS Distribution in the " |
| "primary hard drive to store partitions needed by the operating " |
| "system (e.g., <filename class=\"directory\">/</filename>, <filename " |
| "class=\"directory\">/boot</filename> and swap partition) where the " |
| "working copy is placed in. The second hard drive is an entire " |
| "partition mounted in <filename class=\"directory\">/mnt/backups</" |
| "filename> automatically on boot which only purpose is to duplicate " |
| "the information produced in the workplace." |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "Filesystem Type Size Mounted on\n" |
| "/dev/mapper/VolGroup00-LogVol00 ext3 239G /\n" |
| "/dev/sda1 ext3 104M /boot\n" |
| "tmpfs tmpfs 1.1G /dev/shm\n" |
| "/dev/sdb ext3 247G /mnt/backups\n" |
| msgstr "" |
| |
| msgid "" |
| "The detailed steps followed to prepare the partinioning layout " |
| "described above are described in the <citetitle>Deployment Guide</" |
| "citetitle> provided by <package>Deployment_Guide-en-US-5.2-11.el5." |
| "centos</package> package." |
| msgstr "" |
| |
| msgid "Packages Selection" |
| msgstr "" |
| |
| msgid "" |
| "The packages selection lets you to specify which software does your " |
| "workstation will have once it be installed. In this step, you need " |
| "to select the following groups of packages:" |
| msgstr "" |
| |
| msgid "Desktop Environments" |
| msgstr "" |
| |
| msgid "GNOME Desktop Environment" |
| msgstr "" |
| |
| msgid "KDE (K Desktop Environment)" |
| msgstr "" |
| |
| msgid "Applications" |
| msgstr "" |
| |
| msgid "Authoring and Publishing" |
| msgstr "" |
| |
| msgid "Editors" |
| msgstr "" |
| |
| msgid "Graphical Internet" |
| msgstr "" |
| |
| msgid "Graphics" |
| msgstr "" |
| |
| msgid "Office/Productivity" |
| msgstr "" |
| |
| msgid "Text-based Internet" |
| msgstr "" |
| |
| msgid "Development" |
| msgstr "" |
| |
| msgid "Development Libraries" |
| msgstr "" |
| |
| msgid "Development Tools" |
| msgstr "" |
| |
| msgid "GNOME Software Development" |
| msgstr "" |
| |
| msgid "KDE Software Development" |
| msgstr "" |
| |
| msgid "" |
| "Packages selected in this step provide a base selection of all the " |
| "packages you need in order to have a functional working copy of " |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink>. The only exception for " |
| "this, is the <package>inkscape</package> package and some of its " |
| "dependencies which doesn't come with The CentOS Distribution and " |
| "need to be installed from third party repositroies like EPEL and " |
| "RPMForge. The configuration of third party repository is done " |
| "later, once the workstation has been installed; just as described " |
| "in the <ulink url=\"http://wiki.centos.org/AdditionalResources/" |
| "Repositories\">Repositories</ulink> page." |
| msgstr "" |
| |
| msgid "Configuring Your Workstation" |
| msgstr "" |
| |
| msgid "" |
| "Once your worstation is installed, it is time for you to configure " |
| "it. At this point you create a user for everyday's work, configure " |
| "third party repositories, fix environment variables to fit your " |
| "personal needs, download the working copy of <ulink type=\"https\" " |
| "url=\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> and prepare it for start using it." |
| msgstr "" |
| |
| msgid "Workplace" |
| msgstr "" |
| |
| msgid "" |
| "Once you've installed the workstation and it is up and running, you " |
| "need to create the user name you'll use for your everyday's work. " |
| "In this task you need to use the commands <command>useradd</" |
| "command> and <command>passwd</command> 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 " |
| "<emphasis>root</emphasis> superuser for doing so." |
| msgstr "" |
| |
| msgid "" |
| "Do not use the <emphasis>root</emphasis> username for your " |
| "everyday's work inside your working copy of <ulink type=\"https\" " |
| "url=\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>. This is dangerous and might provoke " |
| "unreversable damages on your workstation." |
| msgstr "" |
| |
| msgid "" |
| "When user names are created inside the workstation, it doesn't " |
| "create only a user identifier for you to login, but a place for you " |
| "to store your information, as well. This place is known as your " |
| "home directory and is unique for each user inside the workstation. " |
| "At the moment, we face the following design problems related to " |
| "handling absolute paths inside the working copies of <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink>:" |
| msgstr "" |
| |
| msgid "Case 1: Different home directories" |
| msgstr "" |
| |
| msgid "" |
| "Assuming you store your working copy under <filename class=" |
| "\"directory\">/home/john/artwork/</filename> and I store mine under " |
| "<filename class=\"directory\">/home/al/artwork/</filename>, we'll " |
| "end up refering the same files inside our working copies through " |
| "different absolute paths. This generates a contradiction when " |
| "files, holding path information inside, are committed up to the " |
| "central repository. The contradiction comes from the question: " |
| "which is the correct absolute path to use inside such files, yours " |
| "or mine? — No one of them is, of course." |
| msgstr "" |
| |
| msgid "Case 2: One unique home directory" |
| msgstr "" |
| |
| msgid "" |
| "Another case would be that you and I ourselves use one unique home " |
| "directory (e.g., <filename class=\"directory\">/home/centos/artwork/" |
| "</filename>) to store the working copy of <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> 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 configuration " |
| "might be not so good for situations where you and I have to share " |
| "the same workstation. In such case, it would be required that we " |
| "both share the password information of the same system user (the " |
| "<emphasis>centos</emphasis> 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 "Case 3: Different home directories 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 fixed. The dynamic part is the " |
| "home directory of the current user and its value can be retrived " |
| "from the <envar>$HOME</envar> environment variable. The fixed part " |
| "of the path is the one we set inside the repositroy structure " |
| "itself as organization matter. What we need here is to find a way " |
| "to expand variables inside files that don't support variable " |
| "expansion. So far we've been doing this through creation template " |
| "instances which are temporal files with translation markers " |
| "expanded inside. This work rather fine with template files that are " |
| "one-time-pass (e.g., 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 "" |
| "From the three cases discussed above, the second one (i.e., One " |
| "unique home directory) seems to be the best candidate. It limits us " |
| "from using more than one working copy in the same workstation, but " |
| "gives us the chance of standardizing the use of absolute paths " |
| "inside all the working copies of <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>. Using absolute paths is very convenient because " |
| "it is possible to reuse information from different locations inside " |
| "the working copy, something that would be almost imposible to " |
| "maintain if relative paths were used instead. Thus, lets assume the " |
| "second case of handling home directories as default solution to " |
| "relatively solve the problem of where to store working copies of " |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> until a better one shows " |
| "itself up." |
| msgstr "" |
| |
| msgid "" |
| "The action of providing working copies of <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> that permit to reuse files inside them unifies " |
| "the way content is produced inside the working copy and provides a " |
| "convenction for people working on different areas to get attached " |
| "to in order to syncronize their works and still keep doing it " |
| "decentralized one another." |
| msgstr "" |
| |
| msgid "Environment Variables" |
| msgstr "" |
| |
| msgid "" |
| "Once you've created the <emphasis>centos</emphasis> user name for " |
| "your everyday's work and you had done login with it, there are some " |
| "environment variables that you can customize to fit your personal " |
| "needs (e.g., default text editor, default locale information, " |
| "default time zone representation, etc.). To customize these " |
| "variables you need to edit your personal profile (i.e., <filename " |
| "class=\"directory\">~/.bash_profile</filename>) and set the " |
| "redefinition there. Notice that you may need to logout and then do " |
| "login again in order for the new variable values to take effect." |
| msgstr "" |
| |
| msgid "Default text editor" |
| msgstr "" |
| |
| msgid "" |
| "The default text editor information is controlled by the " |
| "<envar>EDITOR</envar> environment variable. The <command>centos-art." |
| "sh</command> script uses the default text editor to edit subversion " |
| "pre-commit messages, translation files, documentation files, script " |
| "files, and similar text-based files." |
| msgstr "" |
| |
| msgid "" |
| "If <envar>EDITOR</envar> environment variable is not set, " |
| "<command>centos-art.sh</command> script uses <filename class=" |
| "\"directory\">/usr/bin/vim</filename> as default text editor. " |
| "Otherwise, the following values are recognized by <command>centos-" |
| "art.sh</command> script: <itemizedlist><listitem><para><filename " |
| "class=\"directory\">/usr/bin/vim</filename></para></" |
| "listitem><listitem><para><filename class=\"directory\">/usr/bin/" |
| "emacs</filename></para></listitem><listitem><para><filename class=" |
| "\"directory\">/usr/bin/nano</filename></para></listitem></" |
| "itemizedlist>" |
| msgstr "" |
| |
| msgid "" |
| "If no one of these values is set in the <envar>EDITOR</envar> " |
| "environment variable, the <command>centos-art.sh</command> script " |
| "uses <filename class=\"directory\">/usr/bin/vim</filename> text " |
| "editor, the one installed by default in The CentOS Distribution." |
| msgstr "" |
| |
| msgid "Default locale information" |
| msgstr "" |
| |
| msgid "" |
| "The default locale information is controlled by the <envar>LANG</" |
| "envar> environment variable. This variable is initially set in the " |
| "installation process of The CentOS Distribution, specifically in " |
| "the <emphasis>Language</emphasis> 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 <command>system-" |
| "config-language</command> command." |
| msgstr "" |
| |
| msgid "" |
| "The <command>centos-art.sh</command> script uses the <envar>LANG</" |
| "envar> 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 <ulink " |
| "type=\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink>." |
| msgstr "" |
| |
| msgid "Default time zone representation" |
| msgstr "" |
| |
| msgid "" |
| "The time zone representation is a time correction applied to the " |
| "system time (stored in the BIOS clock) based on your country " |
| "location. This correction is specially useful to distributed " |
| "computers around the world that work together and need to be " |
| "syncronized in time to know when things happened." |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> is made of one server and " |
| "several workstations spread around the world. In order for all " |
| "these workstations to know when changes in the server took place, " |
| "it is required that they all set their system clocks to use the " |
| "same time information (e.g., through UTC (Coordinated Universal " |
| "Time)) and set the time correction for their specific countries in " |
| "the operating system. Otherwise, it would be difficult to know when " |
| "something exactly happened." |
| msgstr "" |
| |
| msgid "" |
| "Generally, setting the time information is a straight-forward task " |
| "and configuration tools provided by The CentOS Distribution do " |
| "cover time correction for most of the countries around the world. " |
| "However, if you need a time precision not provided by any of the " |
| "date and time configuration tools provided by The CentOS " |
| "Distribution then, you need to customize the <envar>TZ</envar> " |
| "environment variable in your personal profile to correct the time " |
| "information by yourself. The format of <envar>TZ</envar> " |
| "environment variable is described in <code>tzset(3)</code> manual " |
| "page." |
| msgstr "" |
| |
| msgid "Administrative Tasks" |
| msgstr "" |
| |
| msgid "" |
| "Sometimes it is necessary that you perform administrative tasks " |
| "inside the workstation the working copy of <ulink type=\"https\" " |
| "url=\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> is stored in. These tasks might demand you to " |
| "type many commands (e.g., for configuring a third party repository) " |
| "or just a one-line command (e.g., for installing a new package). In " |
| "both cases this kind of tasks require permissions that your user " |
| "for everyday's work must not have under no mean." |
| msgstr "" |
| |
| msgid "" |
| "To perform administrative tasks in your workstation, you need to " |
| "login as <emphasis>root</emphasis> or configure the <command>sudo</" |
| "command> program to temporarily granting the permissions your " |
| "regular user needs to perform the administrative tasks. The " |
| "configuration of <command>sudo</command> program is at <filename>/" |
| "etc/sudoers</filename> file and you need to add the " |
| "<emphasis>centos</emphasis> user to the list of privileged user as " |
| "described in the section below:" |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "## Next comes the main part: which users can run what software on \n" |
| "## which machines (the sudoers file can be shared between multiple\n" |
| "## systems).\n" |
| "## Syntax:\n" |
| "##\n" |
| "## user MACHINE=COMMANDS\n" |
| "##\n" |
| "## The COMMANDS section may have other options added to it.\n" |
| "##\n" |
| "## Allow root to run any commands anywhere \n" |
| "root ALL=(ALL) ALL\n" |
| "centos ALL=(ALL) ALL\n" |
| msgstr "" |
| |
| msgid "" |
| "This configuration is required in order for automation scripts to " |
| "realize administrative tasks that otherwise you would need to type " |
| "one by one. It is worth to mention that all these tasks are " |
| "organized in the <function>prepare</function> functionality of the " |
| "<command>centos-art.sh</command> script in the sake of reducing " |
| "work and standardize the procedure of performing them. It is also " |
| "worth to mention that, the <command>centos-art.sh</command> script " |
| "is available for you to run, study, improve and share your changes " |
| "as described in <xref linkend=\"licenses-gpl\"/>." |
| msgstr "" |
| |
| msgid "Working Copy" |
| msgstr "" |
| |
| msgid "" |
| "Once you've installed and configured the workstation, it is ready " |
| "to receive the working copy of <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink>. In this step, you use Subversion's client to communicate " |
| "the source repository of <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> and download all the files that make a working copy of it." |
| msgstr "" |
| |
| msgid "" |
| "To download the working copy of <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> you need to login as your everyday's work user (i.e., the " |
| "<emphasis>centos</emphasis> user) and use the Subversion client " |
| "installed in your workstation to bring all the files you need to " |
| "work with from the source repository down to your workstation, just " |
| "as the following command describes:" |
| msgstr "" |
| |
| |
| msgid "svn co https://projects.centos.org/svn/artwork ~/" |
| msgstr "" |
| |
| msgid "" |
| "This command will create your working copy of <ulink type=\"https\" " |
| "url=\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> in your workstation, specifically in the " |
| "<filename class=\"directory\">/home/centos/artwork</filename> " |
| "directory." |
| msgstr "" |
| |
| msgid "" |
| "If the Subversion's client wasn't installed by default, you need to " |
| "install it using the following command:" |
| msgstr "" |
| |
| |
| msgid "sudo yum install subversion" |
| msgstr "" |
| |
| msgid "" |
| "Once your working copy of <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> has been downloaded, you should notice that there is 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 the action of render them to produce the final files " |
| "(e.g., images and documentation) we use to implement <ulink type=" |
| "\"http\" url=\"http://www.centos.org\">The CentOS Project</ulink> " |
| "Corporate Visual Identity." |
| msgstr "" |
| |
| msgid "" |
| "Another consideration to be aware of at this point, is the need of " |
| "verifying the software installed in the workstation, as well as the " |
| "creation of symbolic links to connect the content produced inside " |
| "the working copy to applications outside it (e.g., to make " |
| "available patterns, brushes, and palettes produced inside the " |
| "working copy in GIMP, the application used to manipulate images)." |
| msgstr "" |
| |
| msgid "" |
| "These final preparation stuff is automated by the " |
| "<function>prepare</function> functionality of the <command>centos-" |
| "art.sh</command> script, as described in <xref linkend=\"scripts-" |
| "bash-prepare\"/>. Execute it right now, to be sure your workstation " |
| "and your working copy are both ready to be used." |
| msgstr "" |
| |
| msgid "Repository History" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> started at <ulink url=" |
| "\"mailto:centos-devel@centos.org\">The CentOS Developers Mailing " |
| "List</ulink> around 2008, on a discussion about how to automate " |
| "slide images used by Anaconda. 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, <ulink " |
| "type=\"https\" url=\"https://projects.centos.org/trac/artwork\">The " |
| "CentOS Artwork SIG</ulink> and <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> were officially created and world wide available." |
| msgstr "" |
| |
| msgid "" |
| "Once <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink> was available, " |
| "Alain Reguera Delgado uploaded the bash script Anaconda slides; " |
| "Ralph Angenendt documented it very well; and people started to " |
| "download working copies of the 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 " |
| "<ulink url=\"http://en.wikipedia.org/Corporate_identity" |
| "\">Wikipedia</ulink> related links. This way, the rendition script " |
| "main's goal becomes to: <emphasis>automate the production process " |
| "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 <citetitle><ulink type=\"https" |
| "\" url=\"https://projects.centos.org/svn/artwork\">The CentOS " |
| "Artwork Repository</ulink> User's Guide</citetitle> was 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 <envar>PATH</envar> 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 Web." |
| 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 <function>render</function>, <function>help</function> and " |
| "<function>locale</function> 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 " |
| "<function>render</function> and locale functionalities. The " |
| "<function>render</function> functionality uses the xsltproc command-" |
| "line <acronym>XSLT</acronym> 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 (<acronym>PO</" |
| "acronym>) the <function>render</function> 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 <function>render</function> and " |
| "<function>locale</function> even more. In this configuration, once " |
| "the DocBook files are written, you use <function>locale</function> " |
| "functionality to localize the DocBook files in your prefered " |
| "language and later, using <function>render</function> " |
| "functionality, you produce the XTHML and PDF outputs as specified " |
| "in a XSLT or DSL customization layer." |
| msgstr "" |
| |
| msgid "The CentOS Project" |
| msgstr "" |
| |
| msgid "" |
| "The CentOS Project Corporate Identity is the <quote>persona</quote> " |
| "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." |
| msgstr "" |
| |
| msgid "The CentOS Project Corporate Identity." |
| msgstr "" |
| |
| msgid "Corporate Mission" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> 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." |
| 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 <ulink type=" |
| "\"http\" url=\"http://wiki.centos.org/\">Wiki</ulink>, <ulink type=" |
| "\"http\" url=\"http://www.centos.org/modules/tinycontent/index.php?" |
| "id=8\">IRC Chat</ulink>, <ulink type=\"http\" url=\"http://lists." |
| "centos.org/\">Email Lists</ulink>, <ulink type=\"http\" url=" |
| "\"http://www.centos.org/modules/newbb/\">Forums</ulink>, and a " |
| "dynamic <ulink type=\"http\" url=\"http://www.centos.org/modules/" |
| "smartfaq/\">FAQ</ulink>." |
| msgstr "" |
| |
| msgid "Corporate 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 " |
| "<emphasis>all</emphasis> 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." |
| msgstr "" |
| |
| msgid "" |
| "In the very specific case of <ulink type=\"http\" url=\"http://www." |
| "centos.org\">The CentOS Project</ulink>, we'll concentrate our " |
| "attention on corporate messages that reach us through the visual " |
| "sense. This is, all the visual manifestations <ulink type=\"http\" " |
| "url=\"http://www.centos.org\">The CentOS Project</ulink> is made " |
| "of. As visual manifestaions we understand all the visible media " |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> uses to manifest its existence on. At this point it " |
| "is necessary to consider what <ulink type=\"http\" url=\"http://www." |
| "centos.org\">The CentOS Project</ulink> 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 <ulink type=\"http\" url=\"http://www.centos.org\">The " |
| "CentOS Project</ulink> we identify and apply corporate design to " |
| "the following visual manifestations: <orderedlist numeration=" |
| "\"arabic\"><listitem><para> 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 <xref linkend=\"identity-distro" |
| "\"/>. </para></listitem><listitem><para> The CentOS Web — This " |
| "visual manifestation exists to cover all actions related to artwork " |
| "production required by <ulink type=\"http\" url=\"http://www.centos." |
| "org\">The CentOS Project</ulink> to manifest its existence in the " |
| "World Wide Web medium. This visual manifestation is described in " |
| "<xref linkend=\"identity-web\"/>. </para></" |
| "listitem><listitem><para> The CentOS Showroom — This visual " |
| "manifestation exists to cover all actions related to artwork " |
| "production required by <ulink type=\"http\" url=\"http://www.centos." |
| "org\">The CentOS Project</ulink> to manifest its existence through " |
| "media produced industrially (e.g., stationery, clothes, CDs, DVDs, " |
| "etc.). This visual manifestation is described in <xref linkend=" |
| "\"identity-showroom\"/>. </para></listitem></orderedlist>" |
| msgstr "" |
| |
| msgid "" |
| "The visual manifestations identified above seem to cover most media " |
| "required by <ulink type=\"http\" url=\"http://www.centos.org\">The " |
| "CentOS Project</ulink>, 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 <ulink type=\"http\" url=\"http://www.centos.org" |
| "\">The CentOS Project</ulink> 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 <ulink type=\"http\" url=\"http://www.centos.org" |
| "\">The CentOS Project</ulink>. 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 "" |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> 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 "" |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> corporate communication takes place through the " |
| "following visual manifestations: " |
| "<variablelist><varlistentry><term>The CentOS Distribution</" |
| "term><listitem><para> 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 <ulink type=\"http\" url=" |
| "\"http://www.centos.org\">The CentOS Project</ulink> images " |
| "required by software packages that do use images in a remarkable " |
| "way, specially those holding the upstream brand (e.g., " |
| "<package>anaconda</package>, <package>grub</package>, " |
| "<package>syslinux</package>, <package>gdm</package>, " |
| "<package>kdebase</package>). </para><itemizedlist><listitem><para> " |
| "The Community Enterprise Operating System itself (communicates the " |
| "essense of <ulink type=\"http\" url=\"http://www.centos.org\">The " |
| "CentOS Project</ulink> existence.). </para></" |
| "listitem><listitem><para> Release Schema (Lifetime) and all the " |
| "stuff related (e.g., Release Notes, Documentation, Erratas, etc.). " |
| "</para></listitem></itemizedlist></listitem></" |
| "varlistentry><varlistentry><term>The CentOS Web</" |
| "term><listitem><para> 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. </para><itemizedlist><listitem><para> The " |
| "CentOS Chat. </para></listitem><listitem><para> The CentOS Mailing " |
| "Lists. </para></listitem><listitem><para> The CentOS Forums. </" |
| "para></listitem><listitem><para> The CentOS Wiki. </para></" |
| "listitem><listitem><para> Special Interest Groups (SIGs). </para></" |
| "listitem><listitem><para> Social Events, Interviews, Conferences, " |
| "etc. </para></listitem><listitem><para> The extensive network of " |
| "mirrors available for downloading ISO files as well as RPMs and " |
| "SRPMs used to build them up in different architectures. </para></" |
| "listitem></itemizedlist></listitem></" |
| "varlistentry><varlistentry><term>The CentOS Showroom</" |
| "term><listitem><para> 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 <ulink type=\"http\" url=" |
| "\"http://www.centos.org\">The CentOS Project</ulink> expenses (e." |
| "g., electrical power, hosting, servers, full-time-developers, " |
| "etc.), in a similar way as donations may do. </" |
| "para><itemizedlist><listitem><para> Stationery (e.g., Posters, " |
| "Stickers, CD Lables and Sleeves). </para></" |
| "listitem><listitem><para> Clothes (e.g., Shirts, T-shirts, " |
| "Pullovers, Caps). </para></listitem><listitem><para> Installation " |
| "media (e.g., CDs, DVD, Pendrives). </para></listitem></" |
| "itemizedlist></listitem></varlistentry></variablelist>" |
| msgstr "" |
| |
| msgid "Corporate Behaviour" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> 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 "" |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> corporate behaviour takes place through <ulink type=" |
| "\"http\" url=\"http://www.centos.org\">The CentOS Project</ulink> " |
| "corporate communication, as described in <xref linkend=\"identity-" |
| "project-communication\"/>." |
| msgstr "" |
| |
| msgid "Corporate Structure" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> 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 <ulink type=\"http\" url=\"http://www.centos.org" |
| "\">The CentOS Project</ulink> 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 <ulink type=\"http" |
| "\" url=\"http://www.centos.org\">The CentOS Project</ulink>." |
| msgstr "" |
| |
| msgid "" |
| "Other corporate structures for <ulink type=\"http\" url=\"http://" |
| "www.centos.org\">The CentOS Project</ulink> 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 <ulink type=\"http" |
| "\" url=\"http://www.centos.org\">The CentOS Project</ulink> is made " |
| "of." |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink>, 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, <ulink type=\"http\" url=\"http://www.centos." |
| "org\">The CentOS Project</ulink> 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 <ulink type=\"http" |
| "\" url=\"http://www.centos.org\">The CentOS Project</ulink> in " |
| "general." |
| msgstr "" |
| |
| msgid "" |
| "In order to produce the <ulink type=\"http\" url=\"http://www." |
| "centos.org\">The CentOS Project</ulink> Monolithic Corporate Visual " |
| "Identity Structure correctly, we need to concider all the visual " |
| "manifestations <ulink type=\"http\" url=\"http://www.centos.org" |
| "\">The CentOS Project</ulink> 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 <ulink " |
| "type=\"http\" url=\"http://www.centos.org\">The CentOS Project</" |
| "ulink> is made of (e.g., The CentOS Web and The CentOS Showroom)?" |
| 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?" |
| msgstr "" |
| |
| msgid "" |
| "Harder to maintain, more work to do, probably. Specially when you " |
| "consider that <ulink type=\"http\" url=\"http://www.centos.org" |
| "\">The CentOS Project</ulink> 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 <ulink type=\"http\" url=\"http://www.centos.org\">The " |
| "CentOS Project</ulink> 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 " |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> visual manifestations would be very good in favor " |
| "of <ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> 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 <ulink type=" |
| "\"http\" url=\"http://www.centos.org\">The CentOS Project</ulink> " |
| "is made of, in a way <ulink type=\"http\" url=\"http://www.centos." |
| "org\">The CentOS Project</ulink> 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 <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>." |
| msgstr "" |
| |
| msgid "The CentOS Brand" |
| msgstr "" |
| |
| msgid "" |
| "The CentOS Brands is the main visual manifestaion of The CentOS " |
| "Project. The CentOS Project uses The CentOS Logo 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 Logo or any visual " |
| "manifestation derived from it, write your intentions to the The " |
| "CentOS Developers mailing list (<ulink url=\"mailto:centos-" |
| "devel@centos.org\">centos-devel@centos.org</ulink>)." |
| msgstr "" |
| |
| msgid "The CentOS Distribution" |
| msgstr "" |
| |
| msgid "Release Schema" |
| msgstr "" |
| |
| msgid "The CentOS Web" |
| msgstr "" |
| |
| msgid "The CentOS Showroom" |
| msgstr "" |
| |
| msgid "" |
| "This part describes the repository's documentation work line. Here " |
| "you'll find how documentation backends inside The CentOS " |
| "Distribution are used to produce documentation manuals inside The " |
| "CentOS Artwork Repository." |
| msgstr "" |
| |
| msgid "Texinfo Backend" |
| msgstr "" |
| |
| msgid "" |
| "Documentation manuals that use <application>Texinfo</application> " |
| "as documentation backend are conceived 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. They provides a documentation entry for " |
| "each directory inside the repository and, this way, a place to " |
| "document it." |
| msgstr "" |
| |
| msgid "" |
| "Most actions related to Texinfo documentation backend (e.g., " |
| "editing, reading, copying, renaming, etc.) are controlled by the " |
| "<function>help</function> functionality as described in <xref " |
| "linkend=\"scripts-bash-help\"/>. Through this functionality you can " |
| "manipulate documentation entries in a way that you don't need to " |
| "take care of updating menus, nodes and cross reference information " |
| "inside the manual source files because the functionality takes care " |
| "of it for you. However, if you need to write repository " |
| "documentation that have nothing to do with repository directories " |
| "(e.g., Preface, Introduction and similar) you need to do it by your " |
| "own, there is no functionality to help you doing such things, yet." |
| msgstr "" |
| |
| msgid "" |
| "The Texinfo documentation backend could result useful to you if " |
| "your only need is to document directory structures in a manual that " |
| "follows, exactly, the same organization of the structure it " |
| "documents (e.g., one directory one documentation entry for it)." |
| msgstr "" |
| |
| msgid "Document Structure" |
| msgstr "" |
| |
| msgid "" |
| "The document structure provides the organization needed to make the " |
| "documentation scalable and maintainable through time which, in " |
| "turn, involves document sectioning and file organization inside " |
| "specific locations of the working copy. The document structure is " |
| "also a convenction we adopt in order to automate frequent tasks " |
| "related to the document structure itself. Without a well defined " |
| "document structure convenction, it would be very difficult for " |
| "automation script to guess where the documentation files are." |
| msgstr "" |
| |
| msgid "" |
| "The file organization of Texinfo documentation backend takes place " |
| "in <filename class=\"directory\">trunk/Manuals/Repository/Texinfo/</" |
| "filename> directory. Inside this location there is one " |
| "documentation structure for each language you want to support and " |
| "the <filename>repository-init.pl</filename> and " |
| "<filename>repository.sed</filename> files which let you control " |
| "common characteristics of final XHTML output (e.g., " |
| "<command>texi2html</command> initialization, and markup " |
| "transformations)." |
| msgstr "" |
| |
| msgid "" |
| "The document sectioning follows the idea of an upside-down tree to " |
| "organize chapters, sections, subsections, and the like. The " |
| "document initiates with a Top node where we placed document's " |
| "title, copyright note, abstract, and a list of available chapters " |
| "to start browsing. Inside each chapter the information is logically " |
| "organized in sections which in turn are subdivided in subsections " |
| "and subsubsections." |
| msgstr "" |
| |
| msgid "" |
| "The Texinfo document structure produced by <function>help</" |
| "function> functionality organizes information in two chapters only, " |
| "which are: <orderedlist><listitem><para> Directories — This chapter " |
| "organizes documentation entries related to repository directories. " |
| "In the normal work flow, you don't need to touch the files of this " |
| "chapter by your own. For that purpose, the <command>centos-art.sh</" |
| "command> script porovides the <function>help</function> " |
| "functionality. To manipulate documentation entries in this chapter, " |
| "you use the <function>help</function> functionality as described in " |
| "<xref linkend=\"scripts-bash-help\"/>. </para></" |
| "listitem><listitem><para> Licenses — This chapter includes licenses " |
| "from <filename class=\"directory\">trunk/Scripts/Functions/Help/" |
| "Texinfo/Templates/<replaceable>language</replaceable>/Licenses/</" |
| "filename> directory. In the normal work flow, you don't need to " |
| "touch this chapter. It is created when the document structure is " |
| "created and should ramain that way. If you need to improve the " |
| "markup, update the template files for your language, not the " |
| "content of this chapter. </para></listitem></orderedlist>" |
| msgstr "" |
| |
| msgid "" |
| "At the same level of chapter directories, the <filename>repository." |
| "texinfo</filename>, <filename>repository-index.texinfo</filename>, " |
| "<filename>repository-menu.texinfo</filename> and " |
| "<filename>repository-nodes.texinfo</filename> files exist to set " |
| "manual's main definitions (e.g., title, copyright notice, chapters, " |
| "appendixes, indexes and all the similar stuff a documentation " |
| "manual should have)." |
| msgstr "" |
| |
| msgid "" |
| "Inside each chapter directory, the <filename>chapter.texinfo</" |
| "filename>, <filename>chapter-menu.texinfo</filename> and " |
| "<filename>chapter-nodes.texinfo</filename> files exist to control " |
| "definition of sections. In addition to these files, there are " |
| "documentation entries to store the document's content itself, using " |
| "arbitrary file names prefixed with the <filename class=\"extension" |
| "\">texinfo</filename> extension, just as it is illustrated in <xref " |
| "linkend=\"doc-texinfo-structure-eg1\"/>." |
| msgstr "" |
| |
| msgid "Texinfo backend's document structure." |
| msgstr "" |
| |
| |
| msgid "" |
| "trunk/Manuals/Repository/Texinfo\n" |
| "|-- en_US\n" |
| "| |-- Directories\n" |
| "| | |-- chapter-menu.texinfo\n" |
| "| | |-- chapter-nodes.texinfo\n" |
| "| | |-- chapter.texinfo\n" |
| "| | |-- trunk/Identity.texinfo\n" |
| "| | `-- trunk.texinfo\n" |
| "| |-- Licenses\n" |
| "| | |-- chapter-menu.texinfo\n" |
| "| | |-- chapter-nodes.texinfo\n" |
| "| | `-- chapter.texinfo\n" |
| "| |-- repository-index.texinfo\n" |
| "| |-- repository-menu.texinfo\n" |
| "| |-- repository-nodes.texinfo\n" |
| "| `-- repository.texinfo\n" |
| "|-- repository-init.pl\n" |
| "|-- repository.css\n" |
| "`-- repository.sed" |
| msgstr "" |
| |
| msgid "Document Templates" |
| msgstr "" |
| |
| msgid "Document Localization" |
| msgstr "" |
| |
| msgid "Document Encoding" |
| msgstr "" |
| |
| msgid "DocBook Backend" |
| msgstr "" |
| |
| msgid "The <command>centos-art.sh</command> script" |
| msgstr "" |
| |
| msgid "The script design" |
| msgstr "" |
| |
| msgid "The <function>render</function> functionality" |
| msgstr "" |
| |
| msgid "The <function>locale</function> functionality" |
| msgstr "" |
| |
| msgid "The <function>help</function> functionality" |
| msgstr "" |
| |
| msgid "" |
| "The <function>help</function> functionality is the interface the " |
| "<command>centos-art.sh</command> script provides to control " |
| "frequent documentation tasks (e.g., reading, editing, update output " |
| "files, etc.) requied by specific documentation backends. " |
| "Documentation backends supported by <function>help</function> " |
| "functionality are described in <xref linkend=\"doc\"/>." |
| msgstr "" |
| |
| msgid "Synopsis" |
| msgstr "" |
| |
| |
| msgid "centos-art help [OPTIONS] path/to/dir ..." |
| msgstr "" |
| |
| msgid "" |
| "The <parameter>path/to/dir</parameter> parameter specifies the " |
| "directory structure inside the working copy of The CentOS Artwork " |
| "Repository you want to process the related documentation entry for. " |
| "More than one directory structure can be passed as <parameter>path/" |
| "to/dir</parameter> parameter." |
| msgstr "" |
| |
| msgid "" |
| "The <function>help</function> functionality accepts the following " |
| "options:" |
| msgstr "" |
| |
| msgid "--quiet" |
| msgstr "" |
| |
| msgid "" |
| "Supress all output messages except error messages. When this option " |
| "is passed, all confirmation requests are supressed as well and a " |
| "possitive answer is assumed for them, just as if the <option>--" |
| "answer-yes</option> option had been provided." |
| msgstr "" |
| |
| msgid "--answer-yes" |
| msgstr "" |
| |
| msgid "Assume <emphasis>yes</emphasis> to all confirmation requests." |
| msgstr "" |
| |
| msgid "--dont-commit-changes" |
| 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 "--backend=\"STRING\"" |
| msgstr "" |
| |
| msgid "" |
| "Specify <replaceable>STRING</replaceable> as default documentation " |
| "backend to use. Possible arguments to this options are: " |
| "<literal>texinfo</literal> or <literal>docbook</literal>. If this " |
| "option is not provided, <literal>texinfo</literal> is used as " |
| "default documentation backend." |
| msgstr "" |
| |
| msgid "--search=\"STRING\"" |
| msgstr "" |
| |
| msgid "Go to node pointed by index entry <literal>STRING</literal>." |
| msgstr "" |
| |
| msgid "--edit" |
| msgstr "" |
| |
| msgid "" |
| "Edit documentation entry related to path specified by " |
| "<parameter>path/to/dir</parameter> parameter." |
| msgstr "" |
| |
| msgid "" |
| "The <parameter>path/to/dir</parameter> parameter must point to any " |
| "directory inside the repository. When more than one <parameter>path/" |
| "to/dir</parameter> are passed as non-option arguments to the " |
| "<command>centos-art.sh</command> 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 " |
| "<envar>EDITOR</envar> 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 <parameter>path/to/dir</" |
| "parameter> path. This option is used internally by <command>centos-" |
| "art.sh</command> script to print out the reference you can follow " |
| "to know more about an error message." |
| msgstr "" |
| |
| msgid "--update" |
| 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 of the " |
| "repository." |
| 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" |
| msgstr "" |
| |
| msgid "" |
| "Delete documentation entries specified by <parameter>path/to/dir</" |
| "parameter> inside the working copy. It is possible to delete more " |
| "than one documentation entry by specifying more <parameter>path/to/" |
| "dir</parameter> 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 <option>--" |
| "delete</option> or <option>--rename</option> options), the " |
| "<function>help</function> functionality takes care of updating " |
| "nodes, menus and cross references related to documentation entries " |
| "in order to keep the manual structure in a correct state." |
| msgstr "" |
| |
| msgid "Examples" |
| msgstr "" |
| |
| |
| msgid "centos-art help --edit trunk/Identity" |
| msgstr "" |
| |
| msgid "" |
| "This command edits the documentation entry related to <filename " |
| "class=\"directory\">trunk/Identity</filename> directory inside the " |
| "repository working copy." |
| msgstr "" |
| |
| |
| msgid "centos-art help --read trunk/Identity" |
| msgstr "" |
| |
| msgid "" |
| "This command reads the documentation entry related to <filename " |
| "class=\"directory\">trunk/Identity</filename> directory inside the " |
| "repository working copy." |
| msgstr "" |
| |
| msgid "Author" |
| msgstr "" |
| |
| msgid "Written by Alain Reguera Delgado." |
| msgstr "" |
| |
| msgid "Reporting Bugs" |
| msgstr "" |
| |
| msgid "" |
| "Report bugs to <ulink type=\"http\" url=\"http://lists.centos.org/" |
| "mailman/centos-artwork\">The CentOS Artwork Mailing List</ulink>." |
| msgstr "" |
| |
| msgid "Copyright" |
| msgstr "" |
| |
| msgid "" |
| "Copyright © 2009, 2010, 2011 <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/trac/artwork\">The CentOS Artwork SIG</ulink>." |
| msgstr "" |
| |
| msgid "" |
| "This is free software. You may redistribute copies of it under the " |
| "terms of the <xref linkend=\"licenses-gpl\"/>. There is NO " |
| "WARRANTY, to the extent permitted by law." |
| msgstr "" |
| |
| msgid "The <function>prepare</function> functionality" |
| msgstr "" |
| |
| msgid "" |
| "The <function>prepare</function> functionality is the interface the " |
| "<command>centos-art.sh</command> script provides to standardize the " |
| "final configuration stuff your workstation needs, once the working " |
| "copy of <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink> has been downloaded " |
| "inside it already." |
| msgstr "" |
| |
| msgid "" |
| "Assuming this is the very first time you run the <command>centos-" |
| "art.sh</command> script, you'll find that it isn't found in your " |
| "workstation. This is correct because you haven't create the command-" |
| "line interface symbolic link that make it available in the " |
| "execution path. In order to make the <command>centos-art.sh</" |
| "command> command-line available in the execution path of your " |
| "workstation, you need to run it using its absolute path first:" |
| msgstr "" |
| |
| |
| msgid "~/artwork/trunk/Scripts/centos-art.sh prepare [OPTIONS]" |
| msgstr "" |
| |
| msgid "" |
| "Later, once the <command>centos-art.sh</command> script is " |
| "available in the execution path of your system, there is no need " |
| "for you to use the absolute path again. From this time on, you can " |
| "use the <command>centos-art</command> command-line interface " |
| "directly, as the following example describes:" |
| msgstr "" |
| |
| |
| msgid "centos-art prepare [OPTIONS]" |
| msgstr "" |
| |
| msgid "" |
| "The <function>prepare</function> functionality accepts the " |
| "following options:" |
| 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 <option>--answer-yes</" |
| "option> option had been provided." |
| msgstr "" |
| |
| msgid "--packages" |
| msgstr "" |
| |
| msgid "" |
| "This option verifies whether required packages need to be installed " |
| "or updated. In both cases, the <command>sudo yum</command> command " |
| "is used to perform such tasks. This configuration requires you to " |
| "configure the <command>sudo</command> command first, as described " |
| "in <xref linkend=\"repo-ws-config-sudo\"/>." |
| msgstr "" |
| |
| msgid "--links" |
| msgstr "" |
| |
| msgid "" |
| "This option creates/updates the symbolic links information required " |
| "in your workstation to connect it with the files inside the working " |
| "copy of <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink>. When you provide " |
| "this option, the <command>centos-art.sh</command> put itself into " |
| "your system's execution path and make common brushes, patterns, " |
| "palettes and fonts available inside applications like GIMP, so you " |
| "can make use of them without loosing version control over them." |
| msgstr "" |
| |
| msgid "" |
| "This option removes all common fonts, brushes, patterns, and " |
| "palettes from your home configuration directories, in order to " |
| "create a fresh installation of them all, again, using the working " |
| "copy as reference." |
| msgstr "" |
| |
| msgid "--images" |
| msgstr "" |
| |
| msgid "" |
| "This option initializes image files inside the working copy. When " |
| "you provide this option, the <command>centos-art.sh</command> " |
| "scripts renders image files from all design models available in the " |
| "working copy. This step is required in order to satisfy " |
| "dependencies from different components inside the working copy." |
| msgstr "" |
| |
| msgid "--manuals" |
| msgstr "" |
| |
| msgid "" |
| "This option initializes documentation files inside the working " |
| "copy. When you provide this option, the <command>centos-art.sh</" |
| "command> script renders all documentation manuals from their " |
| "related source files so you can read them nicely." |
| msgstr "" |
| |
| msgid "--environment" |
| msgstr "" |
| |
| msgid "" |
| "Print the name and value of some of the environment variables used " |
| "by <command>centos-art.sh</command> scripts." |
| msgstr "" |
| |
| msgid "" |
| "As default behaviour, when no option is provided to " |
| "<function>prepare</function> functionality, the <command>centos-art." |
| "sh</command> script excecutes as is it had been executed with the " |
| "<option>--packages</option>, <option>--links</option>, <option>--" |
| "images</option> and <option>--manuals</option> options. Otherwise, " |
| "if you provide any option, the <command>centos-art.sh</command> " |
| "script executes the <function>prepare</function> functionality as " |
| "specified by the options." |
| msgstr "" |
| |
| msgid "" |
| "Notice that is possible for you to execute the <function>prepare</" |
| "function> functionality as much times as you need to. This is " |
| "specially useful when you need to keep syncronized the relation " |
| "between content produced inside your working copy and the " |
| "applications you use outside it. For example, considering you've " |
| "added new brushes to or removed old brushes from your working copy " |
| "of <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink>, the link " |
| "information related to those files need to be updated in the " |
| "<filename class=\"directory\">~/.gimp-2.2/brushes</filename> " |
| "directory too, in a way the addition/deletion change that took " |
| "place in your working copy can be reflected there, as well. The " |
| "same is true for other similar components like fonts, patterns and " |
| "palettes." |
| msgstr "" |
| |
| msgid "" |
| "The examples here seem to be pretty obvious once you've read both " |
| "the synopsis section and the options supported by this " |
| "functionality. Isn't it?" |
| msgstr "" |
| |
| msgid "The <function>tuneup</function> functionality" |
| msgstr "" |
| |
| msgid "Licenses" |
| msgstr "" |
| |
| msgid "GNU General Public License" |
| msgstr "" |
| |
| msgid "Version 2, June 1991" |
| msgstr "" |
| |
| msgid "" |
| "Copyright © 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, " |
| "Cambridge, MA 02139, USA" |
| 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 licenses for most software are designed to take away your " |
| "freedom to share and change it. By contrast, the GNU General Public " |
| "License is intended to guarantee your freedom to share and change " |
| "free software–to make sure the software is free for all its users. " |
| "This General Public License applies to most of the Free Software " |
| "Foundation's software and to any other program whose authors commit " |
| "to using it. (Some other Free Software Foundation software is " |
| "covered by the GNU Library General Public License instead.) You can " |
| "apply it to your programs, too." |
| msgstr "" |
| |
| msgid "" |
| "When we speak of free software, we are referring to freedom, not " |
| "price. Our General Public Licenses are designed to make sure that " |
| "you have the freedom to distribute copies of free software (and " |
| "charge for this service if you wish), that you receive source code " |
| "or can get it if you want it, that you can change the software or " |
| "use pieces of it in new free programs; and that you know you can do " |
| "these things." |
| msgstr "" |
| |
| msgid "" |
| "To protect your rights, we need to make restrictions that forbid " |
| "anyone to deny you these rights or to ask you to surrender the " |
| "rights. These restrictions translate to certain responsibilities " |
| "for you if you distribute copies of the software, or if you modify " |
| "it." |
| msgstr "" |
| |
| msgid "" |
| "For example, if you distribute copies of such a program, whether " |
| "gratis or for a fee, 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 show them these terms so they " |
| "know their rights." |
| msgstr "" |
| |
| msgid "" |
| "We protect your rights with two steps: <orderedlist numeration=" |
| "\"arabic\"><listitem><para>copyright the software, and</para></" |
| "listitem><listitem><para>offer you this license which gives you " |
| "legal permission to copy, distribute and/or modify the software.</" |
| "para></listitem></orderedlist>" |
| msgstr "" |
| |
| msgid "" |
| "Also, for each author's protection and ours, we want to make " |
| "certain that everyone understands that there is no warranty for " |
| "this free software. If the software is modified by someone else and " |
| "passed on, we want its recipients to know that what they have is " |
| "not the original, so that any problems introduced by others will " |
| "not reflect on the original authors' reputations." |
| msgstr "" |
| |
| msgid "" |
| "Finally, any free program is threatened constantly by software " |
| "patents. We wish to avoid the danger that redistributors of a free " |
| "program will individually obtain patent licenses, in effect making " |
| "the program proprietary. To prevent this, we have made it clear " |
| "that any patent must be licensed for everyone's free use or not " |
| "licensed at all." |
| msgstr "" |
| |
| msgid "" |
| "The precise terms and conditions for copying, distribution and " |
| "modification follow." |
| msgstr "" |
| |
| msgid "" |
| "Terms and Conditions for Copying, Distribution and Modification" |
| msgstr "" |
| |
| msgid "Section 1" |
| msgstr "" |
| |
| msgid "" |
| "You may copy and distribute verbatim copies of the Program's source " |
| "code as you receive it, in any medium, provided that you " |
| "conspicuously and appropriately publish on each copy an appropriate " |
| "copyright notice and disclaimer of warranty; keep intact all the " |
| "notices that refer to this License and to the absence of any " |
| "warranty; and give any other recipients of the Program a copy of " |
| "this License along with the Program." |
| msgstr "" |
| |
| msgid "" |
| "You may charge a fee for the physical act of transferring a copy, " |
| "and you may at your option offer warranty protection in exchange " |
| "for a fee." |
| msgstr "" |
| |
| msgid "Section 2" |
| msgstr "" |
| |
| msgid "" |
| "You may modify your copy or copies of the Program or any portion of " |
| "it, thus forming a work based on the Program, and copy and " |
| "distribute such modifications or work under the terms of <xref " |
| "linkend=\"licenses-gpl-1-1\"/> above, provided that you also meet " |
| "all of these conditions:" |
| msgstr "" |
| |
| msgid "" |
| "You must cause the modified files to carry prominent notices " |
| "stating that you changed the files and the date of any change." |
| msgstr "" |
| |
| msgid "" |
| "You must cause any work that you distribute or publish, that in " |
| "whole or in part contains or is derived from the Program or any " |
| "part thereof, to be licensed as a whole at no charge to all third " |
| "parties under the terms of this License." |
| msgstr "" |
| |
| msgid "" |
| "If the modified program normally reads commands interactively when " |
| "run, you must cause it, when started running for such interactive " |
| "use in the most ordinary way, to print or display an announcement " |
| "including an appropriate copyright notice and a notice that there " |
| "is no warranty (or else, saying that you provide a warranty) and " |
| "that users may redistribute the program under these conditions, and " |
| "telling the user how to view a copy of this License. " |
| "<note><title>Exception</title><para> If the Program itself is " |
| "interactive but does not normally print such an announcement, your " |
| "work based on the Program is not required to print an announcement. " |
| "</para></note>" |
| msgstr "" |
| |
| msgid "" |
| "These requirements apply to the modified work as a whole. If " |
| "identifiable sections of that work are not derived from the " |
| "Program, and can be reasonably considered independent and separate " |
| "works in themselves, then this License, and its terms, do not apply " |
| "to those sections when you distribute them as separate works. But " |
| "when you distribute the same sections as part of a whole which is a " |
| "work based on the Program, the distribution of the whole must be on " |
| "the terms of this License, whose permissions for other licensees " |
| "extend to the entire whole, and thus to each and every part " |
| "regardless of who wrote it." |
| msgstr "" |
| |
| msgid "" |
| "Thus, it is not the intent of this section to claim rights or " |
| "contest your rights to work written entirely by you; rather, the " |
| "intent is to exercise the right to control the distribution of " |
| "derivative or collective works based on the Program." |
| msgstr "" |
| |
| msgid "" |
| "In addition, mere aggregation of another work not based on the " |
| "Program with the Program (or with a work based on the Program) on a " |
| "volume of a storage or distribution medium does not bring the other " |
| "work under the scope of this License." |
| msgstr "" |
| |
| msgid "Section 3" |
| msgstr "" |
| |
| msgid "" |
| "You may copy and distribute the Program (or a work based on it, " |
| "under <xref linkend=\"licenses-gpl-1-2\"/>) in object code or " |
| "executable form under the terms of <xref linkend=\"licenses-gpl-1-1" |
| "\"/> and <xref linkend=\"licenses-gpl-1-2\"/> above provided that " |
| "you also do one of the following: <orderedlist numeration=" |
| "\"loweralpha\"><listitem><para> Accompany it with the complete " |
| "corresponding machine-readable source code, which must be " |
| "distributed under the terms of <xref linkend=\"licenses-gpl-1-1\"/> " |
| "and <xref linkend=\"licenses-gpl-1-2\"/> above on a medium " |
| "customarily used for software interchange; or, </para></" |
| "listitem><listitem><para> Accompany it with a written offer, valid " |
| "for at least three years, to give any third party, for a charge no " |
| "more than your cost of physically performing source distribution, a " |
| "complete machine-readable copy of the corresponding source code, to " |
| "be distributed under the terms of <xref linkend=\"licenses-gpl-1-1" |
| "\"/> and <xref linkend=\"licenses-gpl-1-2\"/> above on a medium " |
| "customarily used for software interchange; or, </para></" |
| "listitem><listitem><para> Accompany it with the information you " |
| "received as to the offer to distribute corresponding source code. " |
| "(This alternative is allowed only for noncommercial distribution " |
| "and only if you received the program in object code or executable " |
| "form with such an offer, in accord with Subsection b above.) </" |
| "para></listitem></orderedlist>" |
| msgstr "" |
| |
| msgid "" |
| "The source code for a work means the preferred form of the work for " |
| "making modifications to it. For an executable work, complete source " |
| "code means all the source code for all modules it contains, plus " |
| "any associated interface definition files, plus the scripts used to " |
| "control compilation and installation of the executable. However, as " |
| "a special exception, the source code distributed need not include " |
| "anything that is normally distributed (in either source or binary " |
| "form) with the major components (compiler, kernel, and so on) of " |
| "the operating system on which the executable runs, unless that " |
| "component itself accompanies the executable." |
| msgstr "" |
| |
| msgid "" |
| "If distribution of executable or object code is made by offering " |
| "access to copy from a designated place, then offering equivalent " |
| "access to copy the source code from the same place counts as " |
| "distribution of the source code, even though third parties are not " |
| "compelled to copy the source along with the object code." |
| msgstr "" |
| |
| msgid "Section 4" |
| msgstr "" |
| |
| msgid "" |
| "You may not copy, modify, sublicense, or distribute the Program " |
| "except as expressly provided under this License. Any attempt " |
| "otherwise to copy, modify, sublicense or distribute the Program is " |
| "void, and will automatically terminate your rights under this " |
| "License. However, parties who have received copies, or rights, from " |
| "you under this License will not have their licenses terminated so " |
| "long as such parties remain in full compliance." |
| msgstr "" |
| |
| msgid "Section 5" |
| msgstr "" |
| |
| msgid "" |
| "You are not required to accept this License, since you have not " |
| "signed it. However, nothing else grants you permission to modify or " |
| "distribute the Program or its derivative works. These actions are " |
| "prohibited by law if you do not accept this License. Therefore, by " |
| "modifying or distributing the Program (or any work based on the " |
| "Program), you indicate your acceptance of this License to do so, " |
| "and all its terms and conditions for copying, distributing or " |
| "modifying the Program or works based on it." |
| msgstr "" |
| |
| msgid "Section 6" |
| msgstr "" |
| |
| msgid "" |
| "Each time you redistribute the Program (or any work based on the " |
| "Program), the recipient automatically receives a license from the " |
| "original licensor to copy, distribute or modify the Program subject " |
| "to these terms and conditions. You may not impose any further " |
| "restrictions on the recipients' exercise of the rights granted " |
| "herein. You are not responsible for enforcing compliance by third " |
| "parties to this License." |
| msgstr "" |
| |
| msgid "Section 7" |
| msgstr "" |
| |
| msgid "" |
| "If, as a consequence of a court judgment or allegation of patent " |
| "infringement or for any other reason (not limited to patent " |
| "issues), conditions are imposed on you (whether by court order, " |
| "agreement or otherwise) that contradict the conditions of this " |
| "License, they do not excuse you from the conditions of this " |
| "License. If you cannot distribute so as to satisfy simultaneously " |
| "your obligations under this License and any other pertinent " |
| "obligations, then as a consequence you may not distribute the " |
| "Program at all. For example, if a patent license would not permit " |
| "royalty-free redistribution of the Program by all those who receive " |
| "copies directly or indirectly through you, then the only way you " |
| "could satisfy both it and this License would be to refrain entirely " |
| "from distribution of the Program." |
| msgstr "" |
| |
| msgid "" |
| "If any portion of this section is held invalid or unenforceable " |
| "under any particular circumstance, the balance of the section is " |
| "intended to apply and the section as a whole is intended to apply " |
| "in other circumstances." |
| msgstr "" |
| |
| msgid "" |
| "It is not the purpose of this section to induce you to infringe any " |
| "patents or other property right claims or to contest validity of " |
| "any such claims; this section has the sole purpose of protecting " |
| "the integrity of the free software distribution system, which is " |
| "implemented by public license practices. Many people have made " |
| "generous contributions to the wide range of software distributed " |
| "through that system in reliance on consistent application of that " |
| "system; it is up to the author/donor to decide if he or she is " |
| "willing to distribute software through any other system and a " |
| "licensee cannot impose that choice." |
| msgstr "" |
| |
| msgid "" |
| "This section is intended to make thoroughly clear what is believed " |
| "to be a consequence of the rest of this License." |
| msgstr "" |
| |
| msgid "Section 8" |
| msgstr "" |
| |
| msgid "" |
| "If the distribution and/or use of the Program is restricted in " |
| "certain countries either by patents or by copyrighted interfaces, " |
| "the original copyright holder who places the Program under this " |
| "License may add an explicit geographical distribution limitation " |
| "excluding those countries, so that distribution is permitted only " |
| "in or among countries not thus excluded. In such case, this License " |
| "incorporates the limitation as if written in the body of this " |
| "License." |
| msgstr "" |
| |
| msgid "Section 9" |
| msgstr "" |
| |
| msgid "" |
| "The Free Software Foundation may publish revised and/or new " |
| "versions of the General Public License from time to time. Such new " |
| "versions will be similar in spirit to the present version, but may " |
| "differ in detail to address new problems or concerns." |
| msgstr "" |
| |
| msgid "" |
| "Each version is given a distinguishing version number. If the " |
| "Program specifies a version number of this License which applies to " |
| "it and <quote>any later version</quote>, you have the option of " |
| "following the terms and conditions either of that version or of any " |
| "later version published by the Free Software Foundation. If the " |
| "Program does not specify a version number of this License, you may " |
| "choose any version ever published by the Free Software Foundation." |
| msgstr "" |
| |
| msgid "Section 10" |
| msgstr "" |
| |
| msgid "" |
| "If you wish to incorporate parts of the Program into other free " |
| "programs whose distribution conditions are different, write to the " |
| "author to ask for permission. For software which is copyrighted by " |
| "the Free Software Foundation, write to the Free Software " |
| "Foundation; we sometimes make exceptions for this. Our decision " |
| "will be guided by the two goals of preserving the free status of " |
| "all derivatives of our free software and of promoting the sharing " |
| "and reuse of software generally." |
| msgstr "" |
| |
| msgid "NO WARRANTY" |
| msgstr "" |
| |
| msgid "Section 11" |
| msgstr "" |
| |
| msgid "" |
| "BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO " |
| "WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE " |
| "LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS " |
| "AND/OR OTHER PARTIES PROVIDE THE PROGRAM <quote>AS IS</quote> " |
| "WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, " |
| "INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF " |
| "MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE " |
| "RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. " |
| "SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL " |
| "NECESSARY SERVICING, REPAIR OR CORRECTION." |
| msgstr "" |
| |
| msgid "Section 12" |
| msgstr "" |
| |
| msgid "" |
| "IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN " |
| "WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY " |
| "MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE " |
| "LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, " |
| "INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR " |
| "INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF " |
| "DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU " |
| "OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY " |
| "OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN " |
| "ADVISED OF THE POSSIBILITY OF SUCH DAMAGES." |
| msgstr "" |
| |
| msgid "End of Terms and Conditions." |
| msgstr "" |
| |
| msgid "How to Apply These Terms to Your New Programs" |
| msgstr "" |
| |
| msgid "" |
| "If you develop a new program, and you want it to be of the greatest " |
| "possible use to the public, the best way to achieve this is to make " |
| "it free software which everyone can redistribute and change under " |
| "these terms." |
| msgstr "" |
| |
| msgid "" |
| "To do so, attach the following notices to the program. It is safest " |
| "to attach them to the start of each source file to most effectively " |
| "convey the exclusion of warranty; and each file should have at " |
| "least the <quote>copyright</quote> line and a pointer to where the " |
| "full notice is found." |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "<one line to give the program's name and a brief idea of what it does.>\n" |
| "Copyright (C) 19yy <name of author>\n" |
| " \n" |
| "This program is free software; you can redistribute it and/or modify\n" |
| "it under the terms of the GNU General Public License as published by\n" |
| "the Free Software Foundation; either version 2 of the License, or\n" |
| "(at your option) any later version.\n" |
| " \n" |
| "This program is distributed in the hope that it will be useful,\n" |
| "but WITHOUT ANY WARRANTY; without even the implied warranty of\n" |
| "MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n" |
| "GNU General Public License for more details.\n" |
| " \n" |
| "You should have received a copy of the GNU General Public License\n" |
| "along with this program; if not, write to the Free Software\n" |
| "Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.\n" |
| msgstr "" |
| |
| msgid "" |
| "Also add information on how to contact you by electronic and paper " |
| "mail." |
| msgstr "" |
| |
| msgid "" |
| "If the program is interactive, make it output a short notice like " |
| "this when it starts in an interactive mode:" |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "Gnomovision version 69, Copyright (C) 19yy name of author\n" |
| "Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n" |
| "This is free software, and you are welcome to redistribute it\n" |
| "under certain conditions; type `show c' for details.\n" |
| msgstr "" |
| |
| msgid "" |
| "The hypothetical commands `show w' and `show c' should show the " |
| "appropriate parts of the General Public License. Of course, the " |
| "commands you use may be called something other than `show w' and " |
| "`show c'; they could even be mouse-clicks or menu items–whatever " |
| "suits your program." |
| msgstr "" |
| |
| msgid "" |
| "You should also get your employer (if you work as a programmer) or " |
| "your school, if any, to sign a <quote>copyright disclaimer</quote> " |
| "for the program, if necessary. Here is a sample; alter the names:" |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n" |
| "`Gnomovision' (which makes passes at compilers) written by James Hacker.\n" |
| " \n" |
| "<signature of Ty Coon>, 1 April 1989\n" |
| "Ty Coon, President of Vice\n" |
| msgstr "" |
| |
| msgid "" |
| "This General Public License does not permit incorporating your " |
| "program into proprietary programs. If your program is a subroutine " |
| "library, you may consider it more useful to permit linking " |
| "proprietary applications with the library. If this is what you want " |
| "to do, use the GNU Library General Public License instead of this " |
| "License." |
| msgstr "" |
| |
| msgid "GNU Free Documentation License" |
| msgstr "" |
| |
| msgid "Version 1.2, November 2002" |
| msgstr "" |
| |
| msgid "" |
| "Copyright © 2000, 2001, 2002 Free Software Foundation, Inc. 675 " |
| "Mass Ave, Cambridge, MA 02139, USA" |
| msgstr "" |
| |
| msgid "" |
| "The purpose of this License is to make a manual, textbook, or other " |
| "functional and useful document <quote>free</quote> in the sense of " |
| "freedom: to assure everyone the effective freedom to copy and " |
| "redistribute it, with or without modifying it, either commercially " |
| "or noncommercially. Secondarily, this License preserves for the " |
| "author and publisher a way to get credit for their work, while not " |
| "being considered responsible for modifications made by others." |
| msgstr "" |
| |
| msgid "" |
| "This License is a kind of <quote>copyleft</quote>, which means that " |
| "derivative works of the document must themselves be free in the " |
| "same sense. It complements the <xref linkend=\"licenses-gfdl\"/>, " |
| "which is a copyleft license designed for free software." |
| msgstr "" |
| |
| msgid "" |
| "We have designed this License in order to use it for manuals for " |
| "free software, because free software needs free documentation: a " |
| "free program should come with manuals providing the same freedoms " |
| "that the software does. But this License is not limited to software " |
| "manuals; it can be used for any textual work, regardless of subject " |
| "matter or whether it is published as a printed book. We recommend " |
| "this License principally for works whose purpose is instruction or " |
| "reference." |
| msgstr "" |
| |
| msgid "Applicability and definitions" |
| msgstr "" |
| |
| msgid "" |
| "This License applies to any manual or other work, in any medium, " |
| "that contains a notice placed by the copyright holder saying it can " |
| "be distributed under the terms of this License. Such a notice " |
| "grants a world-wide, royalty-free license, unlimited in duration, " |
| "to use that work under the conditions stated herein. The " |
| "<quote>Document</quote>, below, refers to any such manual or work. " |
| "Any member of the public is a licensee, and is addressed as " |
| "<quote>you</quote>. You accept the license if you copy, modify or " |
| "distribute the work in a way requiring permission under copyright " |
| "law." |
| msgstr "" |
| |
| msgid "" |
| "A <quote>Modified Version</quote> of the Document means any work " |
| "containing the Document or a portion of it, either copied verbatim, " |
| "or with modifications and/or translated into another language." |
| msgstr "" |
| |
| msgid "" |
| "A <quote>Secondary Section</quote> is a named appendix or a front-" |
| "matter section of the Document that deals exclusively with the " |
| "relationship of the publishers or authors of the Document to the " |
| "Document's overall subject (or to related matters) and contains " |
| "nothing that could fall directly within that overall subject. " |
| "(Thus, if the Document is in part a textbook of mathematics, a " |
| "<xref linkend=\"secondary-section\"/> may not explain any " |
| "mathematics.) The relationship could be a matter of historical " |
| "connection with the subject or with related matters, or of legal, " |
| "commercial, philosophical, ethical or political position regarding " |
| "them." |
| msgstr "" |
| |
| msgid "" |
| "The <quote>Invariant Sections</quote> are certain <xref linkend=" |
| "\"secondary-section\"/> whose titles are designated, as being those " |
| "of Invariant Sections, in the notice that says that the Document is " |
| "released under this License. If a section does not fit the above " |
| "definition of Secondary then it is not allowed to be designated as " |
| "Invariant. The Document may contain zero Invariant Sections. If the " |
| "Document does not identify any Invariant Section then there are " |
| "none." |
| msgstr "" |
| |
| msgid "" |
| "The <quote>Cover Texts</quote> are certain short passages of text " |
| "that are listed, as Front-Cover Texts or Back-Cover Texts, in the " |
| "notice that says that the Document is released under this License. " |
| "A Front-Cover Text may be at most 5 words, and a Back-Cover Text " |
| "may be at most 25 words." |
| msgstr "" |
| |
| msgid "" |
| "A <quote>Transparent</quote> copy of the Document means a machine-" |
| "readable copy, represented in a format whose specification is " |
| "available to the general public, that is suitable for revising the " |
| "document straightforwardly with generic text editors or (for images " |
| "composed of pixels) generic paint programs or (for drawings) some " |
| "widely available drawing editor, and that is suitable for input to " |
| "text formatters or for automatic translation to a variety of " |
| "formats suitable for input to text formatters. A copy made in an " |
| "otherwise <xref linkend=\"transparent\"/> file format whose markup, " |
| "or absence of markup, has been arranged to thwart or discourage " |
| "subsequent modification by readers is not <xref linkend=" |
| "\"transparent\"/>. An image format is not <xref linkend=" |
| "\"transparent\"/> if used for any substantial amount of text. A " |
| "copy that is not <quote><xref linkend=\"transparent\"/></quote> is " |
| "called <quote>Opaque</quote>." |
| msgstr "" |
| |
| msgid "" |
| "Examples of suitable formats for <xref linkend=\"transparent\"/> " |
| "copies include plain ASCII without markup, Texinfo input format, " |
| "LaTeX input format, SGML or XML using a publicly available DTD, and " |
| "standard-conforming simple HTML, PostScript or PDF designed for " |
| "human modification. Examples of transparent image formats include " |
| "PNG, XCF and JPG. Opaque formats include proprietary formats that " |
| "can be read and edited only by proprietary word processors, SGML or " |
| "XML for which the DTD and/or processing tools are not generally " |
| "available, and the machine-generated HTML, PostScript or PDF " |
| "produced by some word processors for output purposes only." |
| msgstr "" |
| |
| msgid "" |
| "The <quote>Title Page</quote> means, for a printed book, the title " |
| "page itself, plus such following pages as are needed to hold, " |
| "legibly, the material this License requires to appear in the title " |
| "page. For works in formats which do not have any title page as " |
| "such, <quote>Title Page</quote> means the text near the most " |
| "prominent appearance of the work's title, preceding the beginning " |
| "of the body of the text." |
| msgstr "" |
| |
| msgid "" |
| "A section <quote>Entitled XYZ</quote> means a named subunit of the " |
| "Document whose title either is precisely XYZ or contains XYZ in " |
| "parentheses following text that translates XYZ in another language. " |
| "(Here XYZ stands for a specific section name mentioned below, such " |
| "as <quote>Acknowledgements</quote>, <quote>Dedications</quote>, " |
| "<quote>Endorsements</quote>, or <quote>History</quote>.) To " |
| "<quote>Preserve the Title</quote> of such a section when you modify " |
| "the Document means that it remains a section <quote>Entitled XYZ</" |
| "quote> according to this definition." |
| msgstr "" |
| |
| msgid "" |
| "The Document may include Warranty Disclaimers next to the notice " |
| "which states that this License applies to the Document. These " |
| "Warranty Disclaimers are considered to be included by reference in " |
| "this License, but only as regards disclaiming warranties: any other " |
| "implication that these Warranty Disclaimers may have is void and " |
| "has no effect on the meaning of this License." |
| msgstr "" |
| |
| msgid "Verbatim copying" |
| msgstr "" |
| |
| msgid "" |
| "You may copy and distribute the Document in any medium, either " |
| "commercially or noncommercially, provided that this License, the " |
| "copyright notices, and the license notice saying this License " |
| "applies to the Document are reproduced in all copies, and that you " |
| "add no other conditions whatsoever to those of this License. You " |
| "may not use technical measures to obstruct or control the reading " |
| "or further copying of the copies you make or distribute. However, " |
| "you may accept compensation in exchange for copies. If you " |
| "distribute a large enough number of copies you must also follow the " |
| "conditions in section <xref linkend=\"licenses-gfdl-section-4\"/>." |
| msgstr "" |
| |
| msgid "" |
| "You may also lend copies, under the same conditions stated above, " |
| "and you may publicly display copies." |
| msgstr "" |
| |
| msgid "Copying in quantity" |
| msgstr "" |
| |
| msgid "" |
| "If you publish printed copies (or copies in media that commonly " |
| "have printed covers) of the Document, numbering more than 100, and " |
| "the Document's license notice requires Cover Texts, you must " |
| "enclose the copies in covers that carry, clearly and legibly, all " |
| "these <xref linkend=\"cover-texts\"/>: Front-Cover Texts on the " |
| "front cover, and Back-Cover Texts on the back cover. Both covers " |
| "must also clearly and legibly identify you as the publisher of " |
| "these copies. The front cover must present the full title with all " |
| "words of the title equally prominent and visible. You may add other " |
| "material on the covers in addition. Copying with changes limited to " |
| "the covers, as long as they preserve the title of the Document and " |
| "satisfy these conditions, can be treated as verbatim copying in " |
| "other respects." |
| msgstr "" |
| |
| msgid "" |
| "If the required texts for either cover are too voluminous to fit " |
| "legibly, you should put the first ones listed (as many as fit " |
| "reasonably) on the actual cover, and continue the rest onto " |
| "adjacent pages." |
| msgstr "" |
| |
| msgid "" |
| "If you publish or distribute Opaque copies of the Document " |
| "numbering more than 100, you must either include a machine-readable " |
| "<xref linkend=\"transparent\"/> copy along with each Opaque copy, " |
| "or state in or with each Opaque copy a computer-network location " |
| "from which the general network-using public has access to download " |
| "using public-standard network protocols a complete <xref linkend=" |
| "\"transparent\"/> copy of the Document, free of added material. If " |
| "you use the latter option, you must take reasonably prudent steps, " |
| "when you begin distribution of Opaque copies in quantity, to ensure " |
| "that this <xref linkend=\"transparent\"/> copy will remain thus " |
| "accessible at the stated location until at least one year after the " |
| "last time you distribute an Opaque copy (directly or through your " |
| "agents or retailers) of that edition to the public." |
| msgstr "" |
| |
| msgid "" |
| "It is requested, but not required, that you contact the authors of " |
| "the Document well before redistributing any large number of copies, " |
| "to give them a chance to provide you with an updated version of the " |
| "Document." |
| msgstr "" |
| |
| msgid "Modifications" |
| msgstr "" |
| |
| msgid "" |
| "You may copy and distribute a <xref linkend=\"modified-version\"/> " |
| "of the Document under the conditions of sections <xref linkend=" |
| "\"licenses-gfdl-section-3\"/> and <xref linkend=\"licenses-gfdl-" |
| "section-4\"/> above, provided that you release the <xref linkend=" |
| "\"modified-version\"/> under precisely this License, with the <xref " |
| "linkend=\"modified-version\"/> filling the role of the Document, " |
| "thus licensing distribution and modification of the <xref linkend=" |
| "\"modified-version\"/> to whoever possesses a copy of it. In " |
| "addition, you must do these things in the <xref linkend=\"modified-" |
| "version\"/>: <orderedlist numeration=\"upperalpha" |
| "\"><listitem><para>Use in the <xref linkend=\"title-page\"/> (and " |
| "on the covers, if any) a title distinct from that of the Document, " |
| "and from those of previous versions (which should, if there were " |
| "any, be listed in the History section of the Document). You may use " |
| "the same title as a previous version if the original publisher of " |
| "that version gives permission.</para></" |
| "listitem><listitem><para>List on the <xref linkend=\"title-page\"/" |
| ">, as authors, one or more persons or entities responsible for " |
| "authorship of the modifications in the <xref linkend=\"modified-" |
| "version\"/>, together with at least five of the principal authors " |
| "of the Document (all of its principal authors, if it has fewer than " |
| "five), unless they release you from this requirement.</para></" |
| "listitem><listitem><para>State on the <xref linkend=\"title-page\"/" |
| "> the name of the publisher of the <xref linkend=\"modified-version" |
| "\"/>, as the publisher.</para></listitem><listitem><para>Preserve " |
| "all the copyright notices of the Document.</para></" |
| "listitem><listitem><para>Add an appropriate copyright notice for " |
| "your modifications adjacent to the other copyright notices.</para></" |
| "listitem><listitem><para>Include, immediately after the copyright " |
| "notices, a license notice giving the public permission to use the " |
| "<xref linkend=\"modified-version\"/> under the terms of this " |
| "License, in the form shown in the Addendum below.</para></" |
| "listitem><listitem><para>Preserve in that license notice the full " |
| "lists of <xref linkend=\"invariant-sections\"/> and required <xref " |
| "linkend=\"cover-texts\"/> given in the Document's license notice.</" |
| "para></listitem><listitem><para>Include an unaltered copy of this " |
| "License.</para></listitem><listitem><para>Preserve the section " |
| "Entitled <quote>History</quote>, Preserve its Title, and add to it " |
| "an item stating at least the title, year, new authors, and " |
| "publisher of the <xref linkend=\"modified-version\"/> as given on " |
| "the <xref linkend=\"title-page\"/>. If there is no section Entitled " |
| "<quote>History</quote> in the Document, create one stating the " |
| "title, year, authors, and publisher of the Document as given on its " |
| "<xref linkend=\"title-page\"/>, then add an item describing the " |
| "<xref linkend=\"modified-version\"/> as stated in the previous " |
| "sentence.</para></listitem><listitem><para>Preserve the network " |
| "location, if any, given in the Document for public access to a " |
| "<xref linkend=\"transparent\"/> copy of the Document, and likewise " |
| "the network locations given in the Document for previous versions " |
| "it was based on. These may be placed in the <quote>History</quote> " |
| "section. You may omit a network location for a work that was " |
| "published at least four years before the Document itself, or if the " |
| "original publisher of the version it refers to gives permission.</" |
| "para></listitem><listitem><para>For any section Entitled " |
| "<quote>Acknowledgements</quote> or <quote>Dedications</quote>, " |
| "Preserve the Title of the section, and preserve in the section all " |
| "the substance and tone of each of the contributor acknowledgements " |
| "and/or dedications given therein.</para></" |
| "listitem><listitem><para>Preserve all the <xref linkend=\"invariant-" |
| "sections\"/> of the Document, unaltered in their text and in their " |
| "titles. Section numbers or the equivalent are not considered part " |
| "of the section titles.</para></listitem><listitem><para>Delete any " |
| "section Entitled <quote>Endorsements</quote>. Such a section may " |
| "not be included in the <xref linkend=\"modified-version\"/>.</" |
| "para></listitem><listitem><para>Do not retitle any existing section " |
| "to be Entitled <quote>Endorsements</quote> or to conflict in title " |
| "with any <xref linkend=\"invariant-sections\"/>.</para></" |
| "listitem><listitem><para>Preserve any Warranty Disclaimers.</para></" |
| "listitem></orderedlist>" |
| msgstr "" |
| |
| msgid "" |
| "If the <xref linkend=\"modified-version\"/> includes new front-" |
| "matter sections or appendices that qualify as <xref linkend=" |
| "\"secondary-section\"/> and contain no material copied from the " |
| "Document, you may at your option designate some or all of these " |
| "sections as invariant. To do this, add their titles to the list of " |
| "<xref linkend=\"invariant-sections\"/> in the <xref linkend=" |
| "\"modified-version\"/>'s license notice. These titles must be " |
| "distinct from any other section titles." |
| msgstr "" |
| |
| msgid "" |
| "You may add a section Entitled <quote>Endorsements</quote>, " |
| "provided it contains nothing but endorsements of your <xref linkend=" |
| "\"modified-version\"/> by various parties–for example, statements " |
| "of peer review or that the text has been approved by an " |
| "organization as the authoritative definition of a standard." |
| msgstr "" |
| |
| msgid "" |
| "You may add a passage of up to five words as a Front-Cover Text, " |
| "and a passage of up to 25 words as a Back-Cover Text, to the end of " |
| "the list of <xref linkend=\"cover-texts\"/> in the <xref linkend=" |
| "\"modified-version\"/>. Only one passage of Front-Cover Text and " |
| "one of Back-Cover Text may be added by (or through arrangements " |
| "made by) any one entity. If the Document already includes a cover " |
| "text for the same cover, previously added by you or by arrangement " |
| "made by the same entity you are acting on behalf of, you may not " |
| "add another; but you may replace the old one, on explicit " |
| "permission from the previous publisher that added the old one." |
| msgstr "" |
| |
| msgid "" |
| "The author(s) and publisher(s) of the Document do not by this " |
| "License give permission to use their names for publicity for or to " |
| "assert or imply endorsement of any <xref linkend=\"modified-version" |
| "\"/>." |
| msgstr "" |
| |
| msgid "Combining documents" |
| msgstr "" |
| |
| msgid "" |
| "You may combine the Document with other documents released under " |
| "this License, under the terms defined in section <xref linkend=" |
| "\"licenses-gfdl-section-5\"/> above for modified versions, provided " |
| "that you include in the combination all of the <xref linkend=" |
| "\"invariant-sections\"/> of all of the original documents, " |
| "unmodified, and list them all as <xref linkend=\"invariant-sections" |
| "\"/> of your combined work in its license notice, and that you " |
| "preserve all their Warranty Disclaimers." |
| msgstr "" |
| |
| msgid "" |
| "The combined work need only contain one copy of this License, and " |
| "multiple identical <xref linkend=\"invariant-sections\"/> may be " |
| "replaced with a single copy. If there are multiple <xref linkend=" |
| "\"invariant-sections\"/> with the same name but different contents, " |
| "make the title of each such section unique by adding at the end of " |
| "it, in parentheses, the name of the original author or publisher of " |
| "that section if known, or else a unique number. Make the same " |
| "adjustment to the section titles in the list of <xref linkend=" |
| "\"invariant-sections\"/> in the license notice of the combined work." |
| msgstr "" |
| |
| msgid "" |
| "In the combination, you must combine any sections Entitled " |
| "<quote>History</quote> in the various original documents, forming " |
| "one section Entitled <quote>History</quote>; likewise combine any " |
| "sections Entitled <quote>Acknowledgements</quote>, and any sections " |
| "Entitled <quote>Dedications</quote>. You must delete all sections " |
| "Entitled <quote>Endorsements</quote>." |
| msgstr "" |
| |
| msgid "Collection of documents" |
| msgstr "" |
| |
| msgid "" |
| "You may make a collection consisting of the Document and other " |
| "documents released under this License, and replace the individual " |
| "copies of this License in the various documents with a single copy " |
| "that is included in the collection, provided that you follow the " |
| "rules of this License for verbatim copying of each of the documents " |
| "in all other respects." |
| msgstr "" |
| |
| msgid "" |
| "You may extract a single document from such a collection, and " |
| "distribute it individually under this License, provided you insert " |
| "a copy of this License into the extracted document, and follow this " |
| "License in all other respects regarding verbatim copying of that " |
| "document." |
| msgstr "" |
| |
| msgid "Aggregation with independent works" |
| msgstr "" |
| |
| msgid "" |
| "A compilation of the Document or its derivatives with other " |
| "separate and independent documents or works, in or on a volume of a " |
| "storage or distribution medium, is called an <quote>aggregate</" |
| "quote> if the copyright resulting from the compilation is not used " |
| "to limit the legal rights of the compilation's users beyond what " |
| "the individual works permit. When the Document is included in an " |
| "aggregate, this License does not apply to the other works in the " |
| "aggregate which are not themselves derivative works of the Document." |
| msgstr "" |
| |
| msgid "" |
| "If the Cover Text requirement of section <xref linkend=\"licenses-" |
| "gfdl-section-4\"/> is applicable to these copies of the Document, " |
| "then if the Document is less than one half of the entire aggregate, " |
| "the Document's <xref linkend=\"cover-texts\"/> may be placed on " |
| "covers that bracket the Document within the aggregate, or the " |
| "electronic equivalent of covers if the Document is in electronic " |
| "form. Otherwise they must appear on printed covers that bracket the " |
| "whole aggregate." |
| msgstr "" |
| |
| msgid "Translations" |
| msgstr "" |
| |
| msgid "" |
| "Translation is considered a kind of modification, so you may " |
| "distribute translations of the Document under the terms of section " |
| "<xref linkend=\"licenses-gfdl-section-5\"/>. Replacing <xref " |
| "linkend=\"invariant-sections\"/>with translations requires special " |
| "permission from their copyright holders, but you may include " |
| "translations of some or all <xref linkend=\"invariant-sections\"/> " |
| "in addition to the original versions of these <xref linkend=" |
| "\"invariant-sections\"/>. You may include a translation of this " |
| "License, and all the license notices in the Document, and any " |
| "Warranty Disclaimers, provided that you also include the original " |
| "English version of this License and the original versions of those " |
| "notices and disclaimers. In case of a disagreement between the " |
| "translation and the original version of this License or a notice or " |
| "disclaimer, the original version will prevail." |
| msgstr "" |
| |
| msgid "" |
| "If a section in the Document is Entitled <quote>Acknowledgements</" |
| "quote>, <quote>Dedications</quote>, or <quote>History</quote>, the " |
| "requirement (section <xref linkend=\"licenses-gfdl-section-5\"/>) " |
| "to Preserve its Title (section <xref linkend=\"licenses-gfdl-" |
| "section-2\"/>) will typically require changing the actual title." |
| msgstr "" |
| |
| msgid "Termination" |
| msgstr "" |
| |
| msgid "" |
| "You may not copy, modify, sublicense, or distribute the Document " |
| "except as expressly provided for under this License. Any other " |
| "attempt to copy, modify, sublicense or distribute the Document is " |
| "void, and will automatically terminate your rights under this " |
| "License. However, parties who have received copies, or rights, from " |
| "you under this License will not have their licenses terminated so " |
| "long as such parties remain in full compliance." |
| msgstr "" |
| |
| msgid "Future Revisions of this License" |
| msgstr "" |
| |
| msgid "" |
| "The Free Software Foundation may publish new, revised versions of " |
| "the GNU Free Documentation License from time to time. Such new " |
| "versions will be similar in spirit to the present version, but may " |
| "differ in detail to address new problems or concerns. See <ulink " |
| "url=\"http://www.gnu.org/copyleft/\"/>." |
| msgstr "" |
| |
| msgid "" |
| "Each version of the License is given a distinguishing version " |
| "number. If the Document specifies that a particular numbered " |
| "version of this License <quote>or any later version</quote> applies " |
| "to it, you have the option of following the terms and conditions " |
| "either of that specified version or of any later version that has " |
| "been published (not as a draft) by the Free Software Foundation. If " |
| "the Document does not specify a version number of this License, you " |
| "may choose any version ever published (not as a draft) by the Free " |
| "Software Foundation." |
| msgstr "" |
| |
| msgid "How to use this License for your documents" |
| msgstr "" |
| |
| msgid "" |
| "To use this License in a document you have written, include a copy " |
| "of the License in the document and put the following copyright and " |
| "license notices just after the title page:" |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "Copyright (C) YEAR YOUR NAME.\n" |
| "\n" |
| "Permission is granted to copy, distribute and/or modify this\n" |
| "document under the terms of the GNU Free Documentation License,\n" |
| "Version 1.2 or any later version published by the Free Software\n" |
| "Foundation; with no Invariant Sections, no Front-Cover Texts, and\n" |
| "no Back-Cover Texts. A copy of the license is included in the\n" |
| "section entitled <quote>GNU Free Documentation License</quote>.\n" |
| msgstr "" |
| |
| msgid "" |
| "If you have <xref linkend=\"invariant-sections\"/>, Front-Cover " |
| "Texts and Back-Cover Texts, replace the <quote>with...Texts</" |
| "quote>. line with this:" |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "with the Invariant Sections being LIST THEIR TITLES, with the\n" |
| "Front-Cover Texts being LIST, and with the Back-Cover Texts being\n" |
| "LIST.\n" |
| msgstr "" |
| |
| msgid "" |
| "If you have <xref linkend=\"invariant-sections\"/> without <xref " |
| "linkend=\"cover-texts\"/>, or some other combination of the three, " |
| "merge those two alternatives to suit the situation." |
| msgstr "" |
| |
| msgid "" |
| "If your document contains nontrivial examples of program code, we " |
| "recommend releasing these examples in parallel under your choice of " |
| "free software license, such as the GNU General Public License, to " |
| "permit their use in free software." |
| msgstr "" |
| |
| |
| msgid "translator-credits" |
| msgstr "" |