diff --git a/Manuals/en/Html/Repository/repository.html b/Manuals/en/Html/Repository/repository.html index 7d683c9..c5eb7f4 100644 --- a/Manuals/en/Html/Repository/repository.html +++ b/Manuals/en/Html/Repository/repository.html @@ -58,7 +58,7 @@ ul.toc {list-style: none}
[Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
[Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
diff --git a/Manuals/en/Html/Repository/repository_1.html b/Manuals/en/Html/Repository/repository_1.html index 4ee2689..d94092b 100644 --- a/Manuals/en/Html/Repository/repository_1.html +++ b/Manuals/en/Html/Repository/repository_1.html @@ -66,7 +66,7 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_11.html b/Manuals/en/Html/Repository/repository_11.html index 079f849..fde14a4 100644 --- a/Manuals/en/Html/Repository/repository_11.html +++ b/Manuals/en/Html/Repository/repository_11.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_12.html b/Manuals/en/Html/Repository/repository_12.html index 5311691..df9899e 100644 --- a/Manuals/en/Html/Repository/repository_12.html +++ b/Manuals/en/Html/Repository/repository_12.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_13.html b/Manuals/en/Html/Repository/repository_13.html index a0baba3..7b1c335 100644 --- a/Manuals/en/Html/Repository/repository_13.html +++ b/Manuals/en/Html/Repository/repository_13.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_14.html b/Manuals/en/Html/Repository/repository_14.html index ca71cbe..911b4ec 100644 --- a/Manuals/en/Html/Repository/repository_14.html +++ b/Manuals/en/Html/Repository/repository_14.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_15.html b/Manuals/en/Html/Repository/repository_15.html index 63db219..2dd1a59 100644 --- a/Manuals/en/Html/Repository/repository_15.html +++ b/Manuals/en/Html/Repository/repository_15.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_16.html b/Manuals/en/Html/Repository/repository_16.html index 4224b1f..3433717 100644 --- a/Manuals/en/Html/Repository/repository_16.html +++ b/Manuals/en/Html/Repository/repository_16.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_17.html b/Manuals/en/Html/Repository/repository_17.html index 69881b7..ceef1ee 100644 --- a/Manuals/en/Html/Repository/repository_17.html +++ b/Manuals/en/Html/Repository/repository_17.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_18.html b/Manuals/en/Html/Repository/repository_18.html index 016dc75..8443ff3 100644 --- a/Manuals/en/Html/Repository/repository_18.html +++ b/Manuals/en/Html/Repository/repository_18.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_19.html b/Manuals/en/Html/Repository/repository_19.html index 0389a59..d312819 100644 --- a/Manuals/en/Html/Repository/repository_19.html +++ b/Manuals/en/Html/Repository/repository_19.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_2.html b/Manuals/en/Html/Repository/repository_2.html index 59fe2ee..890bf4c 100644 --- a/Manuals/en/Html/Repository/repository_2.html +++ b/Manuals/en/Html/Repository/repository_2.html @@ -66,7 +66,7 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_21.html b/Manuals/en/Html/Repository/repository_21.html index 897978d..3ffb3ce 100644 --- a/Manuals/en/Html/Repository/repository_21.html +++ b/Manuals/en/Html/Repository/repository_21.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_22.html b/Manuals/en/Html/Repository/repository_22.html index c7fab7b..12c9006 100644 --- a/Manuals/en/Html/Repository/repository_22.html +++ b/Manuals/en/Html/Repository/repository_22.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_23.html b/Manuals/en/Html/Repository/repository_23.html index d22f983..77533dd 100644 --- a/Manuals/en/Html/Repository/repository_23.html +++ b/Manuals/en/Html/Repository/repository_23.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_24.html b/Manuals/en/Html/Repository/repository_24.html index ee1b589..01359da 100644 --- a/Manuals/en/Html/Repository/repository_24.html +++ b/Manuals/en/Html/Repository/repository_24.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_25.html b/Manuals/en/Html/Repository/repository_25.html index 6f47794..d5cd0c9 100644 --- a/Manuals/en/Html/Repository/repository_25.html +++ b/Manuals/en/Html/Repository/repository_25.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_26.html b/Manuals/en/Html/Repository/repository_26.html index 1dae316..5b09b19 100644 --- a/Manuals/en/Html/Repository/repository_26.html +++ b/Manuals/en/Html/Repository/repository_26.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_27.html b/Manuals/en/Html/Repository/repository_27.html index dd86ac4..8b4696a 100644 --- a/Manuals/en/Html/Repository/repository_27.html +++ b/Manuals/en/Html/Repository/repository_27.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_28.html b/Manuals/en/Html/Repository/repository_28.html index aa5f46e..206dc06 100644 --- a/Manuals/en/Html/Repository/repository_28.html +++ b/Manuals/en/Html/Repository/repository_28.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_29.html b/Manuals/en/Html/Repository/repository_29.html index 5556216..c41eb24 100644 --- a/Manuals/en/Html/Repository/repository_29.html +++ b/Manuals/en/Html/Repository/repository_29.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_3.html b/Manuals/en/Html/Repository/repository_3.html index aba3124..e3e4780 100644 --- a/Manuals/en/Html/Repository/repository_3.html +++ b/Manuals/en/Html/Repository/repository_3.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_30.html b/Manuals/en/Html/Repository/repository_30.html index a306e01..90bd408 100644 --- a/Manuals/en/Html/Repository/repository_30.html +++ b/Manuals/en/Html/Repository/repository_30.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_31.html b/Manuals/en/Html/Repository/repository_31.html index 56351eb..7cdae7a 100644 --- a/Manuals/en/Html/Repository/repository_31.html +++ b/Manuals/en/Html/Repository/repository_31.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_32.html b/Manuals/en/Html/Repository/repository_32.html index 57a79d0..9fa920d 100644 --- a/Manuals/en/Html/Repository/repository_32.html +++ b/Manuals/en/Html/Repository/repository_32.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
To render Anaconda progress slide images using the Modern artistic motif design, the Default theme model, and available -translation files (see section trunk/Translations/Identity/Themes/Distro/Anaconda/Progress); use the following commands: +translation files (see section trunk/Translations/Identity/Themes/Distro/Anaconda/Progress); use the following commands:
cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ centos-art render --identity @@ -141,7 +141,7 @@ centos-art render --identity |
diff --git a/Manuals/en/Html/Repository/repository_33.html b/Manuals/en/Html/Repository/repository_33.html index 83ef857..2a729f7 100644 --- a/Manuals/en/Html/Repository/repository_33.html +++ b/Manuals/en/Html/Repository/repository_33.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_34.html b/Manuals/en/Html/Repository/repository_34.html index 186c6c1..d4010e9 100644 --- a/Manuals/en/Html/Repository/repository_34.html +++ b/Manuals/en/Html/Repository/repository_34.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_35.html b/Manuals/en/Html/Repository/repository_35.html index b292397..51955df 100644 --- a/Manuals/en/Html/Repository/repository_35.html +++ b/Manuals/en/Html/Repository/repository_35.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_36.html b/Manuals/en/Html/Repository/repository_36.html index 8564431..d2d1297 100644 --- a/Manuals/en/Html/Repository/repository_36.html +++ b/Manuals/en/Html/Repository/repository_36.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_37.html b/Manuals/en/Html/Repository/repository_37.html index 5a2ef01..81a820d 100644 --- a/Manuals/en/Html/Repository/repository_37.html +++ b/Manuals/en/Html/Repository/repository_37.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_38.html b/Manuals/en/Html/Repository/repository_38.html index d260f80..76736ab 100644 --- a/Manuals/en/Html/Repository/repository_38.html +++ b/Manuals/en/Html/Repository/repository_38.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_39.html b/Manuals/en/Html/Repository/repository_39.html index 3162c6c..e3aff78 100644 --- a/Manuals/en/Html/Repository/repository_39.html +++ b/Manuals/en/Html/Repository/repository_39.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
centos-art
command runs the
@@ -231,7 +231,7 @@ each specific function documentation (see section 3.37 trunk/Scripts/Bash/Functionsdiff --git a/Manuals/en/Html/Repository/repository_4.html b/Manuals/en/Html/Repository/repository_4.html index 0c03754..0c0dfab 100644 --- a/Manuals/en/Html/Repository/repository_4.html +++ b/Manuals/en/Html/Repository/repository_4.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
3.50 trunk/Translations | + | |
3.50 trunk/Translations |
diff --git a/Manuals/en/Html/Repository/repository_40.html b/Manuals/en/Html/Repository/repository_40.html index d0ae505..9b8a2e4 100644 --- a/Manuals/en/Html/Repository/repository_40.html +++ b/Manuals/en/Html/Repository/repository_40.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
3.36 trunk/Scripts/Bash | ||
3.47 trunk/Scripts/Bash/Locale | + | |
3.47 trunk/Scripts/Bash/Locale |
diff --git a/Manuals/en/Html/Repository/repository_41.html b/Manuals/en/Html/Repository/repository_41.html index 831fea6..2ccdd8f 100644 --- a/Manuals/en/Html/Repository/repository_41.html +++ b/Manuals/en/Html/Repository/repository_41.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_42.html b/Manuals/en/Html/Repository/repository_42.html index cd22344..1b66217 100644 --- a/Manuals/en/Html/Repository/repository_42.html +++ b/Manuals/en/Html/Repository/repository_42.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_43.html b/Manuals/en/Html/Repository/repository_43.html index 41c42c9..31a77a4 100644 --- a/Manuals/en/Html/Repository/repository_43.html +++ b/Manuals/en/Html/Repository/repository_43.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_44.html b/Manuals/en/Html/Repository/repository_44.html index 716e32f..dc35450 100644 --- a/Manuals/en/Html/Repository/repository_44.html +++ b/Manuals/en/Html/Repository/repository_44.html @@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_45.html b/Manuals/en/Html/Repository/repository_45.html index 2a18704..69e27d9 100644 --- a/Manuals/en/Html/Repository/repository_45.html +++ b/Manuals/en/Html/Repository/repository_45.html @@ -59,43 +59,34 @@ ul.toc {list-style: none}
The render
functionality exists to automate production of files
-inside the working copy. The render
functionality is aimed to
-satisfy different file types (e.g., text-based and image-based)
-production needs in different information levels (e.g., different
-languages, release numbers, different architectures, etc.).
+inside the working copy. Specifically, the render
functionality
+is aimed to produce text-based and image-based files in different
+information levels (i.e., different languages, release numbers,
+architectures, etc.).
The render
functionality relies on "renderable directory
structures" to produce files. Renderable directory structures can be
either "identity directory structures" or "translation directory
structures" with special directories inside.
Identity directory structures are the starting point of identity rendition. Whenever we want to render a component of CentOS corporate @@ -103,7 +94,7 @@ visual identity we need to point `centos-art.sh' to an identity directory structure. If such identity directory structure doesn't exist, then it is good time to create it. Each identity directory structure represents one visual manifestation of CentOS corporate -visual identity. See section trunk/Identity, for more information. +visual identity.
The first requirement for an identity directory structure to be considered a renderable identity directory structure is its location @@ -113,20 +104,19 @@ inside the working copy: it should be under `trunk/Identity/' or
The second requirement for an identity directory structure to be considered a renderable identity directory structure is its directory structure: it needs to have one `Tpl/' directory to store design -templates files, one `Img/' directory to store files produced as +template files, one `Img/' directory to store files produced as rendition result, one translation directory structure to store translation files and one script directory to store pre-rendition configuration scripts. All these directory structures are connected among themselves by a common component in their path that bonds them -altogether. See section trunk/Scripts/Bash/Functions/Path, for more -information. +altogether.
Inside renderable identity directory structures, `centos-art.sh' can render both image-based and text-based files. Specification of whether a renderable identity directory structure produces image-based or text-based content is a configuration action that takes place in the pre-rendition configuration script of that renderable identity -directory structure. See section trunk/Scripts/Bash/Functions/Render/Config, for more information. +directory structure.
Inside renderable identity directory structures, content production is organized in different configurations. A content production @@ -137,25 +127,15 @@ images), but it can be extended (e.g., adding translation files) to achieve different needs (e.g., to produce translated images).
- -The design template without translation configuration is based on a renderable identity directory structure with an empty translation directory structure. In this configuration, one design template produces one untranslated file. Both design templates and final untranslated files share the same file name, but they differ one -another in the file-type itself and the file-extension used to -describe the file type. -
-Design templates are based on SVG (Scalable Vector Graphics)
-and use the extension .svg
. Files produced as rendition result
-(i.e., the final files translated or not) may be text-based files with
-arbitrary extensions, or PNG (Portable Network Graphics) files
-with the extension .png
. Definition of whether a final file is
-text-based or image-based is set in the pre-rendition configuration
-script of the renderable directory structure we want to produce files
-for.
+another in file-type and file-extension.
For example, to produce images without translations (there is no much use in producing text-based files without translations), consider the @@ -164,26 +144,35 @@ following configuration:
Specify the identity component we want to produce images for. -
-trunk/Identity/DirName -|-- Tpl -| `-- file.svg -`-- Img - `-- file.png +In this example we used `Identity/Path/To/Dir' as the identity +component we want to produce untranslated images for. Identity +components can be either under `trunk/' or `branches/' +directory structure. +
+The identity component (i.e., `Identity/Path/To/Dir', in this +case) is also the bond component we use to connect the identity +directory structures with their respective auxiliar directories (i.e., +translation directory structres and pre-rendition configuration +structures). The bond component is the path convenction that +`centos-art.sh' uses to know where to look for related +translations, configuration scripts and whatever auxiliar thing a +renderable directory structure may need to have. +
+| The bond component + |----------------->| +trunk/Identity/Path/To/Dir <-- Renderable identity directory structure. +|-- Tpl <-- Design template directory. +| `-- file.svg <-- Design template file. +`-- Img <-- Directory used to store final files. + `-- file.png <-- Final image-based file produced from + design template file.-Inside design template directory, design template files can be -organized using several directory levels. Using several levels of -directories inside design template directory let us to create very -simple but extensible configurations, specially if translated images -are not required. -
-- +Note
When we use a "design template without translation" -configuration, `centos-art.sh' creates the `Img/' directory -structure automatically taking the `Tpl/' directory structure as -reference at rendition time. -
Inside design template directory, design template files are based on +SVG (Scalable Vector Graphics) and use the extension +
.svg
. Design template files can be organized using several +directory levels to create a simple but extensible configuration, +specially if translated images are not required. +In order for SVG (Scalable Vector Graphics) files to be considered "design template" files, they should be placed under the design template directory and to have set a
CENTOSARTWORK
@@ -191,10 +180,22 @@ object id inside.The
+CENTOSARTWORK
word itself is a convenction name we use to define which object/design area, inside a design template, the -`centos-art.sh' script will use to export as PNG image at -rendition time. Whithout such object id specification, the -`centos-art.sh' script cannot know what object/design area you -(as designer) want to export as PNG image file. +`centos-art.sh' script will use to export as +PNG (Portable Network Graphic) image at rendition time. +Whithout such object id specification, the `centos-art.sh' script +cannot know what object/design area you (as designer) want to export +as PNG (Portable Network Graphic) image file. ++ +Note
At rendition time, the content of `Img/' directory +structure is produced by `centos-art.sh' automatically. +
When a renderable identity directory structure is configured to +produce image-based content, `centos-art.sh' produces +PNG (Portable Network Graphics) files with the
.png
+extension. Once the base image format has been produced, it is +possible for `centos-art.sh' to use it in order to automatically +create other image formats that may be needed (see section trunk/Scripts/Bash/Functions/Render/Config).Inside the working copy, you can find an example of "design template without translation" configuration at `trunk/Identity/Models/'. @@ -206,46 +207,55 @@ without translation" configuration at `trunk/Identity/Models/'.
In order for an identity entry to be considered an identity renderable directory structure, it should have a translation entry. The content -of the translation entry is relevant to determine how the identity -renderable directory entry is processed. +of the translation entry is relevant to determine how to process the +identity renderable directory entry.
If the translation entry is empty (i.e., there is no file inside it), `centos-art.sh' interprets the identity renderable directory structure as a "design templates without translation" configuration.
-trunk/Translations/Identity/DirName +| The bond component + |----------------->| +trunk/Translations/Identity/Path/To/Dir `-- (empty)If the translation entry is not empty, `centos-art.sh' can -interpret the identity renderable directory structure as any of the -following configuration: "design templates with translations -(one-to-one)" or "design templates with translations (optimized)". -Which one of these configuration is used depends on the value assigned -to the matching list (MATCHINGLIST) variable. +interpret the identity renderable directory structure as one of the +following configurations: "design template with translation +(one-to-one)" or "design template with translation (optimized)". +Which one of these configurations is used depends on the value +assigned to the matching list (MATCHINGLIST) variable in the +pre-rendition configuration script of the renderable identity +directory structure we are producing images for.
If the matching list variable is empty (as it is by default), then -"design templates with translations (one-to-one)" configuration is +"design template with translation (one-to-one)" configuration is used. In this configuration it is required that both design templates -and translation files have the same file names. +and translation files have the same file names. This way, one +translation files is applied to one design template, to produce +one translated image.
If the matching list variable is not empty (because you redefine it in -the pre-rendition configuration script), then "design templates with -translations (optimized)" configuration is used instead. In this +the pre-rendition configuration script), then "design template with +translation (optimized)" configuration is used instead. In this configuration, design templates and translation files don't need to -have the same names since such relation between them is specified in -the matching list properly. +have the same names since such name relationship between them is +specified in the matching list properly.
-See section trunk/Translations, for more information. +
See section trunk/Translations, for more information.
In order to make an identity entry renderable, a pre-rendition -configuration script should exist for it. The pre-rendition -configuration script specifies what type of rendition does -`centos-art.sh' will perform and the way it does it. -
-trunk/Scripts/Bash/Functions/Render/Config/Identity/DirName ++In order to make an identity directory structure renderable, a +pre-rendition configuration script should exist for it. The +pre-rendition configuration script specifies what type of rendition +does `centos-art.sh' will perform over the identity directory +structure and how does it do that. +
+| The bond component + |----------------->| +trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir `-- render.conf.shIn this configuration the pre-rendition configuration script @@ -258,18 +268,24 @@ configuration script specifies what type of rendition does }
Since translation directory structure is empty, `centos-art.sh' +assumes a "design template without translation" configuration to +produce untranslated images. +
To produce untranslated images, `centos-art.sh' takes one design
-template and creates one temporal instance from it. Later,
+template and creates one temporal instance from it. Later,
`centos-art.sh' uses the temporal design template instance as
-source file to export the final untranslated image. The export action
-is possible thanks to Inkscape's command-line interface and the
-CENTOSARTWORK
object id we set inside design templates.
+source file to export the final untranslated image. The action of
+exporting images from SVG (Scalable Vector Graphics) to
+PNG (Portable Network Graphics) is possible thanks to
+Inkscape's command-line interface and the CENTOSARTWORK
object
+id we previously set inside design templates.
centos-art.sh render --identity=trunk/Identity/DirName +centos-art.sh render --identity=trunk/Identity/Path/To/Dir ------------------------------------------------- 0 | Execute centos-art.sh on renderable identity directory structure. --v---------------------------------------------- -trunk/Identity/DirName/Tpl/file.svg +trunk/Identity/Path/To/Dir/Tpl/file.svg ------------------------------------------------- 1 | Create instance from design template. --v---------------------------------------------- @@ -282,18 +298,19 @@ trunk/Identity/NewDir/Img/file.png 3 | Remove design template instance.Finally, when the untranslated image has been created, the temporal -design template instance is removed. At this point, the next design -template in the list is taken to repeat the production flow once again -and so on, until all design templates be processed. +design template instance is removed. At this point, +`centos-art.sh' takes the next design template and repeats the +whole production flow once again (design template by design template), +until all design templates be processed.
-See section trunk/Scripts/Bash/Functions/Render/Config, for more +
See section trunk/Scripts/Bash/Functions/Render/Config, for more information.
Producing untranslated images is fine in many cases, but not always. Sometimes it is required to produce images in different languages and @@ -312,11 +329,13 @@ missing component.
In order for `centos-art.sh' to know which is the relation between translation files and design templates the translation directory structure is taken as reference. For example, the -`trunk/Translations/Identity/DirName/file.sed' translation file -does match `trunk/Identity/DirName/Tpl/file.svg' design template, -but it doesn't match `trunk/Identity/DirName/File.svg' or -`trunk/Identity/DirName/Tpl/File.svg' or -`trunk/Identity/DirName/Tpl/SubDir/file.svg' design templates. +`trunk/Translations/Identity/Path/To/Dir/file.sed' translation +file does match `trunk/Identity/Path/To/Dir/Tpl/file.svg' design +template, but it doesn't match +`trunk/Identity/Path/To/Dir/File.svg' or +`trunk/Identity/Path/To/Dir/Tpl/File.svg' or +`trunk/Identity/Path/To/Dir/Tpl/SubDir/file.svg' design +templates.
The pre-rendition configuration script used to produce untranslated images is the same we use to produce translated images. There is no @@ -339,15 +358,15 @@ image has been produced, `centos-art.sh' removes the translated design template instance. This production flow is repeated for each translation file available in the translatio entry.
-centos-art.sh render --identity=trunk/Identity/DirName +centos-art.sh render --identity=trunk/Identity/Path/To/Dir ------------------------------------------------- 0 | Execute centos-art.sh on directory structure. --v---------------------------------------------- -trunk/Translations/Identity/DirName/file.sed +trunk/Translations/Identity/Path/To/Dir/file.sed ------------------------------------------------- 1 | Apply translation to design template. --v---------------------------------------------- -trunk/Identity/DirName/Tpl/file.svg +trunk/Identity/Path/To/Dir/Tpl/file.svg ------------------------------------------------- 2 | Create design template instance. --v---------------------------------------------- @@ -360,8 +379,8 @@ trunk/Identity/NewDir/Img/file.png 4 | Remove design template instance.- -3.42.3.3 Design template with translation (optimized)
+ +3.42.1.3 Design template with translation (optimized)
Producing translated images satisfies almost all our production images needs, but there is still a pitfall in them. In order to produce @@ -401,7 +420,7 @@ paragraph-based style, controlled by `paragraph.svg' design template; and one image using a list-based style, controlled by `list.svg' design template.
-trunk/Identity/DirName +trunk/Identity/Path/To/Dir |-- Tpl | |-- paragraph.svg | `-- list.svg @@ -421,7 +440,7 @@ names do not match design template names. When we use matching list there is no need for translation files to match the names of design templates, such name relation is set inside the matching list itself. -trunk/Translations/Identity/DirName +trunk/Translations/Identity/Path/To/Dir |-- 01-welcome.sed |-- 02-donate.sed |-- 03-docs.sed @@ -438,7 +457,7 @@ relation between translation files and design templates is set using the matching list MATCHINGLIST variable inside the pre-rendition configuration script of the component we want to produce images for. -trunk/Scripts/Bash/Functions/Render/Config/Identity/DirName +trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir `-- render.conf.shIn this configuration the pre-rendition configuration script @@ -469,8 +488,8 @@ list-based design template. - -
3.42.3.4 Design template with translation (optimized+flexibility)
+ +3.42.1.4 Design template with translation (optimized+flexibility)
In the production models we've seen so far, there are design templates to produce untranslated images and translation files which combiend @@ -523,7 +542,7 @@ present to identify the exportation area, translation marks, etc. However, design models do use dynamic backgrounds inclusion while design templates don't.
-THEMEMODEL | | Design model component +THEMEMODEL | | The bond component |<----| |--------------------->| trunk/Identity/Themes/Models/Default/Distro/Anaconda/Progress/ |-- paragraph.svg @@ -570,7 +589,7 @@ create the translation entry we don't use the name of neither design model nor artistic motif, just the design model component we want to produce images for. -| Design model component +| The bond component |--------------------->| trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ `-- 5 @@ -620,8 +639,8 @@ pre-rendition configuration script is evaluated to teachThe production flow of "optimize+flexibility" configuration…
- -3.42.4 Renderable translation directory structures
+ +3.42.2 Renderable translation directory structures
Translation directory structures are auxiliar structures of renderable identity directory structures. There is one translation directory @@ -652,8 +671,8 @@ from translation templates. `centos-art.sh' can produce text-based files only.
- -3.42.5 Copying renderable directory structures
+ +3.42.3 Copying renderable directory structures
A renderable layout is formed by design models, design images, pre-rendition configuration scripts and translations files. This way, @@ -695,23 +714,23 @@ automatically to the new location specified by FLAG_TO variable.
Design templates + No translation:
Command: -- centos-art render -copy=trunk/Identity/DirName -to=trunk/Identity/NewDirName +- centos-art render -copy=trunk/Identity/Path/To/Dir -to=trunk/Identity/NewPath/To/Dir
Sources: -- trunk/Identity/DirName -- trunk/Translations/Identity/DirName -- trunk/Scripts/Bash/Functions/Render/Config/Identity/DirName +- trunk/Identity/Path/To/Dir +- trunk/Translations/Identity/Path/To/Dir +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir
Targets: -- trunk/Identity/NewDirName -- trunk/Translations/Identity/NewDirName -- trunk/Scripts/Bash/Functions/Render/Config/Identity/NewDirName +- trunk/Identity/NewPath/To/Dir +- trunk/Translations/Identity/NewPath/To/Dir +- trunk/Scripts/Bash/Functions/Render/Config/Identity/NewPath/To/Dir
Renderable layout 2:
Command: - centos-art render -copy=trunk/Identity/Themes/Motifs/TreeFlower \ - -to=trunk/Identity/Themes/Motifs/NewDirName + -to=trunk/Identity/Themes/Motifs/NewPath/To/Dir
Sources: - trunk/Identity/Themes/Motifs/TreeFlower @@ -721,11 +740,11 @@ automatically to the new location specified by FLAG_TO variable. - trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/TreeFlower
Targets: -- trunk/Identity/Themes/Motifs/NewDirName +- trunk/Identity/Themes/Motifs/NewPath/To/Dir - trunk/Translations/Identity/Themes -- trunk/Translations/Identity/Themes/Motifs/NewDirName +- trunk/Translations/Identity/Themes/Motifs/NewPath/To/Dir - trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes -- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewDirName +- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewPath/To/Dir
Notice that design models are not included in source or target locations. This is intentional. In "Renderable layout 2", design @@ -784,30 +803,30 @@ directly involved in rendition process only. Once such directories have been duplicated, the functionality stops thereat.
- -3.42.6 Usage
+ +3.42.4 Usage
3.43 trunk/Scripts/Bash/Functions/Render/Config | + | |
3.43 trunk/Scripts/Bash/Functions/Render/Config |
[ < ] | -[ > ] | +|||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
diff --git a/Manuals/en/Html/Repository/repository_46.html b/Manuals/en/Html/Repository/repository_46.html
index b8ccb89..526d8e5 100644
--- a/Manuals/en/Html/Repository/repository_46.html
+++ b/Manuals/en/Html/Repository/repository_46.html
@@ -54,34 +54,34 @@ ul.toc {list-style: none}
The `trunk/Scripts/Bash/Config' directory exists to oraganize
pre-rendering configuration scripts.
Pre-rendering configuration scripts let you customize the way
@@ -97,7 +97,7 @@ configuration entries are required for each identity entry, but not
for translation entries.
Inside CentOS Artwork Repository, we consider identity entries to all
@@ -139,7 +139,7 @@ scripts using image-based and text-based post-rendering actions,
respectively.
Translation pre-rendering configuration scripts take precedence before
@@ -148,7 +148,7 @@ actions are useful when default translation rendering action do not
fit itself to translation entry rendering requirements.
Inside both image-based and text-based identity pre-rendering
@@ -223,7 +223,7 @@ ACTIONS[1]='POST:renderFormats: xpm jpg tif'
ACTIONS[2]='LAST:groupByformat: png xpm jpg tif'
-
+
Use the following commands to administer both identity and translation
@@ -261,7 +261,7 @@ directory path under `trunk/Identity' or
`trunk/Translations' structures only.
diff --git a/Manuals/en/Html/Repository/repository_47.html b/Manuals/en/Html/Repository/repository_47.html
index a7c817d..c346524 100644
--- a/Manuals/en/Html/Repository/repository_47.html
+++ b/Manuals/en/Html/Repository/repository_47.html
@@ -54,34 +54,34 @@ ul.toc {list-style: none}
This section exists to organize files related to The
diff --git a/Manuals/en/Html/Repository/repository_48.html b/Manuals/en/Html/Repository/repository_48.html
index b1566ee..b29661f 100644
--- a/Manuals/en/Html/Repository/repository_48.html
+++ b/Manuals/en/Html/Repository/repository_48.html
@@ -54,34 +54,34 @@ ul.toc {list-style: none}
This section exists to organize files related to The The metadata used is defined by Inkscape 0.46 using the SVG standard
@@ -219,7 +219,7 @@ Artwork Repository.
Many of the no-longer-used gradients, patterns, and markers (more
@@ -241,7 +241,7 @@ files, the `centos-art.sh' script uses Inkscape command-line
interface, specifically with the `--vaccum-defs' option.
diff --git a/Manuals/en/Html/Repository/repository_49.html b/Manuals/en/Html/Repository/repository_49.html
index cc658b0..cd8d0eb 100644
--- a/Manuals/en/Html/Repository/repository_49.html
+++ b/Manuals/en/Html/Repository/repository_49.html
@@ -54,27 +54,27 @@ ul.toc {list-style: none}
This section exists to organize files related to `centos-art.sh'
@@ -84,7 +84,7 @@ workstation configuration you are planning to use as host for your
working copy of CentOS Artwork Repository.
The first time you download CentOS Artwork Repository you need to
@@ -104,7 +104,7 @@ because `centos-art' symbolic link, under `~/bin/'
directory, has not been created yet.
Installation of auxiliar RPM packages provides the software required
@@ -139,7 +139,7 @@ will be able to configure your users to have Creation of symbolic links helps us to alternate between different
@@ -174,7 +174,7 @@ structure. As consequence of this configuration, automation scripts
cannot be branched under `branches/Scripts' directory structure.
Definition of environemnt variables helps us to set default values to
@@ -273,7 +273,7 @@ location using time zone correction.
-
+
diff --git a/Manuals/en/Html/Repository/repository_5.html b/Manuals/en/Html/Repository/repository_5.html
index f5e6b1e..10cffed 100644
--- a/Manuals/en/Html/Repository/repository_5.html
+++ b/Manuals/en/Html/Repository/repository_5.html
@@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_50.html b/Manuals/en/Html/Repository/repository_50.html
index 925d9ce..0a72ad8 100644
--- a/Manuals/en/Html/Repository/repository_50.html
+++ b/Manuals/en/Html/Repository/repository_50.html
@@ -54,34 +54,34 @@ ul.toc {list-style: none}
This section exists to organize translation messages and templates
used by `centos-art.sh' script.
Translated messages of `centos-art.sh' script are managed using
@@ -90,7 +90,7 @@ automated through `centos-art.sh' script "locale" functionali
(see section trunk/Scripts/Bash/Functions/Locale).
The content of `trunk/Scripts/Bash/Locale' directory should not
@@ -99,7 +99,7 @@ be managed manually. Instead, use the "locale" functionality of
"locale" functionality.
diff --git a/Manuals/en/Html/Repository/repository_51.html b/Manuals/en/Html/Repository/repository_51.html
index 96b8008..9dfc198 100644
--- a/Manuals/en/Html/Repository/repository_51.html
+++ b/Manuals/en/Html/Repository/repository_51.html
@@ -54,27 +54,27 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_52.html b/Manuals/en/Html/Repository/repository_52.html
index d0768a5..abbb52a 100644
--- a/Manuals/en/Html/Repository/repository_52.html
+++ b/Manuals/en/Html/Repository/repository_52.html
@@ -54,27 +54,27 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_53.html b/Manuals/en/Html/Repository/repository_53.html
index 67e7b16..c7b541d 100644
--- a/Manuals/en/Html/Repository/repository_53.html
+++ b/Manuals/en/Html/Repository/repository_53.html
@@ -54,27 +54,27 @@ ul.toc {list-style: none}
The `trunk/Translations' directory exists to:
@@ -85,7 +85,7 @@ ul.toc {list-style: none}
-
+
When you create artwork for CentOS distribution you find that some
@@ -125,7 +125,7 @@ entries" to organize artworks' "translation files" and artworks'
"translation templates".
Translation entries exists for each artwork you want to produce.
@@ -206,7 +206,7 @@ artworks look and feel (the identity entries), and translators in
artworks translations (the translation entries).
@@ -254,7 +254,7 @@ markers well defined makes possible that translators and graphic
designers can work together but independently one another.
Translation files are text files with Template translation files are translation files stored inside
@@ -491,7 +491,7 @@ the REPLACEMENT of `=TITLE=' translation marker replacement
command.
Common translation files contain common translations or no
@@ -516,7 +516,7 @@ the following:
`-- firstboot-left.sed <-- common translation file.
-
+
Specific translation files contain specific translations for their
@@ -540,7 +540,7 @@ script.
`-- firstboot-left.sed
-
+
When rendering translations, the When the In the other hand, if the translation pre-rendering configuration file
@@ -671,7 +671,7 @@ translation marker section
-
+
diff --git a/Manuals/en/Html/Repository/repository_54.html b/Manuals/en/Html/Repository/repository_54.html
index 8a35cda..9cde95e 100644
--- a/Manuals/en/Html/Repository/repository_54.html
+++ b/Manuals/en/Html/Repository/repository_54.html
@@ -54,27 +54,27 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_55.html b/Manuals/en/Html/Repository/repository_55.html
index 33a0bf8..85b65e6 100644
--- a/Manuals/en/Html/Repository/repository_55.html
+++ b/Manuals/en/Html/Repository/repository_55.html
@@ -54,27 +54,27 @@ ul.toc {list-style: none}
Translation files, inside `trunk/Translations/Identity/Brands'
@@ -116,7 +116,7 @@ translation files.
(`Tpl') directory have special meaning:
Convenctional file names look like `blue.sed', `2c-a.sed',
@@ -126,7 +126,7 @@ name. The image dimensions use the same dimensions that design
template has.
Numeric file names look like `300.sed', `200.sed', etc.
@@ -150,7 +150,7 @@ shorter PNG images using numeric translation files as described
above.
Inside `trunk/Translations/Identity/Brands/', translation files
@@ -170,7 +170,7 @@ inside template translation files.
-
+
To render brands' translation files, use the following command:
@@ -178,11 +178,11 @@ inside template translation files.
diff --git a/Manuals/en/Html/Repository/repository_56.html b/Manuals/en/Html/Repository/repository_56.html
index 89ab83f..cc3652b 100644
--- a/Manuals/en/Html/Repository/repository_56.html
+++ b/Manuals/en/Html/Repository/repository_56.html
@@ -54,50 +54,50 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_57.html b/Manuals/en/Html/Repository/repository_57.html
index 63054e3..e71a0af 100644
--- a/Manuals/en/Html/Repository/repository_57.html
+++ b/Manuals/en/Html/Repository/repository_57.html
@@ -54,32 +54,32 @@ ul.toc {list-style: none}
This section exists to organize fonts translation files.
Translation files, inside `trunk/Translations/Fonts', have the
@@ -102,7 +102,7 @@ to use inside CentOS visual identity.
Inside `trunk/Translations/Identity/Fonts', translation files
@@ -121,7 +121,7 @@ combine the following translation markers:
-
+
Inside `trunk/Translations/Fonts' you use your favorite text
@@ -135,7 +135,7 @@ directory (`Tpl/'), nor translation rendering using
diff --git a/Manuals/en/Html/Repository/repository_58.html b/Manuals/en/Html/Repository/repository_58.html
index 1431223..9fa1acd 100644
--- a/Manuals/en/Html/Repository/repository_58.html
+++ b/Manuals/en/Html/Repository/repository_58.html
@@ -54,50 +54,50 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_59.html b/Manuals/en/Html/Repository/repository_59.html
index b781178..73ceaba 100644
--- a/Manuals/en/Html/Repository/repository_59.html
+++ b/Manuals/en/Html/Repository/repository_59.html
@@ -54,50 +54,50 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_6.html b/Manuals/en/Html/Repository/repository_6.html
index da937b9..be2e5a8 100644
--- a/Manuals/en/Html/Repository/repository_6.html
+++ b/Manuals/en/Html/Repository/repository_6.html
@@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_60.html b/Manuals/en/Html/Repository/repository_60.html
index 44daf23..05632a0 100644
--- a/Manuals/en/Html/Repository/repository_60.html
+++ b/Manuals/en/Html/Repository/repository_60.html
@@ -54,50 +54,50 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_61.html b/Manuals/en/Html/Repository/repository_61.html
index 89dbaef..91d6c72 100644
--- a/Manuals/en/Html/Repository/repository_61.html
+++ b/Manuals/en/Html/Repository/repository_61.html
@@ -54,27 +54,27 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_62.html b/Manuals/en/Html/Repository/repository_62.html
index f8a6ae2..430cb36 100644
--- a/Manuals/en/Html/Repository/repository_62.html
+++ b/Manuals/en/Html/Repository/repository_62.html
@@ -54,27 +54,27 @@ ul.toc {list-style: none}
Use the following command to produce translation files based:
@@ -159,25 +159,25 @@ a sum of 18 images around.
-
+
Translation rendering is described in `trunk/Translations'
-documentation entry (see section trunk/Translations).
+documentation entry (see section trunk/Translations).
diff --git a/Manuals/en/Html/Repository/repository_63.html b/Manuals/en/Html/Repository/repository_63.html
index fe51275..8b4a7b6 100644
--- a/Manuals/en/Html/Repository/repository_63.html
+++ b/Manuals/en/Html/Repository/repository_63.html
@@ -54,27 +54,27 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_64.html b/Manuals/en/Html/Repository/repository_64.html
index 7eb2b37..582e8cb 100644
--- a/Manuals/en/Html/Repository/repository_64.html
+++ b/Manuals/en/Html/Repository/repository_64.html
@@ -54,72 +54,72 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_8.html b/Manuals/en/Html/Repository/repository_8.html
index 0037355..e680b24 100644
--- a/Manuals/en/Html/Repository/repository_8.html
+++ b/Manuals/en/Html/Repository/repository_8.html
@@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_9.html b/Manuals/en/Html/Repository/repository_9.html
index 24144c3..6740a09 100644
--- a/Manuals/en/Html/Repository/repository_9.html
+++ b/Manuals/en/Html/Repository/repository_9.html
@@ -59,14 +59,14 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_abt.html b/Manuals/en/Html/Repository/repository_abt.html
index 914a80c..cb983fd 100644
--- a/Manuals/en/Html/Repository/repository_abt.html
+++ b/Manuals/en/Html/Repository/repository_abt.html
@@ -57,7 +57,7 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_fot.html b/Manuals/en/Html/Repository/repository_fot.html
index e590b58..83821cb 100644
--- a/Manuals/en/Html/Repository/repository_fot.html
+++ b/Manuals/en/Html/Repository/repository_fot.html
@@ -57,7 +57,7 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_toc.html b/Manuals/en/Html/Repository/repository_toc.html
index 9c509fd..613e176 100644
--- a/Manuals/en/Html/Repository/repository_toc.html
+++ b/Manuals/en/Html/Repository/repository_toc.html
@@ -57,7 +57,7 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Info/Repository/repository.info.bz2 b/Manuals/en/Info/Repository/repository.info.bz2
index 98af9a7..30cefa8 100644
Binary files a/Manuals/en/Info/Repository/repository.info.bz2 and b/Manuals/en/Info/Repository/repository.info.bz2 differ
diff --git a/Manuals/en/Pdf/Repository/repository.pdf b/Manuals/en/Pdf/Repository/repository.pdf
index 7a379b7..ec3e151 100644
Binary files a/Manuals/en/Pdf/Repository/repository.pdf and b/Manuals/en/Pdf/Repository/repository.pdf differ
diff --git a/Manuals/en/Plaintext/Repository/repository.txt b/Manuals/en/Plaintext/Repository/repository.txt
index fa60094..19e5e3e 100644
--- a/Manuals/en/Plaintext/Repository/repository.txt
+++ b/Manuals/en/Plaintext/Repository/repository.txt
@@ -243,17 +243,15 @@ CentOS Artwork Repository
3.41.3 Usage
3.41.4 See also
3.42 trunk/Scripts/Bash/Functions/Render
- 3.42.1 Goals
- 3.42.2 Description
- 3.42.3 Renderable identity directory structures
- 3.42.3.1 Design template without translation
- 3.42.3.2 Design template with translation (one-to-one)
- 3.42.3.3 Design template with translation (optimized)
- 3.42.3.4 Design template with translation (optimized+flexibility)
- 3.42.4 Renderable translation directory structures
- 3.42.5 Copying renderable directory structures
- 3.42.6 Usage
- 3.42.7 See also
+ 3.42.1 Renderable identity directory structures
+ 3.42.1.1 Design template without translation
+ 3.42.1.2 Design template with translation (one-to-one)
+ 3.42.1.3 Design template with translation (optimized)
+ 3.42.1.4 Design template with translation (optimized+flexibility)
+ 3.42.2 Renderable translation directory structures
+ 3.42.3 Copying renderable directory structures
+ 3.42.4 Usage
+ 3.42.5 See also
3.43 trunk/Scripts/Bash/Functions/Render/Config
3.43.1 Goals
3.43.2 Description
@@ -4084,24 +4082,18 @@ concepts for.
3.42 trunk/Scripts/Bash/Functions/Render
========================================
-3.42.1 Goals
-------------
-
The `render' functionality exists to automate production of files
-inside the working copy. The `render' functionality is aimed to satisfy
-different file types (e.g., text-based and image-based) production
-needs in different information levels (e.g., different languages,
-release numbers, different architectures, etc.).
-
-3.42.2 Description
-------------------
+inside the working copy. Specifically, the `render' functionality is
+aimed to produce text-based and image-based files in different
+information levels (i.e., different languages, release numbers,
+architectures, etc.).
-The `render' functionality relies on "renderable directory structures"
-to produce files. Renderable directory structures can be either
-"identity directory structures" or "translation directory structures"
-with special directories inside.
+ The `render' functionality relies on "renderable directory
+structures" to produce files. Renderable directory structures can be
+either "identity directory structures" or "translation directory
+structures" with special directories inside.
-3.42.3 Renderable identity directory structures
+3.42.1 Renderable identity directory structures
-----------------------------------------------
Identity directory structures are the starting point of identity
@@ -4110,7 +4102,7 @@ visual identity we need to point `centos-art.sh' to an identity
directory structure. If such identity directory structure doesn't
exist, then it is good time to create it. Each identity directory
structure represents one visual manifestation of CentOS corporate
-visual identity. *Note trunk Identity::, for more information.
+visual identity.
The first requirement for an identity directory structure to be
considered a renderable identity directory structure is its location
@@ -4120,21 +4112,19 @@ inside the working copy: it should be under `trunk/Identity/' or
The second requirement for an identity directory structure to be
considered a renderable identity directory structure is its directory
structure: it needs to have one `Tpl/' directory to store design
-templates files, one `Img/' directory to store files produced as
+template files, one `Img/' directory to store files produced as
rendition result, one translation directory structure to store
translation files and one script directory to store pre-rendition
configuration scripts. All these directory structures are connected
among themselves by a common component in their path that bonds them
-altogether. *Note trunk Scripts Bash Functions Path::, for more
-information.
+altogether.
Inside renderable identity directory structures, `centos-art.sh' can
render both image-based and text-based files. Specification of whether
a renderable identity directory structure produces image-based or
text-based content is a configuration action that takes place in the
pre-rendition configuration script of that renderable identity
-directory structure. *Note trunk Scripts Bash Functions Render
-Config::, for more information.
+directory structure.
Inside renderable identity directory structures, content production
is organized in different configurations. A content production
@@ -4144,7 +4134,7 @@ configuration does one thing only (e.g., to produce untranslated
images), but it can be extended (e.g., adding translation files) to
achieve different needs (e.g., to produce translated images).
-3.42.3.1 Design template without translation
+3.42.1.1 Design template without translation
............................................
The design template without translation configuration is based on a
@@ -4152,41 +4142,42 @@ renderable identity directory structure with an empty translation
directory structure. In this configuration, one design template
produces one untranslated file. Both design templates and final
untranslated files share the same file name, but they differ one
-another in the file-type itself and the file-extension used to describe
-the file type.
-
- Design templates are based on SVG (Scalable Vector Graphics) and use
-the extension `.svg'. Files produced as rendition result (i.e., the
-final files translated or not) may be text-based files with arbitrary
-extensions, or PNG (Portable Network Graphics) files with the extension
-`.png'. Definition of whether a final file is text-based or
-image-based is set in the pre-rendition configuration script of the
-renderable directory structure we want to produce files for.
+another in file-type and file-extension.
For example, to produce images without translations (there is no much
use in producing text-based files without translations), consider the
following configuration:
*One renderable identity directory structure:*
- Specify the identity component we want to produce images for.
-
-
- trunk/Identity/DirName
- |-- Tpl
- | `-- file.svg
- `-- Img
- `-- file.png
-
- Inside design template directory, design template files can be
- organized using several directory levels. Using several levels of
- directories inside design template directory let us to create very
- simple but extensible configurations, specially if translated
- images are not required.
-
- *Note* When we use a "design template without translation"
- configuration, `centos-art.sh' creates the `Img/' directory
- structure automatically taking the `Tpl/' directory structure
- as reference at rendition time.
+ In this example we used `Identity/Path/To/Dir' as the identity
+ component we want to produce untranslated images for. Identity
+ components can be either under `trunk/' or `branches/' directory
+ structure.
+
+ The identity component (i.e., `Identity/Path/To/Dir', in this
+ case) is also the bond component we use to connect the identity
+ directory structures with their respective auxiliar directories
+ (i.e., translation directory structres and pre-rendition
+ configuration structures). The bond component is the path
+ convenction that `centos-art.sh' uses to know where to look for
+ related translations, configuration scripts and whatever auxiliar
+ thing a renderable directory structure may need to have.
+
+
+ | The bond component
+ |----------------->|
+ trunk/Identity/Path/To/Dir <-- Renderable identity directory structure.
+ |-- Tpl <-- Design template directory.
+ | `-- file.svg <-- Design template file.
+ `-- Img <-- Directory used to store final files.
+ `-- file.png <-- Final image-based file produced from
+ design template file.
+
+ Inside design template directory, design template files are based
+ on SVG (Scalable Vector Graphics) and use the extension `.svg'.
+ Design template files can be organized using several directory
+ levels to create a simple but extensible configuration, specially
+ if translated images are not required.
In order for SVG (Scalable Vector Graphics) files to be considered
"design template" files, they should be placed under the design
@@ -4195,10 +4186,22 @@ following configuration:
The `CENTOSARTWORK' word itself is a convenction name we use to
define which object/design area, inside a design template, the
- `centos-art.sh' script will use to export as PNG image at
- rendition time. Whithout such object id specification, the
- `centos-art.sh' script cannot know what object/design area you (as
- designer) want to export as PNG image file.
+ `centos-art.sh' script will use to export as PNG (Portable Network
+ Graphic) image at rendition time. Whithout such object id
+ specification, the `centos-art.sh' script cannot know what
+ object/design area you (as designer) want to export as PNG
+ (Portable Network Graphic) image file.
+
+ *Note* At rendition time, the content of `Img/' directory
+ structure is produced by `centos-art.sh' automatically.
+
+ When a renderable identity directory structure is configured to
+ produce image-based content, `centos-art.sh' produces PNG
+ (Portable Network Graphics) files with the `.png' extension. Once
+ the base image format has been produced, it is possible for
+ `centos-art.sh' to use it in order to automatically create other
+ image formats that may be needed (*note trunk Scripts Bash
+ Functions Render Config::).
Inside the working copy, you can find an example of "design
template without translation" configuration at
@@ -4210,7 +4213,7 @@ following configuration:
In order for an identity entry to be considered an identity
renderable directory structure, it should have a translation
entry. The content of the translation entry is relevant to
- determine how the identity renderable directory entry is processed.
+ determine how to process the identity renderable directory entry.
If the translation entry is empty (i.e., there is no file inside
it), `centos-art.sh' interprets the identity renderable directory
@@ -4218,38 +4221,48 @@ following configuration:
configuration.
- trunk/Translations/Identity/DirName
+ | The bond component
+ |----------------->|
+ trunk/Translations/Identity/Path/To/Dir
`-- (empty)
If the translation entry is not empty, `centos-art.sh' can
- interpret the identity renderable directory structure as any of the
- following configuration: "design templates with translations
- (one-to-one)" or "design templates with translations (optimized)".
- Which one of these configuration is used depends on the value
- assigned to the matching list (MATCHINGLIST) variable.
+ interpret the identity renderable directory structure as one of the
+ following configurations: "design template with translation
+ (one-to-one)" or "design template with translation (optimized)".
+ Which one of these configurations is used depends on the value
+ assigned to the matching list (MATCHINGLIST) variable in the
+ pre-rendition configuration script of the renderable identity
+ directory structure we are producing images for.
If the matching list variable is empty (as it is by default), then
- "design templates with translations (one-to-one)" configuration is
+ "design template with translation (one-to-one)" configuration is
used. In this configuration it is required that both design
- templates and translation files have the same file names.
+ templates and translation files have the same file names. This
+ way, _one_ translation files is applied to _one_ design template,
+ to produce _one_ translated image.
If the matching list variable is not empty (because you redefine
it in the pre-rendition configuration script), then "design
- templates with translations (optimized)" configuration is used
+ template with translation (optimized)" configuration is used
instead. In this configuration, design templates and translation
- files don't need to have the same names since such relation
- between them is specified in the matching list properly.
+ files don't need to have the same names since such name
+ relationship between them is specified in the matching list
+ properly.
*Note trunk Translations::, for more information.
*One pre-rendition configuration script:*
- In order to make an identity entry renderable, a pre-rendition
- configuration script should exist for it. The pre-rendition
- configuration script specifies what type of rendition does
- `centos-art.sh' will perform and the way it does it.
+ In order to make an identity directory structure renderable, a
+ pre-rendition configuration script should exist for it. The
+ pre-rendition configuration script specifies what type of rendition
+ does `centos-art.sh' will perform over the identity directory
+ structure and how does it do that.
- trunk/Scripts/Bash/Functions/Render/Config/Identity/DirName
+ | The bond component
+ |----------------->|
+ trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir
`-- render.conf.sh
In this configuration the pre-rendition configuration script
@@ -4263,19 +4276,25 @@ following configuration:
}
+ Since translation directory structure is empty, `centos-art.sh'
+ assumes a "design template without translation" configuration to
+ produce untranslated images.
+
To produce untranslated images, `centos-art.sh' takes one design
- template and creates one temporal instance from it. Later,
+ template and creates one temporal instance from it. Later,
`centos-art.sh' uses the temporal design template instance as
- source file to export the final untranslated image. The export
- action is possible thanks to Inkscape's command-line interface and
- the `CENTOSARTWORK' object id we set inside design templates.
+ source file to export the final untranslated image. The action of
+ exporting images from SVG (Scalable Vector Graphics) to PNG
+ (Portable Network Graphics) is possible thanks to Inkscape's
+ command-line interface and the `CENTOSARTWORK' object id we
+ previously set inside design templates.
- centos-art.sh render --identity=trunk/Identity/DirName
+ centos-art.sh render --identity=trunk/Identity/Path/To/Dir
-------------------------------------------------
0 | Execute centos-art.sh on renderable identity directory structure.
--v----------------------------------------------
- trunk/Identity/DirName/Tpl/file.svg
+ trunk/Identity/Path/To/Dir/Tpl/file.svg
-------------------------------------------------
1 | Create instance from design template.
--v----------------------------------------------
@@ -4288,14 +4307,15 @@ following configuration:
3 | Remove design template instance.
Finally, when the untranslated image has been created, the temporal
- design template instance is removed. At this point, the next design
- template in the list is taken to repeat the production flow once
- again and so on, until all design templates be processed.
+ design template instance is removed. At this point,
+ `centos-art.sh' takes the next design template and repeats the
+ whole production flow once again (design template by design
+ template), until all design templates be processed.
*Note trunk Scripts Bash Functions Render Config::, for more
information.
-3.42.3.2 Design template with translation (one-to-one)
+3.42.1.2 Design template with translation (one-to-one)
......................................................
Producing untranslated images is fine in many cases, but not always.
@@ -4314,11 +4334,11 @@ produce the final image related to the missing component.
In order for `centos-art.sh' to know which is the relation between
translation files and design templates the translation directory
structure is taken as reference. For example, the
-`trunk/Translations/Identity/DirName/file.sed' translation file does
-match `trunk/Identity/DirName/Tpl/file.svg' design template, but it
-doesn't match `trunk/Identity/DirName/File.svg' or
-`trunk/Identity/DirName/Tpl/File.svg' or
-`trunk/Identity/DirName/Tpl/SubDir/file.svg' design templates.
+`trunk/Translations/Identity/Path/To/Dir/file.sed' translation file
+does match `trunk/Identity/Path/To/Dir/Tpl/file.svg' design template,
+but it doesn't match `trunk/Identity/Path/To/Dir/File.svg' or
+`trunk/Identity/Path/To/Dir/Tpl/File.svg' or
+`trunk/Identity/Path/To/Dir/Tpl/SubDir/file.svg' design templates.
The pre-rendition configuration script used to produce untranslated
images is the same we use to produce translated images. There is no
@@ -4341,15 +4361,15 @@ instance. This production flow is repeated for each translation file
available in the translatio entry.
-centos-art.sh render --identity=trunk/Identity/DirName
+centos-art.sh render --identity=trunk/Identity/Path/To/Dir
-------------------------------------------------
0 | Execute centos-art.sh on directory structure.
--v----------------------------------------------
-trunk/Translations/Identity/DirName/file.sed
+trunk/Translations/Identity/Path/To/Dir/file.sed
-------------------------------------------------
1 | Apply translation to design template.
--v----------------------------------------------
-trunk/Identity/DirName/Tpl/file.svg
+trunk/Identity/Path/To/Dir/Tpl/file.svg
-------------------------------------------------
2 | Create design template instance.
--v----------------------------------------------
@@ -4361,7 +4381,7 @@ trunk/Identity/NewDir/Img/file.png
-------------------------------------------------
4 | Remove design template instance.
-3.42.3.3 Design template with translation (optimized)
+3.42.1.3 Design template with translation (optimized)
.....................................................
Producing translated images satisfies almost all our production images
@@ -4399,7 +4419,7 @@ know how translation files are applied to design templates.
`list.svg' design template.
- trunk/Identity/DirName
+ trunk/Identity/Path/To/Dir
|-- Tpl
| |-- paragraph.svg
| `-- list.svg
@@ -4419,7 +4439,7 @@ know how translation files are applied to design templates.
the matching list itself.
- trunk/Translations/Identity/DirName
+ trunk/Translations/Identity/Path/To/Dir
|-- 01-welcome.sed
|-- 02-donate.sed
|-- 03-docs.sed
@@ -4436,7 +4456,7 @@ know how translation files are applied to design templates.
component we want to produce images for.
- trunk/Scripts/Bash/Functions/Render/Config/Identity/DirName
+ trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir
`-- render.conf.sh
In this configuration the pre-rendition configuration script
@@ -4465,7 +4485,7 @@ know how translation files are applied to design templates.
design template, but `03-docs.png' using the list-based design
template.
-3.42.3.4 Design template with translation (optimized+flexibility)
+3.42.1.4 Design template with translation (optimized+flexibility)
.................................................................
In the production models we've seen so far, there are design templates
@@ -4516,7 +4536,7 @@ later create combinations among them using `centos-art.sh'.
dynamic backgrounds inclusion while design templates don't.
- THEMEMODEL | | Design model component
+ THEMEMODEL | | The bond component
|<----| |--------------------->|
trunk/Identity/Themes/Models/Default/Distro/Anaconda/Progress/
|-- paragraph.svg
@@ -4562,7 +4582,7 @@ later create combinations among them using `centos-art.sh'.
we want to produce images for.
- | Design model component
+ | The bond component
|--------------------->|
trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/
`-- 5
@@ -4610,7 +4630,7 @@ later create combinations among them using `centos-art.sh'.
The production flow of "optimize+flexibility" configuration...
-3.42.4 Renderable translation directory structures
+3.42.2 Renderable translation directory structures
--------------------------------------------------
Translation directory structures are auxiliar structures of renderable
@@ -4641,7 +4661,7 @@ translation templates.
Inside renderable translation directory structures, `centos-art.sh'
can produce text-based files only.
-3.42.5 Copying renderable directory structures
+3.42.3 Copying renderable directory structures
----------------------------------------------
A renderable layout is formed by design models, design images,
@@ -4679,22 +4699,22 @@ location specified by FLAG_TO variable.
Design templates + No translation:
- Command: - centos-art render -copy=trunk/Identity/DirName
--to=trunk/Identity/NewDirName
+ Command: - centos-art render -copy=trunk/Identity/Path/To/Dir
+-to=trunk/Identity/NewPath/To/Dir
- Sources: - trunk/Identity/DirName -
-trunk/Translations/Identity/DirName -
-trunk/Scripts/Bash/Functions/Render/Config/Identity/DirName
+ Sources: - trunk/Identity/Path/To/Dir -
+trunk/Translations/Identity/Path/To/Dir -
+trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir
- Targets: - trunk/Identity/NewDirName -
-trunk/Translations/Identity/NewDirName -
-trunk/Scripts/Bash/Functions/Render/Config/Identity/NewDirName
+ Targets: - trunk/Identity/NewPath/To/Dir -
+trunk/Translations/Identity/NewPath/To/Dir -
+trunk/Scripts/Bash/Functions/Render/Config/Identity/NewPath/To/Dir
Renderable layout 2:
Command: - centos-art render
-copy=trunk/Identity/Themes/Motifs/TreeFlower \
--to=trunk/Identity/Themes/Motifs/NewDirName
+-to=trunk/Identity/Themes/Motifs/NewPath/To/Dir
Sources: - trunk/Identity/Themes/Motifs/TreeFlower -
trunk/Translations/Identity/Themes -
@@ -4702,11 +4722,11 @@ trunk/Translations/Identity/Themes/Motifs/TreeFlower -
trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes -
trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/TreeFlower
- Targets: - trunk/Identity/Themes/Motifs/NewDirName -
+ Targets: - trunk/Identity/Themes/Motifs/NewPath/To/Dir -
trunk/Translations/Identity/Themes -
-trunk/Translations/Identity/Themes/Motifs/NewDirName -
+trunk/Translations/Identity/Themes/Motifs/NewPath/To/Dir -
trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes -
-trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewDirName
+trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewPath/To/Dir
Notice that design models are not included in source or target
locations. This is intentional. In "Renderable layout 2", design models
@@ -4762,12 +4782,12 @@ still in need of it.
directly involved in rendition process only. Once such directories have
been duplicated, the functionality stops thereat.
-3.42.6 Usage
+3.42.4 Usage
------------
* ...
-3.42.7 See also
+3.42.5 See also
---------------
3.43 trunk/Scripts/Bash/Functions/Render/Config
@@ -6584,94 +6604,94 @@ documentation entry (*note trunk Translations::).
Index
*****
-branches: See 1. (line 389)
-Common translation files: See 3.50.2.5. (line 6014)
-How to render brands' translation files: See 3.52.3. (line 6318)
-How to render fonts' translation files: See 3.54.3. (line 6391)
-How to render translation files: See 3.50.3. (line 6184)
-Metadata maintainance: See 3.45.2. (line 5144)
-Specific translation files: See 3.50.2.6. (line 6039)
-tags: See 2. (line 392)
-Template translation files: See 3.50.2.4. (line 5844)
-Translation brands file names: See 3.52.2.1. (line 6275)
-Translation configuration scripts: See 3.50.2.8. (line 6073)
-Translation entries: See 3.50.2.1. (line 5660)
-Translation files: See 3.50.2.3. (line 5776)
-Translation markers: See 3.50.2.2. (line 5741)
-Translation paths: See 3.50.2.1. (line 5660)
+branches: See 1. (line 387)
+Common translation files: See 3.50.2.5. (line 6034)
+How to render brands' translation files: See 3.52.3. (line 6338)
+How to render fonts' translation files: See 3.54.3. (line 6411)
+How to render translation files: See 3.50.3. (line 6204)
+Metadata maintainance: See 3.45.2. (line 5164)
+Specific translation files: See 3.50.2.6. (line 6059)
+tags: See 2. (line 390)
+Template translation files: See 3.50.2.4. (line 5864)
+Translation brands file names: See 3.52.2.1. (line 6295)
+Translation configuration scripts: See 3.50.2.8. (line 6093)
+Translation entries: See 3.50.2.1. (line 5680)
+Translation files: See 3.50.2.3. (line 5796)
+Translation markers: See 3.50.2.2. (line 5761)
+Translation paths: See 3.50.2.1. (line 5680)
Translation pre-rendering configuration scripts:See 3.50.2.8.
- (line 6073)
-Translation rendering: See 3.50.2.7. (line 6062)
-Translation rendering default functionality: See 3.50.2.9. (line 6159)
-trunk: See 3. (line 395)
-trunk Identity: See 3.1. (line 398)
-trunk Identity Brands: See 3.2. (line 514)
-trunk Identity Fonts: See 3.3. (line 531)
-trunk Identity Icons: See 3.4. (line 608)
-trunk Identity Isolinux: See 3.5. (line 625)
-trunk Identity Models: See 3.6. (line 642)
-trunk Identity Models Css: See 3.7. (line 662)
-trunk Identity Models Html: See 3.8. (line 684)
-trunk Identity Models Img Promo Web: See 3.9. (line 705)
-trunk Identity Models Tpl: See 3.10. (line 726)
-trunk Identity Models Tpl Promo Web: See 3.11. (line 747)
-trunk Identity Models Xcf: See 3.12. (line 1077)
-trunk Identity Release: See 3.13. (line 1098)
-trunk Identity Themes: See 3.14. (line 1115)
-trunk Identity Themes Models: See 3.15. (line 1140)
-trunk Identity Themes Models Alternative: See 3.16. (line 1173)
-trunk Identity Themes Models Default: See 3.17. (line 1200)
-trunk Identity Themes Models Default Distro: See 3.18. (line 1232)
+ (line 6093)
+Translation rendering: See 3.50.2.7. (line 6082)
+Translation rendering default functionality: See 3.50.2.9. (line 6179)
+trunk: See 3. (line 393)
+trunk Identity: See 3.1. (line 396)
+trunk Identity Brands: See 3.2. (line 512)
+trunk Identity Fonts: See 3.3. (line 529)
+trunk Identity Icons: See 3.4. (line 606)
+trunk Identity Isolinux: See 3.5. (line 623)
+trunk Identity Models: See 3.6. (line 640)
+trunk Identity Models Css: See 3.7. (line 660)
+trunk Identity Models Html: See 3.8. (line 682)
+trunk Identity Models Img Promo Web: See 3.9. (line 703)
+trunk Identity Models Tpl: See 3.10. (line 724)
+trunk Identity Models Tpl Promo Web: See 3.11. (line 745)
+trunk Identity Models Xcf: See 3.12. (line 1075)
+trunk Identity Release: See 3.13. (line 1096)
+trunk Identity Themes: See 3.14. (line 1113)
+trunk Identity Themes Models: See 3.15. (line 1138)
+trunk Identity Themes Models Alternative: See 3.16. (line 1171)
+trunk Identity Themes Models Default: See 3.17. (line 1198)
+trunk Identity Themes Models Default Distro: See 3.18. (line 1230)
trunk Identity Themes Models Default Distro Anaconda:See 3.19.
- (line 1316)
-trunk Identity Themes Models Default Promo: See 3.20. (line 1333)
-trunk Identity Themes Models Default Web: See 3.21. (line 1359)
-trunk Identity Themes Motifs: See 3.22. (line 1384)
-trunk Identity Themes Motifs Flame: See 3.23. (line 1487)
-trunk Identity Themes Motifs Modern: See 3.24. (line 1698)
-trunk Identity Themes Motifs Modern Backgrounds:See 3.25. (line 1717)
+ (line 1314)
+trunk Identity Themes Models Default Promo: See 3.20. (line 1331)
+trunk Identity Themes Models Default Web: See 3.21. (line 1357)
+trunk Identity Themes Motifs: See 3.22. (line 1382)
+trunk Identity Themes Motifs Flame: See 3.23. (line 1485)
+trunk Identity Themes Motifs Modern: See 3.24. (line 1696)
+trunk Identity Themes Motifs Modern Backgrounds:See 3.25. (line 1715)
trunk Identity Themes Motifs Modern Backgrounds Img:See 3.26.
- (line 1838)
+ (line 1836)
trunk Identity Themes Motifs Modern Backgrounds Tpl:See 3.27.
- (line 1859)
+ (line 1857)
trunk Identity Themes Motifs Modern Backgrounds Xcf:See 3.28.
- (line 1880)
+ (line 1878)
trunk Identity Themes Motifs Modern Distro Anaconda Progress:See 3.29.
- (line 1907)
-trunk Identity Themes Motifs Modern Palettes: See 3.30. (line 1963)
-trunk Identity Themes Motifs TreeFlower: See 3.31. (line 1985)
+ (line 1905)
+trunk Identity Themes Motifs Modern Palettes: See 3.30. (line 1961)
+trunk Identity Themes Motifs TreeFlower: See 3.31. (line 1983)
trunk Identity Themes Motifs TreeFlower Backgrounds:See 3.32.
- (line 2004)
-trunk Identity Widgets: See 3.33. (line 2302)
-trunk Manuals: See 3.34. (line 2319)
-trunk Scripts: See 3.35. (line 2340)
-trunk Scripts Bash: See 3.36. (line 2364)
-trunk Scripts Bash Functions: See 3.37. (line 2513)
-trunk Scripts Bash Functions Html: See 3.38. (line 3622)
-trunk Scripts Bash Functions Locale: See 3.39. (line 3643)
-trunk Scripts Bash Functions Manual: See 3.40. (line 3723)
-trunk Scripts Bash Functions Path: See 3.41. (line 3744)
-trunk Scripts Bash Functions Render: See 3.42. (line 4087)
-trunk Scripts Bash Functions Render Config: See 3.43. (line 4776)
-trunk Scripts Bash Functions Shell: See 3.44. (line 4954)
-trunk Scripts Bash Functions Svg: See 3.45. (line 5126)
-trunk Scripts Bash Functions Verify: See 3.46. (line 5314)
-trunk Scripts Bash Locale: See 3.47. (line 5544)
-trunk Scripts Perl: See 3.48. (line 5573)
-trunk Scripts Python: See 3.49. (line 5590)
-trunk Translations: See 3.50. (line 5611)
-trunk Translations Identity: See 3.51. (line 6213)
-trunk Translations Identity Brands: See 3.52. (line 6234)
-trunk Translations Identity Brands Tpl: See 3.53. (line 6329)
-trunk Translations Identity Fonts: See 3.54. (line 6344)
-trunk Translations Identity Models: See 3.55. (line 6407)
-trunk Translations Identity Release: See 3.56. (line 6422)
-trunk Translations Identity Themes: See 3.57. (line 6437)
-trunk Translations Identity Themes Backgrounds:See 3.58. (line 6452)
+ (line 2002)
+trunk Identity Widgets: See 3.33. (line 2300)
+trunk Manuals: See 3.34. (line 2317)
+trunk Scripts: See 3.35. (line 2338)
+trunk Scripts Bash: See 3.36. (line 2362)
+trunk Scripts Bash Functions: See 3.37. (line 2511)
+trunk Scripts Bash Functions Html: See 3.38. (line 3620)
+trunk Scripts Bash Functions Locale: See 3.39. (line 3641)
+trunk Scripts Bash Functions Manual: See 3.40. (line 3721)
+trunk Scripts Bash Functions Path: See 3.41. (line 3742)
+trunk Scripts Bash Functions Render: See 3.42. (line 4085)
+trunk Scripts Bash Functions Render Config: See 3.43. (line 4796)
+trunk Scripts Bash Functions Shell: See 3.44. (line 4974)
+trunk Scripts Bash Functions Svg: See 3.45. (line 5146)
+trunk Scripts Bash Functions Verify: See 3.46. (line 5334)
+trunk Scripts Bash Locale: See 3.47. (line 5564)
+trunk Scripts Perl: See 3.48. (line 5593)
+trunk Scripts Python: See 3.49. (line 5610)
+trunk Translations: See 3.50. (line 5631)
+trunk Translations Identity: See 3.51. (line 6233)
+trunk Translations Identity Brands: See 3.52. (line 6254)
+trunk Translations Identity Brands Tpl: See 3.53. (line 6349)
+trunk Translations Identity Fonts: See 3.54. (line 6364)
+trunk Translations Identity Models: See 3.55. (line 6427)
+trunk Translations Identity Release: See 3.56. (line 6442)
+trunk Translations Identity Themes: See 3.57. (line 6457)
+trunk Translations Identity Themes Backgrounds:See 3.58. (line 6472)
trunk Translations Identity Themes Distro Anaconda Progress:See 3.59.
- (line 6473)
-trunk Translations Identity Widgets: See 3.60. (line 6566)
-Unused definitions: See 3.45.2.1. (line 5251)
+ (line 6493)
+trunk Translations Identity Widgets: See 3.60. (line 6586)
+Unused definitions: See 3.45.2.1. (line 5271)
List of Figures
***************
diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Render.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Render.texi
index 60cd556..58eadca 100644
--- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Render.texi
+++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Render.texi
@@ -1,13 +1,8 @@
-@subsection Goals
-
The @code{render} functionality exists to automate production of files
-inside the working copy. The @code{render} functionality is aimed to
-satisfy different file types (e.g., text-based and image-based)
-production needs in different information levels (e.g., different
-languages, release numbers, different architectures, etc.).
-
-@subsection Description
-
+inside the working copy. Specifically, the @code{render} functionality
+is aimed to produce text-based and image-based files in different
+information levels (i.e., different languages, release numbers,
+architectures, etc.).
The @code{render} functionality relies on ``renderable directory
structures'' to produce files. Renderable directory structures can be
@@ -22,7 +17,7 @@ visual identity we need to point @file{centos-art.sh} to an identity
directory structure. If such identity directory structure doesn't
exist, then it is good time to create it. Each identity directory
structure represents one visual manifestation of CentOS corporate
-visual identity. @xref{trunk Identity}, for more information.
+visual identity.
The first requirement for an identity directory structure to be
considered a renderable identity directory structure is its location
@@ -32,21 +27,19 @@ inside the working copy: it should be under @file{trunk/Identity/} or
The second requirement for an identity directory structure to be
considered a renderable identity directory structure is its directory
structure: it needs to have one @file{Tpl/} directory to store design
-templates files, one @file{Img/} directory to store files produced as
+template files, one @file{Img/} directory to store files produced as
rendition result, one translation directory structure to store
translation files and one script directory to store pre-rendition
configuration scripts. All these directory structures are connected
among themselves by a common component in their path that bonds them
-altogether. @xref{trunk Scripts Bash Functions Path}, for more
-information.
+altogether.
Inside renderable identity directory structures, @file{centos-art.sh}
can render both image-based and text-based files. Specification of
whether a renderable identity directory structure produces image-based
or text-based content is a configuration action that takes place in
the pre-rendition configuration script of that renderable identity
-directory structure. @xref{trunk Scripts Bash Functions Render
-Config}, for more information.
+directory structure.
Inside renderable identity directory structures, content production is
organized in different configurations. A content production
@@ -63,17 +56,7 @@ renderable identity directory structure with an empty translation
directory structure. In this configuration, one design template
produces one untranslated file. Both design templates and final
untranslated files share the same file name, but they differ one
-another in the file-type itself and the file-extension used to
-describe the file type.
-
-Design templates are based on @acronym{SVG,Scalable Vector Graphics}
-and use the extension @code{.svg}. Files produced as rendition result
-(i.e., the final files translated or not) may be text-based files with
-arbitrary extensions, or @acronym{PNG,Portable Network Graphics} files
-with the extension @code{.png}. Definition of whether a final file is
-text-based or image-based is set in the pre-rendition configuration
-script of the renderable directory structure we want to produce files
-for.
+another in file-type and file-extension.
For example, to produce images without translations (there is no much
use in producing text-based files without translations), consider the
@@ -82,28 +65,36 @@ following configuration:
@table @strong
@item One renderable identity directory structure:
-Specify the identity component we want to produce images for.
+In this example we used @file{Identity/Path/To/Dir} as the identity
+component we want to produce untranslated images for. Identity
+components can be either under @file{trunk/} or @file{branches/}
+directory structure.
+
+The identity component (i.e., @file{Identity/Path/To/Dir}, in this
+case) is also the bond component we use to connect the identity
+directory structures with their respective auxiliar directories (i.e.,
+translation directory structres and pre-rendition configuration
+structures). The bond component is the path convenction that
+@file{centos-art.sh} uses to know where to look for related
+translations, configuration scripts and whatever auxiliar thing a
+renderable directory structure may need to have.
@verbatim
-trunk/Identity/DirName
-|-- Tpl
-| `-- file.svg
-`-- Img
- `-- file.png
+ | The bond component
+ |----------------->|
+trunk/Identity/Path/To/Dir <-- Renderable identity directory structure.
+|-- Tpl <-- Design template directory.
+| `-- file.svg <-- Design template file.
+`-- Img <-- Directory used to store final files.
+ `-- file.png <-- Final image-based file produced from
+ design template file.
@end verbatim
-Inside design template directory, design template files can be
-organized using several directory levels. Using several levels of
-directories inside design template directory let us to create very
-simple but extensible configurations, specially if translated images
-are not required.
-
-@quotation
-@strong{Note} When we use a ``design template without translation''
-configuration, @file{centos-art.sh} creates the @file{Img/} directory
-structure automatically taking the @file{Tpl/} directory structure as
-reference at rendition time.
-@end quotation
+Inside design template directory, design template files are based on
+@acronym{SVG,Scalable Vector Graphics} and use the extension
+@code{.svg}. Design template files can be organized using several
+directory levels to create a simple but extensible configuration,
+specially if translated images are not required.
In order for @acronym{SVG,Scalable Vector Graphics} files to be
considered ``design template'' files, they should be placed under the
@@ -112,10 +103,24 @@ object id inside.
The @code{CENTOSARTWORK} word itself is a convenction name we use to
define which object/design area, inside a design template, the
-@file{centos-art.sh} script will use to export as PNG image at
-rendition time. Whithout such object id specification, the
-@file{centos-art.sh} script cannot know what object/design area you
-(as designer) want to export as PNG image file.
+@file{centos-art.sh} script will use to export as
+@acronym{PNG,Portable Network Graphic} image at rendition time.
+Whithout such object id specification, the @file{centos-art.sh} script
+cannot know what object/design area you (as designer) want to export
+as @acronym{PNG,Portable Network Graphic} image file.
+
+@quotation
+@strong{Note} At rendition time, the content of @file{Img/} directory
+structure is produced by @file{centos-art.sh} automatically.
+@end quotation
+
+When a renderable identity directory structure is configured to
+produce image-based content, @file{centos-art.sh} produces
+@acronym{PNG,Portable Network Graphics} files with the @code{.png}
+extension. Once the base image format has been produced, it is
+possible for @file{centos-art.sh} to use it in order to automatically
+create other image formats that may be needed (@pxref{trunk Scripts
+Bash Functions Render Config}).
Inside the working copy, you can find an example of ``design template
without translation'' configuration at @file{trunk/Identity/Models/}.
@@ -126,48 +131,57 @@ without translation'' configuration at @file{trunk/Identity/Models/}.
In order for an identity entry to be considered an identity renderable
directory structure, it should have a translation entry. The content
-of the translation entry is relevant to determine how the identity
-renderable directory entry is processed.
+of the translation entry is relevant to determine how to process the
+identity renderable directory entry.
If the translation entry is empty (i.e., there is no file inside it),
@file{centos-art.sh} interprets the identity renderable directory
structure as a ``design templates without translation'' configuration.
@verbatim
-trunk/Translations/Identity/DirName
+ | The bond component
+ |----------------->|
+trunk/Translations/Identity/Path/To/Dir
`-- (empty)
@end verbatim
If the translation entry is not empty, @file{centos-art.sh} can
-interpret the identity renderable directory structure as any of the
-following configuration: ``design templates with translations
-(one-to-one)'' or ``design templates with translations (optimized)''.
-Which one of these configuration is used depends on the value assigned
-to the matching list (@var{MATCHINGLIST}) variable.
+interpret the identity renderable directory structure as one of the
+following configurations: ``design template with translation
+(one-to-one)'' or ``design template with translation (optimized)''.
+Which one of these configurations is used depends on the value
+assigned to the matching list (@var{MATCHINGLIST}) variable in the
+pre-rendition configuration script of the renderable identity
+directory structure we are producing images for.
If the matching list variable is empty (as it is by default), then
-``design templates with translations (one-to-one)'' configuration is
+``design template with translation (one-to-one)'' configuration is
used. In this configuration it is required that both design templates
-and translation files have the same file names.
+and translation files have the same file names. This way, @emph{one}
+translation files is applied to @emph{one} design template, to produce
+@emph{one} translated image.
If the matching list variable is not empty (because you redefine it in
-the pre-rendition configuration script), then ``design templates with
-translations (optimized)'' configuration is used instead. In this
+the pre-rendition configuration script), then ``design template with
+translation (optimized)'' configuration is used instead. In this
configuration, design templates and translation files don't need to
-have the same names since such relation between them is specified in
-the matching list properly.
+have the same names since such name relationship between them is
+specified in the matching list properly.
@xref{trunk Translations}, for more information.
@item One pre-rendition configuration script:
-In order to make an identity entry renderable, a pre-rendition
-configuration script should exist for it. The pre-rendition
-configuration script specifies what type of rendition does
-@file{centos-art.sh} will perform and the way it does it.
+In order to make an identity directory structure renderable, a
+pre-rendition configuration script should exist for it. The
+pre-rendition configuration script specifies what type of rendition
+does @file{centos-art.sh} will perform over the identity directory
+structure and how does it do that.
@verbatim
-trunk/Scripts/Bash/Functions/Render/Config/Identity/DirName
+ | The bond component
+ |----------------->|
+trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir
`-- render.conf.sh
@end verbatim
@@ -183,19 +197,25 @@ function render_loadConfig {
}
@end verbatim
+Since translation directory structure is empty, @file{centos-art.sh}
+assumes a ``design template without translation'' configuration to
+produce untranslated images.
+
To produce untranslated images, @file{centos-art.sh} takes one design
-template and creates one temporal instance from it. Later,
+template and creates one temporal instance from it. Later,
@file{centos-art.sh} uses the temporal design template instance as
-source file to export the final untranslated image. The export action
-is possible thanks to Inkscape's command-line interface and the
-@code{CENTOSARTWORK} object id we set inside design templates.
+source file to export the final untranslated image. The action of
+exporting images from @acronym{SVG,Scalable Vector Graphics} to
+@acronym{PNG,Portable Network Graphics} is possible thanks to
+Inkscape's command-line interface and the @code{CENTOSARTWORK} object
+id we previously set inside design templates.
@verbatim
-centos-art.sh render --identity=trunk/Identity/DirName
+centos-art.sh render --identity=trunk/Identity/Path/To/Dir
-------------------------------------------------
0 | Execute centos-art.sh on renderable identity directory structure.
--v----------------------------------------------
-trunk/Identity/DirName/Tpl/file.svg
+trunk/Identity/Path/To/Dir/Tpl/file.svg
-------------------------------------------------
1 | Create instance from design template.
--v----------------------------------------------
@@ -209,9 +229,10 @@ trunk/Identity/NewDir/Img/file.png
@end verbatim
Finally, when the untranslated image has been created, the temporal
-design template instance is removed. At this point, the next design
-template in the list is taken to repeat the production flow once again
-and so on, until all design templates be processed.
+design template instance is removed. At this point,
+@file{centos-art.sh} takes the next design template and repeats the
+whole production flow once again (design template by design template),
+until all design templates be processed.
@xref{trunk Scripts Bash Functions Render Config}, for more
information.
@@ -236,11 +257,13 @@ missing component.
In order for @file{centos-art.sh} to know which is the relation
between translation files and design templates the translation
directory structure is taken as reference. For example, the
-@file{trunk/Translations/Identity/DirName/file.sed} translation file
-does match @file{trunk/Identity/DirName/Tpl/file.svg} design template,
-but it doesn't match @file{trunk/Identity/DirName/File.svg} or
-@file{trunk/Identity/DirName/Tpl/File.svg} or
-@file{trunk/Identity/DirName/Tpl/SubDir/file.svg} design templates.
+@file{trunk/Translations/Identity/Path/To/Dir/file.sed} translation
+file does match @file{trunk/Identity/Path/To/Dir/Tpl/file.svg} design
+template, but it doesn't match
+@file{trunk/Identity/Path/To/Dir/File.svg} or
+@file{trunk/Identity/Path/To/Dir/Tpl/File.svg} or
+@file{trunk/Identity/Path/To/Dir/Tpl/SubDir/file.svg} design
+templates.
The pre-rendition configuration script used to produce untranslated
images is the same we use to produce translated images. There is no
@@ -265,15 +288,15 @@ design template instance. This production flow is repeated for each
translation file available in the translatio entry.
@verbatim
-centos-art.sh render --identity=trunk/Identity/DirName
+centos-art.sh render --identity=trunk/Identity/Path/To/Dir
-------------------------------------------------
0 | Execute centos-art.sh on directory structure.
--v----------------------------------------------
-trunk/Translations/Identity/DirName/file.sed
+trunk/Translations/Identity/Path/To/Dir/file.sed
-------------------------------------------------
1 | Apply translation to design template.
--v----------------------------------------------
-trunk/Identity/DirName/Tpl/file.svg
+trunk/Identity/Path/To/Dir/Tpl/file.svg
-------------------------------------------------
2 | Create design template instance.
--v----------------------------------------------
@@ -327,7 +350,7 @@ template; and one image using a list-based style, controlled by
@file{list.svg} design template.
@verbatim
-trunk/Identity/DirName
+trunk/Identity/Path/To/Dir
|-- Tpl
| |-- paragraph.svg
| `-- list.svg
@@ -348,7 +371,7 @@ there is no need for translation files to match the names of design
templates, such name relation is set inside the matching list itself.
@verbatim
-trunk/Translations/Identity/DirName
+trunk/Translations/Identity/Path/To/Dir
|-- 01-welcome.sed
|-- 02-donate.sed
|-- 03-docs.sed
@@ -366,7 +389,7 @@ the matching list @var{MATCHINGLIST} variable inside the pre-rendition
configuration script of the component we want to produce images for.
@verbatim
-trunk/Scripts/Bash/Functions/Render/Config/Identity/DirName
+trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir
`-- render.conf.sh
@end verbatim
@@ -452,7 +475,7 @@ However, design models do use dynamic backgrounds inclusion while
design templates don't.
@verbatim
- THEMEMODEL | | Design model component
+ THEMEMODEL | | The bond component
|<----| |--------------------->|
trunk/Identity/Themes/Models/Default/Distro/Anaconda/Progress/
|-- paragraph.svg
@@ -501,7 +524,7 @@ model nor artistic motif, just the design model component we want to
produce images for.
@verbatim
- | Design model component
+ | The bond component
|--------------------->|
trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/
`-- 5
@@ -625,23 +648,23 @@ automatically to the new location specified by @var{FLAG_TO} variable.
Design templates + No translation:
Command:
-- centos-art render --copy=trunk/Identity/DirName --to=trunk/Identity/NewDirName
+- centos-art render --copy=trunk/Identity/Path/To/Dir --to=trunk/Identity/NewPath/To/Dir
Sources:
-- trunk/Identity/DirName
-- trunk/Translations/Identity/DirName
-- trunk/Scripts/Bash/Functions/Render/Config/Identity/DirName
+- trunk/Identity/Path/To/Dir
+- trunk/Translations/Identity/Path/To/Dir
+- trunk/Scripts/Bash/Functions/Render/Config/Identity/Path/To/Dir
Targets:
-- trunk/Identity/NewDirName
-- trunk/Translations/Identity/NewDirName
-- trunk/Scripts/Bash/Functions/Render/Config/Identity/NewDirName
+- trunk/Identity/NewPath/To/Dir
+- trunk/Translations/Identity/NewPath/To/Dir
+- trunk/Scripts/Bash/Functions/Render/Config/Identity/NewPath/To/Dir
Renderable layout 2:
Command:
- centos-art render --copy=trunk/Identity/Themes/Motifs/TreeFlower \
- --to=trunk/Identity/Themes/Motifs/NewDirName
+ --to=trunk/Identity/Themes/Motifs/NewPath/To/Dir
Sources:
- trunk/Identity/Themes/Motifs/TreeFlower
@@ -651,11 +674,11 @@ Sources:
- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/TreeFlower
Targets:
-- trunk/Identity/Themes/Motifs/NewDirName
+- trunk/Identity/Themes/Motifs/NewPath/To/Dir
- trunk/Translations/Identity/Themes
-- trunk/Translations/Identity/Themes/Motifs/NewDirName
+- trunk/Translations/Identity/Themes/Motifs/NewPath/To/Dir
- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes
-- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewDirName
+- trunk/Scripts/Bash/Functions/Render/Config/Identity/Themes/Motifs/NewPath/To/Dir
Notice that design models are not included in source or target
locations. This is intentional. In ``Renderable layout 2'', design
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.43 trunk/Scripts/Bash/Functions/Render/Config
-
+
3.43.1 Goals
3.43.2 Description
3.43.2.1 The `render.conf.sh' identity model
3.43.2.2 The `render.conf.sh' translation model
3.43.2.3 The `render.conf.sh' rendering actions
3.43.3 Usage
3.43.4 See also
@@ -275,12 +275,12 @@ directory path under `trunk/Identity' or
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.44 trunk/Scripts/Bash/Functions/Shell
-
+
3.44.1 Goals
shell
functionality of `centos-art.sh' script.
3.44.2 Description
shell
functionality of `centos-art.sh' script helps
@@ -215,7 +215,7 @@ used, please share your reasons at
+
3.44.3 Usage
@@ -251,7 +251,7 @@ that `regex', appended to `path/to/dir/' (i.e.
list of files to process.
3.44.4 See also
@@ -263,12 +263,12 @@ list of files to process.
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.45 trunk/Scripts/Bash/Functions/Svg
-
+
3.45.1 Goals
svg
functionality of `centos-art.sh' script.
3.45.2 Description
svg
functionality of `centos-art.sh' script helps you
@@ -95,7 +95,7 @@ functionality to aid you maintain such actions.
3.45.2.1 Metadata maintainance
3.45.2.2 Unused definitions
3.45.3 Usage
@@ -283,7 +283,7 @@ that `regex', appended to `path/to/dir/' (i.e.
list of files to process.
3.45.4 See also
@@ -295,12 +295,12 @@ list of files to process.
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.46 trunk/Scripts/Bash/Functions/Verify
-
+
3.46.1 Goals
3.46.2 Description
3.46.2.1 Packages
sudo
privileges.
3.46.2.2 Links
3.46.2.3 Environment variables
3.46.3 Usage
@@ -330,7 +330,7 @@ provided at all.
-
+
3.46.4 See also
@@ -342,12 +342,12 @@ provided at all.
@@ -101,7 +101,7 @@ ul.toc {list-style: none}
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.47 trunk/Scripts/Bash/Locale
-
+
3.47.1 Goals
3.47.2 Description
3.47.3 Usage
3.47.4 See also
@@ -111,12 +111,12 @@ be managed manually. Instead, use the "locale" functionality of
@@ -112,7 +112,7 @@ to build artworks.
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.48 trunk/Scripts/Perl
-
+
3.48.1 Goals
@@ -82,26 +82,26 @@ ul.toc {list-style: none}
-
+
3.48.2 Description
-
+
3.48.3 Usage
-
+
3.48.4 See also
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.49 trunk/Scripts/Python
-
+
3.49.1 Goals
@@ -82,7 +82,7 @@ ul.toc {list-style: none}
-
+
3.49.2 Description
@@ -90,7 +90,7 @@ ul.toc {list-style: none}
-
+
3.49.3 Usage
@@ -98,18 +98,18 @@ ul.toc {list-style: none}
-
+
3.49.4 See also
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.50 trunk/Translations
-
+
3.50.1 Goals
3.50.2 Description
3.50.2.1 Translation Entries
3.50.2.2 Translation Markers
3.50.2.3 Translation Files
sed
commands inside,
@@ -322,7 +322,7 @@ command with the release number you want to produce translation files
for in the `--filter='release-number'' argument.
3.50.2.4 Template Translation Files
3.50.2.5 Common Translation Files
3.50.2.6 Specific Translation Files
3.50.2.7 Translation Rendering
centos-art
script checks
@@ -553,7 +553,7 @@ case the centos-art
script outputs a message and quits
script execution.
3.50.2.8 Translation (Pre-)Rendering Configuration Scripts
centos-art
script finds a translation template
@@ -642,7 +642,7 @@ above translation pre-rendering configuration directory, is
`render.conf.sh'.
3.50.2.9 Translation Rendering Default Functionality
3.50.3 Usage
@@ -695,19 +695,19 @@ distribution you want to render translations for.
-
+
3.50.4 See also
-
3.52 trunk/Translations/Identity/Brands
+
-3.52 trunk/Translations/Identity/Brands
3.54 trunk/Translations/Identity/Fonts
+
-3.54 trunk/Translations/Identity/Fonts
3.55 trunk/Translations/Identity/Models
+
-3.55 trunk/Translations/Identity/Models
3.56 trunk/Translations/Identity/Release
+
-3.56 trunk/Translations/Identity/Release
3.57 trunk/Translations/Identity/Themes
+ 3.57 trunk/Translations/Identity/Themes
@@ -715,12 +715,12 @@ distribution you want to render translations for.
3.1 trunk/Identity
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.51 trunk/Translations/Identity
-
+
3.51.1 Goals
@@ -82,7 +82,7 @@ ul.toc {list-style: none}
-
+
3.51.2 Description
@@ -90,7 +90,7 @@ ul.toc {list-style: none}
-
+
3.51.3 Usage
@@ -98,21 +98,21 @@ ul.toc {list-style: none}
-
+
3.51.4 See also
-
@@ -101,7 +101,7 @@ ul.toc {list-style: none}
3.52 trunk/Translations/Identity/Brands
+
-3.52 trunk/Translations/Identity/Brands
3.54 trunk/Translations/Identity/Fonts
+
-3.54 trunk/Translations/Identity/Fonts
3.55 trunk/Translations/Identity/Models
+
-3.55 trunk/Translations/Identity/Models
3.56 trunk/Translations/Identity/Release
+
-3.56 trunk/Translations/Identity/Release
3.57 trunk/Translations/Identity/Themes
+
-3.57 trunk/Translations/Identity/Themes
3.60 trunk/Translations/Identity/Widgets
+ 3.60 trunk/Translations/Identity/Widgets
@@ -120,12 +120,12 @@ ul.toc {list-style: none}
3.1 trunk/Identity
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.52 trunk/Translations/Identity/Brands
-
+
3.52.1 Goals
@@ -82,7 +82,7 @@ ul.toc {list-style: none}
-
+
3.52.2 Description
3.52.2.1 Conventional file names
3.52.2.2 Numeric file names
3.52.2.3 Translation markers
3.52.3 Usage
centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands
-
+
3.52.4 See also
-
3.53 trunk/Translations/Identity/Brands/Tpl
+ 3.53 trunk/Translations/Identity/Brands/Tpl
@@ -190,12 +190,12 @@ inside template translation files.
3.2 trunk/Identity/Brands
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.53 trunk/Translations/Identity/Brands/Tpl
-
+
3.53.1 Goals
-
+
3.53.2 Description
-
+
3.53.3 Usage
-
+
3.53.4 See also
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.54 trunk/Translations/Identity/Fonts
-
+
3.54.1 Goals
3.54.2 Description
3.54.2.1 Translation Markers
3.54.3 Usage
vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed
-
+
3.54.4 See also
@@ -146,12 +146,12 @@ directory (`Tpl/'), nor translation rendering using
@@ -167,7 +167,7 @@ improve this section with your reasons.
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.55 trunk/Translations/Identity/Models
-
+
3.55.1 Goals
-
+
3.55.2 Description
-
+
3.55.3 Usage
-
+
3.55.4 See also
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.56 trunk/Translations/Identity/Release
-
+
3.56.1 Goals
-
+
3.56.2 Description
-
+
3.56.3 Usage
-
+
3.56.4 See also
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.57 trunk/Translations/Identity/Themes
-
+
3.57.1 Goals
-
+
3.57.2 Description
-
+
3.57.3 Usage
-
+
3.57.4 See also
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.58 trunk/Translations/Identity/Themes/Backgrounds
-
+
3.58.1 Goals
@@ -82,7 +82,7 @@ ul.toc {list-style: none}
-
+
3.58.2 Description
@@ -90,7 +90,7 @@ ul.toc {list-style: none}
-
+
3.58.3 Usage
@@ -98,18 +98,18 @@ ul.toc {list-style: none}
-
+
3.58.4 See also
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.59 trunk/Translations/Identity/Themes/Distro/Anaconda/Progress
-
+
3.59.1 Goals
@@ -84,7 +84,7 @@ languages and major releases of CentOS distribution.
-
+
3.59.2 Description
3.59.3 Usage
3.59.4 See also
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
3.60 trunk/Translations/Identity/Widgets
-
+
3.60.1 Goals
@@ -82,7 +82,7 @@ ul.toc {list-style: none}
-
+
3.60.2 Description
@@ -90,7 +90,7 @@ ul.toc {list-style: none}
-
+
3.60.3 Usage
@@ -98,11 +98,11 @@ ul.toc {list-style: none}
-
+
3.60.4 See also
-
@@ -111,12 +111,12 @@ ul.toc {list-style: none}
3.60 trunk/Translations/Identity/Widgets
+ 3.60 trunk/Translations/Identity/Widgets
-
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
-[ Up ]
-[ >> ]
+[ Up ]
+[ >> ]
-
-
+
[ < ]
-[ > ]
+[ < ]
+[ > ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
Index
-
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
[ << ]
[ Up ]
-[ >> ]
+[ >> ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
About This Document
@@ -165,7 +165,7 @@ ul.toc {list-style: none}
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
Footnotes
@@ -77,7 +77,7 @@ output of locale -a
command.
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]
Table of Contents
@@ -403,190 +403,188 @@ ul.toc {list-style: none}
-
-
-
-
[Top]
[Contents]
-[Index]
+[Index]
[ ? ]