| msgid "" |
| msgstr "" |
| "Project-Id-Version: centos-art (es_ES)\n" |
| "Report-Msgid-Bugs-To: CentOS Documentation SIG <centos-docs@centos.org>\n" |
| "POT-Creation-Date: 2011-05-17 23:24-0400\n" |
| "PO-Revision-Date: 2011-05-17 14:34-0400\n" |
| "Last-Translator: CentOS Documentation SIG <centos-docs@centos.org>\n" |
| "Language-Team: Español\n" |
| "MIME-Version: 1.0\n" |
| "Content-Type: text/plain; charset=UTF-8\n" |
| "Content-Transfer-Encoding: 8bit\n" |
| "Plural-Forms: nplurals=2; plural=(n != 1);\n" |
| |
| |
| |
| msgid "[<a href=\"#SEC_Top\" title=\"Cover (top) of document\">Top</a>]" |
| msgstr "" |
| "[<a href=\"#SEC_Top\" title=\"Cubierta del documento (superior) \">Inicio</" |
| "a>]" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_toc.xhtml#SEC_Contents\" title=\"Table of contents" |
| "\">Contents</a>]" |
| msgstr "" |
| "[<a href=\"repository_toc.xhtml#SEC_Contents\" title=\"Tabla de contenidos" |
| "\">Contenidos</a>]" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "[<a href=\"repository_58.xhtml#SEC350\" title=\"Index\">Index</a>]" |
| msgstr "[<a href=\"repository_58.xhtml#SEC350\" title=\"Índice\">Índice</a>]" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_abt.xhtml#SEC_About\" title=\"About (help)\"> ? </a>]" |
| msgstr "" |
| "[<a href=\"repository_abt.xhtml#SEC_About\" title=\"Acerca de ... (ayuda)" |
| "\"> ? </a>]" |
| |
| |
| msgid "CentOS Artwork Repository" |
| msgstr "Repositorio Artístico de CentOS" |
| |
| |
| msgid "" |
| "This manuals documents relevant information regarding the deployment, " |
| "organization, and administration of CentOS Artwork Repository." |
| msgstr "" |
| "Este manual documenta información relevante acerca del desarrollo, " |
| "organización y administración del repositorio de los trabajos artísticos de " |
| "CentOS." |
| |
| |
| msgid "Copyright © 2009, 2010, 2011 The CentOS Project" |
| msgstr "" |
| |
| |
| msgid "" |
| "Permission is granted to copy, distribute and/or modify this document under " |
| "the terms of the GNU Free Documentation License, Version 1.2 or any later " |
| "version published by the Free Software Foundation; with no Invariant " |
| "Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the " |
| "license is included in the section entitled GNU Free Documentation License." |
| msgstr "" |
| "Se autoriza la copia, distribución y/o modificación de este documento bajo " |
| "los términos de la GNU Free Documentation License en su versión 1.2 o " |
| "cualquier versión publicada posteriormente por la Fundación de Software " |
| "Libre; con ninguna Sección invariante, ningún texto en la cubierta frontal o " |
| "trasera del documento. Una copia de la licensia ha sido incluida en la " |
| "sección titulada GNU Free Documentation License." |
| |
| |
| |
| |
| |
| msgid "1. Introduction" |
| msgstr "1. Introducción" |
| |
| |
| |
| |
| |
| msgid "2. The Repository Directories" |
| msgstr "2. Los directorios del repositorio" |
| |
| |
| |
| |
| |
| msgid "3. Licenses" |
| msgstr "3. Licencias" |
| |
| |
| |
| |
| |
| msgid "Index" |
| msgstr "Índice" |
| |
| |
| |
| |
| msgid "List of Figures" |
| msgstr "Lista de figuras" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "This document was generated on <i>May, 17 2011</i> using <a class=\"www\" " |
| "href=\"http://texi2html.cvshome.org/\"><i>texi2html 1.76</i></a>." |
| msgstr "" |
| "Este documento fue generado el <i>17 de Mayo del 2011</i> usando <a class=" |
| "\"www\" href=\"http://texi2html.cvshome.org/\"><i>texi2html 1.76</i></a>" |
| |
| |
| msgid "CentOS Artwork Repository: CentOS Artwork Repository" |
| msgstr "Repositorio Artístico de CentOS: Repositorio Artístico de CentOS" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository.xhtml#SEC_Top\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| "[<a href=\"repository.xhtml#SEC_Top\" title=\"Sección prévia en orden de " |
| "lectura\"> < </a>]" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_2.xhtml#SEC2\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| "[<a href=\"repository_2.xhtml#SEC2\" title=\"Sección siguiente en orden de " |
| "lectura\"> > </a>]" |
| |
| |
| |
| |
| msgid "[ << ]" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "[<a href=\"repository.xhtml#SEC_Top\" title=\"Up section\"> Up </a>]" |
| msgstr "" |
| "[<a href=\"repository.xhtml#SEC_Top\" title=\"Sección superior\"> Arriba </" |
| "a>]" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_8.xhtml#SEC31\" title=\"Next chapter\"> >> </a>]" |
| msgstr "" |
| "[<a href=\"repository_8.xhtml#SEC31\" title=\"Capítulo siguiente\"> >> " |
| "</a>]" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository.xhtml#SEC_Top\" title=\"Cover (top) of document\">Top</" |
| "a>]" |
| msgstr "" |
| "[<a href=\"repository.xhtml#SEC_Top\" title=\"Cubierta (inicio) del " |
| "documento \">Inicio</a>]" |
| |
| |
| msgid "Welcome to CentOS Artwork Repository Manual." |
| msgstr "" |
| "Bienvenidos al manual del repositorio de los trabajos artísticos de CentOS." |
| |
| |
| msgid "" |
| "The CentOS Artwork Repository Manual describes how The CentOS Project " |
| "Corporate Visual Identity is organized and produced inside the CentOS " |
| "Artwork Repository (<a class=\"www\" href=\"https://projects.centos.org/svn/" |
| "artwork/\">https://projects.centos.org/svn/artwork/</a>). If you are looking " |
| "for a comprehensive, task-oriented guide for understanding how The CentOS " |
| "Project Corporate Visual Identity is produced, this is the manual for you." |
| msgstr "" |
| "El manual del repositorio artístico de CentOS describe cómo la identidad " |
| "visual corporativa del proyecto CentOS es organizada y producida en el " |
| "repositorio artístico de CentOS (<a class=\"www\" href=\"https://projects." |
| "centos.org/svn/artwork/\">https://projects.centos.org/svn/artwork/</a>). Si " |
| "usted está buscando una guía abarcadora y orientada a tareas para comprender " |
| "cómo la identidad visual corporativa del proyecto CentOS es producida, " |
| "entonces este manual es para usted." |
| |
| |
| msgid "This manual discusses the following intermedite topics:" |
| msgstr "Este manual trata los temas intermedios siguientes:" |
| |
| |
| msgid "The CentOS Brand" |
| msgstr "La marca de CentOS" |
| |
| |
| msgid "The CentOS Corporate Visual Structure" |
| msgstr "La estructura visual corporativa de CentOS" |
| |
| |
| msgid "The CentOS Corporate Visual Style" |
| msgstr "El estilo visual de la identidad corporativa de CentOS" |
| |
| |
| msgid "" |
| "This guide assumes you have a basic understanding of your CentOS system. If " |
| "you need help with CentOS, refer to the help page on the CentOS Wiki (<a " |
| "class=\"www\" href=\"http://wiki.centos.org/Help\">http://wiki.centos.org/" |
| "Help</a>) for a list of different places you can find help." |
| msgstr "" |
| "Esta guía asume que usted tiene conocimientos básicos de su sistema CentOS. " |
| "Si usted necesita ayuda con CentOS, explore la página de ayuda de la wiki de " |
| "CentOS (<a class=\"www\" href=\"http://wiki.centos.org/es/Help\">http://wiki." |
| "centos.org/es/Help</a>) para una lista de los diferentes lugares donde usted " |
| "puede encontrar ayuda." |
| |
| |
| |
| |
| |
| msgid "1.1 History" |
| msgstr "1.1 Historia" |
| |
| |
| |
| |
| |
| msgid "1.2 Authors" |
| msgstr "1.2 Autores" |
| |
| |
| msgid "CentOS Artwork Repository: 1. Introduction" |
| msgstr "Repositorio Artístico de CentOS: 1. Introducción." |
| |
| |
| |
| |
| |
| msgid "1.3 Copying Conditions" |
| msgstr "1.3 Condiciones de distribución" |
| |
| |
| |
| |
| |
| msgid "1.4 Document Convenctions" |
| msgstr "1.4 Convenciones del documento" |
| |
| |
| |
| |
| |
| msgid "1.5 Repository Convenctions" |
| msgstr "1.5 Convenciones del repositorio" |
| |
| |
| |
| |
| |
| msgid "1.6 Send in Your Feedback" |
| msgstr "1.6 Envíe sus sugerencias" |
| |
| |
| |
| msgid "translator-credits" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_9.xhtml#SEC32\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| "[<a href=\"repository_9.xhtml#SEC32\" title=\"Sección prévia en orden de " |
| "lectura\"> < </a>]" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_11.xhtml#SEC42\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| "[<a href=\"repository_11.xhtml#SEC42\" title=\"Sección siguiente en order de " |
| "lectura\"> > </a>]" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_8.xhtml#SEC31\" title=\"Beginning of this chapter or " |
| "previous chapter\"> << </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "[<a href=\"repository_8.xhtml#SEC31\" title=\"Up section\"> Up </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_55.xhtml#SEC332\" title=\"Next chapter\"> >> </" |
| "a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.2 The <tt>`tags'</tt> Directory" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "Goals" |
| msgstr "" |
| |
| |
| msgid "" |
| "This directory implements the Subversion's tags concept in a trunk, " |
| "branches, tags repository structure." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "Description" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`tags/'</tt> directory structure provides frozen branches. " |
| "Generally, we use frozen branches to make check-points in time for " |
| "development lines under <tt>`branches/'</tt> or <tt>`trunk/'</tt> directory " |
| "structure." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "Usage" |
| msgstr "" |
| |
| |
| msgid "The <tt>`tags/'</tt> directory structure is unused, so far." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "See also" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "<a href=\"repository_9.xhtml#SEC32\">The <tt>`branches'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "<a href=\"repository_11.xhtml#SEC42\">The <tt>`trunk'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| msgid "" |
| "The subversion book (<a class=\"www\" href=\"http://svnbook.red-bean.com/" |
| "\">http://svnbook.red-bean.com/</a>)." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.2 The tags Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_10.xhtml#SEC37\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_12.xhtml#SEC47\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "2.3 The <tt>`trunk'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/'</tt> directory structure implements the Subversion's trunk " |
| "concept in a trunk, branches, tags repository structure." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/'</tt> directory structure provides the main development line " |
| "inside the CentOS Artwork Repository." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "See section <a href=\"repository_12.xhtml#SEC47\">The <tt>`trunk/Identity'</" |
| "tt> Directory</a>." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_44.xhtml#SEC231\">The <tt>`trunk/Manual'</" |
| "tt> Directory</a>." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_43.xhtml#SEC226\">The <tt>`trunk/Locales'</" |
| "tt> Directory</a>." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_48.xhtml#SEC253\">The <tt>`trunk/Scripts'</" |
| "tt> Directory</a>." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.3 The trunk Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "<a href=\"repository_10.xhtml#SEC37\">The <tt>`tags'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "The Subversion book (<a class=\"www\" href=\"http://svnbook.red-bean.com/" |
| "\">http://svnbook.red-bean.com/</a>)." |
| msgstr "" |
| |
| |
| |
| msgid "The CentOS Distribution" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Distribution visual manifestation exists to cover all actions " |
| "related to artwork production and rebranding required by the The CentOS " |
| "Distribution (-- <strong>Removed</strong>(pxref:Directories trunk Identity " |
| "Images Themes Models Default Distro) --) in order to comply with its " |
| "upstream redistribution guidelines." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Distribution is made of software packages. Inside the " |
| "distribution there are packages that make a remarkable use of images and " |
| "there are packages that don't use images at all. The CentOS Distribution " |
| "visual manifestation gets focused on software packages that do use images in " |
| "a remarkable way (e.g., <tt>`anaconda'</tt>, <tt>`grub'</tt>, " |
| "<tt>`syslinux'</tt>, <tt>`gdm'</tt>, <tt>`kdm'</tt>) and that way, through " |
| "images, implements the corporate design in The CentOS Distribution (i.e., " |
| "the operating system)." |
| msgstr "" |
| |
| |
| msgid "The CentOS Web" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Web visual manifestation exists to support The CentOS " |
| "Distribution." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Web covers web applications which let The CentOS Project to " |
| "manifest its existence on the Internet. Through these web applications The " |
| "CentOS Project provides Corporate Communication. 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. These visual contraditions " |
| "need to be removed in order to comply with The CentOS Project Corporate " |
| "Structure guidelines." |
| msgstr "" |
| |
| |
| msgid "The CentOS Showroom" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Showroom visual manifestation exists to promote The CentOS " |
| "Distribution." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Showroom covers industrial production of objects branded by The " |
| "CentOS Project (e.g., clothes, stationery and installation media). These " |
| "branded objects are for distribution on social events and/or shops. They " |
| "provide a way of promotion and a route for commercialization that may help " |
| "to aliviate The CentOS Project expenses (e.g., electrical power, hosting, " |
| "servers, full-time-developers, etc.), in a similar way as donations may do." |
| msgstr "" |
| |
| |
| msgid "" |
| "The visual manifestations above seem to cover all the media required by The " |
| "CentOS Project, as organization, to show its existence. However, other " |
| "visual manifestations could be added in the future, if needed, to cover " |
| "different areas like building, offices, road transportation and whaterver " |
| "visual manifestation The CentOS Project thouches to show its existence." |
| msgstr "" |
| |
| |
| msgid "Corporate Communication" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Project Corporate Communication is based on <em>Community " |
| "Communication</em> and takes place through the following avenues:" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Chat (<code>#centos</code>, <code>#centos-social</code>, " |
| "<code>#centos-devel</code> on irc.freenode.net)" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Mailing Lists (<a class=\"www\" href=\"http://lists.centos.org/" |
| "\">http://lists.centos.org/</a>)." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Forums (<a class=\"www\" href=\"http://forums.centos.org/" |
| "\">http://forums.centos.org/</a>)." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Wiki (<a class=\"www\" href=\"http://wiki.centos.org/\">http://" |
| "wiki.centos.org/</a>)." |
| msgstr "" |
| |
| |
| msgid "Social events, interviews, conferences, etc." |
| msgstr "" |
| |
| |
| msgid "Corporate Behaviour" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Project Corporate Behaviour is based on <em>Community Behaviour</" |
| "em> which take place on <em>Corporate Communication</em>." |
| msgstr "" |
| |
| |
| msgid "Corporate Structure" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Project Corporate Structure is based on a <em>Monolithic " |
| "Corporate Visual Identity Structure</em>. In this configuration, one unique " |
| "name and one unique visual style is used in all visual manifestation of The " |
| "CentOS Project." |
| 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: <em>Hey! we are " |
| "all part of The CentOS Project</em>." |
| msgstr "" |
| |
| |
| msgid "" |
| "Other corporate structures for The CentOS Project 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 The CentOS Project is made of." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Project, as organization, is mainly made of (but not limited to) " |
| "three visual manifestions: Distribution, Web and Showroom. Inside the " |
| "Distribution visual manifestations, The CentOS Project maintains near to " |
| "four different major releases of 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 created for no release-specific at all, but for The " |
| "CentOS Project in general." |
| msgstr "" |
| |
| |
| msgid "" |
| "In order to produce the correct corporate structure for The CentOS Project " |
| "we need to concider all the visual manifestations The CentOS Project is made " |
| "of, not just one of them. If one different visual style is used for each " |
| "major release of The CentOS Distribution, which one of those different " |
| "visual styles would be used to cover the remaining visual manifestations The " |
| "CentOS Project is made of (e.g., The CentOS Web and The CentOS Showroom)?" |
| msgstr "" |
| |
| |
| msgid "" |
| "Probably you are thinking, that's right, 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 The CentOS Project 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. Said that, we consider that The CentOS Project " |
| "Corporate 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 would be stronger if " |
| "one unique visual style backups it. In fact, whatever thing you do to " |
| "strength the visual connection among The CentOS Project visual " |
| "manifestations would be very good in favor of The CentOS Project 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 The CentOS Project is " |
| "made of, in a way The CentOS Project 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 the CentOS Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Identity'</tt> directory structure organizes most files used " |
| "to build and implement The CentOS Project Corporate Identity. In that sake, " |
| "the following work lines are available:" |
| msgstr "" |
| |
| |
| msgid "Brushes" |
| msgstr "" |
| |
| |
| msgid "" |
| "This work line provides brushes for GIMP. When you prepare the repository, " |
| "brushes in this location are made available immediatly for you to use in the " |
| "\"Brushes\" panel of GIMP." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_13.xhtml#SEC57\">The <tt>`trunk/Identity/" |
| "Brushes'</tt> Directory</a>, for more information." |
| msgstr "" |
| |
| |
| msgid "Fonts" |
| msgstr "" |
| |
| |
| msgid "" |
| "This work line provides the typography information required by all different " |
| "visual manifestations of The CentOS Project. When you prepare the " |
| "repository, fonts in this location are made available immediatly for you to " |
| "use in GIMP and Inkscape." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_14.xhtml#SEC64\">The <tt>`trunk/Identity/" |
| "Fonts'</tt> Directory</a>, for more information." |
| msgstr "" |
| |
| |
| msgid "Images" |
| msgstr "" |
| |
| |
| msgid "" |
| "This work line provides output location for final images that don't need to " |
| "use background images (e.g., brands, icons, illustrations, etc.)." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_15.xhtml#SEC69\">The <tt>`trunk/Identity/" |
| "Images'</tt> Directory</a>, for more information." |
| msgstr "" |
| |
| |
| msgid "Models" |
| msgstr "" |
| |
| |
| msgid "" |
| "This work line provides design models for final images that don't need to " |
| "use background images (e.g., brands, icons, illustrations, etc.)." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_22.xhtml#SEC107\">The <tt>`trunk/Identity/" |
| "Models'</tt> Directory</a>, for more information." |
| msgstr "" |
| |
| |
| msgid "Palettes" |
| msgstr "" |
| |
| |
| msgid "" |
| "This work line provides palettes of colors for GIMP and Inkscape. When you " |
| "prepare the repository, palettes of colors in this location are made " |
| "available immediatly for you to use in the \"Palettes\" panel of GIMP and " |
| "Inkscape." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_40.xhtml#SEC201\">The <tt>`trunk/Identity/" |
| "Palettes'</tt> Directory</a>, for more information." |
| msgstr "" |
| |
| |
| msgid "Patterns" |
| msgstr "" |
| |
| |
| msgid "" |
| "This work line provides patterns for GIMP. When you prepare the repository, " |
| "patterns in this location are made available immediatly for you to use in " |
| "the \"Patterns\" panel of GIMP." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_41.xhtml#SEC206\">The <tt>`trunk/Identity/" |
| "Patterns'</tt> Directory</a>, for more information." |
| msgstr "" |
| |
| |
| msgid "Themes" |
| msgstr "" |
| |
| |
| msgid "" |
| "This work line provides theme design models and theme artistic motifs for " |
| "The CentOS Project. If you are interested in creating brand new visual " |
| "styles for The CentOS Project this is the place for you." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_16.xhtml#SEC74\">The <tt>`trunk/Identity/" |
| "Images/Themes'</tt> Directory</a>, for more information." |
| msgstr "" |
| |
| |
| msgid "Webenv" |
| msgstr "" |
| |
| |
| msgid "" |
| "This work line provides the HTML/XHTML and CSS standard definitions used by " |
| "The CentOS Web visual manifestation. If you are a web developer and plan to " |
| "improve The CentOS Web visual manifestation, then the files in this location " |
| "may result very useful to you." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_42.xhtml#SEC211\">The <tt>`trunk/Identity/" |
| "Webenv'</tt> Directory</a>, for more information." |
| msgstr "" |
| |
| |
| msgid "" |
| "See <a class=\"www\" href=\"http://en.wikipedia.org/Corporate_identity" |
| "\">http://en.wikipedia.org/Corporate_identity</a> (and related links), for " |
| "general information on Corporate Identity." |
| msgstr "" |
| |
| |
| msgid "" |
| "Specially useful has been, and still is, the book <em>Corporate Identity</" |
| "em> by Wally Olins (1989). This book provides many of the conceptual ideas " |
| "we've used as base to build The CentOS Artwork Repository." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_11.xhtml#SEC42\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_13.xhtml#SEC57\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "2.4 The <tt>`trunk/Identity'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Identity'</tt> describes what The CentOS Project Corporate " |
| "Identity is and the components it is made of." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Project Corporate Identity is the \"persona\" 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 <em>Corporate Design</em>, <em>Corporate Communication</em>, and " |
| "<em>Corporate Behaviour</em>." |
| msgstr "" |
| |
| |
| msgid "Corporate Mission" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.4 The trunk/Identity Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Project exists to provide The CentOS Distribution. Additionally, " |
| "The CentOS Project provides The CentOS Web and The CentOS Showroom to " |
| "support and promote the existence of The CentOS Distribution, respectively." |
| msgstr "" |
| |
| |
| msgid "Corporate Design" |
| msgstr "" |
| |
| |
| msgid "" |
| "Corporate design is focused on the effective communication of corporate " |
| "visual messages. Corporate visual messages are all the information emitted " |
| "by a corporation that can be perceived by the people through their visual " |
| "sence (i.e., the human eye). In order for such visual communication to " |
| "happen, it is required to put the visual message on medium available for " |
| "people to see. These kind of media are know as corporate visual " |
| "manifestations, since the corporate manifests its existence through them " |
| "using corporate design." |
| msgstr "" |
| |
| |
| msgid "" |
| "The amount of visual manifestations a corporation uses to communicate its " |
| "existence is very specific to each corporation itself. Inside The CentOS " |
| "Project Corporate Identity, considering <em>The CentOS Project Corporate " |
| "Structure</em>, <em>The CentOS Project Corporate Mission</em> and <em>The " |
| "CentOS Project Release Schema</em>, the following visual manifestations were " |
| "defined:" |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside the repository, common brushes and theme-specific brushes are created " |
| "individually in different locations, but they all are linked from one unique " |
| "location (i.e., <tt>`~/.gimp-2.2/brushes'</tt>). This configuration may " |
| "provoke brush overlapping if a name convenction is not implemented " |
| "correctly. In that sake, file names used for brushes inside the repository " |
| "must be unique, no matter where they be." |
| msgstr "" |
| |
| |
| msgid "" |
| "As file name convenction inside the repository, brushes are named using " |
| "lowercase letters, numbers, minus characters and dot characters, only. " |
| "Additionally, when links are built, we use one suffix for those brushes " |
| "retrived from <tt>`trunk/Identity/Brushes'</tt> and another suffix for those " |
| "brushes retrivided from theme-specific directories. Using both the brush " |
| "file name and the suffix information, it is possible to build unique names " |
| "for links under <tt>`~/.gimp-2.2/brushes'</tt> directory, scalably." |
| msgstr "" |
| |
| |
| msgid "" |
| "trunk/Identity/Brushes |-- 1.gbr (file) <-- ~/.gimp-2.2/brushes/centos-1." |
| "gbr (link) |-- 2.gbr (file) <-- ~/.gimp-2.2/brushes/centos-2.gbr (link) " |
| "`-- 3.gbr (file) <-- ~/.gimp-2.2/brushes/centos-3.gbr (link)" |
| msgstr "" |
| |
| |
| msgid "" |
| "trunk/Identity/Images/Themes/THEMENAME/THEMEVERSION/Brushes |-- 1.gbr (file) " |
| "<-- ~/.gimp-2.2/brushes/centos-THEMENAME-THEMEVERSION-1.gbr (link) |-- 2." |
| "gbr (file) <-- ~/.gimp-2.2/brushes/centos-THEMENAME-THEMEVERSION-2.gbr " |
| "(link) `-- 3.gbr (file) <-- ~/.gimp-2.2/brushes/centos-THEMENAME-" |
| "THEMEVERSION-3.gbr (link)" |
| msgstr "" |
| |
| |
| msgid "" |
| "Brushes produced with GIMP has a description field associated that is shown " |
| "in the Brushes panel of GIMP. This description is set when the brush is " |
| "created as <tt>`.xcf'</tt> file and can be updated when it is exported " |
| "either to <tt>`.gbr'</tt> or <tt>`.gih'</tt> format. It wouldn't be too " |
| "useful to have two or more brushes using the same description so, we also " |
| "make description of brush files unique, too. In that sake, we use the same " |
| "name schema used to name brush links as description but without including " |
| "the file extension (e.g., if we have the <tt>`centos-flame-3.gbr'</tt> " |
| "brush, its description would be <code>centos-flame-3</code>)." |
| msgstr "" |
| |
| |
| msgid "" |
| "The way you use brushes is up to your creativeness. However, the way brushes " |
| "are made available needs to be standardized. That's the reason of organizing " |
| "brushes in common brushes and theme-specific brushes." |
| msgstr "" |
| |
| |
| msgid "Common brushes" |
| msgstr "" |
| |
| |
| msgid "" |
| "Common brushes exist to organize brushes that can be used anywhere inside " |
| "the repository. Inside the repository, common brushes under <tt>`trunk/" |
| "Identity/Brushes'</tt> are mainly used to hold brand information related to " |
| "The CentOS Project (e.g., symbols, logos, trademarks, etc.)." |
| msgstr "" |
| |
| |
| msgid "" |
| "Common brushes are always made available under <tt>`~/.gimp-2.2/brushes'</" |
| "tt> directory after preparing the repository (see section <a href=" |
| "\"repository_52.xhtml#SEC292\">The <tt>`trunk/Scripts/Functions/Prepare'</" |
| "tt> Directory</a>)." |
| msgstr "" |
| |
| |
| msgid "Theme-specific brushes" |
| msgstr "" |
| |
| |
| msgid "" |
| "Theme-specific brushes exist to organize brushes that can be used inside " |
| "specific artistic motifs only. Inside the repository, theme-specific brushes " |
| "are stored in a directory named <tt>`Brushes'</tt> which is stored in the " |
| "first directory level under the artistic motif directory structure. Each " |
| "artistic motif inside the repository has its own <tt>`Brushes'</tt> " |
| "directory and uses it to store brushes that can be considered auxiliars to " |
| "that artistic motif construction." |
| msgstr "" |
| |
| |
| msgid "" |
| "Theme-specific brushes aren't made available under <tt>`~/.gimp-2.2/" |
| "brushes'</tt> directory after preparing the repository. In order to make " |
| "theme-specific brushes available under <tt>`~/.gimp-2.2./brushes'</tt> it is " |
| "required to activate/deactivate them using the <code>theme</code> " |
| "functionality of <code>centos-art.sh</code> script." |
| msgstr "" |
| |
| |
| msgid "" |
| "<a href=\"file:///usr/share/gimp/2.0/help/en/index.html\">The Gimp Manual</" |
| "a>, specifically the section related to <a href=\"file:///usr/share/gimp/2.0/" |
| "help/en/gimp-concepts-brushes.html\">Brushes</a>." |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "The <tt>`trunk/Identity'</tt> Directory" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "The <tt>`trunk'</tt> Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_12.xhtml#SEC47\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_14.xhtml#SEC64\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.5 The <tt>`trunk/Identity/Brushes'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "This section describes how brushes are organized in the repository and how " |
| "to make them available for you to use in <acronym title=\"GNU Image " |
| "Manipulation Program\">GIMP</acronym> (GNU Image Manipulation Program)." |
| msgstr "" |
| |
| |
| msgid "" |
| "A brush is a pixmap or set of pixmaps used for painting through an image " |
| "manipulation program like GIMP. Inside the repository, we've organized " |
| "brushes in <em>common brushes</em> and <em>theme-specific brushes</em>. In " |
| "both cases, brushes are initially created in <tt>`.xcf'</tt> format and " |
| "later exported to any of the brush formats recognized by GIMP (e.g., <tt>`." |
| "gbr'</tt> or <tt>`.gih'</tt>) using the same name of its source file." |
| msgstr "" |
| |
| |
| msgid "" |
| "1. Common brushes 2. Theme-specific brushes ---------------------- " |
| "----------------------------------------------------------- trunk/Identity/" |
| "Brushes trunk/Identity/Images/Themes/THEMENAME/THEMEVERSION/Brushes |-- Xcf " |
| "|-- Xcf | |-- 1.xcf | |-- 1.xcf | |-- 2.xcf | |-- 2.xcf | `-- 3.xcf | `-- 3." |
| "xcf |-- 1.gbr |-- 1.gbr |-- 2.gih |-- 2.gih `-- 3.gbr `-- 3.gbr" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.5 The trunk/Identity/Brushes Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "In order for both common brushes and theme-specific brushes to be loaded by " |
| "GIMP, related <tt>`.gbr'</tt> and <tt>`.gih'</tt> brush files need to be " |
| "stored under <tt>`~/.gimp-2.2/brushes'</tt> directory. This location is out " |
| "of CentOS Artwork Repository and provides no version control by itself. This " |
| "way, brushes aren't exported to this location but into the repository " |
| "directory structure which is versioned. Later, we create symbolic links in " |
| "<tt>`~/.gimp-2.2/brushes'</tt> to connect file brushes inside the repository " |
| "and, this way, provide the configuration needed by GIMP to use the brush " |
| "files produced inside the repository." |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "Warning" |
| msgstr "" |
| |
| |
| msgid "" |
| "When brushes are added to or removed from the repository, you need to update " |
| "your working copy and all information related to brushes inside your " |
| "workstation (e.g., brush links in <tt>`~/.gimp-2.2/brushes'</tt> and the " |
| "Brushes panel in GIMP). Otherwise, you may end up with broken links or " |
| "brushes in the repository that wouldn't be available for you to use in GIMP." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_13.xhtml#SEC57\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_15.xhtml#SEC69\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.6 The <tt>`trunk/Identity/Fonts'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "This section describes how typographies are organized in the repository and " |
| "how to make them available for you to use in <acronym title=\"GNU Image " |
| "Manipulation Program\">GIMP</acronym> (GNU Image Manipulation Program) and " |
| "Inkscape." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Project Corporate Identity is attached to <samp>`DejaVu LGC'</" |
| "samp> font-family and <samp>`Denmark'</samp> font-family." |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "Caution" |
| msgstr "" |
| |
| |
| msgid "" |
| "The copyright and license of <samp>`Denmark'</samp> typography aren't very " |
| "specific and that issue may represent a threat to The CentOS Project " |
| "Corporate Identity." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <samp>`Denmark'</samp> typography is used as base to build The CentOS " |
| "Logo (i.e., the main graphic design that connects/identifies all visual " |
| "manifestations related to The CentOS Project). If the typography used to " |
| "build The CentOS Logo is compromised somehow, the whole corporate visual " |
| "identity it represents would be compromised, as well. To prevent such " |
| "issues, it would be better for The CentOS Project to move on from " |
| "<samp>`Denmark'</samp> typography to another typography (free, preferably) " |
| "that retain the same visual style of <samp>`Denmark'</samp>, but intruce a " |
| "clearer copyright and license notice." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.6 The trunk/Identity/Fonts Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_23.xhtml#SEC112\">The <tt>`trunk/Identity/" |
| "Models/Brands'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "<a href=\"repository_12.xhtml#SEC47\">The <tt>`trunk/Identity'</tt> " |
| "Directory</a>." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_14.xhtml#SEC64\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_16.xhtml#SEC74\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.7 The <tt>`trunk/Identity/Images'</tt> Directory" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "..." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.7 The trunk/Identity/Images Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "If others find and fix bugs inside the branched development line, we could " |
| "merge such changes/experiences back to trunk development line (not visversa) " |
| "in order for future branches, created from trunk, to benefit." |
| msgstr "" |
| |
| |
| msgid "" |
| "Time intervals used to create branches and tags may vary, just as different " |
| "needs may arrive. For example, consider the release schema of CentOS " |
| "distribution: one major release every 2 years, security updates every 6 " |
| "months, support for 7 years long. Each time a CentOS distribution is " |
| "released, specially if it is a major release, there is a theme need in order " |
| "to cover CentOS distribution artwork requirements. At this point, is where " |
| "CentOS Artwork Repository comes up to scene." |
| msgstr "" |
| |
| |
| msgid "" |
| "Before releasing a new major release of CentOS distribution we create a " |
| "branch for one of several theme development lines available inside the " |
| "CentOS Artwork Repository, perform quality assurance on it, and later, " |
| "freeze that branch using tags. Once a the theme branch has been frozen " |
| "(under <tt>`tags/'</tt> directory), CentOS Packagers (the persons whom build " |
| "CentOS distribution) can use that frozen branch as source location to " |
| "fulfill CentOS distribution artwork needs. The same applies to CentOS " |
| "Webmasters (the persons whom build CentOS websites), and any other visual " |
| "manifestation required by the project." |
| msgstr "" |
| |
| |
| msgid "" |
| "In this location themes are organized in \"Models\" --to store common " |
| "information-- and \"Motifs\"--to store unique information. At rendering " |
| "time, both motifs and models are combined to produce the final CentOS " |
| "themes. CentOS themes can be tagged as \"Default\" or \"Alternative\". " |
| "CentOS themes are maintained by CentOS community." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_24.xhtml#SEC117\">The <tt>`trunk/Identity/" |
| "Models/Themes'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Images Themes " |
| "Motifs) --." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_15.xhtml#SEC69\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_17.xhtml#SEC79\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "2.8 The <tt>`trunk/Identity/Images/Themes'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Identity/Themes/'</tt> directory exists to organize " |
| "production of CentOS themes." |
| msgstr "" |
| |
| |
| msgid "" |
| "Initially, we start working themes on their trunk development line (e.g., " |
| "<tt>`trunk/Identity/Images/Themes/TreeFlower/'</tt>), here we organize " |
| "information that cannot be produced automatically (i.e., background images, " |
| "concepts, color information, screenshots, etc.)." |
| msgstr "" |
| |
| |
| msgid "" |
| "Later, when theme trunk development line is considered \"ready\" for " |
| "implementation (e.g., all required backgrounds have been designed), we " |
| "create a branch for it (e.g., <tt>`branches/Identity/Images/Themes/" |
| "TreeFlower/1/'</tt>). Once the branch has been created, we forget that " |
| "branch and continue working the trunk development line while others (e.g., " |
| "an artwork quality assurance team) test the new branch for tunning it up." |
| msgstr "" |
| |
| |
| msgid "" |
| "Once the branch has been tunned up, and considered \"ready\" for release, it " |
| "is freezed under <tt>`tags/'</tt> directory (e.g., <tt>`tags/Identity/Images/" |
| "Themes/TreeFower/1.0/'</tt>) for packagers, webmasters, promoters, and " |
| "anyone who needs images from that CentOS theme the tag was created for." |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.8 The trunk/Identity/Images/Themes Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "Both branches and tags, inside CentOS Artwork Repository, use numerical " |
| "values to identify themselves under the same location. Branches start at one " |
| "(i.e., <samp>`1'</samp>) and increment one unit for each branch created from " |
| "the same trunk development line. Tags start at zero (i.e., <samp>`0'</samp>) " |
| "and increment one unit for each tag created from the same branch development " |
| "line." |
| msgstr "" |
| |
| |
| msgid "Convenction" |
| msgstr "" |
| |
| |
| msgid "" |
| "Do not freeze trunk development lines using tags directly. If you think you " |
| "need to freeze a trunk development line, create a branch for it and then " |
| "freeze that branch instead." |
| msgstr "" |
| |
| |
| msgid "" |
| "The trunk development line may introduce problems we cannot see immediatly. " |
| "Certainly, the high changable nature of trunk development line complicates " |
| "finding and fixing such problems. On the other hand, the branched " |
| "development lines provide a more predictable area where only fixes/" |
| "corrections to current content are commited up to repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "To add a new motif structure to CentOS Artwork Repository, you need to use " |
| "the <code>centos-art</code> command line in the <tt>`Identity/Images/" |
| "Themes/'</tt> directory as described below:" |
| msgstr "" |
| |
| |
| msgid "centos-art add --motif=ThemeName" |
| msgstr "" |
| |
| |
| msgid "" |
| "The previous command will create the basic structure of themes for you. The " |
| "basic structure produced by <code>centos-art</code> command is illustrated " |
| "in the following figure:" |
| msgstr "" |
| |
| |
| msgid "" |
| "trunk/Identity/Images/Themes/$ThemeName/ |-- Backgrounds | |-- Img | `-- Tpl " |
| "|-- Info | |-- Img | `-- Tpl |-- Palettes `-- Screenshots" |
| msgstr "" |
| |
| |
| msgid "" |
| "When designing artistic motifs for CentOS, consider the following " |
| "recommendations:" |
| msgstr "" |
| |
| |
| msgid "" |
| "Give a unique (case-sensitive) name to your Motif. This name is used as " |
| "value wherever theme variable (<b>$THEME</b>) or translation marker " |
| "(<b>=THEME=</b>) is. Optionally, you can add a description about inspiration " |
| "and concepts behind your work." |
| msgstr "" |
| |
| |
| msgid "" |
| "Use the location <tt>`trunk/Identity/Images/Themes/$THEME/'</tt> to store " |
| "your work. If it doesn't exist create it. Note that this require you to have " |
| "previous commit access in CentOS Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Project is using the blue color (<b>#204c8d</b>) as base color " |
| "for its corporate visual identity. Use such base corporate color information " |
| "as much as possible in your artistic motif designs." |
| msgstr "" |
| |
| |
| msgid "Try to make your design fit one of the theme models." |
| msgstr "" |
| |
| |
| msgid "Feel free to make your art enterprise-level and beautiful." |
| msgstr "" |
| |
| |
| msgid "" |
| "Add the following information on your artwork (both in a visible design area " |
| "and document metadata): <ul class=\"toc\"><li> The name (or logo) of your " |
| "artistic motif. </li><li> The copyright sentence: <b>Copyright (C) YEAR " |
| "YOURNAME</b></li><li> The license under which the work is released. All " |
| "CentOS Art works are released under <a class=\"www\" href=\"http://" |
| "creativecommons.org/licenses/by-sa/3.0/\">Creative Common Share-Alike " |
| "License 3.0</a> (<a class=\"www\" href=\"http://creativecommons.org/licenses/" |
| "by-sa/3.0/\">http://creativecommons.org/licenses/by-sa/3.0/</a>). </li></ul>" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`Backgrounds/'</tt> directory is used to organize artistic motif " |
| "background images and the projects used to build those images." |
| msgstr "" |
| |
| |
| msgid "" |
| "Background images are linked (using the <b>import</b> feature of Inkscape) " |
| "inside almost all theme art works. This structure let you make centralized " |
| "changes on the visual identity and propagate them quickly to other areas." |
| msgstr "" |
| |
| |
| msgid "" |
| "In this configuration you design background images for different screen " |
| "resolutions based on the theme artistic motif." |
| msgstr "" |
| |
| |
| msgid "" |
| "You may create different artistic motifs propositions based on the same " |
| "conceptual idea. The conceptual idea is what defines a theme. Artistic " |
| "motifs are interpretations of that idea." |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside this directory artistic motifs are organized by name (e.g., " |
| "TreeFlower, Modern, etc.)." |
| msgstr "" |
| |
| |
| msgid "" |
| "Each artistic motif directory represents just one unique artistic motif." |
| msgstr "" |
| |
| |
| msgid "" |
| "The artistic motif is graphic design used as common pattern to connect all " |
| "visual manifestations inside one unique theme. The artistic motif is based " |
| "on a conceptual idea. Artistic motifs provide visual style to themes." |
| msgstr "" |
| |
| |
| msgid "" |
| "Designing artistic motifs is for anyone interested in creating beautiful " |
| "themes for CentOS. When building a theme for CentOS, the first design you " |
| "need to define is the artistic motif." |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside CentOS Artwork Repository, theme visual styles (a.k.a., artistic " |
| "motifs) and theme visual structures (a.k.a., design models) are two " |
| "different working lines. When you design an artistic motif for CentOS you " |
| "concentrate on its visual style, and eventualy, use the <code>centos-art</" |
| "code> command line interface to render the visual style, you are currently " |
| "producing, against an already-made theme model in order to produce the final " |
| "result. Final images are stored under <tt>`Motifs/'</tt> directory using the " |
| "model name, and the model directory structure as reference." |
| msgstr "" |
| |
| |
| msgid "" |
| "The artistic motif base structure is used by <code>centos-art</code> to " |
| "produce images automatically. This section describes each directory of " |
| "CentOS artistic motif base structure." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`Backgrounds/'</tt> directory is probably the core component, inside " |
| "<tt>`Motifs/'</tt> directory structure. Inside <tt>`Backgrounds/'</tt> " |
| "directory you produce background images used by almost all theme models (e." |
| "g., Distribution, Websites, Promotion, etc.). The <tt>`Backgrounds/'</tt> " |
| "directory can contain subdirectories to help you organize the design process." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_16.xhtml#SEC74\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_18.xhtml#SEC84\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.9 The <tt>`trunk/Identity/Images/Themes/Motifs'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "The <tt>`trunk/Identity/Images/Themes'</tt> directory exists to:" |
| msgstr "" |
| |
| |
| msgid "Organize CentOS themes' artistic motifs." |
| msgstr "" |
| |
| |
| msgid "" |
| "The artistic motif of theme is a graphic design component that provides the " |
| "visual style of themes, it is used as pattern to connect all visual " |
| "manifestations inside one unique theme." |
| msgstr "" |
| |
| |
| msgid "" |
| "Artistic motifs are based on conceptual ideas. Conceptual ideas bring the " |
| "motivation, they are fuel for the engines of human imagination. Good " |
| "conceptual ideas may produce good motivation to produce almost anything, and " |
| "art works don't escape from it." |
| msgstr "" |
| |
| |
| msgid "`TreeFlower'" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS like trees, has roots, trunk, branches, leaves and flowers. Day by " |
| "day they work together in freedom, ruled by the laws of nature and open " |
| "standards, to show the beauty of its existence." |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.9 The trunk/Identity/Images/Themes/Motifs " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "`Modern'" |
| msgstr "" |
| |
| |
| msgid "Modern, squares and circles flowing up." |
| msgstr "" |
| |
| |
| msgid "" |
| "If you have new conceptual ideas for CentOS, then you can say that you want " |
| "to create a new artistic motif for CentOS. To create a new artistic motif " |
| "you need to create a directory under <tt>`Identity/Images/Themes/'</tt> " |
| "using a name coherent with your conceptual idea. That name will be the name " |
| "of your artistic motif. If possible, when creating new conceptual ideas for " |
| "CentOS, think about what CentOS means for you, what does it makes you feel, " |
| "take your time, think deep, and share; you can improve the idea as time goes " |
| "on." |
| msgstr "" |
| |
| |
| msgid "" |
| "Once you have defined a name for your theme, you need to create the motif " |
| "structure of your theme. The motif structure is the basic direcotry " |
| "structure you'll use to work your ideas. Here is where you organize your " |
| "graphic design projects." |
| msgstr "" |
| |
| |
| msgid "" |
| "With the combination of both CentOS Artwork Repository and <tt>`centos-art." |
| "sh'</tt> scripts we define work lines where translators, programmers, and " |
| "graphic designers work together to distribute and reduce the amount of time " |
| "employed to produce The CentOS Project monolithic corporate identity." |
| msgstr "" |
| |
| |
| msgid "" |
| "From a monolithic corporate visual identity point of view, notice that we " |
| "are producing a new visual style for the same theme (i.e., <em>Flame</em>). " |
| "It would be another flame design but still a flame design. This idea is very " |
| "important to be aware of, because we are somehow \"refreshing\" the theme, " |
| "not changing it at all." |
| msgstr "" |
| |
| |
| msgid "" |
| "This way, as we are \"refreshing\" the theme, we still keep oursleves inside " |
| "the monolithic conception we are trying to be attached to (i.e., one unique " |
| "name, and one unique visual style for all visual manifestations)." |
| msgstr "" |
| |
| |
| msgid "" |
| "Producing artistic motifs is a creative process that may consume long time, " |
| "specially for people without experienced knowledge on graphic design land. " |
| "Using \"randomly generated\" conception to produce artistic motifs could be, " |
| "practically, a way for anyone to follow in order to produce maintainable " |
| "artistic motifs in few steps." |
| msgstr "" |
| |
| |
| msgid "" |
| "Due to the \"randomly generated\" nature of Flame filter, we find that " |
| "<em>Flame</em> pattern is not always the same when we use <em>Flame</em> " |
| "filter interface." |
| msgstr "" |
| |
| |
| msgid "" |
| "Using the same pattern design for each visual manifestation is essential in " |
| "order to maintain the visual connection among all visual manifestations " |
| "inside the same theme. Occasionally, we may introduce pattern variations in " |
| "opacity, size, or even position but never change the pattern design itself, " |
| "nor the color information used by images considered part of the same theme." |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "Important" |
| msgstr "" |
| |
| |
| msgid "" |
| "When we design background images, which are considered part of the same " |
| "theme, it is essential to use the same design pattern always. This is what " |
| "makes theme images to be visually connected among themeselves, and so, the " |
| "reason we use to define the word \"theme\" as: a set of images visually " |
| "connected among themeselves." |
| msgstr "" |
| |
| |
| msgid "" |
| "In order for us to reproduce the same flame pattern always, <em>Flame</em> " |
| "filter interface provides the <samp>`Save'</samp> and <samp>`Open'</samp> " |
| "options. The <samp>`Save'</samp> option brings up a file save dialog that " |
| "allows you to save the current Flame settings for the plug-in, so that you " |
| "can recreate them later. The <samp>`Open'</samp> option brings up a file " |
| "selector that allows you to open a previously saved Flame settings file." |
| msgstr "" |
| |
| |
| msgid "" |
| "The Flame settings we used in our example are saved in the file named " |
| "<tt>`800x600.xcf-flame.def'</tt>, inside the <tt>`Backgrounds/Xcf'</tt> " |
| "directory structure." |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "Screenshots" |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_16.xhtml#SEC74\">The <tt>`trunk/Identity/" |
| "Images/Themes'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_11.xhtml#SEC42\">The <tt>`trunk'</tt> " |
| "Directory</a>." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_17.xhtml#SEC79\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_19.xhtml#SEC89\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.10 The <tt>`trunk/Identity/Images/Themes/Motifs/Flame'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "This section describes the <em>Flame</em> artistic motif. This section may " |
| "be useful for anyone interested in reproducing the <em>Flame</em> artistic " |
| "motif, or in creating new artistic motifs for The CentOS Project corporate " |
| "visual identity." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <em>Flame</em> artistic motif was built using the flame filter of Gimp " |
| "2.2 in CentOS 5.5." |
| msgstr "" |
| |
| |
| msgid "" |
| "The flame filter of Gimp can produce stunning, randomly generated fractal " |
| "patterns. The flame filter of Gimp gives us a great oportunity to reduce the " |
| "time used to produce new artistic motifs, because of its \"randomly generated" |
| "\" nature. Once the artistic motif be created, it is propagated through all " |
| "visual manifestations of CentOS Project corporate visual identity using the " |
| "<tt>`centos-art.sh'</tt> script (see section <a href=\"repository_48." |
| "xhtml#SEC253\">The <tt>`trunk/Scripts'</tt> Directory</a>) inside the CentOS " |
| "Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "To set the time intervals between each new visual style production, we could " |
| "reuse the CentOS distribution major release schema. I.e., we could produce a " |
| "new visual style, every two years, based on a new \"randomly generated\" " |
| "flame pattern, and publish the whole corporate visual identity (i.e., " |
| "distribution stuff, promotion stuff, websites stuff, etc.) with the new " |
| "major release of CentOS distribution all together at once." |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.10 The trunk/Identity/Images/Themes/Motifs/" |
| "Flame Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "Producing a new visual style is not one day's task. Once we have defined the " |
| "artistic motif, we need to propagate it through all visual manifestations of " |
| "The CentOS Project corporate visual identity. When we say that we could " |
| "produce one new visual style every two years we really mean: to work two " |
| "years long in order to propagate a new visual style to all visual " |
| "manifestations of The CentOS Project corporate visual identity." |
| msgstr "" |
| |
| |
| msgid "" |
| "Obviously, in order to propagate one visual style to all different visual " |
| "manifestations of The CentOS Project corporate visual identity, we need " |
| "first to know which the visual manifestations are. To define which visual " |
| "manifestations are inside The CentOS Project corporate visual identity is " |
| "one of the goals the CentOS Artwork Repository and this documentation manual " |
| "are both aimed to satisfy." |
| msgstr "" |
| |
| |
| msgid "" |
| "Once we define which the visual manifestation are, it is possible to define " |
| "how to produce them, and this way, organize the automation process. Such " |
| "automation process is one of the goals of <tt>`centos-art.sh'</tt> script." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_18.xhtml#SEC84\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_20.xhtml#SEC95\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.11 The <tt>`trunk/Identity/Images/Themes/Motifs/Modern'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.11 The trunk/Identity/Images/Themes/Motifs/" |
| "Modern Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The rendition script was named <code>render.sh</code>. The directory " |
| "structures were prepared to receive the rendition script so images could be " |
| "produced inside them. Each directory structure had design templates (.svg), " |
| "translation files (.sed), and translated images (.png)." |
| msgstr "" |
| |
| |
| msgid "" |
| "The rendition script was unified in 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 "" |
| "Concepts about corporate identity began to be considered. As referece, it " |
| "was used the book <em>Corporate Identity</em> by Wally Olins (1989) and " |
| "Wikipedia (<a class=\"www\" href=\"http://en.wikipedia.org/Corporate_identity" |
| "\">http://en.wikipedia.org/Corporate_identity</a>)." |
| msgstr "" |
| |
| |
| msgid "" |
| "The rendition script main's goal becomes to: automate production of a " |
| "monolithic corporate visual identity structure, based on The CentOS Mission " |
| "and The CentOS Release Schema." |
| msgstr "" |
| |
| |
| msgid "" |
| "The documentation of CentOS Artwork Repository started to take form in LaTeX " |
| "format." |
| msgstr "" |
| |
| |
| msgid "2010" |
| msgstr "" |
| |
| |
| msgid "" |
| "The rendition script <code>render.sh</code> is no longer a rendition script, " |
| "but a collection of functionalities grouped into the <code>centos-art.sh</" |
| "code> script where rendition is one functionality among others. The " |
| "<code>centos-art.sh</code> is created to automate most frequent tasks inside " |
| "the repository. There is no need to have links all around the repository if " |
| "a command-line interface can be created (through symbolic links, in the " |
| "<tt>`~/bin'</tt> directory) and be called anywhere inside the repository as " |
| "it would be usually done with regular commands." |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside <code>centos-art.sh</code>, functionalities started to get identified " |
| "and separated one another. For example, when images were rendered, there was " |
| "no need to load functionalities related to documentation manual. This moved " |
| "us onto common functionalities and specific functionalities inside " |
| "<code>centos-art.sh</code> script. Common functionalities are loaded when " |
| "the script is initiated and are available to specific functionalities." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>centos-art.sh</code> script was redesigned to handle options " |
| "trough <code>getopt</code> option parser." |
| msgstr "" |
| |
| |
| msgid "" |
| "The repository directory structure was updated to improve the implementation " |
| "of concepts related to corporate visual identity. Specially in the area " |
| "related to themes which were divided into design models and artistic motifs." |
| msgstr "" |
| |
| |
| msgid "2011" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>centos-art.sh</code> script was redesigned to start translating " |
| "SVG and other XML-based files (e.g., XHTML and Docbook files) through the " |
| "<code>xml2po</code> program and shell scripts files (e.g., Bash scripts) " |
| "through GNU <code>gettext</code> tools. This configuration provided a " |
| "stronger interface for graphic designers, translators and programmers at " |
| "time of producing localized content. <tt>`.sed'</tt> files are no longer " |
| "used to handle translations." |
| msgstr "" |
| |
| |
| msgid "Improve option parsing through <code>getopt</code>." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>centos-art.sh</code> script is updated to organize functionalities " |
| "in two groups: \"the administrative functionalities\" and \"the productive " |
| "functionalities\". The administrative functionalities cover actions like: " |
| "copying, deleting and renaming directory structures inside the repository. " |
| "Also, preparing your workstation for using <code>centos-art.sh</code> " |
| "script, making backups of the distribution theme currently installed, " |
| "installing themes created inside repository and restoring themes from " |
| "backup. On the other hand, the productive functionalities cover actions " |
| "like: content rendition, content localization, content documentation and " |
| "content maintainance." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_1.xhtml#SEC1\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_3.xhtml#SEC7\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_1.xhtml#SEC1\" title=\"Beginning of this chapter or " |
| "previous chapter\"> << </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "[<a href=\"repository_1.xhtml#SEC1\" title=\"Up section\"> Up </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "This section records noteworthy changes of CentOS Artwork Repository through " |
| "years." |
| msgstr "" |
| |
| |
| msgid "2008" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Artwork Repository started at CentOS Developers mailing list (<a " |
| "class=\"mailto\" href=\"mailto:centos-devel@centos.org\">centos-devel@centos." |
| "org</a>) during a discussion about how to automate the slide images of " |
| "Anaconda. In such discussion, Ralph Angenendt rose up his hand to ask: Do " |
| "you have something to show?" |
| msgstr "" |
| |
| |
| msgid "" |
| "To answer the question, Alain Reguera Delgado suggested a bash script which " |
| "combined SVG and SED files in order to produce PNG images in different " |
| "languages --together with the proposition of creating a Subversion " |
| "repository where translations and image production could be distributed " |
| "inside The CentOS Community--." |
| msgstr "" |
| |
| |
| msgid "" |
| "Karanbirn Sighn considered the idea intresting and provided the " |
| "infrastructure necessary to support the effort. This way the CentOS Artwork " |
| "SIG and the CentOS Artwork Repository were officially created and made " |
| "available in the following urls:" |
| msgstr "" |
| |
| |
| msgid "https://projects.centos.org/trac/artwork/" |
| msgstr "" |
| |
| |
| msgid "https://projects.centos.org/svn/artwork/" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 1.1 History" |
| msgstr "" |
| |
| |
| msgid "" |
| "Once the CentOS Artwork Repository was available, Alain Reguera Delagdo " |
| "uploaded the bash script for rendering Anaconda slides; Ralph Angenendt " |
| "documented it very well and The CentOS Translators started to download " |
| "working copies of CentOS Artwork Repository to produce slide images in their " |
| "own languages." |
| msgstr "" |
| |
| |
| msgid "2009" |
| msgstr "" |
| |
| |
| msgid "" |
| "The rendition script is at a very rustic state where only slide images can " |
| "be produced." |
| msgstr "" |
| |
| |
| msgid "" |
| "The rendition script was redesigned to extend image production to other " |
| "areas, not just slide images. In this configuration one translated SVG " |
| "instance was created from the SVG file provided as input in order to produce " |
| "one translated PNG image as output. The translation of SVG files was made " |
| "through SED replacement commands and the rendition of PNG images was " |
| "realized through Inkscape command line internface." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_19.xhtml#SEC89\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_21.xhtml#SEC101\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.12 The <tt>`trunk/Identity/Images/Themes/Motifs/Pipes'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.12 The trunk/Identity/Images/Themes/Motifs/" |
| "Pipes Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_20.xhtml#SEC95\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_22.xhtml#SEC107\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.13 The <tt>`trunk/Identity/Images/Themes/Motifs/TreeFlower'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.13 The trunk/Identity/Images/Themes/Motifs/" |
| "TreeFlower Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_21.xhtml#SEC101\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_23.xhtml#SEC112\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.14 The <tt>`trunk/Identity/Models'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.14 The trunk/Identity/Models Directory" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "Note" |
| msgstr "" |
| |
| |
| msgid "" |
| "The information about trademarks and corporate identity is my personal " |
| "interpretation of <a class=\"www\" href=\"http://en.wikipedia.org/" |
| "Corporate_identity\">http://en.wikipedia.org/Corporate_identity</a> and <a " |
| "class=\"www\" href=\"http://en.wikipedia.org/Trademark\">http://en.wikipedia." |
| "org/Trademark</a> description. If you have practical experiences with these " |
| "affairs, please serve yourself to improve this section with your reasons." |
| msgstr "" |
| |
| |
| msgid "The <tt>`trunk/Identity/Models'</tt> Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_22.xhtml#SEC107\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_24.xhtml#SEC117\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.15 The <tt>`trunk/Identity/Models/Brands'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "This section describes The CentOS Brand design models." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Brand provides the one unique name or trademark that connects the " |
| "producer with their products. In this case, the producer is The CentOS " |
| "Project and the products are The CentOS Project visual manifestations." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Brand is the main visual representation of the CentOS project so " |
| "the typography used in it must be the same always, no matter where it be " |
| "shown. It also has to be clear enough to dismiss any confussion between " |
| "similar typefaces (e.g., the number one (1) sometimes is confuesed with the " |
| "letter <samp>`el'</samp> (l) or letter <samp>`ai'</samp> (i))." |
| msgstr "" |
| |
| |
| msgid "" |
| "As convenction, the word <samp>`CentOS'</samp> uses <samp>`Denmark'</samp> " |
| "typography as base, both for the word <samp>`CentOS'</samp> and the phrase " |
| "<samp>`Community Enterprise Operating System'</samp>. The phrase size of " |
| "CentOS logo is half the size in poits the word <samp>`CentOS'</samp> has and " |
| "it below <samp>`CentOS'</samp> word and aligned with it on the left. The " |
| "distance between <samp>`CentOS'</samp> word and phrase <samp>`Community " |
| "Enterprise Operating System'</samp> have the size in points the phrase has." |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.15 The trunk/Identity/Models/Brands Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "When the CentOS release brand is built, use <samp>`Denmark'</samp> " |
| "typography for the release number. The release number size is two times " |
| "larger (in height) than default <samp>`CentOS'</samp> word. The separation " |
| "between release number and <samp>`CentOS'</samp> word is twice the size in " |
| "points of separation between <samp>`CentOS'</samp> word and phrase " |
| "<samp>`Community Enterprise Operating System'</samp>." |
| msgstr "" |
| |
| |
| msgid "" |
| "Another component inside CentOS logo is the trademark symbol (TM). This " |
| "symbol specifies that the CentOS logo must be consider a product brand, even " |
| "it is not a registered one. The trademark symbol uses DejaVu LGC Sans " |
| "Regular typography. The trademark symbol is aligned right-top on the outter " |
| "side of <samp>`CentOS'</samp> word. The trademark symbol must not exceed haf " |
| "the distance, in points, between <samp>`CentOS'</samp> word and the release " |
| "number on its right." |
| msgstr "" |
| |
| |
| msgid "" |
| "It would be very convenient for the CentOS Project and its community to to " |
| "make a registered trademark (®) of CentOS logo. To make a register trademark " |
| "of CentOS Logo prevents legal complications in the market place of brands. " |
| "It grants the consistency, through time, of CentOS project corporate visual " |
| "identity." |
| msgstr "" |
| |
| |
| |
| |
| msgid "" |
| "<a href=\"repository_16.xhtml#SEC74\">The <tt>`trunk/Identity/Images/" |
| "Themes'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_23.xhtml#SEC112\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_25.xhtml#SEC124\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.16 The <tt>`trunk/Identity/Models/Themes'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "This section describes design models from The CentOS Themes." |
| msgstr "" |
| |
| |
| msgid "" |
| "Theme models let you modeling characteristics (e.g., dimensions, translation " |
| "markers, position of each element on the display area, etc.) common to all " |
| "themes. Theme models let you reduce the time needed when propagating " |
| "artistic motifs to different visual manifestations." |
| msgstr "" |
| |
| |
| msgid "" |
| "Theme models serves as a central pool of design templates for themes to use. " |
| "This way you can produce themes with different artistic motifs but same " |
| "characteristics." |
| msgstr "" |
| |
| |
| msgid "Default Design Model" |
| msgstr "" |
| |
| |
| msgid "" |
| "Default Design Models for CentOS Themes provide the common structural " |
| "information (e.g., image dimensions, translation markers, trademark " |
| "position, etc.) the <code>centos-art</code> script uses to produce images " |
| "when no other design model is specified." |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.16 The trunk/Identity/Models/Themes Directory" |
| msgstr "" |
| |
| |
| msgid "Alternative Design Models" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS alternative theme models exist for people how want to use a different " |
| "visual style on their installations of CentOS distribution. As the visual " |
| "style is needed for a system already installed components like Anaconda are " |
| "not required inside alternative themes. Inside alternative themes you find " |
| "post-installation visual style only (i.e. Backgrounds, Display Managers, " |
| "Grub, etc.). CentOS alternative themes are maintained by CentOS Community." |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default) --." |
| msgstr "" |
| |
| |
| msgid "" |
| "Use a common artistic motifs as background for all CentOS Distribution " |
| "images. -- <strong>Removed</strong>(xref:Directories trunk Identity Images " |
| "Themes Motifs) --, for more information." |
| msgstr "" |
| |
| |
| msgid "So, combining answers above, we could conclude that:" |
| msgstr "" |
| |
| |
| msgid "" |
| "In order to implement the CentOS Monolithic Visual Structure on CentOS " |
| "Distribution visual manifestations, a CentOS Release Trademark and a " |
| "background information based on one unique artistic motif should be used in " |
| "all remarkable images The CentOS Distribution visual manifestation is made " |
| "of." |
| msgstr "" |
| |
| |
| msgid "" |
| "Remarking the CentOS Release Schema inside each major release of CentOS " |
| "Distribution --or similar visual manifestations-- takes <em>high attention</" |
| "em> inside The CentOS Project corporate visual identity. It should be very " |
| "clear for everyone which major release of CentOS Distribution is being used." |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default Distro) --." |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default Concept) --." |
| msgstr "" |
| |
| |
| msgid "The <tt>`trunk/Identity/Images/Themes'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "The <tt>`trunk/Identity/Models/Themes'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(ref:Directories trunk Identity Images Themes " |
| "Motifs) --" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_24.xhtml#SEC117\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_26.xhtml#SEC129\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.17 The <tt>`trunk/Identity/Models/Themes/Default'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "This section describes the default design model of The CentOS Themes." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Identity/Themes/Models/Default'</tt> directory implements the " |
| "concept of <em>Default Design Model</em> for The CentOS Themes. The CentOS " |
| "Themes Default Design Model provides the common structural information (e." |
| "g., image dimensions, translation markers, trademark position, etc.) the " |
| "<code>centos-art</code> script uses to produce images when no other design " |
| "model is specified." |
| msgstr "" |
| |
| |
| msgid "" |
| "Deisgn models in this directory do use the <em>CentOS Release Brand</em>. " |
| "The CentOS Release Brand is a combination of both The CentOS Type and The " |
| "CentOS Release Schema used to illustrate the major release of The CentOS " |
| "Distribution the image produced belongs to. -- <strong>Removed</strong>(xref:" |
| "Directories trunk Identity Models Tpl Brands) --, for more information." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Project maintains near to four different major releases of CentOS " |
| "Distribution. Each major release of CentOS Distribution has internal " |
| "differences that make them unique and, at the same time, each CentOS " |
| "Distribution individually is tagged into the one unique visual manifestation " |
| "(i.e., Distribution). So, how could we implement the monolithic visual " |
| "structure in one visual manifestation that has internal difference?" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.17 The trunk/Identity/Models/Themes/Default " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "To answer this question we broke the question in two parts and later " |
| "combined the resultant answers to build a possible solution." |
| msgstr "" |
| |
| |
| msgid "How to remark the internal differences visually?" |
| msgstr "" |
| |
| |
| msgid "" |
| "Merge both The CentOS Project Release Schema into The CentOS Project " |
| "Trademark to build The CentOS Project Release Trademark. The CentOS Project " |
| "Release Trademark remarks two things: first, it remarks the image is from " |
| "The CentOS Project and second, it remarks which major release of CentOS " |
| "Distribution does the image belongs to. -- <strong>Removed</strong>(xref:" |
| "Directories trunk Identity Models Tpl Brands) --, for more information on " |
| "how to develop and improve The CentOS Project Brand." |
| msgstr "" |
| |
| |
| msgid "How to remark the visual resemblance?" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_25.xhtml#SEC124\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_27.xhtml#SEC134\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.18 The <tt>`trunk/Identity/Models/Themes/Default/Concept'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.18 The trunk/Identity/Models/Themes/Default/" |
| "Concept Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "One thing some people have problems understanding is that if you have any " |
| "CentOS-3 product and update it, you will be updated to the latest CentOS-3.x " |
| "version." |
| msgstr "" |
| |
| |
| msgid "" |
| "The same is true for CentOS-4 and CentOS-5. If you update any CentOS-4 " |
| "product, you will be updated to the latest CentOS-4.x version, or to the " |
| "latest CentOS-5.x version if you are updating a CentOS-5 system. This is " |
| "exactly the same behavior as the upstream product. Let's assume that the " |
| "latest EL4 product is update 6. If you install the upstream original EL4 CDs " |
| "(the ones before any update set) and upgrade via <code>yum</code>, you will " |
| "have latest update set installed (EL4 update 6 in our example). Since all " |
| "updates within a major release (CentOS-2, CentOS-3, CentOS-4, CentOS-5) " |
| "always upgrade to the latest version when updates are performed (thus " |
| "mimicking upstream behavior), only the latest version is maintained in each " |
| "main tree on The CentOS Mirrors (<a class=\"www\" href=\"http://mirrors." |
| "centos.org/\">http://mirrors.centos.org/</a>)." |
| msgstr "" |
| |
| |
| msgid "" |
| "There is a CentOS Vault (<a class=\"www\" href=\"http://vault.centos.org/" |
| "\">http://vault.centos.org/</a>) containing old CentOS trees. This vault is " |
| "a picture of the older tree when it was removed from the main tree, and does " |
| "not receive updates. It should only be used for reference." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Distribution visual style is controlled by image files. These " |
| "image files are packaged inside The CentOS Distribution and made visible " |
| "once such packages are installed and executed. The way to go for changing " |
| "The CentOS Distribution visual style is changing all those image files to " |
| "add the desired visual style first and later, repackage them to make them " |
| "available inside the final iso files of CentOS Distribution." |
| msgstr "" |
| |
| |
| msgid "" |
| "Sometimes, between major releases, image files inside packages can be added, " |
| "removed or just get the name changed. In order to describe such variations, " |
| "the design models directory structure is organized in the same way the " |
| "variations are introduced (i.e., through The CentOS Distribution Release " |
| "Schema). So, each major release of The CentOS Distribution has its own " |
| "design model directory structure." |
| msgstr "" |
| |
| |
| msgid "" |
| "When a new package/component is added to one or all the major releases of " |
| "The CentOS Distribution, a design model directory structure for that " |
| "component needs to be created. Later, it is filled up with related design " |
| "models. Design models are created for each image file inside the component " |
| "that need to be rebuilt in order to set the visual style and brand " |
| "information correctly." |
| msgstr "" |
| |
| |
| msgid "" |
| "When a package is removed from one or all major releases of The CentOS " |
| "Distribution, the design model directory structure releated to that package/" |
| "component is no longer used. However, it could be very useful for historical " |
| "reasons. Also, someone could feel motivation enough to keep himself " |
| "documenting it or supporting it for whatever reason." |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default Distro 5) --." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(ref:Directories trunk Identity Models Themes " |
| "Default) --." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "<a href=\"repository_24.xhtml#SEC117\">The <tt>`trunk/Identity/Models/" |
| "Themes'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_26.xhtml#SEC129\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_28.xhtml#SEC141\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.19 The <tt>`trunk/Identity/Models/Themes/Default/Distro'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "This section organizes default design models for different major releases of " |
| "CentOS Distribution." |
| msgstr "" |
| |
| |
| msgid "" |
| "In order to better understatand how this visual manifestation is organized, " |
| "it is necessary to consider what The CentOS Distribution is and how it is " |
| "released." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Distribution is 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 Project 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 "" |
| "CentOS Artwork Repository: 2.19 The trunk/Identity/Models/Themes/Default/" |
| "Distro Directory" |
| msgstr "" |
| |
| |
| msgid "The CentOS Distribution Release Schema" |
| msgstr "" |
| |
| |
| msgid "" |
| "The upstream vendor has released 4 versions of their <acronym title=" |
| "\"Enterprise Linux\">EL</acronym> (Enterprise Linux) product that The CentOS " |
| "Project rebuilds the freely available SRPMS for. The upstream vendor " |
| "releases security updates as required by circumstances. The CentOS Project " |
| "releases rebuilds of security updates as soon as possible. Usually within 24 " |
| "hours (our stated goal is with 72 hours, but we are usually much faster)." |
| msgstr "" |
| |
| |
| msgid "" |
| "The upstream vendor also releases numbered update sets for major versions of " |
| "their EL product from 2 to 4 times per year. There are new ISOs from the " |
| "upstream vendor provided for these update sets. Update sets will be " |
| "completed as soon as possible after the upstream vendor releases their " |
| "version … generally within 2 weeks. The CentOS Project follows these " |
| "conventions as well, so CentOS-3.9 correlates with EL 3 update 9 and CentOS-" |
| "4.6 correlates with EL 4 update 6, CentOS-5.1 correlates to EL 5 update 1, " |
| "etc." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_27.xhtml#SEC134\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_29.xhtml#SEC146\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.20 The <tt>`trunk/Identity/Models/Themes/Default/Distro/5'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default Distro 5 Syslinux) --." |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default Distro 5 Anaconda) --." |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default Distro 5 Rhgb) --." |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default Distro 5 Gdm) --." |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default Distro 5 Kdm) --." |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default Distro 5 Grub) --." |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default Distro 5 Gsplash) --." |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(xref:Directories trunk Identity Models Themes " |
| "Default Distro 5 Ksplash) --." |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.20 The trunk/Identity/Models/Themes/Default/" |
| "Distro/5 Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "-- <strong>Removed</strong>(ref:Directories trunk Identity Models Themes " |
| "Default Distro) --." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_28.xhtml#SEC141\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_30.xhtml#SEC151\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.21 The <tt>`trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/" |
| "Release'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.21 The trunk/Identity/Models/Themes/Default/" |
| "Distro/5.5/Notes/Release Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_2.xhtml#SEC2\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_4.xhtml#SEC14\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "This section records authoring information of CentOS Artwork Repository " |
| "along the years:" |
| msgstr "" |
| |
| |
| msgid "Graphic Design" |
| msgstr "" |
| |
| |
| msgid "Guideon de Kok" |
| msgstr "" |
| |
| |
| |
| |
| msgid "Alain Reguera Delgado" |
| msgstr "" |
| |
| |
| msgid "Marcus Moeller" |
| msgstr "" |
| |
| |
| msgid "Documentation" |
| msgstr "" |
| |
| |
| |
| |
| msgid "Ralph Angenendt" |
| msgstr "" |
| |
| |
| msgid "Localization" |
| msgstr "" |
| |
| |
| msgid "" |
| "<a class=\"mailto\" href=\"mailto:al@art.centos.org\">Alain Reguera Delgado</" |
| "a> (Spanish)" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 1.2 Authors" |
| msgstr "" |
| |
| |
| msgid "Automation" |
| msgstr "" |
| |
| |
| msgid "Infrastructure" |
| msgstr "" |
| |
| |
| |
| msgid "Karanbirn Singh" |
| msgstr "" |
| |
| |
| msgid "Packaging" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_29.xhtml#SEC146\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_31.xhtml#SEC156\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.22 The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Anaconda'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.22 The trunk/Identity/Models/Themes/Default/" |
| "Distro/5/Anaconda Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_30.xhtml#SEC151\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_32.xhtml#SEC161\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.23 The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Firstboot'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.23 The trunk/Identity/Models/Themes/Default/" |
| "Distro/5/Firstboot Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_31.xhtml#SEC156\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_33.xhtml#SEC166\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.24 The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Gdm'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "Another example of using last-rendition flow is that related to GDM and KDM " |
| "<tt>`tar.gz'</tt> file construction. Each <tt>`tar.gz'</tt> file is made of " |
| "several files that need to be put together in order to make them " |
| "installable. In the very specific case of GDM and KDM some of the required " |
| "files are retrived from design models directory structure and others from " |
| "artistic motifs directory structure after had been produced through base-" |
| "rendition. In this case, the action of grouping files and packing them is " |
| "realized through last-rendition action. This couldn't be possible through " |
| "post-rendition because we need to wait to have two images first (produced " |
| "through base-rendition) before we could grouping them all into the <tt>`tar." |
| "gz'</tt> package." |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.24 The trunk/Identity/Models/Themes/Default/" |
| "Distro/5/Gdm Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_32.xhtml#SEC161\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_34.xhtml#SEC171\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.25 The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Grub'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.25 The trunk/Identity/Models/Themes/Default/" |
| "Distro/5/Grub Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_33.xhtml#SEC166\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_35.xhtml#SEC176\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.26 The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Gsplash'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.26 The trunk/Identity/Models/Themes/Default/" |
| "Distro/5/Gsplash Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_34.xhtml#SEC171\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_36.xhtml#SEC181\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.27 The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Kdm'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.27 The trunk/Identity/Models/Themes/Default/" |
| "Distro/5/Kdm Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_35.xhtml#SEC176\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_37.xhtml#SEC186\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.28 The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Ksplash'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`Preview.png'</tt> image of Ksplash which is made of three different " |
| "images. In order to build the <tt>`Preview.png'</tt> image, we need to " |
| "create the three images the <tt>`Preview.png'</tt> image is made of first (e." |
| "g., through base-rendition) and then, combine them all together into one new " |
| "image, the <tt>`Preview.png'</tt> image in this case." |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.28 The trunk/Identity/Models/Themes/Default/" |
| "Distro/5/Ksplash Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_36.xhtml#SEC181\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_38.xhtml#SEC191\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.29 The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Rhgb'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.29 The trunk/Identity/Models/Themes/Default/" |
| "Distro/5/Rhgb Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_37.xhtml#SEC186\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_39.xhtml#SEC196\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.30 The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Syslinux'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.30 The trunk/Identity/Models/Themes/Default/" |
| "Distro/5/Syslinux Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_38.xhtml#SEC191\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_40.xhtml#SEC201\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "2.31 The <tt>`trunk/Identity/Models/Themes/Default/Posters'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.31 The trunk/Identity/Models/Themes/Default/" |
| "Posters Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The precise conditions of the license for the <code>centos-art.sh</code> " |
| "script are found in the General Public Licenses (see section <a href=" |
| "\"repository_56.xhtml#SEC333\">GNU General Public License</a>). This manual " |
| "specifically is covered by the GNU Free Documentation License (see section " |
| "<a href=\"repository_57.xhtml#SEC337\">GNU Free Documentation License</a>)." |
| msgstr "" |
| |
| |
| msgid "1. The CentOS Brand" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Brand (see section <a href=\"repository_23.xhtml#SEC112\">The " |
| "<tt>`trunk/Identity/Models/Brands'</tt> Directory</a>) is the main visual " |
| "manifestaion of The CentOS Project. The CentOS Project uses The CentOS Brand " |
| "to connect all its visual manifestions (e.g., GNU/Linux Distributions, " |
| "Websites, Stationery, etc.) and, this way, it provides recognition among " |
| "other similar projects." |
| msgstr "" |
| |
| |
| msgid "" |
| "Both The CentOS Brand and all the visual manifestations that derivate from " |
| "it are available for you to study and propose improvement around a good " |
| "citizen's will at The CentOS Community environment, but you are not allowed " |
| "to redistribute them elsewhere, without the given permission of The CentOS " |
| "Project." |
| msgstr "" |
| |
| |
| msgid "" |
| "If you need to redistribute either The CentOS Brand or any the visual " |
| "manifestatinos that derivate from it, write your intentions to the <a class=" |
| "\"mailto\" href=\"mailto:centos-devel@centos.org\">centos-devel@centos.org</" |
| "a> mailing list." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_3.xhtml#SEC7\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_5.xhtml#SEC17\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| msgid "Copyright © 2009, 2010, 2011 The CentOS Project." |
| msgstr "" |
| |
| |
| |
| |
| msgid "" |
| "Everyone is permitted to copy and distribute verbatim copies of this license " |
| "document, but changing it is not allowed." |
| msgstr "" |
| |
| |
| |
| |
| msgid "Preamble" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Artwork Repository organizes files in a very specific way to " |
| "implement The CentOS Project corporate visual identity. This very specific " |
| "organization of files is part of <code>centos-art.sh</code> script, a bash " |
| "script that automate most of the frequent tasks inside the repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>centos-art.sh</code> script and the organization of files it needs " |
| "to work are not in the public domain; they are copyrighted and there are " |
| "restrictions on their distribution, but these restrictions are designed to " |
| "permit everything that a good cooperating citizen would want to do. What is " |
| "not allowed is to try to prevent others from further sharing any version of " |
| "this program that they might get from you." |
| msgstr "" |
| |
| |
| msgid "" |
| "Specifically, we want to make sure that you have the right to give away " |
| "copies of <code>centos-art.sh</code> script, that you receive source code or " |
| "else can get it if you want it, that you can change this program or use " |
| "pieces of it in new free programs, and that you know you can do these things." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 1.3 Copying Conditions" |
| 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 " |
| "<code>centos-art.sh</code> script, you must give the recipients all the " |
| "rights that you have. You must make sure that they, too, receive or can get " |
| "the source code. And you must tell them their rights." |
| msgstr "" |
| |
| |
| msgid "" |
| "Also, for our own protection, we must make certain that everyone finds out " |
| "that there is no warranty for the <code>centos-art.sh</code> script. If this " |
| "program is modified by someone else and passed on, we want their recipients " |
| "to know that what they have is not what we distributed, so that any problems " |
| "introduced by others will not reflect on our reputation." |
| msgstr "" |
| |
| |
| msgid "" |
| "The centos-art.sh script is released as a GPL work. Individual packages used " |
| "by centos-art.sh script include their own licenses and the centos-art.sh " |
| "script license applies to all packages that it does not clash with. If there " |
| "is a clash between the centos-art.sh script license and individual package " |
| "licenses, the individual package license applies instead." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_39.xhtml#SEC196\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_41.xhtml#SEC206\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.32 The <tt>`trunk/Identity/Palettes'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.32 The trunk/Identity/Palettes Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_40.xhtml#SEC201\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_42.xhtml#SEC211\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.33 The <tt>`trunk/Identity/Patterns'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.33 The trunk/Identity/Patterns Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "This visual style diversity complicates our goal of one unique visual style " |
| "for all web applications. So, if we want one unique visual style for all web " |
| "applications used, it is innevitable to modify the web applications in order " |
| "to implement the CentOS one unique visual style customization in them. " |
| "Direct modification of upstream applications is not convenient because " |
| "upstream applications come with their one visual style and administrators " |
| "take the risk of loosing all customization changes the next time the " |
| "application be updated (since not all upstream web applications, used in " |
| "CentOS web environment, separate presentation from logic)." |
| msgstr "" |
| |
| |
| msgid "" |
| "To solve the \"one unique visual style\" issue, installation and " |
| "actualization of web applications --used inside CentOS web environment-- " |
| "need to be independent from upstream web applications development line; in a " |
| "way that CentOS web environment administrators can install and update web " |
| "applications freely without risk of loosing the one unique visual style " |
| "customization changes." |
| msgstr "" |
| |
| |
| msgid "" |
| "At the surface of this issue we can see the need of one specific yum " |
| "repository to store CentOS web environment customized web applications." |
| msgstr "" |
| |
| |
| msgid "Design model (without ads)" |
| msgstr "" |
| |
| |
| msgid "Design model (with ads)" |
| msgstr "" |
| |
| |
| msgid "HTML definitions" |
| msgstr "" |
| |
| |
| msgid "Controlling visual style" |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside CentOS web environment, the visual style is controlled by the " |
| "following compenents:" |
| msgstr "" |
| |
| |
| msgid "Webenv header background" |
| msgstr "" |
| |
| |
| msgid "trunk/Identity/Images/Themes/$THEME/Backgrounds/Img/1024x250.png" |
| msgstr "" |
| |
| |
| msgid "CSS definitions" |
| msgstr "" |
| |
| |
| msgid "trunk/Identity/Themes/Models/Default/Promo/Web/CSS/stylesheet.css" |
| msgstr "" |
| |
| |
| msgid "Producing visual style" |
| msgstr "" |
| |
| |
| msgid "" |
| "The visual style of CentOS web environment is defined in the following files:" |
| msgstr "" |
| |
| |
| msgid "" |
| "trunk/Identity/Images/Themes/$THEME/Backgrounds/Xcf/1024x250.xcf trunk/" |
| "Identity/Images/Themes/$THEME/Backgrounds/Img/1024x250.png trunk/Identity/" |
| "Images/Themes/$THEME/Backgrounds/Img/1024x250-bg.png trunk/Identity/Images/" |
| "Themes/$THEME/Backgrounds/Tpl/1024x250.svg" |
| msgstr "" |
| |
| |
| msgid "" |
| "As graphic designer you use <tt>`1024x250.xcf'</tt> file to produce " |
| "<tt>`1024x250-bg.png'</tt> file. Later, inside <tt>`1024x250.svg'</tt> file, " |
| "you use the <tt>`1024x250-bg.png'</tt> file as background layer to draw your " |
| "vectorial design. When you consider you artwork ready, use the <code>centos-" |
| "art.sh</code> script, as described below, to produce the visual style " |
| "controller images of CentOS web environment." |
| msgstr "" |
| |
| |
| msgid "" |
| "centos-art render --entry=trunk/Identity/Images/Themes/$THEME/Backgrounds --" |
| "filter='1024x250'" |
| msgstr "" |
| |
| |
| msgid "" |
| "Once you have rendered required image files, changing the visual style of " |
| "CentOS web environment is a matter of replacing old image files with new " |
| "ones, inside webenv repository file system structure. The visual style " |
| "changes will take effect the next time customization line of CentOS web " |
| "applications be packaged, uploded, and installed from [webenv] or [webenv-" |
| "test] repositories." |
| msgstr "" |
| |
| |
| msgid "Navigation" |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside CentOS web environment, the one-step navegation between web " |
| "applications is addressed using the web environment navigation bar. The web " |
| "environment navigation bar contains links to main applications and is always " |
| "visible no matter where you are inside the web environment." |
| msgstr "" |
| |
| |
| msgid "Development and release cycle" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS web environment development and relase cycle is described below:" |
| msgstr "" |
| |
| |
| msgid "Download" |
| msgstr "" |
| |
| |
| msgid "" |
| "The first action is download the source code of web applications we want to " |
| "use inside CentOS web environment." |
| msgstr "" |
| |
| |
| msgid "" |
| "The source location from which web application are downloaded is very " |
| "important. Use SRPMs from CentOS <strong>[base]</strong> and <strong>" |
| "[updates]</strong> repositories as first choise, and third party " |
| "repositories (e.g. RPMForge, EPEL, etc.) as last resource." |
| msgstr "" |
| |
| |
| msgid "Prepare" |
| msgstr "" |
| |
| |
| msgid "" |
| "Once web application source code has been downloaded, our duty is organize " |
| "its files inside <samp>`webenv'</samp> version controlled repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "When preparing the structure keep in mind that different web applications " |
| "have different visual styles, and also different ways to implement it. A " |
| "convenient way to organize the file system structure would be create one " |
| "development line for each web application we use inside CentOS web " |
| "environment. For example, consider the following file system structure:" |
| msgstr "" |
| |
| |
| msgid "" |
| "https://projects.centos.org/svn/webenv/trunk/ |-- WebApp1/ | |-- Sources/ | " |
| "| `-- webapp1-0.0.1/ | |-- Rpms/ | | `-- webapp1-0.0.1.rpm | |-- Srpms/ | | " |
| "`-- webapp1-0.0.1.srpm | `-- Specs/ | `-- webapp1-0.0.1.spec |-- WebApp2/ " |
| "`-- WebAppN/" |
| msgstr "" |
| |
| |
| msgid "Customize" |
| msgstr "" |
| |
| |
| msgid "" |
| "Once web applications have been organized inside the version controlled " |
| "repository file system, use subversion to create the CentOS customization " |
| "development line of web applications source code. For example, using the " |
| "above file system structure, you can create the customization development " |
| "line of <tt>`webapp1-0.0.1/'</tt> with the following command:" |
| msgstr "" |
| |
| |
| msgid "" |
| "svn cp trunk/WebApp1/Sources/webapp1-0.0.1 trunk/WebApp1/Sources/webapp1-" |
| "0.0.1-webenv" |
| msgstr "" |
| |
| |
| msgid "The command above creates the following structure:" |
| msgstr "" |
| |
| |
| msgid "" |
| "https://projects.centos.org/svn/webenv/trunk/ |-- WebApp1/ | |-- Sources/ | " |
| "| |-- webapp1-0.0.1/ | | `-- webapp1-0.0.1-webenv/ | |-- Rpms/ | | `-- " |
| "webapp1-0.0.1.rpm | |-- Srpms/ | | `-- webapp1-0.0.1.srpm | `-- Specs/ | `-- " |
| "webapp1-0.0.1.spec |-- WebApp2/ `-- WebAppN/" |
| msgstr "" |
| |
| |
| msgid "" |
| "In the above structure, the <tt>`webapp1-0.0.1-webenv/'</tt> directory is " |
| "the place where you customize the visual style of <tt>`webapp1-0.0.1/'</tt> " |
| "web application." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "Tip" |
| msgstr "" |
| |
| |
| msgid "" |
| "Use the <code>diff</code> command of Subversion between CentOS customization " |
| "and upstream development lines to know what you are changing exactly." |
| msgstr "" |
| |
| |
| msgid "Build packages" |
| msgstr "" |
| |
| |
| msgid "" |
| "When web application has been customized, build the web application RPM and " |
| "SRPM using the source location with <samp>`-webenv'</samp> prefix." |
| msgstr "" |
| |
| |
| msgid "" |
| "https://projects.centos.org/svn/webenv/trunk/ |-- WebApp1/ | |-- Sources/ | " |
| "| |-- webapp1-0.0.1/ | | `-- webapp1-0.0.1-webenv/ | |-- Rpms/ | | |-- " |
| "webapp1-0.0.1.rpm | | `-- webapp1-0.0.1-webenv.rpm | |-- Srpms/ | | |-- " |
| "webapp1-0.0.1.srpm | | `-- webapp1-0.0.1-webenv.srpm | `-- Specs/ | |-- " |
| "webapp1-0.0.1.spec | `-- webapp1-0.0.1-webenv.spec |-- WebApp2/ `-- WebAppN/" |
| msgstr "" |
| |
| |
| msgid "Release for testing" |
| msgstr "" |
| |
| |
| msgid "" |
| "When the customized web application has been packaged, make packages " |
| "available for testing and quality assurance. This can be achives using a " |
| "[webenv-test] yum repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "The [webenv-test] repository is not shipped inside CentOS distribution " |
| "default yum configuraiton. In order to use [webenv-test] repository you need " |
| "to configure it first." |
| msgstr "" |
| |
| |
| msgid "" |
| "If some problem is found to install/update/use the customized version of web " |
| "application, the problem is notified somewhere (a bugtracker maybe) and the " |
| "customization face is repated in order to fix the problem. To release the " |
| "new package add a number after <samp>`-webenv'</samp> prefix. For example, " |
| "if some problem is found in <tt>`webapp1-0.0.1-webenv.rpm'</tt>, when it be " |
| "fixed the new package will be named <tt>`webapp1-0.0.1-webenv-1.rpm'</tt>. " |
| "If a problem is found in <tt>`webapp1-0.0.1-webenv-1.rpm'</tt>, when it be " |
| "fixed the new package will be named <tt>`webapp1-0.0.1-webenv-2.rpm'</tt>, " |
| "and so on." |
| msgstr "" |
| |
| |
| msgid "" |
| "The \"customization -- release for testing\" process is repeated until " |
| "CentOS quality assurance team considers the package is ready for production." |
| msgstr "" |
| |
| |
| msgid "Release for production" |
| msgstr "" |
| |
| |
| msgid "" |
| "When customized web application packages are considered ready for production " |
| "they are moved from [webenv-test] to [webenv] repository. This action is " |
| "commited by CentOS quality assurance team." |
| msgstr "" |
| |
| |
| msgid "" |
| "The [webenv] repository is not shipped inside CentOS distribution default " |
| "yum configuraiton. In order to use [webenv] repository you need to configure " |
| "it first." |
| msgstr "" |
| |
| |
| msgid "The [webenv-test] repository" |
| msgstr "" |
| |
| |
| msgid "/etc/yum.repos.d/CentOS-Webenv-test.repo" |
| msgstr "" |
| |
| |
| msgid "" |
| "[webenv-test] name=CentOS-$releasever - Webenv-test mirrorlist=http://" |
| "mirrorlist.centos.org/?release=$releasever&arch=$basearch&" |
| "repo=webenv-test #baseurl=http://mirror.centos.org/centos/$releasever/webenv-" |
| "test/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-" |
| "$releasever enabled=1 priority=10" |
| msgstr "" |
| |
| |
| msgid "The [webenv] repository" |
| msgstr "" |
| |
| |
| msgid "/etc/yum.repos.d/CentOS-Webenv.repo" |
| msgstr "" |
| |
| |
| msgid "" |
| "[webenv] name=CentOS-$releasever - Webenv mirrorlist=http://mirrorlist." |
| "centos.org/?release=$releasever&arch=$basearch&repo=webenv " |
| "#baseurl=http://mirror.centos.org/centos/$releasever/webenv/$basearch/ " |
| "gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-$releasever " |
| "enabled=1 priority=10" |
| msgstr "" |
| |
| |
| msgid "Priority configuration" |
| msgstr "" |
| |
| |
| msgid "" |
| "Both [webenv] and [webenv-test] repositories update packages inside CentOS " |
| "[base] and CentOS [updates] repositories." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_41.xhtml#SEC206\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_43.xhtml#SEC226\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.34 The <tt>`trunk/Identity/Webenv'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS web environment is formed by a central web application --to cover " |
| "base needs (e.g., per-major release information like release notes, " |
| "lifetime, downloads, documentation, support, security advisories, bugs, " |
| "etc.)-- and many different free web applications --to cover specific needs " |
| "(e.g., wiki, mailing lists, etc.)--." |
| msgstr "" |
| |
| |
| msgid "The CentOS web environment is addressed to solve the following issues:" |
| msgstr "" |
| |
| |
| msgid "" |
| "One unique name and one unique visual style to all web applications used " |
| "inside the web environment." |
| msgstr "" |
| |
| |
| msgid "One-step navigation to web applications inside the environment." |
| msgstr "" |
| |
| |
| msgid "" |
| "High degree of customization to change the visual style of all web " |
| "applications with few changes (e.g, updating just two or three images plus " |
| "common style sheet [CSS] definitions)." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.34 The trunk/Identity/Webenv Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS project is attached to a monolithic corporate visual identity " |
| "(see section <a href=\"repository_12.xhtml#SEC47\">The <tt>`trunk/Identity'</" |
| "tt> Directory</a>), where all visual manifestations have one unique name and " |
| "one unique visual style. This way, the CentOS web environment has one unique " |
| "name (the CentOS brand) and one unique visual style (the CentOS default " |
| "theme) for all its visual manifestations, the web applications in this case." |
| msgstr "" |
| |
| |
| msgid "" |
| "Since a maintainance point of view, achiving the one unique visual style " |
| "inside CentOS web environment is not a simple task. The CentOS web " |
| "environment is built upon many different web applications which have " |
| "different visual styles and different internal ways to customize their own " |
| "visual styles. For example: MoinMoin, the web application used to support " |
| "the CentOS wiki (<a class=\"www\" href=\"http://wiki.centos.org/\">http://" |
| "wiki.centos.org/</a>) is highly customizable but Mailman (in its 2.x.x " |
| "serie), the web application used to support the CentOS mailing list, doesn't " |
| "support<a name=\"DOCF1\" href=\"repository_fot.xhtml#FOOT1\" id=\"DOCF1\">(1)" |
| "</a> a customization system that separates presentation from logic, similar " |
| "to that used by MoinMoin." |
| msgstr "" |
| |
| |
| msgid "" |
| "Another difference between <code>xml2po</code> and <code>xgettext</code> we " |
| "need to be aware of is the directory structure used to store machine " |
| "objects. In <code>xml2po</code>, the machine object is created in the " |
| "current working directory as <tt>`.xml2po.mo'</tt> and can be safetly " |
| "removed once the translated XML file has been created. In the case of " |
| "<code>xgettext</code>, the machine object needs to be stored in the <tt>`" |
| "$TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo'</tt> file in order for the " |
| "system to interpret it and should not be removed since it is the file that " |
| "contain the translation messages themselves." |
| msgstr "" |
| |
| |
| msgid "" |
| "Automation of localization tasks is achived through the <code>locale</code> " |
| "functionality of command-line interface." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "See section <a href=\"repository_51.xhtml#SEC281\">The <tt>`trunk/Scripts/" |
| "Functions/Locale'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_42.xhtml#SEC211\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_44.xhtml#SEC231\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.35 The <tt>`trunk/Locales'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Locales'</tt> directory structure provides the localization " |
| "work line and its main goal is provide the translation messages required to " |
| "produce content in different languages." |
| msgstr "" |
| |
| |
| msgid "" |
| "Translation messages inside the repository are stored as portable objects (e." |
| "g., .po, .pot) and machine objects (.mo) under <tt>`trunk/Locales'</tt> " |
| "directory structure." |
| msgstr "" |
| |
| |
| msgid "" |
| "Translation messages are organized using the directory structure of the " |
| "component being translated. For example, if we want to provide translation " |
| "messages for <tt>`trunk/Manuals/Repository'</tt>, then the <tt>`trunk/" |
| "Locales/Manuals/Repository'</tt> directory needs to be created." |
| msgstr "" |
| |
| |
| msgid "" |
| "Once the locale directory exists for the component we want to provide " |
| "translation messages for, it is necessary to create the translation files " |
| "where translation messages are. The translation files follows the concepts " |
| "of <code>xml2po</code> and GNU <code>gettext</code> tools." |
| msgstr "" |
| |
| |
| msgid "" |
| "The basic translation process is as follow: first, translatable strings are " |
| "extracted from files and a portable object template (.pot) is created or " |
| "updated with the information. Using the portable object template, a portable " |
| "object (.po) is created or updated for translator to locale the messages " |
| "retrived. Finally, a machine object (.mo) is created from portable object to " |
| "sotore the translated messages." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.35 The trunk/Locales Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside the repository there are two ways to retrive translatable strings " |
| "from files. The first one is through <code>xml2po</code> command and the " |
| "second through <code>xgettext</code> command. The <code>xml2po</code> is " |
| "used to retrive translatable strings from XML files (e.g., Scalable Vector " |
| "Graphics, DocBook, etc.) and the <code>xgettext</code> command is used to " |
| "retrive translatable strings from shell scripts files (e.g., the files that " |
| "make the <code>centos-art.sh</code> command-line interface)." |
| msgstr "" |
| |
| |
| msgid "" |
| "When translatable strings are retrived from XML files, using the " |
| "<code>xml2po</code> command, there is no need to create the machine object " |
| "as we do when translatable strings ar retrived from shell files, using the " |
| "<code>xgettext</code> command. The <code>xml2po</code> produces a temporal " |
| "machine object in order to create a translated XML file. Once the translated " |
| "XML file has been created the machine object is no longer needed. On the " |
| "other hand, the machine object produced by the <code>xgettext</code> command " |
| "is required by the system in order for the show shell script localized " |
| "messages." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_43.xhtml#SEC226\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_45.xhtml#SEC238\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.36 The <tt>`trunk/Manual'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Manual'</tt> directory is the place where files related to " |
| "documentation work line are stored in. The main goal of documentation work " |
| "line is to describe what each directory inside the CentOS Artwork Repository " |
| "is for, the conceptual ideas behind them and, if possible, how automation " |
| "scripts make use of them." |
| msgstr "" |
| |
| |
| msgid "Files" |
| msgstr "" |
| |
| |
| msgid "`repository.css'" |
| msgstr "" |
| |
| |
| msgid "`repository-index.texi'" |
| msgstr "" |
| |
| |
| msgid "`repository.info.bz2'" |
| msgstr "" |
| |
| |
| msgid "`repository-init.pl'" |
| msgstr "" |
| |
| |
| msgid "`repository-menu.texi'" |
| msgstr "" |
| |
| |
| msgid "`repository-node.texi'" |
| msgstr "" |
| |
| |
| msgid "`repository.pdf'" |
| msgstr "" |
| |
| |
| msgid "`repository.sed'" |
| msgstr "" |
| |
| |
| msgid "`repository.texi'" |
| msgstr "" |
| |
| |
| msgid "`repository.txt.bz2'" |
| msgstr "" |
| |
| |
| msgid "`repository.xhtml.bz2'" |
| msgstr "" |
| |
| |
| msgid "`repository.xml'" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.36 The trunk/Manual Directory" |
| msgstr "" |
| |
| |
| msgid "Directories" |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_45.xhtml#SEC238\">The <tt>`trunk/Manual/" |
| "Directories'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_46.xhtml#SEC243\">The <tt>`trunk/Manual/" |
| "Introduction'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_47.xhtml#SEC248\">The <tt>`trunk/Manual/" |
| "Licenses'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "See section <a href=\"repository_50.xhtml#SEC272\">The <tt>`trunk/Scripts/" |
| "Functions/Help'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_44.xhtml#SEC231\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_46.xhtml#SEC243\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.37 The <tt>`trunk/Manual/Directories'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Manual/Directories'</tt> directory stores source " |
| "documentation files related to repository directories. The directory " |
| "structure in this location mirrors the directory structure being documented " |
| "in the repository from top level directories (e.g., <tt>`trunk'</tt>, " |
| "<tt>`branches'</tt> and <tt>`tags'</tt>) to inner levels, including the " |
| "<tt>`trunk/Manual'</tt> location itself where documentation source files are " |
| "stored in." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.37 The trunk/Manual/Directories Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_45.xhtml#SEC238\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_47.xhtml#SEC248\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.38 The <tt>`trunk/Manual/Introduction'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.38 The trunk/Manual/Introduction Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_46.xhtml#SEC243\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_48.xhtml#SEC253\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.39 The <tt>`trunk/Manual/Licenses'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.39 The trunk/Manual/Licenses Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The script execution environment exists to provide script definitions that " |
| "can't be set anywhere else inside the script. Example of such definitions " |
| "include initialization of internationalization through <code>gettext</code> " |
| "program, script personal information and initialization of global " |
| "functionalities." |
| msgstr "" |
| |
| |
| msgid "" |
| "The global execution environment exists to provide definitions that can't be " |
| "set anywhere else inside the script. Example of such definitions include " |
| "initialization of functionalities (e.g., <code>cli_printMessage</code>, " |
| "<code>cli_getCurrentLocale</code>, <code>cli_checkFiles</code>, etc.) and " |
| "variables (e.g., <var>FUNCNAM</var>, <var>FUNCDIR</var>, <var>FUNCDIRNAM</" |
| "var>, <var>ARGUMENTS</var>, etc.) that can be both used on specific and " |
| "action execution environments, only." |
| msgstr "" |
| |
| |
| msgid "" |
| "The specific execution environment exists to provide definitions that can't " |
| "be set anywhere else inside the script. Example of such definitions include " |
| "initialization of specifc functionalities (e.g., <code>render</code>, " |
| "<code>help</code>, <code>locale</code>, etc.) and specific variables " |
| "(<var>ACTIONNAM</var>, <var>ACTIONVAL</var>, etc.) that can be used on " |
| "action execution environment only." |
| msgstr "" |
| |
| |
| msgid "" |
| "The action execution environment exists to perform the script actions " |
| "themselves. It is here where we perform content rendition, content " |
| "documentation, content localization and whatever action you plan for the " |
| "<code>centos-art.sh</code> script to perform. For example, if you passed the " |
| "<code>render</code> value as first argument to <code>centos-art.sh</code> " |
| "command-line, the script performs the content rendition action through the " |
| "<code>render</code> function which is defined in the <tt>`render.sh'</tt> " |
| "file under <tt>`trunk/Scripts/Functions/Render'</tt> directory. Is there, " |
| "inside <code>render</code> functionality were the action execution " |
| "environment takes place exactly." |
| msgstr "" |
| |
| |
| msgid "Command-line interface" |
| msgstr "" |
| |
| |
| msgid "" |
| "When the <code>centos-art</code> command is executed in a bash terminal, the " |
| "bash interpreter uses the <code>PATH</code> environment variable to find " |
| "where such command is. In order to run the <code>centos-art</code>, it must " |
| "exist either as a link to an executable file or an executable file by its " |
| "own, in any of the paths provided by <code>PATH</code> environment variable. " |
| "Otherwise, the bash interpreter will print an error message and prompt you " |
| "back to type a valid command." |
| msgstr "" |
| |
| |
| msgid "" |
| "By default, after installing The CentOS Distribution, there is no " |
| "<code>centos-art</code> command available in the <code>PATH</code> " |
| "environment variable for you to execute. The <code>centos-art</code> command " |
| "is made available in your workstation as result of executing the " |
| "<code>prepare</code> functionality of <code>centos-art.sh</code> script (see " |
| "section <a href=\"repository_52.xhtml#SEC292\">The <tt>`trunk/Scripts/" |
| "Functions/Prepare'</tt> Directory</a>) which requires you had previously " |
| "downloaded a working copy of CentOS Artwork Repository in your workstation." |
| msgstr "" |
| |
| |
| msgid "" |
| "When the <code>centos-art</code> is executed, the first positional parameter " |
| "passed is required and represents the name of the function you want to " |
| "perform (e.g., <code>render</code> for content rendition, <code>locale</" |
| "code> for content localization, etc.). Beyond the first positional parameter " |
| "you can provide either option or non-option parameters in no specific order. " |
| "There are also, option parameters with arguments and without arguments. " |
| "Frequently, non-option paramters are used to specify the path location " |
| "inside the repository where the function will be performed in (e.g., the " |
| "directory structure do you want to produce content for) and option " |
| "parameters to specify how such functionality is performed (e.g., do you want " |
| "to go quietly? do you want to do filtering? etc.)." |
| msgstr "" |
| |
| |
| msgid "" |
| "A B C D E ---------- ------- ----------- ---------------- ------- centos-art " |
| "funcnam path/to/dir --filter='regex' --quiet ---------- ------- ----------- " |
| "---------------- ------- A = The centos-art.sh script command-line. B = The " |
| "centos-art.sh function name. C = Non-option parameter. D = Option parameter " |
| "(with argument). E = Option parameter (without argument)." |
| msgstr "" |
| |
| |
| msgid "Parsing command-line options" |
| msgstr "" |
| |
| |
| msgid "" |
| "The action of parsing options is performed through <code>getopt</code> and " |
| "results particularly interesting. <code>getopt</code> breaks up (parse) " |
| "options in command lines and checks for legal options using the GNU " |
| "<code>getopt</code> routines to do this. One important consideration on " |
| "<code>centos-art.sh</code> script design is that positional parameters are " |
| "retrived in the <code>cli</code> function but parsed on each specific " |
| "function, individually. There isn't a big parsing definition to cover all " |
| "specific functions, but one parsing definitions for each specific functions." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_49.xhtml#SEC261\">The <tt>`trunk/Scripts/" |
| "Functions'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_47.xhtml#SEC248\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_49.xhtml#SEC261\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.40 The <tt>`trunk/Scripts'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "This section provides the automation work line. The automation work line " |
| "exists to standardize content production in CentOS Artwork Repository. There " |
| "is no need to type several tasks, time after time, if they can be programmed " |
| "into just one executable script." |
| msgstr "" |
| |
| |
| msgid "" |
| "In this section you'll find how to organize and extend the <code>centos-art." |
| "sh</code> script, a bash scripts specially designed to automate most " |
| "frequent tasks in the repository (e.g., image rendition, documenting " |
| "directory structures, translating content, etc.). If you can't resist the " |
| "idea of automating repeatable tasks, then take a look here." |
| msgstr "" |
| |
| |
| msgid "" |
| "The best way to understand the <code>centos-art.sh</code> script is studying " |
| "and improving its source code. However, as start point, you may prefer to " |
| "read an introductory resume before diving into the source code details. In " |
| "this section we identify the different parts the <code>centos-art.sh</code> " |
| "script is made of and how these parts interact one another." |
| msgstr "" |
| |
| |
| msgid "Execution environments" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.40 The trunk/Scripts Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>centos-art.sh</code> script is basically made of four execution " |
| "environments which are named <em>script</em>, <em>global</em>, <em>specific</" |
| "em> and <em>action</em>. These execution environments are nested one into " |
| "another and provide different definition levels for variables and functions. " |
| "In this design, variables and functions defined in higher execution " |
| "environments are available on lower execution environments, but variables " |
| "and functions defined in lower execution environments are not available for " |
| "higher execution enviroments." |
| msgstr "" |
| |
| |
| msgid "" |
| "+----------------------------------------------------------------------+ | " |
| "[centos@host]$ centos-art function path/to/dir --option='value' | " |
| "+----------------------------------------------------------------------+ | ~/" |
| "bin/centos-art --> ~/artwork/trunk/Scripts/centos-art.sh | +---" |
| "v--------------------------------------------------------------v---+ | " |
| "centos-art.sh | +---v------------------------------------------------------" |
| "v---+ . | cli $@ | . . +---v----------------------------------------------" |
| "v---+ . . . | cli_getFunctions | . . . . +---" |
| "v--------------------------------------v---+ . . . . . | function " |
| "| . . . . . . +---v------------------------------v---+ . . . . . . . | " |
| "function_getOptions | . . . . . . . . | function_doSomething " |
| "| . . . . . . . . +------------------------------" |
| "+ . . . . . . . . . . . . . . . . Execution environment " |
| "(action) . . . . . . . ........................................ . . . . . . . . . . . . " |
| "Execution environment " |
| "(specific) . . . . . ................................................ . . . . . . . . " |
| "Execution environment " |
| "(global) . . . ........................................................ . . . . " |
| "Execution environment " |
| "(script) . ................................................................" |
| msgstr "" |
| |
| |
| msgid "" |
| "#!/bin/bash # # greet.sh -- This function outputs different kind of " |
| "greetings to # your screen. Use this function to understand how centos-art." |
| "sh # script specific functionalities work. # # Copyright (C) YEAR " |
| "YOURFULLNAME # # 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. # " |
| "---------------------------------------------------------------------- # $Id" |
| "$ # ---------------------------------------------------------------------- " |
| "function greet { # Define command-line interface. greet_getOptions # Execute " |
| "action name. if [[ $ACTIONNAM =~ \"^${FUNCNAM}_[A-Za-z]+$\" ]];then eval " |
| "$ACTIONNAM else cli_printMessage \"`gettext \"A valid action is required.\"`" |
| "\" 'AsErrorLine' cli_printMessage \"${FUNCDIRNAM}\" 'AsToKnowMoreLine' fi }" |
| msgstr "" |
| |
| |
| msgid "" |
| "The first definition inside <code>greet</code> function is for variables " |
| "that will be available along the whole execution environment of <code>greet</" |
| "code> function. This time we didn't define any variable here so, we " |
| "continued with definition of command-line interface, through " |
| "<code>greet_getOptions</code> function." |
| msgstr "" |
| |
| |
| msgid "" |
| "The command-line interface of <code>greet</code> functionality defines how " |
| "to interpret arguments passed from <code>centos-art.sh</code> script command-" |
| "line. Inside <code>centos-art.sh</code> script, the interpretation of " |
| "arguments passed through its command-line takes place by mean of " |
| "<code>getopt</code> command and is written as the following code example " |
| "describes:" |
| msgstr "" |
| |
| |
| msgid "" |
| "function greet_getOptions { # Define short options we want to support. local " |
| "ARGSS=\"\" # Define long options we want to support. local ARGSL=\"hello:," |
| "bye:,quiet\" # Redefine ARGUMENTS variable using getopt output. " |
| "cli_doParseArguments # Redefine positional parameters using ARGUMENTS " |
| "variable. eval set -- \"$ARGUMENTS\" # Look for options passed through " |
| "command-line. while true; do case \"$1\" in --hello ) ACTIONNAM=\"${FUNCNAM}" |
| "_sayHello\" ACTIONVAL=\"$2\" shift 2 ;; --bye ) ACTIONNAM=\"${FUNCNAM}" |
| "_sayGoodbye\" ACTIONVAL=\"$2\" shift 2 ;; --quiet ) FLAG_QUIET='true' shift " |
| "1 ;; -- ) # Remove the `--' argument from the list of arguments # in order " |
| "for processing non-option arguments # correctly. At this point all option " |
| "arguments have # been processed already but the `--' argument still # " |
| "remains to mark ending of option arguments and # begining of non-option " |
| "arguments. The `--' argument # needs to be removed here in order to avoid # " |
| "centos-art.sh script to process it as a path inside # the repository, which " |
| "obviously is not. shift 1 break ;; esac done # Redefine ARGUMENTS variable " |
| "using current positional parameters. cli_doParseArgumentsReDef \"$@\" }" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>greet_sayHello</code> and <code>greet_sayGoodbye</code> function " |
| "definitions are the core of <code>greet</code> specific functionality. In " |
| "such function definitions we set what our <code>greet</code> function really " |
| "does: to output different kinds of greetings." |
| msgstr "" |
| |
| |
| msgid "" |
| "function greet_sayHello { cli_printMessage \"`gettext \"Hello\"`, $ACTIONVAL" |
| "\" }" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>greet_sayHello</code> function definition is stored in " |
| "<tt>`greet_sayHello.sh'</tt> function script." |
| msgstr "" |
| |
| |
| msgid "" |
| "function greet_sayGoodbye { cli_printMessage \"`gettext \"Goodbye\"`, " |
| "$ACTIONVAL\" }" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>greet_sayGoodbye</code> function definition is stored in the " |
| "<tt>`greet_sayGoodbye.sh'</tt> function script." |
| msgstr "" |
| |
| |
| msgid "Executing the <code>greet</code> functionality" |
| msgstr "" |
| |
| |
| msgid "" |
| "To execute the <code>greet</code> specific functionality we've just created, " |
| "pass the function name (i.e., <code>greet</code>) as first argument to " |
| "<tt>`centos-art.sh'</tt> script and any of the valid options after it. Some " |
| "examples are illustrated below:" |
| msgstr "" |
| |
| |
| msgid "" |
| "[centos@projects ~]$ centos-art greet --hello='World' Hello, World " |
| "[centos@projects ~]$ centos-art greet --bye='World' Goodbye, World " |
| "[centos@projects ~]$ centos-art greet --bye='World' --quiet [centos@projects " |
| "~]$" |
| msgstr "" |
| |
| |
| msgid "" |
| "The word <samp>`World'</samp> in the examples above can be anything. " |
| "Likewise, if you need to change the way either the hello or goodbye messages " |
| "are printed out, you can modifie the functions <code>greet_sayHello</code> " |
| "and <code>greet_sayGoodbye</code>, respectively." |
| msgstr "" |
| |
| |
| msgid "Documenting the <code>greet</code> functionality" |
| msgstr "" |
| |
| |
| msgid "" |
| "Now that <code>greet</code> functionality works as we expect, it is time to " |
| "document it. To document functionalities inside <code>centos-art.sh</code> " |
| "script we use the function directory path as argument to the <code>help</" |
| "code> functionality (see section <a href=\"repository_50.xhtml#SEC272\">The " |
| "<tt>`trunk/Scripts/Functions/Help'</tt> Directory</a>) of <tt>`centos-art." |
| "sh'</tt> script, just as the following command illustrates:" |
| msgstr "" |
| |
| |
| msgid "centos-art help --edit trunk/Scripts/Functions/Greet" |
| msgstr "" |
| |
| |
| msgid "" |
| "The function documentation helps to understand how the function really works " |
| "and how it should be used. Also, when <code>centos-art.sh</code> script ends " |
| "because an error, the documentation entry related to the functionality being " |
| "currently executed is used as vehicle to communicate the user what is the " |
| "correct way of using the functionality." |
| msgstr "" |
| |
| |
| msgid "Localizing the <code>greet</code> functionality" |
| msgstr "" |
| |
| |
| msgid "" |
| "Now that <code>greet</code> functionality has been documented, it is time to " |
| "localize its output messages. Localizing specific functionalities of " |
| "<code>centos-art.sh</code> script takes place as part of <code>centos-art." |
| "sh</code> script localization itself which is performed by applying the path " |
| "<tt>`trunk/Scripts'</tt> to the <code>locale</code> functionality of " |
| "<code>centos-art.sh</code> script." |
| msgstr "" |
| |
| |
| msgid "" |
| "As the <code>greet</code> functionality added new translatable strings to " |
| "the <code>centos-art.sh</code> script, it is required to update the " |
| "translation messages firstly, to add the new translatable strings from " |
| "<code>greet</code> functionality to <code>centos-art.sh</code> script " |
| "translation messages and then, edit the translation messages of <code>centos-" |
| "art.sh</code> script to localize the new translatable strings that have been " |
| "added. To achieve this, execute the following two commands:" |
| msgstr "" |
| |
| |
| |
| msgid "centos-art locale --update trunk/Scripts" |
| msgstr "" |
| |
| |
| |
| msgid "centos-art locale --edit trunk/Scripts" |
| msgstr "" |
| |
| |
| msgid "" |
| "To translate output messages in different languages, your system locale " |
| "information --as in <code>LANG</code> environment variable-- must be set to " |
| "that locale you want to produce translated messages for. For example, if you " |
| "want to produce translated messages for Spanish language, your system locale " |
| "information must be set to <samp>`es_ES.UTF-8'</samp>, or similar, before " |
| "executing the <code>locale</code> functionality of <code>centos-art.sh</" |
| "code> script." |
| msgstr "" |
| |
| |
| msgid "Well, it seems that our example is rather complete by now." |
| msgstr "" |
| |
| |
| msgid "Extending the <code>greet</code> functionality" |
| msgstr "" |
| |
| |
| msgid "" |
| "In the <code>greet</code> functionality we've described so far, we only use " |
| "<code>cli_printMessage</code> function in action specific function " |
| "definitions in order to print messages, but more interesting things can be " |
| "achieved inside action specific function definitions. For example, if you " |
| "pass a directory path as argument, you could use it to retrive a list of " |
| "files from therein and process them. If the list of files turns too long or " |
| "you just want to control which files to process, so you could add another " |
| "argument in the form <samp>`--filter='regex''</samp> and reduce the list of " |
| "files to process using a regular expression pattern." |
| msgstr "" |
| |
| |
| msgid "" |
| "In case you consider to extend the <code>greet</code> functionality to do " |
| "something different but print out grettings, consider changing the function " |
| "name from <code>greet</code> to something more appropriate, as well. The " |
| "name change must be coherent with the actions the new function is designed " |
| "to perform." |
| msgstr "" |
| |
| |
| msgid "" |
| "If you doubt what name is better for your functionality, write to <a class=" |
| "\"mailto\" href=\"mailto:centos-devel@centos.org\">centos-devel@centos.org</" |
| "a> mailing list, explain what your functionality intends to do and request " |
| "suggestion about what name would be more appropriate for it. That would be " |
| "also very convenient for you, in order to evaluate the purposes of your " |
| "function and what the community thinks about it. It is a way for you to " |
| "gather ideas that help you to write using the community feeling as base." |
| msgstr "" |
| |
| |
| msgid "" |
| "If your function passes the community evaluation, that is a good sign for " |
| "you to start/keep writing it. However, if it doesn't, it is time for you to " |
| "rethink what you are doing and ask again until it passes the community " |
| "evaluation. You can considered you've passed the community evaluation when " |
| "after proposing your idea, you get a considerable amount of possitve " |
| "responses for what you are doing, specially if those responses come from " |
| "community leaders." |
| msgstr "" |
| |
| |
| msgid "" |
| "It is very hard to do something useful for a community of people without any " |
| "point of contact with that community you are trying to do things for. How " |
| "could you know you are doing something that is needed if you don't know what " |
| "the needs are? So, explore the community needs first, define them, work them " |
| "out and repeat the process time after time, even when you might think the " |
| "need has been already satisfied. At that point, surely, you'll find smaller " |
| "needs that need to be satisfied, as well." |
| msgstr "" |
| |
| |
| msgid "Conclusions" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_48.xhtml#SEC253\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>greet</code> functionality described in this section may serve as " |
| "introduction for you to understand how specific functionalities are created " |
| "inside <tt>`centos-art.sh'</tt> script. With some of luck this introduction " |
| "will also serve you as motivation to create your own specific " |
| "functionalities for <tt>`centos-art.sh'</tt> script." |
| msgstr "" |
| |
| |
| msgid "" |
| "By the way, the <code>greet</code> functionality doesn't exist inside " |
| "<tt>`centos-art.sh'</tt> script yet. Would you like to create it?" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_50.xhtml#SEC272\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "The following specific functions of <tt>`centos-art.sh'</tt> script, are " |
| "available for you to use:" |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_52.xhtml#SEC292\">The <tt>`trunk/Scripts/" |
| "Functions/Prepare'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_53.xhtml#SEC305\">The <tt>`trunk/Scripts/" |
| "Functions/Render'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_54.xhtml#SEC320\">The <tt>`trunk/Scripts/" |
| "Functions/Tuneup'</tt> Directory</a>." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| msgid "The <tt>`trunk/Scripts'</tt> Directory" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.41 The <tt>`trunk/Scripts/Functions'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Scripts/Functions'</tt> directory exists to organize " |
| "<tt>`centos-art.sh'</tt> specific functionalities." |
| msgstr "" |
| |
| |
| msgid "" |
| "The specific functions of <tt>`centos-art.sh'</tt> script are designed with " |
| "the \"Software Toolbox\" philosophy (See <a href=\"../coreutils/Toolbox-" |
| "introduction.html#Toolbox-introduction\">(coreutils.info)Toolbox " |
| "introduction</a>) in mind: each program \"should do one thing well\". Inside " |
| "<tt>`centos-art.sh'</tt> script, each specific functionality is considered a " |
| "program that should do one thing well. Of course, if you find that they " |
| "still don't do it, feel free to improve them in order for them to do so." |
| msgstr "" |
| |
| |
| msgid "" |
| "The specific functions of <tt>`centos-art.sh'</tt> script are organized " |
| "inside specific directories under <tt>`trunk/Scripts/Functions'</tt> " |
| "location. Each specific function directory should be named as the function " |
| "it represents, with the first letter in uppercase. For example, if the " |
| "function name is <code>render</code>, the specific function directory for it " |
| "would be <samp>`trunk/Scripts/Functions/Render'</samp>." |
| msgstr "" |
| |
| |
| msgid "Creating the <code>greet</code> functionality" |
| msgstr "" |
| |
| |
| msgid "" |
| "To better understand how to design specific functions for <tt>`centos-art." |
| "sh'</tt> script, let's create the <code>greet</code> functionality which " |
| "only goal is to print out different kind of greetings to your screen. The " |
| "<code>greet</code> functionality will be set using the follwiing directory " |
| "structure:" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.41 The trunk/Scripts/Functions Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "trunk/Scripts/Functions/Greet <-- The source location of greet function. " |
| "|-- greet_getOptions.sh <-- Defines command-line interface. |-- " |
| "greet_sayGoodbye.sh <-- Defines specific action. |-- greet_sayHello.sh " |
| "<-- Defines specific action. `-- greet.sh <-- Defines function " |
| "initialization." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`greet.sh'</tt> file contains the initialization script of " |
| "<code>greet</code> functionality. It is the first file loaded from function " |
| "source location by <code>centos-art.sh</code> script when it is executed " |
| "using the <code>greet</code> functionality as first argument." |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside <tt>`centos-art.sh'</tt> script, as convenction, each function script " |
| "has one top commentary, followed by one blank line, and then one function " |
| "defintion below it only. The top commentary has the function description, " |
| "one-line for copyright notice with your personal information, the license " |
| "under which the function source code is released --the <tt>`centos-art.sh'</" |
| "tt> script is released as GPL, so do all its functions-- and the <code>$Id$</" |
| "code> keyword of Subversion which is later expanded by <code>svn propset</" |
| "code> command. In our example, the top comment of <code>greet.sh</code> " |
| "function script would look like the following:" |
| msgstr "" |
| |
| |
| msgid "" |
| "To use <kbd>TAB</kbd> completion to list particular files in a directory, " |
| "type <code>ls</code>, then a character, and finally the Tab key. Your " |
| "terminal displays the list of files in the working directory that begin with " |
| "that character." |
| msgstr "" |
| |
| |
| msgid "key-combination" |
| msgstr "" |
| |
| |
| msgid "A combination of keystrokes is represented in this way. For example:" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <kbd>Ctrl-Alt-Backspace</kbd> 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:" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>ls</code> command displays the contents of a directory. For " |
| "example:" |
| msgstr "" |
| |
| |
| msgid "" |
| "Config help_renameEntry.sh help_copyEntry.sh help_restoreCrossReferences.sh " |
| "help_deleteCrossReferences.sh help_searchIndex.sh" |
| 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 "" |
| "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 <tt>`/usr/share/doc/'</tt> 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 "" |
| "[<a href=\"repository_4.xhtml#SEC14\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_6.xhtml#SEC18\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "In this manual the personal pronoun <em>we</em> is used to repesent <em>The " |
| "CentOS Artwork SIG</em>. This is, the group of persons building the CentOS " |
| "Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "In this manual, certain words are represented in different fonts, typefaces, " |
| "sizes, and weights. This highlighting is systematic; different words are " |
| "represented in the same style to indicate their inclusion in a specific " |
| "category. The types of words that are represented this way include the " |
| "following:" |
| msgstr "" |
| |
| |
| msgid "command" |
| msgstr "" |
| |
| |
| msgid "" |
| "Linux commands (and other operating system commands, when used) are " |
| "represented this way. This style should indicate to you that you can type " |
| "the word or phrase on the command line and press Enter to invoke a command. " |
| "Sometimes a command contains words that would be displayed in a different " |
| "style on their own (such as file names). In these cases, they are considered " |
| "to be part of the command, so the entire phrase is displayed as a command. " |
| "For example:" |
| msgstr "" |
| |
| |
| msgid "" |
| "Use the <code>centos-art identity --render='path/to/dir'</code> command to " |
| "produce contents inside the <tt>`trunk/Identity'</tt> directory structure." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 1.4 Document Convenctions" |
| 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 <tt>`init.sh'</tt> file in <tt>`trunk/Scripts/Bash/Cli/'</tt> directory " |
| "is the initialization script, written in Bash, used to automate most of " |
| "tasks in the repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>centos-art</code> command uses the <tt>`ImageMagick'</tt> 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 "" |
| "The <tt>`path/to/dir'</tt> must point to any directory inside the " |
| "repository. When more than one <tt>`path/to/dir'</tt> are passed as non-" |
| "option arguments to the <code>centos-art.sh</code> 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 <code>EDITOR</code> " |
| "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 \"path/to/dir\"'" |
| msgstr "" |
| |
| |
| msgid "" |
| "Read documentation entry specified by <tt>`file/to/dir'</tt> path, using " |
| "<code>info</code> command. This option is useful to read the repository " |
| "manual on text-based terminals. This option is also used internally by " |
| "<code>centos-art.sh</code> script to print out the reference you can follow " |
| "to know more about an error message." |
| msgstr "" |
| |
| |
| |
| msgid "`--update'" |
| msgstr "" |
| |
| |
| msgid "Update output files rexporting them from Texinfo source files." |
| msgstr "" |
| |
| |
| msgid "`--copy \"path/to/file.texi\" \"path/to/dir\"'" |
| msgstr "" |
| |
| |
| msgid "" |
| "Duplicate documentation entries under <tt>`trunk/Manual'</tt> directory " |
| "structure." |
| msgstr "" |
| |
| |
| msgid "" |
| "When documentation entries are copied, it is possible to pass more than one " |
| "Texinfo file as source location. In this case, they all and their dependent " |
| "files will be copied into the target location. The target location must be a " |
| "directory and passed as last non-option argument in the command-line." |
| msgstr "" |
| |
| |
| msgid "`--delete \"path/to/file.texi\"'" |
| msgstr "" |
| |
| |
| msgid "" |
| "Delete documentation entries under <tt>`trunk/Manual'</tt> directory " |
| "structure." |
| msgstr "" |
| |
| |
| msgid "" |
| "When documentation entries are deleted, all cross references that point to " |
| "the deleted documentation entry will be rebuilt to remove Texinfo markup and " |
| "remark the fact that it had been removed indeed from the repository." |
| msgstr "" |
| |
| |
| msgid "`--rename \"path/to/file.texi\" \"path/to/file.texi\"'" |
| msgstr "" |
| |
| |
| msgid "" |
| "Rename documentation entries under <tt>`trunk/Manual'</tt> directory " |
| "structure." |
| msgstr "" |
| |
| |
| msgid "" |
| "When documentation entries are removed (e.g., through <samp>`--delete'</" |
| "samp> or <samp>`--rename'</samp> options), the <code>centos-art.sh</code> " |
| "script takes care of updating nodes, menus and cross references related to " |
| "documentation entries in order to keep the manual structure in a correct " |
| "state." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Project corporate identity is organized through directories in " |
| "The CentOS Artwork Repository. Each directory inside the repository responds " |
| "to conceptual ideas and uses files to get the implementation of those ideas. " |
| "The <code>help</code> functionality of <code>centos-art.sh</code> script " |
| "uses this directory layout as reference to document the conceptual ideas it " |
| "is based on. Each directory inside the repository can be documented, in " |
| "order to provide the explanation of what it is for and how automation " |
| "scripts use it." |
| msgstr "" |
| |
| |
| msgid "" |
| "When the repository directory layout changes, the documentation layout " |
| "related must be changed as well in order for both locations to be consistent " |
| "in their paths. Otherwise, you may end up having documentation entries that " |
| "point to unexistent directories in the repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "Files inside the repository are not documented. The only exception to this " |
| "rule are files under <tt>`trunk/Manual'</tt> directory, the place where " |
| "documentation source files are stored in. Inside this location you can refer " |
| "<tt>`.texi'</tt> files for direct actions using the <code>help</code> " |
| "functionality of <code>centos-art.sh</code> script. File actions, in this " |
| "location, are also used to manage specific parts of the manual which have no " |
| "association outside <tt>`trunk/Manual'</tt> directory (e.g., Preface, " |
| "Introduction, etc.)." |
| msgstr "" |
| |
| |
| msgid "" |
| "The manual structure (see section <a href=\"repository_44.xhtml#SEC231\">The " |
| "<tt>`trunk/Manual'</tt> Directory</a>) is supported by GNU Texinfo, a " |
| "documentation system that can produce both online information and a printed " |
| "manual from a single source. The <code>help</code> functionality is an " |
| "interface you can use to control the source files in the manual structure." |
| msgstr "" |
| |
| |
| msgid "" |
| "The manual output files is produced from Texinfo files and stored in " |
| "<tt>`trunk/Manual'</tt> on different formats including Info, Pdf, XHTML, XML " |
| "and TXT." |
| msgstr "" |
| |
| |
| msgid "" |
| "Whatever your prefered language be, you'll always edit documentation entries " |
| "in English language and so will be the output produced from them, when you " |
| "use the <code>help</code> functionality of <code>centos-art.sh</code> " |
| "script. However, you can achieve the manual localization to your prefered " |
| "language by applying the <code>locale</code> functionality of <code>centos-" |
| "art.sh</code> script (see section <a href=\"repository_51.xhtml#SEC281\">The " |
| "<tt>`trunk/Scripts/Functions/Locale'</tt> Directory</a>) to any of the XML-" |
| "based English outputs supported by <code>centos-art.sh</code> script (e.g., " |
| "XHTML and Docbook) to produce portable objects for your prefered language " |
| "and the <code>render</code> functionality of <code>centos-art.sh</code> " |
| "script (see section <a href=\"repository_53.xhtml#SEC305\">The <tt>`trunk/" |
| "Scripts/Functions/Render'</tt> Directory</a>) to produce the translated " |
| "version of the output XHTML files taken in first place. The translated " |
| "version is produced in the same format of the file taken as reference to " |
| "build the portable objects. XHTML format in this case." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "Examples" |
| msgstr "" |
| |
| |
| msgid "centos-art help --edit trunk/Identity" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command edits the documentation entry related to <tt>`trunk/Identity'</" |
| "tt> directory." |
| msgstr "" |
| |
| |
| msgid "centos-art help --read trunk/Identity" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command reads the doumentation entry related to <tt>`trunk/Identity'</" |
| "tt> directory in info format." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "Author" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "Written by Alain Reguera Delgado." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "Reporting bugs" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "Report bugs to <a class=\"mailto\" href=\"mailto:centos-artwork@centos.org" |
| "\">centos-artwork@centos.org</a> mailing list." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "Copyright" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "This is free software. You may redistribute copies of it under the terms of " |
| "the GNU General Public License (see section <a href=\"repository_56." |
| "xhtml#SEC333\">GNU General Public License</a>). There is NO WARRANTY, to the " |
| "extent permitted by law." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "The <tt>`trunk/Scripts/Functions'</tt> Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_49.xhtml#SEC261\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_51.xhtml#SEC281\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.42 The <tt>`trunk/Scripts/Functions/Help'</tt> Directory" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| msgid "Name" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>help</code> functionlity is part of <code>centos-art.sh</code> " |
| "script and standardizes documentation tasks inside the working copy of " |
| "CentOS Artwork Repository." |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "Synopsis" |
| msgstr "" |
| |
| |
| msgid "centos-art help [OPTIONS] path/to/dir …" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "The <tt>`path/to/dir'</tt> parameter specifies what directory structure " |
| "inside the working copy of CentOS Artwork Repository you want to process." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>help</code> functionality of <code>centos-art.sh</code> script " |
| "accepts the following options:" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "`--quiet'" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "Supress all output messages except error messages. When this option is " |
| "passed, all confirmation requests are supressed as well and a possitive " |
| "answer is assumed for them, just as if the <samp>`--answer-yes'</samp> " |
| "option had been provided." |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.42 The trunk/Scripts/Functions/Help Directory" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "`--answer-yes'" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "Assume `yes' to all confirmation requests." |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "`--dont-commit-changes'" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "" |
| "Supress all commit and update actions realized over files, before and after " |
| "the action itself had took place over files in the working copy." |
| msgstr "" |
| |
| |
| msgid "`--search=\"STRING\"'" |
| msgstr "" |
| |
| |
| msgid "Go to node pointed by index entry <samp>`STRING'</samp>." |
| msgstr "" |
| |
| |
| msgid "`--edit \"path/to/dir\"'" |
| msgstr "" |
| |
| |
| msgid "" |
| "Edit documentation entry related to path specified by <tt>`path/to/dir'</tt>." |
| msgstr "" |
| |
| |
| msgid "" |
| "This option extracts translatable strings from both XML-based files (using " |
| "<code>xml2po</code>) and shell scripts (using <code>xgettext</code>) under " |
| "<tt>`path/to/dir'</tt>. Translatable strings are initially stored in " |
| "portable objects templates (.pot) which are later merged into portable " |
| "objects (.po) in order to be converted as machine objects (.mo)." |
| msgstr "" |
| |
| |
| msgid "" |
| "Use this option each time you change translatable stirngs inside design " |
| "models and script files." |
| msgstr "" |
| |
| |
| msgid "`--edit'" |
| msgstr "" |
| |
| |
| msgid "" |
| "This option edits the portable object related to <tt>`path/to/dir'</tt> " |
| "location." |
| msgstr "" |
| |
| |
| msgid "" |
| "Use this option after updating portable objects (through <samp>`--update'</" |
| "samp> option) in order to change the language-specific information of " |
| "translatable strings." |
| msgstr "" |
| |
| |
| msgid "`--dont-create-mo'" |
| msgstr "" |
| |
| |
| msgid "This option supresses the creation of machine objects." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Artwork Repository exists to cover the visual needs of The CentOS " |
| "Project Corporate Identity. The CentOS Project is an internationl project " |
| "and sometimes requires contents in different languages. So, in that sake, " |
| "the CentOS Artwork Repository is designed to produce content in as many " |
| "locales as supported by The CentOS Distribution, the platform that supports " |
| "the whole CentOS Artwork Repository, both in workstations and server." |
| msgstr "" |
| |
| |
| msgid "" |
| "To know what locales are supported by The CentOS Distribution you are " |
| "currently using, run the following command:" |
| msgstr "" |
| |
| |
| msgid "locale -a | less" |
| msgstr "" |
| |
| |
| msgid "" |
| "The localization process is very tied to the input files we want to provide " |
| "localized messages for. Inside the CentOS Artwork Repository, it is possible " |
| "to localize XML files (e.g., SVG, XHTML, Docbook) and programs written in " |
| "most popular programming languages (e.g., C, C++, C#, Shell Scripts, Python, " |
| "Java, GNU awk, PHP, etc.)." |
| msgstr "" |
| |
| |
| msgid "Design models localization" |
| msgstr "" |
| |
| |
| msgid "" |
| "Design models are used as input to produce most images and some other " |
| "contents as well. Design models are always XML-based files (e.g., SVG, " |
| "XHTML, Docbook), so the <code>locale</code> functionality uses the " |
| "<code>xml2po</code> program to create protable objects from them under " |
| "<tt>`trunk/Locales/Models'</tt> directory. Portable objects contain the " |
| "relation between message id and message translation, as translator, need to " |
| "take care of." |
| msgstr "" |
| |
| |
| msgid "" |
| "Thanks to <code>xml2po</code>, it is possible for the <code>locale</code> " |
| "functionality to separate designing tasks from the translating tasks. It is " |
| "possible for graphic designers to concentrate their efforts on designing " |
| "models in English language while translators take care of their localization " |
| "using the <samp>`--update'</samp> and <samp>`--edit'</samp> options as much " |
| "as it be needed." |
| msgstr "" |
| |
| |
| msgid "" |
| "Once design models have been localized, rendering them in different language " |
| "is a matter using the <code>render</code> functionality of <code>centos-art." |
| "sh</code> script. See section <a href=\"repository_53.xhtml#SEC305\">The " |
| "<tt>`trunk/Scripts/Functions/Render'</tt> Directory</a>, for more " |
| "information about it." |
| msgstr "" |
| |
| |
| msgid "Shell script localization" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>locale</code> functionality is used to localize the <code>centos-" |
| "art.sh</code> script itself. The <code>centos-art.sh</code> script is a " |
| "shell script written in Bash, so the <code>locale</code> functionality uses " |
| "the <code>gettext</code> tools to retrive translatable strings, create " |
| "portable objects and machine objects." |
| msgstr "" |
| |
| |
| msgid "" |
| "Thanks to <code>gettext</code>, it is possible for the <code>locale</code> " |
| "functionality to separate programming tasks from the translating tasks. It " |
| "is possible for programmer to concentrate their efforts in programming " |
| "output messages in English language while translators take care of their " |
| "localization using the <samp>`--update'</samp> and <samp>`--edit'</samp> " |
| "options as much as it be needed." |
| msgstr "" |
| |
| |
| msgid "" |
| "Once <code>centos-art.sh</code> script has been localized, the translated " |
| "messages should be immediatly visible to you, the next time you execute the " |
| "<code>centos-art.sh</code> script" |
| msgstr "" |
| |
| |
| msgid "" |
| "In order to localize translatable strings from English language to another " |
| "language you need to be sure the <code>LANG</code> environment variable has " |
| "been already set to the locale code you want to localize message for or see " |
| "them printed out before running the <code>centos-art.sh</code> script. " |
| "Localizing English language to itself is not supported." |
| msgstr "" |
| |
| |
| msgid "" |
| "centos-art locale --update trunk/Identity/Models/Default/Distro/5/Anaconda" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command updates portable objects related to Anaconda default design " |
| "models of The CentOS Distribution major release 5. The update action " |
| "consists on adding new translatable strings or removing old translatable " |
| "strings from portable objects in order to keep both the portable object and " |
| "the design model consistent." |
| msgstr "" |
| |
| |
| msgid "" |
| "This command is executed by translators once the graphic designers have " |
| "committed updates to Anaconda default design models (e.g., slide text " |
| "changes)." |
| msgstr "" |
| |
| |
| msgid "" |
| "centos-art locale --edit trunk/Identity/Models/Default/Distro/5/Anaconda" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command let translators to edit portable objects related to Anaconda " |
| "default design models of The CentOS Distribution major release 5. The edit " |
| "action is where the translator localize translatable strings in English " |
| "language to another language." |
| msgstr "" |
| |
| |
| msgid "" |
| "When portable objects for XML-base files are produced, there is no need to " |
| "retain the machine object format, so we the <samp>`--dont-create-mo'</samp> " |
| "is automatically assumed." |
| msgstr "" |
| |
| |
| msgid "" |
| "This command updates portable objects related to <code>centos-art.sh</code> " |
| "script. The update action consists on adding new translatable strings or " |
| "removing old translatable strings from portable objects in order to keep " |
| "both the portable object and the <code>centos-art.sh</code> script to be " |
| "consistent one another." |
| msgstr "" |
| |
| |
| msgid "" |
| "This command is executed by translators once the programmers have committed " |
| "updates <code>centos-art.sh</code> script." |
| msgstr "" |
| |
| |
| msgid "" |
| "This command edits portable objects related to <code>centos-art.sh</code> " |
| "script in your prefered language." |
| msgstr "" |
| |
| |
| msgid "centos-art locale --update trunk/Manual/repository.xhtml" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command updates portable objects for the XHTML output of the repository " |
| "documentation manual. The portable objects are created in your prefered " |
| "language and can be used to produced localized versions of the manual in " |
| "XHTML format." |
| msgstr "" |
| |
| |
| msgid "" |
| "The update action consists on adding new translatable strings to or removing " |
| "old translatable strings from the portable objects in order to keep both the " |
| "portable object and the manual XHTML output consistent one another." |
| msgstr "" |
| |
| |
| msgid "" |
| "People execute this command after committing changes to the repository " |
| "documentation manual." |
| msgstr "" |
| |
| |
| msgid "centos-art locale --edit trunk/Manual/repository.xhtml" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command takes all the repository documentation manual XHTML output " |
| "files, which have not been translated yet inside the <tt>`trunk/Manual/" |
| "repository.xhtml'</tt> directory, as input to produce portable objects from " |
| "them so as for you to localize translatable strings to your prefered " |
| "language (e.g., as specified by the <code>LANG</code> environment variable)." |
| msgstr "" |
| |
| |
| msgid "" |
| "Once the portable objects have been created they are used to produce the " |
| "translated version of the manual in XHTML format under the <tt>`trunk/Manual/" |
| "repository.xml/LANG'</tt> directory, where <samp>`LANG'</samp> refers your " |
| "prefered language. The translated version of the XHTML files is produced " |
| "using the <code>render</code> functionality of <code>centos-art.sh</code> " |
| "script (see section <a href=\"repository_53.xhtml#SEC305\">The <tt>`trunk/" |
| "Scripts/Functions/Render'</tt> Directory</a>)." |
| msgstr "" |
| |
| |
| msgid "" |
| "When your prefered language is other but English, the <code>centos-art.sh</" |
| "code> script takes care of updating both the portable objects and the " |
| "translated version of files after you've edited a manual documentation " |
| "entry, using the <code>help</code> functionality of <code>centos-art.sh</" |
| "code> script (see section <a href=\"repository_50.xhtml#SEC272\">The " |
| "<tt>`trunk/Scripts/Functions/Help'</tt> Directory</a>). In other situations, " |
| "you need to do these actions by yourself." |
| msgstr "" |
| |
| |
| msgid "" |
| "The GNU <code>gettext</code> tools documentation (<code>info gettext</code>)" |
| msgstr "" |
| |
| |
| msgid "The <code>xml2po</code> command documentation (<code>man xml2po</code>)" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_50.xhtml#SEC272\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_52.xhtml#SEC292\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.43 The <tt>`trunk/Scripts/Functions/Locale'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>locale</code> functionlity is part of <code>centos-art.sh</code> " |
| "script and standardizes localization tasks inside the working copy of CentOS " |
| "Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "centos-art locale [OPTIONS] path/to/dir" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`path/to/dir'</tt> parameter specifies what directory structure " |
| "inside the working copy of CentOS Artwork Repository you want to create " |
| "translation messages for." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>locale</code> functionality of <code>centos-art.sh</code> script " |
| "accepts the following options:" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.43 The trunk/Scripts/Functions/Locale Directory" |
| msgstr "" |
| |
| |
| |
| |
| msgid "`--filter=\"REGEX\"'" |
| msgstr "" |
| |
| |
| |
| |
| msgid "" |
| "Reduce the list of files to process using <samp>`REGEX'</samp> as pattern. " |
| "You can use this option in combination with <tt>`path/to/dir'</tt> in order " |
| "to control the amount of files you want to produce as base-rendition. The " |
| "deeper you go into the directory structure the more specific you'll be about " |
| "the component you want to produce. When you cannot go deeper into the " |
| "directory structure, you can use <samp>`--filter'</samp> option to reduce " |
| "the list of files." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`inkscape'</tt> package isn't inside The CentOS Distribution or any " |
| "of The CentOS Project repositories neither, so you need to install it from a " |
| "third party repository like <samp>`RPMForge'</samp> or <samp>`EPEL'</samp>. " |
| "See page <a class=\"www\" href=\"http://wiki.centos.org/AdditionalResources/" |
| "Repositories/\">The CentOS Repositories</a>, to know how to configure third " |
| "party repositories in The CentOS Distribution." |
| msgstr "" |
| |
| |
| msgid "`--link'" |
| msgstr "" |
| |
| |
| msgid "" |
| "This option uses symbolic links to install/update the connection between " |
| "components inside the working copy and components outside the working copy. " |
| "Among the components that need to be connected figure out the command-line " |
| "internface of <code>centos-art.sh</code> script; fonts, brushes, palettes " |
| "and patterns used by programs like GIMP and Inkscape; and configuration " |
| "files of text editors." |
| msgstr "" |
| |
| |
| msgid "" |
| "The main purpose of such connection is to adapt the working copy to the " |
| "CentOS Distribution filesystem layout (e.g., <tt>`~/bin'</tt> directory is " |
| "for storing personal programs, <tt>`~/gimp-2.2/brushes'</tt> is for storing " |
| "GIMP brushes for personal use, etc.) and, at the same time, to provide a way " |
| "of sharing changes made to connected components to other workstations (e.g., " |
| "if I update a GIMP brush in my workstation, you'll receive the change the " |
| "next you update your working copy and then will be immediatly available for " |
| "you to use in GIMP)." |
| msgstr "" |
| |
| |
| msgid "`--environment'" |
| msgstr "" |
| |
| |
| msgid "" |
| "Print the name and value of some of the environment variables used by " |
| "<code>centos-art.sh</code> scripts." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>prepare</code> functionality of <code>centos-art.sh</code> script " |
| "is part of the CentOS Artwork Repository. So, in order to execute the " |
| "<code>prepare</code> functionality of <code>centos-art.sh</code> script you " |
| "need to have access to a working copy of CentOS Artwork Repository, first. " |
| "Working copies of CentOS Artwork Repository are downloaded from the source " |
| "repository and made available to you by mean of workstations. A workstation " |
| "is a computer that you install and configure (prepare) to do something. In " |
| "this case, you pick up a computer and prepare it for working on the CentOS " |
| "Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "Installing the workstation" |
| msgstr "" |
| |
| |
| msgid "" |
| "Installing the workstation is the first step you need to do. In this step " |
| "you make your computer functional through an operating system. In this case, " |
| "The Community Enterprise Operating System; which is also know as The CentOS " |
| "Distribution or just CentOS, for short." |
| msgstr "" |
| |
| |
| msgid "" |
| "To install The CentOS Distribution you need to have the installation media " |
| "somehow (e.g., CDs, DVDs, Pendrives, etc.). There are several different ways " |
| "to perform the installation process of CentOS distribution, but generally, " |
| "you put the installation media in your media reader, boot the computer from " |
| "it, and follow the installer intructions. That simple." |
| msgstr "" |
| |
| |
| msgid "" |
| "If you don't have the installation media of CentOS distribution, you need to " |
| "download the ISO files related to the media you plan to use (e.g., CD or " |
| "DVD) and then create the installation media by yourself. The CentOS " |
| "Distribution ISO files can be downloaded from <a class=\"www\" href=\"http://" |
| "mirrors.centos.org/\">http://mirrors.centos.org/</a> and, if you chosen CD " |
| "or DVD as your prefered installation medium, you can burn the ISO files " |
| "using the <code>K3B</code> application so as to create the installation " |
| "media you'll use. Of course, in order to download the ISO files and create " |
| "the installation media, you need to have an already installed CentOS " |
| "workstation where you can realized all the work." |
| msgstr "" |
| |
| |
| msgid "Configuring the workstation" |
| msgstr "" |
| |
| |
| msgid "" |
| "Once you've installed the workstation and it is up and running, login as " |
| "<samp>`root'</samp> user, create a username (e.g., <samp>`centos'</samp>) " |
| "and set a password for it. This is the username you must use for everyday " |
| "work inside your working copy of the CentOS Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "Do not use the <samp>`root'</samp> username for your everyday work inside " |
| "the working copy of CentOS Artwork Repository. It is dangerous and might " |
| "provoke unreversable damages on your workstation." |
| msgstr "" |
| |
| |
| msgid "" |
| "Once you've created the username for your everyday work, there are some " |
| "environment variables that you can customize to fit your personal needs (e." |
| "g., default text editor, default locale information, default time zone " |
| "representation, etc.). To customize these variables you need to edit your " |
| "profile file (i.e., <tt>`~/.bash_profile'</tt>) and set the redefinition " |
| "there. Notice that you may need to logout and then do login again in order " |
| "for the new variable values to take effect." |
| msgstr "" |
| |
| |
| msgid "Default text editor:" |
| msgstr "" |
| |
| |
| msgid "" |
| "The default text editor information is contrlled by the <code>EDITOR</code> " |
| "environment variable. The <tt>`centos-art.sh'</tt> script uses the default " |
| "text editor to edit subversion pre-commit messages, translation files, " |
| "documentation files, script files, and similar text-based files." |
| msgstr "" |
| |
| |
| msgid "" |
| "If <code>EDITOR</code> environment variable is not set, <tt>`centos-art.sh'</" |
| "tt> script uses <tt>`/usr/bin/vim'</tt> as default text editor. Otherwise, " |
| "the following values are recognized by <tt>`centos-art.sh'</tt> script:" |
| msgstr "" |
| |
| |
| msgid "`/usr/bin/vim'" |
| msgstr "" |
| |
| |
| msgid "`/usr/bin/emacs'" |
| msgstr "" |
| |
| |
| msgid "`/usr/bin/nano'" |
| msgstr "" |
| |
| |
| msgid "" |
| "If no one of these values is set in the <code>EDITOR</code> environment " |
| "variable, the <tt>`centos-art.sh'</tt> script uses <tt>`/usr/bin/vim'</tt> " |
| "text editor, the one installed by default in The CentOS Distribution." |
| msgstr "" |
| |
| |
| msgid "Default locale information:" |
| msgstr "" |
| |
| |
| msgid "" |
| "The default locale information is controlled by the <code>LANG</code> " |
| "environment variable. This variable is initially set in the configuration " |
| "process of CentOS distribution installer, specifically in the " |
| "<samp>`Language'</samp> step; or once installed using the <code>system-" |
| "config-language</code> tool." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>centos-art.sh</code> script uses the <code>LANG</code> environment " |
| "variable to determine what language to use for printing output messages. " |
| "Another use of <code>LANG</code> variable inside <code>centos-art.sh</code> " |
| "script is to determine what translation file to update or edit when input " |
| "files are localized." |
| msgstr "" |
| |
| |
| msgid "Default time zone representation:" |
| msgstr "" |
| |
| |
| msgid "" |
| "The time zone representation is a time correction applied to the system time " |
| "(stored in the BIOS clock) based on your country location. This correction " |
| "is specially useful to distributed computers around the world that work " |
| "together and need to be syncronized in time to know when things happened." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Artwork Repository is made of one server and several workstations " |
| "spread around the world. In order for all these workstations to know when " |
| "changes in the server took place, it is required that they all set their " |
| "system clocks to use the same time information (i.e., <acronym title=" |
| "\"Coordinated Universal Time\">UTC</acronym> (Coordinated Universal Time)) " |
| "and set the time correction for their specific countries in the operating " |
| "system. Otherwise, it would be difficult to know when something exactly " |
| "happened." |
| msgstr "" |
| |
| |
| msgid "" |
| "Generally, setting the time information is a straight-forward task and " |
| "configuration tools provided by The CentOS Distribution do cover time " |
| "correction for most of the countries around the world. However, if you need " |
| "a time precision not provided by any of the date and time configuration " |
| "tools provided by The CentOS Distribution then, you need to use the " |
| "<code>TZ</code> environment variable to correct the time information by " |
| "yourself. The format of <code>TZ</code> environment variable is described in " |
| "<tt>`tzset(3)'</tt> manual page." |
| msgstr "" |
| |
| |
| msgid "Downloading the working copy" |
| msgstr "" |
| |
| |
| msgid "" |
| "Once you've configured the workstation, it is time to download the working " |
| "copy of CentOS Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "To download the working copy of CentOS Artwork Repository you need to login " |
| "as your everyday work username (e.g., <samp>`centos'</samp>) and use the " |
| "Subversion client to bring all the files you need to work with down from the " |
| "source location of CentOS Artwork Repository (<a class=\"www\" href=" |
| "\"https://projects.centos.org/svn/artwork/\">https://projects.centos.org/svn/" |
| "artwork/</a>) to your workstation, just as the following command describes:" |
| msgstr "" |
| |
| |
| msgid "svn co https://projects.centos.org/svn/artwork ~/" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command will create the working copy of CentOS Artwork Repository in " |
| "your workstation, specifically in the <tt>`/home/centos/artwork'</tt> " |
| "directory. Note that you only need to execute this command once. After that, " |
| "to keep your working copy up to date, you use the Subversion <code>update</" |
| "code> command instead." |
| msgstr "" |
| |
| |
| msgid "" |
| "In the condition that you don't have Subversion client installed in the " |
| "workstation, then you can install it using the command:" |
| msgstr "" |
| |
| |
| msgid "sudo yum install subversion" |
| msgstr "" |
| |
| |
| msgid "Configuring the working copy" |
| msgstr "" |
| |
| |
| msgid "" |
| "Once you have a working copy of CentOS Artwork Repository in your " |
| "workstation, you can go and run the <code>prepare</code> functionality of " |
| "<code>centos-art.sh</code> script to realize the remaining configuration " |
| "stuff." |
| msgstr "" |
| |
| |
| msgid "" |
| "Assuming this is the very first time you run the <code>centos-art.sh</code> " |
| "script, you'll find that there is no <code>centos-art</code> command-line " |
| "interface for it in your workstation. This is correct. In order to have the " |
| "<code>centos-art</code> command-line in your workstation, you need to run " |
| "the <code>centos-art.sh</code> script using its absolute path:" |
| msgstr "" |
| |
| |
| msgid "~/artwork/trunk/Scripts/centos-art.sh prepare [OPTIONS]" |
| msgstr "" |
| |
| |
| msgid "" |
| "Assuming you've already run the <code>prepare</code> functionality before, " |
| "there is no need for you to use the absolute path again. Instead, you can " |
| "use the <code>centos-art</code> command-line interface directly, as the " |
| "following example describes:" |
| msgstr "" |
| |
| |
| msgid "centos-art.sh prepare [OPTIONS]" |
| msgstr "" |
| |
| |
| msgid "" |
| "Notice that you can execute the <code>prepare</code> functionality more than " |
| "once. This is specially useful to keep the link information syncronized. For " |
| "example, considering you've added new brushes to or removed old brushes from " |
| "your working copy of CentOS Artwork Repository, the link information related " |
| "to those files need to be updated in the <tt>`~/.gimp-2.2/brushes'</tt> " |
| "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 components." |
| msgstr "" |
| |
| |
| msgid "centos-art prepare --packages --link" |
| msgstr "" |
| |
| |
| msgid "" |
| "Preapare both links and packages required to use the working copy of CentOS " |
| "Artwork Repository in the workstation. If required packages are already " |
| "installed this command looks for updates instead." |
| msgstr "" |
| |
| |
| msgid "centos-art prepare --link --quiet" |
| msgstr "" |
| |
| |
| msgid "" |
| "Update connection between the workstation and the working copy of CentOS " |
| "Artwork Repository, using no output." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_51.xhtml#SEC281\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_53.xhtml#SEC305\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.44 The <tt>`trunk/Scripts/Functions/Prepare'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>prepare</code> functionality is part of the <code>centos-art.sh</" |
| "code> script and standardizes configuration of preliminar steps you need to " |
| "follow in order to get your workstation ready for using a working copy of " |
| "CentOS Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "centos-art prepare [OPTIONS]" |
| msgstr "" |
| |
| |
| msgid "" |
| "There is no need to specify <tt>`path/to/dir'</tt> information in this " |
| "functionality. Most actions are performed through options." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>prepare</code> functionality of centos-art.sh script accepts the " |
| "following options:" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.44 The trunk/Scripts/Functions/Prepare Directory" |
| msgstr "" |
| |
| |
| msgid "Assume <samp>`yes'</samp> to all confirmation requests." |
| msgstr "" |
| |
| |
| msgid "`--packages'" |
| msgstr "" |
| |
| |
| msgid "" |
| "Install/update software packages required by the working copy of CentOS " |
| "Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "The process of software installation takes place through <code>sudo yum</" |
| "code> and the repository configuration currently set in your workstation." |
| msgstr "" |
| |
| |
| msgid "" |
| "Most of the software packages required by the working copy of CentOS Artwork " |
| "Repository are available on The CentOS Distribution and can be installed " |
| "using The CentOS Distribution installation media. The only exception is " |
| "Inkscape, the program used to manipulate <acronym title=\"Scalable Vector " |
| "Graphics\">SVG</acronym> (Scalable Vector Graphics) files in the working " |
| "copy." |
| msgstr "" |
| |
| |
| msgid "`--releasever=\"STRING\"'" |
| msgstr "" |
| |
| |
| msgid "" |
| "This option expands release-specific translation makers to <samp>`STRING'</" |
| "samp>. Use this option when no releasae-specific information can be retrived " |
| "from the path of the directory structure you are currently rendering." |
| msgstr "" |
| |
| |
| msgid "`--basearch=\"STRING\"'" |
| msgstr "" |
| |
| |
| msgid "" |
| "This option expands architecture-specific translation makers to " |
| "<samp>`STRING'</samp>. Use this option when no architecture-specific " |
| "information can be retrived from the path of the directory structure you are " |
| "currently rendering." |
| msgstr "" |
| |
| |
| msgid "`--theme-model=\"STRING\"'" |
| msgstr "" |
| |
| |
| msgid "" |
| "Specify the name of the theme model you want to use to produce theme " |
| "artistic motifs. By default, if this option is not passed, the " |
| "<samp>`Default'</samp> theme model is used as reference to produce theme " |
| "motifs." |
| msgstr "" |
| |
| |
| msgid "`--post-rendition=\"STRING\"'" |
| msgstr "" |
| |
| |
| msgid "" |
| "This option let you apply a command as post-rendition action. In this case, " |
| "the <samp>`STRING'</samp> represents the command string you want to execute " |
| "in order to perform in-place modifications to base-rendition output." |
| msgstr "" |
| |
| |
| msgid "`--last-rendition=\"STRING\"'" |
| msgstr "" |
| |
| |
| msgid "" |
| "This option let you apply a command as last-rendition action. In this case, " |
| "the <samp>`STRING'</samp> 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 CentOS Artwork Repository, rendition tasks take " |
| "place inside renderable directories. Inside the <code>render</code> " |
| "functionality of <code>centos-art.sh</code> script, you can control " |
| "rendition tasks through different flows of rendition named base-rendition, " |
| "post-rendition, last-rendition and directory-specific rendition." |
| msgstr "" |
| |
| |
| msgid "Renderable directories" |
| msgstr "" |
| |
| |
| msgid "" |
| "In order for a directory structure to be considered renderable, it should " |
| "have one directory structure for input files and one directory structure for " |
| "output files. Optionally, a third directory structure might be available for " |
| "storing translation files." |
| msgstr "" |
| |
| |
| msgid "" |
| "Renderable directories are very tied to the way content is produced inside " |
| "the working copy of CentOS Artwork Repository. Presently, content is " |
| "produced through the following organizations:" |
| msgstr "" |
| |
| |
| msgid "Direct rendition" |
| msgstr "" |
| |
| |
| msgid "" |
| "In direct rendition, there is one directory structure for input files " |
| "(<tt>`trunk/Identity/Models'</tt>) and one directory structure for output " |
| "files (e.g., <tt>`trunk/Identity/Images'</tt>). Optionally, a third " |
| "directory structure is available to store the input related translation " |
| "files (e.g., <tt>`trunk/Locales/Identity/Models'</tt>)." |
| msgstr "" |
| |
| |
| msgid "" |
| "In direct rendition, when the <code>render</code> functionality of " |
| "<code>centos-art.sh</code> script is executed, it uses the input directory " |
| "structure to build a list of files to process, which is used as reference to " |
| "determine the location of the translation file and the location of the " |
| "output file, as well." |
| msgstr "" |
| |
| |
| msgid "Theme-specific rendition" |
| msgstr "" |
| |
| |
| msgid "" |
| "In theme-specific rendition, there is one directory structure to store input " |
| "files (<tt>`trunk/Identity/Themes/Models'</tt>), one directory structure to " |
| "store translation files (<tt>`trunk/Locales/Identity/Themes/Models/'</tt>), " |
| "one directory structure to store artistic motifs (<tt>`trunk/Identity/Images/" |
| "Themes'</tt>) and one directory structure to store output files (<tt>`trunk/" |
| "Identity/Images/Themes'</tt>)." |
| msgstr "" |
| |
| |
| msgid "" |
| "In theme-specific rendition, when the <code>render</code> functionality of " |
| "<code>centos-art.sh</code> script is executed, it uses the input directory " |
| "structure to build a list of files to process, which is used as reference to " |
| "determine the location of the translation file and the location of the " |
| "output file, as well." |
| msgstr "" |
| |
| |
| msgid "" |
| "In contrast with direct rendition, when we use theme-specific rendition, it " |
| "is possible to combine both design models and artistic motifs to produce " |
| "output in an arbitrary way. This configuration is specially interesting " |
| "because it is possible to create different artistic motifs and one unique " |
| "design model in order to produce one unique theme structure with different " |
| "visual styles. Or the opposite, to create different theme structures and " |
| "apply one unique visual style to produce one unique visual styles on " |
| "different theme structure. Or even get a bit farther and experiment with " |
| "arbitrary combinations among them all." |
| msgstr "" |
| |
| |
| msgid "" |
| "In both direct and theme-specific rendition, if the location where the " |
| "output file should be stored doesn't exist, the <code>render</code> " |
| "functionality of <code>centos-art.sh</code> script will create it for you." |
| msgstr "" |
| |
| |
| msgid "" |
| "In both direct and theme-specific rendition, if the input related " |
| "translation file doesn't exist, the <code>render</code> functionality of " |
| "<code>centos-art.sh</code> script will produce the output in the same " |
| "language of its input file." |
| msgstr "" |
| |
| |
| msgid "The base-rendition flow" |
| msgstr "" |
| |
| |
| msgid "" |
| "The base-rendition flow is the first rendition flow of all rendition flows " |
| "available and takes place immediatly after executing the <code>render</code> " |
| "functionality of <code>centos-art.sh</code> script." |
| msgstr "" |
| |
| |
| msgid "" |
| "The base-rendition produces different outputs from one unique input format. " |
| "This is, one input file is used to produce one ore more output files. When " |
| "translation files are available for input files, the base-rendition applies " |
| "the translation file to the input file in order to produce a translated " |
| "instance of it, then this translated instance is used as input file to " |
| "produce one or more output files." |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside the <code>render</code> functionality of <code>centos-art.sh</code> " |
| "script, the input format is always XML (e.g., SVG, XHTML, Docbook), the " |
| "translation files are always portable objects (e.g., PO) and the output " |
| "format depends on the input file provided (e.g., when the input format is a " |
| "SVG file, the base output is a PNG file; when the input format is XHTML the " |
| "base output is an XHTML file; when the input format is a Docbook file the " |
| "base output might be either HTML, RTF, PS or PDF)." |
| msgstr "" |
| |
| |
| msgid "" |
| "As application example of base-rendition flow, consider the description of " |
| "the following sections:" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Anaconda'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Identity/Models/Themes/Default/Distro/5.5/Notes/Release'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "The post-rendition flow" |
| msgstr "" |
| |
| |
| msgid "" |
| "The post-rendition flow is performed immediatly after base-rendition flow to " |
| "extend the base-rendition flow by applying in-place modifications to base-" |
| "rendition output. In-place modifications can be performed either through the " |
| "<samp>`--post-rendition'</samp> command-line option of <code>centos-art.sh</" |
| "code> script or through directory-specific rendition." |
| msgstr "" |
| |
| |
| msgid "" |
| "Actions commanded through <samp>`--post-rendition'</samp> option are applied " |
| "first and directory-specific actions later. This order is required to " |
| "propagate in-place changes commited to base-rendition output to modified " |
| "copies (i.e., new files) of it created through directory-specific rendition. " |
| "Creation of modified copies is something specific to directory-specific " |
| "rendition only. It is not possible for the <samp>`--post-rendition'</samp> " |
| "option to create modified copies of base-rendition flow because commands " |
| "passed through it are applied to the base-rendition output file directly in " |
| "a disposition that don't support creation of new files, but in-place " |
| "modifications only." |
| msgstr "" |
| |
| |
| msgid "" |
| "The command passed to <samp>`--post-rendition'</samp> option can be changed " |
| "everytime you run the <code>centos-art.sh</code> script, but actions " |
| "specified in directory-specific rendition cannot be changed in the same way. " |
| "Direcctory-specific rendition is set inside <code>centos-art.sh</code> " |
| "script to perform specific tasks that cannot be achived through <samp>`--" |
| "post-rendition'</samp> option." |
| msgstr "" |
| |
| |
| msgid "" |
| "As application example of post-rendition flow, consider the description of " |
| "the following sections:" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Syslinux'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Grub'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "The last-rendition flow" |
| msgstr "" |
| |
| |
| msgid "" |
| "The last-rendition flow takes place after post-rendition and applies in-" |
| "place modifications to all files produced as result of both base-rendition " |
| "and post-rendition flows in the same directory structure, just before " |
| "passing to process a different directory structure. In-place modifications " |
| "can be performed either through the <samp>`--last-rendition'</samp> command-" |
| "line option of <code>centos-art.sh</code> script or through directory-" |
| "specific rendition." |
| msgstr "" |
| |
| |
| msgid "" |
| "Actions commanded through <samp>`--last-rendition'</samp> option are applied " |
| "after directory-specific actions. This order is required to prevent last-" |
| "rendition actions commanded from directory-specifc rendition to overlap last-" |
| "rendition actions commanded from <samp>`--last-rendition'</samp> option." |
| msgstr "" |
| |
| |
| msgid "" |
| "The command passed to <samp>`--last-rendition'</samp> option can be changed " |
| "everytime you run the <code>centos-art.sh</code> script, but actions " |
| "specified in directory-specific rendition cannot be changed in the same way. " |
| "Actions commanded from directory-specific rendition are set inside " |
| "<code>centos-art.sh</code> script to perform specific tasks that cannot be " |
| "achived through <samp>`--last-rendition'</samp> option." |
| msgstr "" |
| |
| |
| msgid "" |
| "As application example of last-rendition flow, consider the description of " |
| "the following sections:" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Ksplash'</tt> " |
| "Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk/Identity/Models/Themes/Default/Distro/5/Gdm'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "The directory-specific rendition flow" |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside the working copy of CentOS Artwork Repository, some directory " |
| "structure (e.g., <tt>`Syslinux'</tt>, <tt>`Gurb'</tt>, <tt>`Gdm'</tt>, " |
| "<tt>`Kdm'</tt> and <tt>`KSplash'</tt>) required more than base-rendition or " |
| "even the commands you could pass through the <samp>`--post-rendition'</samp> " |
| "and <samp>`--last-rendition'</samp> options, in order for their final files " |
| "to be produced. In these situations, we make use of directory-specific " |
| "rendition flow." |
| msgstr "" |
| |
| |
| msgid "" |
| "The directory-specific rendition flow applies specific actions to specific " |
| "directory structures when they enter into the rendition flow. Using this " |
| "configuration speeds up production of all those components that require " |
| "intermediate formats or even several independent files, in order for the " |
| "final content to be created." |
| msgstr "" |
| |
| |
| msgid "" |
| "The directory-specific rendition flow is generally used in combination with " |
| "post-rendition and last-rendition flows inside <code>centos-art.sh</code> " |
| "script." |
| msgstr "" |
| |
| |
| msgid "Translations" |
| msgstr "" |
| |
| |
| msgid "" |
| "To translate output files, the <code>render</code> functionality of " |
| "<code>centos-art.sh</code> script creates a translated instance of the input " |
| "file and uses it then to create the base output file. The translated " |
| "instance is created using the related translation messages of the input " |
| "file. Translation messages are stored under <tt>`trunk/Locales'</tt> and are " |
| "created using the <code>locale</code> functionality of <code>centos-art.sh</" |
| "code> script (see section <a href=\"repository_51.xhtml#SEC281\">The " |
| "<tt>`trunk/Scripts/Functions/Locale'</tt> Directory</a>)." |
| msgstr "" |
| |
| |
| msgid "" |
| "Translation files are optional. When no translation file is available for " |
| "the input file, the base-rendition output is produced using the same " |
| "language of the input file." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_52.xhtml#SEC292\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "centos-art render trunk/Identity/Images/Brands" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command produces all branding information related to The CentOS Project " |
| "(e.g., symbols, logos and variants of them)." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_54.xhtml#SEC320\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "centos-art render trunk/Identity/Images/Brands --filter=\"symbol\"" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command produces all branding information, related to The CentOS " |
| "Project, which file names contain the <samp>`symbol'</samp> string on it." |
| msgstr "" |
| |
| |
| msgid "centos-art render trunk/Identity/Images/Themes/Flame/2" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command produces all visual manifestations related to version 2 of " |
| "Flame artistic motif (e.g., Distribution, Posters, etc.) as specified by " |
| "default design models." |
| msgstr "" |
| |
| |
| msgid "centos-art render trunk/Identity/Images/Themes/Flame/2/Distro" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command produces the Distribution visual manifestations related to " |
| "version 2 of Flame artistic motif (e.g., Anaconda, Syslinux, Grub, " |
| "Firstboot, Gdm, Kdm, Gsplash, Ksplash, and Rhgb) as specified by default " |
| "design models." |
| msgstr "" |
| |
| |
| msgid "" |
| "centos-art render trunk/Identity/Images/Themes --filter='Distro/5/Anaconda'" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command produces all the images related to Anaconda component from " |
| "Distribution visual manifestations on its major release number five, for all " |
| "the artistic motifs available and as specified by default design models." |
| msgstr "" |
| |
| |
| msgid "" |
| "centos-art render trunk/Identity/Images/Themes --filter='Concept' --post-" |
| "rendition='mogrify -normalize'" |
| msgstr "" |
| |
| |
| msgid "" |
| "This command produces all the images related to Concept component from all " |
| "artistic motifs as specified by default design models. Moreover, the " |
| "<code>mogrify -normalize</code> command is applied to each PNG image " |
| "produced as result of the base-rendition output." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>mogrify</code> command is part of ImageMagick® software suite " |
| "and let you to resize an image, blur, crop, despeckle, dither, draw on, " |
| "flip, join, re-sample, and much more. The ImageMagick® software suite is " |
| "copyrighted to <a class=\"www\" href=\"http://redux.imagemagick.org/" |
| "MagickStudio/scripts/MagickStudio.cgi\">ImageMagick Studio LLC</a>, a non-" |
| "profit organization dedicated to making software imaging solutions freely " |
| "available." |
| msgstr "" |
| |
| |
| msgid "" |
| "The ImageMagick® software suite documentation (<code>rpm -qd ImageMagick " |
| "| less</code>)." |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.45 The <tt>`trunk/Scripts/Functions/Render'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>render</code> functionlity is part of <code>centos-art.sh</code> " |
| "script and standardizes rendition tasks inside the working copy of CentOS " |
| "Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "centos-art render [OPTIONS] path/to/dir" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`path/to/dir'</tt> parameter specifies what directory structure " |
| "inside the working copy of CentOS Artwork Repository you want to produce." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>render</code> functionality of <code>centos-art.sh</code> script " |
| "accepts the following options:" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.45 The trunk/Scripts/Functions/Render Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "Tasks related to file maintainance are repetitive. You might find yourself " |
| "doing them time after time inside the working copy of CentOS Artwork " |
| "Repository. 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 <code>tuneup</code> functionality of <code>centos-art." |
| "sh</code> script, it looks for all files that match the supported extensions " |
| "(e.g., <tt>`.sh'</tt>, <tt>`.svg'</tt> and <tt>`.xhtml'</tt>) in the " |
| "directory specified, builds a list with them and applies the maintainance " |
| "tasks using file extensions as reference." |
| msgstr "" |
| |
| |
| msgid "Maintaining <tt>`.sh'</tt> files" |
| msgstr "" |
| |
| |
| msgid "" |
| "If shell scripts are found, the <code>tuneup</code> functionality of " |
| "<code>centos-art.sh</code> script reads a comment template from <tt>`trunk/" |
| "Scripts/Functions/Prepare/Config/shell_topcomment.sed'</tt> and applies it " |
| "to 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 following structure:" |
| msgstr "" |
| |
| |
| msgid "" |
| "1| #!/bin/bash 2| # 3| # doSomething.sh -- The function description goes " |
| "here. 4| # 5| # Copyright 6| # 7| # ... 8| # 9| # " |
| "---------------------------------------------------------------------- 10| # " |
| "$Id$ 11| # " |
| "---------------------------------------------------------------------- 12| " |
| "13| function doSomething { 14| 15| }" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>tuneup</code> functionality of <code>centos-art.sh</code> script " |
| "replaces all lines between the <samp>`Copyright'</samp> line (e.g., line 5) " |
| "and the first separator line (e.g., line 9), inclusively. Everything else in " |
| "the file will remain immutable." |
| msgstr "" |
| |
| |
| msgid "Maintaining <tt>`.svg'</tt> files" |
| msgstr "" |
| |
| |
| msgid "" |
| "If scalable vector graphics are found, the <code>tuneup</code> functionality " |
| "reads a metadata template (<tt>`trunk/Scripts/Functions/Tuneup/Config/" |
| "svg_metadata.sed'</tt>) 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 file, too." |
| msgstr "" |
| |
| |
| msgid "" |
| "The metadata we apply from the metadata template is created dynamicaly " |
| "combining the file absolute path, the workstation time information and the " |
| "<code>centos-art.sh</code> script copyright holder information as reference. " |
| "Additionally, the <em>Creative Common Distribution-ShareAlike 3.0 License</" |
| "em> is also set in the metadata." |
| msgstr "" |
| |
| |
| msgid "" |
| "The elimination of unused definitions inside SVG files takes place through " |
| "the <samp>`--vacuum-defs'</samp> option of <code>inkscape</code> command-" |
| "line interface which is described in its man page (<code>man inkscape</" |
| "code>)." |
| msgstr "" |
| |
| |
| msgid "Maintaining <tt>`.xhtml'</tt> files" |
| msgstr "" |
| |
| |
| msgid "" |
| "If web pages are found, the <code>tuneup</code> functionality of " |
| "<code>centos-art.sh</code> 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 page." |
| msgstr "" |
| |
| |
| msgid "" |
| "Once the <code><div class=\"toc\"></div></code> piece of code " |
| "has be expanded, there is no need to put anything else in the page. You can " |
| "run the <code>tuneup</code> functionality everytime you update the heading " |
| "information so as to update the table of contents, too." |
| msgstr "" |
| |
| |
| msgid "" |
| "In order for the <code>tuneup</code> functionality of <code>centos-art.sh</" |
| "code> script to transform headings, you need to put headings in just one " |
| "line using one of the following forms:" |
| msgstr "" |
| |
| |
| msgid "" |
| "<h1><a name=\"\">Title</a></h1> <h1><a href=" |
| "\"\">Title</a></h1> <h1><a name=\"\" href=\"\">" |
| "Title</a></h1>" |
| msgstr "" |
| |
| |
| msgid "" |
| "In the example above, h1 can vary from h1 to h6. Closing tag must be present " |
| "and also match the openning tag. The value of <samp>`name'</samp> and " |
| "<samp>`href'</samp> options from the anchor element are set dynamically " |
| "using the md5sum output of combining the page location, the <code>head-</" |
| "code> string and the heading string. If any of the components used to build " |
| "the heading reference changes, you need to run the the <code>tuneup</code> " |
| "functionality of <code>centos-art.sh</code> script in order for the anchor " |
| "elements to use the correct information." |
| msgstr "" |
| |
| |
| msgid "centos-art tuneup trunk/Scripts" |
| msgstr "" |
| |
| |
| msgid "" |
| "Update the copyright and license notice of all the shell scripts we have in " |
| "<tt>`trunk/Scripts'</tt> directory structure." |
| msgstr "" |
| |
| |
| msgid "centos-art tuneup trunk/Identity/Models/Brands --filter=\"symbol\"" |
| msgstr "" |
| |
| |
| msgid "" |
| "Update metadata and remove unused definitions from all design models in " |
| "<tt>`trunk/Identity/Models/Brands'</tt> which have the word <samp>`symbol'</" |
| "samp> in the file name." |
| msgstr "" |
| |
| |
| msgid "centos-art tuneup trunk/Identity/Webenv/App/Home" |
| msgstr "" |
| |
| |
| msgid "" |
| "Update headings and the related table of contents to all web pages inside " |
| "<tt>`trunk/Identity/Webenv/App/Home'</tt>, recusively." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_53.xhtml#SEC305\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_55.xhtml#SEC332\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.46 The <tt>`trunk/Scripts/Functions/Tuneup'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>tuneup</code> functionlity is part of <code>centos-art.sh</code> " |
| "script and standardizes tasks related to file maintainance inside the " |
| "working copy of CentOS Artwork Repository." |
| msgstr "" |
| |
| |
| msgid "centos-art tuneup [OPTIONS] path/to/dir" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>tuneup</code> functionality of <code>centos-art.sh</code> script " |
| "accepts the following options:" |
| msgstr "" |
| |
| |
| msgid "" |
| "CentOS Artwork Repository: 2.46 The trunk/Scripts/Functions/Tuneup Directory" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_54.xhtml#SEC320\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_56.xhtml#SEC333\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_58.xhtml#SEC350\" title=\"Next chapter\"> >> </" |
| "a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "3.1 GNU General Public License" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "3.2 GNU Free Documentation License" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 3. Licenses" |
| 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 "" |
| "0. This License applies to any program or other work which contains a notice " |
| "placed by the copyright holder saying it may be distributed under the terms " |
| "of this General Public License. The \"Program\", below, refers to any such " |
| "program or work, and a \"work based on the Program\" means either the " |
| "Program or any derivative work under copyright law: that is to say, a work " |
| "containing the Program or a portion of it, either verbatim or with " |
| "modifications and/or translated into another language. (Hereinafter, " |
| "translation is included without limitation in the term \"modification\".) " |
| "Each licensee is addressed as \"you\"." |
| msgstr "" |
| |
| |
| msgid "" |
| "Activities other than copying, distribution and modification are not covered " |
| "by this License; they are outside its scope. The act of running the Program " |
| "is not restricted, and the output from the Program is covered only if its " |
| "contents constitute a work based on the Program (independent of having been " |
| "made by running the Program). Whether that is true depends on what the " |
| "Program does." |
| msgstr "" |
| |
| |
| msgid "" |
| "1. 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 "" |
| "2. 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 Section 1 above, provided that you " |
| "also meet all of these conditions:" |
| msgstr "" |
| |
| |
| msgid "" |
| "a) You must cause the modified files to carry prominent notices stating that " |
| "you changed the files and the date of any change." |
| msgstr "" |
| |
| |
| msgid "" |
| "b) 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 "" |
| "c) 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. (Exception: 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 "" |
| "3. You may copy and distribute the Program (or a work based on it, under " |
| "Section 2) in object code or executable form under the terms of Sections 1 " |
| "and 2 above provided that you also do one of the following:" |
| msgstr "" |
| |
| |
| msgid "" |
| "a) Accompany it with the complete corresponding machine-readable source " |
| "code, which must be distributed under the terms of Sections 1 and 2 above on " |
| "a medium customarily used for software interchange; or," |
| msgstr "" |
| |
| |
| msgid "" |
| "b) 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 Sections 1 " |
| "and 2 above on a medium customarily used for software interchange; or," |
| msgstr "" |
| |
| |
| msgid "" |
| "c) 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 "" |
| "4. 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 "" |
| "5. 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 "" |
| "6. 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 "" |
| "7. 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 "" |
| "8. 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 "" |
| "9. 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 \"any " |
| "later version\", 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 "" |
| "10. 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 "" |
| "11. 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 \"AS IS\" 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 "" |
| "12. 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 "Appendix: 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 \"copyright\" " |
| "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 "" |
| "[<a href=\"repository_55.xhtml#SEC332\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_57.xhtml#SEC337\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| 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 \"copyright disclaimer\" 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 "" |
| "[<a href=\"repository_55.xhtml#SEC332\" title=\"Beginning of this chapter or " |
| "previous chapter\"> << </a>]" |
| 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 "[<a href=\"repository_55.xhtml#SEC332\" title=\"Up section\"> Up </a>]" |
| msgstr "" |
| |
| |
| msgid "Version 2, June 1991" |
| msgstr "" |
| |
| |
| msgid "" |
| "Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, " |
| "Cambridge, MA 02139, USA" |
| 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 "CentOS Artwork Repository: 3.1 GNU General Public License" |
| 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: (1) copyright the software, and (2) " |
| "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 "" |
| "A \"Secondary Section\" 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 " |
| "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 \"Invariant Sections\" are certain Secondary Sections 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 Sections then there are none." |
| msgstr "" |
| |
| |
| msgid "" |
| "The \"Cover Texts\" 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 \"Transparent\" 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 Transparent file format whose markup, or absence of markup, has " |
| "been arranged to thwart or discourage subsequent modification by readers is " |
| "not Transparent. An image format is not Transparent if used for any " |
| "substantial amount of text. A copy that is not \"Transparent\" is called " |
| "\"Opaque\"." |
| msgstr "" |
| |
| |
| msgid "" |
| "Examples of suitable formats for 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 \"Title Page\" 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, \"Title Page\" 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 \"Entitled XYZ\" 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 \"Acknowledgements\", \"Dedications\", " |
| "\"Endorsements\", or \"History\".) To \"Preserve the Title\" of such a " |
| "section when you modify the Document means that it remains a section " |
| "\"Entitled XYZ\" 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 "2. 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 <em>3. COPYING IN QUANTITY</em>." |
| msgstr "" |
| |
| |
| msgid "" |
| "You may also lend copies, under the same conditions stated above, and you " |
| "may publicly display copies." |
| msgstr "" |
| |
| |
| msgid "3. 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 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 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 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 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 "4. MODIFICATIONS" |
| msgstr "" |
| |
| |
| msgid "" |
| "You may copy and distribute a Modified Version of the Document under the " |
| "conditions of sections <em>2. VERBATIM COPYING</em> and <em>3. COPYING IN " |
| "QUANTITY</em> above, provided that you release the Modified Version under " |
| "precisely this License, with the Modified Version filling the role of the " |
| "Document, thus licensing distribution and modification of the Modified " |
| "Version to whoever possesses a copy of it. In addition, you must do these " |
| "things in the Modified Version:" |
| msgstr "" |
| |
| |
| msgid "" |
| "A. Use in the 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 "" |
| "B. List on the Title Page, as authors, one or more persons or entities " |
| "responsible for authorship of the modifications in the 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 "" |
| "C. State on the Title page the name of the publisher of the Modified " |
| "Version, as the publisher." |
| msgstr "" |
| |
| |
| msgid "D. Preserve all the copyright notices of the Document." |
| msgstr "" |
| |
| |
| msgid "" |
| "E. Add an appropriate copyright notice for your modifications adjacent to " |
| "the other copyright notices." |
| msgstr "" |
| |
| |
| msgid "" |
| "F. Include, immediately after the copyright notices, a license notice giving " |
| "the public permission to use the Modified Version under the terms of this " |
| "License, in the form shown in the Addendum below." |
| msgstr "" |
| |
| |
| msgid "" |
| "G. Preserve in that license notice the full lists of Invariant Sections and " |
| "required Cover Texts given in the Document's license notice." |
| msgstr "" |
| |
| |
| msgid "H. Include an unaltered copy of this License." |
| msgstr "" |
| |
| |
| msgid "" |
| "I. Preserve the section Entitled \"History\", Preserve its Title, and add to " |
| "it an item stating at least the title, year, new authors, and publisher of " |
| "the Modified Version as given on the Title Page. If there is no section " |
| "Entitled \"History\" in the Document, create one stating the title, year, " |
| "authors, and publisher of the Document as given on its Title Page, then add " |
| "an item describing the Modified Version as stated in the previous sentence." |
| msgstr "" |
| |
| |
| msgid "" |
| "J. Preserve the network location, if any, given in the Document for public " |
| "access to a 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 \"History\" 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 "" |
| "K. For any section Entitled \"Acknowledgements\" or \"Dedications\", " |
| "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 "" |
| "L. Preserve all the 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 "" |
| "M. Delete any section Entitled \"Endorsements\". Such a section may not be " |
| "included in the Modified Version." |
| msgstr "" |
| |
| |
| msgid "" |
| "N. Do not retitle any existing section to be Entitled \"Endorsements\" or to " |
| "conflict in title with any Invariant Section." |
| msgstr "" |
| |
| |
| msgid "O. Preserve any Warranty Disclaimers." |
| msgstr "" |
| |
| |
| msgid "" |
| "If the Modified Version includes new front-matter sections or appendices " |
| "that qualify as Secondary Sections 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 Invariant Sections in " |
| "the Modified Version's license notice. These titles must be distinct from " |
| "any other section titles." |
| msgstr "" |
| |
| |
| msgid "" |
| "You may add a section Entitled \"Endorsements\", provided it contains " |
| "nothing but endorsements of your 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 " |
| "Cover Texts in the 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 Modified Version." |
| msgstr "" |
| |
| |
| msgid "5. COMBINING DOCUMENTS" |
| msgstr "" |
| |
| |
| msgid "" |
| "You may combine the Document with other documents released under this " |
| "License, under the terms defined in section <em>4. MODIFICATIONS</em> above " |
| "for modified versions, provided that you include in the combination all of " |
| "the Invariant Sections of all of the original documents, unmodified, and " |
| "list them all as 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 Invariant Sections may be replaced with a single copy. If there " |
| "are multiple 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 Invariant Sections in the license notice of the " |
| "combined work." |
| msgstr "" |
| |
| |
| msgid "" |
| "In the combination, you must combine any sections Entitled \"History\" in " |
| "the various original documents, forming one section Entitled \"History\"; " |
| "likewise combine any sections Entitled \"Acknowledgements\", and any " |
| "sections Entitled \"Dedications\". You must delete all sections Entitled " |
| "\"Endorsements\"." |
| msgstr "" |
| |
| |
| msgid "6. COLLECTIONS 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 "" |
| "[<a href=\"repository_56.xhtml#SEC333\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| 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 "" |
| "[<a href=\"repository_58.xhtml#SEC350\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "7. AGGREGATION WITH IDENPENDENT 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 \"aggregate\" 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 <em>3. COPYING IN QUANTITY</em> is " |
| "applicable to these copies of the Document, then if the Document is less " |
| "than one half of the entire aggregate, the Document's 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 "8. TRANSLATIONS" |
| msgstr "" |
| |
| |
| msgid "" |
| "Translation is considered a kind of modification, so you may distribute " |
| "translations of the Document under the terms of section <em>4. " |
| "MODIFICATIONS</em>. Replacing Invariant Sections with translations requires " |
| "special permission from their copyright holders, but you may include " |
| "translations of some or all Invariant Sections in addition to the original " |
| "versions of these 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 \"Acknowledgements\", \"Dedications" |
| "\", or \"History\", the requirement (section <em>4. MODIFICATIONS</em>) to " |
| "Preserve its Title (section <em>1. APPLICABILITY AND DEFINITIONS</em>) will " |
| "typically require changing the actual title." |
| msgstr "" |
| |
| |
| msgid "9. 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 "Appendix 1. 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 <a class=\"www\" href=\"http://www.gnu." |
| "org/copyleft/\">http://www.gnu.org/copyleft/</a>." |
| 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 \"or " |
| "any later version\" 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 "Appendix 2. 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 ``GNU " |
| "Free Documentation License''." |
| msgstr "" |
| |
| |
| msgid "" |
| "If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, " |
| "replace the \"with...Texts\". 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 Invariant Sections without 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 "Version 1.2, November 2002" |
| msgstr "" |
| |
| |
| msgid "" |
| "Copyright (C) 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 \"free\" 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 \"copyleft\", which means that derivative works of " |
| "the document must themselves be free in the same sense. It complements the " |
| "GNU General Public License, 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 "CentOS Artwork Repository: 3.2 GNU Free Documentation License" |
| msgstr "" |
| |
| |
| msgid "1. 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 \"Document\", below, refers to any such " |
| "manual or work. Any member of the public is a licensee, and is addressed as " |
| "\"you\". You accept the license if you copy, modify or distribute the work " |
| "in a way requiring permission under copyright law." |
| msgstr "" |
| |
| |
| msgid "" |
| "A \"Modified Version\" 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 "Directories trunk Identity Images Themes Motifs Pipes" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Images Themes Motifs TreeFlower" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Brands" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Concept" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Distro" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Distro 5" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Distro 5 Anaconda" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Distro 5 Firstboot" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Distro 5 Gdm" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Distro 5 Grub" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Distro 5 Gsplash" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Distro 5 Kdm" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Distro 5 Ksplash" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Distro 5 Rhgb" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Distro 5 Syslinux" |
| msgstr "" |
| |
| |
| msgid "" |
| "Directories trunk Identity Models Themes Default Distro 5.5 Notes Release" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Models Themes Default Posters" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Palettes" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Patterns" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Webenv" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Locales" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Manual" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Manual Directories" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Manual Introduction" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Manual Licenses" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Scripts" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Scripts Functions" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Scripts Functions Help" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Scripts Functions Locale" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Scripts Functions Prepare" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Scripts Functions Render" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Scripts Functions Tuneup" |
| msgstr "" |
| |
| |
| msgid "Document convenctions" |
| msgstr "" |
| |
| |
| |
| |
| msgid "1.5.4.2 Documentation" |
| msgstr "" |
| |
| |
| msgid "Documentation work line" |
| msgstr "" |
| |
| |
| |
| |
| msgid "E" |
| msgstr "" |
| |
| |
| |
| |
| msgid "1.5.7 Extending repository organization" |
| msgstr "" |
| |
| |
| msgid "Extending repository organization" |
| msgstr "" |
| |
| |
| |
| |
| msgid "F" |
| msgstr "" |
| |
| |
| msgid "Feedback" |
| msgstr "" |
| |
| |
| |
| |
| msgid "G" |
| msgstr "" |
| |
| |
| msgid "GNU Free Documentation License" |
| msgstr "" |
| |
| |
| msgid "GNU General Public License" |
| msgstr "" |
| |
| |
| |
| |
| msgid "1.5.4.1 Graphic design" |
| msgstr "" |
| |
| |
| msgid "Graphic design work line" |
| msgstr "" |
| |
| |
| |
| |
| msgid "H" |
| msgstr "" |
| |
| |
| msgid "History" |
| msgstr "" |
| |
| |
| |
| |
| msgid "I" |
| msgstr "" |
| |
| |
| msgid "Introduction" |
| msgstr "" |
| |
| |
| |
| |
| msgid "L" |
| msgstr "" |
| |
| |
| msgid "Licenses" |
| msgstr "" |
| |
| |
| |
| |
| msgid "1.5.4.3 Localization" |
| msgstr "" |
| |
| |
| msgid "Localization work line" |
| msgstr "" |
| |
| |
| |
| |
| msgid "M" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| msgid "1.5.5 Connection between directories" |
| msgstr "" |
| |
| |
| msgid "Master paths" |
| msgstr "" |
| |
| |
| |
| |
| msgid "R" |
| msgstr "" |
| |
| |
| msgid "Repository convenctions" |
| msgstr "" |
| |
| |
| msgid "Repository directories" |
| msgstr "" |
| |
| |
| |
| |
| msgid "1.5.3 Repository file names" |
| msgstr "" |
| |
| |
| msgid "Repository file names" |
| msgstr "" |
| |
| |
| |
| |
| msgid "1.5.2 Repository organization" |
| msgstr "" |
| |
| |
| msgid "Repository organization" |
| msgstr "" |
| |
| |
| |
| |
| msgid "1.5.1 Repository policy" |
| msgstr "" |
| |
| |
| msgid "Repository policy" |
| msgstr "" |
| |
| |
| |
| |
| msgid "S" |
| msgstr "" |
| |
| |
| |
| |
| msgid "1.5.6 Syncronizing path information" |
| msgstr "" |
| |
| |
| msgid "Syncronizing path information" |
| msgstr "" |
| |
| |
| |
| |
| msgid "A" |
| msgstr "" |
| |
| |
| |
| msgid "Jump to: " |
| msgstr "" |
| |
| |
| |
| |
| msgid "C" |
| msgstr "" |
| |
| |
| |
| |
| msgid "D" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_57.xhtml#SEC337\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_59.xhtml#SEC351\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_59.xhtml#SEC351\" title=\"Next chapter\"> >> </" |
| "a>]" |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC350\" title=\"Index\">Index</a>]" |
| msgstr "" |
| |
| |
| msgid "Index Entry" |
| msgstr "Entrada del índice" |
| |
| |
| msgid "Section" |
| msgstr "Sección" |
| |
| |
| msgid "CentOS Artwork Repository: Index" |
| msgstr "Repositorio Artístico de CentOS: Índice" |
| |
| |
| msgid "Authors" |
| msgstr "Autores" |
| |
| |
| |
| |
| msgid "1.5.4.4 Automation" |
| msgstr "" |
| |
| |
| msgid "Automation work line" |
| msgstr "" |
| |
| |
| msgid "Auxiliar paths" |
| msgstr "" |
| |
| |
| msgid "Connection between directories" |
| msgstr "" |
| |
| |
| msgid "Copying conditions" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "2.1 The <tt>`branches'</tt> Directory" |
| msgstr "" |
| |
| |
| msgid "Directories branches" |
| msgstr "" |
| |
| |
| msgid "Directories tags" |
| msgstr "" |
| |
| |
| msgid "Directories trunk" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Brushes" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Fonts" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Images" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Images Themes" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Images Themes Motifs" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Images Themes Motifs Flame" |
| msgstr "" |
| |
| |
| msgid "Directories trunk Identity Images Themes Motifs Modern" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_58.xhtml#SEC350\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| |
| msgid "[ > ]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_58.xhtml#SEC350\" title=\"Beginning of this chapter or " |
| "previous chapter\"> << </a>]" |
| msgstr "" |
| |
| |
| |
| |
| msgid "[ >> ]" |
| msgstr "" |
| |
| |
| msgid "Figure 1.1" |
| msgstr "" |
| |
| |
| msgid "Path construction." |
| msgstr "" |
| |
| |
| msgid "Figure 1.2" |
| msgstr "" |
| |
| |
| msgid "Path construction extended." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: List of Figures" |
| msgstr "" |
| |
| |
| msgid "" |
| "As a good community citizen one understand of a person who respects the work " |
| "already done for others and share ideas with authors before changing " |
| "relevant parts of their work, specially in situations when the access " |
| "required to realize the changes has been granted already. Of course, there " |
| "is a time when conversation has taken place, the paths has been traced and " |
| "changing the work is so obvious that there is no need for you to talk about " |
| "it; that's because you already did, you already built the trust to keep " |
| "going. Anyway, the mailing list mentioned above is available for sharing " |
| "ideas in a way that good relationship between community citizens could be " |
| "constantly balanced." |
| msgstr "" |
| |
| |
| msgid "" |
| "The relationship between community citizens is monitored by repository " |
| "administrators. Repository administrators are responsible of granting " |
| "everything goes the way it needs to go in order for the CentOS Artwork " |
| "Repository to comply its mission which is: to provide a colaborative tool " |
| "for The CentOS Community where The CentOS Project Corporate Identity is " |
| "built and maintained from The CentOS Community itself." |
| msgstr "" |
| |
| |
| msgid "" |
| "It is also important to remember that all source files inside CentOS Artwork " |
| "Repository should comply the terms of GNU General Public License (see " |
| "section <a href=\"repository_56.xhtml#SEC333\">GNU General Public License</" |
| "a>) in order for them to remain inside the repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "[<a href=\"#SEC19\" title=\"Previous section in reading order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC21\" title=\"Next section in reading order\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| msgid "[<a href=\"#SEC18\" title=\"Up section\"> Up </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Artwork Repository uses a <tt>`trunk'</tt>, <tt>`branches'</tt>, " |
| "and <tt>`tags'</tt> organization." |
| msgstr "" |
| |
| |
| msgid "`trunk'" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`trunk'</tt> directory organizes the main development line of CentOS " |
| "Artwork Repository. See section <a href=\"repository_11.xhtml#SEC42\">The " |
| "<tt>`trunk'</tt> Directory</a>, for more information." |
| msgstr "" |
| |
| |
| msgid "`branches'" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`branches'</tt> directory oranizes intermediate development lines " |
| "taken from the main development line. See section <a href=\"repository_9." |
| "xhtml#SEC32\">The <tt>`branches'</tt> Directory</a>, for more information." |
| msgstr "" |
| |
| |
| msgid "`tags'" |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`tags'</tt> directory organizes frozen development lines taken " |
| "either from the main or the intermediate lines of development. See section " |
| "<a href=\"repository_10.xhtml#SEC37\">The <tt>`tags'</tt> Directory</a>, for " |
| "more information." |
| msgstr "" |
| |
| |
| msgid "" |
| "[<a href=\"#SEC20\" title=\"Previous section in reading order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC22\" title=\"Next section in reading order\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside the CentOS Artwork Repository, file names are all written in " |
| "lowercase (e.g., <samp>`01-welcome.png'</samp>, <samp>`splash.png'</samp>, " |
| "<samp>`anaconda_header.png'</samp>, etc.) and directory names are all " |
| "written capitalized (e.g., <samp>`Identity'</samp>, <samp>`Themes'</samp>, " |
| "<samp>`Motifs'</samp>, <samp>`TreeFlower'</samp>, etc.)." |
| msgstr "" |
| |
| |
| msgid "" |
| "[<a href=\"#SEC21\" title=\"Previous section in reading order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC23\" title=\"Next section in reading order\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "1.5.4 Repository work lines" |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside CentOS Artwork Repository there are four major work lines of " |
| "production which are: <em>graphic design</em>, <em>documentation</em>, " |
| "<em>localization</em> and <em>automation</em>. These work lines describe " |
| "different areas of content production. Content production inside these " |
| "specific areas may vary as much as persons be working on them. Producing " |
| "content in too many different ways may result innapropriate in a " |
| "collaborative environment like CentOS Artwork Repository where content " |
| "produced in one area depends somehow from content produced in another " |
| "different area. So, a <em>content production standard</em> is required for " |
| "each available work line." |
| msgstr "" |
| |
| |
| msgid "" |
| "[<a href=\"#SEC22\" title=\"Previous section in reading order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC24\" title=\"Next section in reading order\"> > </a>]" |
| msgstr "" |
| |
| |
| |
| |
| |
| msgid "[<a href=\"#SEC22\" title=\"Up section\"> Up </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "The graphic design work line exists to cover brand design, typography design " |
| "and themes design mainly. Additionally, some auxiliar areas like icon " |
| "design, illustration design, brushes design, patterns designs and palettes " |
| "of colors are also included here for completeness." |
| msgstr "" |
| |
| |
| msgid "" |
| "Inside CentOS Artwork Repository graphic design is performed through " |
| "Inkscape (<a class=\"www\" href=\"http://www.inkscape.org/\">http://www." |
| "inkscape.org/</a>) and GIMP (<a class=\"www\" href=\"http://www.gimp.org/" |
| "\">http://www.gimp.org/</a>). The Inkscape tool is used to create and " |
| "manipulate scalable vector graphics and export them to PNG format; it also " |
| "provides a command-line interface that we use to perform massive exportation " |
| "from SVG files to PNG files in automation scripts. On the other hand, GIMP " |
| "is used to create and manipulate rastered images, create brushes, patterns " |
| "and palettes of colors." |
| msgstr "" |
| |
| |
| msgid "" |
| "Combine both Inkscape and GIMP specific functionalities and possibilities to " |
| "produce very beautiful images." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Project Corporate Visual Identity is made of different visual " |
| "manifestations (e.g., Distributions, Web sites, Stationery, etc.). Visual " |
| "manifestations implement the corporate identity concepts by mean of images. " |
| "To produce these images, we decompose image production in <em>design models</" |
| "em> and <em>artistic motifs</em>." |
| msgstr "" |
| |
| |
| msgid "" |
| "Design models provide the structural information of images (i.e., dimension, " |
| "position of common elements in the visible area, translation markers, etc.) " |
| "and they are generally produced as scalable vector graphics to take " |
| "advantage of SVG standard, an XML-based standard." |
| msgstr "" |
| |
| |
| msgid "" |
| "Artistic motifs provide the visual style (i.e., the background information, " |
| "the look and feel) some design models need to complete the final image " |
| "produced by automation scripts. Artistic motifs are generally produced as " |
| "rastered images." |
| msgstr "" |
| |
| |
| msgid "" |
| "The result produced from combining one design model with one artistic motif " |
| "is what we know as a <em>theme</em>. Inside themes directory structure (see " |
| "section <a href=\"repository_16.xhtml#SEC74\">The <tt>`trunk/Identity/Images/" |
| "Themes'</tt> Directory</a>), you can find several design models and several " |
| "artistic motifs independently one another that can be albitrarily combined " |
| "through <em>theme rendition</em>, a flexible way to produce images for " |
| "different visual manifestations in very specific visual styles. Inside " |
| "themes directory structure, theme rendition is performed in <tt>`trunk/" |
| "Identity/Images/Themes'</tt> directory structure, the required design models " |
| "are taken from <tt>`trunk/Identity/Models/Themes'</tt> directory structure " |
| "and the action itself is controlled by the <code>render</code> functionality " |
| "of <code>centos-art.sh</code> script." |
| msgstr "" |
| |
| |
| msgid "" |
| "In addition to theme rendition you can find <em>direct rendition</em>, too. " |
| "Direct rendition is another way of image production where there is no " |
| "artistic motif at all but design models only. Direct rendition is very " |
| "useful to produce simple content that doesn't need specific background " |
| "information. Some of these contents are brands, icons and illustrations. " |
| "Direct rendition is performed in <tt>`trunk/Identity/Images'</tt>, the " |
| "required design models are taken from <tt>`trunk/Identity/Models'</tt> " |
| "directory structure and the action itself is controlled by the <code>render</" |
| "code> functionality of <code>centos-art.sh</code> script." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_12.xhtml#SEC47\">The <tt>`trunk/Identity'</" |
| "tt> Directory</a>, for more information about The CentOS Corporate Identity " |
| "and how graphic design fits on it." |
| msgstr "" |
| |
| |
| msgid "" |
| "[<a href=\"#SEC23\" title=\"Previous section in reading order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC25\" title=\"Next section in reading order\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "The documentation work line exists to describe what each directory inside " |
| "the CentOS Artwork Repository is for, the conceptual ideas behind them and, " |
| "if possible, how automation scripts make use of them." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Artwork Repository documentation is supported by Texinfo, a " |
| "documentation system that uses a single source file to produce both online " |
| "information and printed output." |
| msgstr "" |
| |
| |
| msgid "" |
| "The repository documentation is organized under <tt>`trunk/Manual'</tt> " |
| "directory and uses the repository directory structre as reference. Each " |
| "directory in the repository has a documentation entry associated in the " |
| "documentation manual. Documentation entries are stored under <tt>`trunk/" |
| "Manual/Directories'</tt> directory and the action itself is controlled by " |
| "the <code>help</code> functionality of <code>centos-art.sh</code> script." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <code>help</code> functionality let you create, edit and delete " |
| "documentation entries in a way that you don't need to take care of updating " |
| "menus, nodes and cross reference information inside the manual structure; " |
| "the functionality takes care of it for you. However, if you need to write " |
| "repository documentation that have nothing to do with repository directories " |
| "(e.g., Preface, Introduction and similar) you need to do it manually, there " |
| "is no functionality to automate such process yet." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_44.xhtml#SEC231\">The <tt>`trunk/Manual'</" |
| "tt> Directory</a>, for more information on documentation." |
| msgstr "" |
| |
| |
| msgid "" |
| "[<a href=\"repository_5.xhtml#SEC17\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "[<a href=\"#SEC24\" title=\"Previous section in reading order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC26\" title=\"Next section in reading order\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC19\" title=\"Next section in reading order\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "The localization work line exists to provide the translation messages " |
| "required to produce content in different languages. Translation messages " |
| "inside the repository are stored as portable objects (e.g., .po, .pot) and " |
| "machine objects (.mo) under <tt>`trunk/Locales'</tt> directory structure." |
| msgstr "" |
| |
| |
| msgid "" |
| "The procedure used to localize content is taken from <code>gettext</code> " |
| "standard specification. Basically, translatable strings are retrived from " |
| "source files in order to create portable objects and machine objects for " |
| "them. These portable objects are editable files that contain the information " |
| "used by translators to localize the translatable strings retrived from " |
| "source files. On the other hand, machine objects are produced to be machine-" |
| "redable only, as its name implies, and are produced from portable objects." |
| msgstr "" |
| |
| |
| msgid "" |
| "Since <code>gettext</code> needs to extract translatable strings form source " |
| "files in order to let translators to localize them, we are limitted to use " |
| "source files supported by <code>gettext</code> program. This is not a " |
| "limitation at all since <code>gettext</code> supports most popular " |
| "programming laguages (e.g., C, C++, Java, Bash, Python, Perl, PHP and GNU " |
| "Awk just to mention a few ones). Nevertheless, formats like SVG, XHTML and " |
| "Docbook don't figure as supported formats in the list of <code>gettext</" |
| "code> supported source files." |
| msgstr "" |
| |
| |
| msgid "" |
| "To translate XML based source files like SVG, XHTML and Docbook we use the " |
| "<code>xml2po</code> program instead. The <code>xml2po</code> comes with the " |
| "<tt>`gnome-doc-utils'</tt> package and retrives translatable strings from " |
| "one XML file to produce portable objects for them." |
| msgstr "" |
| |
| |
| msgid "" |
| "Portable objects produced by <code>xml2po</code> have the same format that " |
| "portable objects produced by <code>gettext</code>. This make the " |
| "localization process quite consistent from translators' point of view. No " |
| "matter what the source file be, the translator will always face the same " |
| "translation file format (i.e., the portable object format)." |
| msgstr "" |
| |
| |
| msgid "" |
| "With the portable object in place, the <code>xml2po</code> program is used " |
| "again to create the final translated XML, just with the same definition of " |
| "the source file where translatable strings were taken from (e.g., if we " |
| "extract translatable strings from a SVG file, as result we get the same SVG " |
| "file but with translatable strings already localized --obviously, for this " |
| "to happen translators need to localize translatable strings inside the " |
| "portable object first, localization won't appear as art of magic--). When " |
| "using <code>xml2po</code>, the machine object is used as temporal file to " |
| "produce the final translated XML file." |
| msgstr "" |
| |
| |
| msgid "" |
| "If you want to have your content localized inside CentOS Artwork Repository " |
| "be sure to use source files supported either by <code>gettext</code> or " |
| "<code>xml2po</code> programs." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_43.xhtml#SEC226\">The <tt>`trunk/Locales'</" |
| "tt> Directory</a>, for more information." |
| msgstr "" |
| |
| |
| msgid "" |
| "[<a href=\"#SEC25\" title=\"Previous section in reading order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC27\" title=\"Next section in reading order\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "The automation work line exists to standardize content production in CentOS " |
| "Artwork Repository. There is no need to type several tasks, time after time, " |
| "if they can be programmed into just one executable script." |
| msgstr "" |
| |
| |
| msgid "" |
| "The automation work line takes place under <tt>`trunk/Scripts'</tt> " |
| "directory structure. Here is developed the <code>centos-art.sh</code> " |
| "script, a bash script specially designed to automate most frequent tasks (e." |
| "g., rendition, documentation and localization) inside the repository. " |
| "Basically, the <code>centos-art.sh</code> script is divided in several " |
| "functionalities independent one another that perform specific tasks and " |
| "relay on repository organization to work as expected." |
| msgstr "" |
| |
| |
| msgid "" |
| "If you need to improve the way content is produced, look inside automation " |
| "scripts and make your improvement there for everyone to benefit." |
| msgstr "" |
| |
| |
| msgid "" |
| "See section <a href=\"repository_48.xhtml#SEC253\">The <tt>`trunk/Scripts'</" |
| "tt> Directory</a>, for more information on automation." |
| msgstr "" |
| |
| |
| msgid "" |
| "[<a href=\"#SEC26\" title=\"Previous section in reading order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC28\" title=\"Next section in reading order\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "In order to produce content in CentOS Artwork Repository, it is required " |
| "that all work lines be connected somehow. This is the way automation scripts " |
| "can know where to retrive the information they need to work with (e.g., " |
| "design model, translation messages, output location, etc.). We build this " |
| "kind of connection using two path constructions named <em>master paths</em> " |
| "and <em>auxiliar paths</em>." |
| msgstr "" |
| |
| |
| msgid "" |
| "The master path points only to directories that contain the source files (e." |
| "g., SVG files) required to produce base content (e.g., PNG files) through " |
| "automation scripts. Each master path inside the repository may have several " |
| "auxiliar paths associated, but auxiliar paths can only have one master path " |
| "associated." |
| msgstr "" |
| |
| |
| msgid "" |
| "The auxiliar paths can point either to directories or files. When an " |
| "auxiliar path points to a directory, that directory contains information " |
| "that modifies somehow the content produced from master paths (e.g., " |
| "translation messages) or provides the output information required to know " |
| "where to store the content produced from master path. When an auxiliar path " |
| "points to a file, that file has no other purpose but to document the master " |
| "path it refers to." |
| msgstr "" |
| |
| |
| msgid "" |
| "The relation between auxiliar paths and master paths is realized combining " |
| "two path informations which are: the master path itself and one second level " |
| "directory structure from the repository. Generally, the master path is " |
| "considered the path identifier and the second level directory structure " |
| "taken from the repository is considered the common part of the path where " |
| "the identifier is appended." |
| msgstr "" |
| |
| |
| msgid "" |
| "-----+---------------+----------------------------+------+----------- Path | " |
| "Suffix | Identifier |Prefix| Type -----+---------------" |
| "+----------------------------+------+----------- A | |trunk/Identity/Models/" |
| "Brands| | Directory -----+---------------+----------------------------+------" |
| "+----------- B | trunk/Manual/|trunk/Identity/Models/Brands|.texi | File " |
| "-----+---------------+----------------------------+------+----------- C | " |
| "trunk/Locales/|trunk/Identity/Models/Brands| | Directory -----" |
| "+---------------+----------------------------+------+----------- D | |trunk/" |
| "Identity/Images/Brands| | Directory -----+---------------" |
| "+----------------------------+------+----------- E | trunk/Locales/|trunk/" |
| "Identity/Images/Brands|.texi | File -----+---------------" |
| "+----------------------------+------+----------- A = Master path. B = " |
| "Auxiliar path to documentation entry. C = Auxiliar path to translation " |
| "messages. D = Auxiliar path to final content output. E = Auxiliar path to " |
| "documentation entry." |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Artwork Repository is supported by Subversion (<a class=\"www\" " |
| "href=\"http://subversion.tigris.org/\">http://subversion.tigris.org/</a>), 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 "Figure 1.1: Path construction." |
| msgstr "" |
| |
| |
| msgid "" |
| "The path information described above (see <a href=\"#Path-construction" |
| "\">Path construction</a>) is used by direct rendition and can be taken as " |
| "reference to add other components that are equally produced in the " |
| "repository. To add new components that make use of direct rendition inside " |
| "the repository, change just the component name used above (e.g., " |
| "<tt>`Brands'</tt>) to that one you want to add, without changing the path " |
| "structure around it." |
| msgstr "" |
| |
| |
| msgid "" |
| "The file organization used by theme rendition extends direct rendition by " |
| "separating design models information from backgrounds information. To better " |
| "understand this configuration, you can consider it as two independent lists, " |
| "one of design models and one of artistic motifs, which are arbitrary " |
| "combined between themselves in order to render images in specific ways. The " |
| "possibilities of this configuration are endless and let us describe visual " |
| "manifestations very well. For example, consider the organization used to " |
| "produce <tt>`Anaconda'</tt> images; for CentOS distribution major release 5; " |
| "using <tt>`Default'</tt> design models and version <tt>`3'</tt> of " |
| "<tt>`Flame'</tt> artistic motif:" |
| msgstr "" |
| |
| |
| msgid "" |
| "-----+---------------+------------------------------------------------------" |
| "+------+----------- Path | Suffix | Identifier |Prefix| Type -----" |
| "+---------------+------------------------------------------------------" |
| "+------+----------- A | |trunk/Identity/Models/Themes/Default/Distro/5/" |
| "Anaconda| | Directory -----+---------------" |
| "+------------------------------------------------------+------+----------- B " |
| "| trunk/Manual/|trunk/Identity/Models/Themes/Default/Distro/5/Anaconda|.texi " |
| "| File -----+---------------" |
| "+------------------------------------------------------+------+----------- C " |
| "| trunk/Locales/|trunk/Identity/Models/Themes/Default/Distro/5/Anaconda| | " |
| "Directory -----+---------------" |
| "+------------------------------------------------------+------+----------- D " |
| "| |trunk/Identity/Images/Themes/Flame/3/Distro/5/Anaconda| | Directory -----" |
| "+---------------+------------------------------------------------------" |
| "+------+----------- E | trunk/Locales/|trunk/Identity/Images/Themes/Flame/3/" |
| "Distro/5/Anaconda|.texi | File -----+---------------" |
| "+------------------------------------------------------+------+----------- A " |
| "= Master path. B = Auxiliar path to documentation entry. C = Auxiliar path " |
| "to translation messages. D = Auxiliar path to final content output. E = " |
| "Auxiliar path to documentation entry." |
| msgstr "" |
| |
| |
| msgid "Figure 1.2: Path construction extended." |
| msgstr "" |
| |
| |
| msgid "" |
| "When using Subversion there is one <em>source repository</em> and many " |
| "<em>working copies</em> 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 works 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 path information described above (see <a href=\"#Path-construction-" |
| "extended\">Path construction extended</a>) is used by theme rendition and " |
| "can be taken as reference to add other components that are equally produced " |
| "in the repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "In this configuration we can change both design model name (e.g., " |
| "<tt>`Default'</tt>) and artistic motif name (e.g., <tt>`Flame/3'</tt>) to " |
| "something else in order to achieve a different result. The only limitations " |
| "impossed are the storage space provided in the server machine and your own " |
| "creativeness as graphic designer." |
| msgstr "" |
| |
| |
| msgid "" |
| "A theme ready for implementation may consume from 100 MB to 400 MB of " |
| "storage space. The exact space consumed by a theme depends on the amount of " |
| "screen resolutions the theme supports. The more screen resolutions the theme " |
| "supports, the more storage space demanded for it." |
| msgstr "" |
| |
| |
| msgid "" |
| "In this configuration we saw how to build the path information for " |
| "<tt>`Anaconda'</tt> component as part of CentOS Distribution visual " |
| "manifestation, but that is not the only component we have inside CentOS " |
| "Distribution visual manifestation. There are other components like Syslinux, " |
| "Grub, Rhgb, Gdm, Kdm, Gsplash and Ksplash that share a similar file " |
| "organization to that described above for <tt>`Anaconda'</tt> component." |
| msgstr "" |
| |
| |
| msgid "" |
| "[<a href=\"#SEC27\" title=\"Previous section in reading order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC29\" title=\"Next section in reading order\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "Syncronizing path information is the action that keeps all path information " |
| "up to date in the repository. This action implies both <em>file movement</" |
| "em> and <em>file content replacement</em> in this very specific order. File " |
| "movement is related to duplicate, delete and rename files and directories in " |
| "the repository. File content replacement is related to replace information, " |
| "path information in this case, inside files in the repository." |
| msgstr "" |
| |
| |
| msgid "" |
| "The order followed to syncronize path information is relevant because the " |
| "versioned nature of the files we are working with. We don't perform file " |
| "content replacement first because that would imply a repository change which " |
| "will immediatly demmand a commit in order for actions like duplicate, delete " |
| "or rename to take place. However, if we perform file movement first, it is " |
| "possible to commit both file moved and file content replacements as if they " |
| "were just one change. In this case the file content replacement takes palce " |
| "in the target location that have been duplicated or renamed, not the one use " |
| "as source location. This configuration is specially useful when files are " |
| "renamed (i.e., one file is copied from a source location to a target " |
| "location and then the source location of it is removed from repository)." |
| msgstr "" |
| |
| |
| msgid "" |
| "There is no support for URLs actions inside <code>centos-art.sh</code> " |
| "script. The <code>centos-art.sh</code> script is designed to work with local " |
| "files inside the working copy only. If you need to perform URL actions " |
| "directly, use Subversion commands instead." |
| msgstr "" |
| |
| |
| msgid "" |
| "When one master path is changed it is required that all related auxiliar " |
| "paths be changed, too. This is required in order for master paths to retain " |
| "their relation with auxiliar paths. This way, automation scripts are able to " |
| "know where to retrive translation messages from, where to store final output " |
| "images to and where to look for documentation. If 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." |
| msgstr "" |
| |
| |
| msgid "" |
| "The auxiliar paths should never be modified under any reason but to satisfy " |
| "the relationship with the master path. Liberal change of auxiliar paths may " |
| "suppress the conceptual idea they were initially created for; and certainly, " |
| "automation scripts may stop working as expected. The update direction to " |
| "rename path information must be from master path to auxiliar path and never " |
| "the opposite." |
| msgstr "" |
| |
| |
| msgid "" |
| "The relation between master and auxiliar paths is useful to keep repository " |
| "organized but introduce some complications when we work with files that use " |
| "master path information as reference to build structural information. This " |
| "is the case of repository documentation manual source files where " |
| "inclusions, menus, nodes and cross references are built using master path " |
| "information as reference. Now, to see what kind of complication we are " |
| "talking about, consider what would happen to a structural definitions (i.e., " |
| "inlusions, menus, nodes and cross refereces) already set in the manual from " |
| "one master path that is suddenly renamed to something different. If the path " |
| "information is not syncronized, at this point, we lose connection between " |
| "the master path and the auxiliar path created to store the related " |
| "documentation entry, as well as the related structural definitions that end " |
| "up pointing to a master path that no longer exist." |
| msgstr "" |
| |
| |
| msgid "" |
| "The syncronization of path information is aimed to solve these kind of " |
| "issues." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"#SEC28\" title=\"Previous section in reading order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_7.xhtml#SEC30\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "[<a href=\"#SEC18\" title=\"Previous section in reading order\"> < </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "Occasionly, you may find that new components of The CentOS Project Corporate " |
| "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 start " |
| "to create directories blindly all over, is: <em>What is the right place to " |
| "store it?</em>" |
| msgstr "" |
| |
| |
| msgid "" |
| "The best place to find answers is in The CentOS Community (see page <a class=" |
| "\"www\" href=\"http://wiki.centos.org/GettingHelp\">http://wiki.centos.org/" |
| "GettingHelp</a>), but going there with hands empty is not good idea. It may " |
| "give the impression you don't really care about. Instead, consider the " |
| "following suggestions to find your own comprehension in order to make your " |
| "own propositions based on it." |
| msgstr "" |
| |
| |
| msgid "[<a href=\"#SEC20\" title=\"Next section in reading order\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "When extending respository structure it is very useful to bear in mind The " |
| "CentOS Project Corporate Identity Structure (see section <a href=" |
| "\"repository_12.xhtml#SEC47\">The <tt>`trunk/Identity'</tt> Directory</a>) " |
| "The CentOS Mission and The CentOS Release Schema. The rest is just matter of " |
| "choosing appropriate names. It is also worth to know that each directory in " |
| "the repository responds to a conceptual idea that justifies its existence." |
| msgstr "" |
| |
| |
| msgid "" |
| "To build a directory structure, you need to define the conceptual idea first " |
| "and later create the directory. There are some locations inside the " |
| "repository that already define some concepts you probably want to reuse. For " |
| "example, <tt>`trunk/Identity/Images/Themes'</tt> to store theme artistic " |
| "motifs, <tt>`trunk/Identity/Models/Themes'</tt> to store theme design " |
| "models, <tt>`trunk/Manual'</tt> to store documentation files, <tt>`trunk/" |
| "Locales'</tt> to store translation messages, <tt>`trunk/Scripts'</tt> to " |
| "store automation scripts and so on." |
| msgstr "" |
| |
| |
| msgid "" |
| "To illustrate this desition process let's consider the <tt>`trunk/Identity/" |
| "Images/Themes/TreeFlower/3'</tt> directory structure as example. This " |
| "directory can be read as: the theme development line of version <tt>`3'</tt> " |
| "of <tt>`TreeFlower'</tt> artistic motif. Additional, we can identify that " |
| "artistic motifs are part of themes as well as themes are part of The CentOS " |
| "Project Corporate Identity. These concepts are better described " |
| "independently in each documentation entry related to the directory structure " |
| "as it is respectively shown in the list of commands bellow." |
| msgstr "" |
| |
| |
| msgid "" |
| "centos-art help --read turnk centos-art help --read turnk/Identity centos-" |
| "art help --read turnk/Identity/Themes centos-art help --read turnk/Identity/" |
| "Images/Themes centos-art help --read turnk/Identity/Images/Themes/TreeFlower " |
| "centos-art help --read turnk/Identity/Images/Themes/TreeFlower/3" |
| msgstr "" |
| |
| |
| msgid "" |
| "The concepts behind other location can be found in the same way described " |
| "above, just change the path information used above to the one you are trying " |
| "to know concepts for." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 1.5 Repository Convenctions" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Artwork Repository is a collaborative tool that anyone can have " |
| "access to. However, changing that tool in any form is something that should " |
| "be requested in <a class=\"mailto\" href=\"mailto:centos-devel@centos.org" |
| "\">centos-devel@centos.org</a> mailing list. Generally, people download " |
| "working copies from CentOS Artwork Repository, study the repository " |
| "organization, make some changes in their working copies, make some tests to " |
| "verify such changes do work the way expected and finally request access to " |
| "commit them up to the CentOS Artwork Repository (i.e., the source " |
| "repository) for others to benefit from them." |
| msgstr "" |
| |
| |
| msgid "" |
| "Once you've received access to commit your changes, there is no need for you " |
| "to request permission again to commit other changes from your working copy " |
| "to CentOS Artwork Repository as long as you behave as a <em>good community " |
| "citizen</em>." |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_6.xhtml#SEC29\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_8.xhtml#SEC31\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "If you find an error in the <em>CentOS Artwork Repository</em>, or if you " |
| "have thought of a way to make this manual better, we would like to hear from " |
| "you! Share your suggestions in the appropriate mailing list (<a class=\"www" |
| "\" href=\"http://lists.centos.org/\">http://lists.centos.org/</a>) and/or " |
| "bug tracker (<a class=\"www\" href=\"http://bugs.centos.org/\">http://bugs." |
| "centos.org/</a>)." |
| msgstr "" |
| |
| |
| msgid "" |
| "When you make suggestion, try to be as specific as possible. For example, if " |
| "you have found an error in the manual, include the section number and some " |
| "of the surrounding text so we can find it easily." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 1.6 Send in Your Feedback" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_7.xhtml#SEC30\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_9.xhtml#SEC32\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "The CentOS Artwork Repository uses directories to organize files and " |
| "describe conceptual idea about corporate identity. Such conceptual ideas are " |
| "explained in each directory related documentation entry." |
| msgstr "" |
| |
| |
| msgid "" |
| "In this chapter you'll learn what each directory inside The CentOS Artwork " |
| "Repository is for and so, how you can make use of them. For that purpose, " |
| "the following list of directories is available for you to explore:" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2. The Repository Directories" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_8.xhtml#SEC31\" title=\"Previous section in reading " |
| "order\"> < </a>]" |
| msgstr "" |
| |
| |
| |
| msgid "" |
| "[<a href=\"repository_10.xhtml#SEC37\" title=\"Next section in reading order" |
| "\"> > </a>]" |
| msgstr "" |
| |
| |
| msgid "" |
| "This directory implements the Subversion's branches concept in a trunk, " |
| "branches, tags repository structure." |
| msgstr "" |
| |
| |
| msgid "" |
| "The <tt>`branches/'</tt> directory structure provides the intermediate space " |
| "for creating several instances of <tt>`trunk/'</tt> directory structure for " |
| "parallel development and later merging changes back to <tt>`trunk/'</tt> in " |
| "the same parallel basis." |
| msgstr "" |
| |
| |
| msgid "The <tt>`branches/'</tt> directory structure is unused, so far." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: 2.1 The branches Directory" |
| msgstr "" |
| |
| |
| msgid "[ ? ]" |
| msgstr "" |
| |
| |
| msgid "About" |
| msgstr "Acerca de" |
| |
| |
| msgid "about (help)" |
| msgstr "acerca de ... (ayuda)" |
| |
| |
| msgid "" |
| "where the <strong> Example </strong> assumes that the current position is at " |
| "<strong> Subsubsection One-Two-Three </strong> of a document of the " |
| "following structure:" |
| msgstr "" |
| |
| |
| msgid "" |
| "1. Section One <ul><li>1.1 Subsection One-One <ul><li>...</li></ul></" |
| "li><li>1.2 Subsection One-Two <ul><li>1.2.1 Subsubsection One-Two-One</" |
| "li><li>1.2.2 Subsubsection One-Two-Two</li><li>1.2.3 Subsubsection One-Two-" |
| "Three <strong><== Current Position </strong></li><li>1.2.4 " |
| "Subsubsection One-Two-Four</li></ul></li><li>1.3 Subsection One-Three " |
| "<ul><li>...</li></ul></li><li>1.4 Subsection One-Four</li></ul>" |
| msgstr "" |
| |
| |
| |
| msgid "[<a href=\"#SEC_About\" title=\"About (help)\"> ? </a>]" |
| msgstr "" |
| |
| |
| msgid "About This Document" |
| msgstr "Acerca de este documento" |
| |
| |
| msgid "The buttons in the navigation panels have the following meaning:" |
| msgstr "" |
| |
| |
| msgid "Button" |
| msgstr "" |
| |
| |
| msgid "Go to" |
| msgstr "" |
| |
| |
| msgid "From 1.2.3 go to" |
| msgstr "" |
| |
| |
| msgid "[ < ]" |
| msgstr "" |
| |
| |
| msgid "Back" |
| msgstr "" |
| |
| |
| msgid "previous section in reading order" |
| msgstr "" |
| |
| |
| msgid "1.2.2" |
| msgstr "" |
| |
| |
| msgid "Forward" |
| msgstr "" |
| |
| |
| msgid "next section in reading order" |
| msgstr "" |
| |
| |
| msgid "1.2.4" |
| msgstr "" |
| |
| |
| msgid "FastBack" |
| msgstr "" |
| |
| |
| msgid "beginning of this chapter or previous chapter" |
| msgstr "" |
| |
| |
| msgid "1" |
| msgstr "" |
| |
| |
| msgid "[ Up ]" |
| msgstr "" |
| |
| |
| msgid "Up" |
| msgstr "" |
| |
| |
| msgid "up section" |
| msgstr "" |
| |
| |
| msgid "1.2" |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: About This Document" |
| msgstr "" |
| |
| |
| msgid "FastForward" |
| msgstr "" |
| |
| |
| msgid "next chapter" |
| msgstr "" |
| |
| |
| msgid "2" |
| msgstr "" |
| |
| |
| msgid "[Top]" |
| msgstr "[Inicio]" |
| |
| |
| msgid "Top" |
| msgstr "Inicio" |
| |
| |
| msgid "cover (top) of document" |
| msgstr "cubierta (inicio) del documento" |
| |
| |
| msgid "[Contents]" |
| msgstr "[Contenidos]" |
| |
| |
| msgid "Contents" |
| msgstr "" |
| |
| |
| msgid "table of contents" |
| msgstr "" |
| |
| |
| msgid "[Index]" |
| msgstr "[Índice]" |
| |
| |
| msgid "index" |
| msgstr "índice" |
| |
| |
| msgid "Footnotes" |
| msgstr "Pié de página" |
| |
| |
| msgid "(1)" |
| msgstr "" |
| |
| |
| msgid "" |
| "The theme support of Mailman may be introduced in mailman-3.x.x release." |
| msgstr "" |
| |
| |
| msgid "CentOS Artwork Repository: Footnotes" |
| msgstr "Repositorio Artístico de CentOS: Pié de página" |
| |
| |
| |
| msgid "[<a href=\"#SEC_Contents\" title=\"Table of contents\">Contents</a>]" |
| msgstr "" |
| "[<a href=\"#SEC_Contents\" title=\"Table de contenidos\">Contenidos</a>]" |
| |
| |
| msgid "Table of Contents" |
| msgstr "Tabla de contenidos" |
| |
| |
| msgid "CentOS Artwork Repository: Table of Contents" |
| msgstr "Repositorio Artístico de CentOS: Tabla de contenidos" |