| msgid "" |
| msgstr "" |
| "Project-Id-Version: PACKAGE VERSION\n" |
| "POT-Creation-Date: 2012-09-16 11:22-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: 'Images/Manuals/Corporate/monolithic.png'; " |
| "md5=6d128a567333d3f96ff0fd5e4c49abf6" |
| 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 "2012" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink>. All rights reserved." |
| msgstr "" |
| |
| msgid "" |
| "Permission is granted to copy, distribute and/or modify this " |
| "document under the terms of the GNU Free Documentation License, " |
| "Version 1.2 or any later version published by the Free Software " |
| "Foundation; with no Invariant Sections, no Front-Cover Texts, and " |
| "no Back-Cover Texts. A copy of the license is included in <xref " |
| "linkend=\"licenses-gfdl\"/>." |
| msgstr "" |
| |
| msgid "1.0" |
| msgstr "" |
| |
| msgid "Today" |
| msgstr "" |
| |
| msgid "Under development." |
| msgstr "" |
| |
| msgid "Preface" |
| msgstr "" |
| |
| msgid "Overview" |
| msgstr "" |
| |
| msgid "" |
| "Welcome to <citetitle>The CentOS Artwork Repository User's Guide</" |
| "citetitle>, the official documentation of <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>." |
| msgstr "" |
| |
| msgid "" |
| "This book describes the corporate visual identity of <ulink type=" |
| "\"http\" url=\"http://www.centos.org\">The CentOS Project</ulink> " |
| "and the way it is produced. If you are interested in making <ulink " |
| "type=\"http\" url=\"http://www.centos.org\">The CentOS Project</" |
| "ulink> a more beautiful project, this book is definitly for you." |
| msgstr "" |
| |
| msgid "" |
| "To make the information in this book managable, it has been " |
| "organized in the following parts:" |
| msgstr "" |
| |
| msgid "" |
| "<xref linkend=\"repo\"/> describes the convenctions you should " |
| "follow to keep everything organized and consistent inside the " |
| "repository directory structure, how to to install and configure a " |
| "working copy inside your workstation. At the end of this part you " |
| "will find a history of most relevant changes committed to the " |
| "repository along the years." |
| msgstr "" |
| |
| msgid "" |
| "<xref linkend=\"identity\"/> describes the corporate visual " |
| "identity of the organization known as <ulink type=\"http\" url=" |
| "\"http://www.centos.org\">The CentOS Project</ulink> and the " |
| "production tasks related to image rendition inside <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink>. If you are a graphic designer, " |
| "this part of the book might result interesting to you." |
| msgstr "" |
| |
| msgid "" |
| "<xref linkend=\"locale\"/> describes production tasks related to " |
| "content internationalization and localization inside <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink>. If you are a translator, this " |
| "part of the book might result interesting to you." |
| msgstr "" |
| |
| msgid "" |
| "<xref linkend=\"manuals\"/> describes production tasks related to " |
| "content documentation inside <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink>. If you are a documentor, this part of the book might result " |
| "interesting to you." |
| msgstr "" |
| |
| msgid "" |
| "<xref linkend=\"scripts\"/> describes automation of production " |
| "tasks inside <ulink type=\"https\" url=\"https://projects.centos." |
| "org/svn/artwork\">The CentOS Artwork Repository</ulink>. If you are " |
| "a programmer, this part of the book might result interesting to you." |
| msgstr "" |
| |
| msgid "" |
| "<xref linkend=\"licenses\"/> organizes the licenses mentioned in " |
| "this book." |
| msgstr "" |
| |
| msgid "" |
| "This book assumes you have a basic understanding of The CentOS " |
| "Distribution. If you need help with it, go to the <ulink url=" |
| "\"http://wiki.centos.org/Help\">Help</ulink> page inside <ulink " |
| "type=\"http\" url=\"http://wiki.centos.org/\">The CentOS Wiki</" |
| "ulink> for or a list of different places you can find help." |
| msgstr "" |
| |
| msgid "Document Convenctions" |
| msgstr "" |
| |
| msgid "" |
| "In this manual, certain words are represented in different fonts, " |
| "typefaces, sizes, and weights. This highlighting is systematic; " |
| "different words are represented in the same style to indicate their " |
| "inclusion in a specific category. The types of words that are " |
| "represented this way include the following:" |
| msgstr "" |
| |
| msgid "command" |
| msgstr "" |
| |
| msgid "" |
| "Linux commands (and other operating system commands, when used) are " |
| "represented this way. This style should indicate to you that you " |
| "can type the word or phrase on the command line and press " |
| "<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 a bug in <ulink type=\"https\" url=\"https://projects." |
| "centos.org/svn/artwork\">The CentOS Artwork Repository</ulink> or " |
| "this manual, we would like to hear about it. To report bugs related " |
| "to this manual, send an e-mail to the <email>centos-devel@centos." |
| "org</email> mailing list. When you write the bug report, take care " |
| "of being specific about the problem you are reporting on (e.g., " |
| "where it is, the section number, etc.) so we can found it easily." |
| msgstr "" |
| |
| msgid "Repository" |
| msgstr "" |
| |
| msgid "Repository Convenctions" |
| msgstr "" |
| |
| msgid "Repository Mission" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> exists to produce <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 inside <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> provides organization through a convenctional " |
| "<filename class=\"directory\">trunk/</filename>, <filename class=" |
| "\"directory\">branches/</filename> and <filename class=\"directory" |
| "\">tags/</filename> layout. As proposition we are assuming that:" |
| msgstr "" |
| |
| msgid "" |
| "The <filename class=\"directory\">trunk/</filename> directory is " |
| "where development changes take place." |
| msgstr "" |
| |
| msgid "" |
| "The <filename class=\"directory\">branches/</filename> directory is " |
| "where maintainance changes take place." |
| msgstr "" |
| |
| msgid "" |
| "The <filename class=\"directory\">tags/</filename> directory is " |
| "where final releases take place." |
| msgstr "" |
| |
| msgid "" |
| "The second level of directories inside <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> provides organization for different work lines, " |
| "as described in <xref linkend=\"repo-convs-worklines\"/>. All other " |
| "subsequent directory levels from third level on exist to organize " |
| "specific concepts related to the work line they belong to." |
| msgstr "" |
| |
| msgid "Repository Work Lines" |
| msgstr "" |
| |
| msgid "" |
| "The content production inside <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> has been divided into individual work lines that relate one " |
| "another based on the idea of doing one thing well. In this model, " |
| "the content produced individually by each work line is combined one " |
| "another later to achieve higher purposes (e.g., corporate identity " |
| "for <ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink>). The repository work lines, as conceived here, " |
| "provide a relaible environment for people to work syncronized and " |
| "descentralized." |
| msgstr "" |
| |
| msgid "" |
| "The action of combining work lines inside <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> is known as the corporate identity production " |
| "cycle. The rest of this section describes the work lines available " |
| "in the repository and how they fit inside the corporate identity " |
| "production cycle." |
| msgstr "" |
| |
| msgid "Visual Identity" |
| msgstr "" |
| |
| msgid "" |
| "The visual identity is the first component we work out in order to " |
| "produce a new corporate identity. Through this work line, graphic " |
| "designers create <quote>models</quote> and <quote>motifs</quote> " |
| "for all the visual manifestation <ulink type=\"http\" url=\"http://" |
| "www.centos.org\">The CentOS Project</ulink> is made of. Once design " |
| "models and artistic motifs are set in place, graphic designers use " |
| "the <function>render</function> functionality described in <xref " |
| "linkend=\"scripts-bash-render\"/> to combine both design models and " |
| "artistic motifs into final images." |
| msgstr "" |
| |
| msgid "" |
| "The main purposes of this work line is define all the visual " |
| "manifestations the <ulink type=\"http\" url=\"http://www.centos.org" |
| "\">The CentOS Project</ulink> is made of and provide design models " |
| "and artistic motifs for them in order to render the set of images " |
| "required to transmit the visual style that identifies <ulink type=" |
| "\"http\" url=\"http://www.centos.org\">The CentOS Project</ulink> " |
| "as unique organization. To know more about <ulink type=\"http\" url=" |
| "\"http://www.centos.org\">The CentOS Project</ulink> Corporate " |
| "Visual Identity, read <xref linkend=\"identity\"/>." |
| msgstr "" |
| |
| msgid "" |
| "The visual identity work line takes palce in the <ulink url=" |
| "\"https://projects.centos.org/svn/artwork/trunk/Identity" |
| "\"><filename class=\"directory\">trunk/Identity</filename></ulink> " |
| "directory." |
| msgstr "" |
| |
| msgid "Localization" |
| msgstr "" |
| |
| msgid "" |
| "The content localization is the second component that must be " |
| "worked out in the corporate identity production cycle. Through this " |
| "work line translators localize source files (e.g., SVG, DocBook, " |
| "Shell scripts) which are later use to produce localized images, " |
| "localized documentation and localized automation scripts. To " |
| "localize source files, translators use the <function>locale</" |
| "function> functionality described in <xref linkend=\"scripts-bash-" |
| "locale\"/> which takes 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 main purpose of this work line is extend the visual identity " |
| "(produced in English language) to as many native languages as " |
| "possible in order for people which doesn't understand English " |
| "languague to feel more confortable with <ulink type=\"http\" url=" |
| "\"http://www.centos.org\">The CentOS Project</ulink> and its " |
| "messages. To know more about the specific localization process read " |
| "<xref linkend=\"locale\"/>." |
| msgstr "" |
| |
| msgid "" |
| "The localization work line takes palce in the <ulink url=\"https://" |
| "projects.centos.org/svn/artwork/trunk/Locales\"><filename class=" |
| "\"directory\">trunk/Locales</filename></ulink> directory." |
| msgstr "" |
| |
| msgid "Documentation" |
| msgstr "" |
| |
| msgid "" |
| "The documentation work line is the third component that must be " |
| "worked out in the corporate identity production cycle. Through this " |
| "work line documentors settle down the conceptual and practical used " |
| "to edificate <ulink type=\"https\" url=\"https://projects.centos." |
| "org/svn/artwork\">The CentOS Artwork Repository</ulink>. To write " |
| "documentation, documentors use the <function>help</function> " |
| "functionality described in <xref linkend=\"scripts-bash-help\"/> " |
| "which provides a consistent interface for building documentation " |
| "through different documentation backends (e.g., Texinfo, DocBook, " |
| "LaTeX, etc.)." |
| msgstr "" |
| |
| msgid "" |
| "The main purpose of this work line is describe the standard " |
| "procedures <ulink type=\"https\" url=\"https://projects.centos.org/" |
| "svn/artwork\">The CentOS Artwork Repository</ulink> realies on, as " |
| "well as conceive a place to help you understand what <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink> is and what can you do with it." |
| msgstr "" |
| |
| msgid "" |
| "The documentation work line takes palce in the <ulink url=\"https://" |
| "projects.centos.org/svn/artwork/trunk/Manuals\"><filename class=" |
| "\"directory\">trunk/Manuals</filename></ulink> directory." |
| msgstr "" |
| |
| msgid "Packaging" |
| msgstr "" |
| |
| msgid "" |
| "The packaging work line is the fourth component that must be worked " |
| "out in the corporate identity production cycle. Through this work " |
| "line packager gather final images, final translations and final " |
| "documentation related to art works and put all together inside RPM " |
| "packages. For this purpose, packagers use the <function>pack</" |
| "function> describe in <xref linkend=\"scripts-bash-pack\"/> which " |
| "provides a consistent interface for building packages inside the " |
| "repository." |
| msgstr "" |
| |
| msgid "" |
| "The main purpose of this work line is pack all the information " |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> requires to rebrand The CentOS Distribution " |
| "according Red Hat redistribution guidelines." |
| msgstr "" |
| |
| msgid "" |
| "The packaging work line takes palce in the <ulink url=\"https://" |
| "projects.centos.org/svn/artwork/trunk/Packages\"><filename class=" |
| "\"directory\">trunk/Packages</filename></ulink> directory." |
| msgstr "" |
| |
| msgid "Automation" |
| msgstr "" |
| |
| msgid "" |
| "The automation work line is the fifth and last component that must " |
| "be worked out in the corporate identity production cycle. This work " |
| "line closes the production cycle and provides the production " |
| "standards graphic designers, documentors, translators and packagers " |
| "need to make their work consistent and reusable. For this purpose, " |
| "programmers develop the <command>centos-art.sh</command> script " |
| "described in <xref linkend=\"scripts\"/>." |
| msgstr "" |
| |
| msgid "" |
| "The main purpose of this work line is standardize the interaction " |
| "of work lines in a reliable way." |
| msgstr "" |
| |
| msgid "" |
| "The automation work line takes palce in the <ulink url=\"https://" |
| "projects.centos.org/svn/artwork/trunk/Scripts\"><filename class=" |
| "\"directory\">trunk/Scripts</filename></ulink> directory." |
| 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.). 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:" |
| msgstr "" |
| |
| msgid "trunk/Identity/Models/Brands" |
| msgstr "" |
| |
| msgid "trunk/Manuals/Tcar-ug" |
| msgstr "" |
| |
| msgid "trunk/Identity/Models/Themes/Default/Distro/5/Anaconda" |
| msgstr "" |
| |
| msgid "Auxiliar Paths" |
| msgstr "" |
| |
| msgid "" |
| "An auxiliar path refers to directories inside the repository " |
| "considered auxiliar for one single master path. Auxiliar path can " |
| "be either for output or localization. Assuming the master path " |
| "provides the input information, the auxiliar paths provide the " |
| "auxiliar information which describes how and where that input " |
| "information must be rendered by automation scripts. Examples of " |
| "auxiliar paths inside the repository include:" |
| msgstr "" |
| |
| msgid "trunk/Identity/Images/Brands" |
| msgstr "" |
| |
| msgid "trunk/Manuals/Tcar-ug/es_ES" |
| msgstr "" |
| |
| msgid "trunk/Locales/Manuals/Tcar-ug/es_ES" |
| msgstr "" |
| |
| msgid "trunk/Identity/Images/Themes/Flame/3/Distro/5/Anaconda/es_ES" |
| msgstr "" |
| |
| msgid "trunk/Locales/Identity/Models/Default/Distro/5/Anaconda/es_ES" |
| msgstr "" |
| |
| msgid "" |
| "The relationship between master and auxiliar paths is built by " |
| "combining the second directory level of master paths with " |
| "directories in the second directory level of repository layout. In " |
| "the second directory level of repository layout, the <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 <varname>LANG</varname> environment variable is " |
| "set to <quote>es_ES.UTF-8</quote> and you execute the " |
| "<function>render</function> functionality of <command>centos-art." |
| "sh</command> script with the <filename class=\"directory\">trunk/" |
| "Manuals/Tcar-ug</filename> master path as argument, it will produce " |
| "<citetitle>The CentOS Artwork Repository User's Guide</citetitle> " |
| "in Spanish language using translation messages from <filename>trunk/" |
| "Locales/Manuals/Tcar-ug/es_ES</filename> auxiliar path and would " |
| "save final documentation output files under <filename class=" |
| "\"directory\">trunk/Manuals/Tcar-ug/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. Through path syncronization we " |
| "organize and extend the content production inside the repository." |
| msgstr "" |
| |
| msgid "" |
| "Path syncronization affects both movement of files and replacement " |
| "of content inside files. Movement of files is related to actions " |
| "like renaming files and directories inside the repository. " |
| "Replacement of content inside files is related to actions like " |
| "replacing information (e.g., paths information) inside files in " |
| "order to keep file contents and file locations consistent one " |
| "another after a file has been moved." |
| msgstr "" |
| |
| msgid "" |
| "The order followed to syncronize path information is very important " |
| "because the versioned nature of the files we are working with. When " |
| "a renaming action needs to be performed inside the repository, we " |
| "avoid making replacements inside files first and file movements " |
| "later. This would demand two commit actions: one for the files' " |
| "internal changes and another for the file movement itself. Instead, " |
| "we prefer to perform file movements first and files' internal " |
| "replacements later. This way it is possible to commit both changes " |
| "as if they were just one." |
| msgstr "" |
| |
| msgid "" |
| "There is no support for URLs actions inside <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 isn't full implementation of path " |
| "syncronization inside <command>centos-art.sh</command> script and " |
| "that is somthing we need to do oursleves. However, the " |
| "<quote>texinfo</quote> backend inside the <function>help</function> " |
| "functionality does provide a restricted implementation of path " |
| "syncronization to documentation area through the <option>--copy</" |
| "option>, <option>--delete</option> and <option>--rename</option> " |
| "options. You can read this implementation and use it as reference " |
| "to implement path syncronization in other areas." |
| msgstr "" |
| |
| msgid "" |
| "The plan for a full implementation of path syncronization inside " |
| "<command>centos-art.sh</command> script 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 can know which are all the restricted actions that " |
| "should be performed in order to make the full path syncronization." |
| msgstr "" |
| |
| msgid "" |
| "For example, if the directory we are renaming is a master path, it " |
| "is required to syncronize the related output and localization " |
| "auxiliar paths. On the other hand, if the directory we are renaming " |
| "through full path syncronization is an auxiliar path, it is " |
| "required to determine first what is the related master path and " |
| "later, perform the syncronization from master path to auxiliar " |
| "paths as if the path provided would be the master path not the " |
| "auxiliar path." |
| 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 "" |
| "To build a directory structure inside the repository you need to " |
| "define the concept behind it first. Later you need to create a new " |
| "directory inside the repository, remembering that there are " |
| "locations inside the repository that already define concepts you " |
| "probably would prefer to reuse. For example, the <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/Locales</filename> stores " |
| "translation messages, and the <filename class=\"directory\">trunk/" |
| "Scripts</filename> stores automation scripts." |
| msgstr "" |
| |
| msgid "" |
| "The best suggestion we can probably give you would be to send a " |
| "mail with your questions to the <ulink url=\"mailto:centos-" |
| "devel@centos.org\">CentOS developers mailing list</ulink> (<ulink " |
| "url=\"mailto:centos-devel@centos.org\">centos-devel@centos.org</" |
| "ulink>). This is the place where development of <ulink type=\"https" |
| "\" url=\"https://projects.centos.org/svn/artwork\">The CentOS " |
| "Artwork Repository</ulink> takes place and surely, in community, it " |
| "will be possible to find a place for your new component inside the " |
| "repository." |
| 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 from the Subversion's client " |
| "you've 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 " |
| "sending a mail to the <ulink url=\"http://lists.centos.org/mailman/" |
| "listinfo/centos-devel\">CentOS Developers mailing list</ulink> " |
| "(<ulink url=\"mailto:centos-devel@centos.org\">centos-devel@centos." |
| "org</ulink>), 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 (see <xref linkend=\"repo-convs-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=\"http\" url=\"http://www.centos." |
| "org\">The CentOS Project</ulink>. This is something you, as author, " |
| "should be aware of because you are contributing your creation's " |
| "rights to someone else; <ulink type=\"http\" url=\"http://www." |
| "centos.org\">The CentOS Project</ulink> in this case. This way, " |
| "your work is distributed using <quote><ulink type=\"http\" url=" |
| "\"http://www.centos.org\">The CentOS Project</ulink></quote> as " |
| "copyright holder, not your name (even you remain as natural author " |
| "of the work). Because <ulink type=\"http\" url=\"http://www.centos." |
| "org\">The CentOS Project</ulink> is the copyright holder, is the " |
| "license chosen by <ulink type=\"http\" url=\"http://www.centos.org" |
| "\">The CentOS Project</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 "" |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> is a community project controlled by its own " |
| "community of users. Inside the community, The CentOS Administrators " |
| "group is the higher authority and the only one able to set core " |
| "desition like the kind of license used inside the project and " |
| "subprojects like <ulink type=\"https\" url=\"https://projects." |
| "centos.org/svn/artwork\">The CentOS Artwork Repository</ulink>." |
| msgstr "" |
| |
| msgid "" |
| "The redistribution conditions of <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> are described in <xref linkend=\"repo-convs-" |
| "copying\"/>." |
| msgstr "" |
| |
| msgid "Repository Copying Conditions" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> uses <ulink type=\"https\" url=\"https://projects." |
| "centos.org/svn/artwork\">The CentOS Artwork Repository</ulink> to " |
| "produce <ulink type=\"http\" url=\"http://www.centos.org\">The " |
| "CentOS Project</ulink> corporate visual identity." |
| msgstr "" |
| |
| msgid "" |
| "The <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink> is not in the " |
| "public domain; it is copyrighted and there are restrictions on " |
| "their distribution, but these restrictions are designed to permit " |
| "everything that a good cooperating citizen would want to do. What " |
| "is not allowed is to try to prevent others from further sharing any " |
| "version of this work that they might get from you." |
| msgstr "" |
| |
| msgid "" |
| "Specifically, we want to make sure that you have the right to give " |
| "away copies of <ulink type=\"https\" url=\"https://projects.centos." |
| "org/svn/artwork\">The CentOS Artwork Repository</ulink>, 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 <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink>, 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 <ulink type=\"https\" " |
| "url=\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>. 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 <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink> is released as a " |
| "GPL work. Individual packages used by <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> include their own licenses and the <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink> license applies to all packages " |
| "that it does not clash with. If there is a clash between the <ulink " |
| "type=\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink> license and individual package " |
| "licenses, the individual package license applies instead." |
| msgstr "" |
| |
| msgid "" |
| "The precise conditions of the license for the <ulink type=\"https\" " |
| "url=\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> are found in <xref linkend=\"licenses-gpl\"/>. " |
| "This manual specifically is covered by the conditions found in " |
| "<xref linkend=\"licenses-gfdl\"/>." |
| msgstr "" |
| |
| msgid "Preparing Your Workstation" |
| msgstr "" |
| |
| msgid "Introduction" |
| 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 later download in it." |
| msgstr "" |
| |
| msgid "" |
| "This chapter describes the steps you need to follow in order to " |
| "install and configure a workstation for using a working copy of " |
| "<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 "" |
| "To install your workstation use The CentOS Distribution default " |
| "configuration as proposed by The CentOS Distribution installer. " |
| "This includes default partitioning and packages. <ulink type=\"https" |
| "\" url=\"https://projects.centos.org/svn/artwork\">The CentOS " |
| "Artwork Repository</ulink> is been completly develop upon The " |
| "CentOS Distribution and realies on such environment to achieve most " |
| "automation tasks. In order to get a reproducable environment, it is " |
| "convenient that you, too, use the same operating system that we do." |
| msgstr "" |
| |
| msgid "Supported Platforms" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> has been tested in the " |
| "following platforms:" |
| msgstr "" |
| |
| msgid "" |
| "The CentOS Distribution major release 5 update 5, for i386 and i686 " |
| "architectures." |
| msgstr "" |
| |
| msgid "" |
| "In case you be using a working copy of <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> in a different platform from those listed here, " |
| "please send a mail to <ulink url=\"mailto:centos-devel@centos.org" |
| "\">centos-devel@centos.org</ulink> notifying it. It is our " |
| "intention to make <ulink type=\"https\" url=\"https://projects." |
| "centos.org/svn/artwork\">The CentOS Artwork Repository</ulink> as " |
| "portable as possible through different major releases of The CentOS " |
| "Distribution." |
| msgstr "" |
| |
| msgid "Configuring Your Workstation" |
| msgstr "" |
| |
| msgid "" |
| "Once your workstation has been installed, it is time for you to " |
| "configure it. The configuration of your workstation consists on " |
| "defining your workplace, download a working copy from <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink> and finally, run the " |
| "<function>prepare</function> functionality of <command>centos-art." |
| "sh</command> script to install/update the software needed, render " |
| "images, create links, and anything else needed." |
| msgstr "" |
| |
| msgid "Define Your Workplace" |
| msgstr "" |
| |
| msgid "" |
| "Once you've installed the workstation and it is up and running, you " |
| "need to register the user name you'll use for working. In this task " |
| "you need to use the commands <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 " |
| "<quote>root</quote> superuser for doing so." |
| msgstr "" |
| |
| msgid "" |
| "Do not use the <quote>root</quote> username for regular tasks " |
| "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 to " |
| "your workstation." |
| msgstr "" |
| |
| msgid "" |
| "When you've registered your user name in the workstation, it " |
| "provides an identifier for you to open a user's session in the " |
| "workstation and a place to store the information you produce, as " |
| "well. This place is known as your home directory and is unique for " |
| "each user registered in the workstation. For example, if you " |
| "register the user name john in your workstation, your home " |
| "directory would be located at <filename class=\"directory\">/home/" |
| "john/</filename>." |
| msgstr "" |
| |
| msgid "" |
| "At this point it is important to define where to download the " |
| "working copy of <ulink type=\"https\" url=\"https://projects.centos." |
| "org/svn/artwork\">The CentOS Artwork Repository</ulink> inside your " |
| "home directory. This desition deserves special attention and should " |
| "be implemented carefully in order to grant a standard environment " |
| "that could be distributed. Let's see some alternatives." |
| msgstr "" |
| |
| msgid "Different absolute paths" |
| msgstr "" |
| |
| msgid "" |
| "Consider that you store your working copy under <filename class=" |
| "\"directory\">/home/john/Projects/artwork/</filename> and I store " |
| "mine under <filename class=\"directory\">/home/al/Projects/artwork/" |
| "</filename>, we'll end up refering the same files inside our " |
| "working copies through different absolute paths. This alternative " |
| "generates a contradiction when files which hold path information " |
| "inside are committed up to the central repository from different " |
| "working copies. The contradiction comes from the question: which is " |
| "the correct absolute path to use inside such files, yours or mine? " |
| "(None of them is, of course.)" |
| msgstr "" |
| |
| msgid "One unique absolute path" |
| msgstr "" |
| |
| msgid "" |
| "Another case would be that where you and I ourselves use one unique " |
| "home directory (e.g., <filename class=\"directory\">/home/centos/" |
| "Projects/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 alternative might be not so good in situations where you and I " |
| "have to share the same workstation. In such cases, it would be " |
| "required that we both share the password information of the same " |
| "system user (the <quote>centos</quote> user in our example) which, " |
| "in addition, gives access to that user's subversion client " |
| "configuration and this way provokes the whole sense of using " |
| "different subversion credentials for committing changes to be lost." |
| msgstr "" |
| |
| msgid "Different absolute paths through dynamic expansion" |
| msgstr "" |
| |
| msgid "" |
| "Most of the absolute paths we use inside the working copy are made " |
| "of two parts, one dynamic and one relative fixed. The dynamic part " |
| "is the home directory of the current user and its value can be " |
| "retrived from the <envar>$HOME</envar> environment variable. The " |
| "fixed part of the path is the one we set inside the repositroy " |
| "structure itself as a matter of organization. What we need here is " |
| "to find a way to expand variables inside files that don't support " |
| "variable expansion. This alternative had worked rather fine when we " |
| "produce produce PNG files from SVG files and XTHML from DocBook " |
| "files, but the same is not true for absolute paths inside files " |
| "that are used as in their permanent state inside the repository (e." |
| "g., CSS files and other files similar in purpose)." |
| msgstr "" |
| |
| msgid "" |
| "Different absolute paths, dynamic expansion, symbolic links, " |
| "relative links, and environment variables" |
| msgstr "" |
| |
| msgid "" |
| "With this solution it is possible to store working copies of <ulink " |
| "type=\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink> on different locations inside the " |
| "same workstation without lose relation between files. Here we use " |
| "the TCAR_WORKDIR environment variable to set the location of the " |
| "working copy inside the workstation. Later the centos-art.sh " |
| "scripts uses this value as reference to determine where the working " |
| "copy is. This value is also the one used for dynamic expansion " |
| "inside design models and other similar files. In the case of web " |
| "projects where different components are required to produce the " |
| "final content, we create symbolic links between them and use " |
| "relative paths so it is possible to reuse them and retain the " |
| "relation between them in different contexts." |
| msgstr "" |
| |
| msgid "" |
| "For example, lets consider the organization of XHTML manuals " |
| "rendered from DocBook source files. When you render a DocBook " |
| "manual inside <ulink type=\"https\" url=\"https://projects.centos." |
| "org/svn/artwork\">The CentOS Artwork Repository</ulink> it creates " |
| "XHTML files. This XHTML files use images and common style sheets " |
| "for better presentation. Both of these images and styles components " |
| "live outside the XHTML structure so, in order to make them " |
| "available relatively to the XHTML structure, we created symbolic " |
| "links from the XHTML structure to the outside location where they " |
| "are in. The creation of symbolic links takes place automatically " |
| "when each DockBook manual is rendered through <command>centos-art." |
| "sh</command>, which uses the value of TCAR_WORKDIR environment " |
| "variable as reference to determine the absolute path of the working " |
| "copy." |
| msgstr "" |
| |
| msgid "" |
| "Bacause absolute paths are no longer stored inside permanent files " |
| "and <command>centos-art.sh</command> script uses the TCAR_WORKDIR " |
| "environment variable to determine where the working copy is stored " |
| "in the workstation, it should be safe to download working copies of " |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> anywhere in the " |
| "workstation. One just have to be sure that the value of " |
| "TCAR_WORKDIR environment variable does match the location of the " |
| "working copy you are using." |
| msgstr "" |
| |
| msgid "Download Your Working Copy" |
| msgstr "" |
| |
| msgid "" |
| "In order to use <ulink type=\"https\" url=\"https://projects.centos." |
| "org/svn/artwork\">The CentOS Artwork Repository</ulink> you need to " |
| "download a working copy from the central repository into your " |
| "workstation. To download such working copy use the following " |
| "command:" |
| msgstr "" |
| |
| |
| msgid "svn co https://projects.centos.org/svn/artwork ~/" |
| msgstr "" |
| |
| msgid "" |
| "This command will create your working copy inside your home " |
| "directory, specifically in a directory named <filename class=" |
| "\"directory\">artwork</filename>. Inside this directory you will " |
| "find all the files you need to work with inside <ulink type=\"https" |
| "\" url=\"https://projects.centos.org/svn/artwork\">The CentOS " |
| "Artwork Repository</ulink>. If you want to have your working copy " |
| "in a location different to that one shown above, see <xref linkend=" |
| "\"repo-ws-config-ChangeWorkingCopy\"/>." |
| msgstr "" |
| |
| msgid "" |
| "The first time you download the working copy it contains no image " |
| "files, nor documentation, or localized content inside it. This is " |
| "because all the files provided in the working copy are source files " |
| "(e.g., the files needed to produce other files) and it is up to you " |
| "to render them in order to produce the final files (e.g., images " |
| "and documentation) used to implement <ulink type=\"http\" url=" |
| "\"http://www.centos.org\">The CentOS Project</ulink> Corporate " |
| "Visual Identity." |
| msgstr "" |
| |
| msgid "Configure Administrative Tasks" |
| msgstr "" |
| |
| msgid "" |
| "Most of the administrative tasks you need to perform in your " |
| "working copy of <ulink type=\"https\" url=\"https://projects.centos." |
| "org/svn/artwork\">The CentOS Artwork Repository</ulink> are " |
| "standardized inside the <function>prepare</function> functionality " |
| "of <command>centos-art.sh</command> script. Inside <command>centos-" |
| "art.sh</command> script, all administrative task are invoked " |
| "through the <command>sudo</command> command. Thus, in order for the " |
| "<command>centos-art.sh</command> script to perform administrative " |
| "tasks, you need to update the <command>sudo</command>'s " |
| "configuration in a way that such administrative actions be allowed." |
| msgstr "" |
| |
| msgid "" |
| "At time of this writing the <command>centos-art.sh</command> script " |
| "implements just one administrative task, that is package " |
| "management. Nevertheless, in the future, other administrative tasks " |
| "might be included as well (e.g., installing themes locally from the " |
| "working copy for testing purposes.)." |
| msgstr "" |
| |
| msgid "" |
| "To update the <command>sudo</command>'s configuration, execute the " |
| "<command>visudo</command> command as <quote>root</quote>. Later, " |
| "uncoment the <varname>Cmnd_Alias</varname> related to " |
| "<quote>SOFTWARE</quote> and add a line for your username allowing " |
| "software commands. This configuration is illustrated in <xref " |
| "linkend=\"repo-ws-config-sudoers-example\"/>." |
| msgstr "" |
| |
| msgid "The <filename>/etc/sudoers</filename> configuration file" |
| msgstr "" |
| |
| msgid "<filename>/etc/sudoers</filename> configuration file" |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "## Installation and management of software\n" |
| "Cmnd_Alias SOFTWARE = /bin/rpm, /usr/bin/up2date, /usr/bin/yum\n" |
| "\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" |
| "\n" |
| "## Allow the centos user to run installation and management of\n" |
| "## software anywhere.\n" |
| "al ALL=(ALL) SOFTWARE\n" |
| msgstr "" |
| |
| msgid "Run Preparation Tool" |
| msgstr "" |
| |
| msgid "" |
| "Once you've both downloaded a working copy from <ulink type=\"https" |
| "\" url=\"https://projects.centos.org/svn/artwork\">The CentOS " |
| "Artwork Repository</ulink> and configured the <command>sudo</" |
| "command>'s configuration file successfully, run the " |
| "<function>prepare</function> functionality of <command>centos-art." |
| "sh</command> script to complete the configuration process using the " |
| "following command:" |
| msgstr "" |
| |
| |
| msgid "~/artwork/trunk/Scripts/Bash/centos-art.sh prepare" |
| msgstr "" |
| |
| msgid "" |
| "To know more about the <function>prepare</function> functionality " |
| "of <command>centos-art.sh</command> script, see <xref linkend=" |
| "\"scripts-bash-prepare\"/>." |
| msgstr "" |
| |
| msgid "Changing Your Working Copy Default Path" |
| msgstr "" |
| |
| msgid "" |
| "By default your working copy should be store in your home " |
| "directory, specifically in the location <filename class=\"directory" |
| "\">~/artwork</filename>. This location may not be the final " |
| "location where you want to have your working copy in situations " |
| "where you are working on several projects at the same time or you " |
| "already have a define location to organize your projects inside " |
| "your home directory. Thus, you may need to change the default " |
| "location of your working copy to a more appropriate location." |
| msgstr "" |
| |
| msgid "" |
| "The default path to your working copy is controlled by the " |
| "<envar>TCAR_WORKDIR</envar> environment variable. This variable is " |
| "firstly defined in your personal profile after running the prepare " |
| "functionality of <command>centos-art.sh</command> script. So, to " |
| "change the path of your working copy correctly, do the following:" |
| msgstr "" |
| |
| msgid "" |
| "Create the parent directory you will use to store your working " |
| "copy. For example: <screen>mkdir -p ~/Projects/CentOS</screen>" |
| msgstr "" |
| |
| msgid "" |
| "Move the currently downloaded working copy from ~/artwork to your " |
| "new location. For example: <screen>mv ~/artwork ~/Projects/CentOS/</" |
| "screen>" |
| msgstr "" |
| |
| msgid "" |
| "Edit <filename>~/.bash_profile</filename> file to set the new " |
| "location (without trailing slash) of your working copy as value of " |
| "TCAR_WORKDIR environment variable. For example: " |
| "<screen>TCAR_WORKDIR=${HOME}/Projects/CentOS/artwork</screen>" |
| msgstr "" |
| |
| msgid "" |
| "Do log out from your active user's seesion and do log in again so " |
| "the environment changes take effect. Or just update the current " |
| "environment information by running the following command: <screen>. " |
| "~/.bash_profile</screen>" |
| msgstr "" |
| |
| msgid "" |
| "Update internal links by running the following command: <screen>" |
| "${TCAR_WORKDIR}/trunk/Scripts/Bash/centos-art.sh prepare --links</" |
| "screen>" |
| msgstr "" |
| |
| msgid "Repository History" |
| msgstr "" |
| |
| msgid "" |
| "This chapter summarizes relevant changes committed to <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink> along the years." |
| msgstr "" |
| |
| msgid "2008's" |
| 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 (The CentOS Distribution installer). " |
| "In such discussion, <ulink url=\"http://wiki.centos.org/" |
| "RalphAngenendt\">Ralph Angenendt</ulink> rose up his hand to ask —" |
| "Do you have something to show?—." |
| msgstr "" |
| |
| msgid "" |
| "To answer the question, <ulink url=\"http://wiki.centos.org/" |
| "AlainRegueraDelgado\">Alain Reguera Delgado</ulink> 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 "" |
| "<ulink url=\"http://wiki.centos.org/KaranbirSingh\">Karanbir Singh</" |
| "ulink> 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 made world wide available. In " |
| "this configuration, users were able to register themselves and " |
| "administrators were able to assign access rights to registered " |
| "users inside <ulink type=\"https\" url=\"https://projects.centos." |
| "org/svn/artwork\">The CentOS Artwork Repository</ulink>, both using " |
| "a web interface." |
| 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 used to produce the " |
| "Anaconda slides;<footnote><para>See <ulink url=\"https://projects." |
| "centos.org/trac/artwork/browser/trunk/Main/render.sh?rev=15\"/></" |
| "para></footnote> Ralph Angenendt documented it very well;" |
| "<footnote><para>See <ulink type=\"http\" url=\"https://projects." |
| "centos.org/trac/artwork/wiki/HowToTranslateSlides\"/></para></" |
| "footnote> and people started to download working copies of <ulink " |
| "type=\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink> to produce slide images in their " |
| "own languages.<footnote><para>See the following <ulink url=\"http://" |
| "www.google.com/search?q=anaconda+slides+site%3Alists.centos.org" |
| "\">Google search</ulink>.</para></footnote>" |
| msgstr "" |
| |
| msgid "" |
| "From this time on <ulink type=\"https\" url=\"https://projects." |
| "centos.org/svn/artwork\">The CentOS Artwork Repository</ulink> has " |
| "been evolving into an automated production environment where The " |
| "CentOS Community can conceive <ulink type=\"http\" url=\"http://www." |
| "centos.org\">The CentOS Project</ulink> corporate visual identity." |
| msgstr "" |
| |
| msgid "" |
| "The exact changes commited to <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> through history can be found in the <ulink url=\"https://" |
| "projects.centos.org/trac/artwork/timeline\">repository logs</ulink> " |
| "so you can know the real history about it. For those of you who " |
| "just want to get a glance of changes committed, see <xref linkend=" |
| "\"repo-history\"/>." |
| 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 art " |
| "work that needed to be produced. In this configuration, if you " |
| "would want to produce the same art work with a different visual " |
| "style or structure, it was needed to create a new directory " |
| "structure for it because both the image structure and the image " |
| "visual style were together in the design template." |
| msgstr "" |
| |
| msgid "" |
| "The rendition script was moved to a common place and linked from " |
| "different directory structures. There was no need to have the same " |
| "code in different directory structures if it could be in just one " |
| "place and then be linked from different locations." |
| 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 " |
| "related links</ulink>. 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>The CentOS Artwork " |
| "Repository 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 <command>centos-art</" |
| "command> command-line interface was used instead. The " |
| "<command>centos-art</command> command-line interface is a symbolic " |
| "link stored inside the <filename class=\"directory\">~/bin</" |
| "filename> directory pointing 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 <command>centos-art</" |
| "command> command-line interface, it is possible 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 separated into two different " |
| "directory structures: the design models and the artistic motifs " |
| "directory structures. From this point on, the <command>centos-art." |
| "sh</command> was able to produce themes as result of arbitrary " |
| "combinations between design models (structure) and artistic motifs " |
| "(visual styles)." |
| msgstr "" |
| |
| msgid "" |
| "In the documentation area, the documents in LaTeX format were " |
| "migrated to Texinfo format. In this configuration, each directory " |
| "structure in the repository has a documentation entry associated in " |
| "a Texinfo structure which can be read, edited and administered (e." |
| "g., renamed, deleted and copied) interactively through " |
| "<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 consolidated themselves " |
| "as the most frequent tasks performed in <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> working copy. Additionally, the " |
| "<function>prepare</function> and <function>tuneup</function> " |
| "functionalities were also maintained as useful tasks." |
| msgstr "" |
| |
| msgid "" |
| "In the documentation area, it was introduced the transformation of " |
| "localized DocBook XML DTD instances through the <function>render</" |
| "function> and <function>locale</function> functionalities. In this " |
| "configuration, you use <function>locale</function> functionality to " |
| "localize DocBook source files to your prefered language and later, " |
| "using the <function>render</function> functionality, you can " |
| "produce the localized XTHML and PDF output as specified in a XSLT " |
| "layer. Unfortunly, the transformation DocBook XML -> FO -> " |
| "PDF (through PassiveTex) seems to be buggy inside CentOS 5.5, so it " |
| "was commented inside the <command>centos-art.sh</command> script. " |
| "Most documentation is now organized in DocBook format, even Texinfo " |
| "format remains as the only format with automated production tasks." |
| msgstr "" |
| |
| msgid "" |
| "In the automation area, the <command>centos-art.sh</command> script " |
| "introduced the capability of reading configuration files. The main " |
| "goal here was moving some command-line options from functionalities " |
| "onto a more persistent medium. Most configuration files were set to " |
| "define the position of brands inside images and documentation " |
| "manual specific options." |
| msgstr "" |
| |
| msgid "2012's" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> development was eventually " |
| "stopped at November 2011 until July 2012 when we needed to make the " |
| "<command>centos-art.sh</command> script a bit more customizable " |
| "than it presently was. For example, it was considered as a need " |
| "that functionalities inside the <command>centos-art.sh</command> " |
| "script must be not just conceived independent one another but " |
| "reusable in different contexts as well." |
| msgstr "" |
| |
| msgid "" |
| "Make Localization Of <command>centos-art.sh</command> Script " |
| "Specific To Different Contexts" |
| msgstr "" |
| |
| msgid "" |
| "The procedure used to locale messages inside the <command>centos-" |
| "art.sh</command> script had to be re-designed in order to accept " |
| "such pluggable behavior into the script. We couldn't publish unique " |
| "<filename>centos-art.sh.po</filename> and <filename>centos-art.sh." |
| "mo</filename> files because they may contain different information " |
| "in different contexts. For example, if you are using the " |
| "<function>render</function> and <function>help</function> " |
| "functionalities you only need translation messages for them and not " |
| "those from other functionalities that may exist in the central " |
| "repository but you didn't download nor use into your working copy." |
| msgstr "" |
| |
| msgid "" |
| "One solution for this could be to have independent PO files for " |
| "each functionality of <command>centos-art.sh</command> script which " |
| "are combined to create the final PO and MO files that " |
| "<application>gettext</application> uses to retrive translated " |
| "strings when <command>centos-art.sh</command> script is running. " |
| "For this solution to be effective, you must be selective about the " |
| "functionalities and locales directories you download into your " |
| "working copy. For example, if you want to use the render " |
| "functionality and its locale messages only, you must download the " |
| "required directories and exclude others." |
| msgstr "" |
| |
| msgid "" |
| "In case you don't want to be selective and download the whole " |
| "repository, the creation of the <filename>centos-art.sh.po</" |
| "filename>, <filename>centos-art.sh.pot</filename> and " |
| "<filename>centos-art.sh.mo</filename> files will occur " |
| "automatically the first time you run the <function>prepare</" |
| "function> functionality (which require the <function>locale</" |
| "function> functionality to be available), or later, by running the " |
| "following command: <screen>centos-art locale trunk/Scripts/Bash --" |
| "update</screen>" |
| msgstr "" |
| |
| msgid "" |
| "For more information about the <function>prepare</function> and " |
| "<function>locale</function> functionalities, see <xref linkend=" |
| "\"scripts-bash-locale\"/> and <xref linkend=\"scripts-bash-prepare" |
| "\"/> respectively." |
| msgstr "" |
| |
| msgid "" |
| "As shown in <xref linkend=\"repository-history-2012-2\"/>, both " |
| "<function>Commons</function> and <function>Locales</function> " |
| "functionalities will always be required directories. The " |
| "<function>Commons</function> directory contains the common " |
| "functionalities and the <function>Locales</function> directory " |
| "contains the standard procedures you need to run in order to build " |
| "the final <filename>centos-art.sh.mo</filename> file used by " |
| "<application>gettext</application> to retrive translation strings " |
| "when the <command>centos-art.sh</command> script is running. " |
| "Remember that <filename>centos-art.sh.pot</filename>, " |
| "<filename>centos-art.sh.po</filename> files aren't under version " |
| "control and they are built by combining each funtionality message." |
| "po file into a PO and later a MO file." |
| msgstr "" |
| |
| msgid "Directory structure of a rendering-only context" |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "/home/centos/Projects/artwork/trunk/\n" |
| "|-- Locales/\n" |
| "| `-- Scripts/\n" |
| "| `-- Bash/\n" |
| "| `-- es_ES/\n" |
| "| |-- Functions/\n" |
| "| | |-- Commons/\n" |
| "| | | |-- messages.po\n" |
| "| | | `-- messages.pot\n" |
| "| | |-- Locales/\n" |
| "| | | |-- messages.po\n" |
| "| | | `-- messages.pot\n" |
| "| | `-- Render/\n" |
| "| | |-- messages.po\n" |
| "| | `-- messages.pot\n" |
| "| |-- LC_MESSAGES/\n" |
| "| | `-- centos-art.sh.mo\n" |
| "| |-- centos-art.sh.po\n" |
| "| `-- centos-art.sh.pot\n" |
| "`-- Scripts/\n" |
| " `-- Bash/\n" |
| " |-- Functions/\n" |
| " | |-- Commons/\n" |
| " | |-- Locales/\n" |
| " | `-- Render/\n" |
| " `-- centos-art.sh\n" |
| msgstr "" |
| |
| msgid "" |
| "A practical example of using the solution described above may be " |
| "found when you are working on the corporate identity of <ulink type=" |
| "\"http\" url=\"http://www.centos.org\">The CentOS Project</ulink> " |
| "and then need to start a new corporate identity project for another " |
| "organization. You want to keep the directory structure of <ulink " |
| "type=\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink> and its automation tool, the " |
| "<command>centos-art.sh</command> script. Your new project requires " |
| "you to introduce new functionalities to <command>centos-art.sh</" |
| "command> which don't fit the needs of <ulink type=\"http\" url=" |
| "\"http://www.centos.org\">The CentOS Project</ulink> (e.g., you " |
| "want to introduce a <function>report</function> functionality to " |
| "mesure how much connect time do you consume through your PPP " |
| "internface.) or you just want to keep the directory structure of " |
| "your new project as simple as possible." |
| msgstr "" |
| |
| msgid "" |
| "To go through this it is possible to mix specific parts of " |
| "different central repositories into one single working copy. This " |
| "is the working copy you'll use to manage your new project. In <xref " |
| "linkend=\"repository-history-2012-1\"/>, we see how the <filename " |
| "class=\"directory\">Render</filename>, <filename class=\"directory" |
| "\">Locales</filename> and <filename class=\"directory\">Commons</" |
| "filename> directories which come from the <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> has been integrated into the working copy of " |
| "your new project." |
| msgstr "" |
| |
| msgid "Mixing automation functionalities." |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "/home/al/Projects/Myapp/trunk/\n" |
| "|-- Locales/ \n" |
| "| `-- Scripts/\n" |
| "| `-- Bash/ \n" |
| "| `-- es_ES/\n" |
| "| |-- Functions/\n" |
| "| | |-- Commons/ <--| from https://projects.centos.org/svn/artwork/\n" |
| "| | | |-- messages.po\n" |
| "| | | `-- messages.pot\n" |
| "| | |-- Locales/ <--| from https://projects.centos.org/svn/artwork/\n" |
| "| | | |-- messages.po\n" |
| "| | | `-- messages.pot\n" |
| "| | |-- Render/ <--| from https://projects.centos.org/svn/artwork/\n" |
| "| | | |-- messages.po\n" |
| "| | | `-- messages.pot\n" |
| "| | `-- Report/\n" |
| "| | |-- messages.po\n" |
| "| | `-- messages.pot\n" |
| "| |-- LC_MESSAGES/\n" |
| "| | `-- myapp.sh.mo\n" |
| "| |-- myapp.sh.po\n" |
| "| `-- myapp.sh.pot\n" |
| "`-- Scripts/\n" |
| " `-- Bash/\n" |
| " |-- Functions/\n" |
| " | |-- Commons/ <--| from https://projects.centos.org/svn/artwork/\n" |
| " | |-- Locales/ <--| from https://projects.centos.org/svn/artwork/\n" |
| " | |-- Render/ <--| from https://projects.centos.org/svn/artwork/\n" |
| " | `-- Report/\n" |
| " `-- myapp.sh\n" |
| msgstr "" |
| |
| msgid "" |
| "At this point, your working copy contains files from two different " |
| "central repositories. One repository provides the files of your new " |
| "organization project and the other one provides the files related " |
| "to the <function>render</function> functionality from <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink>. In this environment, all updates " |
| "commited to the <filename class=\"directory\">Render</filename>, " |
| "<filename class=\"directory\">Locales</filename> and <filename " |
| "class=\"directory\">Commons</filename> directories at <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink> will be available to you too, the " |
| "next time you update your working copy. Likewise, if you change " |
| "something in any of these directories and commit your changes, your " |
| "changes will be available to poeple working in <ulink type=\"https" |
| "\" url=\"https://projects.centos.org/svn/artwork\">The CentOS " |
| "Artwork Repository</ulink> the next time they update their working " |
| "copies." |
| msgstr "" |
| |
| msgid "" |
| "Understanding the need of mixing different central repositories " |
| "into a single working copy is an important step for reusing the " |
| "functionalities that come with centos-art.sh script, but it is not " |
| "enough if you want to customize the information produced by it. By " |
| "default, the centos-art.sh script uses information related to " |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink>. You probably need to change this if you are " |
| "producing images to a different organization than <ulink type=\"http" |
| "\" url=\"http://www.centos.org\">The CentOS Project</ulink>. For " |
| "example, some of the information you might need to change would be " |
| "the copyright holder, brands, domain names, mailing lists, and so " |
| "forth. To change this information you need to duplicate the file " |
| "<filename>centos-art.sh</filename> and rename it to something else. " |
| "Later, you need to edit the renamed version and change variables " |
| "inside according your needs. In <xref linkend=\"repository-history-" |
| "2012-1\"/>, we used the name <command>myapp.sh</command> instead of " |
| "<command>centos-art.sh</command> so the information we set inside " |
| "it could reflect the specific needs that motivated the creation of " |
| "a new project without affecting those from <ulink type=\"http\" url=" |
| "\"http://www.centos.org\">The CentOS Project</ulink>." |
| msgstr "" |
| |
| msgid "" |
| "Most of the information you need to change in your duplicated " |
| "version of <filename>centos-art.sh</filename> file is controlled by " |
| "a set of read-only variables. You modify these variables here and " |
| "they will be available all along the script execution time. For " |
| "example, you can change the value of <varname>CLI_WRKCOPY</varname> " |
| "variable inside your duplicated version of <filename>centos-art.sh</" |
| "filename> to change the absolute path you use to store your working " |
| "copy." |
| msgstr "" |
| |
| msgid "Update DocBook Documentation Structure And Processing" |
| msgstr "" |
| |
| msgid "..." |
| msgstr "" |
| |
| msgid "Corporate Visual Identity" |
| 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 Graphic Design" |
| msgstr "" |
| |
| msgid "" |
| "The corporate design is focused on the effective presentation of " |
| "corporate messages. As corporate messages we understand all the " |
| "information emitted from the organization; and when we say " |
| "<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:" |
| msgstr "" |
| |
| msgid "" |
| "The CentOS Distribution — This visual manifestation exists to cover " |
| "all actions related to artwork production and rebranding, required " |
| "by The CentOS Distribution in order to comply with upstream's " |
| "redistribution guidelines. This visual manifestation is described " |
| "in <xref linkend=\"identity-distro\"/>." |
| msgstr "" |
| |
| msgid "" |
| "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\"/>." |
| msgstr "" |
| |
| msgid "" |
| "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\"/>." |
| 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:" |
| msgstr "" |
| |
| msgid "The CentOS Distribution" |
| msgstr "" |
| |
| msgid "" |
| "This visual manifestation communicates its existence through " |
| "software packages. There are packages that make a remarkable use of " |
| "images, packages that make a moderate use of images, and packages " |
| "that don't use images at all. This visual manifestation is focused " |
| "on providing <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>)." |
| msgstr "" |
| |
| msgid "" |
| "The Community Enterprise Operating System itself (communicates the " |
| "essense of <ulink type=\"http\" url=\"http://www.centos.org\">The " |
| "CentOS Project</ulink> existence.)." |
| msgstr "" |
| |
| msgid "" |
| "Release Schema (Lifetime) and all the stuff related (e.g., Release " |
| "Notes, Documentation, Erratas, etc.)." |
| msgstr "" |
| |
| msgid "The CentOS Web" |
| msgstr "" |
| |
| msgid "" |
| "This visual manifestation communicates its existence through web " |
| "applications. These web applications are free software and come " |
| "from different providers which distribute their work with " |
| "predefined visual styles. Frequently, these predefined visual " |
| "styles have no visual relation among themselves and introduce some " |
| "visual contraditions when they all are put together. Removing these " |
| "visual contraditions is object of work for this visual " |
| "manifestation." |
| msgstr "" |
| |
| msgid "The CentOS Chat." |
| msgstr "" |
| |
| msgid "The CentOS Mailing Lists." |
| msgstr "" |
| |
| msgid "The CentOS Forums." |
| msgstr "" |
| |
| msgid "The CentOS Wiki." |
| msgstr "" |
| |
| msgid "Special Interest Groups (SIGs)." |
| msgstr "" |
| |
| msgid "Social Events, Interviews, Conferences, etc." |
| msgstr "" |
| |
| msgid "" |
| "The extensive network of mirrors available for downloading ISO " |
| "files as well as RPMs and SRPMs used to build them up in different " |
| "architectures." |
| msgstr "" |
| |
| msgid "The CentOS Showroom" |
| msgstr "" |
| |
| msgid "" |
| "This visual manifestation communicates its existence through " |
| "production of industrial objects carrying The CentOS Brand. These " |
| "branded objects are directed to be distributed on social events and/" |
| "or shops. They provide a way of promotion and commercialization " |
| "that may help to reduce <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." |
| msgstr "" |
| |
| msgid "Stationery (e.g., Posters, Stickers, CD Lables and Sleeves)." |
| msgstr "" |
| |
| msgid "Clothes (e.g., Shirts, T-shirts, Pullovers, Caps)." |
| msgstr "" |
| |
| msgid "Installation media (e.g., CDs, DVD, Pendrives)." |
| 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 Brand is the main visual manifestaion of <ulink type=" |
| "\"http\" url=\"http://www.centos.org\">The CentOS Project</ulink>. " |
| "<ulink type=\"http\" url=\"http://www.centos.org\">The CentOS " |
| "Project</ulink> uses The CentOS Brand to connect all the visual " |
| "manifestions it is made of (e.g., GNU/Linux Distributions, Web " |
| "sites, Stationery, etc.) and, this way, provides recognition " |
| "<footnote><para> ... just as a GPG signature might do for RPM " |
| "packages. </para></footnote> among similar projects available on " |
| "the Internet. The CentOS Brand is made of a graphical component " |
| "(<xref linkend=\"identity-brand-symbol\"/>) and a typographical " |
| "component (<xref linkend=\"identity-brand-type\"/>) that, when put " |
| "together, make <xref linkend=\"identity-brand-logo\"/>. The " |
| "components that make The CentOS Brand can be used together or " |
| "separately, considering that, in hierarchy order, <xref linkend=" |
| "\"identity-brand-logo\"/> is rather prefered than <xref linkend=" |
| "\"identity-brand-symbol\"/>, as well as <xref linkend=\"identity-" |
| "brand-symbol\"/> is rather prefered than <xref linkend=\"identity-" |
| "brand-type\"/>." |
| msgstr "" |
| |
| msgid "" |
| "In addition to those components mentioned above, The CentOS Brand " |
| "includes another component named <xref linkend=\"identity-brand-" |
| "motif\"/>. <xref linkend=\"identity-brand-motif\"/> is mainly used " |
| "as background on images and is directly related to the look and " |
| "feel of all visual manifestations <ulink type=\"http\" url=\"http://" |
| "www.centos.org\">The CentOS Project</ulink> shows its existence on. " |
| "In contrast with <xref linkend=\"identity-brand-logo\"/>, <xref " |
| "linkend=\"identity-brand-symbol\"/> and <xref linkend=\"identity-" |
| "brand-type\"/>; <xref linkend=\"identity-brand-motif\"/> might " |
| "change from time to time providing a vehicle to <quote>refresh</" |
| "quote> how <ulink type=\"http\" url=\"http://www.centos.org\">The " |
| "CentOS Project</ulink> looks and feels." |
| msgstr "" |
| |
| msgid "" |
| "The CentOS Brand and all the visual manifestations derivated from " |
| "it are available for you to study and propose improvement around a " |
| "good citizen's will inside The CentOS Community, but you are not " |
| "allowed to redistribute them elsewhere, without the given " |
| "permission of <ulink type=\"http\" url=\"http://www.centos.org" |
| "\">The CentOS Project</ulink>." |
| msgstr "" |
| |
| msgid "" |
| "If you need to redistribute either <xref linkend=\"identity-brand-" |
| "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 Symbol" |
| msgstr "" |
| |
| msgid "The CentOS Type" |
| msgstr "" |
| |
| msgid "The CentOS Logo" |
| msgstr "" |
| |
| msgid "The CentOS Motif" |
| msgstr "" |
| |
| msgid "Release Schema" |
| msgstr "" |
| |
| msgid "" |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> documentation work line is " |
| "implemented through documentation manuals. Documentation manuals " |
| "are implemented through different documentation formats provided " |
| "inside The CentOS Distribution (e.g., <application>Docbook</" |
| "application>, <application>Texinfo</application>, " |
| "<application>LaTeX</application>, etc.). Structuring tasks related " |
| "to documentation systems (e.g., creating, editing, deleting, " |
| "copying, renaming, etc.) are standardized through the <code>help</" |
| "code> functionality of <command>centos-art.sh</command> script, as " |
| "described in <xref linkend=\"scripts-bash-help\"/>. This way, " |
| "people writting documentation don't need to deal with underlaying " |
| "tasks like creating files, updating menus, nodes, cross references " |
| "and wondering where to put everything in <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>." |
| msgstr "" |
| |
| msgid "Documentation Production Cycle" |
| msgstr "" |
| |
| msgid "" |
| "This chapter describes the procedure you should follow to create " |
| "and maintain documentation manuals inside <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>." |
| msgstr "" |
| |
| msgid "" |
| "This chapter describes general concepts that can be applied through " |
| "the documentation formats supported inside the <function>help</" |
| "function> functionality of <command>centos-art.sh</command> script. " |
| "To illustrate the production process related to documentation " |
| "manuals inside <ulink type=\"https\" url=\"https://projects.centos." |
| "org/svn/artwork\">The CentOS Artwork Repository</ulink>, this " |
| "chapter uses the <citetitle>The CentOS Artwork Repository File " |
| "System</citetitle> (TCAR-FS) documentation manual as example." |
| msgstr "" |
| |
| msgid "Identifying Document Goals" |
| msgstr "" |
| |
| msgid "" |
| "The first step in producing a documentation manual is to clearly " |
| "understand what you exactly need to document and why you need to do " |
| "so. The obvious answer to this question would be to describe the " |
| "basic ideas behind an implementation so it can be useful once " |
| "published. It is important that you find out the reasons you need " |
| "to do what you are doing and, also, those helping you to retain the " |
| "motivation to keep doing it in the future. Otherwise, without such " |
| "foundations, you'll surely end up leaving the effort soon enough to " |
| "make a lost cause from your initial work." |
| msgstr "" |
| |
| msgid "" |
| "Before <citetitle>The CentOS Artwork Repository File System</" |
| "citetitle> documentation manual exist, there was an emerging need " |
| "to understand what each directory inside the growing directory " |
| "layout was for, how they could be used and how they could be " |
| "connected one another. At that moment, the directory layout was " |
| "very unstable and explaining the whole idea behind it was not " |
| "possible, there were too many changing concepts floating around " |
| "which needed to be considered in the same changing way. So, to " |
| "understand what was happening, the <citetitle>The CentOS Artwork " |
| "Repository File System</citetitle> documentation manual was created." |
| msgstr "" |
| |
| msgid "" |
| "The <citetitle>The CentOS Artwork Repository File System</" |
| "citetitle> manual was conceived based on the idea of individually " |
| "documenting each directory inside the repository and, later, by " |
| "considering all directory documentations together, it would be " |
| "(hypothetically) possible to correct the whole idea through an " |
| "improvement cycle that would consolidate the final idea we try to " |
| "implement." |
| msgstr "" |
| |
| msgid "" |
| "Other documentation manuals can be based on reasons different from " |
| "those described above, however, no matter what those reasons be, it " |
| "will be helpful to make yourself a clean idea about what you are " |
| "going to document exactly before putting your hands on it." |
| msgstr "" |
| |
| msgid "Identifying Document Title" |
| msgstr "" |
| |
| msgid "" |
| "Once you've make yourself an clean idea of what the documentation " |
| "manual is for and the needs behind, it is time for you to define " |
| "the manual's title and the manual's directory name. Both manuals' " |
| "title and manual's directory name describe what the documentation " |
| "manual is about. The manual's title is used inside the " |
| "documentation while the manual's directory name is used to store " |
| "the related source files inside <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> directory structure. Generally, the manual's title is a " |
| "phrase of few words and the manual's directory name is the " |
| "abbreviation of that phrase set as manual's title." |
| msgstr "" |
| |
| msgid "" |
| "Following with our example, the manual's title chosen was " |
| "<citetitle>The CentOS Artwork Repository File System</citetitle> " |
| "and its directory name was set to <quote><filename>Tcar-fs</" |
| "filename></quote> to comply with the file name convenctions " |
| "described at <xref linkend=\"repo-convs-filenames\"/>." |
| msgstr "" |
| |
| msgid "Identifying Document Structure" |
| msgstr "" |
| |
| msgid "" |
| "Once both the manual's title and the manual's directory name have " |
| "been defined, it is time for you to plan the document structure " |
| "through which the manual's content will be organized." |
| msgstr "" |
| |
| msgid "" |
| "The document structure of documentation manuals is specific to that " |
| "documentation format used to write documentation source files. " |
| "Nevertheless, no matter what the documentation format be, the " |
| "document structure produce produced from the <function>help</" |
| "function> functionality of <command>centos-art.sh</command> script " |
| "follows and upside-down tree configuration. In this configuration, " |
| "documentation manuals can be organized through parts, chapters, " |
| "sections, and several subsection levels based in whether the chosen " |
| "documentation format supports them or not." |
| msgstr "" |
| |
| msgid "" |
| "Considering the <citetitle>The CentOS Artwork Repository File " |
| "System</citetitle> documentation manual, we already know that it " |
| "was conceived to document each directory structure <ulink type=" |
| "\"https\" url=\"https://projects.centos.org/svn/artwork\">The " |
| "CentOS Artwork Repository</ulink> is made of using Texinfo format " |
| "and the sectioning levels supported by it. At this point we phase " |
| "that <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink> has more levels " |
| "deep than sectioning commands available inside Texinfo formats. " |
| "This way it is not possible to use one sectioning command for each " |
| "directory level inside the repository directory structure we need " |
| "to document. Based on these issues, it is imperative to " |
| "reaccomodate the document structure in order to be able of " |
| "documenting every directory <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> is made of, using the sectioning levels supported by most " |
| "documentation formats inside The CentOS Distribution, no matter how " |
| "many levels deep the repository directory structure has." |
| msgstr "" |
| |
| msgid "" |
| "As consequence, <citetitle>The CentOS Artwork Repository File " |
| "System</citetitle> ended up being organized through the following " |
| "documentation structure:" |
| msgstr "" |
| |
| msgid "" |
| "Chapter 1. The <filename class=\"directory\">trunk</filename> " |
| "Directory" |
| msgstr "" |
| |
| msgid "" |
| "This chapter describes the <filename class=\"directory\">trunk</" |
| "filename> directory inside the repository and all subdirectories " |
| "inside it. The first level of directories (i.e., the <filename " |
| "class=\"directory\">trunk</filename> directory itself) is described " |
| "inside the chapter entry. Deeper directory levels are all " |
| "documented through sections and have a file for their own. It is " |
| "also possible to write subsections and subsubsections, however, " |
| "they don't have a file for their own as sections do. Subsections " |
| "and Subsubsections should be written as part of section files (i." |
| "e., when writting sections)." |
| msgstr "" |
| |
| msgid "" |
| "Chapter 2. The <filename class=\"directory\">branches</filename> " |
| "Directory" |
| msgstr "" |
| |
| msgid "" |
| "This chapter describes the <filename class=\"directory\">branches</" |
| "filename> directory and all directories inside it following the " |
| "same structure described for <filename class=\"directory\">trunk</" |
| "filename> directory above." |
| msgstr "" |
| |
| msgid "" |
| "Chapter 3. The <filename class=\"directory\">tags</filename> " |
| "Directory" |
| msgstr "" |
| |
| msgid "" |
| "This chapter describes the <filename class=\"directory\">tags</" |
| "filename> directory and all directories inside it following the " |
| "same structure described for <filename class=\"directory\">trunk</" |
| "filename> directory above." |
| msgstr "" |
| |
| msgid "Appendix A. Licenses" |
| msgstr "" |
| |
| msgid "" |
| "This appendix is confined to organize licenses mentioned in the " |
| "manual. The content of this appendix is out of documenatation " |
| "manual scope itself and is shared among all documentation manuals " |
| "written through the <function>help</function> of <command>centos-" |
| "art.sh</command> script inside <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink>." |
| msgstr "" |
| |
| msgid "Index" |
| msgstr "" |
| |
| msgid "" |
| "This chapter organizes links to those index definitions you defined " |
| "inside the documentation manual. The index information displayed by " |
| "this chapter is auto-generated each time the manual's output files " |
| "are created so this chapter is not editable." |
| msgstr "" |
| |
| msgid "" |
| "The document structure illustrated above is also considered the " |
| "default document structure used by the <function>help</function> " |
| "functionality of <command>centos-art.sh</command> script when you " |
| "produce new documentation manuals inside <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>. In contrast with document structure illustrated " |
| "above, the default document structure used by <function>help</" |
| "function> functionality doesn't include sectioning constructions " |
| "like parts, chapters, sections, subsections and the like. Such " |
| "structuring constructions should be specified by you when building " |
| "the documentation manual. The only exceptions to this restriction " |
| "are sectioning structures used to organize contents like " |
| "<quote>Index</quote> and <quote>Licenses</quote>, which are " |
| "considered inseparable components of documentation manuals stored " |
| "inside <ulink type=\"https\" url=\"https://projects.centos.org/svn/" |
| "artwork\">The CentOS Artwork Repository</ulink>." |
| msgstr "" |
| |
| msgid "Implementing Document Structure" |
| msgstr "" |
| |
| msgid "" |
| "This section describes the steps you should follow to implement " |
| "document structures like that one described in <xref linkend=" |
| "\"manuals-production-identifying-structure\"/>." |
| msgstr "" |
| |
| msgid "Creating Document Structure" |
| msgstr "" |
| |
| msgid "" |
| "To create new documentation manuals inside <ulink type=\"https\" " |
| "url=\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> you need to use the <function>help</function> " |
| "functionality of <command>centos-art.sh</command> script, as shown " |
| "in the following command:" |
| msgstr "" |
| |
| |
| msgid "centos-art help --edit \"<replaceable>manual-name</replaceable>\"" |
| msgstr "" |
| |
| msgid "" |
| "The first time you execute this command, you will be prompted to " |
| "enter manual specific information like document format, document " |
| "title, document subtitle, document author, etc. Once this " |
| "information has been collected the <function>help</function> " |
| "functionality performs some repository verifications and creates " |
| "the manual source files inside the manual's directory name you " |
| "specified as <replaceable>manual-name</replaceable>." |
| msgstr "" |
| |
| msgid "" |
| "When you create new documentation manuals, take care of the locale " |
| "information you are currently using. This information is generally " |
| "set in the <envar>LANG</envar> environment variable and is used by " |
| "the <function>help</function> functionality of <command>centos-art." |
| "sh</command> script to define the language of new documentation " |
| "manual and the document template used to build it, as well." |
| msgstr "" |
| |
| msgid "" |
| "Once the documentation structure has been created this way, the " |
| "recently created documentation manual is ready to receive new " |
| "chapters and sections as it is described in <xref linkend=\"manuals-" |
| "production-maintaining-structure\"/>." |
| msgstr "" |
| |
| msgid "Maintaining Document Structure" |
| msgstr "" |
| |
| msgid "" |
| "This section describes the steps you should follow to maintain " |
| "documentation structures like that one described in <xref linkend=" |
| "\"manuals-production-identifying-structure\"/>." |
| msgstr "" |
| |
| msgid "Editing Document Structure" |
| msgstr "" |
| |
| msgid "centos-art help --edit \"tcar-fs::trunk\"" |
| msgstr "" |
| |
| msgid "" |
| "This command creates the base structure for the <quote>trunk</" |
| "quote> chapter and opens its main definition file with your " |
| "favorite text editor so you can update the chapter introduction. " |
| "This very same procedure is used to create <quote>branches</quote> " |
| "and <quote>tags</quote> chapters, just be sure to change the " |
| "chapter field accordingly." |
| msgstr "" |
| |
| msgid "centos-art help --edit \"tcar-fs::trunk:identity\"" |
| msgstr "" |
| |
| msgid "" |
| "This command creates the <quote>identity</quote> section inside the " |
| "<quote>trunk</quote> chapter. If the chapter doesn't exist it will " |
| "be created first. In this command, the <quote>identity</quote> " |
| "section refers to <filename class=\"directory\">trunk/Identity</" |
| "filename> directory inside <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink>. In order to document other directories, follow the same " |
| "procedure but using minus signs to separate directories. For " |
| "example, to document the <quote><filename class=\"directory\">trunk/" |
| "Identity/Models/Themes</filename></quote> directory you should use " |
| "the <quote><code>tcar-fs::trunk:identity-models-themes</code></" |
| "quote> documentation entry." |
| msgstr "" |
| |
| msgid "" |
| "In the very specific case of <citetitle>TCAR-FS</citetitle> manual, " |
| "it is also possible to refer chapters and sections using a " |
| "<quote><filename class=\"directory\">path/to/dir</filename></quote> " |
| "format. For example, the reference <quote><code>tcar-fs::trunk:" |
| "identity-models-themes</code></quote> can be also specified as " |
| "<quote><filename class=\"directory\">trunk/Identity/Models/Themes</" |
| "filename></quote>, in case you feel more confortable with it than " |
| "the former one." |
| msgstr "" |
| |
| msgid "Copying Document Structure" |
| msgstr "" |
| |
| msgid "Deleting Document Structure" |
| msgstr "" |
| |
| msgid "Renaming Document Structure" |
| msgstr "" |
| |
| msgid "Updating Document Structure" |
| msgstr "" |
| |
| msgid "Documentation Formats" |
| msgstr "" |
| |
| msgid "" |
| "The CentOS Distribution provides support for different " |
| "documentation formats, including Texinfo, LaTeX, DocBook and " |
| "LinuxDoc. These formats have their own specifications and " |
| "requirements to create and maintain documentation manuals written " |
| "through them. Inside <ulink type=\"https\" url=\"https://projects." |
| "centos.org/svn/artwork\">The CentOS Artwork Repository</ulink>, the " |
| "<function>help</function> functionality of <command>centos-art.sh</" |
| "command> script provides an interface where documentation format " |
| "specifications have been already considered for you to be able of " |
| "creating and maintaining documentation manuals without needing to " |
| "take care of those underlaying structuring tasks." |
| msgstr "" |
| |
| msgid "" |
| "This chapter describes how the <function>help</function> " |
| "functionality of <command>centos-art.sh</command> script implements " |
| "the different documentation source formats available inside The " |
| "CentOS Distribution, and the internationalization issues related to " |
| "documentation manuals produced through them." |
| msgstr "" |
| |
| msgid "Texinfo" |
| msgstr "" |
| |
| msgid "" |
| "This section describes the implementation of Texinfo documentation " |
| "format inside the <function>help</function> functionality of " |
| "<command>centos-art.sh</command> script described in <xref linkend=" |
| "\"scripts-bash-help\"/>. In this section we assume you have a basic " |
| "understanding of Texinfo documentation system. Otherwise, if you " |
| "don't know what Texinfo documentation system is, read the Texinfo " |
| "manual first (e.g., by running the <command>info texinfo</command> " |
| "command) and then, come back here." |
| msgstr "" |
| |
| msgid "Document Structure" |
| msgstr "" |
| |
| msgid "" |
| "The <function>help</function> functionality of <command>centos-art." |
| "sh</command> provides a document structure that makes documentation " |
| "manuals created through it to be scalable and maintainable through " |
| "time. This document structure follows the idea of an upside-down " |
| "tree to organize chapters, sections, subsections and the like, as " |
| "described in <xref linkend=\"manuals-production-identifying-" |
| "structure\"/>." |
| msgstr "" |
| |
| msgid "" |
| "The first time you use the <function>help</function> functionality " |
| "to create a documentation manual in Texinfo format, the " |
| "<function>help</function> functionality considers the working " |
| "directory you are placed in to determine where to store the " |
| "documentation manual source files. When the current working " |
| "directory is <filename class=\"directory\">branches/Manuals/" |
| "Texinfo</filename>, the documentation manual directory is created " |
| "therein. On all other situations, the documentation manual " |
| "directory is created under <filename class=\"directory\">trunk/" |
| "Manuals</filename> directory. Once the documentation manual " |
| "directory has been created, the <function>help</function> " |
| "functionality creates the related definition files using Texinfo " |
| "documentation templates, as described in <xref linkend=\"manuals-" |
| "formats-texinfo-templates\"/>." |
| msgstr "" |
| |
| msgid "" |
| "Inside the documentation manual directory, source files are stored " |
| "inside language-specific directories. The language-specific " |
| "directories are necessary to implement internationalization of " |
| "Texinfo source files, as described in <xref linkend=\"manuals-" |
| "formats-texinfo-l10n\"/>." |
| msgstr "" |
| |
| msgid "" |
| "Inside the language-specific directory, the following files exist " |
| "to store the manual's main definitions (e.g., title, subtitle, " |
| "author, copyright notice, chapters, appendixes, indexes and all the " |
| "similar stuff a documentation manual would have). In addition to " |
| "these files, there is one directory for each chapter created inside " |
| "the manual. Inside each chapter directory, you'll found the files " |
| "controlling the section definitions related to that chapter they " |
| "belong to. The section files (a.k.a. <quote>documentation entries</" |
| "quote>) are suffixed with a <filename class=\"extension\">texinfo</" |
| "filename> extension and named arbitrarily, as it is illustrated in " |
| "<xref linkend=\"manuals-formats-texinfo-structure-example1\"/>. " |
| "Inside section files it is where you write the manual's content " |
| "itself." |
| msgstr "" |
| |
| msgid "Texinfo document structure" |
| msgstr "" |
| |
| |
| msgid "" |
| "trunk/Manuals/${MANUAL_NAME}\n" |
| "`-- ${LANG}\n" |
| " |-- ${CHAPTER_NAME}\n" |
| " | |-- chapter-menu.texinfo\n" |
| " | |-- chapter-nodes.texinfo\n" |
| " | |-- chapter.texinfo\n" |
| " | `-- ${SECTION_NAME}.texinfo\n" |
| " |-- Licenses\n" |
| " | |-- chapter-menu.texinfo\n" |
| " | |-- chapter-nodes.texinfo\n" |
| " | `-- chapter.texinfo\n" |
| " |-- ${MANUAL_NAME}.conf\n" |
| " |-- ${MANUAL_NAME}-index.texinfo\n" |
| " |-- ${MANUAL_NAME}-menu.texinfo\n" |
| " |-- ${MANUAL_NAME}-nodes.texinfo\n" |
| " `-- ${MANUAL_NAME}.texinfo" |
| msgstr "" |
| |
| msgid "" |
| "Texinfo (as in <package>texinfo-4.8-14.el5</package>) doesn't " |
| "support part sectioning inside documentation manuals, so neither " |
| "does the <function>help</function> functionality of <command>centos-" |
| "art.sh</command> script. Nevertheless, you can create several " |
| "documentation manuals and <emphasis>considered</emphasis> them as " |
| "part of a bigger documentation manual to workaround this issue." |
| msgstr "" |
| |
| msgid "" |
| "In this document structure, the creation of documentation manuals, " |
| "chapters and sections is not limitted. You can create as many " |
| "documenation manuals, chapters and sections as you need. The only " |
| "limitation would be the amount of free space required to store the " |
| "Texinfo source files and the output files produced from them." |
| msgstr "" |
| |
| msgid "Document Templates" |
| msgstr "" |
| |
| msgid "" |
| "Texinfo document templates provide the initial state the " |
| "<function>help</function> functionality of <command>centos-art.sh</" |
| "command> script needs in order to create and maintain document " |
| "structures, as that one described in <xref linkend=\"manuals-" |
| "formats-texinfo-structure\"/>." |
| msgstr "" |
| |
| msgid "" |
| "Texinfo document templates are language-specific. This means that " |
| "there is (or, at least, must be) one Texinfo document template for " |
| "each language you plan to support documentation manuals for. By " |
| "default, <ulink type=\"https\" url=\"https://projects.centos.org/" |
| "svn/artwork\">The CentOS Artwork Repository</ulink> provides a " |
| "default Texinfo document template under <filename class=\"directory" |
| "\">en_US</filename> directory. This template structure is used when " |
| "your current locale is English language or when you are creating/" |
| "editing a documentation manual in a language other than English, " |
| "but no language-specific document template for that language exists " |
| "in the directory:" |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "trunk/Scripts/Bash/Functions/Help/Texinfo/Templates" |
| msgstr "" |
| |
| msgid "" |
| "This directory organizes all Texinfo document templates using the " |
| "format LL_CC, where LL is the language code (as in ISO-639) and CC " |
| "the country code (as in ISO-3166). The directory structure of " |
| "Texinfo document templates is illustrated in the <xref linkend=" |
| "\"manuals-formats-texinfo-templates-example1\"/> and implemented " |
| "through the following files:" |
| msgstr "" |
| |
| msgid "manual.texinfo" |
| msgstr "" |
| |
| msgid "" |
| "This file can be found inside the language-specific directory and " |
| "contains the manual's main definitions (e.g., document title, " |
| "document language, document authors, copyright notice, etc.)." |
| msgstr "" |
| |
| msgid "manual-menu.texinfo" |
| msgstr "" |
| |
| msgid "" |
| "This file can be found inside the language-specific directory and " |
| "contains the menu definitions of chapters inside the manual. Menu " |
| "definitions in this file are automatically updated when a new " |
| "chapter is created or deleted through the <function>help</function> " |
| "functionality of <command>centos-art.sh</command> script. " |
| "Generally, you don't need to edit this file once the documentation " |
| "manual has been created." |
| msgstr "" |
| |
| msgid "" |
| "When a documentation manual is created for first time, this file is " |
| "copied from Texinfo document template directory structure to the " |
| "documentation manual being currently created. At this specific " |
| "moment, this file contains the following Texinfo menu definition:" |
| msgstr "" |
| |
| |
| msgid "" |
| "@menu\n" |
| "* Licenses::\n" |
| "* Index::\n" |
| "@end menu" |
| msgstr "" |
| |
| msgid "" |
| "Later, when chapters are added to or deleted from the documentation " |
| "manual, the content of this file varies adding or deleting menu " |
| "entries accordingly. Nevertheless, the two entries shown above are " |
| "ignored when new chapters are added to or removed from the list, so " |
| "they will always be present in this file. To preserve the manual " |
| "consistency, the <function>help</function> functionality prevents " |
| "you from deleting any of these chapters once the documentation " |
| "manual has been created." |
| msgstr "" |
| |
| msgid "manual-nodes.texinfo" |
| msgstr "" |
| |
| msgid "" |
| "This file can be found inside the language-specific directory and " |
| "contains the node definitions of all chapters inside the manual. " |
| "Node definitions in this file are automatically created based on " |
| "menu definitions (see <filename>manual-menu.texinfo</filename> file " |
| "above) and they don't include any content here. Instead, as part of " |
| "the node definition, the <code>@include</code> command is used to " |
| "connect each node with its content. Generally, you don't need to " |
| "edit this file once the documentation manual has been created." |
| msgstr "" |
| |
| msgid "manual-index.texinfo" |
| msgstr "" |
| |
| msgid "" |
| "This file can be found inside the language-specific directory and " |
| "contains the Texinfo commands used to generated an organized view " |
| "of all indexes you defined inside documentation entries so they can " |
| "be quickly accessed. Generally, you don't need to edit this file " |
| "once the documentation manual has been created." |
| msgstr "" |
| |
| msgid "manual.conf" |
| msgstr "" |
| |
| msgid "" |
| "This file contains the initial configuration of documentation " |
| "manuals written in Texinfo format. When a documentation manual is " |
| "created for first time, this file is copied into its target " |
| "directory so you be able of later customizing specific information " |
| "like menu order, title styles and template assignments. The content " |
| "of this file is described in <xref linkend=\"manuals-formats-" |
| "texinfo-configuration\"/>." |
| msgstr "" |
| |
| msgid "chapter.texinfo" |
| msgstr "" |
| |
| msgid "" |
| "This file contains the Texinfo's main chapter definition used by " |
| "<function>help</function> functionality when new chapters are " |
| "created inside documentation manuals. When chapters are created for " |
| "first time, they come without any introduction or documentation " |
| "entry inside. If you want to add/update any information inside the " |
| "chapter definition itself, edit the related chapter file inside the " |
| "documentation manual you are working on, not the template file used " |
| "to create it." |
| msgstr "" |
| |
| msgid "chapter-menu.texinfo" |
| msgstr "" |
| |
| msgid "" |
| "This file is part of Texinfo's main chapter definition and should " |
| "be initially empty. Later, when chapters are created for first " |
| "time, this file is copied as it is (i.e., empty) into the " |
| "documentation manual to store the Texinfo menu entries related to " |
| "all documentation entries created inside the chapter. The Texinfo " |
| "menu entries related to documentation entries are automatically " |
| "created using Texinfo source files as reference." |
| msgstr "" |
| |
| msgid "chapter-nodes.texinfo" |
| msgstr "" |
| |
| msgid "" |
| "This file is part of Texinfo's main chapter definition and contains " |
| "the node definition the <function>help</function> functionality " |
| "uses as reference to create the list of Texinfo nodes related to " |
| "all documentation entries created inside the chapter. The node " |
| "definition of documentation entries is automatically created from " |
| "the menu definition of documentation entries (see <filename>chapter-" |
| "menu.texinfo</filename> file above), once it has been updated from " |
| "Texinfo source files." |
| msgstr "" |
| |
| msgid "section.texinfo" |
| msgstr "" |
| |
| msgid "" |
| "This file contains the Texinfo section definition used by " |
| "<function>help</function> functionality when new documentation " |
| "entries are created inside the chapters of a documentation manual. " |
| "When documentation entries are created for first time, they are " |
| "created as empty documentation entries that you need to fill up " |
| "with content. Again, if you want to update the content of sections " |
| "inside the documentation manual, update the related documentation " |
| "entry inside the documentation manual, not the template file used " |
| "to create it." |
| msgstr "" |
| |
| msgid "" |
| "The creation of documentation entries inside the documentation " |
| "manual is represented by the <filename>${SECTION_NAME}.texinfo</" |
| "filename> file, as described in <xref linkend=\"manuals-formats-" |
| "texinfo-structure-example1\"/>. In this example, <code>" |
| "${SECTION_NAME}</code> is a variable string refering the file name " |
| "of documentaiton entries. The file names of documentation entries " |
| "is made of letters, numbers and the minus sign (which is generally " |
| "used to separate words)." |
| msgstr "" |
| |
| msgid "" |
| "Documentation entries are not limited inside a documentation " |
| "manual. You can create as many documentation entries as you need to " |
| "describe the content of your manual." |
| msgstr "" |
| |
| msgid "" |
| "There are other files which aren't related to manual's source " |
| "files, but to manual's output files. Such files are described below " |
| "and can be found either inside or outside the language-specific " |
| "directories so you can control common and specific output settings " |
| "through them. These files aren't copied into the directory " |
| "structure of new documentation manuals created through the " |
| "<function>help</function> functionality of <command>centos-art.sh</" |
| "command> script. Instead, they remain inside the template directory " |
| "structure so as to be reused each time the output of documentation " |
| "manuals is rendered." |
| msgstr "" |
| |
| msgid "manual-init.pl" |
| msgstr "" |
| |
| msgid "" |
| "This file can be found inside and outside language-specific " |
| "directories and contains the Texi2html initialization script. When " |
| "this file is outside the language-specific directory, it contains " |
| "common customizations to all language-specific outputs (e.g., " |
| "changing the output DTD). When this file is inside the language-" |
| "specific directory, it contains translations for that language-" |
| "specific output (e.g., special words like See, Index, Contents, " |
| "Top, etc., are localized here)." |
| msgstr "" |
| |
| msgid "manual.sed" |
| msgstr "" |
| |
| msgid "" |
| "This file can be found inside and outside language-specific " |
| "directories and contain special transformations for Texi2html " |
| "output. Again, when this file is inside language-specific " |
| "directories the transformation have are applied to that language-" |
| "specific XHTML output and when it is outside language-specific " |
| "directories the transformations are applied to all language-" |
| "specific XHTML outputs. Most transformations achived through this " |
| "file are to produce admonitions since Texinfo documentation format " |
| "(as in <package>texinfo-4.8-14.el5</package>) doesn't have an " |
| "internal command to build them." |
| msgstr "" |
| |
| msgid "Texinfo document template" |
| msgstr "" |
| |
| |
| msgid "" |
| "trunk/Scripts/Bash/Functions/Help/Texinfo/Templates\n" |
| "|-- ${LANG}\n" |
| "| |-- Chapters\n" |
| "| | |-- chapter-menu.texinfo\n" |
| "| | |-- chapter-nodes.texinfo\n" |
| "| | |-- chapter.texinfo\n" |
| "| | `-- section.texinfo\n" |
| "| |-- Licenses\n" |
| "| | |-- GFDL.texinfo\n" |
| "| | |-- GPL.texinfo\n" |
| "| | |-- chapter-menu.texinfo\n" |
| "| | |-- chapter-nodes.texinfo\n" |
| "| | `-- chapter.texinfo\n" |
| "| |-- manual-index.texinfo\n" |
| "| |-- manual-init.pl\n" |
| "| |-- manual-menu.texinfo\n" |
| "| |-- manual-nodes.texinfo\n" |
| "| |-- manual.conf\n" |
| "| |-- manual.sed\n" |
| "| `-- manual.texinfo\n" |
| "|-- manual-init.pl\n" |
| "`-- manual.sed" |
| msgstr "" |
| |
| msgid "" |
| "Inside the directory structure of Texinfo document templates, the " |
| "<filename class=\"directory\">Chapters</filename> directory " |
| "organizes chapter specific models used to create and maintain both " |
| "chapter and sections files inside manuals. On the other hand, the " |
| "<filename class=\"directory\">Licenses</filename> directory " |
| "organizes the license information linked from all manuals. Notice " |
| "the license information is not copied into documentation manuals " |
| "when they are created, but refered from this location where they " |
| "are maintained. This configuration permites that all documentation " |
| "manuals written in Texinfo format inside <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink> do use the same license information and if a " |
| "change is committed to the license files, such changes be " |
| "immediatly propagated to documentation manuals the next time their " |
| "output files be updated." |
| msgstr "" |
| |
| msgid "Document Expansions" |
| msgstr "" |
| |
| msgid "" |
| "The document expansions are special constructions used to generate " |
| "content dynamically inside Texinfo source files." |
| msgstr "" |
| |
| msgid "The <code>SeeAlso</code> Expansion" |
| msgstr "" |
| |
| msgid "" |
| "This expansion creates a list of links with section entries one " |
| "level ahead from the section entry being currently processed. In " |
| "this construction, the TYPE variable can be either <quote>itemize</" |
| "quote>, <quote>enumerate</quote> or <quote>menu</quote>. When no " |
| "TYPE variable is provided, the <quote>itemize</quote> value is " |
| "considered as default." |
| msgstr "" |
| |
| |
| msgid "" |
| "@c -- <[centos-art(SeeAlso,TYPE)\n" |
| "@c -- ]>" |
| msgstr "" |
| |
| msgid "" |
| "This expansion might result useful when you are documenting the " |
| "repository file system. For example, if you are currently editing " |
| "the documentation entry related to <filename class=\"directory" |
| "\">trunk/Identity</filename> directory and want to create a " |
| "linkable list of all documentation entries in the first level under " |
| "it, the code you'll have once the construction be expanded would " |
| "look like the following:" |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "@c -- <[centos-art(SeeAlso)\n" |
| "@itemize\n" |
| "@item @ref{Trunk Identity Brushes}\n" |
| "@item @ref{Trunk Identity Fonts}\n" |
| "@item @ref{Trunk Identity Images}\n" |
| "@item @ref{Trunk Identity Models}\n" |
| "@item @ref{Trunk Identity Palettes}\n" |
| "@item @ref{Trunk Identity Patterns}\n" |
| "@item @ref{Trunk Identity Webenv}\n" |
| "@end itemize\n" |
| "@c -- ]>\n" |
| msgstr "" |
| |
| msgid "" |
| "An interesting thing to notice here is that document expansions are " |
| "executed each time the related documentation entry is edited or " |
| "updated. Following with the example above, if the documentation " |
| "entries related to directories under <filename class=\"directory" |
| "\">trunk/Identity</filename> changes for some reason (e.g., they " |
| "are removed from documentation manual), the list generated as " |
| "result of document expansion will be updated automatically after " |
| "editing the documentation entry or updating the documentation " |
| "manual structure." |
| msgstr "" |
| |
| msgid "Document Configuration" |
| msgstr "" |
| |
| msgid "" |
| "The document configuration is stored in the <filename>" |
| "${MANUAL_NAME}.conf</filename> file, inside the documentation " |
| "manual directory structure. This file is originally copied from " |
| "<filename>manual.conf</filename> template file when the " |
| "documentation manual is created for first time. The content of " |
| "<filename>${MANUAL_NAME}.conf</filename> file is organized in " |
| "sections. Each section here is written in one line of its own and " |
| "have the form <code>[section_name]</code>. Under sections, the " |
| "configuration settings take place through <code>name=\"value\"</" |
| "code> pairs set in one line each. Notice that quotation marks " |
| "around the option_value are required. Comments are also possible " |
| "using the <code>#</code> character at the begining of lines. " |
| "Comments and empty lines (including tabs and white spaces) are " |
| "ignored. In case more than one section or option appear with the " |
| "same name inside the configuration file, the first one found will " |
| "be used. Nested section definitions are not supported." |
| msgstr "" |
| |
| |
| msgid "" |
| "[section_name]\n" |
| "# This is a comment.\n" |
| "option_name = \"option_value\"" |
| msgstr "" |
| |
| msgid "" |
| "The <filename>${MANUAL_NAME}.conf</filename> file is specific to " |
| "document templates. If you are using Texinfo document template to " |
| "create documentation manuals, then the default configuration file " |
| "for that documentation manual is taken from Texinfo document " |
| "template directory structure. However, if you are using a document " |
| "template different to Texinfo document template, the default " |
| "configuration file will be taken from the related document template " |
| "directory structure you are creating the documentation manual from." |
| msgstr "" |
| |
| msgid "The <code>[main]</code> Section" |
| msgstr "" |
| |
| msgid "" |
| "The <code>[main]</code> section organizes settings that let you " |
| "customize the way sections and menu definitions are created inside " |
| "the documentation manual. The following options are available in " |
| "this section:" |
| msgstr "" |
| |
| msgid "manual_format" |
| msgstr "" |
| |
| msgid "" |
| "This option specifies the documentation format used by manual. To " |
| "write documentation manuals in Texinfo format, the value of this " |
| "option must always be:" |
| msgstr "" |
| |
| |
| msgid "manual_format = \"texinfo\"" |
| msgstr "" |
| |
| msgid "" |
| "Once the documentation manual has been created, you must not change " |
| "the value of <option>manual_format</option> option. This will " |
| "produce an error." |
| msgstr "" |
| |
| msgid "manual_section_style" |
| msgstr "" |
| |
| msgid "" |
| "This option specifies the title style used by sections inside the " |
| "manual. Possible values to this option are `cap-each-word' to " |
| "capitalize each word in the section title, `cap-first-word' to " |
| "capitalize the first word in the section title only and `directory' " |
| "to transform each word in the section title into a directory path. " |
| "From all these options, `cap-each-word' is the one used as default." |
| msgstr "" |
| |
| |
| msgid "manual_section_style = \"cap-each-word\"" |
| msgstr "" |
| |
| msgid "manual_section_order" |
| msgstr "" |
| |
| msgid "" |
| "This option specifies the order used by sections inside the manual. " |
| "By default new sections added to the manual are put on the end to " |
| "follow the section order in which they were `created'. Other " |
| "possible values to this option are `ordered' and `reversed' to sort " |
| "the list of sections alphabetically from A-Z and Z-A, respectively." |
| msgstr "" |
| |
| |
| msgid "manual_section_order = \"created\"" |
| msgstr "" |
| |
| msgid "The <code>[templates]</code> Section" |
| msgstr "" |
| |
| msgid "" |
| "The <code>[templates]</code> section provides the assignment " |
| "relation between template files and documentation entry files " |
| "inside the manual. The template definition is set on the left side " |
| "using relative path and the documentation entry files are described " |
| "on the right side using a regular expression. The first match wins." |
| msgstr "" |
| |
| |
| msgid "Chapters/section.texinfo = \"^.+\\.texinfo$\"" |
| msgstr "" |
| |
| msgid "Document Internationalization" |
| msgstr "" |
| |
| msgid "" |
| "To produce localized documentation manuals through Texinfo " |
| "documentation format it is necessary to create one documentation " |
| "manual for each language it is desired to support documentation " |
| "for. Documentation manuals created in this configuration don't have " |
| "a direct relation among themselves except that one adopted by " |
| "people writting them to keep their content syncronized. In this " |
| "configuration translators take one documentation manual as " |
| "reference (a.k.a. the source manual) and produce several translated " |
| "manuals based on its content. To keep track of changes inside the " |
| "source manual, the underlaying version control system must be used " |
| "considering that there is no direct way to apply " |
| "<application>gettext</application><footnote><para> The " |
| "<application>gettext</application> program translates a natural " |
| "language message into the user's language, by looking up the " |
| "translation in a message catalog. For more information about the " |
| "<application>gettext</application> program, run <command>info " |
| "gettext</command>. </para></footnote> procedures to Texinfo source " |
| "files." |
| msgstr "" |
| |
| msgid "" |
| "In order to maintain localization of Texinfo source files through " |
| "<application>gettext</application> procedures, it is necessary to " |
| "convert the Texinfo source files into XML format first. This way it " |
| "would be possible to make use of <function>locale</function> and " |
| "<function>render</function> functionalities from <command>centos-" |
| "art.sh</command> script to maintain translation messages in " |
| "different languages through portable objets and producing localized " |
| "XML files based on such portable objects, respectively. Once the " |
| "localized XML file is available, it would be a matter of using an " |
| "XSLT processor (see the <command>xsltproc</command> command) to " |
| "realize the convertion from XML to a localize Texinfo (or possible " |
| "other) format. Nevertheless, this workaround fails because the " |
| "Document Type Definition (DTD) required to validate the XML file " |
| "produced from <command>makeinfo</command> (as in <package>texinfo-" |
| "4.8-14.el5</package>) is not availabe inside The CentOS " |
| "Distribution (release 5.5), nor it is the XSLT files required to " |
| "realize the transformation itself for such DTD." |
| msgstr "" |
| |
| msgid "" |
| "Another similar approach to maintain localization of Texinfo source " |
| "files through <application>gettext</application> procedures would " |
| "be to convert Texinfo source file to DocBook format; for who the " |
| "required DTD and XSLT files are available inside The CentOS " |
| "Distribution. This way, following a procedure similar to that one " |
| "describe for XML files above, it would be possible to end up having " |
| "localized DocBook files that can be used as source to produce " |
| "localized output for both online and printing media. However, the " |
| "DocBook output produced from <command>makeinfo</command> command " |
| "(as in <package>texinfo-4.8-14.el5</package>) isn't a valid DocBook " |
| "document according to DocBook DTDs available inside The CentOS " |
| "Distribution (release 5.5) thus provoking the validation and " |
| "transformation of such a malformed document to fail." |
| msgstr "" |
| |
| msgid "Document Language" |
| msgstr "" |
| |
| msgid "" |
| "The language information of those documentation manuals produced " |
| "through Texinfo documentation format is declared by Texinfo's " |
| "<code>@documentlanguage</code> command. This command receives one " |
| "argument refering the language code (as in ISO-639 standard) and " |
| "must be set inside the manual's main definition file. Generally, " |
| "there is no need to change the document language declaration once " |
| "it has been created by the <function>help</function> functionality " |
| "of <command>centos-art.sh</command> script; unless you mistakently " |
| "create the manual for a locale code different to that one you " |
| "previously pretended to do in first place, of course." |
| msgstr "" |
| |
| msgid "" |
| "The language information used in both Texinfo source files and " |
| "XHTML output produced by the <function>help</function> " |
| "functionality of <command>centos-art.sh</command> script is " |
| "determined by the user's session <envar>LANG</envar> environment " |
| "variable. This variable can be customized in the graphical login " |
| "screen before login, or once you've login by explicitly setting the " |
| "value of <envar>LANG</envar> environment variable inside the " |
| "<filename>~/.bash_profile</filename> file." |
| msgstr "" |
| |
| msgid "" |
| "To create documentation manuals in English language the " |
| "<envar>LANG</envar> environment variable must be set to <code>en_US." |
| "UTF-8</code> or something similar. Likewise, if you want to create " |
| "documentation manuals in a language other than English, be sure the " |
| "<envar>LANG</envar> environment variable is set to the appropriate " |
| "locale code.<footnote><para> The appropriate locale code to set " |
| "here can be found in the output produced by the <command>locale -a " |
| "| less</command> command. </para></footnote>" |
| msgstr "" |
| |
| msgid "" |
| "When producing output from Texinfo source files using the " |
| "<command>makeinfo</command> command (as in the <package>texinfo-4.8-" |
| "14.el5</package> package), the language information set by " |
| "<code>@documentlanguage</code> is ignored in Info and HTML output, " |
| "but cosidered by Tex program to redefine various English words used " |
| "in the PDF output (e.g., <quote>Chapter</quote>, <quote>Index</" |
| "quote>, <quote>See</quote>, and so on) based on the current " |
| "language set in." |
| msgstr "" |
| |
| msgid "Document Encoding" |
| msgstr "" |
| |
| msgid "" |
| "The encoding information of documentation manuals produced through " |
| "Texinfo documentation format is declared by Texinfo's " |
| "<code>@documentencoding</code> command and can take either <code>US-" |
| "ASCII</code>, <code>ISO-8859-1</code>, <code>ISO-8859-15</code> or " |
| "<code>ISO-8859-2</code> as argument. Nevertheless, you should be " |
| "aware that the <code>help</code> functionality of <command>centos-" |
| "art.sh</command> script doesn't declare the " |
| "<code>@documentencoding</code> inside Texinfo source files. Let's " |
| "see why." |
| msgstr "" |
| |
| msgid "" |
| "When the <code>@documentencoding</code> command is set in Texinfo " |
| "source files, the terminal encoding you use to read the Info output " |
| "produced from such files must be set to that encoding information " |
| "you provided as argument to <code>@documentencoding</code> command; " |
| "this, before using an Info reader to open the Info output file in " |
| "the terminal. Otherwise, when the terminal and the Texinfo source " |
| "files encoding definition differ one another, characters defined " |
| "through Texinfo's special way of producing floating accents won't " |
| "be displayed as expected (even when the <option>--enable-encoding</" |
| "option> is provided to <command>makeinfo</command> command). On the " |
| "other hand, when the <code>@documentencoding</code> command is not " |
| "set in Texinfo source files, it is possible to write and read " |
| "documentation manuals using the UTF-8 encoding without needing to " |
| "use Texinfo's special way of producing floating accents because the " |
| "terminal encoding would be able to interpret the characters entered " |
| "when the Texinfo source files were written in first place." |
| msgstr "" |
| |
| msgid "" |
| "When Texinfo's special way of producing floating accents isn't " |
| "used, HTML entities are not produced in XHTML output produced by " |
| "<command>texi2html</command>, nor in the HTML output produced by " |
| "<command>makeinfo</command>, nor in PDF output. In this last case, " |
| "when producing PDF output, you can realize what the floating " |
| "accents are by trying to produce an accentuated Spanish <code>i</" |
| "code> letter (e.g., <code>Ã</code>). When you do so, you'll note " |
| "that that construction puts the accentuation mark <emphasis>over</" |
| "emphasis> the <code>i</code> letter's dot, instead of removing the " |
| "<code>i</code> letter's dot and put the accentuation mark on its " |
| "place. In the case of XHTML output, however, it possible to produce " |
| "well localized XHTML output by setting" |
| msgstr "" |
| |
| |
| msgid "<meta http-equiv=\"content-type\" content=\"text/html; charset=UTF-8\" />" |
| msgstr "" |
| |
| msgid "" |
| "on the head section of each XHTML output to instruct the web " |
| "browsers what encoding to use to display the document content. Of " |
| "course, in order to display the document content correctly, the web " |
| "browser should provide support for UTF-8 encoding." |
| msgstr "" |
| |
| msgid "" |
| "These contradictions provide the reasons over which it was decided " |
| "not to set the <code>@documentencoding</code> in those Texinfo " |
| "source files produced by the <code>help</code> functionality of " |
| "<command>centos-art.sh</command> script. Now, considering them, we " |
| "can conclude that it is no viable way to localize Texinfo source " |
| "files through <application>gettext</application> procedures so one " |
| "documentation manual must be created for each language we desire to " |
| "support documentation for. In this configuration, it is difficult " |
| "the production of well localized PDF output, but it is possible to " |
| "produce well localized Info, Text, and XHTML outputs as long as no " |
| "document encoding be explicitly set inside Texinfo source files and " |
| "UTF-8 be used as default terminal character encoding." |
| msgstr "" |
| |
| msgid "DocBook" |
| msgstr "" |
| |
| msgid "" |
| "This section describes the implementation of DocBook documentation " |
| "format inside the <function>help</function> functionality of centos-" |
| "art.sh script described in <xref linkend=\"scripts-bash-help\"/>. " |
| "In this section we assume you have a basic understanding of DocBook " |
| "documentation system." |
| msgstr "" |
| |
| msgid "LaTeX" |
| msgstr "" |
| |
| msgid "" |
| "This section describes the implementation of LaTeX documentation " |
| "format inside the <function>help</function> functionality of centos-" |
| "art.sh script described in <xref linkend=\"scripts-bash-help\"/>. " |
| "In this section we assume you have a basic understanding of LaTeX " |
| "language." |
| msgstr "" |
| |
| msgid "" |
| "This part of the book describes <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink> automation work line. Through this work line programmers " |
| "provide the production standards that graphic designers, " |
| "documentalists, translators and packagers need to make their work " |
| "consistent and reusable. For this purpose, programmers develop the " |
| "<command>centos-art.sh</command> script and its functionalities. " |
| "The main purpose of this work line is standardize the interaction " |
| "of work lines in a reliable way. The automation work line takes " |
| "place in the <ulink url=\"https://projects.centos.org/svn/artwork/" |
| "trunk/Scripts\">trunk/Scripts</ulink> directory." |
| msgstr "" |
| |
| msgid "The Bash Script (<command>centos-art.sh</command>)" |
| msgstr "" |
| |
| msgid "" |
| "This chapter describes the <command>centos-art.sh</command> script, " |
| "its environments, variables, functions and command-line. The " |
| "<command>centos-art.sh</command> script is written in Bash and its " |
| "main goal is to automate frequent tasks inside <ulink type=\"https" |
| "\" url=\"https://projects.centos.org/svn/artwork\">The CentOS " |
| "Artwork Repository</ulink>. The <command>centos-art.sh</command> " |
| "script is organized by independent functions which try to do just " |
| "one thing and do it well." |
| msgstr "" |
| |
| msgid "Execution Environments" |
| msgstr "" |
| |
| msgid "" |
| "When you execute the <command>centos-art.sh</command> script in a " |
| "command-line terminal (shell), the command-line interpreter behind " |
| "it (e.g., Bash) creates a new execution environment for it. This " |
| "new execution environment inherits all the variables and functions " |
| "set in the shell environment and those exported to it through the " |
| "<filename>~/.bash_profile</filename> file, as well." |
| msgstr "" |
| |
| msgid "" |
| "The <command>centos-art.sh</command> script uses the <filename>~/." |
| "bash_profile</filename> file to implement per-user customizations. " |
| "For example, you can use this file to set the location of your " |
| "working copy through the <envar>TCAR_WORKDIR</envar> enviroment " |
| "variable. By default this variable is set to <filename class=" |
| "\"directory\">${HOME}/artwork</filename>, but you can reset to " |
| "something different to fit your needs. See <xref linkend=\"repo-ws-" |
| "config-ChangeWorkingCopy\"/>." |
| msgstr "" |
| |
| msgid "" |
| "Once the <command>centos-art.sh</command> script has been executed, " |
| "it creates different levels of execution environments inside the " |
| "one created by the script itself on the shell. This different " |
| "levels can be seen as a tree of execution environments which " |
| "inherit one another, as illustrated in <xref linkend=\"scripts-bash-" |
| "environments-1\"/>. These different levels of execution evironments " |
| "are where the <command>centos-art.sh</command> script is developed " |
| "in." |
| msgstr "" |
| |
| msgid "" |
| "This section is a reference for developers who want to know which " |
| "functions and variables are available in the first two execution " |
| "environments levels of <command>centos-art.sh</command> script and " |
| "provides links to find out information about deeper execution " |
| "environment levels." |
| msgstr "" |
| |
| msgid "Execution environments" |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "----------------------------------------------------------\n" |
| "Shell execution environment\n" |
| "----|-------------------|---------------------------------\n" |
| ". |-- TCAR_WORKDIR |-- EDITOR .\n" |
| ". |-- LANG |-- HOME .\n" |
| ". `-- centos-art.sh `-- ... .\n" |
| ". ----|------------------------------------------- .\n" |
| ". centos-art.sh script execution environment .\n" |
| ". ----|--------------------|---------------------- .\n" |
| ". . |-- CLI_NAME `-- cli() . .\n" |
| ". . |-- CLI_VERSION |-- render() . .\n" |
| ". . |-- CLI_BASEDIR | |-- svg() . .\n" |
| ". . |-- CLI_FUNCDIR | `-- docbook() . .\n" |
| ". . |-- TMPDIR |-- help() . .\n" |
| ". . `-- ... | |-- docbook() . .\n" |
| ". . | `-- texinfo() . .\n" |
| ". . |-- locale() . .\n" |
| ". . `-- ... . .\n" |
| ". ................................................ .\n" |
| "..........................................................\n" |
| msgstr "" |
| |
| msgid "Shell Execution Environment" |
| msgstr "" |
| |
| msgid "" |
| "The centos-art.sh script uses the following variables from the " |
| "shell execution environment:" |
| msgstr "" |
| |
| msgid "PATH" |
| msgstr "" |
| |
| msgid "" |
| "The <envar>PATH</envar> environment variable is specific to the " |
| "operating system and provides search paths for command execution. " |
| "By default, the centos-art.sh script links executable scripts from " |
| "the <filename class=\"directory\">~/bin</filename> directory which " |
| "is one of the locations used as search path in this variable. This " |
| "is how we create the <command>centos-art</command> command from the " |
| "<command>centos-art.sh</command> script inside your working copy." |
| msgstr "" |
| |
| msgid "EDITOR" |
| msgstr "" |
| |
| msgid "" |
| "The <envar>EDITOR</envar> environment variable is specific to the " |
| "operating system and provides the path to your default text editor. " |
| "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. 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:" |
| msgstr "" |
| |
| msgid "/usr/bin/vim" |
| msgstr "" |
| |
| msgid "/usr/bin/emacs" |
| msgstr "" |
| |
| msgid "/usr/bin/nano" |
| msgstr "" |
| |
| msgid "" |
| "If none 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 "TCAR_WORKDIR" |
| msgstr "" |
| |
| msgid "" |
| "The <envar>TCAR_WORKDIR</envar> environment variable is specific to " |
| "<command>centos-art.sh</command> script and controls the working " |
| "copy default location in the workstation. This variable doesn't " |
| "exist just after installing your workstation. In order for this " |
| "variable to be customizable you need to configure your workstation " |
| "first, as described in <xref linkend=\"repo-ws-config\"/>." |
| msgstr "" |
| |
| msgid "" |
| "By default, when this variable hadn't been set, the centos-art.sh " |
| "script assumes the <filename class=\"directory\">${HOME}/artwork</" |
| "filename> path as default location for your working copy." |
| msgstr "" |
| |
| msgid "" |
| "Besides these variables, the centos-art.sh script uses the " |
| "following environment variables which you don't need to customize " |
| "in your ~/.bash_profile file. These variables are configured when " |
| "you installed your workstation and can be changed later, using the " |
| "system configuration tools." |
| msgstr "" |
| |
| msgid "LANG" |
| msgstr "" |
| |
| msgid "" |
| "The <envar>LANG</envar> environment variable is specific to the " |
| "operating system and controls the default locale information of it. " |
| "The <command>centos-art.sh</command> script use 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 "" |
| "The <envar>LANG</envar> environment 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, or even " |
| "resetting the variable before executing the <command>centos-art.sh</" |
| "command> script." |
| msgstr "" |
| |
| msgid "" |
| "There are more variables set in a shell execution environment than " |
| "those expossed here. To know all the variables available in the " |
| "shell execution environment you can run the following command:" |
| msgstr "" |
| |
| |
| msgid "printenv" |
| msgstr "" |
| |
| msgid "Script Specific Environment" |
| msgstr "" |
| |
| msgid "" |
| "Once the centos-art.sh script has been executed from the command " |
| "line, it calls the <filename>Functions/Common/cli.sh</filename> " |
| "file. This file initializes variables and functions used along the " |
| "script execution environment. These variables and functions are " |
| "described in <xref linkend=\"scripts-bash-environments-script-vars" |
| "\"/> and <xref linkend=\"scripts-bash-environments-script-funcs\"/" |
| ">, respectively." |
| msgstr "" |
| |
| msgid "Script Specific Environment Variables" |
| msgstr "" |
| |
| msgid "" |
| "Once you run the centos-art.sh script, in addition to variables " |
| "from shell execution environment, the following variables will be " |
| "always available inside it:" |
| msgstr "" |
| |
| msgid "CLI_NAME" |
| msgstr "" |
| |
| msgid "Script Specific Environment Functions" |
| msgstr "" |
| |
| msgid "" |
| "Once you run the centos-art.sh script, in addition to variables " |
| "from shell execution environment, the following functions will be " |
| "always available inside it:" |
| msgstr "" |
| |
| msgid "" |
| "cli_checkFiles <parameter>FILE</parameter><parameter>...</parameter>" |
| msgstr "" |
| |
| msgid "" |
| "cli_printMessage <parameter>MESSAGE</parameter><parameter>TYPE</" |
| "parameter>" |
| msgstr "" |
| |
| msgid "cli_exportFunctions <parameter>PATH</parameter>" |
| msgstr "" |
| |
| msgid "Standardizing Configuration Tasks" |
| msgstr "" |
| |
| msgid "" |
| "The <function>prepare</function> functionality is the interface the " |
| "<command>centos-art.sh</command> script provides to standardize the " |
| "content production tasks inside the working copy." |
| msgstr "" |
| |
| msgid "Syntax" |
| msgstr "" |
| |
| msgid "" |
| "Assuming this is the very first time you run the <command>centos-" |
| "art</command> command, you'll find that there isn't such a command " |
| "in your workstation. This is correct because you haven't created " |
| "the symbolic link that makes it available in your execution path, " |
| "yet. In order to make the <command>centos-art</command> command " |
| "available in the execution path of your workstation, you need to " |
| "run the <command>centos-art.sh</command> script using its absolute " |
| "path first:" |
| msgstr "" |
| |
| |
| msgid "~/artwork/trunk/Scripts/Bash/centos-art.sh prepare [OPTIONS]" |
| msgstr "" |
| |
| msgid "" |
| "Later, once the <command>centos-art</command> command is available " |
| "in your execution path, there is no need for you to use any " |
| "absolute path again. From this time on, you can use the " |
| "<command>centos-art</command> command-line interface directly, as " |
| "the following example describes:" |
| msgstr "" |
| |
| |
| msgid "centos-env prepare [OPTIONS]" |
| msgstr "" |
| |
| msgid "Options" |
| msgstr "" |
| |
| msgid "" |
| "When the <command>centos-art</command> command is executed with the " |
| "<function>prepare</function> functionality, it 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 and a possitive " |
| "answer is assumed for them, just as if the <option>--answer-yes</" |
| "option> option whould have been provided." |
| msgstr "" |
| |
| msgid "--answer-yes" |
| msgstr "" |
| |
| msgid "Assume <emphasis>yes</emphasis> to all confirmation requests." |
| msgstr "" |
| |
| msgid "--packages" |
| msgstr "" |
| |
| msgid "" |
| "This option verifies packeges required by automation scripts and " |
| "installs or updates them as required. When required packages aren't " |
| "installed or need to be updated, the <command>centos-art</command> " |
| "uses the <command>sudo</command> and <command>yum</command> to " |
| "perform either installations or actualizations tasks. In both " |
| "cases, it is required that you configure the <filename>/etc/" |
| "sudoers</filename> configuration file first, as discribed in <xref " |
| "linkend=\"repo-ws-config-sudoers\"/>." |
| msgstr "" |
| |
| msgid "--locales" |
| msgstr "" |
| |
| msgid "" |
| "This option creates or updates the portable objects (PO) and " |
| "machine object (MO) used by <application>gettext</application> to " |
| "retrive translated strings related to <command>centos-art.sh</" |
| "command> script. This option calls the <function>locale</function> " |
| "functionality of centos-art.sh with the <option>--update</option> " |
| "option, as described in <xref linkend=\"scripts-bash-locale\"/>." |
| msgstr "" |
| |
| msgid "--links" |
| msgstr "" |
| |
| msgid "" |
| "This option maintains the file relation between your working copy " |
| "and configuration files inside your workstation through symbolic " |
| "links. When you provide this option, the <command>centos-art.sh</" |
| "command> script puts itself into your system's execution path " |
| "through its command line interface <command>centos-art</command> " |
| "and makes common brushes, patterns, palettes and fonts inside the " |
| "working copy, available to applications like GIMP in order for you " |
| "to make use of them without loosing version control over them." |
| msgstr "" |
| |
| msgid "" |
| "This option removes all common fonts, brushes, patterns, and " |
| "palettes currently installed in your home directory, 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> calls " |
| "the <function>render</function> functionality to create images " |
| "related to each design model available in your working copy, as " |
| "described in <xref linkend=\"scripts-bash-render\"/>." |
| 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 calls both the <function>render</function> and " |
| "<function>help</function> functionality to produce DocBook and " |
| "Texinfo manuals, respectively." |
| msgstr "" |
| |
| msgid "--see-environment" |
| msgstr "" |
| |
| msgid "" |
| "Print the name and value of some of the environment variables used " |
| "by <command>centos-art.sh</command> script as described in <xref " |
| "linkend=\"scripts-bash-environment\"/>." |
| msgstr "" |
| |
| msgid "--set-environment" |
| msgstr "" |
| |
| msgid "" |
| "Set default environment values to your personal profile " |
| "(<filename>~/.bash_profile</filename>)." |
| msgstr "" |
| |
| msgid "Description" |
| msgstr "" |
| |
| msgid "" |
| "When no option is provided to <function>prepare</function> " |
| "functionality, the <command>centos-art.sh</command> script uses the " |
| "<option>--set-environment</option>, <option>--packages</option>, " |
| "<option>--locales</option><option>--links</option>, <option>--" |
| "images</option> and <option>--manuals</option> options, in that " |
| "order, as default behaviour. Otherwise, if you provide any option, " |
| "the <command>centos-art.sh</command> script avoids its default " |
| "behaviour and executes the <function>prepare</function> " |
| "functionality as specified by the options you provided." |
| msgstr "" |
| |
| msgid "" |
| "Notice that it is possible for you to execute the " |
| "<function>prepare</function> functionality as many 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 "Function Specific Environment" |
| msgstr "" |
| |
| msgid "Authors" |
| msgstr "" |
| |
| msgid "" |
| "The following people have worked in the <function>prepare</" |
| "function> functionality:" |
| msgstr "" |
| |
| msgid "" |
| "Alain Reguera Delgado <<ulink url=\"mailto:alain.reguera@gmail." |
| "com\">alain.reguera@gmail.com</ulink>>, =COPYRIGHT_YEAR_LIST=" |
| msgstr "" |
| |
| msgid "License" |
| msgstr "" |
| |
| msgid "Copyright © =COPYRIGHT_YEAR_LIST= The CentOS Project" |
| msgstr "" |
| |
| msgid "" |
| "This program is free software; you can redistribute it and/or " |
| "modify it under the terms of the GNU General Public License as " |
| "published by the Free Software Foundation; either version 2 of the " |
| "License, or (at your option) any later version." |
| msgstr "" |
| |
| msgid "" |
| "This program is distributed in the hope that it will be useful, but " |
| "WITHOUT ANY WARRANTY; without even the implied warranty of " |
| "MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU " |
| "General Public License for more details." |
| msgstr "" |
| |
| msgid "" |
| "You should have received a copy of the GNU General Public License " |
| "along with this program; if not, write to the Free Software " |
| "Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA." |
| msgstr "" |
| |
| msgid "Standardizing Content Rendition" |
| msgstr "" |
| |
| msgid "" |
| "The <function>render</function> functionality is the interface the " |
| "<command>centos-art.sh</command> script provides to standardize the " |
| "content production tasks inside the working copy." |
| msgstr "" |
| |
| |
| msgid "centos-art render [OPTIONS] [DIRECTORY]" |
| msgstr "" |
| |
| msgid "" |
| "The <varname>DIRECTORY</varname> parameter specifies the directory " |
| "path, inside the working copy of <ulink type=\"https\" url=" |
| "\"https://projects.centos.org/svn/artwork\">The CentOS Artwork " |
| "Repository</ulink>, where the files you want to process are stored " |
| "in. This paramter can be provided more than once in order to " |
| "process more than one directory path in a single command execution. " |
| "When this parameter is not provided, the current directory path " |
| "where the command was called from is used instead." |
| msgstr "" |
| |
| msgid "" |
| "The <function>render</function> functionality accepts the following " |
| "options:" |
| msgstr "" |
| |
| msgid "" |
| "This option supresses 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 would have been provided." |
| msgstr "" |
| |
| msgid "--filter=\"REGEX\"" |
| msgstr "" |
| |
| msgid "" |
| "This option reduces the list of files to process inside " |
| "<varname>DIRECTORY</varname> using <varname>REGEX</varname> as " |
| "pattern. You can use this option to control the amount of files you " |
| "want to render. The deeper you go into the directory structure the " |
| "more specific you'll be about the files you want to render. When " |
| "you cannot go deeper into the directory structure through " |
| "<varname>DIRECTORY</varname> specification, use this option to " |
| "reduce the list of files therein." |
| msgstr "" |
| |
| msgid "--dont-commit-changes" |
| msgstr "" |
| |
| msgid "" |
| "This option supresses all commit and update actions realized over " |
| "files, before and after the action itself had took place over files " |
| "in the working copy." |
| msgstr "" |
| |
| msgid "--releasever=\"NUMBER\"" |
| msgstr "" |
| |
| msgid "" |
| "This option expands the <code>=\\RELEASE=</code>, <code>=" |
| "\\MAJOR_RELEASE=</code>, and <code>=\\MINOR_RELEASE=</code> " |
| "translation makers based on <varname>NUMBER</varname> value. Notice " |
| "that translation markers here were escaped using a backslash (<code>" |
| "\\</code>) in order to prevent their expansion. Use this option " |
| "when you need to produce release-specific contents, but no release " |
| "information can be retrived from the directory path you are " |
| "currently rendering." |
| msgstr "" |
| |
| msgid "--basearch=\"ARCH\"" |
| msgstr "" |
| |
| msgid "" |
| "This option expands the <code>=\\ARCHITECTURE=</code>, translation " |
| "makers based on <varname>ARHC</varname> value. Notice that " |
| "translation markers here were escaped using a backslash (<code>\\</" |
| "code>) in order to prevent their expansion. Use this option when " |
| "you need to produce architecture-sepecific contents but no " |
| "architecture information can be retrived from the directory path " |
| "you are currently rendering." |
| msgstr "" |
| |
| msgid "--theme-model=\"NAME\"" |
| msgstr "" |
| |
| msgid "" |
| "This option specifies the name of theme model you want to use when " |
| "producing theme artistic motifs. By default, if this option is not " |
| "provided, the <literal>Default</literal> theme model is used as " |
| "reference to produce theme artistic motifs. To know what values " |
| "does the <varname>NAME</varname> variable can have, run <command>ls " |
| "~/artwork/trunk/Identity/Models/Themes</command> command." |
| msgstr "" |
| |
| msgid "--post-rendition=\"COMMAND\"" |
| msgstr "" |
| |
| msgid "" |
| "This option lets you apply a command as post-rendition action. In " |
| "this case, the <varname>COMMAND</varname> represents the command-" |
| "line you want to execute in order to perform in-place modifications " |
| "to base-rendition output." |
| msgstr "" |
| |
| msgid "--last-rendition=\"COMMAND\"" |
| msgstr "" |
| |
| msgid "" |
| "This option lets you apply a command as last-rendition action. In " |
| "this case, the <varname>COMMAND</varname> argument represents the " |
| "command string you want to execute in order to perform in-place " |
| "modifications to base-rendition, post-rendition and directory-" |
| "specific rendition outputs." |
| msgstr "" |
| |
| msgid "" |
| "Inside the working copy of <ulink type=\"https\" url=\"https://" |
| "projects.centos.org/svn/artwork\">The CentOS Artwork Repository</" |
| "ulink>, rendition tasks take place inside renderable directories. " |
| "The rendition itself is performed through a serie of rendition " |
| "flows named base-rendition, post-rendition, last-rendition and " |
| "directory-specific rendition." |
| msgstr "" |
| |
| msgid "" |
| "Renderable directories are convenctional locations inside the " |
| "working copy where you can find source files, output files and " |
| "auxiliar files. Source files are used to produce output files. " |
| "Auxiliar files are used to modify the way output files are produced " |
| "from source files (e.g., to produce localized output). Auxiliar " |
| "files are optionals." |
| msgstr "" |
| |
| msgid "" |
| "Renderable directories are made of several directories but only the " |
| "output dirctory path is passed to <function>render</function> " |
| "functionality as <varname>DIRECTORY</varname> parameter in the " |
| "command-line. The directories related to source and auxiliar files " |
| "are automatically constructed based on a directory organization " |
| "convenction. This way, the <function>render</function> " |
| "functionality collects all the information it needs to work with." |
| msgstr "" |
| |
| msgid "" |
| "Inside the working copy, renderable directories are divided in two " |
| "categories in a way differences between them can be preserved. " |
| "These categories are named <quote>direct production</quote> and " |
| "<quote>theme production</quote>. These categories provide the file " |
| "organization convenction the <function>render</function> " |
| "functionality needs, to produce content based on rendition flows." |
| msgstr "" |
| |
| msgid "Direct Production" |
| msgstr "" |
| |
| msgid "Theme Production" |
| msgstr "" |
| |
| msgid "Base Rendition Flow" |
| msgstr "" |
| |
| msgid "Post Rendition Flow" |
| msgstr "" |
| |
| msgid "Last Rendition Flow" |
| msgstr "" |
| |
| msgid "Directory-Specific Rendition Flow" |
| msgstr "" |
| |
| msgid "" |
| "The following people have worked in the <function>render</function> " |
| "functionality:" |
| msgstr "" |
| |
| msgid "Standardizing Content Localization" |
| msgstr "" |
| |
| msgid "" |
| "The <function>locale</function> functionality is the interface the " |
| "<command>centos-art.sh</command> script provides to standardize " |
| "localization tasks inside the working copy." |
| msgstr "" |
| |
| |
| msgid "centos-art locale [OPTIONS] [DIRECTORY]" |
| msgstr "" |
| |
| msgid "" |
| "The <function>locale</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 would have been provided." |
| msgstr "" |
| |
| msgid "" |
| "Reduce the list of files to process inside <varname>DIRECTORY</" |
| "varname> using <varname>REGEX</varname> as pattern. You can use " |
| "this option to control the amount of files you want to locale. The " |
| "deeper you go into the directory structure the more specific you'll " |
| "be about the files you want to locale. When you cannot go deeper " |
| "into the directory structure through <varname>DIRECTORY</varname> " |
| "specification, use this option to reduce the list of files therein." |
| msgstr "" |
| |
| msgid "" |
| "Supress all commit and update actions realized over files, before " |
| "and after the actions themselves had took place over files in the " |
| "working copy." |
| msgstr "" |
| |
| msgid "--update" |
| msgstr "" |
| |
| msgid "" |
| "This option updates both POT and PO files related to source files. " |
| "Use this option everytime you change translatable strings inside " |
| "the source files." |
| msgstr "" |
| |
| msgid "--edit" |
| msgstr "" |
| |
| msgid "" |
| "This option edits the portable object related to source files. When " |
| "you provide this option, your default text editor is used to open " |
| "the portable object you, as translator, need to change in order to " |
| "keep source file messages consistent with their localized versions. " |
| "In the very specific case of shell scripts localization, this " |
| "option takes care of updating the machine object (MO) file the " |
| "shell script requires to displayed translation messages correctly " |
| "when it is executed." |
| msgstr "" |
| |
| msgid "--delete" |
| msgstr "" |
| |
| msgid "" |
| "This option unlocalizes source files. When you provide this option, " |
| "the localization directory related to source files is removed from " |
| "the working copy in conjunction with all portable objects and " |
| "machine objects inside it." |
| msgstr "" |
| |
| msgid "--dont-create-mo" |
| msgstr "" |
| |
| msgid "" |
| "This option suppresses machine objects creation when shell scripts " |
| "are localized." |
| msgstr "" |
| |
| msgid "" |
| "The localization process is very tied to the source files we want " |
| "to provide localized messages for. Inside the working copy of " |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink> it is possible to localize " |
| "XML-based files (e.g., SVG and Docbook) and programs written in " |
| "most popular programming languages (e.g., C, C++, C#, Shell " |
| "Scripts, Python, Java, GNU awk, PHP, etc.)." |
| msgstr "" |
| |
| msgid "" |
| "The localization process initiates by retriving translatable " |
| "strings from source files. When source files are XML-based files, " |
| "the only requisite to retrive translatable strings correctly is " |
| "that they be well-formed. Beyond that, the <command>xml2po</" |
| "command> command takes care of everything else. When source files " |
| "are Shell script files, it is necessary that you previously define " |
| "what strings inside the script are considered as translatable " |
| "strings in order for <command>xgettext</command> command to retrive " |
| "them correctly. To define translatable strings inside shell " |
| "scripts, you need to use either <command>gettext</command>, " |
| "<command>ngettext</command>, <command>eval_gettext</command> or " |
| "<command>eval_ngettext</command> command as it is following " |
| "described:" |
| msgstr "" |
| |
| msgid "" |
| "Use the <command>gettext</command> command to display the native " |
| "language translation of a textual message." |
| msgstr "" |
| |
| |
| msgid "MESSAGE=\"`gettext \"There is no entry to create.\"`\"" |
| msgstr "" |
| |
| msgid "" |
| "Use the <command>ngettext</command> command to display the native " |
| "language translation of a textual message whose grammatical form " |
| "depends on a number." |
| msgstr "" |
| |
| |
| msgid "" |
| "MESSAGE=\"`ngettext \"The following entry will be created\" \\\n" |
| " \"The following entries will be created\" \\\n" |
| " $COUNT`:\"" |
| msgstr "" |
| |
| msgid "" |
| "Use the <command>eval_gettext</command> command to display the " |
| "native language translation of a textual message, performing dollar-" |
| "substitution on the result. Note that only shell variables " |
| "mentioned in the message will be dollar-substituted in the result." |
| msgstr "" |
| |
| |
| msgid "MESSAGE=\"`eval_gettext \"The location \\\\\\\"\\\\\\$LOCATION\\\\\\\" is not valid.\"`\"" |
| msgstr "" |
| |
| msgid "" |
| "Use the <command>eval_ngettext</command> command to display the " |
| "native language translation of a textual message whose grammatical " |
| "form depends on a number, performing dollar-substitution on the " |
| "result. Note that only shell variables mentioned in messages will " |
| "be dollar-substituted in the result." |
| msgstr "" |
| |
| |
| msgid "" |
| "MESSAGE=\"`eval_ngettext \"The following entry will be created in \\\\\\$LOCATION\" \\\n" |
| " \"The following entries will be created in \\\\\\$LOCATION\" \\\n" |
| " $COUNT`:\"" |
| msgstr "" |
| |
| msgid "" |
| "Once translatable strings are retrived, a portable object template " |
| "(POT) file is created for storing them. Later, the POT file is used " |
| "to create a portable object (PO). The portable object is the place " |
| "where localization itself takes place, it is the file translators " |
| "edit to localize messages. When translatable strings change inside " |
| "source files, it is necessary that you update these POT and PO " |
| "files in order to keep consistency between source file messages and " |
| "their localized versions." |
| msgstr "" |
| |
| msgid "" |
| "Inside source files, translatable strings are always written in " |
| "English language. In order to localize translatable strings from " |
| "English language to another language, you need to be sure the " |
| "<envar>LANG</envar> environment variable has been already set to " |
| "the locale code you want to localize message for or see them " |
| "printed out before running the <function>locale</function> " |
| "functionality of <command>centos-art.sh</command> script. " |
| "Localizing English language to itself is not supported." |
| msgstr "" |
| |
| msgid "" |
| "To have a list of all locale codes you can have localized messages " |
| "for, run the following command: <command>locale -a | less</command>." |
| msgstr "" |
| |
| msgid "" |
| "The following people have worked in the <function>locale</function> " |
| "functionality:" |
| msgstr "" |
| |
| msgid "Standardizing Documentation Tasks" |
| msgstr "" |
| |
| msgid "" |
| "The <function>help</function> functionality is the interface the " |
| "<command>centos-art.sh</command> script provides to standardize " |
| "frequent documentation tasks, based on specific documentation " |
| "formats, as described in <xref linkend=\"manuals-formats\"/>." |
| msgstr "" |
| |
| |
| msgid "centos-art help [OPTIONS] [DOCENTRY]" |
| msgstr "" |
| |
| msgid "" |
| "The <varname>DOCENTRY</varname> parameter specifies the " |
| "documentation entry you want to process. It can be provided one or " |
| "more times in the form <code>MANUAL:PART:CHAPTER:SECTION</code> or " |
| "<code>MANUAL::CHAPTER:SECTION</code> based on whether the manual " |
| "documentation backend you are using supports structuring through " |
| "parts or not. When <varname>DOCENTRY</varname> parameter is not " |
| "provided, <quote><ulink type=\"https\" url=\"https://projects." |
| "centos.org/svn/artwork\">The CentOS Artwork Repository</ulink> " |
| "Repository File System</quote> documentation manual is used as " |
| "default value." |
| msgstr "" |
| |
| msgid "" |
| "To determine the documentation format to use, when new " |
| "documentation manuals are created and no configuration file is " |
| "available, the <function>help</function> functionality request you " |
| "to enter one of the supported documentation formats and then, uses " |
| "it to create the documentation manual. Once the documentation " |
| "manual is created, the document configuration file is available " |
| "inside the manual directory structure and used to retrive the " |
| "document format information, instead." |
| msgstr "" |
| |
| msgid "" |
| "The <function>help</function> functionality accepts the following " |
| "options:" |
| msgstr "" |
| |
| msgid "" |
| "Supress all commit and update actions realized over files, before " |
| "and after the action itself had took place over files in the " |
| "working copy." |
| msgstr "" |
| |
| msgid "--search=\"KEYWORD\"" |
| msgstr "" |
| |
| msgid "" |
| "This option looks for <varname>KEYWORD</varname> inside the manual " |
| "specified in the documentation entry and display related " |
| "information you to read." |
| msgstr "" |
| |
| msgid "" |
| "Edit documentation entry related to path specified by " |
| "<varname>DOCENTRY</varname> parameter." |
| msgstr "" |
| |
| msgid "" |
| "The <varname>DOCENTRY</varname> parameter must point to any " |
| "directory inside the working copy. When more than one " |
| "<varname>DOCENTRY</varname> 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 <varname>DOCENTRY</varname> " |
| "path. This option is used internally by <command>centos-art.sh</" |
| "command> script to refer documentation based on errors, so you can " |
| "know more about them and the causes that could have provoked them." |
| msgstr "" |
| |
| msgid "" |
| "Update output files rexporting them from the specified backend " |
| "source files." |
| msgstr "" |
| |
| msgid "--copy" |
| msgstr "" |
| |
| msgid "Duplicate documentation entries inside the working copy." |
| msgstr "" |
| |
| msgid "" |
| "When documentation entries are copied, it is required to pass two " |
| "non-option parameters in the command-line. The first non-option " |
| "parameter is considered the source location and the second one the " |
| "target location. Both source location and target location must " |
| "point to a directory under the working copy." |
| msgstr "" |
| |
| msgid "" |
| "Delete documentation entries specified by <varname>DOCENTRY</" |
| "varname> inside the working copy. It is possible to delete more " |
| "than one documentation entry by specifying more <varname>DOCENTRY</" |
| "varname> 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 consistent state." |
| msgstr "" |
| |
| msgid "" |
| "The following people have worked in the <function>help</function> " |
| "functionality:" |
| msgstr "" |
| |
| msgid "Standardizing Packaging Tasks" |
| msgstr "" |
| |
| msgid "Standardizing File Maintainance" |
| msgstr "" |
| |
| msgid "" |
| "The <function>tuneup</function> functionality is the interface the " |
| "<command>centos-art.sh</command> script provides to standardize the " |
| "maintainance tasks related to individual files inside the working " |
| "copy." |
| msgstr "" |
| |
| |
| msgid "centos-art tuneup [OPTIONS] [DIRECTORY]" |
| msgstr "" |
| |
| msgid "" |
| "The <function>tuneup</function> functionality accepts the following " |
| "options:" |
| msgstr "" |
| |
| msgid "" |
| "Reduce the list of files to process inside <replaceable>path/to/" |
| "dir</replaceable> using <replaceable>REGEX</replaceable> as " |
| "pattern. You can use this option to control the amount of files you " |
| "want to tuneup. The deeper you go into the directory structure the " |
| "more specific you'll be about the files you want to tuneup. When " |
| "you cannot go deeper into the directory structure through " |
| "<replaceable>path/to/dir</replaceable> specification, use this " |
| "option to reduce the list of files therein." |
| msgstr "" |
| |
| msgid "" |
| "Tasks related to file maintainance are repetitive. You might find " |
| "yourself doing them time after time inside the working copy of " |
| "<ulink type=\"https\" url=\"https://projects.centos.org/svn/artwork" |
| "\">The CentOS Artwork Repository</ulink>. Some of these " |
| "maintainance tasks do update top comments on shell scripts, create " |
| "table of contents for web pages, update metadata related to design " |
| "models and remove unused definitions from design models." |
| msgstr "" |
| |
| msgid "" |
| "When you execute the tuneup functionality of centos-art.sh script, " |
| "it looks for all files that match the supported extensions (e.g., " |
| "<filename class=\"extension\">.sh</filename>, <filename class=" |
| "\"extension\">.svg</filename> and <filename class=\"extension\">." |
| "xhtml</filename>) in the directory specified, builds a list with " |
| "them and applies the maintainance tasks using file extensions as " |
| "reference." |
| msgstr "" |
| |
| msgid "" |
| "When shell scripts are found, the <function>tuneup</function> " |
| "functionality of centos-art.sh script reads a comment template from " |
| "<filename>trunk/Scripts/Functions/Tuneup/Shell/Config/topcomment." |
| "sed</filename> and applies it to all shell scripts found, one by " |
| "one. As result, all shell scripts will end up having the same " |
| "copyright and license information the comment template does." |
| msgstr "" |
| |
| msgid "" |
| "In order for the shell script top comment template to be applied " |
| "correctly, the shell scripts you write must have the structure " |
| "described in <xref linkend=\"scripts-bash-tuneup-fig1\"/>." |
| msgstr "" |
| |
| msgid "Shell script top-comment template." |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| " 1| #!/bin/bash\n" |
| " 2| #\n" |
| " 3| # doSomething.sh -- The function description goes here.\n" |
| " 4| # \n" |
| " 5| # Copyright\n" |
| " 6| #\n" |
| " 7| # ...\n" |
| " 8| #\n" |
| " 9| # ----------------------------------------------------------------------\n" |
| "10| # $Id$\n" |
| "11| # ----------------------------------------------------------------------\n" |
| "12|\n" |
| "13| function doSomething {\n" |
| "14| \n" |
| "15| }\n" |
| msgstr "" |
| |
| msgid "" |
| "The <function>tuneup</function> functionality of <command>centos-" |
| "art.sh</command> script replaces all lines between the " |
| "<literal>Copyright</literal> line (e.g., line 5) and the first " |
| "separator line (e.g., line 9), inclusively. Everything else will " |
| "remain immutable in the file." |
| msgstr "" |
| |
| msgid "" |
| "When scalable vector graphics are found, the tuneup functionality " |
| "reads a SVG metadata template from <filename>trunk/Scripts/" |
| "Functions/Tuneup/Svg/Config/metadata.sed</filename> and applies it " |
| "to all files found, one by one. Immediatly after the metadata " |
| "template has been applied and, before passing to next file, all " |
| "unused definition are removed from the file, too." |
| msgstr "" |
| |
| msgid "" |
| "The metadata applied by the SVG metadata template is created " |
| "dynamicaly combining the absolute path of the file being currently " |
| "modified, the workstation's date information, the <command>centos-" |
| "art.sh</command> script copyright holder (e.g., =COPYRIGHT_HOLDER=) " |
| "as reference and the Creative Common Distribution-ShareAlike 3.0 " |
| "License as default license to release SVG files." |
| msgstr "" |
| |
| msgid "" |
| "The elimination of unused definitions inside SVG files takes place " |
| "through Inkscape's <option>--vacuum-defs</option> option, as " |
| "described in its man page (e.g., <command>man inkscape</command>)." |
| msgstr "" |
| |
| msgid "" |
| "When HTML files are found, the <function>tuneup</function> " |
| "functionality of <command>centos-art.sh</command> script transforms " |
| "web page headings to make them accessible through a table of " |
| "contents. The table of contents is expanded in place, wherever the " |
| "<code><div class=\"toc\"></div></code> piece of code be " |
| "in the file. Once the table of contents has been expanded, there is " |
| "no need to put anything else in the page. You can run the " |
| "<function>tuneup</function> functionality everytime you update the " |
| "heading information so as to update the table of contents, too." |
| msgstr "" |
| |
| msgid "" |
| "In order for this functionality to build the table of contents from " |
| "headings, you need to put headings in just one line. The headin " |
| "level can vary from <code>h1</code> to <code>h6</code> with " |
| "attribute definitions accepted. Closing tag must be present and " |
| "also match the openning tag. Inside the heading definition an " |
| "anchor definition must be present with attribute definitions " |
| "accepted. The value of <property>name</property> and " |
| "<property>href</property> attributes from the anchor element are " |
| "set dynamically using the md5sum output of combining the page " |
| "location, the <literal>head-</literal> string and the heading " |
| "content itself. If any of the components used to build the heading " |
| "reference changes, you need to run the the tuneup functionality of " |
| "<command>centos-art.sh</command> script in order for the anchor " |
| "elements to use the correct information." |
| msgstr "" |
| |
| msgid "" |
| "For example, the headings shown in <xref linkend=\"scripts-bash-" |
| "tuneup-fig2\"/> produces the table of contents shown in <xref " |
| "linkend=\"scripts-bash-tuneup-fig3\"/>." |
| msgstr "" |
| |
| msgid "HTML heading definition." |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "<h1 class=\"title\"><a name=\"head-8a23b56a28dfa7277d176576f217054a\">Forms</a></h1>\n" |
| "<h2 class=\"title\"><a name=\"head-629f38bc607f2a270177106b450aeae3\">Elements</a></h2>\n" |
| "<h2 class=\"title\"><a name=\"head-f49cae1d73592c984bbb0bffb1d5699a\">Recommendations</a></h2>\n" |
| msgstr "" |
| |
| msgid "HTML table of contents definition." |
| msgstr "" |
| |
| |
| msgid "" |
| "\n" |
| "<div class=\"toc\"> <p>Table of contents</p> <dl><dt><a href=\"#head-8a23b56a28dfa7277d176576f217054a\">Forms</a> <dl><dt><a href=\"#head-629f38bc607f2a270177106b450aeae3\">Elements</a> </dt><dt><a href=\"#head-f49cae1d73592c984bbb0bffb1d5699a\">Recommendations</a> </dt></dl> </dt></dl> </div>\n" |
| msgstr "" |
| |
| msgid "" |
| "The following people have worked in the <function>tuneup</function> " |
| "functionality:" |
| msgstr "" |
| |
| msgid "Licencias" |
| 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:" |
| msgstr "" |
| |
| msgid "copyright the software, and" |
| msgstr "" |
| |
| msgid "" |
| "offer you this license which gives you legal permission to copy, " |
| "distribute and/or modify the software." |
| 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." |
| msgstr "" |
| |
| msgid "Exception" |
| msgstr "" |
| |
| msgid "" |
| "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." |
| 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:" |
| msgstr "" |
| |
| msgid "" |
| "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," |
| msgstr "" |
| |
| msgid "" |
| "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," |
| msgstr "" |
| |
| msgid "" |
| "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.)" |
| 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 " <one line to give the program's name and a brief idea of what it does.> Copyright (C) 19yy <name of author> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. " |
| 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 " Gnomovision version 69, Copyright (C) 19yy name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. " |
| 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 " Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. <signature of Ty Coon>, 1 April 1989 Ty Coon, President of Vice " |
| 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\"/>:" |
| msgstr "" |
| |
| msgid "" |
| "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." |
| msgstr "" |
| |
| msgid "" |
| "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." |
| msgstr "" |
| |
| msgid "" |
| "State on the <xref linkend=\"title-page\"/> the name of the " |
| "publisher of the <xref linkend=\"modified-version\"/>, as the " |
| "publisher." |
| msgstr "" |
| |
| msgid "Preserve all the copyright notices of the Document." |
| msgstr "" |
| |
| msgid "" |
| "Add an appropriate copyright notice for your modifications adjacent " |
| "to the other copyright notices." |
| msgstr "" |
| |
| msgid "" |
| "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." |
| msgstr "" |
| |
| msgid "" |
| "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." |
| msgstr "" |
| |
| msgid "Include an unaltered copy of this License." |
| msgstr "" |
| |
| msgid "" |
| "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." |
| msgstr "" |
| |
| msgid "" |
| "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." |
| msgstr "" |
| |
| msgid "" |
| "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." |
| msgstr "" |
| |
| msgid "" |
| "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." |
| msgstr "" |
| |
| msgid "" |
| "Delete any section Entitled <quote>Endorsements</quote>. Such a " |
| "section may not be included in the <xref linkend=\"modified-version" |
| "\"/>." |
| msgstr "" |
| |
| msgid "" |
| "Do not retitle any existing section to be Entitled " |
| "<quote>Endorsements</quote> or to conflict in title with any <xref " |
| "linkend=\"invariant-sections\"/>." |
| msgstr "" |
| |
| msgid "Preserve any Warranty Disclaimers." |
| 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 " Copyright (C) YEAR YOUR NAME. 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 <quote>GNU Free Documentation License</quote>. " |
| 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 " with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. " |
| 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 "" |