<?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"> < </a>]</td>
<td valign="middle" align="left">[<a href="repository_3.xhtml#SEC7" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="repository_1.xhtml#SEC1" title="Beginning of this chapter or previous chapter"> << </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"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </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.
</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 to support the effort. This way both the CentOS Artwork
SIG and the CentOS Artwork Repository were created.
</p>
<ul class="toc">
<li> <a class="www" href="https://projects.centos.org/svn/artwork/">https://projects.centos.org/svn/artwork/</a>
</li><li> <a class="www" href="https://projects.centos.org/trac/artwork/">https://projects.centos.org/trac/artwork/</a>
</li></ul>
<p>Once the CentOS Artwork Repository was available, Alain Reguera
Delagdo uploaded the bash script for rendering Anaconda slides and
Ralph Angenendt documented the script very well.
</p>
<p>Once the rendition script and its documentation were available online,
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 designed to take one SVG file, apply one SED
file with replacement command inside to produce one SVG translated
instance that is used to produce one translated PNG image by means of
Inkscape program. The rendition script was named <code>render.sh</code>
and it is copied to each directory structure that requires such
process to produce images.
</p>
<p>Furthermore, functionalies are centralized in a common placed and
linked from different directory structures. There is no need to have
the same code in different directory structures if can have it in just
one place and then create links to it.
</p>
<p>Start to implement concepts about corporate identity. 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). The main
goal of <code>render.sh</code> becomes to: automate production of a
monolithic corporate visual identity structure based on The CentOS
Mission and The CentOS Release Schema.
</p>
<p>Around March, Alain Reguera Delgado is out of Internet for an
undefined amount of time, but continues developing the idea of CentOS
Artwork Repository and the rendition script off-line.
</p>
<p>Most of the work I propose from this time on is my own responsability.
I keep myself thinking to be part of the CentOS Artwork SIG and in
that sake, I use the personal pronoun <em>we</em> to refer what I do as
part of the group hoping someday to share this work with you again and
improve it together.
</p>
<p>The CentOS Artwork Repository documentation starts to take form in
LaTeX format.
</p>
<a name="SEC5"></a>
<h3 class="subheading"> 2010 </h3>
<p>The <code>render.sh</code> is removed from the repository directory
structures and the <code>centos-art.sh</code> script is used instead. The
<code>centos-art.sh</code> is created to be a command-line interface that
automate most frequent tasks inside the repository and can be called
anywhere inside the repository or outside it; whenever it points to a
directory structure inside the repository. At the very first moments
of using <code>centos-art.sh</code> command-line, it used to have the
following using form:
</p>
<pre class="verbatim">centos-art function --action=path/to/dir
</pre>
<p>Inside the rendition script, functionalities started to get identified
and separated one another. For example, when images are rendered,
there is no need to load manual functionality. There are now common
functionalities and specific functionalities. Common functionalities
are loaded when the script is initiated and are available to specific
functionalities.
</p>
<p>Start using <code>getopt</code> to handle command-line options.
</p>
<p>The repository directory structure is optimized to continue
implementing corporate identity concepts and the <code>centos-art</code>
command-line.
</p>
<a name="SEC6"></a>
<h3 class="subheading"> 2011 </h3>
<p>The `trunk/Translation' directory structure is removed. The
`trunk/Locales' directory structure is used instead to store locale
information.
</p>
<p>The `.sed' translation files are no longer used, scalable vector
graphics are used instead. Translation messages take place by means
of xml2po and gettext. With xml2po translatable strings are retrived
from `.svg' files and stored inside gettext `.pot' and `.po' files for
translators to edit. Finally, xml2po is used again to build the
temporal design model translated instance which the final `.png' image
is built from.
</p>
<p>Inside <code>centos-art.sh</code>, update command-line arguments and
options parsing. Keep using <code>getopt</code> to parse options passed
in the command-line, but change the way <code>centos-art.sh</code> is
called from. The following form is used:
</p>
<pre class="verbatim">centos-art function path/to/dir --options
</pre>
<p>Start using verbs to name the <code>centos-art.sh</code> functionalities.
</p>
<p>Organize <code>centos-art.sh</code> functionalities in "administrative"
functions and "productive" functions. Administrative functions
cover actions like: copying, deleting and renaming directory
structures. Also, preparing your workstation for using
<code>centos-art</code> command-line, make backups of the distribution
theme currently installed, installing themes created inside The
CentOS Artwork repository and restoring themes from backup. On the
other hand, productive functions 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"> < </a>]</td>
<td valign="middle" align="left">[<a href="repository_3.xhtml#SEC7" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="repository_1.xhtml#SEC1" title="Beginning of this chapter or previous chapter"> << </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"> >> </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>