diff --git a/Locales/Manuals/Userguide/es_ES/messages.po b/Locales/Manuals/Userguide/es_ES/messages.po index 8abed1a..4924ca2 100644 --- a/Locales/Manuals/Userguide/es_ES/messages.po +++ b/Locales/Manuals/Userguide/es_ES/messages.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: centos-art (es_ES)\n" "Report-Msgid-Bugs-To: CentOS Documentation SIG \n" -"POT-Creation-Date: 2011-06-09 22:50-0400\n" +"POT-Creation-Date: 2011-06-16 22:57-0400\n" "PO-Revision-Date: 2011-06-09 19:20-0400\n" "Last-Translator: CentOS Documentation SIG \n" "Language-Team: Español\n" @@ -11,7 +11,11 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" -msgid "The CentOS Artwork Repository Manual" +#. Front matter +msgid "The CentOS Artwork Repository" +msgstr "" + +msgid "User's Guide" msgstr "" msgid "Alain" @@ -52,9 +56,6 @@ msgstr "" "organización y administración del repository de los trabjajos artísticos de " "El Proyecto CentOS." -msgid "Repository" -msgstr "Repositorio" - msgid "Introduction" msgstr "Introducción" @@ -82,32 +83,37 @@ msgid "History" msgstr "" msgid "" -"The CentOS Artwork Repository started around 2008 during a discussion about " -"how to automate the slide images of Anaconda, at CentOS Developers mailing " -"list (centos-devel@centos.org). In such discussion, Ralph Angenendt rose up " -"his hand to ask —Do you have something to show?—." +"The CentOS Artwork Repository started during a discussion about how to " +"automate the slide images of Anaconda, at CentOS Developers mailing list " +"(centos-devel@centos.org) around 2008. In such discussion, Ralph Angenendt rose up his hand to " +"ask —Do you have something to show?—." msgstr "" msgid "" -"To answer the question, I 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—." +"To answer the question, Alain Reguera Delgado suggested a bash script which " +"combined SVG and SED files in order to produce PNG images in different " +"languages —in conjunction with the proposition of creating a Subversion " +"repository where translations and image production could be distributed " +"inside The CentOS Community—." msgstr "" msgid "" "Karanbirn Sighn considered the idea intresting and provided the " -"infrastructure necessary to support the effort. This way the CentOS Artwork " -"SIG (https://projects.centos.org/trac/artwork/) and the CentOS Artwork " -"Repository (https://projects.centos.org/svn/artwork/) were officially " -"created." +"infrastructure necessary to support the effort. This way the CentOS Artwork SIG and " +"the CentOS Artwork " +"Repository were officially created." msgstr "" msgid "" -"Once the CentOS Artwork Repository was available, I uploaded the bash script " -"for rendering Anaconda slides; Ralph Angenendt documented it very well; and " -"people started to download working copies of CentOS Artwork Repository to " -"produce slide images in their own languages." +"Once the CentOS Artwork Repository was available, Alain Reguera Delgado " +"uploaded the bash script for rendering Anaconda slides; Ralph Angenendt " +"documented it very well; and people started to download working copies of " +"CentOS Artwork Repository to produce slide images in their own languages." +msgstr "" + +msgid "2009's" msgstr "" msgid "" @@ -139,110 +145,137 @@ msgid "" msgstr "" msgid "" -"The concepts about corporate identity began to be considered. As referece, " -"it was used the book Corporate Identity by Wally Olins (1989) " -"and Wikipedia related links (e.g., ). This way, the rendition script main's goal becomes " -"to: automate production of a monolithic corporate visual identity structure, " -"based on the mission and the release schema of The CentOS Project." +"Corporate identity concepts began to be considered. As referece, it was used " +"the book \"Corporate Identity\" by Wally Olins (1989) and Wikipedia related " +"links. This way, the rendition script main's goal becomes into: " +"automating production of a monolithic corporate visual identity " +"structure, based on the mission and the release schema of The CentOS " +"Project." msgstr "" msgid "" -"The repository directory structures began to be documented inside by mean of " -"flat text files. Later, documentation in flat text files was moved onto " -"LaTeX format and this way The CentOS Artwork Repository Manual is initiated." +"The repository directory structures began to be documented by mean of flat " +"text files. Later, documentation in flat text files was moved onto LaTeX " +"format and this way the \"The CentOS Artwork Repository\" documentation " +"manual is initiated." +msgstr "" + +msgid "2010's" msgstr "" msgid "" "Around 2010, the rendition script changed its name from render.sh to centos-art.sh and became a collection of " -"functionalities where rendition was just one among others (e.g., documenting " -"and localizing)." +"functionalities where rendition was just one among others (e.g., " +"documentation and localization)." msgstr "" msgid "" -"The centos-art.sh was initialy conceived to organize " -"automation of most frequent tasks inside the repository based in the " -"conceptual idea of Unix toolbox: create small and specialized " -"tools that do one thing well. This way, functionalities inside " -"centos-art.sh were identified and separated one another. " -"For example, when images were rendered, there was no need to load " -"functionalities related to documentation manual. This layout moved us onto " -"common functionalities and specific functionalities inside centos-" -"art.sh script. Common functionalities are loaded when " -"centos-art.sh script is initiated and are available to " -"specific functionalities." +"The centos-art.sh was initially conceived to automate " +"frequent tasks inside the repository based in the idea of Unix toolbox: to " +"create small and specialized tools that do one thing well. This way, " +"functionalities inside centos-art.sh began to be " +"identified and separated one another. For example, when images were " +"rendered, there was no need to load functionalities related to documentation " +"manual. This layout moved us onto common functionalities and " +"specific functionalities inside centos-art.sh script. Common functionalities are loaded when centos-art." +"sh script is initiated and are available to specific " +"functionalities." msgstr "" msgid "" -"There was no need to have links all around the repository if a command-line " -"interface could be created (through symbolic links, in the ~/bin directory) and be called anywhere inside the " -"repository as it would be a regular command." +"Suddenly, no need was found to keep all the links spreaded around the " +"repository in order to execute the centos-art.sh script " +"from different locations. The centos-art command-line interface was used " +"instead. The centos-art command-line interface is a symbolic link stored " +"inside the ~/bin directory that " +"point to centos-art.sh script. As default configuration, " +"inside The CentOS Distribution, the path to ~/" +"bin is included in the search path for commands (see PATH " +"environment variable). This way, using the centos-art command-line " +"interface, it is possible for us to execute the centos-art.sh script from virtually anywhere inside the workstation, just as we " +"frequently do with regular commands." msgstr "" msgid "" -"The centos-art.sh script was redesigned to handle command-" -"line options trough getopt option parser." +"Start using GNU getopt as default option parser inside the centos-" +"art.sh script." 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 to eliminate the content " -"duplication produced by having both image structure and image visual style " -"in the same file. Now, both centos-art.sh and repository " -"directory structure are able to produce themes as result of arbitrary " -"combinations between design models (structures) and artistic motifs (visual " -"styles)." +"of corporate visual identity concepts. Specially in the area related to " +"themes. Having both structure and style in the same file introduced content " +"duplication when producing art works. Because of this reason, they were " +"divided out to separate directory structures: the design models and artistic " +"motifs directory structures. From this point on, the centos-art.sh is able to produce themes as result of arbitrary combinations " +"between design models (structures) and artistic motifs (visual styles)." msgstr "" msgid "" -"In the documentation area, the documentation files in LaTeX format were " -"migrated to Texinfo format. In this configuration, each directory structure " -"in the repository has a documentation entry associated in a Texinfo " -"structure which can be read, edited and administered (e.g., renamed, " -"deleted, copied) interactively throuch centos-art.sh. " -"Additionally, the texi2html program was used to produced " -"XHTML output customized by CSS from The CentOS Webenv." +"In the documentation area, the documents in LaTeX format were migrated to " +"Texinfo format. In this configuration, each directory structure in the " +"repository has a documentation entry associated in a Texinfo structure which " +"can be read, edited and administered (e.g., renamed, deleted and copied) " +"interactively through centos-art.sh script. Additionally, " +"the texi2html program was used to produced customized XHTML output in " +"conjunction with CSS from The CentOS Webenv." +msgstr "" + +msgid "2011's" msgstr "" msgid "" "Around 2011, the centos-art.sh script was redesigned to " -"start translating SVG and other XML-based files (e.g., XHTML and Docbook " -"files) through the xml2po program and shell scripts files " -"(e.g., Bash scripts) through GNU gettext tools. This " -"configuration provided a stronger interface for graphic designers, " -"translators and programmers to produce localized content. The SED files are " -"no longer used to handle translations." +"start translating XML-based files (e.g., SVG and Docbook files) through " +"xml2po program and shell scripts (e.g., Bash scripts) " +"through GNU gettext tools. This configuration provided a stronger " +"localization interface for graphic designers, translators and programmers. " +"The SED replacement files are no longer used to handle localization." msgstr "" msgid "" "The render, help and locale " "functionalities were consolidated as the most frequent tasks performed " -"inside the repository. Additionally, the prepare and " -"tuneup functionalities are maintained as useful tasks." +"inside the repository. Additionally, the prepare and tuneup functionalities " +"are also maintained as useful tasks." msgstr "" msgid "" -"The centos-art.sh 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 " -"centos-art.sh 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." +"In the documentation area, support for producing localized transformations " +"of DocBook XML DTD instances was added through the render and " +"locale functionalities. The render functionality uses the " +"xsltproc command-line XSLT parser in conjunction with the " +"styles provided by the docbook-style-xsl package, both of " +"them included inside The CentOS Distribution. The locale functionality " +"creates the localized portable object (PO) the " +"render functionality needs to produce localized transformations " +"of DocBook XML DTD instances." +msgstr "" + +msgid "" +"To build DocBook documentation, it was considered the idea of using concepts " +"behind repository directory structure as base, not the opposite (as I've " +"been doing with Texinfo backend, so far)." +msgstr "" + +msgid "" +"Producing documentation through DocBook XML as default documentation backend " +"consolidates render and locale even more. In this " +"configuration, once the DocBook files are written, you use locale functionality to localize the DocBook files in your prefered language " +"and later, using render functionality, you produce the XTHML " +"and PDF outputs as specified in a XSLT or DSL customization layer." msgstr "" msgid "Copying conditions" msgstr "" -msgid "Copyright © 2009, 2010, 2011 The CentOS Project" +msgid "Copyright © 2009, 2010, 2011 The CentOS Artwork SIG" msgstr "" msgid "" @@ -334,6 +367,139 @@ msgid "" "Developers mailing list (centos-devel@centos.org)." msgstr "" +msgid "Document convenctions" +msgstr "" + +msgid "" +"In this manual the personal pronoun we is used to " +"repesent The CentOS Artwork SIG, the group of persons " +"that build The CentOS Project corporate visual identity through 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 centos-art identity --render='path/to/dir' " +"command to produce contents inside the trunk/" +"Identity directory structure." +msgstr "" + +msgid "file name" +msgstr "" + +msgid "" +"File names, directory names, paths, and RPM package names are represented " +"this way. This style indicates that a particular file or directory exists " +"with that name on your system. Examples:" +msgstr "" + +msgid "" +"The init.sh file in trunk/" +"Scripts/Bash/Cli/ directory is the initialization script, written " +"in Bash, used to automate most of tasks in the repository." +msgstr "" + +msgid "" +"The centos-art command uses the ImageMagick RPM package to convert images from PNG format to other formats." +msgstr "" + +msgid "key" +msgstr "" + +msgid "A key on the keyboard is shown in this style. For example:" +msgstr "" + +msgid "" +"To use TAB completion to list particular files in a " +"directory, type @command{ls}, then a character, and finally the Tab key. " +"Your terminal displays the list of files in the working directory that begin " +"with that character." +msgstr "" + +msgid "key-combination" +msgstr "" + +msgid "A combination of keystrokes is represented in this way. For example:" +msgstr "" + +msgid "" +"The CtrlAltBackspace key combination exits your " +"graphical session and returns you to the graphical login screen or the " +"console." +msgstr "" + +#, no-wrap +msgid "computer output" +msgstr "" + +msgid "" +"Text in this style indicates text displayed to a shell prompt such as error " +"messages and responses to commands. For example:" +msgstr "" + +msgid "" +"The ls command displays the contents of a directory. For " +"example: \n" +"Config help_renameEntry.sh\n" +"help_copyEntry.sh help_restoreCrossReferences.sh\n" +"help_deleteCrossReferences.sh help_searchIndex.sh\n" +" 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 /usr/share/doc/ " +"contains additional documentation for packages installed on your system." +msgstr "" + +msgid "" +"If you modify the DHCP configuration file, the changes do not take effect " +"until you restart the DHCP daemon." +msgstr "" + +msgid "" +"Do not perform routine tasks as root — use a regular user account unless you " +"need to use the root account for system administration tasks." +msgstr "" + +msgid "" +"Be careful to remove only the necessary partitions. Removing other " +"partitions could result in data loss or a corrupted system environment." +msgstr "" + msgid "Usage convenctions" msgstr "" @@ -686,288 +852,47 @@ msgid "" "The CentOS Artwork Repository is organized through a convenctional " "trunk, branches and tags " "layout. Explanation of each directory inside the repository can be found in " -"the chapter." +"the Directories part." msgstr "" -msgid "Directories" +msgid "Send in your feedback" 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." +"If you find an error in the CentOS Artwork Repository, " +"or if you have thought of a way to make this manual better, we would like to " +"hear from you! Share your suggestions in the appropriate mailing list " +"(http://lists.centos.org/) and/or bug tracker (http://bugs.centos.org/)." 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 "trunk" -msgstr "" - -msgid "" -"The trunk directory structure " -"implements the Subversion's trunk concept in a trunk, branches, tags " -"repository structure. The trunk " -"directory structure provides the main development line inside the CentOS " -"Artwork Repository." -msgstr "" - -msgid "trunk/Identity" +"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 "" -"The trunk/Identity directory " -"implements The CentOS Project corporate identity based " -"on the The CentOS Project mission and release " -"schema." -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 "" -"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. The " -"CentOS Project corporate identity provides visibility, recognizability, " -"reputation, structure and identification to The CentOS Project organization " -"by means of corporate design, corporate " -"communication, and corporate behaviour." -msgstr "" - -msgid "" -"The corporate design is focused on the effective communication of corporate " -"messages. Corporate messages are all the information emitted from the " -"corporation to a target audience. In order for such communication to happen, " -"it is required to put the messages on a medium available for the target " -"audience to react upon. These media are know as corporate " -"manifestations, because the corporation manifests its existence " -"through them. The specific way used by the corporation to set their messages " -"on different media is what the corporate design is about." -msgstr "" - -msgid "" -"The amount of manifestations a corporation uses to communicate its existence " -"may very from one corporation to another. In the very specific case of The " -"CentOS Project, the following corporate manifestations come to mind:" -msgstr "" - -msgid "" -"The CentOS Distribution — This corporate manifestaion is built from SRPM " -"packages. There are SRPM packages that make a remarkable use of images (e." -"g., Anaconda, Grub, Syslinux, Gdm, Kdm, Gsplash, Ksplash, Rhgb, Firstboot, " -"etc.), packages that make a moderate use of images and packages that don't " -"use images at all. Also, there are some packages that make use of text-based " -"information that need to be changed, too (e.g., release notes, eula, the " -"welcome page of the web browser, etc.), in order for The CentOS Project to " -"comply the redistribution guidelines of its upstream provider. The CentOS " -"Distribution corporate manifestation focuses its attention on SRPM packages " -"that use images in a remarkable way, specifically those packages that " -"contain branding information, in both image and textual format, from the " -"upstream provider. This way, replacing image and text-based files, we " -"implement the corporate design of The CentOS Distribution corporate " -"manifestations." -msgstr "" - -msgid "" -"The CentOS Web — This corporate manifestation exists to support The CentOS " -"Distribution corporate manifestation. The CentOS Web corporate manifestation " -"covers web applications used by The CentOS Project to manifest its existence " -"on the Internet. 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 — This corporate manifestation exists to promote The " -"CentOS Distribution. The CentOS Showroom corporate manifestation 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., hosting, servers, full-time-developers, etc.), in a " -"similar way as donations may do." -msgstr "" - -msgid "" -"The corporate manifestations above seem to cover all the media required by " -"The CentOS Project, as organization, to show its existence. However, other " -"corporate manifestations could be added in the future, if needed, to cover " -"different areas like building, offices, transportation and whaterver medium " -"The CentOS Project thouches to show its existence." -msgstr "" - -msgid "" -"The CentOS Project corporate communication is based on community " -"communication and takes place through the following avenues: " -"The CentOS Chat (#centos, #centos-social}, " -"#centos-devel on irc.freenode.net)The " -"CentOS Mailing Lists ().The CentOS Forums ().The CentOS Wiki ().Social " -"events, interviews, conferences, etc." -msgstr "" - -msgid "" -"The CentOS Project corporate behaviour is based on community " -"behaviour which take place in ." -msgstr "" - -msgid "" -"The CentOS Project corporate structure is based on a monolithic " -"corporate visual identity structure. In this configuration, one " -"unique name and one unique visual style is used in all corporate " -"manifestations of The CentOS Project." -msgstr "" - -msgid "" -"In a monolithic corporate visual identity structure, internal and external " -"stakeholders feel a strong sensation of uniformity, orientation, and " -"identification with the organization. No matter if you are visiting web " -"sites, using the distribution, or acting on social events, the one unique " -"name and one unique visual style connects them all to say: Hey! we " -"are all part of The CentOS Project." -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 corporate manifestions: The CentOS Distribution, The CentOS Web and " -"The CentOS Showroom. Inside The CentOS Distribution corporate " -"manifestations, The CentOS Project maintains near to four different major " -"releases of The CentOS Distribution (e.g., the operating system), 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 corporate 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, beyond the work it might require initially. 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, " -"too. In fact, whatever thing you do to strength the visual connection among " -"The CentOS Project corporate manifestations would be very good in favor of " -"The CentOS Project recognition." -msgstr "" - -msgid "" -"Obviously, having just one visual style in all corporate manifestations for " -"eternity would be a very boring thing and would give the impression 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 corporate 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 "trunk/Identity/Models" +msgid "Visual Identity" msgstr "" msgid "..." msgstr "" -msgid "trunk/Identity/Models/Themes" -msgstr "" - -msgid "" -"This directory implements the concept of themes' design models." -msgstr "" - -msgid "" -"Themes' design models provide the structural part of images (e.g., " -"dimensions, translation markers, position of each element on the visible " -"area, etc.) required by centos-art.sh to perform theme " -"rendition. The provide the modeling characteristics for all the different " -"visual manifestations a theme is made of. Using themes' design models reduce " -"the time needed for propagating an artistic motif to different visual " -"manifestations." -msgstr "" - -msgid "" -"In this directory, themes' design models are organized by name. There is one " -"directory for each theme's design model. Each design model directory must be " -"named as specified in . Inside " -"themes' design models directories, there is one directory for each visual " -"manifestions a theme is made of. These directories are named " -"visual manifestation directories and contain one or " -"more SVG files to describe the visual structure of that visual manifestion." +msgid "The CentOS Distribution" msgstr "" -msgid "" -"Themes' design models are SVG files and can be localized " -"using the locale functionality of centos-art.sh script." +msgid "The CentOS Web-Environment" msgstr "" -msgid "trunk/Identity/Models/Themes/Default" +msgid "The CentOS Showroom" msgstr "" -msgid "" -"This directory implements the concept of themes' default design " -"models." +msgid "Localization" msgstr "" -msgid "" -"Themes' default design models provide the common structural information (e." -"g., image dimensions, translation markers, trademark position, etc.) the " -"centos-art.sh script uses to produce images when no other " -"design model is specified through the option " -"at rendition time." +msgid "Documentation" msgstr "" -msgid "trunk/Manuals" +msgid "Automation" msgstr "" msgid "Licenses" @@ -1140,17 +1065,18 @@ msgid "" "the complete corresponding machine-readable source code, which must be " "distributed under the terms of and " " above on a medium customarily used for " -"software interchange; or,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 " +"software interchange; or, 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 and above on a medium customarily " -"used for software interchange; or,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.)" +"used for software interchange; or, " +"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 "" @@ -1353,23 +1279,22 @@ msgstr "" #, no-wrap msgid "" "\n" -" <one line to give the program's name and a brief idea of what it does.>\n" -" Copyright (C) 19yy <name of author>\n" +"<one line to give the program's name and a brief idea of what it does.>\n" +"Copyright (C) 19yy <name of author>\n" " \n" -" This program is free software; you can redistribute it and/or modify\n" -" it under the terms of the GNU General Public License as published by\n" -" the Free Software Foundation; either version 2 of the License, or\n" -" (at your option) any later version.\n" +"This program is free software; you can redistribute it and/or modify\n" +"it under the terms of the GNU General Public License as published by\n" +"the Free Software Foundation; either version 2 of the License, or\n" +"(at your option) any later version.\n" " \n" -" This program is distributed in the hope that it will be useful,\n" -" but WITHOUT ANY WARRANTY; without even the implied warranty of\n" -" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n" -" GNU General Public License for more details.\n" +"This program is distributed in the hope that it will be useful,\n" +"but WITHOUT ANY WARRANTY; without even the implied warranty of\n" +"MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n" +"GNU General Public License for more details.\n" " \n" -" You should have received a copy of the GNU General Public License\n" -" along with this program; if not, write to the Free Software\n" -" Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.\n" -" " +"You should have received a copy of the GNU General Public License\n" +"along with this program; if not, write to the Free Software\n" +"Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.\n" msgstr "" msgid "" @@ -1384,11 +1309,10 @@ msgstr "" #, no-wrap msgid "" "\n" -" Gnomovision version 69, Copyright (C) 19yy name of author\n" -" Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n" -" This is free software, and you are welcome to redistribute it\n" -" under certain conditions; type `show c' for details.\n" -" " +"Gnomovision version 69, Copyright (C) 19yy name of author\n" +"Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n" +"This is free software, and you are welcome to redistribute it\n" +"under certain conditions; type `show c' for details.\n" msgstr "" msgid "" @@ -1407,12 +1331,11 @@ msgstr "" #, no-wrap msgid "" "\n" -" Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n" -" `Gnomovision' (which makes passes at compilers) written by James Hacker.\n" +"Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n" +"`Gnomovision' (which makes passes at compilers) written by James Hacker.\n" " \n" -" <signature of Ty Coon>, 1 April 1989\n" -" Ty Coon, President of Vice\n" -" " +"<signature of Ty Coon>, 1 April 1989\n" +"Ty Coon, President of Vice\n" msgstr "" msgid "" @@ -1881,15 +1804,14 @@ msgstr "" #, no-wrap msgid "" "\n" -" Copyright (C) YEAR YOUR NAME.\n" +"Copyright (C) YEAR YOUR NAME.\n" "\n" -" Permission is granted to copy, distribute and/or modify this\n" -" document under the terms of the GNU Free Documentation License,\n" -" Version 1.2 or any later version published by the Free Software\n" -" Foundation; with no Invariant Sections, no Front-Cover Texts, and\n" -" no Back-Cover Texts. A copy of the license is included in the\n" -" section entitled GNU Free Documentation License.\n" -" " +"Permission is granted to copy, distribute and/or modify this\n" +"document under the terms of the GNU Free Documentation License,\n" +"Version 1.2 or any later version published by the Free Software\n" +"Foundation; with no Invariant Sections, no Front-Cover Texts, and\n" +"no Back-Cover Texts. A copy of the license is included in the\n" +"section entitled GNU Free Documentation License.\n" msgstr "" msgid "" @@ -1900,10 +1822,9 @@ msgstr "" #, no-wrap msgid "" "\n" -" with the Invariant Sections being LIST THEIR TITLES, with the\n" -" Front-Cover Texts being LIST, and with the Back-Cover Texts being\n" -" LIST.\n" -" " +"with the Invariant Sections being LIST THEIR TITLES, with the\n" +"Front-Cover Texts being LIST, and with the Back-Cover Texts being\n" +"LIST.\n" msgstr "" msgid "" @@ -1922,3 +1843,6 @@ msgstr "" #. Put one translator per line, in the form of NAME , YEAR1, YEAR2. msgid "translator-credits" msgstr "" + +#~ msgid "Repository" +#~ msgstr "Repositorio" diff --git a/Locales/Manuals/Userguide/es_ES/messages.pot b/Locales/Manuals/Userguide/es_ES/messages.pot index d77937b..379b949 100644 --- a/Locales/Manuals/Userguide/es_ES/messages.pot +++ b/Locales/Manuals/Userguide/es_ES/messages.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2011-06-09 22:50-0400\n" +"POT-Creation-Date: 2011-06-16 22:57-0400\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -9,7 +9,11 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -msgid "The CentOS Artwork Repository Manual" +#. Front matter +msgid "The CentOS Artwork Repository" +msgstr "" + +msgid "User's Guide" msgstr "" msgid "Alain" @@ -48,9 +52,6 @@ msgid "" "Repository." msgstr "" -msgid "Repository" -msgstr "" - msgid "Introduction" msgstr "" @@ -79,35 +80,39 @@ msgid "History" msgstr "" msgid "" -"The CentOS Artwork Repository started around 2008 during a " -"discussion about how to automate the slide images of Anaconda, at " -"CentOS Developers mailing list (centos-devel@centos.org). In such " -"discussion, Ralph Angenendt rose up his hand to ask —Do you have " -"something to show?—." +"The CentOS Artwork Repository started during a discussion about how " +"to automate the slide images of Anaconda, at CentOS Developers " +"mailing list (centos-" +"devel@centos.org) around 2008. In such discussion, Ralph " +"Angenendt rose up his hand to ask —Do you have something to show?—." msgstr "" msgid "" -"To answer the question, I 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—." +"To answer the question, Alain Reguera Delgado suggested a bash " +"script which combined SVG and SED files in order to produce PNG " +"images in different languages —in conjunction with the proposition " +"of creating a Subversion repository where translations and image " +"production could be distributed inside The CentOS Community—." msgstr "" msgid "" "Karanbirn Sighn considered the idea intresting and provided the " -"infrastructure necessary to support the effort. This way the CentOS " -"Artwork SIG (https://projects.centos.org/trac/artwork/) and the " -"CentOS Artwork Repository (https://projects.centos.org/svn/" -"artwork/) were officially created." +"infrastructure necessary to support the effort. This way the CentOS Artwork " +"SIG and the CentOS Artwork Repository were officially " +"created." msgstr "" msgid "" -"Once the CentOS Artwork Repository was available, I uploaded the " -"bash script for rendering Anaconda slides; Ralph Angenendt " -"documented it very well; and people started to download working " -"copies of CentOS Artwork Repository to produce slide images in " -"their own languages." +"Once the CentOS Artwork Repository was available, Alain Reguera " +"Delgado uploaded the bash script for rendering Anaconda slides; " +"Ralph Angenendt documented it very well; and people started to " +"download working copies of CentOS Artwork Repository to produce " +"slide images in their own languages." +msgstr "" + +msgid "2009's" msgstr "" msgid "" @@ -141,120 +146,147 @@ msgid "" msgstr "" msgid "" -"The concepts about corporate identity began to be considered. As " -"referece, it was used the book Corporate Identity by " -"Wally Olins (1989) and Wikipedia related links (e.g., ). This way, the " -"rendition script main's goal becomes to: automate production of a " +"Corporate identity concepts began to be considered. As referece, it " +"was used the book \"Corporate Identity\" by Wally Olins (1989) and " +"Wikipedia related links. This way, the rendition script " +"main's goal becomes into: automating production of a " "monolithic corporate visual identity structure, based on the " -"mission and the release schema of The CentOS Project." +"mission and the release schema of The CentOS Project." msgstr "" msgid "" -"The repository directory structures began to be documented inside " -"by mean of flat text files. Later, documentation in flat text files " -"was moved onto LaTeX format and this way The CentOS Artwork " -"Repository Manual is initiated." +"The repository directory structures began to be documented by mean " +"of flat text files. Later, documentation in flat text files was " +"moved onto LaTeX format and this way the \"The CentOS Artwork " +"Repository\" documentation manual is initiated." +msgstr "" + +msgid "2010's" msgstr "" msgid "" "Around 2010, the rendition script changed its name from " "render.sh to centos-art.sh " "and became a collection of functionalities where rendition was just " -"one among others (e.g., documenting and localizing)." +"one among others (e.g., documentation and localization)." msgstr "" msgid "" -"The centos-art.sh was initialy conceived to " -"organize automation of most frequent tasks inside the repository " -"based in the conceptual idea of Unix toolbox: create " -"small and specialized tools that do one thing well. This " -"way, functionalities inside centos-art.sh were " -"identified and separated one another. For example, when images were " -"rendered, there was no need to load functionalities related to " -"documentation manual. This layout moved us onto common " -"functionalities and specific functionalities inside centos-" -"art.sh script. Common functionalities are loaded when " -"centos-art.sh script is initiated and are " -"available to specific functionalities." +"The centos-art.sh was initially conceived to " +"automate frequent tasks inside the repository based in the idea of " +"Unix toolbox: to create small and specialized tools that do one " +"thing well. This way, functionalities inside centos-art." +"sh began to be identified and separated one another. For " +"example, when images were rendered, there was no need to load " +"functionalities related to documentation manual. This layout moved " +"us onto common functionalities and specific " +"functionalities inside centos-art.sh " +"script. Common functionalities are loaded when centos-art." +"sh script is initiated and are available to specific " +"functionalities." msgstr "" msgid "" -"There was no need to have links all around the repository if a " -"command-line interface could be created (through symbolic links, in " -"the ~/bin directory) and " -"be called anywhere inside the repository as it would be a regular " -"command." +"Suddenly, no need was found to keep all the links spreaded around " +"the repository in order to execute the centos-art.sh script from different locations. The centos-art command-" +"line interface was used instead. The centos-art command-line " +"interface is a symbolic link stored inside the ~/bin directory that point to " +"centos-art.sh script. As default configuration, " +"inside The CentOS Distribution, the path to ~/bin is included in the search path for " +"commands (see PATH environment variable). This way, using the " +"centos-art command-line interface, it is possible for us to execute " +"the centos-art.sh script from virtually anywhere " +"inside the workstation, just as we frequently do with regular " +"commands." msgstr "" msgid "" -"The centos-art.sh script was redesigned to " -"handle command-line options trough getopt option " -"parser." +"Start using GNU getopt as default option parser inside the " +"centos-art.sh script." 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 to eliminate the content duplication produced by having " -"both image structure and image visual style in the same file. Now, " -"both centos-art.sh and repository directory " -"structure are able to produce themes as result of arbitrary " +"implementation of corporate visual identity concepts. Specially in " +"the area related to themes. Having both structure and style in the " +"same file introduced content duplication when producing art works. " +"Because of this reason, they were divided out to separate directory " +"structures: the design models and artistic motifs directory " +"structures. From this point on, the centos-art.sh is able to produce themes as result of arbitrary " "combinations between design models (structures) and artistic motifs " "(visual styles)." msgstr "" msgid "" -"In the documentation area, the documentation files in LaTeX format " -"were migrated to Texinfo format. In this configuration, each " -"directory structure in the repository has a documentation entry " -"associated in a Texinfo structure which can be read, edited and " -"administered (e.g., renamed, deleted, copied) interactively throuch " -"centos-art.sh. Additionally, the " -"texi2html program was used to produced XHTML " -"output customized by CSS from The CentOS Webenv." +"In the documentation area, the documents in LaTeX format were " +"migrated to Texinfo format. In this configuration, each directory " +"structure in the repository has a documentation entry associated in " +"a Texinfo structure which can be read, edited and administered (e." +"g., renamed, deleted and copied) interactively through " +"centos-art.sh script. Additionally, the " +"texi2html program was used to produced customized XHTML output in " +"conjunction with CSS from The CentOS Webenv." +msgstr "" + +msgid "2011's" msgstr "" msgid "" "Around 2011, the centos-art.sh script was " -"redesigned to start translating SVG and other XML-based files (e." -"g., XHTML and Docbook files) through the xml2po " -"program and shell scripts files (e.g., Bash scripts) through GNU " -"gettext tools. This configuration provided a " -"stronger interface for graphic designers, translators and " -"programmers to produce localized content. The SED files are no " -"longer used to handle translations." +"redesigned to start translating XML-based files (e.g., SVG and " +"Docbook files) through xml2po program and shell " +"scripts (e.g., Bash scripts) through GNU gettext tools. This " +"configuration provided a stronger localization interface for " +"graphic designers, translators and programmers. The SED replacement " +"files are no longer used to handle localization." msgstr "" msgid "" "The render, help and locale " "functionalities were consolidated as the most frequent tasks " -"performed inside the repository. Additionally, the prepare and tuneup functionalities are maintained as " -"useful tasks." +"performed inside the repository. Additionally, the prepare and " +"tuneup functionalities are also maintained as useful tasks." msgstr "" msgid "" -"The centos-art.sh 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 " -"centos-art.sh 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." +"In the documentation area, support for producing localized " +"transformations of DocBook XML DTD instances was added through the " +"render and locale functionalities. The render functionality uses the xsltproc command-line XSLT parser in conjunction with the styles provided by the " +"docbook-style-xsl package, both of them included " +"inside The CentOS Distribution. The locale functionality creates " +"the localized portable object (PO) the " +"render functionality needs to produce localized " +"transformations of DocBook XML DTD instances." +msgstr "" + +msgid "" +"To build DocBook documentation, it was considered the idea of using " +"concepts behind repository directory structure as base, not the " +"opposite (as I've been doing with Texinfo backend, so far)." +msgstr "" + +msgid "" +"Producing documentation through DocBook XML as default " +"documentation backend consolidates render and " +"locale even more. In this configuration, once the " +"DocBook files are written, you use locale " +"functionality to localize the DocBook files in your prefered " +"language and later, using render functionality, you " +"produce the XTHML and PDF outputs as specified in a XSLT or DSL " +"customization layer." msgstr "" msgid "Copying conditions" msgstr "" -msgid "Copyright © 2009, 2010, 2011 The CentOS Project" +msgid "Copyright © 2009, 2010, 2011 The CentOS Artwork SIG" msgstr "" msgid "" @@ -352,6 +384,147 @@ msgid "" "CentOS Developers mailing list (centos-devel@centos.org)." msgstr "" +msgid "Document convenctions" +msgstr "" + +msgid "" +"In this manual the personal pronoun we is used " +"to repesent The CentOS Artwork SIG, the group " +"of persons that build The CentOS Project corporate visual identity " +"through 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 centos-art identity --render='path/to/dir' command to produce contents inside the trunk/Identity directory structure." +msgstr "" + +msgid "file name" +msgstr "" + +msgid "" +"File names, directory names, paths, and RPM package names are " +"represented this way. This style indicates that a particular file " +"or directory exists with that name on your system. Examples:" +msgstr "" + +msgid "" +"The init.sh file in trunk/Scripts/Bash/Cli/ directory is the " +"initialization script, written in Bash, used to automate most of " +"tasks in the repository." +msgstr "" + +msgid "" +"The centos-art command uses the " +"ImageMagick RPM package to convert images from " +"PNG format to other formats." +msgstr "" + +msgid "key" +msgstr "" + +msgid "A key on the keyboard is shown in this style. For example:" +msgstr "" + +msgid "" +"To use TAB completion to list particular files in " +"a directory, type @command{ls}, then a character, and finally the " +"Tab key. Your terminal displays the list of files in the working " +"directory that begin with that character." +msgstr "" + +msgid "key-combination" +msgstr "" + +msgid "" +"A combination of keystrokes is represented in this way. For example:" +msgstr "" + +msgid "" +"The CtrlAltBackspace key combination exits " +"your graphical session and returns you to the graphical login " +"screen or the console." +msgstr "" + +#, no-wrap +msgid "computer output" +msgstr "" + +msgid "" +"Text in this style indicates text displayed to a shell prompt such " +"as error messages and responses to commands. For example:" +msgstr "" + +msgid "" +"The ls command displays the contents of a " +"directory. For example: \n" +"Config help_renameEntry.sh\n" +"help_copyEntry.sh help_restoreCrossReferences.sh\n" +"help_deleteCrossReferences.sh help_searchIndex.sh\n" +" 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 /usr/share/doc/ contains additional documentation for packages installed " +"on your system." +msgstr "" + +msgid "" +"If you modify the DHCP configuration file, the changes do not take " +"effect until you restart the DHCP daemon." +msgstr "" + +msgid "" +"Do not perform routine tasks as root — use a regular user account " +"unless you need to use the root account for system administration " +"tasks." +msgstr "" + +msgid "" +"Be careful to remove only the necessary partitions. Removing other " +"partitions could result in data loss or a corrupted system " +"environment." +msgstr "" + msgid "Usage convenctions" msgstr "" @@ -737,312 +910,49 @@ msgid "" "The CentOS Artwork Repository is organized through a convenctional " "trunk, branches and tags layout. Explanation of each directory inside the repository " -"can be found in the chapter." -msgstr "" - -msgid "Directories" -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 "trunk" -msgstr "" - -msgid "" -"The trunk directory " -"structure implements the Subversion's trunk concept in a trunk, " -"branches, tags repository structure. The trunk directory structure provides the main " -"development line inside the CentOS Artwork Repository." -msgstr "" - -msgid "trunk/Identity" -msgstr "" - -msgid "" -"The trunk/Identity " -"directory implements The CentOS Project corporate " -"identity based on the The CentOS Project " -"mission and release schema." -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 "" -"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. The " -"CentOS Project corporate identity provides visibility, " -"recognizability, reputation, structure and identification to The " -"CentOS Project organization by means of corporate design, corporate communication, and " -"corporate behaviour." -msgstr "" - -msgid "" -"The corporate design is focused on the effective communication of " -"corporate messages. Corporate messages are all the information " -"emitted from the corporation to a target audience. In order for " -"such communication to happen, it is required to put the messages on " -"a medium available for the target audience to react upon. These " -"media are know as corporate manifestations, " -"because the corporation manifests its existence through them. The " -"specific way used by the corporation to set their messages on " -"different media is what the corporate design is about." -msgstr "" - -msgid "" -"The amount of manifestations a corporation uses to communicate its " -"existence may very from one corporation to another. In the very " -"specific case of The CentOS Project, the following corporate " -"manifestations come to mind:" -msgstr "" - -msgid "" -"The CentOS Distribution — This corporate manifestaion is built from " -"SRPM packages. There are SRPM packages that make a remarkable use " -"of images (e.g., Anaconda, Grub, Syslinux, Gdm, Kdm, Gsplash, " -"Ksplash, Rhgb, Firstboot, etc.), packages that make a moderate use " -"of images and packages that don't use images at all. Also, there " -"are some packages that make use of text-based information that need " -"to be changed, too (e.g., release notes, eula, the welcome page of " -"the web browser, etc.), in order for The CentOS Project to comply " -"the redistribution guidelines of its upstream provider. The CentOS " -"Distribution corporate manifestation focuses its attention on SRPM " -"packages that use images in a remarkable way, specifically those " -"packages that contain branding information, in both image and " -"textual format, from the upstream provider. This way, replacing " -"image and text-based files, we implement the corporate design of " -"The CentOS Distribution corporate manifestations." -msgstr "" - -msgid "" -"The CentOS Web — This corporate manifestation exists to support The " -"CentOS Distribution corporate manifestation. The CentOS Web " -"corporate manifestation covers web applications used by The CentOS " -"Project to manifest its existence on the Internet. 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 — This corporate manifestation exists to " -"promote The CentOS Distribution. The CentOS Showroom corporate " -"manifestation 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., hosting, servers, full-time-developers, etc.), in a " -"similar way as donations may do." +"can be found in the Directories part." msgstr "" -msgid "" -"The corporate manifestations above seem to cover all the media " -"required by The CentOS Project, as organization, to show its " -"existence. However, other corporate manifestations could be added " -"in the future, if needed, to cover different areas like building, " -"offices, transportation and whaterver medium The CentOS Project " -"thouches to show its existence." +msgid "Send in your feedback" msgstr "" msgid "" -"The CentOS Project corporate communication is based on " -"community communication and takes place " -"through the following avenues: The " -"CentOS Chat (#centos, #centos-social}, #centos-devel on irc." -"freenode.net)The CentOS Mailing " -"Lists ().The CentOS Forums ().The " -"CentOS Wiki ().Social events, interviews, conferences, " -"etc." +"If you find an error in the CentOS Artwork Repository, or if you have thought of a way to make this manual " +"better, we would like to hear from you! Share your suggestions in " +"the appropriate mailing list (http://lists.centos.org/) and/or bug " +"tracker (http://bugs.centos.org/)." msgstr "" msgid "" -"The CentOS Project corporate behaviour is based on " -"community behaviour which take place in ." +"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 "" -"The CentOS Project corporate structure is based on a " -"monolithic corporate visual identity structure. In this configuration, one unique name and one unique " -"visual style is used in all corporate manifestations of The CentOS " -"Project." -msgstr "" - -msgid "" -"In a monolithic corporate visual identity structure, internal and " -"external stakeholders feel a strong sensation of uniformity, " -"orientation, and identification with the organization. No matter if " -"you are visiting web sites, using the distribution, or acting on " -"social events, the one unique name and one unique visual style " -"connects them all to say: Hey! we are all part of The " -"CentOS Project." -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 corporate manifestions: The CentOS Distribution, " -"The CentOS Web and The CentOS Showroom. Inside The CentOS " -"Distribution corporate manifestations, The CentOS Project maintains " -"near to four different major releases of The CentOS Distribution (e." -"g., the operating system), 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 corporate 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, beyond " -"the work it might require initially. 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, too. In fact, whatever thing you do to strength the " -"visual connection among The CentOS Project corporate manifestations " -"would be very good in favor of The CentOS Project recognition." -msgstr "" - -msgid "" -"Obviously, having just one visual style in all corporate " -"manifestations for eternity would be a very boring thing and would " -"give the impression 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 corporate 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 "trunk/Identity/Models" +msgid "Visual Identity" msgstr "" msgid "..." msgstr "" -msgid "trunk/Identity/Models/Themes" -msgstr "" - -msgid "" -"This directory implements the concept of themes' design " -"models." -msgstr "" - -msgid "" -"Themes' design models provide the structural part of images (e.g., " -"dimensions, translation markers, position of each element on the " -"visible area, etc.) required by centos-art.sh to " -"perform theme rendition. The provide the modeling characteristics " -"for all the different visual manifestations a theme is made of. " -"Using themes' design models reduce the time needed for propagating " -"an artistic motif to different visual manifestations." -msgstr "" - -msgid "" -"In this directory, themes' design models are organized by name. " -"There is one directory for each theme's design model. Each design " -"model directory must be named as specified in . Inside themes' design models directories, " -"there is one directory for each visual manifestions a theme is made " -"of. These directories are named visual manifestation " -"directories and contain one or more SVG files to " -"describe the visual structure of that visual manifestion." +msgid "The CentOS Distribution" msgstr "" -msgid "" -"Themes' design models are SVG files and can be " -"localized using the locale functionality of " -"centos-art.sh script." +msgid "The CentOS Web-Environment" msgstr "" -msgid "trunk/Identity/Models/Themes/Default" +msgid "The CentOS Showroom" msgstr "" -msgid "" -"This directory implements the concept of themes' default " -"design models." +msgid "Localization" msgstr "" -msgid "" -"Themes' default design models provide the common structural " -"information (e.g., image dimensions, translation markers, trademark " -"position, etc.) the centos-art.sh script uses to " -"produce images when no other design model is specified through the " -" option at rendition time." +msgid "Documentation" msgstr "" -msgid "trunk/Manuals" +msgid "Automation" msgstr "" msgid "Licenses" @@ -1228,20 +1138,20 @@ msgid "" "corresponding machine-readable source code, which must be " "distributed under the terms of " "and above on a medium " -"customarily used for software interchange; or,Accompany it with a written offer, valid " +"customarily used for software interchange; or, 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 and above on a medium " -"customarily used for software interchange; or,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.)" +"customarily used for software interchange; or, 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 "" @@ -1456,23 +1366,22 @@ msgstr "" #, no-wrap msgid "" "\n" -" <one line to give the program's name and a brief idea of what it does.>\n" -" Copyright (C) 19yy <name of author>\n" +"<one line to give the program's name and a brief idea of what it does.>\n" +"Copyright (C) 19yy <name of author>\n" " \n" -" This program is free software; you can redistribute it and/or modify\n" -" it under the terms of the GNU General Public License as published by\n" -" the Free Software Foundation; either version 2 of the License, or\n" -" (at your option) any later version.\n" +"This program is free software; you can redistribute it and/or modify\n" +"it under the terms of the GNU General Public License as published by\n" +"the Free Software Foundation; either version 2 of the License, or\n" +"(at your option) any later version.\n" " \n" -" This program is distributed in the hope that it will be useful,\n" -" but WITHOUT ANY WARRANTY; without even the implied warranty of\n" -" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n" -" GNU General Public License for more details.\n" +"This program is distributed in the hope that it will be useful,\n" +"but WITHOUT ANY WARRANTY; without even the implied warranty of\n" +"MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n" +"GNU General Public License for more details.\n" " \n" -" You should have received a copy of the GNU General Public License\n" -" along with this program; if not, write to the Free Software\n" -" Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.\n" -" " +"You should have received a copy of the GNU General Public License\n" +"along with this program; if not, write to the Free Software\n" +"Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.\n" msgstr "" msgid "" @@ -1488,11 +1397,10 @@ msgstr "" #, no-wrap msgid "" "\n" -" Gnomovision version 69, Copyright (C) 19yy name of author\n" -" Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n" -" This is free software, and you are welcome to redistribute it\n" -" under certain conditions; type `show c' for details.\n" -" " +"Gnomovision version 69, Copyright (C) 19yy name of author\n" +"Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n" +"This is free software, and you are welcome to redistribute it\n" +"under certain conditions; type `show c' for details.\n" msgstr "" msgid "" @@ -1512,12 +1420,11 @@ msgstr "" #, no-wrap msgid "" "\n" -" Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n" -" `Gnomovision' (which makes passes at compilers) written by James Hacker.\n" +"Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n" +"`Gnomovision' (which makes passes at compilers) written by James Hacker.\n" " \n" -" <signature of Ty Coon>, 1 April 1989\n" -" Ty Coon, President of Vice\n" -" " +"<signature of Ty Coon>, 1 April 1989\n" +"Ty Coon, President of Vice\n" msgstr "" msgid "" @@ -2025,15 +1932,14 @@ msgstr "" #, no-wrap msgid "" "\n" -" Copyright (C) YEAR YOUR NAME.\n" +"Copyright (C) YEAR YOUR NAME.\n" "\n" -" Permission is granted to copy, distribute and/or modify this\n" -" document under the terms of the GNU Free Documentation License,\n" -" Version 1.2 or any later version published by the Free Software\n" -" Foundation; with no Invariant Sections, no Front-Cover Texts, and\n" -" no Back-Cover Texts. A copy of the license is included in the\n" -" section entitled GNU Free Documentation License.\n" -" " +"Permission is granted to copy, distribute and/or modify this\n" +"document under the terms of the GNU Free Documentation License,\n" +"Version 1.2 or any later version published by the Free Software\n" +"Foundation; with no Invariant Sections, no Front-Cover Texts, and\n" +"no Back-Cover Texts. A copy of the license is included in the\n" +"section entitled GNU Free Documentation License.\n" msgstr "" msgid "" @@ -2045,10 +1951,9 @@ msgstr "" #, no-wrap msgid "" "\n" -" with the Invariant Sections being LIST THEIR TITLES, with the\n" -" Front-Cover Texts being LIST, and with the Back-Cover Texts being\n" -" LIST.\n" -" " +"with the Invariant Sections being LIST THEIR TITLES, with the\n" +"Front-Cover Texts being LIST, and with the Back-Cover Texts being\n" +"LIST.\n" msgstr "" msgid ""