Blob Blame History Raw
<?xml version="1.0"?>
<!DOCTYPE html
    PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>

    <title>CentOS Artwork Repository: 1.1 History</title>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
    <meta name="description" content="CentOS Artwork Repository: 1.1 History" />
    <meta name="keywords" content="CentOS Artwork Repository: 1.1 History" />
    <meta name="resource-type" content="document" />
    <meta name="distribution" content="global" />
    <meta name="generator" content="texi2html 1.76" />
    <meta name="copyright" content="2009-2011 Alain Reguera Delgado" />

    <link href="/home/centos/artwork/trunk/Identity/Manual/repository.css" rel="stylesheet" type="text/css" media="screen projection" />

</head>

<body>

<a name="top" />

<div id="wrap">

    <div id="page-body">

        <div id="content">

<!-- Created on March, 30 2011 by texi2html 1.76 -->
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="repository_1.xhtml#SEC1" title="Previous section in reading order"> &lt; </a>]</td>
<td valign="middle" align="left">[<a href="repository_3.xhtml#SEC7" title="Next section in reading order"> &gt; </a>]</td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left">[<a href="repository_1.xhtml#SEC1" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
<td valign="middle" align="left">[<a href="repository_1.xhtml#SEC1" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_7.xhtml#SEC12" title="Next chapter"> &gt;&gt; </a>]</td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left">[<a href="repository.xhtml#SEC_Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="repository_toc.xhtml#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="repository_80.xhtml#SEC416" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="repository_abt.xhtml#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="History"></a>
<a name="SEC2"></a>
<h2 class="section"> 1.1 History </h2>

<p>This section records noteworthy changes of CentOS Artwork Repository
through years.
</p>
<a name="SEC3"></a>
<h3 class="subheading"> 2008 </h3>

<p>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? 
</p>
<p>To answer the question, Alain Reguera Delgado posted a bash script to
produce slide images in different languages --together with the
proposition of creating a Subversion centralized repository where
translations and image production could be distributed inside The
CentOS Community--.
</p>
<p>Karanbirn Sighn considered the idea intresting and provides the
infrastructure necessary to support the effort. This way the CentOS
Artwork SIG and the CentOS Artwork Repository are officially created
and made available in the following urls:
</p>
<ul class="toc">
<li> <a class="www" href="https://projects.centos.org/trac/artwork/">https://projects.centos.org/trac/artwork/</a>
</li><li> <a class="www" href="https://projects.centos.org/svn/artwork/">https://projects.centos.org/svn/artwork/</a>
</li></ul>

<p>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.
</p>
<a name="SEC4"></a>
<h3 class="subheading"> 2009 </h3>

<p>The rendition script is at a very rustic state where only slide images
can be produced. 
</p>
<p>The rendition script is improved to produce not only slide images, but
PNG images using one SVG file as input. In this configuration one
translated SVG instance was created from the SVG provided as input in
order to produce one translated PNG image as output.  The translation
of SVG files is made through SED replacement commands and the
rendition of PNG images is realized through Inkscape command line
internface.
</p>
<p>The rendition script is named <code>render.sh</code>. The directory
structures are prepared to receive the rendition script so images
could be produced inside them. Each directory structure has design
templates (.svg), translation files (.sed), and translated images
(.png).
</p>
<p>The rendition script is unified in a common place and linked from
different directory structures. There is no need to have the same code
in different directory structures if it can be in just one place and
then be linked from different locations.
</p>
<p>The concepts of corporate identity started to be considered. As
referece, it is used Wikipedia
(<a class="www" href="http://en.wikipedia.org/Corporate_identity">http://en.wikipedia.org/Corporate_identity</a>) and the book
<em>Corporate Identity</em> by Wally Olins (1989). 
</p>
<p>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. 
</p>
<p>The documentation of CentOS Artwork Repository starts to take form in
LaTeX format.
</p>
<a name="SEC5"></a>
<h3 class="subheading"> 2010 </h3>

<p>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
and called anywhere inside the repository as it is usually done with
regular commands.   
</p>
<p>Inside <code>centos-art.sh</code>, functionalities started to get
identified and separated one another. For example, when images are
rendered, there is no need to load functionalities related to
documentation manual. There is now common functionalities and specific
functionalities. Common functionalities are loaded when the script is
initiated and are available to specific functionalities.
</p>
<p>The <code>centos-art.sh</code> script is updated to handle options trough
<code>getopt</code> option parser.
</p>
<p>The repository directory structure is updated to improve the
implementation of corporate visual identity concepts.
</p>
<a name="SEC6"></a>
<h3 class="subheading"> 2011 </h3>

<p>The <code>centos-art.sh</code> script is updated to translate SVG and
other XML-based files (e.g., XHTML and Docbook) through
<code>xml2po</code> program and shell scripts files through
<code>xgettext</code> command.  In this configuration there is no need to
use `.sed' translation files as they previously were used.
</p>
<p>The <code>centos-art.sh</code> script is updated to improve option
parsing through <code>getopt</code> program. All arguments are parsed by
<code>getopt</code> now. Once all option arguments have been parsed, only
non-option arguments remain for processing.
</p>
<p>The <code>centos-art.sh</code> script is updated to organize
functionalities in two groups: &quot;the administrative functionalities&quot;
and &quot;the productive functionalities&quot;.  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.
</p>
<div class="page-line white"><hr style="display:none;" /></div>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="repository_1.xhtml#SEC1" title="Previous section in reading order"> &lt; </a>]</td>
<td valign="middle" align="left">[<a href="repository_3.xhtml#SEC7" title="Next section in reading order"> &gt; </a>]</td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left">[<a href="repository_1.xhtml#SEC1" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
<td valign="middle" align="left">[<a href="repository_1.xhtml#SEC1" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_7.xhtml#SEC12" title="Next chapter"> &gt;&gt; </a>]</td>
</tr></table>

            <div class="page-line"><hr style="display:none;" /></div>

        </div>

    </div>

    <div class="page-line white"><hr style="display:none;" /></div>

</div>

</body>

</html>