<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">
<html>
<!--This manual describes what the CentOS Artwork Repository is and what
can you do inside it.
Copyright C 2009, 2010 CentOS Artwork SIG. All rights
reserved.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
<!-- Created on October, 27 2010 by texi2html 1.76 -->
<!--
Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
Olaf Bachmann <obachman@mathematik.uni-kl.de>
and many others.
Maintained by: Many creative people <dev@texi2html.cvshome.org>
Send bugs and suggestions to <users@texi2html.cvshome.org>
-->
<head>
<title>CentOS Artwork Repository: 3.1 trunk/Identity</title>
<meta name="description" content="CentOS Artwork Repository: 3.1 trunk/Identity">
<meta name="keywords" content="CentOS Artwork Repository: 3.1 trunk/Identity">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2html 1.76">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css">
<!--
@import "/home/centos/artwork/trunk/Identity/Models/Css/Texi2html/common.css";
a.summary-letter {text-decoration: none}
pre.display {font-family: serif}
pre.format {font-family: serif}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: serif; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: serif; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.sansserif {font-family:sans-serif; font-weight:normal;}
ul.toc {list-style: none}
-->
</style>
</head>
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="repository_3.html#SEC3" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="#SEC5" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="repository_3.html#SEC3" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="repository_3.html#SEC3" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_63.html#SEC349" 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.html#SEC_Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="repository_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="repository_63.html#SEC349" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="repository_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="trunk-Identity"></a>
<a name="SEC4"></a>
<h2 class="section"> 3.1 trunk/Identity </h2>
<a name="SEC5"></a>
<h3 class="subsection"> 3.1.1 Goals </h3>
<p>The <tt>`trunk/Identity'</tt> directory exists to organize CentOS
corporate identity artworks.
</p>
<a name="SEC6"></a>
<h3 class="subsection"> 3.1.2 Description </h3>
<p>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
visual identity expresses the values and ambitions of the CentOS
Project organization, its business, and its characteristics.
</p>
<p>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.
</p>
<p>The CentOS Project settles down its corporate visual identity on a
"monolithic corporate visual identity structure". In this structure
The CentOS Project uses one unique name (The CentOS Brand) and one
unique visual style (The CentOS Default Theme) in all its
manifestations.
</p>
<dl compact="compact">
<dt> <strong>The CentOS Brands</strong></dt>
<dd><p>The CentOS brand is the name or trademark that conncects the producer
with their products. In this case, the producer is The CentOS Project
and the products are the CentOS distributions, the CentOS web sites,
the CentOS promotion stuff, etc.
</p>
<p>See section <a href="repository_5.html#SEC20">trunk/Identity/Brands</a>, for more information.
</p>
</dd>
<dt> <strong>The CentOS Themes</strong></dt>
<dd><p>The CentOS themes are a set of image files connected by one unique
visual style. The CentOS themes implements CentOS project corporate
visual identity in each visual manifestation of CentOS project (e.g.,
distributions, websites, promotion stuff, etc.).
</p>
<p>See section <a href="repository_17.html#SEC90">trunk/Identity/Themes</a>, for more information.
</p></dd>
</dl>
<p>Inside a monolithic corporate visual identity structure, internal and
external stakeholders use to feel a strong sensation of uniformity,
orientation, and identification with the organization. No matter if
you are visiting websites, using the distribution, or acting on social
events, the one unique name and one unique visual style conect them
all to say: Hey! we are all parts of the CentOS project. And,
probably, some vister will say: Can I join the party? Yes you can, it
is free. :)
</p>
<a name="SEC7"></a>
<h3 class="subsection"> 3.1.3 Usage </h3>
<p>To produce identity artworks, use the following commands:
</p>
<dl compact="compact">
<dt> <samp>`centos-art render 'path/to/dir''</samp> </dt>
<dd>
<p>When <samp>`path/to/dir'</samp> refers to one renderable directory under
<tt>`trunk/Identity'</tt>, this command renders identity artworks using
both related design models and related translation files.
</p>
</dd>
<dt> <samp>`centos-art render 'path/to/dir' --filter='pattern''</samp> </dt>
<dd>
<p>When <samp>`path/to/dir'</samp> refers to one renderable directory under
<tt>`trunk/Identity'</tt>, this command renders identity artworks using
both related design models and related translation files that match
the regular expression passed in <samp>`--filter='pattern''</samp> argument.
</p>
<p>To control the number of files produced by <code>centos-art</code>
command, you need to look into the translation path and provide a
regular expression pattern that matches the translation path, or
paths, related to the file, or files, you want to produce.
</p>
<p>The regular expression pattern you provide to <code>centos-art</code>
command is applied to the translation path from its very beginning.
It is not the same to say <samp>`5/en/01-welcome'</samp> that
<samp>`01-welcome'</samp>, the frist expression matches but the last one does
not.
</p>
<p>When using <samp>`--filter='pattern''</samp> you don't need to specify the
file extension. It is removed from translation path before applying
the pattern, so it doesn't count here.
</p></dd>
</dl>
<a name="SEC8"></a>
<h3 class="subsection"> 3.1.4 Renderable directories </h3>
<p>Inside <tt>`trunk/Identity'</tt>, renderable directories should have one
of the following directory layouts:
</p>
<a name="SEC9"></a>
<h4 class="subsubsection"> 3.1.4.1 Layout 1: Simple image rendering </h4>
<p>This directory layout contains one <tt>`Img/'</tt> directory (to store
final images), one <tt>`Tpl/'</tt> directory to store design templates,
and the translation entry is empty (there isn't translation files in
this configuration). In this configuration, one design template
produces one untranslated PNG image, just as it is in the template.
</p>
<pre class="verbatim">trunk/Identity/path/to/dir
|-- Img
| |-- anaconda_header_fig1.png
| |-- anaconda_header_fig2.png
| `-- anaconda_header_summary.png
`-- Tpl
|-- anaconda_header_fig1.svg
|-- anaconda_header_fig2.svg
`-- anaconda_header_summary.svg
</pre>
<a name="SEC10"></a>
<h4 class="subsubsection"> 3.1.4.2 Layout 2: Simple image rendering (extended) </h4>
<p>This directory layout contains one <tt>`Img/'</tt> directory (to store
final images), one <tt>`Tpl/'</tt> directory to store design templates,
and the translation entry is empty (there isn't translation files in
this configuration). When images are rendered, the <tt>`Img/'</tt>
directory structure is created automatically using the <tt>`Tpl/'</tt>
directory structure as reference. In this configuration, one design
template produces one untranslated PNG image, just as it is in the
template.
</p>
<pre class="verbatim">trunk/Identity/path/to/dir
|-- Img
| |-- Corporate
| | `-- monolithic.png
| `-- Distro
| `-- Anaconda
| `-- Header
| |-- fig1.png
| |-- fig2.png
| `-- summary.png
`-- Tpl
|-- Corporate
| `-- monolithic.svg
`-- Distro
`-- Anaconda
`-- Header
|-- fig1.svg
|-- fig2.svg
`-- summary.svg
</pre>
<a name="SEC11"></a>
<h4 class="subsubsection"> 3.1.4.3 Layout 3: Language specific image rendering </h4>
<p>This directory layout extends previous one in order to produce
language-specific images. This directory layout contains one
<tt>`Img/'</tt> directory (to store final images), one <tt>`Tpl/'</tt>
directory to store design templates, and the translation entry
contains translation files inside (organized by language codes).
</p>
<pre class="verbatim">trunk/Translations/Identity/path/to/dir
|-- en
| |-- Corporate
| | `-- monolithic.sed
| `-- Distro
| `-- Anaconda
| `-- Header
| |-- fig1.sed
| |-- fig2.sed
| `-- summary.sed
`-- es
|-- Corporate
| `-- monolithic.sed
`-- Distro
`-- Anaconda
`-- Header
|-- fig1.sed
|-- fig2.sed
`-- summary.sed
</pre>
<p>When images are rendered, the <tt>`Img/'</tt> directory structure is
created automatically using the translation entry structure as
reference (see above).
</p>
<pre class="verbatim">trunk/Identity/path/to/dir
|-- Img
| |-- en
| | |-- Corporate
| | | `-- monolithic.png
| | `-- Distro
| | `-- Anaconda
| | `-- Header
| | |-- fig1.png
| | |-- fig2.png
| | `-- summary.png
| `-- es
| |-- Corporate
| | `-- monolithic.png
| `-- Distro
| `-- Anaconda
| `-- Header
| |-- fig1.png
| |-- fig2.png
| `-- summary.png
`-- Tpl
|-- Corporate
| `-- monolithic.svg
`-- Distro
`-- Anaconda
`-- Header
|-- fig1.svg
|-- fig2.svg
`-- summary.svg
</pre>
<p>In this configuration, one language-specific file is applied to one
design tempalate to produce one translated PNG image. The relation
between language-specific translation file and design template is done
removing the language-specific directory from translation path, and
the one design template path that matches it is used.
</p>
<p>If no design template is found for one translation file, the final PNG
image for that translation file is not produced and the next
translation file in the list is evaluated.
</p>
<p>For example, in this configuration the following translation files:
</p>
<pre class="verbatim">trunk/Translations/Identity/path/to/dir/en/Corporate/monolithic.sed
trunk/Translations/Identity/path/to/dir/es/Corporate/monolithic.sed
</pre>
<p>match the same design template file:
</p>
<pre class="verbatim">trunk/Identity/path/to/dir/Tpl/Corporate/monolithic.svg
</pre>
<p>in order to produce the following PNG image files:
</p>
<pre class="verbatim">trunk/Identity/path/to/dir/Img/en/Corporate/monolithic.png
trunk/Identity/path/to/dir/Img/es/Corporate/monolithic.png
</pre>
<a name="SEC12"></a>
<h4 class="subsubsection"> 3.1.4.4 Layout 4: Release and language specific image rendering </h4>
<p>This directory layout extends previous one in order to produce
language-specific images for different major releases of CentOS
distribution (as CentOS release schema describes).
</p>
<p>This directory layout contains one <tt>`Img/'</tt> directory (to store
final images), one <tt>`Tpl/'</tt> directory to store design templates,
and the translation entry contains translation files inside (organized
by language codes and major release numbers).
</p>
<pre class="verbatim">trunk/Translations/Identity/path/to/dir
|-- 5
| |-- en
| | |-- Corporate
| | | `-- monolithic.sed
| | `-- Distro
| | `-- Anaconda
| | `-- Header
| | |-- fig1.sed
| | |-- fig2.sed
| | `-- summary.sed
| `-- es
| |-- Corporate
| | `-- monolithic.sed
| `-- Distro
| `-- Anaconda
| `-- Header
| |-- fig1.sed
| |-- fig2.sed
| `-- summary.sed
`-- 6
|-- en
| |-- Corporate
| | `-- monolithic.sed
| `-- Distro
| `-- Anaconda
| `-- Header
| |-- fig1.sed
| |-- fig2.sed
| `-- summary.sed
`-- es
|-- Corporate
| `-- monolithic.sed
`-- Distro
`-- Anaconda
`-- Header
|-- fig1.sed
|-- fig2.sed
`-- summary.sed
</pre>
<p>When images are rendered, the <tt>`Img/'</tt> directory structure is
created automatically using the translation entry structure as
reference (see above).
</p>
<pre class="verbatim">trunk/Identity/path/to/dir
|-- Img
| |-- 5
| | |-- en
| | | |-- Corporate
| | | | `-- monolithic.png
| | | `-- Distro
| | | `-- Anaconda
| | | `-- Header
| | | |-- fig1.png
| | | |-- fig2.png
| | | `-- summary.png
| | `-- es
| | |-- Corporate
| | | `-- monolithic.png
| | `-- Distro
| | `-- Anaconda
| | `-- Header
| | |-- fig1.png
| | |-- fig2.png
| | `-- summary.png
| `-- 6
| |-- en
| | |-- Corporate
| | | `-- monolithic.png
| | `-- Distro
| | `-- Anaconda
| | `-- Header
| | |-- fig1.png
| | |-- fig2.png
| | `-- summary.png
| `-- es
| |-- Corporate
| | `-- monolithic.png
| `-- Distro
| `-- Anaconda
| `-- Header
| |-- fig1.png
| |-- fig2.png
| `-- summary.png
`-- Tpl
|-- Corporate
| `-- monolithic.svg
`-- Distro
`-- Anaconda
`-- Header
|-- fig1.svg
|-- fig2.svg
`-- summary.svg
</pre>
<p>In this configuration, one language-specific file, is applied to one
design tempalate to produce one translated PNG image for each major
release specified in the translation entry. The relation among
release-specific and language-specific translation files, and design
template is done removing the release-specific and language-specific
directories from translation path, and looking for the one design
template path that matches.
</p>
<p>If no design template matches the translation file, the final PNG
image for that translation file is not produced and the next
translation file in the list is evaluated.
</p>
<p>For example, in this configuration, the following translation files:
</p>
<pre class="verbatim">trunk/Translations/Identity/path/to/dir/5/en/Corporate/monolithic.sed
trunk/Translations/Identity/path/to/dir/5/es/Corporate/monolithic.sed
trunk/Translations/Identity/path/to/dir/6/en/Corporate/monolithic.sed
trunk/Translations/Identity/path/to/dir/6/es/Corporate/monolithic.sed
</pre>
<p>match the same design template file:
</p>
<pre class="verbatim">trunk/Identity/path/to/dir/Tpl/Corporate/monolithic.svg
</pre>
<p>in order to produce the following PNG image files:
</p>
<pre class="verbatim">trunk/Identity/path/to/dir/Img/5/en/Corporate/monolithic.png
trunk/Identity/path/to/dir/Img/5/es/Corporate/monolithic.png
trunk/Identity/path/to/dir/Img/6/en/Corporate/monolithic.png
trunk/Identity/path/to/dir/Img/6/es/Corporate/monolithic.png
</pre>
<a name="SEC13"></a>
<h4 class="subsubsection"> 3.1.4.5 Layout 5: Brands specific image rendering </h4>
<p>See section <a href="repository_5.html#SEC20">trunk/Identity/Brands</a>, for more information about themes
specific image rendering and directory layout.
</p>
<a name="SEC14"></a>
<h4 class="subsubsection"> 3.1.4.6 Layout 6: Themes specific image rendering </h4>
<p>See section <a href="repository_17.html#SEC90">trunk/Identity/Themes</a>, for more information about themes
specific image rendering and directory layout.
</p>
<a name="SEC15"></a>
<h3 class="subsection"> 3.1.5 File name convenctions </h3>
<p>As file name convenction, inside CentOS Artwork Repository, both
text-based and image-based file name produced by <code>centos-art.sh</code>
script has the same name of their translation files without
the <samp>`.sed'</samp> extension. The file extension is set as follow:
</p>
<a name="SEC16"></a>
<h4 class="subsubsection"> 3.1.5.1 When text-based files are rendered </h4>
<p>Text-based files end up having the same extension of their design
template file.
</p>
<a name="SEC17"></a>
<h4 class="subsubsection"> 3.1.5.2 When image-based files are rendered </h4>
<p>Image-based files always end up having the <tt>`.png'</tt> extension.
</p>
<blockquote class="orange"><img src="/home/centos/artwork/trunk/Identity/Widgets/Img/icon-admonition-idea.png" alt="Info"><h3>Tip</h3><p> Once <tt>`.png'</tt> images are created, other image formats
may be created using the <code>renderFormats</code> post-rendering
action, inside the image-based related pre-rendering configuration
script.
</p>
<p>See section <a href="repository_37.html#SEC195">trunk/Scripts/Bash</a>, for more information.
</p></blockquote>
<a name="SEC18"></a>
<h3 class="subsection"> 3.1.6 See also </h3>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="repository_52.html#SEC281">3.49 trunk/Translations</a></td><td> </td><td align="left" valign="top">
</td></tr>
</table>
<a name="SEC19"></a>
<h3 class="subsection"> 3.1.7 References </h3>
<ul class="toc">
<li> <a href="http://en.wikipedia.org/Corporate_identity">http://en.wikipedia.org/Corporate_identity</a> (and related
links).
</li></ul>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#SEC18" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="repository_5.html#SEC20" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="repository_3.html#SEC3" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="#SEC4" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_63.html#SEC349" title="Next chapter"> >> </a>]</td>
</tr></table>
<p>
<font size="-1">
This document was generated on <i>October, 27 2010</i> using <a href="http://texi2html.cvshome.org/"><i>texi2html 1.76</i></a>.
</font>
<br>
</p>
</body>
</html>