diff --git a/Manuals/TODO b/Manuals/TODO new file mode 100644 index 0000000..50e49de --- /dev/null +++ b/Manuals/TODO @@ -0,0 +1,39 @@ +* Add breadcrumbs navigation using header path. Here we need to find a + way to de-compose h2 headers and create links, to the correct + documentation section, for each component inside the string (using / + as separator). Tip: look for customization inside texi2html source + code. + +* Fix default navigation menu. Make browsing section aware only, not + subsection, nor subsubsection. + +* Add the 'move' action to centos-art.sh script. This action should be + able to move one directory or file from one location to another + inside the repository in a way that all path related information to + the source location being moved to the target location be also + updated. For example, if you move trunk/Identity/DirSource to + trunk/Identity/DirTarget these paths need to be updated inside + documentation files. And not also inside, but outside too. So + + trunk/Manuals/en/Texinfo/Repository/trunk/Identity/DirSource + trunk/Manuals/es/Texinfo/Repository/trunk/Identity/DirSource + + whould change, automatically, to + + trunk/Manuals/en/Texinfo/Repository/trunk/Identity/DirTarget + trunk/Manuals/es/Texinfo/Repository/trunk/Identity/DirTarget + + and all references (e.g., @xref, @ref, @pxref, etc.) commands + inside the whole documentation should reflect the change too. + +* Add the 'remove' action to centos-art.sh script. This action should + be able to remove repository entries and their related information. + For example, if you remove the path: + + trunk/Identity/DirSource + + the following directories will be removed too: + + trunk/Manuals/$LANG/Texinfo/Repository/trunk/Identity/DirSource + trunk/Manuals/$LANG/Html/Repository/trunk-Identity-DirSource.html + diff --git a/Manuals/en/Html/Repository/repository.html b/Manuals/en/Html/Repository/repository.html index b855166..6f64921 100644 --- a/Manuals/en/Html/Repository/repository.html +++ b/Manuals/en/Html/Repository/repository.html @@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. --> - + - + - +
-3.8 trunk/Identity/Models/Tpl/Promo/Web | + |
[ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_100.html b/Manuals/en/Html/Repository/repository_100.html
index 795c043..41531f5 100644
--- a/Manuals/en/Html/Repository/repository_100.html
+++ b/Manuals/en/Html/Repository/repository_100.html
@@ -86,7 +86,7 @@ documentation entries. Some useful links are itemized below:
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_101.html b/Manuals/en/Html/Repository/repository_101.html
index 1a1688e..3949438 100644
--- a/Manuals/en/Html/Repository/repository_101.html
+++ b/Manuals/en/Html/Repository/repository_101.html
@@ -79,7 +79,7 @@ ul.toc {list-style: none}
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_102.html b/Manuals/en/Html/Repository/repository_102.html
index f9eae49..8cae57f 100644
--- a/Manuals/en/Html/Repository/repository_102.html
+++ b/Manuals/en/Html/Repository/repository_102.html
@@ -82,7 +82,7 @@ ul.toc {list-style: none}
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_103.html b/Manuals/en/Html/Repository/repository_103.html
index 378b3ac..c819b83 100644
--- a/Manuals/en/Html/Repository/repository_103.html
+++ b/Manuals/en/Html/Repository/repository_103.html
@@ -82,7 +82,7 @@ ul.toc {list-style: none}
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_104.html b/Manuals/en/Html/Repository/repository_104.html
index bcc8282..5f0779d 100644
--- a/Manuals/en/Html/Repository/repository_104.html
+++ b/Manuals/en/Html/Repository/repository_104.html
@@ -82,7 +82,7 @@ ul.toc {list-style: none}
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_105.html b/Manuals/en/Html/Repository/repository_105.html
index 8e47ab8..60e7bea 100644
--- a/Manuals/en/Html/Repository/repository_105.html
+++ b/Manuals/en/Html/Repository/repository_105.html
@@ -79,7 +79,7 @@ ul.toc {list-style: none}
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_106.html b/Manuals/en/Html/Repository/repository_106.html
index d86534d..47bdd0b 100644
--- a/Manuals/en/Html/Repository/repository_106.html
+++ b/Manuals/en/Html/Repository/repository_106.html
@@ -82,7 +82,7 @@ ul.toc {list-style: none}
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_107.html b/Manuals/en/Html/Repository/repository_107.html
index 077c2e9..b6c4129 100644
--- a/Manuals/en/Html/Repository/repository_107.html
+++ b/Manuals/en/Html/Repository/repository_107.html
@@ -165,7 +165,7 @@ Brand images in different dimensions and colors.
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_108.html b/Manuals/en/Html/Repository/repository_108.html
index b3e9617..114b14b 100644
--- a/Manuals/en/Html/Repository/repository_108.html
+++ b/Manuals/en/Html/Repository/repository_108.html
@@ -82,7 +82,7 @@ ul.toc {list-style: none}
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_109.html b/Manuals/en/Html/Repository/repository_109.html
index 73929b5..5989852 100644
--- a/Manuals/en/Html/Repository/repository_109.html
+++ b/Manuals/en/Html/Repository/repository_109.html
@@ -79,7 +79,7 @@ ul.toc {list-style: none}
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_11.html b/Manuals/en/Html/Repository/repository_11.html
index 4779c42..c89d84d 100644
--- a/Manuals/en/Html/Repository/repository_11.html
+++ b/Manuals/en/Html/Repository/repository_11.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
The `trunk/Identity/Themes/' directory exists to: -
In this location themes are organized in "Models" --to store common -information-- and "Motifs"--to store unique information. At -rendering time, both motifs and models are combined to produce the -final CentOS themes. CentOS themes can be tagged as "Default" or -"Alternative". CentOS themes are maintained by CentOS community. -
+3.16 trunk/Identity/Themes/Motifs | - | |
3.9 trunk/Identity/Themes/Models | - | |
3.53 trunk/Translations/Identity/Themes | + | |
3.7 trunk/Identity/Models/Img/Promo/Web |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_110.html b/Manuals/en/Html/Repository/repository_110.html
index a05e3a9..a0856a3 100644
--- a/Manuals/en/Html/Repository/repository_110.html
+++ b/Manuals/en/Html/Repository/repository_110.html
@@ -84,7 +84,7 @@ languages and major releases of CentOS distribution.
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
- This document was generated on September, 5 2010 using texi2html 1.76.
+ This document was generated on September, 5 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_111.html b/Manuals/en/Html/Repository/repository_111.html
index 0f26dc7..efb603d 100644
--- a/Manuals/en/Html/Repository/repository_111.html
+++ b/Manuals/en/Html/Repository/repository_111.html
@@ -81,7 +81,7 @@ documentation entry (see section trunk/Transl
diff --git a/Manuals/en/Html/Repository/repository_112.html b/Manuals/en/Html/Repository/repository_112.html
index 60ba342..cae1a7f 100644
--- a/Manuals/en/Html/Repository/repository_112.html
+++ b/Manuals/en/Html/Repository/repository_112.html
@@ -149,7 +149,7 @@ a sum of 18 images around.
diff --git a/Manuals/en/Html/Repository/repository_113.html b/Manuals/en/Html/Repository/repository_113.html
index 17f7e71..3d830c2 100644
--- a/Manuals/en/Html/Repository/repository_113.html
+++ b/Manuals/en/Html/Repository/repository_113.html
@@ -85,7 +85,7 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_114.html b/Manuals/en/Html/Repository/repository_114.html
index 727f270..7464cb7 100644
--- a/Manuals/en/Html/Repository/repository_114.html
+++ b/Manuals/en/Html/Repository/repository_114.html
@@ -201,7 +201,7 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_115.html b/Manuals/en/Html/Repository/repository_115.html
index 949d699..c2a3758 100644
--- a/Manuals/en/Html/Repository/repository_115.html
+++ b/Manuals/en/Html/Repository/repository_115.html
@@ -83,7 +83,7 @@ ul.toc {list-style: none}
diff --git a/Manuals/en/Html/Repository/repository_12.html b/Manuals/en/Html/Repository/repository_12.html
index 7bd5357..093d0db 100644
--- a/Manuals/en/Html/Repository/repository_12.html
+++ b/Manuals/en/Html/Repository/repository_12.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
Theme models let you modeling characteristics (e.g., dimensions, -translation markers, position of each element on the display area, -etc.) common to all themes. Theme models let you reduce the time -needed when propagating artistic motifs to different visual -manifestations. -
-Theme models serves as a central pool of design templates for themes -to use. This way you can produce themes with different artistic motifs -but same characteristics. -
Inside the framework location above, you find theme models organized -by name. You can add your own theme models to the structure by adding -a directory to the list. By default you have the `See section Default,' and `See section Alternative,' ready-to-use theme models. -
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_13.html b/Manuals/en/Html/Repository/repository_13.html
index 70fee40..f81d84d 100644
--- a/Manuals/en/Html/Repository/repository_13.html
+++ b/Manuals/en/Html/Repository/repository_13.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
The `trunk/Identity/Themes/' directory exists to: +
CentOS alternative theme models exist for people how want to use a -different visual style on their installations of CentOS distribution. -As the visual style is needed for a system already installed -components like Anaconda are not required inside alternative themes. -Inside alternative themes you find post-installation visual style only -(i.e. Backgrounds, Display Managers, Grub, etc.). CentOS alternative -themes are maintained by CentOS Community. -
In this location themes are organized in "Models" --to store common +information-- and "Motifs"--to store unique information. At +rendering time, both motifs and models are combined to produce the +final CentOS themes. CentOS themes can be tagged as "Default" or +"Alternative". CentOS themes are maintained by CentOS community. +
3.18 trunk/Identity/Themes/Motifs | + | |
3.11 trunk/Identity/Themes/Models | + | |
3.55 trunk/Translations/Identity/Themes | + |
[ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_14.html b/Manuals/en/Html/Repository/repository_14.html
index 9ebf0c8..03a921d 100644
--- a/Manuals/en/Html/Repository/repository_14.html
+++ b/Manuals/en/Html/Repository/repository_14.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
This location stores CentOS default theme model. The CentOS default -theme model is used in all visual manifestations of CentOS Project's -corporate visual identity (e.g., distributions, web sites, promotion, -etc.). -
+Theme models let you modeling characteristics (e.g., dimensions, +translation markers, position of each element on the display area, +etc.) common to all themes. Theme models let you reduce the time +needed when propagating artistic motifs to different visual +manifestations. +
+Theme models serves as a central pool of design templates for themes +to use. This way you can produce themes with different artistic motifs +but same characteristics. +
Changing CentOS default theme is not very convenient because that -affects the "recognition" of CentOS Project. Nevertheless, we are -interested on seeing your art work propositions. Specially if your -art work is an improvement to the base idea behind CentOS default -theme (Modern, squares and circles flowing up.). -
-If you are not happy with CentOS default theme, you can look inside -CentOS alternative themes and download the one you are interested in. -If you are not happy with any of the CentOS alternative themes -available, then go and design your own CentOS alternative theme as -described in See section Theme Motifs. +
Inside the framework location above, you find theme models organized +by name. You can add your own theme models to the structure by adding +a directory to the list. By default you have the `See section Default,' and `See section Alternative,' ready-to-use theme models.
@@ -116,11 +117,11 @@ described in See section Theme Motifs.
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_15.html b/Manuals/en/Html/Repository/repository_15.html
index b7e3b33..226c5da 100644
--- a/Manuals/en/Html/Repository/repository_15.html
+++ b/Manuals/en/Html/Repository/repository_15.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
It applies to all major releases of CentOS distribution. +
CentOS alternative theme models exist for people how want to use a +different visual style on their installations of CentOS distribution. +As the visual style is needed for a system already installed +components like Anaconda are not required inside alternative themes. +Inside alternative themes you find post-installation visual style only +(i.e. Backgrounds, Display Managers, Grub, etc.). CentOS alternative +themes are maintained by CentOS Community.
-Sometimes, specific visual manifestations are formed by common -components which have internal differences. That is the case of CentOS -distribution visual manifestation. -
-Since a visual style point of view, the CentOS distributions share -common artwork components like Anaconda --to cover the CentOS -distribution installation--, BootUp --to cover the CentOS -distribution start up--, and Backgrounds --to cover the CentOS -distribution desktop--. Now, since a technical point of view, those -common artwork components are made of software improved constantly. -So, we need to find a way to keep one unique name and one unique -visual style in artwork components that have internal difference and -also remark internal difference as well. -
-- -Important
Remarking the CentOS release schema inside each -major release of CentOS distribution --or similar visual -manifestation-- takes high attention inside The CentOS Project -corporate visual identity. It should be very clear for people which -major release of CentOS distribution they are using. -
In order to remark the CentOS release schema, the CentOS Artwork SIG -uses a release-specific brand design named "The CentOS Release -Brand". The CentOS release brand is compossed by the CentOS logotype -and the CentOS major release number (as specified in CentOS -release schema definition). In this solution, the CentOS release brand -is set inside all release-specific artworks (e.g., distribution, -installation media, etc.) in remarkable way. The CentOS release -brand is the design component that lets us remark the CentOS release -schema inside the monolithic corporate visual identity structure we -propose to use. -
- - -Other way we've been using to remark CentOS release schema is -applying one unique theme for each major release of CentOS -distribution. That is, if we have 4 major releases of CentOS -distribution, we need to provide 4 different themes to cover each -CentOS distribution available. -
-Inside CentOS Artwork Repository, you can create many themes and that -is very convenient. But using one unique theme for each major -release of CentOS distribution would bring visual isolation among -distributions, websites and promotion visual manifestations. If the -CentOS project would maintain just one CentOS distribution (and many -experienced graphic designers ready to create beautiful artworks) this -model would be nice. Indeed, this model looks quite similar to that -one used by Fedora project, doesn't it. But no, the CentOS project -maintains near to 4 major releases of CentOS distribution in parallel, -and that fact makes a huge difference since the corporate visual -identity point of view. -
-If we use one unique theme for each major release of CentOS -distribution, which one of those themes, does we use to cover other -CentOS visual manifestations, like websites and promotion stuff? -
-In whatever case you choose some release-specific distribution user -will be visually isolated from other CentOS visual manifestations like -websites and promotion stuff, even if the CentOS brand is present in -all visual manifestations. In such a case, probably, users will end up -asking themselves, why my CentOS distribution has this design and the -CentOS website another one? Isn't them on the same project? With luck -the CentOS brand will exonerate user form visual isolation. -
- -[ < ] | -[ > ] | +|||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_16.html b/Manuals/en/Html/Repository/repository_16.html
index ae9c823..8c98c20 100644
--- a/Manuals/en/Html/Repository/repository_16.html
+++ b/Manuals/en/Html/Repository/repository_16.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
This location stores CentOS default theme model. The CentOS default +theme model is used in all visual manifestations of CentOS Project's +corporate visual identity (e.g., distributions, web sites, promotion, +etc.). +
- +Changing CentOS default theme is not very convenient because that +affects the "recognition" of CentOS Project. Nevertheless, we are +interested on seeing your art work propositions. Specially if your +art work is an improvement to the base idea behind CentOS default +theme (Modern, squares and circles flowing up.). +
+If you are not happy with CentOS default theme, you can look inside +CentOS alternative themes and download the one you are interested in. +If you are not happy with any of the CentOS alternative themes +available, then go and design your own CentOS alternative theme as +described in See section Theme Motifs. +
- +[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_17.html b/Manuals/en/Html/Repository/repository_17.html
index b4d62b8..3f06507 100644
--- a/Manuals/en/Html/Repository/repository_17.html
+++ b/Manuals/en/Html/Repository/repository_17.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
It applies to all tangible and non tangible items CentOS uses to -promote its existence. Clothes, posters, installation media, -stationery, release countdown images, banners, stickers, are all -examples of promotion designs. +
It applies to all major releases of CentOS distribution.
-Sometimes, specific visual manifestations are formed by common +components which have internal differences. That is the case of CentOS +distribution visual manifestation. +
+Since a visual style point of view, the CentOS distributions share +common artwork components like Anaconda --to cover the CentOS +distribution installation--, BootUp --to cover the CentOS +distribution start up--, and Backgrounds --to cover the CentOS +distribution desktop--. Now, since a technical point of view, those +common artwork components are made of software improved constantly. +So, we need to find a way to keep one unique name and one unique +visual style in artwork components that have internal difference and +also remark internal difference as well. +
++ +Important
Remarking the CentOS release schema inside each +major release of CentOS distribution --or similar visual +manifestation-- takes high attention inside The CentOS Project +corporate visual identity. It should be very clear for people which +major release of CentOS distribution they are using. +
In order to remark the CentOS release schema, the CentOS Artwork SIG +uses a release-specific brand design named "The CentOS Release +Brand". The CentOS release brand is compossed by the CentOS logotype +and the CentOS major release number (as specified in CentOS +release schema definition). In this solution, the CentOS release brand +is set inside all release-specific artworks (e.g., distribution, +installation media, etc.) in remarkable way. The CentOS release +brand is the design component that lets us remark the CentOS release +schema inside the monolithic corporate visual identity structure we +propose to use. +
+ + +Other way we've been using to remark CentOS release schema is +applying one unique theme for each major release of CentOS +distribution. That is, if we have 4 major releases of CentOS +distribution, we need to provide 4 different themes to cover each +CentOS distribution available. +
+Inside CentOS Artwork Repository, you can create many themes and that +is very convenient. But using one unique theme for each major +release of CentOS distribution would bring visual isolation among +distributions, websites and promotion visual manifestations. If the +CentOS project would maintain just one CentOS distribution (and many +experienced graphic designers ready to create beautiful artworks) this +model would be nice. Indeed, this model looks quite similar to that +one used by Fedora project, doesn't it. But no, the CentOS project +maintains near to 4 major releases of CentOS distribution in parallel, +and that fact makes a huge difference since the corporate visual +identity point of view. +
+If we use one unique theme for each major release of CentOS +distribution, which one of those themes, does we use to cover other +CentOS visual manifestations, like websites and promotion stuff? +
+In whatever case you choose some release-specific distribution user +will be visually isolated from other CentOS visual manifestations like +websites and promotion stuff, even if the CentOS brand is present in +all visual manifestations. In such a case, probably, users will end up +asking themselves, why my CentOS distribution has this design and the +CentOS website another one? Isn't them on the same project? With luck +the CentOS brand will exonerate user form visual isolation. +
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_18.html b/Manuals/en/Html/Repository/repository_18.html
index fa10063..fcea280 100644
--- a/Manuals/en/Html/Repository/repository_18.html
+++ b/Manuals/en/Html/Repository/repository_18.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
It applies to all web applications CentOS uses to handle its needs -(Ex. Portals, Wikis, Forums, Blogs, Bug Tracker). Anything involving -HTML standards should be consider here. -
-
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_19.html b/Manuals/en/Html/Repository/repository_19.html
index 019efac..ae7633d 100644
--- a/Manuals/en/Html/Repository/repository_19.html
+++ b/Manuals/en/Html/Repository/repository_19.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
The `trunk/Identity/Themes/Motifs' directory exists to: -
The artistic motif of theme is a graphic design component that -provides theme's visual style, it is used as pattern to connect all -visual manifestations inside one unique theme. -
-Artistic motifs are based on conceptual ideas. Conceptual ideas bring -the motivation, they are fuel for the engines of human imagination. -Good conceptual ideas may produce good motivation to produce almost -anything, and art works don't escape from it. -
-CentOS like trees, has roots, trunk, branches, leaves and flowers. Day -by day they work together in freedom, ruled by the laws of nature and -open standards, to show the beauty of its existence. -
Modern, squares and circles flowing up. -
If you have new conceptual ideas for CentOS, then you can say that you -want to create a new artistic motif for CentOS. To create a new -artistic motif you need to create a directory under -`Identity/Themes/Motifs/' using a name coherent with your -conceptual idea. That name will be your artistic motif's name. If -possible, when creating new conceptual ideas for CentOS, think about -what CentOS means for you, what does it makes you feel, take your -time, think deep, and share; you can improve the idea as time goes on. -
-Once you have defined a name for your theme, you need to create the -motif structure of your theme. The motif structure is the basic -direcotry structure you'll use to work your ideas. Here is where you -organize your graphic design projects. -
-To add a new motif structure to CentOS Artwork Repository, you need to
-use the centos-art
command line in the
-`Identity/Themes/Motifs/' directory as described below:
-
centos-art add --motif=ThemeName - |
The previous command will create the motif's basic structure for you.
-The basic structure produced by centos-art
command is
-illustrated in the following figure:
-
trunk/Identity/Themes/Motifs/$ThemeName/ -|-- Backgrounds -| |-- Img -| `-- Tpl -|-- Info -| |-- Img -| `-- Tpl -|-- Palettes -`-- Screenshots - |
When designing artistic motifs for CentOS, consider the following -recommendations: +
It applies to all tangible and non tangible items CentOS uses to +promote its existence. Clothes, posters, installation media, +stationery, release countdown images, banners, stickers, are all +examples of promotion designs.
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_2.html b/Manuals/en/Html/Repository/repository_2.html
index e3232f3..befadbd 100644
--- a/Manuals/en/Html/Repository/repository_2.html
+++ b/Manuals/en/Html/Repository/repository_2.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
-
+
Inside motif's `Backgrounds/' directory you can create vectorial -designs using Inkscape and background images using Gimp. Later, you -can export background images as `.png' and load them in your -vectorial design project using Inkscape's import feautre. -
-You may need to repeat this technic for different screen resoluions. -In that case you need to create one file for each screen resolution -and do the appropriate linking inside .svg to .png files. For example -if you need to produce background images in 800x600 you need to create -the following file: -
-xcf/800x600.xcf - |
to produce the background image: -
-img/800x600-bg.png - |
which is loaded in: -
-svg/800x600.svg - |
to produce the final background image: -
-img/800x600.png - |
The `img/800x600.png' background image is produced automatically -by means of rendering scripts. -
-In other cases, like Anaconda's, it is possible that you need to make -some variations to one background image that don't want to appear on -regular background images of the same resolution. In this case you -need to create a new and specific background image for that art -component. For example, if you need to produce the background image -used by Anconda (800x600) art works you create the file: -
-xcf/800x600-anaconda.xcf - |
to produce the background image: -
-img/800x600-anaconda-bg.png - |
which is loaded in: -
-svg/800x600-anaconda.svg - |
to produce the file: -
-img/800x600-anaconda.png - |
The 800x600-anaconda.png file is used by all Anaconda art works -sharing a common 800x600 screen resolution (e.g., Header, Progress, -Splash, Firstboot, etc.). The Anaconda Prompt is indexed to 16 colors -and 640x480 pixels so you need to create a 640x480 background image -for it, and take the color limitation into account when designing it. -
-Background images without artistic motif are generally used as based -to build the Background images that do contain the theme's artistic -motif. -
-Background images are linked (using Inkscape's import feature) -inside almost all theme art works. This structure let you make -centralized changes on the visual identity and propagate them quickly -to other areas. -
-In this structure you design background images for different screen -resolutions based on theme's artistic motif. -
-You may create different artistic motifs propositions based -on the same conceptual idea. The conceptual idea is what defines a -theme. Artistic motifs are interpretations of that idea. -
-Inside this directory artistic motifs are organized by name (e.g., -TreeFlower, Modern, etc.). -
-Inside each motif directories represent just one unique artistic motif. -
-The artistic motif is graphic design used as common pattern to connect -all visual manifestations inside one unique theme. The artistic motif -is based on a conceptual idea. Artistic motifs provide visual style -to themes. -
-Designing artistic motifs is for anyone interested in creating -beautiful themes for CentOS. When building a theme for CentOS, the -first design you need to define is the artistic motif. +
It applies to all web applications CentOS uses to handle its needs +(Ex. Portals, Wikis, Forums, Blogs, Bug Tracker). Anything involving +HTML standards should be consider here.
+Inside CentOS Artwork Repository, theme visual styles (Motifs) and
-theme visual structures (Models) are two different working lines.
-When you design an artistic motif for CentOS you concentrate on its
-visual style, and eventualy, use the centos-art
command line
-interface to render the visual style, you are currently producing,
-against an already-made theme model in order to produce the final
-result. Final images are stored under the motif's name directory
-using the model directory structure as reference.
-
The artistic motif base structure is used by centos-art
to
-produce images automatically. This section describes each directory of
-CentOS artistic motif base structure.
-
The motif's `Backgrounds/' directory is probably the motif's core -component. Inside motif's `Backgrounds/' directory you produce -background images used by almost all theme models (e.g., Distribution, -Websites, Promotion, etc.). The motif's `Backgrounds/' directory -can contain subdirectories to help you organize the design process. -
+[ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_21.html b/Manuals/en/Html/Repository/repository_21.html
index 5459c50..3190e8c 100644
--- a/Manuals/en/Html/Repository/repository_21.html
+++ b/Manuals/en/Html/Repository/repository_21.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
The `trunk/Identity/Themes/Motifs' directory exists to: +
The artistic motif of theme is a graphic design component that +provides theme's visual style, it is used as pattern to connect all +visual manifestations inside one unique theme. +
+Artistic motifs are based on conceptual ideas. Conceptual ideas bring +the motivation, they are fuel for the engines of human imagination. +Good conceptual ideas may produce good motivation to produce almost +anything, and art works don't escape from it. +
+CentOS like trees, has roots, trunk, branches, leaves and flowers. Day +by day they work together in freedom, ruled by the laws of nature and +open standards, to show the beauty of its existence. +
Modern, squares and circles flowing up. +
If you have new conceptual ideas for CentOS, then you can say that you +want to create a new artistic motif for CentOS. To create a new +artistic motif you need to create a directory under +`Identity/Themes/Motifs/' using a name coherent with your +conceptual idea. That name will be your artistic motif's name. If +possible, when creating new conceptual ideas for CentOS, think about +what CentOS means for you, what does it makes you feel, take your +time, think deep, and share; you can improve the idea as time goes on. +
+Once you have defined a name for your theme, you need to create the +motif structure of your theme. The motif structure is the basic +direcotry structure you'll use to work your ideas. Here is where you +organize your graphic design projects. +
+To add a new motif structure to CentOS Artwork Repository, you need to
+use the centos-art
command line in the
+`Identity/Themes/Motifs/' directory as described below:
+
centos-art add --motif=ThemeName + |
The previous command will create the motif's basic structure for you.
+The basic structure produced by centos-art
command is
+illustrated in the following figure:
+
trunk/Identity/Themes/Motifs/$ThemeName/ +|-- Backgrounds +| |-- Img +| `-- Tpl +|-- Info +| |-- Img +| `-- Tpl +|-- Palettes +`-- Screenshots + |
In this directory is where you store all background images (e.g., -.png, .jpg, .xpm, etc.). This directory is required by -`centos-art' command line interface. +
When designing artistic motifs for CentOS, consider the following +recommendations:
+[ < ] | [ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_22.html b/Manuals/en/Html/Repository/repository_22.html
index 0116402..c9654d9 100644
--- a/Manuals/en/Html/Repository/repository_22.html
+++ b/Manuals/en/Html/Repository/repository_22.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
Inside motif's `Backgrounds/' directory you can create vectorial +designs using Inkscape and background images using Gimp. Later, you +can export background images as `.png' and load them in your +vectorial design project using Inkscape's import feautre. +
+You may need to repeat this technic for different screen resoluions. +In that case you need to create one file for each screen resolution +and do the appropriate linking inside .svg to .png files. For example +if you need to produce background images in 800x600 you need to create +the following file: +
+xcf/800x600.xcf + |
to produce the background image: +
+img/800x600-bg.png + |
which is loaded in: +
+svg/800x600.svg + |
to produce the final background image: +
+img/800x600.png + |
The `img/800x600.png' background image is produced automatically +by means of rendering scripts. +
+In other cases, like Anaconda's, it is possible that you need to make +some variations to one background image that don't want to appear on +regular background images of the same resolution. In this case you +need to create a new and specific background image for that art +component. For example, if you need to produce the background image +used by Anconda (800x600) art works you create the file: +
+xcf/800x600-anaconda.xcf + |
to produce the background image: +
+img/800x600-anaconda-bg.png + |
which is loaded in: +
+svg/800x600-anaconda.svg + |
to produce the file: +
+img/800x600-anaconda.png + |
The 800x600-anaconda.png file is used by all Anaconda art works +sharing a common 800x600 screen resolution (e.g., Header, Progress, +Splash, Firstboot, etc.). The Anaconda Prompt is indexed to 16 colors +and 640x480 pixels so you need to create a 640x480 background image +for it, and take the color limitation into account when designing it. +
+Background images without artistic motif are generally used as based +to build the Background images that do contain the theme's artistic +motif. +
+Background images are linked (using Inkscape's import feature) +inside almost all theme art works. This structure let you make +centralized changes on the visual identity and propagate them quickly +to other areas. +
+In this structure you design background images for different screen +resolutions based on theme's artistic motif. +
+You may create different artistic motifs propositions based +on the same conceptual idea. The conceptual idea is what defines a +theme. Artistic motifs are interpretations of that idea. +
+Inside this directory artistic motifs are organized by name (e.g., +TreeFlower, Modern, etc.). +
+Inside each motif directories represent just one unique artistic motif. +
+The artistic motif is graphic design used as common pattern to connect +all visual manifestations inside one unique theme. The artistic motif +is based on a conceptual idea. Artistic motifs provide visual style +to themes. +
+Designing artistic motifs is for anyone interested in creating +beautiful themes for CentOS. When building a theme for CentOS, the +first design you need to define is the artistic motif. +
+ +Inside CentOS Artwork Repository, theme visual styles (Motifs) and
+theme visual structures (Models) are two different working lines.
+When you design an artistic motif for CentOS you concentrate on its
+visual style, and eventualy, use the centos-art
command line
+interface to render the visual style, you are currently producing,
+against an already-made theme model in order to produce the final
+result. Final images are stored under the motif's name directory
+using the model directory structure as reference.
+
The artistic motif base structure is used by centos-art
to
+produce images automatically. This section describes each directory of
+CentOS artistic motif base structure.
+
In this directory is where you store all the scalable vector graphics -(e.g., .svg) files. This directory is required by `centos-art' -command line interface. +
The motif's `Backgrounds/' directory is probably the motif's core +component. Inside motif's `Backgrounds/' directory you produce +background images used by almost all theme models (e.g., Distribution, +Websites, Promotion, etc.). The motif's `Backgrounds/' directory +can contain subdirectories to help you organize the design process.
[ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_23.html b/Manuals/en/Html/Repository/repository_23.html
index e1e38d8..755424d 100644
--- a/Manuals/en/Html/Repository/repository_23.html
+++ b/Manuals/en/Html/Repository/repository_23.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
In this directory is where you store Gimp's project files (e.g, .xcf). -This directory is not required by `centos-art' command line -interface. If you can create a beautiful background images using -scalable vector graphics only, then there is no need to use the -`Xcf/' directory to store Gimp's background projects. Of course, -you can merge Gimp's power with Inkscape's power to produce images -based on them. In this last case you need the `Xcf/' directory. +
In this directory is where you store all background images (e.g., +.png, .jpg, .xpm, etc.). This directory is required by +`centos-art' command line interface.
@@ -110,17 +101,18 @@ based on them. In this last case you need the `Xcf/' directory. +[ < ] | [ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_24.html b/Manuals/en/Html/Repository/repository_24.html
index afac589..4796ca0 100644
--- a/Manuals/en/Html/Repository/repository_24.html
+++ b/Manuals/en/Html/Repository/repository_24.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
To render Anaconda progress slide images using the Modern's artistic -motif design, the Default theme model, and available translation files -(see section trunk/Translations/Identity/Themes/Distro/Anaconda/Progress); -use the following commands: +
In this directory is where you store all the scalable vector graphics +(e.g., .svg) files. This directory is required by `centos-art' +command line interface.
-cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ -centos-art render --identity - |
The above command will create the following structure: -
-trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress -|-- 3 -| |-- en -| | |-- 01-welcome.png -| | |-- 02-donate.png -| | `-- 03-yum.png -| `-- es -| |-- 01-welcome.png -| |-- 02-donate.png -| `-- 03-yum.png -|-- 4 -| |-- en -| | |-- 01-welcome.png -| | |-- 02-donate.png -| | `-- 03-yum.png -| `-- es -| |-- 01-welcome.png -| |-- 02-donate.png -| `-- 03-yum.png -`-- 5 - |-- en - | |-- 01-welcome.png - | |-- 02-donate.png - | `-- 03-yum.png - `-- es - |-- 01-welcome.png - |-- 02-donate.png - `-- 03-yum.png - |
[ < ] | [ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_25.html b/Manuals/en/Html/Repository/repository_25.html
index 95dc2e6..a1daa60 100644
--- a/Manuals/en/Html/Repository/repository_25.html
+++ b/Manuals/en/Html/Repository/repository_25.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
Here is where graphic designers define theme palettes for -color-limited art works. Theme palettes contain the color information -that rendering functions need, in order to produce images with color -limitations. Theme palettes contain theme's unique color information. +
In this directory is where you store Gimp's project files (e.g, .xcf). +This directory is not required by `centos-art' command line +interface. If you can create a beautiful background images using +scalable vector graphics only, then there is no need to use the +`Xcf/' directory to store Gimp's background projects. Of course, +you can merge Gimp's power with Inkscape's power to produce images +based on them. In this last case you need the `Xcf/' directory.
@@ -108,11 +116,11 @@ limitations. Theme palettes contain theme's unique color information.
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_26.html b/Manuals/en/Html/Repository/repository_26.html
index c5aeea5..8b506f8 100644
--- a/Manuals/en/Html/Repository/repository_26.html
+++ b/Manuals/en/Html/Repository/repository_26.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
To render Anaconda progress slide images using the Modern's artistic +motif design, the Default theme model, and available 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 + |
The above command will create the following structure: +
+trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress +|-- 3 +| |-- en +| | |-- 01-welcome.png +| | |-- 02-donate.png +| | `-- 03-yum.png +| `-- es +| |-- 01-welcome.png +| |-- 02-donate.png +| `-- 03-yum.png +|-- 4 +| |-- en +| | |-- 01-welcome.png +| | |-- 02-donate.png +| | `-- 03-yum.png +| `-- es +| |-- 01-welcome.png +| |-- 02-donate.png +| `-- 03-yum.png +`-- 5 + |-- en + | |-- 01-welcome.png + | |-- 02-donate.png + | `-- 03-yum.png + `-- es + |-- 01-welcome.png + |-- 02-donate.png + `-- 03-yum.png + |
[ < ] | [ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_27.html b/Manuals/en/Html/Repository/repository_27.html
index 6d0b973..8cabaa8 100644
--- a/Manuals/en/Html/Repository/repository_27.html
+++ b/Manuals/en/Html/Repository/repository_27.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
Here is where graphic designers define theme palettes for +color-limited art works. Theme palettes contain the color information +that rendering functions need, in order to produce images with color +limitations. Theme palettes contain theme's unique color information. +
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_28.html b/Manuals/en/Html/Repository/repository_28.html
index 599d46d..245d2c9 100644
--- a/Manuals/en/Html/Repository/repository_28.html
+++ b/Manuals/en/Html/Repository/repository_28.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
Use this command to read directory documentation specified in -`path/to/dir'. -
-Use this command to read file documentation as specified by -`path/to/dir/filename' combination. -
-Use this command to edit directory documentation as specified in -`path/to/dir'. -
-Use this command to edit file documentation as specified in -`path/to/dir/filename' combination. -
-Use this command to update documentation output files. -
-Use this command to remove directory documentation as specified in -`path/to/dir'. -
-- -Caution
When directory documentation is removed all -documentation under it is also removed. -
- -Tip
To recover from directory documentation lost, try the -following command (before commit local changes up to central -repository): -
svn revert path/to/dir --recursive -
Use this command to remove file documentation as specified in -`path/to/dir/filename' combination. -
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_29.html b/Manuals/en/Html/Repository/repository_29.html
index 7ede4c8..d17066e 100644
--- a/Manuals/en/Html/Repository/repository_29.html
+++ b/Manuals/en/Html/Repository/repository_29.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
The `trunk/Scripts' directory exists to: -
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_3.html b/Manuals/en/Html/Repository/repository_3.html
index 2aca25a..ee6923e 100644
--- a/Manuals/en/Html/Repository/repository_3.html
+++ b/Manuals/en/Html/Repository/repository_3.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
-
+
The `trunk/Scripts/Bash' directory exists to organize the
-"trunk" development line of centos-art.sh
automation
-script. The centos-art.sh
script standardize frequent tasks
-inside your working copy of CentOS Artwork Repository.
-
The best way to understand centos-art.sh
automation script
-is studying its source code. The centos-art.sh
script is
-splited in several configuration and function files which are loaded
-when the centos-art.sh
script is executed. This section
-describes the order in which centos-art.sh
loads its
-configuration and function files.
-
When you type the centos-art
command in your terminal, the
-operating system trys to execute that command. In order to execute the
-command, the operating system needs to know where it is, so the
-operating system uses the PATH environment variable to look for
-that command's location. If your system was prepared to use CentOS
-Artwork Repository correctly (see usage section above), you should
-have a symbolic link inside `~/bin/' directory that points to the
-centos-art.sh
script file. As `~/bin/' directory is, by
-default, inside PATH environment variable, the execution of
-centos-art
command runs the `centos-art.sh' script.
-
When centos-art.sh
script is executed, the first it does is
-execute the `trunk/Scripts/Bash/initFunctions.sh' file to
-initialize gettext
variables and all function scripts inside
-`trunk/Scripts/Bash/Functions' directory.
-
Once gettext
variables and all function scripts have been
-initialized, the centos-art.sh
script initializes its
-environment variables using the cli_getVariables
function.
-At this point the centos-art.sh
script calls the
-cli_getActions
function from cli_getVariables
-function's bottom.
-
The cli_getActions
function defines which actions the
-centos-art.sh
script is able to perform. Inside
-cli_getActions
function, actions are defined combining
-positional arguments and function calls.
-
+------------------------------------------------------------------+ -| [centos@host]$ centos-art action 'path/to/dir' --option='value' | -+------------------------------------------------------------------+ -| ~/bin/centos-art --> ~/artwork/trunk/Scripts/Bash/centos-art.sh | -+---v-----------------------------------------v--------------------+ - | centos-art.sh | - +---v---------------------------------v---+ - . | initFunctions.sh | . - . +---------------------------------+ . - . | cli_getVariables $@ | . - . +---v-------------------------v---+ . - . . | cli_getActions | . . - . . +---v-----------------v---+ . . - . . . | function call 1 | . . . - . . . | function call 2 | . . . - . . . | function call n | . . . - . . . +-----------------+ . . . - . . ........................... . . - . ................................... . - ........................................... --
Figure 3.1: The centos-art.sh
initialization environment.
-
-
The identity matching list is used by identity rendering functions to -define the relation between translation files and identity design -templates. See section trunk/Scripts/Bash/Functions/Config/cli_getIdentityMatchinglist.sh, for more information. -
- - -To add new features inside centos-art.sh
script, you need to
-set positional arguments and function calls inside
-cli_getActions
function for the new function or functions
-required by the new feature you want to add.
-
centos-art
`check' action This feature is supported through the following command: -
This command verifies paths, symbolic links, installed packages and
-everything your workstation needs in order to run the
-centos-art
command correctly.
+
Use this command to read directory documentation specified in +`path/to/dir'.
-Warning
If this is the first time you run -
centos-art
command, the appropriate way to execute check -action is not using thecentos-art
command, but the absolute -path tocentos-art.sh
script instead: -~/artwork/trunk/Scripts/Bash/centos-art.sh check -
centos-art
`search' action This feature is not supported yet. -
-Use this command to find directories and files that match exactly the -posix-regular expression set in `pattern' as in `^pattern$'. +
Use this command to read file documentation as specified by +`path/to/dir/filename' combination.
Use this command to search repository entries that match pattern1 -or patter2 or patternN as in -`'^.*(pattern1|pattern2|patternN).*$''. +
Use this command to edit directory documentation as specified in +`path/to/dir'.
Use this command to search repository entries that match -`path/to/dir1' or `path/to/dir2', or -`path/to/dirN' as in -`^.*(path/to/dir1|path/to/dir2|path/to/dirN).*$''. +
Use this command to edit file documentation as specified in +`path/to/dir/filename' combination.
centos-art
`path' action This feature is not supported yet. +
Use this command to update documentation output files.
-centos-art
`locale-art' action This feature is not supported yet. -
-centos-art
`license' action Use this command to remove directory documentation as specified in +`path/to/dir'. +
++ +Caution
When directory documentation is removed all +documentation under it is also removed. +
-Tip
To recover from directory documentation lost, try the +following command (before commit local changes up to central +repository): +
svn revert path/to/dir --recursive +
This feature is supported through the following command: -
-Use this command to see a brief description of centos-art
-command its copyright and its license notes.
+
Use this command to remove file documentation as specified in +`path/to/dir/filename' combination.
3.28 trunk/Scripts/Bash/Config | - | |
3.31 trunk/Scripts/Bash/Functions | - | |
3.43 trunk/Scripts/Bash/Locale | - | |
3.26 trunk/Scripts | - |
[ < ] | -[ > ] | +|||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_31.html b/Manuals/en/Html/Repository/repository_31.html
index 4315d2d..692c8d3 100644
--- a/Manuals/en/Html/Repository/repository_31.html
+++ b/Manuals/en/Html/Repository/repository_31.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
The `trunk/Scripts/Bash/Config' directory exists to oraganize -pre-rendering configuration scripts. +
The `trunk/Scripts' directory exists to:
+Pre-rendering configuration scripts let you customize the way
-centos-art.sh
script renders identity and translation
-repository entries. Pre-rendering configuration scripts are
-`render.conf.sh' files with loadConfiguration
function
-definition inside.
-
There is one `render.conf.sh' file for each pre-rendering -configuration entry. Pre-rendering configuration entries can be based -both on identity and translation repository entires. Pre-rendering -configuration entries are required for each identity entry, but not -for translation entries. -
- - -Inside CentOS Artwork Repository, we consider directories under -`trunk/Identity' as identity entries. Identity entries can be -image-based or text-based. When you render image-based identity -entries you need to use image-based pre-rendering configuration -scripts. Likewise, when you render text-based identity entries you -need to use text-based pre-rendering configuration scripts. -
-Inside both image-based and text-based identity pre-rendering
-configuration scripts, we use the `ACTIONS' array variable to
-define the way centos-art.sh
script performs identity
-rendering. The first entry inside `ACTIONS' array variable (i.e.,
-`ACTIONS[0]') is reserved to define the primary rendering action
-(i.e, `renderImage' or `renderText'). Further entries
-inside `ACTIONS' (i.e., `ACTIONS[1]', `ACTIONS[2]',
-etc.) are used to define identity post-rendering actions.
-
Inside identity pre-rendering configuration scripts, image-based -pre-rendering configuration scripts look like the following: -
-#!/bin/bash - -function loadConfiguration { - - # Define post-rendering actions. An empty value means that no - # post-rendering action is applied. - ACTIONS[0]='renderImage' - ACTIONS[1]='renderFormats: tif xpm pdf ppm' - -} --
Inside identity pre-rendering configuration scripts, text-based -pre-rendering configuration scripts look like the following: -
-#!/bin/bash - -function loadConfiguration { - - # Define post-rendering actions. An empty value means that no - # post-rendering action is applied. - ACTIONS[0]='renderText' - ACTIONS[1]='formatText: --width=70 --uniform-spacing' -} --
When using identity pre-rendering configuration scripts, you can -extend both image-based and text-based pre-rendering configuration -scripts using image-based and text-based post-rendering actions, -respectively. -
+ +Translation pre-rendering configuration scripts take precedence before -default translation rendering action. Translation pre-rendering -actions are useful when default translation rendering action do not -fit itself to translation entry rendering requirements. -
- +Use the following commands to administer both identity and translation -pre-rendering configuration scripts: -
-Use this command to create `path/to/dir' related pre-rendering -configuration script. -
-Use this command to edit `path/to/dir' related pre-rendering -configuration script. -
-Use this command to read `path/to/dir' related pre-rendering -configuration script. -
-Use this command to remove `path/to/dir' related pre-rendering -configuration script. -
-In the commands above, `path/to/dir' refers to one renderable -directory path under `trunk/Identity' or -`trunk/Translations' structures only. -
- +3.29 trunk/Scripts/Bash/Config/Identity | - | |
3.30 trunk/Scripts/Bash/Config/Translations | - | |
3.27 trunk/Scripts/Bash | - |
[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_32.html b/Manuals/en/Html/Repository/repository_32.html
index 10e3b7c..a217cb1 100644
--- a/Manuals/en/Html/Repository/repository_32.html
+++ b/Manuals/en/Html/Repository/repository_32.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
The `trunk/Scripts/Bash' directory exists to organize the
+"trunk" development line of centos-art.sh
automation
+script. The centos-art.sh
script standardize frequent tasks
+inside your working copy of CentOS Artwork Repository.
+
The best way to understand centos-art.sh
automation script
+is studying its source code. The centos-art.sh
script is
+splited in several configuration and function files which are loaded
+when the centos-art.sh
script is executed. This section
+describes the order in which centos-art.sh
loads its
+configuration and function files.
+
When you type the centos-art
command in your terminal, the
+operating system trys to execute that command. In order to execute the
+command, the operating system needs to know where it is, so the
+operating system uses the PATH environment variable to look for
+that command's location. If your system was prepared to use CentOS
+Artwork Repository correctly (see usage section above), you should
+have a symbolic link inside `~/bin/' directory that points to the
+centos-art.sh
script file. As `~/bin/' directory is, by
+default, inside PATH environment variable, the execution of
+centos-art
command runs the `centos-art.sh' script.
+
When centos-art.sh
script is executed, the first it does is
+execute the `trunk/Scripts/Bash/initFunctions.sh' file to
+initialize gettext
variables and all function scripts inside
+`trunk/Scripts/Bash/Functions' directory.
+
Once gettext
variables and all function scripts have been
+initialized, the centos-art.sh
script initializes its
+environment variables using the cli_getVariables
function.
+At this point the centos-art.sh
script calls the
+cli_getActions
function from cli_getVariables
+function's bottom.
+
The cli_getActions
function defines which actions the
+centos-art.sh
script is able to perform. Inside
+cli_getActions
function, actions are defined combining
+positional arguments and function calls.
+
+------------------------------------------------------------------+ +| [centos@host]$ centos-art action 'path/to/dir' --option='value' | ++------------------------------------------------------------------+ +| ~/bin/centos-art --> ~/artwork/trunk/Scripts/Bash/centos-art.sh | ++---v-----------------------------------------v--------------------+ + | centos-art.sh | + +---v---------------------------------v---+ + . | initFunctions.sh | . + . +---------------------------------+ . + . | cli_getVariables $@ | . + . +---v-------------------------v---+ . + . . | cli_getActions | . . + . . +---v-----------------v---+ . . + . . . | function call 1 | . . . + . . . | function call 2 | . . . + . . . | function call n | . . . + . . . +-----------------+ . . . + . . ........................... . . + . ................................... . + ........................................... ++
Figure 3.1: The centos-art.sh
initialization environment.
+
+
The identity matching list is used by identity rendering functions to +define the relation between translation files and identity design +templates. See section trunk/Scripts/Bash/Functions/Config/cli_getIdentityMatchinglist.sh, for more information. +
+ + +To add new features inside centos-art.sh
script, you need to
+set positional arguments and function calls inside
+cli_getActions
function for the new function or functions
+required by the new feature you want to add.
+
centos-art
`check' action This feature is supported through the following command: +
+This command verifies paths, symbolic links, installed packages and
+everything your workstation needs in order to run the
+centos-art
command correctly.
+
+Warning
If this is the first time you run +
centos-art
command, the appropriate way to execute check +action is not using thecentos-art
command, but the absolute +path tocentos-art.sh
script instead: +~/artwork/trunk/Scripts/Bash/centos-art.sh check +
centos-art
`search' action This feature is not supported yet. +
+Use this command to find directories and files that match exactly the +posix-regular expression set in `pattern' as in `^pattern$'. +
+Use this command to search repository entries that match pattern1 +or patter2 or patternN as in +`'^.*(pattern1|pattern2|patternN).*$''. +
+Use this command to search repository entries that match +`path/to/dir1' or `path/to/dir2', or +`path/to/dirN' as in +`^.*(path/to/dir1|path/to/dir2|path/to/dirN).*$''. +
+centos-art
`path' action This feature is not supported yet. +
+centos-art
`locale-art' action This feature is not supported yet. +
+centos-art
`license' action This feature is supported through the following command: +
+Use this command to see a brief description of centos-art
+command its copyright and its license notes.
+
3.30 trunk/Scripts/Bash/Config | + | |
3.33 trunk/Scripts/Bash/Functions | + | |
3.45 trunk/Scripts/Bash/Locale | + | |
3.28 trunk/Scripts | + |
[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_33.html b/Manuals/en/Html/Repository/repository_33.html
index 36037b8..a058813 100644
--- a/Manuals/en/Html/Repository/repository_33.html
+++ b/Manuals/en/Html/Repository/repository_33.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
The `trunk/Scripts/Bash/Config' directory exists to oraganize +pre-rendering configuration scripts. +
+ -Pre-rendering configuration scripts let you customize the way
+centos-art.sh
script renders identity and translation
+repository entries. Pre-rendering configuration scripts are
+`render.conf.sh' files with loadConfiguration
function
+definition inside.
+
There is one `render.conf.sh' file for each pre-rendering +configuration entry. Pre-rendering configuration entries can be based +both on identity and translation repository entires. Pre-rendering +configuration entries are required for each identity entry, but not +for translation entries. +
-Inside CentOS Artwork Repository, we consider directories under +`trunk/Identity' as identity entries. Identity entries can be +image-based or text-based. When you render image-based identity +entries you need to use image-based pre-rendering configuration +scripts. Likewise, when you render text-based identity entries you +need to use text-based pre-rendering configuration scripts. +
+Inside both image-based and text-based identity pre-rendering
+configuration scripts, we use the `ACTIONS' array variable to
+define the way centos-art.sh
script performs identity
+rendering. The first entry inside `ACTIONS' array variable (i.e.,
+`ACTIONS[0]') is reserved to define the primary rendering action
+(i.e, `renderImage' or `renderText'). Further entries
+inside `ACTIONS' (i.e., `ACTIONS[1]', `ACTIONS[2]',
+etc.) are used to define identity post-rendering actions.
+
Inside identity pre-rendering configuration scripts, image-based +pre-rendering configuration scripts look like the following: +
+#!/bin/bash -
Inside identity pre-rendering configuration scripts, text-based +pre-rendering configuration scripts look like the following: +
+#!/bin/bash + +function loadConfiguration { + + # Define post-rendering actions. An empty value means that no + # post-rendering action is applied. + ACTIONS[0]='renderText' + ACTIONS[1]='formatText: --width=70 --uniform-spacing' -
When using identity pre-rendering configuration scripts, you can +extend both image-based and text-based pre-rendering configuration +scripts using image-based and text-based post-rendering actions, +respectively. +
+ + +Translation pre-rendering configuration scripts take precedence before +default translation rendering action. Translation pre-rendering +actions are useful when default translation rendering action do not +fit itself to translation entry rendering requirements. +
Use the following commands to administer both identity and translation +pre-rendering configuration scripts: +
+Use this command to create `path/to/dir' related pre-rendering +configuration script. +
+Use this command to edit `path/to/dir' related pre-rendering +configuration script. +
+Use this command to read `path/to/dir' related pre-rendering +configuration script. +
+Use this command to remove `path/to/dir' related pre-rendering +configuration script. +
+In the commands above, `path/to/dir' refers to one renderable +directory path under `trunk/Identity' or +`trunk/Translations' structures only. +
3.31 trunk/Scripts/Bash/Config/Identity | + | |
3.32 trunk/Scripts/Bash/Config/Translations | + | |
3.29 trunk/Scripts/Bash | + |
[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_34.html b/Manuals/en/Html/Repository/repository_34.html
index 1b93d3c..7f3cae2 100644
--- a/Manuals/en/Html/Repository/repository_34.html
+++ b/Manuals/en/Html/Repository/repository_34.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_35.html b/Manuals/en/Html/Repository/repository_35.html
index d3549a7..5864a50 100644
--- a/Manuals/en/Html/Repository/repository_35.html
+++ b/Manuals/en/Html/Repository/repository_35.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
+ + +Redirection
-The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/Config, instead. -
[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_36.html b/Manuals/en/Html/Repository/repository_36.html
index 2c47d08..5806fad 100644
--- a/Manuals/en/Html/Repository/repository_36.html
+++ b/Manuals/en/Html/Repository/repository_36.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
Redirection
-The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh, instead. -
[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_37.html b/Manuals/en/Html/Repository/repository_37.html
index 21a1b65..5e18c16 100644
--- a/Manuals/en/Html/Repository/repository_37.html
+++ b/Manuals/en/Html/Repository/repository_37.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
+Redirection
-The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActions.sh, instead. +The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/Config, instead.
[ < ] | -[ > ] | +|||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_38.html b/Manuals/en/Html/Repository/repository_38.html
index 43b2dec..2cdb743 100644
--- a/Manuals/en/Html/Repository/repository_38.html
+++ b/Manuals/en/Html/Repository/repository_38.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
Redirection
-The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh, instead. +The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActionsIdentity.sh, instead.
[ < ] | -[ > ] | +|||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_39.html b/Manuals/en/Html/Repository/repository_39.html
index abdf3e2..64832be 100644
--- a/Manuals/en/Html/Repository/repository_39.html
+++ b/Manuals/en/Html/Repository/repository_39.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
+Removed
-The content of this page was removed. Use the following command to -search what you need: -
-centos-art help --search --filter='your search pattern' -
Redirection
+The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActions.sh, instead. +
[ < ] | -[ > ] | +|||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_4.html b/Manuals/en/Html/Repository/repository_4.html
index 2f5c734..ac83d8f 100644
--- a/Manuals/en/Html/Repository/repository_4.html
+++ b/Manuals/en/Html/Repository/repository_4.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
Redirection
+The content of this page was moved. See section trunk/Scripts/Bash/Functions/Render/render_getActionsTranslations.sh, instead. +
[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_41.html b/Manuals/en/Html/Repository/repository_41.html
index 2e4526e..9fbe35d 100644
--- a/Manuals/en/Html/Repository/repository_41.html
+++ b/Manuals/en/Html/Repository/repository_41.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
Removed
+The content of this page was removed. Use the following command to +search what you need: +
+centos-art help --search --filter='your search pattern' +
[ < ] | +|||||||
[ < ] | [ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_42.html b/Manuals/en/Html/Repository/repository_42.html
index dd901ec..25a3153 100644
--- a/Manuals/en/Html/Repository/repository_42.html
+++ b/Manuals/en/Html/Repository/repository_42.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_43.html b/Manuals/en/Html/Repository/repository_43.html
index 8359694..1323401 100644
--- a/Manuals/en/Html/Repository/repository_43.html
+++ b/Manuals/en/Html/Repository/repository_43.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_44.html b/Manuals/en/Html/Repository/repository_44.html
index b423820..76fc7d2 100644
--- a/Manuals/en/Html/Repository/repository_44.html
+++ b/Manuals/en/Html/Repository/repository_44.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_45.html b/Manuals/en/Html/Repository/repository_45.html
index 0ff12d4..3fc7678 100644
--- a/Manuals/en/Html/Repository/repository_45.html
+++ b/Manuals/en/Html/Repository/repository_45.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_46.html b/Manuals/en/Html/Repository/repository_46.html
index 9aea6e1..b0d2c84 100644
--- a/Manuals/en/Html/Repository/repository_46.html
+++ b/Manuals/en/Html/Repository/repository_46.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
This command looks for `.sh' files inside Bash directory and
-extracts translatable strings from files, using xgettext
-command, in order to create a portable object template
-(`centos-art.sh.pot') file for them.
-
With the `centos-art.sh.pot' file up to date, the
-centos-art
command removes the temporal list of files sotred
-inside `/tmp' directory and checks the current language of your
-user's session to create a portable object file for it, in the
-location `$CLI_LANG/$CLI_LANG.po'.
-
The CLI_LANG variable discribes the locale language used to
-output messages inside centos-art
command. The locale
-language used inside centos-art
command is taken from the
-LANG environment variable. The CLI_LANG variable has the
-`LL_CC' format, where `LL' is a language code from the
-ISO-639 standard, and `CC' a country code from the ISO-3166
-standard.
-
The LANG environment variable is set when you do log in to your
-system. If you are using a graphical session, change language to your
-native language and do login. That would set and exoprt the LANG
-environment variable to the correct value. On the other side, if you
-are using a text session edit your `~/.bash_profile' file to set
-and export the LANG environment variable to your native locale
-as defines the locale -a
command output; do logout, and do
-login again.
-
At this point, the LANG environment variable has the appropriate
-value you need, in order to translate centos-art.sh
messages
-to your native language (the one set in LANG environment
-variable).
-
With the `$CLI_LANG/$CLI_LANG.po' file up to date, the
-centos-art
opens it for you to update translation strings.
-The centos-art
command uses the value of EDITOR
-environment variable to determine your favorite text editor. If no
-value is defined on EDITOR, the `/usr/bin/vim' text editor
-is used as default.
-
When you finish PO file's edition and quit text editor, the
-centos-art
command creates the related machine object in the
-location `$CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo'.
-
At this point, all translations you made in the PO file should be
-available to your language when runing centos-art.sh
script.
-
In order to make the centos-art.sh
internationalization, the
-centos-art.sh
script was modified as described in the
-gettext
info documentation (info gettext
). You
-can find such modifications in the following files:
-
centos-art
`locale-cli' action Use this command to translate command-line interface output messages -in the current system locale you are using (as specified in LANG -environment variable). -
Use this command to see the command-line interface locale report. -
3.28 trunk/Scripts/Bash/Config | - | |
3.31 trunk/Scripts/Bash/Functions | - | |
3.26 trunk/Scripts | - |
[ < ] | -[ > ] | +|||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_47.html b/Manuals/en/Html/Repository/repository_47.html
index 8a6cee6..d123a2a 100644
--- a/Manuals/en/Html/Repository/repository_47.html
+++ b/Manuals/en/Html/Repository/repository_47.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_48.html b/Manuals/en/Html/Repository/repository_48.html
index f34abbc..0083b13 100644
--- a/Manuals/en/Html/Repository/repository_48.html
+++ b/Manuals/en/Html/Repository/repository_48.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
This command looks for `.sh' files inside Bash directory and
+extracts translatable strings from files, using xgettext
+command, in order to create a portable object template
+(`centos-art.sh.pot') file for them.
+
With the `centos-art.sh.pot' file up to date, the
+centos-art
command removes the temporal list of files sotred
+inside `/tmp' directory and checks the current language of your
+user's session to create a portable object file for it, in the
+location `$CLI_LANG/$CLI_LANG.po'.
+
The CLI_LANG variable discribes the locale language used to
+output messages inside centos-art
command. The locale
+language used inside centos-art
command is taken from the
+LANG environment variable. The CLI_LANG variable has the
+`LL_CC' format, where `LL' is a language code from the
+ISO-639 standard, and `CC' a country code from the ISO-3166
+standard.
+
The LANG environment variable is set when you do log in to your
+system. If you are using a graphical session, change language to your
+native language and do login. That would set and exoprt the LANG
+environment variable to the correct value. On the other side, if you
+are using a text session edit your `~/.bash_profile' file to set
+and export the LANG environment variable to your native locale
+as defines the locale -a
command output; do logout, and do
+login again.
+
At this point, the LANG environment variable has the appropriate
+value you need, in order to translate centos-art.sh
messages
+to your native language (the one set in LANG environment
+variable).
+
With the `$CLI_LANG/$CLI_LANG.po' file up to date, the
+centos-art
opens it for you to update translation strings.
+The centos-art
command uses the value of EDITOR
+environment variable to determine your favorite text editor. If no
+value is defined on EDITOR, the `/usr/bin/vim' text editor
+is used as default.
+
When you finish PO file's edition and quit text editor, the
+centos-art
command creates the related machine object in the
+location `$CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo'.
+
At this point, all translations you made in the PO file should be
+available to your language when runing centos-art.sh
script.
+
In order to make the centos-art.sh
internationalization, the
+centos-art.sh
script was modified as described in the
+gettext
info documentation (info gettext
). You
+can find such modifications in the following files:
+
centos-art
`locale-cli' action Use this command to translate command-line interface output messages +in the current system locale you are using (as specified in LANG +environment variable). +
Use this command to see the command-line interface locale report. +
3.30 trunk/Scripts/Bash/Config | + | |
3.33 trunk/Scripts/Bash/Functions | + | |
3.28 trunk/Scripts | + |
[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_49.html b/Manuals/en/Html/Repository/repository_49.html
index 63bf284..876e336 100644
--- a/Manuals/en/Html/Repository/repository_49.html
+++ b/Manuals/en/Html/Repository/repository_49.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
The `trunk/Translations' directory exists to: -
When you create artwork for CentOS distribution you find that some -artworks need to be created for different major releases of CentOS -distribution and inside each major release they need to be created for -different locales. To get an approximate idea of how many files we are -talking about, consider the followig approximate statistic: -
-In order to aliviate maintainance of artwork production for such -environment, we divided artwork production in three production lines: -
-Inside CentOS Artwork Repository, the artworks' translation production -line is stored under `trunk/Translations' directory. -
-Inside `trunk/Translations' directory, we use "translation -entries" to organize artworks' "translation files" and artworks' -"translation templates". -
-Translation entries exists for each artwork you want to produce. -Translation entries can be empty directories, or directories -containing translation files and translation templates. -
-When translation entries are empty directories, the identity entry is
-used as reference to create file names and directories layout for
-rendered files. In this case, the centos-art
script takes
-one design template and outputs one non-translated file for each
-design template available. This configuration is mainly used to
-produce non-translatable artworks like themes' backgrounds.
-
When translation entries contain translation files, the translation
-entry implements the CentOS release schema and is used as reference to
-create file names and directories layout for translated artworks. In
-this case, the centos-art
script applies one translation
-file to one design template to create one translated instance which is
-used to output one translated file. When the translated file is
-rendered, the centos-art
script remove the previous instance
-and takes the next file in the list of translation files to repate the
-whole process once again, and so on for all files in the list. This
-configuration is mainly used to produce translatable artworks like
-Anaconda's progress slide images.
-
To find out correspondence between translation entries and identity -entries, you need to look the path of both translation entries and -identity entries. For example, if you are using the Modern's artisitic -motif, the identity entry for Anaconda progress artwork is: -
-trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress --
and its translation entry is: -
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress --
Note how the `Translations/' directory prefixes `Identity/' -directory, also how static values (e.g., Identity, Themes, Distro, -etc.) in the identity's entry path remain in translation's entry path, -and how variable values like theme names (e.g., Modern) are stript out -from translation's entry path. The same convenction can be applied to -other identity entries in order to determine their translation -entries, or to other translation entries to determine their identity -entries. -
-- -Note
Translation entries related to identity entries under -`trunk/Identity/Themes/Motifs' do not use `Motifs/' in the -path. We've done this because `trunk/Identity/Themes/Models' -structure, the other structure under `trunk/Identity/Themes', -doesn't require translation paths so far. So in the sake of saving -characters space when building translation entries for -`trunk/Identity/Themes/Motifs' structure, we organize Motifs -translation entries under `trunk/Translations/Identity/Themes/' -directly. -
-If for some reason `trunk/Identity/Themes/Models' structure -requires translation entries, we need to re-oraganize the current -directory structure accordingly. -
Translation entries, as described above, can be re-used by similar -identity entries. For example the following identity entries: -
-trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ -trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Progress/ -trunk/Identity/Themes/Motifs/Mettle/Distro/Anaconda/Progress/ --
are all valid identity entries able to re-use translation files inside -Anaconda progress translation entry (the one shown in our example -above). This way, you can create several identity entries and maintain -just one translation entry for all of them. Once you change the -translation files inside the common translation entry, changes inside -identity entries will take effect inside the next you render them. -
-Trying to make things plain and simple: inside CentOS Artwork -Repository, graphic designers can concentrate their efforts in -artworks look and feel (the identity entries), and translators in -artworks translations (the translation entries). -
- - -Translation markers are used in "Theme Model Designs" and
-"Translation Files" as replacement patterns to commit content
-translation. When you are rendering content using
-centos-art
script inisde `trunk/Identity' structure,
-artistic motifs and translation files are applied to model designs to
-produce translated content as result. In order to have the appropriate
-translation in content rendered, markers defintion in translation
-files should match markers in model designs exactly.
-
Figure 3.2: The image rendering flow. - -
-Translation markers can be whatever text you want, but as convenction -we use the following to represent releases of CentOS distribution: -
-Replace with minor release of CentOS distribution. In the schema M.N, the minor -release is represented by the N letter. -
Replace with major release of CentOS distribution. In the schema M.N, -the major release is represented by the M letter. -
Replace the full release of CentOS distribution. It is -`=MAJOR_RELEASE=.=MINOR_RELEASE=' basically. -
Specific translation markers convenctions are described inside -specific translation entries. Read translation entries documentation -to know more about supported translation markers. -
-Translation markers standardization creates a common point of -reference for translators and graphic designers. To have translation -markers well defined makes possible that translators and graphic -designers can work together but independently one another. -
- - -Translation files are text files with sed
's commands inside,
-replacement commands mainly. As convenction, translation file names
-end in `.sed'. Translation files are used by centos-art
-script to produce translated artworks for specific major releases of
-CentOS Distribution. There are common translation files, specific
-translation, and template translation files.
-
For example, the Firstboot artwork of CentOS distribution uses the -images `splash-small.png' and `firstboot-left.png' as based -to control its visual style. The `splash-small.png' image -contains, in its graphic design, the release number information of -CentOS distribution. So the `splash-small.png' is -release-specific. In the other hand, the `firstboot-left.png' -doesn't contain release number information. So the -`firstboot-left.png' is not release-specific. -
-If we want to produce Firstboot artwork for different major releases -of CentOS distribution, using a monolithic visual identity, all -Firstboot images should have the same visual style and, at the same -time, the release-specific information in the release-specific images. -
-- -Note
The monolithic visual identity is implemented using -theme models (see section trunk/Identity/Themes/Models) and artistic -motifs (see section trunk/Identity/Themes/Motifs). -
Assuming that both theme models and theme motifs are ready for using, -the initial translation entry to produce Firstboot artworks would look -like the following: -
-trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ -|-- Tpl -| `-- splash-small.sed -`-- firstboot-left.sed --
With the translation entry above, centos-art
command is able
-to produce the image `firstboot-left.png' only. To produce
-`splash-small.png' images for major releases (e.g., 3, 4, 5, and
-6) of CentOS distribution we need to produce the release-specific
-translation files using the centos-art
script as following:
-
centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Themes/BootUp/Firstboot --filter='3,4,5,6' --
The above command produces the following translation entiry: -
-trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ -|-- 3 -| `-- splash-small.sed -|-- 4 -| `-- splash-small.sed -|-- 5 -| `-- splash-small.sed -|-- 6 -| `-- splash-small.sed -|-- Tpl -| `-- splash-small.sed -`-- firstboot-left.sed --
At this point centos-art
is able to produce the Firstboot
-artwork images for major releases of CentOS distribution. To add new
-release-specific translation files, run the translation rendering
-command with the release number you want to produce translation files
-for in the `--filter='release-number'' argument.
-
Template translation files are translation files stored inside
-translation template directory. Template translation files are used by
-centos-art
script to produce specific translation files
-only. Template translation files may be empty or contain
-sed
's replacement commands. If template translation files
-are empty files, the final specifc translation file built from it
-contains release-specific replacement commands only. For example,
-see the following translation entry:
-
trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ -|-- 3 -| `-- splash-small.sed -|-- 4 -| `-- splash-small.sed -|-- 5 -| `-- splash-small.sed -|-- 6 -| `-- splash-small.sed -|-- Tpl -| `-- splash-small.sed <-- template translation file. -`-- firstboot-left.sed --
In the above exmaple, the `splash-small.sed' file is a template -translation file and looks like: -
-# ------------------------------------- -# $Id: Translations.texi 94 2010-09-18 10:59:42Z al $ -# ------------------------------------- --
In the above template translation file there are three comments lines,
-but when you render it, the centos-art
adds the
-release-specific replacement commands. In our Firstboot example, after
-rendering Firstboot translation entry, the `splash-small.sed'
-translation file specific to CentOS 5, looks like the following:
-
# Warning: Do not modify this file directly. This file is created -# automatically using 'centos-art' command line interface. Any change -# you do in this file will be lost the next time you update -# translation files using 'centos-art' command line interface. If you -# want to improve the content of this translation file, improve its -# template file instead and run the 'centos-art' command line -# interface later to propagate your changes. -# ------------------------------------- -# $Id: Translations.texi 94 2010-09-18 10:59:42Z al $ -# ------------------------------------- - -# Release number information. -s!=RELEASE=!=MAJOR_RELEASE=.=MINOR_RELEASE=!g -s!=MINOR_RELEASE=!0!g -s!=MAJOR_RELEASE=!5!g --
If template translation files are not empty, replacement commands -inside template translation files are preserved inside -release-specific translation files. For example, consider the English -template translation file of Anaconda progress welcome slide. The -translation template directory structure looks like the following: -
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ -`-- Tpl - `-- en - `-- 01-welcome.sed --
and if we render translation files for CentOS 4 and CentOS 5 major -releases, the translation entry would look like the following: -
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ -|-- 4 -| `-- en -| `-- 01-welcome.sed -|-- 5 -| `-- en -| `-- 01-welcome.sed -`-- Tpl - `-- en - `-- 01-welcome.sed --
- -Note
Release-specific translation directories preserve -template translation directory structure and file names. -
In the example above, the template translation file looks like the -following: -
-# ------------------------------------------------------------ -# $Id: Translations.texi 94 2010-09-18 10:59:42Z al $ -# ------------------------------------------------------------ -s/=TITLE=/Welcome to CentOS =MAJOR_RELEASE= !/ -s/=TEXT1=/Thank you for installing CentOS =MAJOR_RELEASE=./ -s/=TEXT2=/CentOS is an enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor./ -s/=TEXT3=/CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. CentOS mainly changes packages to remove upstream vendor branding and artwork./ -s/=TEXT4=// -s/=TEXT5=// -s/=TEXT6=// -s!=URL=!http://www.centos.org/! --
and, after render the translation entry, specific translation files -look like the following: -
-# Warning: Do not modify this file directly. This file is created -# automatically using 'centos-art' command line interface. Any change -# you do in this file will be lost the next time you update -# translation files using 'centos-art' command line interface. If you -# want to improve the content of this translation file, improve its -# template file instead and run the 'centos-art' command line -# interface later to propagate your changes. -# ------------------------------------------------------------ -# $Id: Translations.texi 94 2010-09-18 10:59:42Z al $ -# ------------------------------------------------------------ - -s/=TITLE=/Welcome to CentOS =MAJOR_RELEASE= !/ -s/=TEXT1=/Thank you for installing CentOS =MAJOR_RELEASE=./ -s/=TEXT2=/CentOS is an enterprise-class Linux Distribution derived from sources freely provided to the public by a prominen t North American Enterprise Linux vendor./ -s/=TEXT3=/CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. Cent OS mainly changes packages to remove upstream vendor branding and artwork./ -s/=TEXT4=// -s/=TEXT5=// -s/=TEXT6=// -s!=URL=!http://www.centos.org/! - -# Release number information. -s!=RELEASE=!=MAJOR_RELEASE=.=MINOR_RELEASE=!g -s!=MINOR_RELEASE=!0!g -s!=MAJOR_RELEASE=!5!g --
In the example above, relevant lines begin with the `s' word -followed by a separation character (e.g., `/', `!', etc.). -These lines have the following format: -
-s/REGEXP/REPLACEMENT/FLAGS --
The `/' characters may be uniformly replaced by any other single
-character within any given s
command. The `/'
-character (or whatever other character is used in its stead) can
-appear in the REGEXP or REPLACEMENT only if it is preceded by a
-`\' character.
-
The s
command is probably the most important in
-sed
and has a lot of different options. Its basic concept
-is simple: the s
command attempts to match the pattern space
-against the supplied REGEXP; if the match is successful, then that
-portion of the pattern space which was matched is replaced with
-REPLACEMENT.
-
In the context of our translation files, the REGEXP is where you -define translation markers and REPLACEMENT where you define the -translation text you want to have after artworks rendering. Sometimes -we use the FLAG component with the `g' command to apply the -replacements globally. -
-- -Tip
More information about how to use
sed
's -replacement commands and flags is available insed
's -documentation manual. To read sed's documentation manual type the -following command: -info sed -
Inside translation files, you can use translation markers not only -inside the REGEXP but in the REPLACEMENT too. In order for this -configuration to work, the REPLACEMENT of translation markers needs to -be define after its definition. For example, see in the -release-specific translation file above, how the -`s!=MAJOR_RELASE=!5!g' replacement command is defined -after `=MAJOR_RELASE=' translation marker definition in -the REPLACEMENT of `=TITLE=' translation marker replacement -command. -
- - -Common translation files contain common translations or no -translation at all for their related artworks. They are in the root -directory of the translation entry. Common translation files create -common artworks for all major releases of CentOS Distribution. -
-Translation entries, with common translation files inside, look like -the following: -
-trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ -|-- 3 -| `-- splash-small.sed -|-- 4 -| `-- splash-small.sed -|-- 5 -| `-- splash-small.sed -|-- 6 -| `-- splash-small.sed -|-- Tpl -| `-- splash-small.sed -`-- firstboot-left.sed <-- common translation file. -- - -
Specific translation files contain specific translations for their
-related artworks. Specific translation files are not in the root
-directory of the translation entry, but inside directories which
-describe the type of translation they are doing. Specific translation
-files are produced automatically using the centos-art
-script.
-
trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ -|-- 3 -| `-- splash-small.sed <-- CentOS 3 specific translation file. -|-- 4 -| `-- splash-small.sed <-- CentOS 4 specific translation file. -|-- 5 -| `-- splash-small.sed <-- CentOS 5 specific translation file. -|-- 6 -| `-- splash-small.sed <-- CentOS 6 specific translation file. -|-- Tpl -| `-- splash-small.sed -`-- firstboot-left.sed -- - -
When rendering translations, the centos-art
script checks
-the translation entry to verify that it has a translation template
-directory inside. The translation template directory (`Tpl/')
-contains common translation files used to build release-specific
-translation files. If the translation template directory doesn't exist
-inside the translation entry the translation rendering fails. In this
-case the centos-art
script outputs a message and quits
-script execution.
-
When the centos-art
script finds a translation template
-directory inside translation entry, it looks for translations
-pre-rendering configuration scripts for that translation entry.
-Translation pre-rendering configuration scripts let you extend
-translation's default functionality (described below).
-
Translation pre-rendering configuration scripts are stored under
-`trunk/Scripts' directory, specifically under the appropriate
-language implementation. If you are using centos-art
Bash's
-implementation, the translation pre-rendering scripts are store in the
-`trunk/Scripts/Bash/Config' location; if you are using
-centos-art
Python's implementation, then translation
-pre-rendering scripts are stored in the
-`trunk/Scripts/Python/Config' location, and so on for other
-implementations.
-
Bash's translation pre-rendering configuration scripts look like the -following: -
-#!/bin/bash -# -# loadConfiguration.sh -- brief description here. -# -# Copyright (C) YEAR YOURNAME -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -# General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 -# USA. -# -# ---------------------------------------------------------------------- -# $Id: Translations.texi 94 2010-09-18 10:59:42Z al $ -# ---------------------------------------------------------------------- - -function loadConfiguration { -... -} --
Translation pre-rendering scripts are function scripts loaded and
-executed when rendering a translation entry. Translation pre-rendering
-scripts are loaded using the translation entry being rendered as
-reference. For example, suppose you are using the
-centos-art
Bash's implementation, and you are rendering
-translations for CentOS brands, in this situation the translation
-entry would be:
-
trunk/Translations/Identity/Brands --
and the entry inside the translation pre-rendering configuration -structure would be: -
-trunk/Scripts/Bash/Config/Identity/Brands --
Once the centos-art
script detects that translation
-pre-rendering configuration directory exists, the centos-art
-script looks for the translation pre-rendering configuration file. If
-the translation pre-rendering configuration file exists, it is loaded
-and executed. Once the translation pre-rendering configuration file
-has been executed the translation rendering process is over, and so
-the script execution.
-
- -Note
Translation pre-rendering configuration files have the -following form: -
render.conf.extension -where `extension' refers the programming language implementation -you are using. For example, `sh' for Bash's, `py' for -Python's, `pl' for Perl's, and so on for other implementations. -
As we are using Bash implementation to describe the translation
-pre-rendering configuration example, the translation pre-rendering
-configuration file that centos-art
looks for, inside the
-above translation pre-rendering configuration directory, is
-`render.conf.sh'.
-
In the other hand, if the translation pre-rendering configuration file
-doesn't exist, or it isn't written as function script, the
-centos-art
script ignore translation pre-rendering
-configuration functionality and passes to render translation using
-default functionality instead.
-
The translation rendering default functionality takes template
-translation directory structure, duplicates it for each release number
-specified in the `--filter='release-number'' argument and
-produces release-specific directories. As part of template translation
-duplication process take place, the centos-art
script adds
-release-specific replacement commands to each specific translation
-file inside release-specific directories. As result, specific
-translation files, inside release-specific directories, contain
-template translation replacement commands plus,
-release-specific replacement commands.
-
- - - -Note
Release-specific replacement commands are standardized -inside
centos-art
script using predifined release -translation markers. Release translation markers are described in the -translation marker section -(see Translation Markers). -
When `path/to/dir' refers one directory under -`trunk/Translations', this command orverwrites available -translation files using translation templates. -
-When `path/to/dir' refers one directory under -`trunk/Translations', this command renders release-specific -translation files as you specify in the `--filter='pattern'' -argument. In this case, `pattern' not a regular expression but an -number (e.g., `5') or a list of numbers separated by commas -(e.g., `3,4,5,6') that specify the major release of CentOS -distribution you want to render translations for. -
-[ < ] | -[ > ] | +|||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_5.html b/Manuals/en/Html/Repository/repository_5.html
index 5a7c8f5..443a61c 100644
--- a/Manuals/en/Html/Repository/repository_5.html
+++ b/Manuals/en/Html/Repository/repository_5.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_51.html b/Manuals/en/Html/Repository/repository_51.html
index 344291e..529f9b5 100644
--- a/Manuals/en/Html/Repository/repository_51.html
+++ b/Manuals/en/Html/Repository/repository_51.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
The `trunk/Translations' directory exists to: +
Translation files, inside `trunk/Translations/Identity/Brands' -translation entry, don't use default rendering translation -functionality, they use the following translation pre-rendering -configuration file instead: +
When you create artwork for CentOS distribution you find that some +artworks need to be created for different major releases of CentOS +distribution and inside each major release they need to be created for +different locales. To get an approximate idea of how many files we are +talking about, consider the followig approximate statistic: +
+In order to aliviate maintainance of artwork production for such +environment, we divided artwork production in three production lines: +
+Inside CentOS Artwork Repository, the artworks' translation production +line is stored under `trunk/Translations' directory. +
+Inside `trunk/Translations' directory, we use "translation +entries" to organize artworks' "translation files" and artworks' +"translation templates". +
+ + +Translation entries exists for each artwork you want to produce. +Translation entries can be empty directories, or directories +containing translation files and translation templates.
-/home/centos/artwork/trunk/Translation/Identity/Brands/render.conf.sh +When translation entries are empty directories, the identity entry is +used as reference to create file names and directories layout for +rendered files. In this case, the
+centos-art
script takes +one design template and outputs one non-translated file for each +design template available. This configuration is mainly used to +produce non-translatable artworks like themes' backgrounds. +When translation entries contain translation files, the translation +entry implements the CentOS release schema and is used as reference to +create file names and directories layout for translated artworks. In +this case, the
+centos-art
script applies one translation +file to one design template to create one translated instance which is +used to output one translated file. When the translated file is +rendered, thecentos-art
script remove the previous instance +and takes the next file in the list of translation files to repate the +whole process once again, and so on for all files in the list. This +configuration is mainly used to produce translatable artworks like +Anaconda's progress slide images. +To find out correspondence between translation entries and identity +entries, you need to look the path of both translation entries and +identity entries. For example, if you are using the Modern's artisitic +motif, the identity entry for Anaconda progress artwork is: +
+trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress ++and its translation entry is: +
+trunk/Translations/Identity/Themes/Distro/Anaconda/Progress-Inside `trunk/Translations/Identity/Brands' translation entry, -translation files are symbolic links pointing to the common template -translation structure, inside the translation template (`Tpl/') -directory. +
Note how the `Translations/' directory prefixes `Identity/' +directory, also how static values (e.g., Identity, Themes, Distro, +etc.) in the identity's entry path remain in translation's entry path, +and how variable values like theme names (e.g., Modern) are stript out +from translation's entry path. The same convenction can be applied to +other identity entries in order to determine their translation +entries, or to other translation entries to determine their identity +entries.
-Inside `trunk/Translations/Identity/Brands' translation entry, -translation files are created using identity design templates as -reference. The translation pre-rendering script creates a translation -structure where the translation template (`Tpl/') directory -structure applies to each single design template available. +
+ +Note
Translation entries related to identity entries under +`trunk/Identity/Themes/Motifs' do not use `Motifs/' in the +path. We've done this because `trunk/Identity/Themes/Models' +structure, the other structure under `trunk/Identity/Themes', +doesn't require translation paths so far. So in the sake of saving +characters space when building translation entries for +`trunk/Identity/Themes/Motifs' structure, we organize Motifs +translation entries under `trunk/Translations/Identity/Themes/' +directly.
-For example, if the brands' translation template (`Tpl/') -directory has 30 translation files, and there are 20 design templates; -the brands' translation pre-rendering script creates a translation -structure of symbolic links where the 30 translation files apply the -20 design templates one by one, producing 600 translation symbolic -links as result. At this point, when rendering identity, the -
centos-art
script considers translation symbolic links as -translation files. +If for some reason `trunk/Identity/Themes/Models' structure +requires translation entries, we need to re-oraganize the current +directory structure accordingly. +
Translation entries, as described above, can be re-used by similar +identity entries. For example the following identity entries:
-Translation file names, inside brands' translation template -(`Tpl') directory have special meaning: +
trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ +trunk/Identity/Themes/Motifs/TreeFlower/Distro/Anaconda/Progress/ +trunk/Identity/Themes/Motifs/Mettle/Distro/Anaconda/Progress/ ++are all valid identity entries able to re-use translation files inside +Anaconda progress translation entry (the one shown in our example +above). This way, you can create several identity entries and maintain +just one translation entry for all of them. Once you change the +translation files inside the common translation entry, changes inside +identity entries will take effect inside the next you render them. +
+Trying to make things plain and simple: inside CentOS Artwork +Repository, graphic designers can concentrate their efforts in +artworks look and feel (the identity entries), and translators in +artworks translations (the translation entries).
- -3.48.2.1 Conventional file names
+ +3.48.2.2 Translation Markers
+ +Translation markers are used in "Theme Model Designs" and +"Translation Files" as replacement patterns to commit content +translation. When you are rendering content using +
+centos-art
script inisde `trunk/Identity' structure, +artistic motifs and translation files are applied to model designs to +produce translated content as result. In order to have the appropriate +translation in content rendered, markers defintion in translation +files should match markers in model designs exactly. ++-
Convenctional file names look like `blue.sed', `2c-a.sed', -etc. Replacement commands inside translation file are applied to -design templates and translation file names are used as final image -name. The image dimensions use the same dimensions that design -template has. +
Figure 3.2: The image rendering flow. +
+Translation markers can be whatever text you want, but as convenction +we use the following to represent releases of CentOS distribution: +
+
Replace with minor release of CentOS distribution. In the schema M.N, the minor +release is represented by the N letter. +
Replace with major release of CentOS distribution. In the schema M.N, +the major release is represented by the M letter. +
Replace the full release of CentOS distribution. It is +`=MAJOR_RELEASE=.=MINOR_RELEASE=' basically. +
Specific translation markers convenctions are described inside +specific translation entries. Read translation entries documentation +to know more about supported translation markers. +
+Translation markers standardization creates a common point of +reference for translators and graphic designers. To have translation +markers well defined makes possible that translators and graphic +designers can work together but independently one another. +
+ + +Numeric file names look like `300.sed', `200.sed', etc. -Replacements commands inside translation files are applied to design -templates, and translation file names are used as final image name. -The final image is saved using an specific `width' defined by the -number part of the translation file name. The image `height' is -automatically scaled based on the previous `width' definition to -maintain the design's ratio. +
Translation files are text files with sed
's commands inside,
+replacement commands mainly. As convenction, translation file names
+end in `.sed'. Translation files are used by centos-art
+script to produce translated artworks for specific major releases of
+CentOS Distribution. There are common translation files, specific
+translation, and template translation files.
For example, if your design template has 400x200 pixels of dimension, -and you apply a translation file named `300.sed' to it, the final -image you get as result will have 300x100 pixels of dimension. The -same is true if you use higher numbers like `1024.sed', `2048.sed', -etc. In these cases you have bigger images proportionally. +
For example, the Firstboot artwork of CentOS distribution uses the +images `splash-small.png' and `firstboot-left.png' as based +to control its visual style. The `splash-small.png' image +contains, in its graphic design, the release number information of +CentOS distribution. So the `splash-small.png' is +release-specific. In the other hand, the `firstboot-left.png' +doesn't contain release number information. So the +`firstboot-left.png' is not release-specific.
-As we are using scalable vector graphics to design identity templates, -the image size you produce is not limitted in size. You can use one -design template produced in 400x200 pixels to produce larger or -shorter PNG images using numeric translation files as described -above. +
If we want to produce Firstboot artwork for different major releases +of CentOS distribution, using a monolithic visual identity, all +Firstboot images should have the same visual style and, at the same +time, the release-specific information in the release-specific images.
+- -Note
The monolithic visual identity is implemented using +theme models (see section trunk/Identity/Themes/Models) and artistic +motifs (see section trunk/Identity/Themes/Motifs). +
Assuming that both theme models and theme motifs are ready for using, +the initial translation entry to produce Firstboot artworks would look +like the following: +
+trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ +|-- Tpl +| `-- splash-small.sed +`-- firstboot-left.sed ++
With the translation entry above, centos-art
command is able
+to produce the image `firstboot-left.png' only. To produce
+`splash-small.png' images for major releases (e.g., 3, 4, 5, and
+6) of CentOS distribution we need to produce the release-specific
+translation files using the centos-art
script as following:
+
centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Themes/BootUp/Firstboot --filter='3,4,5,6' ++
The above command produces the following translation entiry: +
+trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ +|-- 3 +| `-- splash-small.sed +|-- 4 +| `-- splash-small.sed +|-- 5 +| `-- splash-small.sed +|-- 6 +| `-- splash-small.sed +|-- Tpl +| `-- splash-small.sed +`-- firstboot-left.sed ++
At this point centos-art
is able to produce the Firstboot
+artwork images for major releases of CentOS distribution. To add new
+release-specific translation files, run the translation rendering
+command with the release number you want to produce translation files
+for in the `--filter='release-number'' argument.
+
Inside `trunk/Translations/Identity/Brands/', translation files -combine the following translation markers: + +
Template translation files are translation files stored inside
+translation template directory. Template translation files are used by
+centos-art
script to produce specific translation files
+only. Template translation files may be empty or contain
+sed
's replacement commands. If template translation files
+are empty files, the final specifc translation file built from it
+contains release-specific replacement commands only. For example,
+see the following translation entry:
Specify which color to use when rendering brand images. +
trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ +|-- 3 +| `-- splash-small.sed +|-- 4 +| `-- splash-small.sed +|-- 5 +| `-- splash-small.sed +|-- 6 +| `-- splash-small.sed +|-- Tpl +| `-- splash-small.sed <-- template translation file. +`-- firstboot-left.sed ++
In the above exmaple, the `splash-small.sed' file is a template +translation file and looks like: +
+# ------------------------------------- +# $Id: Translations.texi 94 2010-09-18 10:59:42Z al $ +# ------------------------------------- ++
In the above template translation file there are three comments lines,
+but when you render it, the centos-art
adds the
+release-specific replacement commands. In our Firstboot example, after
+rendering Firstboot translation entry, the `splash-small.sed'
+translation file specific to CentOS 5, looks like the following:
+
# Warning: Do not modify this file directly. This file is created +# automatically using 'centos-art' command line interface. Any change +# you do in this file will be lost the next time you update +# translation files using 'centos-art' command line interface. If you +# want to improve the content of this translation file, improve its +# template file instead and run the 'centos-art' command line +# interface later to propagate your changes. +# ------------------------------------- +# $Id: Translations.texi 94 2010-09-18 10:59:42Z al $ +# ------------------------------------- + +# Release number information. +s!=RELEASE=!=MAJOR_RELEASE=.=MINOR_RELEASE=!g +s!=MINOR_RELEASE=!0!g +s!=MAJOR_RELEASE=!5!g ++
If template translation files are not empty, replacement commands +inside template translation files are preserved inside +release-specific translation files. For example, consider the English +template translation file of Anaconda progress welcome slide. The +translation template directory structure looks like the following: +
+trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ +`-- Tpl + `-- en + `-- 01-welcome.sed ++
and if we render translation files for CentOS 4 and CentOS 5 major +releases, the translation entry would look like the following:
-Note
As translation files inside -`trunk/Translations/Identity/Brands' are symbolic links that -point to template translation files, translation markers are defined -inside template translation files. +
trunk/Translations/Identity/Themes/Distro/Anaconda/Progress/ +|-- 4 +| `-- en +| `-- 01-welcome.sed +|-- 5 +| `-- en +| `-- 01-welcome.sed +`-- Tpl + `-- en + `-- 01-welcome.sed ++-Note
Release-specific translation directories preserve +template translation directory structure and file names.
In the example above, the template translation file looks like the +following: +
+# ------------------------------------------------------------ +# $Id: Translations.texi 94 2010-09-18 10:59:42Z al $ +# ------------------------------------------------------------ +s/=TITLE=/Welcome to CentOS =MAJOR_RELEASE= !/ +s/=TEXT1=/Thank you for installing CentOS =MAJOR_RELEASE=./ +s/=TEXT2=/CentOS is an enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor./ +s/=TEXT3=/CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. CentOS mainly changes packages to remove upstream vendor branding and artwork./ +s/=TEXT4=// +s/=TEXT5=// +s/=TEXT6=// +s!=URL=!http://www.centos.org/! ++
and, after render the translation entry, specific translation files +look like the following: +
+# Warning: Do not modify this file directly. This file is created +# automatically using 'centos-art' command line interface. Any change +# you do in this file will be lost the next time you update +# translation files using 'centos-art' command line interface. If you +# want to improve the content of this translation file, improve its +# template file instead and run the 'centos-art' command line +# interface later to propagate your changes. +# ------------------------------------------------------------ +# $Id: Translations.texi 94 2010-09-18 10:59:42Z al $ +# ------------------------------------------------------------ - -+3.48.3 Usage
+s/=TITLE=/Welcome to CentOS =MAJOR_RELEASE= !/ +s/=TEXT1=/Thank you for installing CentOS =MAJOR_RELEASE=./ +s/=TEXT2=/CentOS is an enterprise-class Linux Distribution derived from sources freely provided to the public by a prominen t North American Enterprise Linux vendor./ +s/=TEXT3=/CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. Cent OS mainly changes packages to remove upstream vendor branding and artwork./ +s/=TEXT4=// +s/=TEXT5=// +s/=TEXT6=// +s!=URL=!http://www.centos.org/! -To render brands' translation files, use the following command: +# Release number information. +s!=RELEASE=!=MAJOR_RELEASE=.=MINOR_RELEASE=!g +s!=MINOR_RELEASE=!0!g +s!=MAJOR_RELEASE=!5!g +
In the example above, relevant lines begin with the `s' word +followed by a separation character (e.g., `/', `!', etc.). +These lines have the following format: +
+s/REGEXP/REPLACEMENT/FLAGS ++
The `/' characters may be uniformly replaced by any other single
+character within any given s
command. The `/'
+character (or whatever other character is used in its stead) can
+appear in the REGEXP or REPLACEMENT only if it is preceded by a
+`\' character.
+
The s
command is probably the most important in
+sed
and has a lot of different options. Its basic concept
+is simple: the s
command attempts to match the pattern space
+against the supplied REGEXP; if the match is successful, then that
+portion of the pattern space which was matched is replaced with
+REPLACEMENT.
+
In the context of our translation files, the REGEXP is where you +define translation markers and REPLACEMENT where you define the +translation text you want to have after artworks rendering. Sometimes +we use the FLAG component with the `g' command to apply the +replacements globally. +
++ +Tip
More information about how to use
sed
's +replacement commands and flags is available insed
's +documentation manual. To read sed's documentation manual type the +following command: +info sed +
Inside translation files, you can use translation markers not only +inside the REGEXP but in the REPLACEMENT too. In order for this +configuration to work, the REPLACEMENT of translation markers needs to +be define after its definition. For example, see in the +release-specific translation file above, how the +`s!=MAJOR_RELASE=!5!g' replacement command is defined +after `=MAJOR_RELASE=' translation marker definition in +the REPLACEMENT of `=TITLE=' translation marker replacement +command. +
+ + +Common translation files contain common translations or no +translation at all for their related artworks. They are in the root +directory of the translation entry. Common translation files create +common artworks for all major releases of CentOS Distribution. +
+Translation entries, with common translation files inside, look like +the following: +
+trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ +|-- 3 +| `-- splash-small.sed +|-- 4 +| `-- splash-small.sed +|-- 5 +| `-- splash-small.sed +|-- 6 +| `-- splash-small.sed +|-- Tpl +| `-- splash-small.sed +`-- firstboot-left.sed <-- common translation file. ++ + +
Specific translation files contain specific translations for their
+related artworks. Specific translation files are not in the root
+directory of the translation entry, but inside directories which
+describe the type of translation they are doing. Specific translation
+files are produced automatically using the centos-art
+script.
centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands +trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ +|-- 3 +| `-- splash-small.sed <-- CentOS 3 specific translation file. +|-- 4 +| `-- splash-small.sed <-- CentOS 4 specific translation file. +|-- 5 +| `-- splash-small.sed <-- CentOS 5 specific translation file. +|-- 6 +| `-- splash-small.sed <-- CentOS 6 specific translation file. +|-- Tpl +| `-- splash-small.sed +`-- firstboot-left.sed- + +3.48.2.7 Translation Rendering
+ +When rendering translations, the
+ + +centos-art
script checks +the translation entry to verify that it has a translation template +directory inside. The translation template directory (`Tpl/') +contains common translation files used to build release-specific +translation files. If the translation template directory doesn't exist +inside the translation entry the translation rendering fails. In this +case thecentos-art
script outputs a message and quits +script execution. +3.48.2.8 Translation (Pre-)Rendering Configuration Scripts
+ +When the
+centos-art
script finds a translation template +directory inside translation entry, it looks for translations +pre-rendering configuration scripts for that translation entry. +Translation pre-rendering configuration scripts let you extend +translation's default functionality (described below). +Translation pre-rendering configuration scripts are stored under +`trunk/Scripts' directory, specifically under the appropriate +language implementation. If you are using
+centos-art
Bash's +implementation, the translation pre-rendering scripts are store in the +`trunk/Scripts/Bash/Config' location; if you are using +centos-art
Python's implementation, then translation +pre-rendering scripts are stored in the +`trunk/Scripts/Python/Config' location, and so on for other +implementations. +Bash's translation pre-rendering configuration scripts look like the +following: +
+#!/bin/bash +# +# loadConfiguration.sh -- brief description here. +# +# Copyright (C) YEAR YOURNAME +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, but +# WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +# General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 +# USA. +# +# ---------------------------------------------------------------------- +# $Id: Translations.texi 94 2010-09-18 10:59:42Z al $ +# ---------------------------------------------------------------------- + +function loadConfiguration { +... +} ++Translation pre-rendering scripts are function scripts loaded and +executed when rendering a translation entry. Translation pre-rendering +scripts are loaded using the translation entry being rendered as +reference. For example, suppose you are using the +
+centos-art
Bash's implementation, and you are rendering +translations for CentOS brands, in this situation the translation +entry would be: +trunk/Translations/Identity/Brands ++and the entry inside the translation pre-rendering configuration +structure would be: +
+trunk/Scripts/Bash/Config/Identity/Brands ++Once the
+centos-art
script detects that translation +pre-rendering configuration directory exists, thecentos-art
+script looks for the translation pre-rendering configuration file. If +the translation pre-rendering configuration file exists, it is loaded +and executed. Once the translation pre-rendering configuration file +has been executed the translation rendering process is over, and so +the script execution. ++ +Note
Translation pre-rendering configuration files have the +following form: +
render.conf.extension +where `extension' refers the programming language implementation +you are using. For example, `sh' for Bash's, `py' for +Python's, `pl' for Perl's, and so on for other implementations. +
As we are using Bash implementation to describe the translation +pre-rendering configuration example, the translation pre-rendering +configuration file that
+ + +centos-art
looks for, inside the +above translation pre-rendering configuration directory, is +`render.conf.sh'. +3.48.2.9 Translation Rendering Default Functionality
+ +In the other hand, if the translation pre-rendering configuration file +doesn't exist, or it isn't written as function script, the +
+centos-art
script ignore translation pre-rendering +configuration functionality and passes to render translation using +default functionality instead. +The translation rendering default functionality takes template +translation directory structure, duplicates it for each release number +specified in the `--filter='release-number'' argument and +produces release-specific directories. As part of template translation +duplication process take place, the
+centos-art
script adds +release-specific replacement commands to each specific translation +file inside release-specific directories. As result, specific +translation files, inside release-specific directories, contain +template translation replacement commands plus, +release-specific replacement commands. ++ + + + +Note
Release-specific replacement commands are standardized +inside
centos-art
script using predifined release +translation markers. Release translation markers are described in the +translation marker section +(see Translation Markers). +3.48.3 Usage
+ +
When `path/to/dir' refers one directory under +`trunk/Translations', this command orverwrites available +translation files using translation templates. +
+When `path/to/dir' refers one directory under +`trunk/Translations', this command renders release-specific +translation files as you specify in the `--filter='pattern'' +argument. In this case, `pattern' not a regular expression but an +number (e.g., `5') or a list of numbers separated by commas +(e.g., `3,4,5,6') that specify the major release of CentOS +distribution you want to render translations for. +
+[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_52.html b/Manuals/en/Html/Repository/repository_52.html
index 35d9e30..c6beeaa 100644
--- a/Manuals/en/Html/Repository/repository_52.html
+++ b/Manuals/en/Html/Repository/repository_52.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_53.html b/Manuals/en/Html/Repository/repository_53.html
index 8fe0bc3..986a076 100644
--- a/Manuals/en/Html/Repository/repository_53.html
+++ b/Manuals/en/Html/Repository/repository_53.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
Translation files, inside `trunk/Translations/Fonts', have the -following structure: +
Translation files, inside `trunk/Translations/Identity/Brands' +translation entry, don't use default rendering translation +functionality, they use the following translation pre-rendering +configuration file instead:
-# ---------------------------------------------------------------------- -# $Id: Fonts.texi 29 2010-09-12 05:32:26Z al $ -# ---------------------------------------------------------------------- - -s!font-family:Denmark!font-family:DejaVu LGC Sans! -s!font-weight:normal!font-weight:bold! -s!font-style:normal!font-style:italic! +/home/centos/artwork/trunk/Translation/Identity/Brands/render.conf.sh-Inside `trunk/Translations/Fonts', there is one translation file -for each font preview image you want to produce. This way, we create -one translation file for each font-family we use somewhere inside -CentOS visual identity. +
Inside `trunk/Translations/Identity/Brands' translation entry, +translation files are symbolic links pointing to the common template +translation structure, inside the translation template (`Tpl/') +directory. +
+Inside `trunk/Translations/Identity/Brands' translation entry, +translation files are created using identity design templates as +reference. The translation pre-rendering script creates a translation +structure where the translation template (`Tpl/') directory +structure applies to each single design template available. +
+For example, if the brands' translation template (`Tpl/') +directory has 30 translation files, and there are 20 design templates; +the brands' translation pre-rendering script creates a translation +structure of symbolic links where the 30 translation files apply the +20 design templates one by one, producing 600 translation symbolic +links as result. At this point, when rendering identity, the +
+centos-art
script considers translation symbolic links as +translation files. +Translation file names, inside brands' translation template +(`Tpl') directory have special meaning:
-+ +Important
Do not create translation files for font-families -not used somewhere inside CentOS visual identity. The font's identity -entry (see section trunk/Identity/Fonts) is used as reference when someone -needs to know which font-families are allowed to use inside CentOS -visual identity. -
3.50.2.1 Conventional file names
- -3.50.2.1 Translation Markers
+Convenctional file names look like `blue.sed', `2c-a.sed', +etc. Replacement commands inside translation file are applied to +design templates and translation file names are used as final image +name. The image dimensions use the same dimensions that design +template has. +
-Inside `trunk/Translations/Identity/Fonts', translation files + +
3.50.2.2 Numeric file names
+ +Numeric file names look like `300.sed', `200.sed', etc. +Replacements commands inside translation files are applied to design +templates, and translation file names are used as final image name. +The final image is saved using an specific `width' defined by the +number part of the translation file name. The image `height' is +automatically scaled based on the previous `width' definition to +maintain the design's ratio. +
+For example, if your design template has 400x200 pixels of dimension, +and you apply a translation file named `300.sed' to it, the final +image you get as result will have 300x100 pixels of dimension. The +same is true if you use higher numbers like `1024.sed', `2048.sed', +etc. In these cases you have bigger images proportionally. +
+As we are using scalable vector graphics to design identity templates, +the image size you produce is not limitted in size. You can use one +design template produced in 400x200 pixels to produce larger or +shorter PNG images using numeric translation files as described +above. +
+ + +3.50.2.3 Translation markers
+ +Inside `trunk/Translations/Identity/Brands/', translation files combine the following translation markers:
Specify which font family to use when rendering font preview images. -
Specify which font weight to use when rendering font preview images. -
Specify which font style to use when rendering font preview images. -
Specify which color to use when rendering brand images. +
++Note
As translation files inside +`trunk/Translations/Identity/Brands' are symbolic links that +point to template translation files, translation markers are defined +inside template translation files. +
Inside `trunk/Translations/Fonts' you use your favorite text
-editor to create translation files. Inside
-`trunk/Translations/Fonts' there is not translation template
-directory (`Tpl/'), nor translation rendering using
-centos-art
script. For example, to create the
-`dejavu_lgc_sans-boldoblique.sed' translation file using
-vim
editor, type the following command:
+
To render brands' translation files, use the following command:
-vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed +centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity/Brands- +3.50.4 See also
3.3 trunk/Identity/Fonts | + | |
3.51 trunk/Translations/Identity/Brands/Tpl | + | |
3.2 trunk/Identity/Brands |
[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_54.html b/Manuals/en/Html/Repository/repository_54.html
index b0c3ca8..698680c 100644
--- a/Manuals/en/Html/Repository/repository_54.html
+++ b/Manuals/en/Html/Repository/repository_54.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_55.html b/Manuals/en/Html/Repository/repository_55.html
index 15ab235..fdbe9ad 100644
--- a/Manuals/en/Html/Repository/repository_55.html
+++ b/Manuals/en/Html/Repository/repository_55.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||
[ < ] | +[ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
Translation files, inside `trunk/Translations/Fonts', have the +following structure: +
+# ---------------------------------------------------------------------- +# $Id: Fonts.texi 29 2010-09-12 05:32:26Z al $ +# ---------------------------------------------------------------------- + +s!font-family:Denmark!font-family:DejaVu LGC Sans! +s!font-weight:normal!font-weight:bold! +s!font-style:normal!font-style:italic! ++
Inside `trunk/Translations/Fonts', there is one translation file +for each font preview image you want to produce. This way, we create +one translation file for each font-family we use somewhere inside +CentOS visual identity. +
+-Important
Do not create translation files for font-families +not used somewhere inside CentOS visual identity. The font's identity +entry (see section trunk/Identity/Fonts) is used as reference when someone +needs to know which font-families are allowed to use inside CentOS +visual identity. +
Inside `trunk/Translations/Identity/Fonts', translation files +combine the following translation markers: +
+Specify which font family to use when rendering font preview images. +
Specify which font weight to use when rendering font preview images. +
Specify which font style to use when rendering font preview images. +
Inside `trunk/Translations/Fonts' you use your favorite text
+editor to create translation files. Inside
+`trunk/Translations/Fonts' there is not translation template
+directory (`Tpl/'), nor translation rendering using
+centos-art
script. For example, to create the
+`dejavu_lgc_sans-boldoblique.sed' translation file using
+vim
editor, type the following command:
+
vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.sed +
3.3 trunk/Identity/Fonts | + |
[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_56.html b/Manuals/en/Html/Repository/repository_56.html
index 2005ab9..c674d5a 100644
--- a/Manuals/en/Html/Repository/repository_56.html
+++ b/Manuals/en/Html/Repository/repository_56.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_57.html b/Manuals/en/Html/Repository/repository_57.html
index a750c43..9cbe7b9 100644
--- a/Manuals/en/Html/Repository/repository_57.html
+++ b/Manuals/en/Html/Repository/repository_57.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_58.html b/Manuals/en/Html/Repository/repository_58.html
index dfbf54a..8150cba 100644
--- a/Manuals/en/Html/Repository/repository_58.html
+++ b/Manuals/en/Html/Repository/repository_58.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
Use the following command to produce translation files based: -
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress -`-- Tpl - |-- en - | |-- 01-welcome.sed - | |-- 02-donate.sed - | `-- 03-yum.sed - `-- es - |-- 01-welcome.sed - |-- 02-donate.sed - `-- 03-yum.sed - |
In order to produce the slide images in PNG format we need to have the -translation files first. So we use the following commands to create -translation files for CentOS 3, 4, and 5 major releases: -
-centos-art render --translation --filter='3,4,5' - |
The above commands will produce the following translation structure: -
-trunk/Translations/Identity/Themes/Distro/Anaconda/Progress -|-- 3 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -|-- 4 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -|-- 5 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -`-- Tpl - |-- en - | |-- 01-welcome.sed - | |-- 02-donate.sed - | `-- 03-yum.sed - `-- es - |-- 01-welcome.sed - |-- 02-donate.sed - `-- 03-yum.sed - |
At this point we have all the translation files we need to produce -Anaconda progress welcome, donate and yum slides images; in English -and Spanish languages; for CentOS 3, CentOS 4, and CentOS 5. That is, -a sum of 18 images around. -
-Now, with translation files in place, let's move to -`trunk/Identity' structure and render them. -
-Translation rendering is described in `trunk/Translations' -documentation entry (see section trunk/Translations). -
-[ < ] | [ > ] | [ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_59.html b/Manuals/en/Html/Repository/repository_59.html
index 2892f77..c424de6 100644
--- a/Manuals/en/Html/Repository/repository_59.html
+++ b/Manuals/en/Html/Repository/repository_59.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
3.56 trunk/Translations/Identity/Widgets | - |
[ << ] | [ Up ] | -[ >> ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_6.html b/Manuals/en/Html/Repository/repository_6.html
index bbb8cb1..93fbd1e 100644
--- a/Manuals/en/Html/Repository/repository_6.html
+++ b/Manuals/en/Html/Repository/repository_6.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
-
+
[ < ] | -[ > ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
Jump to: | B - -C - -H - -S - -T - - |
---|
Jump to: | B - -C - -H - -S - -T - - |
---|
Use the following command to produce translation files based: +
+trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +`-- Tpl + |-- en + | |-- 01-welcome.sed + | |-- 02-donate.sed + | `-- 03-yum.sed + `-- es + |-- 01-welcome.sed + |-- 02-donate.sed + `-- 03-yum.sed + |
In order to produce the slide images in PNG format we need to have the +translation files first. So we use the following commands to create +translation files for CentOS 3, 4, and 5 major releases: +
+centos-art render --translation --filter='3,4,5' + |
The above commands will produce the following translation structure: +
+trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +|-- 3 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +|-- 4 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +|-- 5 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +`-- Tpl + |-- en + | |-- 01-welcome.sed + | |-- 02-donate.sed + | `-- 03-yum.sed + `-- es + |-- 01-welcome.sed + |-- 02-donate.sed + `-- 03-yum.sed + |
At this point we have all the translation files we need to produce +Anaconda progress welcome, donate and yum slides images; in English +and Spanish languages; for CentOS 3, CentOS 4, and CentOS 5. That is, +a sum of 18 images around. +
+Now, with translation files in place, let's move to +`trunk/Identity' structure and render them. +
+Translation rendering is described in `trunk/Translations' +documentation entry (see section trunk/Translations). +
+ + + +[ < ] | -[ > ] | +||||||
[ < ] | +[ > ] | [ << ] | -[ Up ] | -[ >> ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_61.html b/Manuals/en/Html/Repository/repository_61.html
index c8340bc..0ae551a 100644
--- a/Manuals/en/Html/Repository/repository_61.html
+++ b/Manuals/en/Html/Repository/repository_61.html
@@ -13,7 +13,7 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.
-->
-
+
[ < ] | -[ > ] | +||||||||||||||||
[ < ] | +[ > ] | - | [ << ] | -[ Up ] | -[ >> ] | +[ << ] | +[ Up ] | +[ >> ] | [Top] | [Contents] | -[Index] | +[Index] | [ ? ] |
The centos-art.sh
initialization environment.
-
The image rendering flow. -
3.58 trunk/Translations/Identity/Widgets | + |
[ < ] | -[ > ] | +|||||||
[ < ] | +[ > ] | - | [ << ] | -[ Up ] | -[ >> ] | +[ << ] | +[ Up ] | +[ >> ] |
- This document was generated on September, 23 2010 using texi2html 1.76.
+ This document was generated on October, 1 2010 using texi2html 1.76.
diff --git a/Manuals/en/Html/Repository/repository_62.html b/Manuals/en/Html/Repository/repository_62.html
index 7a15dae..fcb2fed 100644
--- a/Manuals/en/Html/Repository/repository_62.html
+++ b/Manuals/en/Html/Repository/repository_62.html
@@ -3,7 +3,7 @@
-
+