|
|
e935c3 |
|
|
|
d9e5c1 |
<sect1 id="repository-history-section-2" label="1.2">
|
|
|
e935c3 |
|
|
|
e935c3 |
<title>2009</title>
|
|
|
e935c3 |
|
|
|
e935c3 |
<para>The rendition script is at a very rustic state where only
|
|
|
eb3c68 |
slide images can be produced, so it was redesigned to extend the
|
|
|
eb3c68 |
image production to other areas, not just slide images. In this
|
|
|
eb3c68 |
configuration, one SVG file was used as input to produced a
|
|
|
eb3c68 |
translated instance of it which, in turn, was used to produce one
|
|
|
eb3c68 |
translated PNG image as output. The SVG translated instance was
|
|
|
eb3c68 |
created through SED replacement commands. The translated PNG image
|
|
|
eb3c68 |
was created from the SVG translated instance using Inkscape
|
|
|
eb3c68 |
command-line interface.</para>
|
|
|
e935c3 |
|
|
|
eb3c68 |
<para>The rendition script was named
|
|
|
eb3c68 |
<quote>render.sh</quote>.</para>
|
|
|
e935c3 |
|
|
|
eb3c68 |
<para>The repository directory structure was prepared to receive
|
|
|
eb3c68 |
the rendition script using design templates and translation files
|
|
|
eb3c68 |
in the same location. There was one directory structure for each
|
|
|
eb3c68 |
artwork that needed to be produced. In this configuration, if you
|
|
|
eb3c68 |
would want to produce the same artwork with a different visual
|
|
|
eb3c68 |
style or structure, it was needed to create a new directory
|
|
|
eb3c68 |
structure for it because both the image structure and the image
|
|
|
eb3c68 |
visual style were together in the design template.</para>
|
|
|
e935c3 |
|
|
|
eb3c68 |
<para>The rendition script was moved to a common place and linked
|
|
|
eb3c68 |
from different directory structures. There was no need to have the
|
|
|
eb3c68 |
same code in different directory structures if it could be in just
|
|
|
eb3c68 |
one place and then be linked from different locations.</para>
|
|
|
e935c3 |
|
|
|
eb3c68 |
<para>The concepts about corporate identity began to be
|
|
|
eb3c68 |
considered. As referece, it was used the book <quote>Corporate
|
|
|
eb3c68 |
Identity</quote> by Wally Olins (1989) and Wikipedia (
|
|
|
eb3c68 |
url="http://en.wikipedia.org/Corporate_identity" />). This way,
|
|
|
eb3c68 |
the rendition script main's goal becomes to: automate production
|
|
|
eb3c68 |
of a monolithic corporate visual identity structure, based on the
|
|
|
eb3c68 |
mission and the release schema of The CentOS Project.</para>
|
|
|
e935c3 |
|
|
|
eb3c68 |
<para>The directory structures started to be documented inside the
|
|
|
eb3c68 |
repository using text files without markup. Later, documentation
|
|
|
eb3c68 |
in flat text files was moved to LaTeX format and this way
|
|
|
eb3c68 |
<quote>The CentOS Artwork Repository Manual</quote> started to
|
|
|
eb3c68 |
take form.</para>
|
|
|
e935c3 |
|
|
|
d9e5c1 |
</sect1>
|