diff --git a/Manuals/Texinfo/en_US/Introduction/history.texinfo b/Manuals/Texinfo/en_US/Introduction/history.texinfo index 1785ad1..d96b914 100755 --- a/Manuals/Texinfo/en_US/Introduction/history.texinfo +++ b/Manuals/Texinfo/en_US/Introduction/history.texinfo @@ -4,94 +4,110 @@ through years. @subheading 2008 The CentOS Artwork Repository started at CentOS Developers mailing -list (@email{centos-devel@@centos.org}) during a discussion about how +(@email{centos-devel@@centos.org}) 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? - +Angenendt rose up his hand to ask: Do you have something to show? + 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---. - + 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: - -@itemize -@item @url{https://projects.centos.org/trac/artwork/} -@item @url{https://projects.centos.org/svn/artwork/} -@end itemize - +infrastructure necessary to support the effort. This way the CentOS +Artwork SIG (@url{https://projects.centos.org/trac/artwork/}) and the +CentOS Artwork Repository +(@url{https://projects.centos.org/svn/artwork/}) were officially +created. + 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. +Angenendt documented it very well; and people started to download +working copies of CentOS Artwork Repository to produce slide images in +their own languages. @subheading 2009 -The rendition script is at a very rustic state where only slide images -can be produced. - -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. - -The rendition script was named @command{render.sh}. 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). - -The rendition script was unified in a common place and linked from +The rendition script was at a very rustic state where only slide +images could be produced, so it was redesigned to extend the image +production to other areas, not just slide images. In this +configuration, one SVG file was used as input to produce a translated +instance of it which, in turn, was used to produce one translated PNG +image as output. The SVG translated instance was created through SED +replacement commands. The translated PNG image was created from the +SVG translated instance using Inkscape command-line interface. + +The rendition script was named @command{render.sh}. + +The repository directory structure was prepared to receive the +rendition script using design templates and translation files in the +same location. There was one directory structure for each artwork +that needed to be produced. In this configuration, if you would want +to produce the same artwork with a different visual style or +structure, it was needed to create a new directory structure for it +because both the image structure and the image visual style were +together in the design template. + +The rendition script was moved to a common place and linked from different directory structures. There was no need to have the same code in different directory structures if it could be in just one place and then be linked from different locations. - -Concepts about corporate identity began to be considered. As referece, -it was used the book @emph{Corporate Identity} by Wally Olins (1989) -and Wikipedia (@url{http://en.wikipedia.org/Corporate_identity}). - -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. - -The documentation of CentOS Artwork Repository started to take form in -@LaTeX{} format. + +The concepts about corporate identity began to be considered. As +referece, it was used the book ``Corporate Identity'' by Wally Olins +(1989) and Wikipedia +(@url{http://en.wikipedia.org/Corporate_identity}). 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. + +The directory structures started to be documented inside the +repository using text files without markup. Later, documentation in +flat text files was moved to LaTeX format and this way ``The CentOS +Artwork Repository Manual'' started to take form. @subheading 2010 -The rendition script @command{render.sh} is no longer a rendition -script, but a collection of functionalities grouped into the -@command{centos-art.sh} script where rendition is one functionality -among others. The @command{centos-art.sh} 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 +The rendition script changed its name from @command{render.sh} to +@command{centos-art.sh} and became a collection of functionalities +where rendition was just one among others (e.g., documenting and +localizing). + +The @command{centos-art.sh} was created to organize automation of most +frequent tasks inside the repository. There was no need to have links +all around the repository if a command-line interface could be created (through symbolic links, in the @file{~/bin} directory) and be called -anywhere inside the repository as it would be usually done with -regular commands. +anywhere inside the repository as it would be a regular command. Inside @command{centos-art.sh}, 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 @command{centos-art.sh} script. Common -functionalities are loaded when the script is initiated and are -available to specific functionalities. +documentation manual. This layout moved us onto common functionalities +and specific functionalities inside @command{centos-art.sh} script. +Common functionalities are loaded when @command{centos-art.sh} script +is initiated and are available to specific functionalities. -The @command{centos-art.sh} script was redesigned to handle options -trough @command{getopt} option parser. +The @command{centos-art.sh} script was redesigned to handle +command-line options trough @command{getopt} option parser. 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. +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, themes are produced as result of +arbitrary combinations of both design models (structures) and artistic +motifs (visual styles). + +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 +@command{centos-art.sh}. Additionally, the @command{texi2html} program +was used to produced XHTML output customized by CSS from The CentOS +Webenv. @subheading 2011 @@ -100,19 +116,24 @@ SVG and other XML-based files (e.g., XHTML and Docbook files) through the @command{xml2po} program and shell scripts files (e.g., Bash scripts) through GNU @command{gettext} tools. This configuration provided a stronger interface for graphic designers, translators and -programmers at time of producing localized content. @file{.sed} files -are no longer used to handle translations. +programmers to produce localized content. The SED files are no longer +used to handle translations. Improve option parsing through @command{getopt}. +Consolidate the @code{render}, @code{help} and @code{locale} +functionalities as the most frequent tasks performed inside the +repository. Additionally, the @code{prepare} and @code{tuneup} +functionalities are maintained as useful tasks. + The @command{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 @command{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. +directory structures inside the repository. Also, preparing your +workstation for using @command{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. diff --git a/Manuals/Texinfo/en_US/repository.texinfo b/Manuals/Texinfo/en_US/repository.texinfo index 43f7aa8..dd3ff8e 100644 --- a/Manuals/Texinfo/en_US/repository.texinfo +++ b/Manuals/Texinfo/en_US/repository.texinfo @@ -10,7 +10,7 @@ This manuals documents relevant information regarding the deployment, organization, and administration of CentOS Artwork Repository. -Copyright @copyright{} 2009, 2010, 2011 The CentOS Project +Copyright @copyright{} 2009, 2010, 2011 The CentOS Artwork SIG Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or diff --git a/Manuals/Texinfo/es_ES/repository.texinfo b/Manuals/Texinfo/es_ES/repository.texinfo index 67c21b7..d3e7d8f 100644 --- a/Manuals/Texinfo/es_ES/repository.texinfo +++ b/Manuals/Texinfo/es_ES/repository.texinfo @@ -15,7 +15,7 @@ Este manual documenta informaci@'on relevante al desempe@~no, organizaci@'on y administraci@'on del repositorio art@'istico del proyecto CentOS. -Copyright @copyright{} 2009, 2010, 2011 The CentOS Project +Copyright @copyright{} 2009, 2010, 2011 The CentOS Artwork SIG Se otorga permiso para copiar, distribuir y/o modificar este documento bajo los t@'erminos de la Licencia de Documentaci@'on Libre de GNU,