From eb3c68db83afe4ec41e0935a686d3fef8d6f1b7a Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: May 21 2011 03:45:21 +0000 Subject: Update Repository/History/section-2.docbook. --- diff --git a/Manuals/Docbook/Repository/History/section-2.docbook b/Manuals/Docbook/Repository/History/section-2.docbook index 63515cf..815893b 100644 --- a/Manuals/Docbook/Repository/History/section-2.docbook +++ b/Manuals/Docbook/Repository/History/section-2.docbook @@ -4,38 +4,44 @@ 2009 The rendition script is at a very rustic state where only - slide images can be produced. + slide images can 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 produced 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 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 + render.sh. - The rendition script was named 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 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 unified in 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. + 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 Corporate Identity - by Wally Olins (1989) and Wikipedia. + The concepts about corporate identity began to be + considered. As referece, it was used the book Corporate + Identity by Wally Olins (1989) and Wikipedia (). 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 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 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.