From 6904e974cb6b4e3f6ed3eef7f9eb6ff11b947952 Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: Apr 19 2011 01:48:46 +0000 Subject: Update repository documentation manual. --- diff --git a/Manual/Directories/branches.texi b/Manual/Directories/branches.texi index b4e8f8d..231ff96 100755 --- a/Manual/Directories/branches.texi +++ b/Manual/Directories/branches.texi @@ -5,7 +5,7 @@ trunk, branches, tags repository structure. @subheading Description -The @file{branches/} directory structre provides the intermediate +The @file{branches/} directory structure provides the intermediate space for creating several instances of @file{trunk/} directory structure for parallel development and later merging changes back to @file{trunk/} in the same parallel basis. @@ -17,7 +17,7 @@ The @file{branches/} directory structure is unused, so far. @subheading See also @itemize -@item @xref{Directories tags}. -@item @xref{Directories trunk}. -@item Subversion's book (@url{http://svnbook.red-bean.com/}). +@item @ref{Directories tags}. +@item @ref{Directories trunk}. +@item The Subversion book (@url{http://svnbook.red-bean.com/}). @end itemize diff --git a/Manual/Directories/tags.texi b/Manual/Directories/tags.texi index a69c2e9..609583a 100755 --- a/Manual/Directories/tags.texi +++ b/Manual/Directories/tags.texi @@ -5,7 +5,7 @@ branches, tags repository structure. @subheading Description -The @file{tags/} directory structre provides frozen branches. +The @file{tags/} directory structure provides frozen branches. Generally, we use frozen branches to make check-points in time for development lines under @file{branches/} or @file{trunk/} directory structure. @@ -17,8 +17,8 @@ The @file{tags/} directory structure is unused, so far. @subheading See also @itemize -@item @xref{Directories branches}. -@item @xref{Directories trunk}. -@item Subversion's book (@url{http://svnbook.red-bean.com/}). +@item @ref{Directories branches}. +@item @ref{Directories trunk}. +@item The subversion book (@url{http://svnbook.red-bean.com/}). @end itemize diff --git a/Manual/Directories/trunk.texi b/Manual/Directories/trunk.texi index c6818d1..226013a 100644 --- a/Manual/Directories/trunk.texi +++ b/Manual/Directories/trunk.texi @@ -5,58 +5,11 @@ trunk concept in a trunk, branches, tags repository structure. @subheading Description -The @file{trunk/} directory structure is the main development line -inside the CentOS Artwork Repository and organizes the following -work lines: +The @file{trunk/} directory structure provides the main development +line inside the CentOS Artwork Repository. -@table @strong -@item Graphic design -The graphic design work line exists to cover brand design, typography -design and themes design mainly. Additionally, some auxiliar areas -like icon design, illustration design, brushes design, patterns -designs and palettes of colors are also included here for -completeness. - -In this section you'll find how to organize and produce gaphic designs -in the repository. The graphic design work line is the perfect place -to consolidate @emph{The CentOS Artwork SIG}. If you are interested in -producing graphic designs for The CentOS Project, this place is for -you. - -@xref{Directories trunk Identity}, for more information. - -@item Documentation - -The documentation work line exists to describe what each directory -inside the CentOS Artwork Repository is for, the conceptual ideas -behind them and, if possible, how automation scripts make use of them. - -In this section you'll find how to organize and produce the -@emph{CentOS Artwork Repository Manual} (i.e., the documentation -manual you're reading right now). If you are interested in producing -documentation for the repository, this place is for you. - -@xref{Directories trunk Manual}, for more information. - -@item Localization - -The localization work line exists to provide the translation messages -required to produce content in different languages. Translation -messages inside the repository are stored as portable objects (e.g., -.po, .pot) and machine objects (.mo) under @file{trunk/Locales} -directory structure. - -In this section you'll find how to organize and produce translation -messages for @emph{graphic designs}, @emph{documentation} and -@emph{automation scripts} in the repository. This place is perfect to -consolidate @emph{The CentOS Translation SIG}. If you love -translating, you'll find lot of messages waiting for you to translate -here. - -@xref{Directories trunk Locales}, for more information. - -@item Automation +@subsubheading Automation The automation work line exists to standardize content production in CentOS Artwork Repository. There is no need to type several tasks, @@ -70,18 +23,19 @@ documenting directory structures, translating content, etc.). If you can't resist the idea of automating repeatable tasks, then take a look here. -@xref{Directories trunk Scripts}, for more information. -@end table - @subheading Usage -It seems to be no other use for this directory but to organize the -sections described above. +@itemize +@item @xref{Directories trunk Identity}. +@item @xref{Directories trunk Manual}. +@item @xref{Directories trunk Locales}. +@item @xref{Directories trunk Scripts}. +@end itemize @subheading See also @itemize -@item @xref{Directories branches}. -@item @xref{Directories tags}. -@item Subversion's book (@url{http://svnbook.red-bean.com/}). +@item @ref{Directories branches}. +@item @ref{Directories tags}. +@item The Subversion book (@url{http://svnbook.red-bean.com/}). @end itemize diff --git a/Manual/Directories/trunk/Identity.texi b/Manual/Directories/trunk/Identity.texi index 9570a55..b97930f 100644 --- a/Manual/Directories/trunk/Identity.texi +++ b/Manual/Directories/trunk/Identity.texi @@ -53,64 +53,13 @@ visual manifestations were defined: The CentOS Distribution visual manifestation covers all actions related to branding and artwork production required by the The CentOS -Distribution. @xref{Directories trunk Identity Themes Models Default -Distro}. - -The CentOS Distribution is an Enterprise-class Linux Distribution -derived from sources freely provided to the public by a prominent -North American Enterprise Linux vendor. The CentOS Distribution -conforms fully with the upstream vendors redistribution policy and -aims to be 100% binary compatible. (The CentOS Project mainly changes -packages to remove upstream vendor branding and artwork.) - -The CentOS Distribution is developed by a small but growing team of -core developers. In turn the core developers are supported by an -active user community including system administrators, network -administrators, enterprise users, managers, core Linux contributors -and Linux enthusiasts from around the world. - -The upstream vendor has released 4 versions of their -@acronym{EL,Enterprise Linux} product that The CentOS Project rebuilds -the freely available SRPMS for. The upstream vendor releases security -updates as required by circumstances. The CentOS Project releases -rebuilds of security updates as soon as possible. Usually within 24 -hours (our stated goal is with 72 hours, but we are usually much -faster). - -The upstream vendor also releases numbered update sets for major -versions of their EL product from 2 to 4 times per year. There are new -ISOs from the upstream vendor provided for these update sets. Update -sets will be completed as soon as possible after the upstream vendor -releases their version @dots{} generally within 2 weeks. The CentOS -Project follows these conventions as well, so CentOS-3.9 correlates -with EL 3 update 9 and CentOS-4.6 correlates with EL 4 update 6, -CentOS-5.1 correlates to EL 5 update 1, etc. - -One thing some people have problems understanding is that if you have -any CentOS-3 product and update it, you will be updated to the latest -CentOS-3.x version. - -The same is true for CentOS-4 and CentOS-5. If you update any CentOS-4 -product, you will be updated to the latest CentOS-4.x version, or to -the latest CentOS-5.x version if you are updating a CentOS-5 system. -This is exactly the same behavior as the upstream product. Let's -assume that the latest EL4 product is update 6. If you install the -upstream original EL4 CDs (the ones before any update set) and upgrade -via @command{yum}, you will have latest update set installed (EL4 -update 6 in our example). Since all updates within a major release -(CentOS-2, CentOS-3, CentOS-4, CentOS-5) always upgrade to the latest -version when updates are performed (thus mimicking upstream behavior), -only the latest version is maintained in each main tree on The CentOS -Mirrors (@url{http://mirrors.centos.org/}). - -There is a CentOS Vault (@url{http://vault.centos.org/}) containing -old CentOS trees. This vault is a picture of the older tree when it -was removed from the main tree, and does not receive updates. It -should only be used for reference. +Distribution (@pxref{Directories trunk Identity Themes Models Default +Distro}). @item The CentOS Web -The CentOS Web exists to support The CentOS Distribution. +The CentOS Web visual manifestation exists to support The CentOS +Distribution. The CentOS Web covers web applications which let The CentOS Project to manifest its existence on the Internet. Through these web applications @@ -124,7 +73,8 @@ to comply with The CentOS Project Corporate Structure guidelines. @item The CentOS Showroom -The CentOS Showroom exists to promote The CentOS Distribution. +The CentOS Showroom visual manifestation exists to promote The CentOS +Distribution. The CentOS Showroom covers industrial production of objects branded by The CentOS Project (e.g., clothes, stationery and installation media). diff --git a/Manual/Directories/trunk/Identity/Models.texi b/Manual/Directories/trunk/Identity/Models.texi index 60cb2e1..7e764ff 100755 --- a/Manual/Directories/trunk/Identity/Models.texi +++ b/Manual/Directories/trunk/Identity/Models.texi @@ -12,16 +12,9 @@ @subheading Usage -@table @strong -@item Brands - -The CentOS Brand provides the one unique name or trademark that -connects the producer with their products. In this case, the producer -is The CentOS Project and the products are The CentOS Project visual -manifestations. - -@xref{Directories trunk Identity Models Brands}, for more information. -@end table +@itemize +@item @dots{} +@end itemize @subheading See also diff --git a/Manual/Directories/trunk/Identity/Models/Brands.texi b/Manual/Directories/trunk/Identity/Models/Brands.texi index 7e30abf..9fb611d 100644 --- a/Manual/Directories/trunk/Identity/Models/Brands.texi +++ b/Manual/Directories/trunk/Identity/Models/Brands.texi @@ -1,12 +1,15 @@ @subheading Goals -@itemize -@item ... -@end itemize +This section describes The CentOS Brand design models. @subheading Description -The CentOS logo is the main visual representation of the CentOS +The CentOS Brand provides the one unique name or trademark that +connects the producer with their products. In this case, the producer +is The CentOS Project and the products are The CentOS Project visual +manifestations. + +The CentOS Brand is the main visual representation of the CentOS project so the typography used in it must be the same always, no matter where it be shown. It also has to be clear enough to dismiss any confussion between similar typefaces (e.g., the number one (1) diff --git a/Manual/Directories/trunk/Identity/Themes.texi b/Manual/Directories/trunk/Identity/Themes.texi index 5f0bd58..6783cfa 100644 --- a/Manual/Directories/trunk/Identity/Themes.texi +++ b/Manual/Directories/trunk/Identity/Themes.texi @@ -5,8 +5,6 @@ production of CentOS themes. @subheading Description -@subsubheading Work Flow - Initially, we start working themes on their trunk development line (e.g., @file{trunk/Identity/Themes/Motifs/TreeFlower/}), here we organize information that cannot be produced automatically (i.e., @@ -78,14 +76,14 @@ 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. -@menu -* Directories trunk Identity Themes Models:: -* Directories trunk Identity Themes Motifs:: -@end menu +@itemize +@item @xref{Directories trunk Identity Themes Models}. +@item @xref{Directories trunk Identity Themes Motifs}. +@end itemize @subheading See also -@menu -* Directories trunk Identity:: -* Directories trunk:: -@end menu +@itemize +@item @ref{Directories trunk Identity}. +@item @ref{Directories trunk}. +@end itemize diff --git a/Manual/Directories/trunk/Identity/Themes/Models.texi b/Manual/Directories/trunk/Identity/Themes/Models.texi index cfd9740..3ce12c8 100644 --- a/Manual/Directories/trunk/Identity/Themes/Models.texi +++ b/Manual/Directories/trunk/Identity/Themes/Models.texi @@ -1,8 +1,6 @@ @subheading Goals -@itemize -@item Organize theme models. -@end itemize +This section describes design models from The CentOS Themes. @subheading Description @@ -16,16 +14,15 @@ 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. -@subheading Usage +@subsubheading Default Design Model -@table @strong -@item Default Design Model Default Design Models for CentOS Themes provide the common structural information (e.g., image dimensions, translation markers, trademark position, etc.) the @command{centos-art} script uses to produce images when no other design model is specified. -@item Alternative Design Models +@subsubheading Alternative Design Models + 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 @@ -33,9 +30,17 @@ 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. -@end table + +@subheading Usage + +@itemize +@item @xref{Directories trunk Identity Themes Models Default}. +@end itemize @subheading See also -@menu -@end menu +@itemize +@item @ref{Directories trunk Identity Themes}. +@item @ref{Directories trunk Identity}. +@item @ref{Directories trunk}. +@end itemize diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default.texi index 99bf17b..46899fc 100644 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default.texi +++ b/Manual/Directories/trunk/Identity/Themes/Models/Default.texi @@ -1,42 +1,22 @@ @subheading Goals -Default Design Models for CentOS Themes provide design models for the -following components: - -@table @strong -@item Distribution -Design models for CentOS Distribution (e.g., Anaconda, Firstboot, Gdm, -Grub, Gsplash, Kdm, Ksplash, Rhgb and Syslinux, etc.). -@xref{Directories trunk Identity Themes Models Default Distro}, for -more information. - -@item Concept -Design models to illustrate Artistic Motifs Concepts. -@xref{Directories trunk Identity Themes Models Default Concept}, for -more information. - -@item Promotion -Design models for CentOS Promotion stuff (e.g., installation media, -posters, etc.). --- @strong{Removed}(xref:Directories trunk Identity Themes Models Default -Promo) ---, for more information. -@end table +This section describes the default design model of The CentOS Themes. @subheading Description -This directory implements the concept of @emph{Default Design Models -for CentOS Themes}. Default Design Models for CentOS Themes provide -the common structural information (e.g., image dimensions, translation -markers, trademark position, etc.) the @command{centos-art} script -uses to produce images when no other design model is specified. +The @file{trunk/Identity/Themes/Models/Default} directory implements +the concept of @emph{Default Design Model} for The CentOS Themes. The +CentOS Themes Default Design Model provides the common structural +information (e.g., image dimensions, translation markers, trademark +position, etc.) the @command{centos-art} script uses to produce images +when no other design model is specified. Deisgn models in this directory do use the @emph{CentOS Release Brand}. The CentOS Release Brand is a combination of both The CentOS Type and The CentOS Release Schema used to illustrate the major -release of CentOS Distribution the image produced belongs to. ---- @strong{Removed}(xref:Directories trunk Identity Models Tpl Brands) ---, for more -information. - -@subheading Usage +release of The CentOS Distribution the image produced belongs to. --- +@strong{Removed}(xref:Directories trunk Identity Models Tpl Brands) +---, for more information. The CentOS Project maintains near to four different major releases of CentOS Distribution. Each major release of CentOS Distribution has @@ -83,6 +63,13 @@ Project corporate visual identity. It should be very clear for everyone which major release of CentOS Distribution is being used. @end quotation +@subheading Usage + +@itemize +@item @xref{Directories trunk Identity Themes Models Default Distro}. +@item @xref{Directories trunk Identity Themes Models Default Concept}. +@end itemize + @subheading See also @itemize diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro.texi index 16ea20f..bbd5d46 100644 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro.texi +++ b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro.texi @@ -1,10 +1,70 @@ @subheading Goals -This directory provides design models to produce image files for the -following CentOS Distribution components: +This section organizes default design models for different major +releases of CentOS Distribution. @subheading Description +In order to better understatand how this visual manifestation is +organized, it is necessary to consider what The CentOS Distribution is +and how it is released. + +@subsubheading The CentOS Distribution + +The CentOS Distribution is an Enterprise-class Linux Distribution +derived from sources freely provided to the public by a prominent +North American Enterprise Linux vendor. The CentOS Distribution +conforms fully with the upstream vendors redistribution policy and +aims to be 100% binary compatible. (The CentOS Project mainly changes +packages to remove upstream vendor branding and artwork.) + +The CentOS Distribution is developed by a small but growing team of +core developers. In turn the core developers are supported by an +active user community including system administrators, network +administrators, enterprise users, managers, core Linux contributors +and Linux enthusiasts from around the world. + +@subsubheading The CentOS Distribution Release Schema + +The upstream vendor has released 4 versions of their +@acronym{EL,Enterprise Linux} product that The CentOS Project rebuilds +the freely available SRPMS for. The upstream vendor releases security +updates as required by circumstances. The CentOS Project releases +rebuilds of security updates as soon as possible. Usually within 24 +hours (our stated goal is with 72 hours, but we are usually much +faster). + +The upstream vendor also releases numbered update sets for major +versions of their EL product from 2 to 4 times per year. There are new +ISOs from the upstream vendor provided for these update sets. Update +sets will be completed as soon as possible after the upstream vendor +releases their version @dots{} generally within 2 weeks. The CentOS +Project follows these conventions as well, so CentOS-3.9 correlates +with EL 3 update 9 and CentOS-4.6 correlates with EL 4 update 6, +CentOS-5.1 correlates to EL 5 update 1, etc. + +One thing some people have problems understanding is that if you have +any CentOS-3 product and update it, you will be updated to the latest +CentOS-3.x version. + +The same is true for CentOS-4 and CentOS-5. If you update any CentOS-4 +product, you will be updated to the latest CentOS-4.x version, or to +the latest CentOS-5.x version if you are updating a CentOS-5 system. +This is exactly the same behavior as the upstream product. Let's +assume that the latest EL4 product is update 6. If you install the +upstream original EL4 CDs (the ones before any update set) and upgrade +via @command{yum}, you will have latest update set installed (EL4 +update 6 in our example). Since all updates within a major release +(CentOS-2, CentOS-3, CentOS-4, CentOS-5) always upgrade to the latest +version when updates are performed (thus mimicking upstream behavior), +only the latest version is maintained in each main tree on The CentOS +Mirrors (@url{http://mirrors.centos.org/}). + +There is a CentOS Vault (@url{http://vault.centos.org/}) containing +old CentOS trees. This vault is a picture of the older tree when it +was removed from the main tree, and does not receive updates. It +should only be used for reference. + The CentOS Distribution visual style is controlled by image files. These image files are packaged inside The CentOS Distribution and made visible once such packages are installed and executed. The way to go @@ -15,39 +75,25 @@ CentOS Distribution. @subheading Usage -This directory provides organizationl structure to store default -design models for CentOS Themes of CentOS Distribution and so it -should be considered to be used. - -When a new component is added to CentOS Distribution, this is the -directory you need to go for specifying design models for image files -inside such component. - -The procedure to follow is creatig a directory for each component -using its very same name (e.g., the directory @file{Anaconda} stores -image files for Anaconda component, the installer program). Inside the -directory, you need to create one scalable vector graphic for each -image file inside the component you want to produce images for. This, -in order to set image dimensions, image file-name, position of -trademarks in the final image, translation markers and whatever common -information you need to have specified in them when rendered by -@command{centos-art} script. - Sometimes, between major releases, image files inside packages can be -added, removed or just change their names. In order to describe such -image files variations, the design models directory structure is -organized in the same way the file variations are introduced (i.e., -through The CentOS Project Release Schema). So, each major release of -CentOS Distribution does have its own design model directory structure -in this directory. +added, removed or just get the name changed. In order to describe such +variations, the design models directory structure is organized in the +same way the variations are introduced (i.e., through The CentOS +Distribution Release Schema). So, each major release of The CentOS +Distribution has its own design model directory structure. -When a whole package is removed from one or all CentOS Distribution -major releases, the design models directory structure releated to it -is no longer used. However it could be very useful for historical -reasons. Also, someone could feel motivated enough to keep himself -documenting it or supporting it for whatever reason. +When a new package/component is added to one or all the major releases +of The CentOS Distribution, a design model directory structure for +that component needs to be created. Later, it is filled up with +related design models. Design models are created for each image file +inside the component that need to be rebuilt in order to set the +visual style and brand information correctly. -@subsubheading Major release 5 +When a package is removed from one or all major releases of The CentOS +Distribution, the design model directory structure releated to that +package/component is no longer used. However, it could be very useful +for historical reasons. Also, someone could feel motivation enough to +keep himself documenting it or supporting it for whatever reason. @itemize @item @xref{Directories trunk Identity Themes Models Default Distro @@ -56,6 +102,10 @@ documenting it or supporting it for whatever reason. @subheading See also -@menu -* Directories trunk Identity Themes Models Default:: -@end menu +@itemize +@item @ref{Directories trunk Identity Themes Models Default}. +@item @ref{Directories trunk Identity Themes Models}. +@item @ref{Directories trunk Identity Themes}. +@item @ref{Directories trunk Identity}. +@item @ref{Directories trunk}. +@end itemize diff --git a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5.texi b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5.texi index cc66c51..19e11c5 100755 --- a/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5.texi +++ b/Manual/Directories/trunk/Identity/Themes/Models/Default/Distro/5.texi @@ -12,68 +12,24 @@ @subheading Usage -@table @strong -@item Syslinux -Contains design models for syslinux, the program used to boot the -CentOS Distribution installation media. - @itemize @item @xref{Directories trunk Identity Themes Models Default Distro 5 Syslinux}. +@item @xref{Directories trunk Identity Themes Models Default Distro 5 Anaconda}. +@item @xref{Directories trunk Identity Themes Models Default Distro 5 Rhgb}. +@item @xref{Directories trunk Identity Themes Models Default Distro 5 Gdm}. +@item @xref{Directories trunk Identity Themes Models Default Distro 5 Kdm}. +@item @xref{Directories trunk Identity Themes Models Default Distro 5 Grub}. +@item @xref{Directories trunk Identity Themes Models Default Distro 5 Gsplash}. +@item @xref{Directories trunk Identity Themes Models Default Distro 5 Ksplash}. @end itemize -@item Anaconda -Contains design models for Anaconda, the program used to install -CentOS Distribution. - -@itemize -@item @xref{Directories trunk Identity Themes Models Default Distro 5 -Anaconda}. -@end itemize - -@item Firstboot -Contains design models for the first boot program used to configure -the maching onece installed. --- @strong{Removed}(xref:Directories trunk Identity Themes -Models Default Distro Firstboot) ---, for more information. - -@item Rhgb -Contains design models for CentOS Graphical Boot, the program used to -show the boot process from Grub to Display Manager. --- @strong{Removed}(xref:Directories -trunk Identity Themes Models Default Distro Rhgb) ---, for more -information. - -@item Gdm -Contains design models for GNOME Display Manager, the program used to -log into the manchine once installed and configured. --- @strong{Removed}(xref:Directories -trunk Identity Themes Models Default Distro Gdm) ---, for more -information. - -@item Kdm -Contains design models for KDE Display Manager, the program used to -log into the manchine once installed and configured. @xref{Directories -trunk Identity Themes Models Default Distro 5 Kdm}, for more -information. - -@item Grub -Contains design models for GRUB (Grand Unified Boot Loader), the -program used to boot the machine into an operating system. -@xref{Directories trunk Identity Themes Models Default Distro 5 Kdm}, for -more information. - -@item Gsplash -Contains design models for GNOME splash, the program used to show the -progress information while user's graphical session is loading. -@xref{Directories trunk Identity Themes Models Default Distro 5 Gsplash}, -for more information. - -@item Ksplash -Contains design models for KDE splash, the program used to show the -progress information while user's graphical session is loading. -@xref{Directories trunk Identity Themes Models Default Distro 5 Ksplash}, -for more information. -@end table - @subheading See also @itemize -@item ... +@item @ref{Directories trunk Identity Themes Models Default Distro}. +@item @ref{Directories trunk Identity Themes Models Default}. +@item @ref{Directories trunk Identity Themes Models}. +@item @ref{Directories trunk Identity Themes}. +@item @ref{Directories trunk Identity}. +@item @ref{Directories trunk}. @end itemize diff --git a/Manual/Directories/trunk/Locales.texi b/Manual/Directories/trunk/Locales.texi index 7e5457c..cec803d 100644 --- a/Manual/Directories/trunk/Locales.texi +++ b/Manual/Directories/trunk/Locales.texi @@ -1,5 +1,14 @@ -The @file{trunk/Locales} directory exists to store the translation -messages used to produce content in different languages. +@subheading Goals + +The @file{trunk/Locales} directory structure provides the localization +work line and its main goal is provide the translation messages +required to produce content in different languages. + +@subheading Description + +Translation messages inside the repository are stored as portable +objects (e.g., .po, .pot) and machine objects (.mo) under +@file{trunk/Locales} directory structure. Translation messages are organized using the directory structure of the component being translated. For example, if we want to provide @@ -50,7 +59,15 @@ the file that contain the translation messages themselves. Automation of localization tasks is achived through the @code{locale} functionality of command-line interface. -@menu -* Directories trunk Scripts Functions Locale:: -@end menu +@subheading Usage + +@itemize +@item ... +@end itemize + +@subheading See also + +@itemize +@ref{Directories trunk Scripts Functions Locale} +@end itemize diff --git a/Manual/Directories/trunk/Manual.texi b/Manual/Directories/trunk/Manual.texi index e226b31..081eebf 100644 --- a/Manual/Directories/trunk/Manual.texi +++ b/Manual/Directories/trunk/Manual.texi @@ -1,8 +1,10 @@ @subheading Goals -@itemize -@item ... -@end itemize +This @file{trunk/Manual} directory structure provides the +documentation work line. The main goal of documentation work line is +describe what each directory inside the CentOS Artwork Repository is +for, the conceptual ideas behind them and, if possible, how automation +scripts make use of them. @subheading Description diff --git a/Manual/repository.info.bz2 b/Manual/repository.info.bz2 index 1574ac2..694fc2c 100644 Binary files a/Manual/repository.info.bz2 and b/Manual/repository.info.bz2 differ diff --git a/Manual/repository.pdf b/Manual/repository.pdf index 5db0560..1fddbae 100644 Binary files a/Manual/repository.pdf and b/Manual/repository.pdf differ diff --git a/Manual/repository.txt.bz2 b/Manual/repository.txt.bz2 index 90c50ec..6c68379 100644 Binary files a/Manual/repository.txt.bz2 and b/Manual/repository.txt.bz2 differ diff --git a/Manual/repository.xhtml.tar.bz2 b/Manual/repository.xhtml.tar.bz2 index 2af6031..db6ba3b 100644 Binary files a/Manual/repository.xhtml.tar.bz2 and b/Manual/repository.xhtml.tar.bz2 differ diff --git a/Manual/repository.xml b/Manual/repository.xml index ae5f7de..4373f97 100644 --- a/Manual/repository.xml +++ b/Manual/repository.xml @@ -594,43 +594,43 @@ centos-art help --read turnk/Identity/Themes/Motifs/TreeFlower/3 - Directories trunk Identity Themes Models Default Distro 5 Syslinux - Directories trunk Identity Themes Models Default Distro 5 Syslinux + Directories trunk Identity Themes Models Default Distro 5 Firstboot + Directories trunk Identity Themes Models Default Distro 5 Firstboot - Directories trunk Identity Themes Models Default Distro Firstboot - Directories trunk Identity Themes Models Default Distro Firstboot + Directories trunk Identity Themes Models Default Distro 5 Gdm + Directories trunk Identity Themes Models Default Distro 5 Gdm - Directories trunk Identity Themes Models Default Distro Gdm - Directories trunk Identity Themes Models Default Distro Gdm + Directories trunk Identity Themes Models Default Distro 5 Grub + Directories trunk Identity Themes Models Default Distro 5 Grub - Directories trunk Identity Themes Models Default Distro Grub - Directories trunk Identity Themes Models Default Distro Grub + Directories trunk Identity Themes Models Default Distro 5 Gsplash + Directories trunk Identity Themes Models Default Distro 5 Gsplash - Directories trunk Identity Themes Models Default Distro Gsplash - Directories trunk Identity Themes Models Default Distro Gsplash + Directories trunk Identity Themes Models Default Distro 5 Kdm + Directories trunk Identity Themes Models Default Distro 5 Kdm - Directories trunk Identity Themes Models Default Distro Kdm - Directories trunk Identity Themes Models Default Distro Kdm + Directories trunk Identity Themes Models Default Distro 5 Ksplash + Directories trunk Identity Themes Models Default Distro 5 Ksplash - Directories trunk Identity Themes Models Default Distro Ksplash - Directories trunk Identity Themes Models Default Distro Ksplash + Directories trunk Identity Themes Models Default Distro 5 Rhgb + Directories trunk Identity Themes Models Default Distro 5 Rhgb - Directories trunk Identity Themes Models Default Distro Rhgb - Directories trunk Identity Themes Models Default Distro Rhgb + Directories trunk Identity Themes Models Default Distro 5 Syslinux + Directories trunk Identity Themes Models Default Distro 5 Syslinux @@ -731,20 +731,20 @@ centos-art help --read turnk/Identity/Themes/Motifs/TreeFlower/3 Goals This directory implements the Subversion's branches concept in a trunk, branches, tags repository structure. Description - The branches/ directory structre provides the intermediate space for creating several instances of trunk/ directory structure for parallel development and later merging changes back to trunk/ in the same parallel basis. + The branches/ directory structure provides the intermediate space for creating several instances of trunk/ directory structure for parallel development and later merging changes back to trunk/ in the same parallel basis. Usage The branches/ directory structure is unused, so far. See also • - See Directories tags. + Directories tags. - See Directories trunk. + Directories trunk. - Subversion's book (http://svnbook.red-bean.com/). + The Subversion book (http://svnbook.red-bean.com/). @@ -760,20 +760,20 @@ centos-art help --read turnk/Identity/Themes/Motifs/TreeFlower/3 Goals This directory implements the Subversion's tags concept in a trunk, branches, tags repository structure. Description - The tags/ directory structre provides frozen branches. Generally, we use frozen branches to make check-points in time for development lines under branches/ or trunk/ directory structure. + The tags/ directory structure provides frozen branches. Generally, we use frozen branches to make check-points in time for development lines under branches/ or trunk/ directory structure. Usage The tags/ directory structure is unused, so far. See also • - See Directories branches. + Directories branches. - See Directories trunk. + Directories trunk. - Subversion's book (http://svnbook.red-bean.com/). + The subversion book (http://svnbook.red-bean.com/). @@ -789,54 +789,37 @@ centos-art help --read turnk/Identity/Themes/Motifs/TreeFlower/3 Goals The trunk/ directory structure implements the Subversion's trunk concept in a trunk, branches, tags repository structure. Description - The trunk/ directory structure is the main development line inside the CentOS Artwork Repository and organizes the following work lines: - - - Graphic design - - The graphic design work line exists to cover brand design, typography design and themes design mainly. Additionally, some auxiliar areas like icon design, illustration design, brushes design, patterns designs and palettes of colors are also included here for completeness. - In this section you'll find how to organize and produce gaphic designs in the repository. The graphic design work line is the perfect place to consolidate The CentOS Artwork SIG. If you are interested in producing graphic designs for The CentOS Project, this place is for you. - See Directories trunk Identity, for more information. - - - - Documentation - - The documentation work line exists to describe what each directory inside the CentOS Artwork Repository is for, the conceptual ideas behind them and, if possible, how automation scripts make use of them. - In this section you'll find how to organize and produce the CentOS Artwork Repository Manual (i.e., the documentation manual you're reading right now). If you are interested in producing documentation for the repository, this place is for you. - See Directories trunk Manual, for more information. - - - - Localization - - The localization work line exists to provide the translation messages required to produce content in different languages. Translation messages inside the repository are stored as portable objects (e.g., .po, .pot) and machine objects (.mo) under trunk/Locales directory structure. - In this section you'll find how to organize and produce translation messages for graphic designs, documentation and automation scripts in the repository. This place is perfect to consolidate The CentOS Translation SIG. If you love translating, you'll find lot of messages waiting for you to translate here. - See Directories trunk Locales, for more information. - - - - Automation - - The automation work line exists to standardize content production in CentOS Artwork Repository. There is no need to type several tasks, time after time, if they can be programmed into just one executable script. - In this section you'll find how to organize and extend the centos-art.sh script, a bash scripts specially designed to automate most frequent tasks in the repository (e.g., image rendition, documenting directory structures, translating content, etc.). If you can't resist the idea of automating repeatable tasks, then take a look here. - See Directories trunk Scripts, for more information. - - -
+ The trunk/ directory structure provides the main development line inside the CentOS Artwork Repository. + Automation + The automation work line exists to standardize content production in CentOS Artwork Repository. There is no need to type several tasks, time after time, if they can be programmed into just one executable script. + In this section you'll find how to organize and extend the centos-art.sh script, a bash scripts specially designed to automate most frequent tasks in the repository (e.g., image rendition, documenting directory structures, translating content, etc.). If you can't resist the idea of automating repeatable tasks, then take a look here. Usage - It seems to be no other use for this directory but to organize the sections described above. + + • + + See Directories trunk Identity. + + + See Directories trunk Manual. + + + See Directories trunk Locales. + + + See Directories trunk Scripts. + + See also • - See Directories branches. + Directories branches. - See Directories tags. + Directories tags. - Subversion's book (http://svnbook.red-bean.com/). + The Subversion book (http://svnbook.red-bean.com/). @@ -869,27 +852,20 @@ centos-art help --read turnk/Identity/Themes/Motifs/TreeFlower/3 The CentOS Distribution - The CentOS Distribution visual manifestation covers all actions related to branding and artwork production required by the The CentOS Distribution. See Directories trunk Identity Themes Models Default Distro. - The CentOS Distribution is an Enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor. The CentOS Distribution conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. (The CentOS Project mainly changes packages to remove upstream vendor branding and artwork.) - The CentOS Distribution is developed by a small but growing team of core developers. In turn the core developers are supported by an active user community including system administrators, network administrators, enterprise users, managers, core Linux contributors and Linux enthusiasts from around the world. - The upstream vendor has released 4 versions of their ELEnterprise Linux product that The CentOS Project rebuilds the freely available SRPMS for. The upstream vendor releases security updates as required by circumstances. The CentOS Project releases rebuilds of security updates as soon as possible. Usually within 24 hours (our stated goal is with 72 hours, but we are usually much faster). - The upstream vendor also releases numbered update sets for major versions of their EL product from 2 to 4 times per year. There are new ISOs from the upstream vendor provided for these update sets. Update sets will be completed as soon as possible after the upstream vendor releases their version &dots; generally within 2 weeks. The CentOS Project follows these conventions as well, so CentOS-3.9 correlates with EL 3 update 9 and CentOS-4.6 correlates with EL 4 update 6, CentOS-5.1 correlates to EL 5 update 1, etc. - One thing some people have problems understanding is that if you have any CentOS-3 product and update it, you will be updated to the latest CentOS-3.x version. - The same is true for CentOS-4 and CentOS-5. If you update any CentOS-4 product, you will be updated to the latest CentOS-4.x version, or to the latest CentOS-5.x version if you are updating a CentOS-5 system. This is exactly the same behavior as the upstream product. Let's assume that the latest EL4 product is update 6. If you install the upstream original EL4 CDs (the ones before any update set) and upgrade via yum, you will have latest update set installed (EL4 update 6 in our example). Since all updates within a major release (CentOS-2, CentOS-3, CentOS-4, CentOS-5) always upgrade to the latest version when updates are performed (thus mimicking upstream behavior), only the latest version is maintained in each main tree on The CentOS Mirrors (http://mirrors.centos.org/). - There is a CentOS Vault (http://vault.centos.org/) containing old CentOS trees. This vault is a picture of the older tree when it was removed from the main tree, and does not receive updates. It should only be used for reference. + The CentOS Distribution visual manifestation covers all actions related to branding and artwork production required by the The CentOS Distribution (see Directories trunk Identity Themes Models Default Distro). The CentOS Web - The CentOS Web exists to support The CentOS Distribution. + The CentOS Web visual manifestation exists to support The CentOS Distribution. The CentOS Web covers web applications which let The CentOS Project to manifest its existence on the Internet. Through these web applications The CentOS Project provides Corporate Communication. These web applications are free software and come from different providers which distribute their work with predefined visual styles. Frequently, these predefined visual styles have no visual relation among themselves and introduce some visual contraditions when they all are put together. These visual contraditions need to be removed in order to comply with The CentOS Project Corporate Structure guidelines. The CentOS Showroom - The CentOS Showroom exists to promote The CentOS Distribution. + The CentOS Showroom visual manifestation exists to promote The CentOS Distribution. The CentOS Showroom covers industrial production of objects branded by The CentOS Project (e.g., clothes, stationery and installation media). These branded objects are for distribution on social events and/or shops. They provide a way of both promotion and monetary incomming to aliviate The CentOS Project expenses (e.g., electrical power, hosting, servers, full-time-developers, etc.), in a similar way as donations do. @@ -1159,15 +1135,12 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes Usage - - - Brands - - The CentOS Brand provides the one unique name or trademark that connects the producer with their products. In this case, the producer is The CentOS Project and the products are The CentOS Project visual manifestations. - See Directories trunk Identity Models Brands, for more information. - - -
+ + • + + &dots; + + See also • @@ -1186,14 +1159,10 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes The <file>trunk/Identity/Models/Brands</file> Directory Directories trunk Identity Models Brands Goals - - • - - ... - - + This section describes The CentOS Brand design models. Description - The CentOS logo is the main visual representation of the CentOS project so the typography used in it must be the same always, no matter where it be shown. It also has to be clear enough to dismiss any confussion between similar typefaces (e.g., the number one (1) sometimes is confuesed with the letter el (l) or letter ai (i)). + The CentOS Brand provides the one unique name or trademark that connects the producer with their products. In this case, the producer is The CentOS Project and the products are The CentOS Project visual manifestations. + The CentOS Brand is the main visual representation of the CentOS project so the typography used in it must be the same always, no matter where it be shown. It also has to be clear enough to dismiss any confussion between similar typefaces (e.g., the number one (1) sometimes is confuesed with the letter el (l) or letter ai (i)). As convenction, the word CentOS uses Denmark typography as base, both for the word CentOS and the phrase Community Enterprise Operating System. The phrase size of CentOS logo is half the size in poits the word CentOS has and it below CentOS word and aligned with it on the left. The distance between CentOS word and phrase Community Enterprise Operating System have the size in points the phrase has. Figure @@ -1292,7 +1261,6 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes Goals The trunk/Identity/Themes/ directory exists to organize production of CentOS themes. Description - Work Flow Initially, we start working themes on their trunk development line (e.g., trunk/Identity/Themes/Motifs/TreeFlower/), here we organize information that cannot be produced automatically (i.e., background images, concepts, color information, screenshots, etc.). Later, when theme trunk development line is considered “ready” for implementation (e.g., all required backgrounds have been designed), we create a branch for it (e.g., branches/Identity/Themes/Motifs/TreeFlower/1/). Once the branch has been created, we forget that branch and continue working the trunk development line while others (e.g., an artwork quality assurance team) test the new branch for tunning it up. Once the branch has been tunned up, and considered “ready” for release, it is freezed under tags/ directory (e.g., tags/Identity/Themes/Motifs/TreeFower/1.0/) for packagers, webmasters, promoters, and anyone who needs images from that CentOS theme the tag was created for. @@ -1306,31 +1274,25 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes Before releasing a new major release of CentOS distribution we create a branch for one of several theme development lines available inside the CentOS Artwork Repository, perform quality assurance on it, and later, freeze that branch using tags. Once a the theme branch has been frozen (under tags/ directory), CentOS Packagers (the persons whom build CentOS distribution) can use that frozen branch as source location to fulfill CentOS distribution artwork needs. The same applies to CentOS Webmasters (the persons whom build CentOS websites), and any other visual manifestation required by the project. Usage 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. - - - Directories trunk Identity Themes Models - Directories trunk Identity Themes Models - - - - Directories trunk Identity Themes Motifs - Directories trunk Identity Themes Motifs - - - + + • + + See Directories trunk Identity Themes Models. + + + See Directories trunk Identity Themes Motifs. + + See also - - - Directories trunk Identity - Directories trunk Identity - - - - Directories trunk - Directories trunk - - - + + • + + Directories trunk Identity. + + + Directories trunk. + + @@ -1342,33 +1304,34 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes The <file>trunk/Identity/Themes/Models</file> Directory Directories trunk Identity Themes Models Goals + This section describes design models from The CentOS Themes. + Description + 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. + Default Design Model + Default Design Models for CentOS Themes provide the common structural information (e.g., image dimensions, translation markers, trademark position, etc.) the centos-art script uses to produce images when no other design model is specified. + Alternative Design Models + 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. + Usage • - Organize theme models. + See Directories trunk Identity Themes Models Default. - Description - 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. - Usage - - - Default Design Model - - Default Design Models for CentOS Themes provide the common structural information (e.g., image dimensions, translation markers, trademark position, etc.) the centos-art script uses to produce images when no other design model is specified. - - - - Alternative Design Models - - 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. - - -
See also - - + + • + + Directories trunk Identity Themes. + + + Directories trunk Identity. + + + Directories trunk. + + @@ -1380,31 +1343,10 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes The <file>trunk/Identity/Themes/Models/Default</file> Directory Directories trunk Identity Themes Models Default Goals - Default Design Models for CentOS Themes provide design models for the following components: - - - Distribution - - Design models for CentOS Distribution (e.g., Anaconda, Firstboot, Gdm, Grub, Gsplash, Kdm, Ksplash, Rhgb and Syslinux, etc.). See Directories trunk Identity Themes Models Default Distro, for more information. - - - - Concept - - Design models to illustrate Artistic Motifs Concepts. See Directories trunk Identity Themes Models Default Concept, for more information. - - - - Promotion - - Design models for CentOS Promotion stuff (e.g., installation media, posters, etc.). — Removed(xref:Directories trunk Identity Themes Models Default Promo) —, for more information. - - -
+ This section describes the default design model of The CentOS Themes. Description - This directory implements the concept of Default Design Models for CentOS Themes. Default Design Models for CentOS Themes provide the common structural information (e.g., image dimensions, translation markers, trademark position, etc.) the centos-art script uses to produce images when no other design model is specified. - Deisgn models in this directory do use the CentOS Release Brand. The CentOS Release Brand is a combination of both The CentOS Type and The CentOS Release Schema used to illustrate the major release of CentOS Distribution the image produced belongs to. — Removed(xref:Directories trunk Identity Models Tpl Brands) —, for more information. - Usage + The trunk/Identity/Themes/Models/Default directory implements the concept of Default Design Model for The CentOS Themes. The CentOS Themes Default Design Model provides the common structural information (e.g., image dimensions, translation markers, trademark position, etc.) the centos-art script uses to produce images when no other design model is specified. + Deisgn models in this directory do use the CentOS Release Brand. The CentOS Release Brand is a combination of both The CentOS Type and The CentOS Release Schema used to illustrate the major release of The CentOS Distribution the image produced belongs to. — Removed(xref:Directories trunk Identity Models Tpl Brands) —, for more information. The CentOS Project maintains near to four different major releases of CentOS Distribution. Each major release of CentOS Distribution has internal differences that make them unique and, at the same time, each CentOS Distribution individually is tagged into the one unique visual manifestation (i.e., Distribution). So, how could we implement the monolithic visual structure in one visual manifestation that has internal difference? To answer this question we broke the question in two parts and later combined the resultant answers to build a possible solution. @@ -1430,6 +1372,16 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes Important Remarking the CentOS Release Schema inside each major release of CentOS Distribution —or similar visual manifestations— takes high attention inside The CentOS Project corporate visual identity. It should be very clear for everyone which major release of CentOS Distribution is being used. + Usage + + • + + See Directories trunk Identity Themes Models Default Distro. + + + See Directories trunk Identity Themes Models Default Concept. + + See also • @@ -1488,16 +1440,23 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes The <file>trunk/Identity/Themes/Models/Default/Distro</file> Directory Directories trunk Identity Themes Models Default Distro Goals - This directory provides design models to produce image files for the following CentOS Distribution components: + This section organizes default design models for different major releases of CentOS Distribution. Description + In order to better understatand how this visual manifestation is organized, it is necessary to consider what The CentOS Distribution is and how it is released. + The CentOS Distribution + The CentOS Distribution is an Enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor. The CentOS Distribution conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. (The CentOS Project mainly changes packages to remove upstream vendor branding and artwork.) + The CentOS Distribution is developed by a small but growing team of core developers. In turn the core developers are supported by an active user community including system administrators, network administrators, enterprise users, managers, core Linux contributors and Linux enthusiasts from around the world. + The CentOS Distribution Release Schema + The upstream vendor has released 4 versions of their ELEnterprise Linux product that The CentOS Project rebuilds the freely available SRPMS for. The upstream vendor releases security updates as required by circumstances. The CentOS Project releases rebuilds of security updates as soon as possible. Usually within 24 hours (our stated goal is with 72 hours, but we are usually much faster). + The upstream vendor also releases numbered update sets for major versions of their EL product from 2 to 4 times per year. There are new ISOs from the upstream vendor provided for these update sets. Update sets will be completed as soon as possible after the upstream vendor releases their version &dots; generally within 2 weeks. The CentOS Project follows these conventions as well, so CentOS-3.9 correlates with EL 3 update 9 and CentOS-4.6 correlates with EL 4 update 6, CentOS-5.1 correlates to EL 5 update 1, etc. + One thing some people have problems understanding is that if you have any CentOS-3 product and update it, you will be updated to the latest CentOS-3.x version. + The same is true for CentOS-4 and CentOS-5. If you update any CentOS-4 product, you will be updated to the latest CentOS-4.x version, or to the latest CentOS-5.x version if you are updating a CentOS-5 system. This is exactly the same behavior as the upstream product. Let's assume that the latest EL4 product is update 6. If you install the upstream original EL4 CDs (the ones before any update set) and upgrade via yum, you will have latest update set installed (EL4 update 6 in our example). Since all updates within a major release (CentOS-2, CentOS-3, CentOS-4, CentOS-5) always upgrade to the latest version when updates are performed (thus mimicking upstream behavior), only the latest version is maintained in each main tree on The CentOS Mirrors (http://mirrors.centos.org/). + There is a CentOS Vault (http://vault.centos.org/) containing old CentOS trees. This vault is a picture of the older tree when it was removed from the main tree, and does not receive updates. It should only be used for reference. The CentOS Distribution visual style is controlled by image files. These image files are packaged inside The CentOS Distribution and made visible once such packages are installed and executed. The way to go for changing The CentOS Distribution visual style is changing all those image files to add the desired visual style first and later, repackage them to make them available inside the final iso files of CentOS Distribution. Usage - This directory provides organizationl structure to store default design models for CentOS Themes of CentOS Distribution and so it should be considered to be used. - When a new component is added to CentOS Distribution, this is the directory you need to go for specifying design models for image files inside such component. - The procedure to follow is creatig a directory for each component using its very same name (e.g., the directory Anaconda stores image files for Anaconda component, the installer program). Inside the directory, you need to create one scalable vector graphic for each image file inside the component you want to produce images for. This, in order to set image dimensions, image file-name, position of trademarks in the final image, translation markers and whatever common information you need to have specified in them when rendered by centos-art script. - Sometimes, between major releases, image files inside packages can be added, removed or just change their names. In order to describe such image files variations, the design models directory structure is organized in the same way the file variations are introduced (i.e., through The CentOS Project Release Schema). So, each major release of CentOS Distribution does have its own design model directory structure in this directory. - When a whole package is removed from one or all CentOS Distribution major releases, the design models directory structure releated to it is no longer used. However it could be very useful for historical reasons. Also, someone could feel motivated enough to keep himself documenting it or supporting it for whatever reason. - Major release 5 + Sometimes, between major releases, image files inside packages can be added, removed or just get the name changed. In order to describe such variations, the design models directory structure is organized in the same way the variations are introduced (i.e., through The CentOS Distribution Release Schema). So, each major release of The CentOS Distribution has its own design model directory structure. + When a new package/component is added to one or all the major releases of The CentOS Distribution, a design model directory structure for that component needs to be created. Later, it is filled up with related design models. Design models are created for each image file inside the component that need to be rebuilt in order to set the visual style and brand information correctly. + When a package is removed from one or all major releases of The CentOS Distribution, the design model directory structure releated to that package/component is no longer used. However, it could be very useful for historical reasons. Also, someone could feel motivation enough to keep himself documenting it or supporting it for whatever reason. • @@ -1505,13 +1464,24 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes See also - - - Directories trunk Identity Themes Models Default - Directories trunk Identity Themes Models Default - - - + + • + + Directories trunk Identity Themes Models Default. + + + Directories trunk Identity Themes Models. + + + Directories trunk Identity Themes. + + + Directories trunk Identity. + + + Directories trunk. + + @@ -1537,86 +1507,60 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes Usage -
- - Syslinux - - Contains design models for syslinux, the program used to boot the CentOS Distribution installation media. - - • - - See Directories trunk Identity Themes Models Default Distro 5 Syslinux. - - - - - - Anaconda - - Contains design models for Anaconda, the program used to install CentOS Distribution. - - • - - See Directories trunk Identity Themes Models Default Distro 5 Anaconda. - - - - - - Firstboot - - Contains design models for the first boot program used to configure the maching onece installed. See Directories trunk Identity Themes Models Default Distro Firstboot, for more information. - - - - Rhgb - - Contains design models for CentOS Graphical Boot, the program used to show the boot process from Grub to Display Manager. See Directories trunk Identity Themes Models Default Distro Rhgb, for more information. - - - - Gdm - - Contains design models for GNOME Display Manager, the program used to log into the manchine once installed and configured. See Directories trunk Identity Themes Models Default Distro Gdm, for more information. - - - - Kdm - - Contains design models for KDE Display Manager, the program used to log into the manchine once installed and configured. See Directories trunk Identity Themes Models Default Distro Kdm, for more information. - - - - Grub - - Contains design models for GRUB (Grand Unified Boot Loader), the program used to boot the machine into an operating system. See Directories trunk Identity Themes Models Default Distro Kdm, for more information. - - - - Gsplash - - Contains design models for GNOME splash, the program used to show the progress information while user's graphical session is loading. See Directories trunk Identity Themes Models Default Distro Gsplash, for more information. - - - - Ksplash - - Contains design models for KDE splash, the program used to show the progress information while user's graphical session is loading. See Directories trunk Identity Themes Models Default Distro Ksplash, for more information. - - -
+ + • + + See Directories trunk Identity Themes Models Default Distro 5 Syslinux. + + + See Directories trunk Identity Themes Models Default Distro 5 Anaconda. + + + See Directories trunk Identity Themes Models Default Distro 5 Rhgb. + + + See Directories trunk Identity Themes Models Default Distro 5 Gdm. + + + See Directories trunk Identity Themes Models Default Distro 5 Kdm. + + + See Directories trunk Identity Themes Models Default Distro 5 Grub. + + + See Directories trunk Identity Themes Models Default Distro 5 Gsplash. + + + See Directories trunk Identity Themes Models Default Distro 5 Ksplash. + + See also • - ... + Directories trunk Identity Themes Models Default Distro. + + + Directories trunk Identity Themes Models Default. + + + Directories trunk Identity Themes Models. + + + Directories trunk Identity Themes. + + + Directories trunk Identity. + + + Directories trunk. Directories trunk Identity Themes Models Default Distro 5 Anaconda - Directories trunk Identity Themes Models Default Distro 5 Syslinux + Directories trunk Identity Themes Models Default Distro 5 Firstboot Directories trunk Identity Themes Models Default Distro 5 Directories
@@ -1637,13 +1581,13 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes
- Directories trunk Identity Themes Models Default Distro 5 Syslinux - Directories trunk Identity Themes Models Default Distro Firstboot + Directories trunk Identity Themes Models Default Distro 5 Firstboot + Directories trunk Identity Themes Models Default Distro 5 Gdm Directories trunk Identity Themes Models Default Distro 5 Anaconda Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/5/Syslinux</file> Directory - Directories trunk Identity Themes Models Default Distro 5 Syslinux + The <file>trunk/Identity/Themes/Models/Default/Distro/5/Firstboot</file> Directory + Directories trunk Identity Themes Models Default Distro 5 Firstboot Goals • @@ -1666,22 +1610,18 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes See also - - • - - ... - - + +
- Directories trunk Identity Themes Models Default Distro Firstboot - Directories trunk Identity Themes Models Default Distro Gdm - Directories trunk Identity Themes Models Default Distro 5 Syslinux + Directories trunk Identity Themes Models Default Distro 5 Gdm + Directories trunk Identity Themes Models Default Distro 5 Grub + Directories trunk Identity Themes Models Default Distro 5 Firstboot Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Firstboot</file> Directory - Directories trunk Identity Themes Models Default Distro Firstboot + The <file>trunk/Identity/Themes/Models/Default/Distro/5/Gdm</file> Directory + Directories trunk Identity Themes Models Default Distro 5 Gdm Goals • @@ -1709,13 +1649,13 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes
- Directories trunk Identity Themes Models Default Distro Gdm - Directories trunk Identity Themes Models Default Distro Grub - Directories trunk Identity Themes Models Default Distro Firstboot + Directories trunk Identity Themes Models Default Distro 5 Grub + Directories trunk Identity Themes Models Default Distro 5 Gsplash + Directories trunk Identity Themes Models Default Distro 5 Gdm Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Gdm</file> Directory - Directories trunk Identity Themes Models Default Distro Gdm + The <file>trunk/Identity/Themes/Models/Default/Distro/5/Grub</file> Directory + Directories trunk Identity Themes Models Default Distro 5 Grub Goals • @@ -1743,13 +1683,13 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes
- Directories trunk Identity Themes Models Default Distro Grub - Directories trunk Identity Themes Models Default Distro Gsplash - Directories trunk Identity Themes Models Default Distro Gdm + Directories trunk Identity Themes Models Default Distro 5 Gsplash + Directories trunk Identity Themes Models Default Distro 5 Kdm + Directories trunk Identity Themes Models Default Distro 5 Grub Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Grub</file> Directory - Directories trunk Identity Themes Models Default Distro Grub + The <file>trunk/Identity/Themes/Models/Default/Distro/5/Gsplash</file> Directory + Directories trunk Identity Themes Models Default Distro 5 Gsplash Goals • @@ -1777,13 +1717,13 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes
- Directories trunk Identity Themes Models Default Distro Gsplash - Directories trunk Identity Themes Models Default Distro Kdm - Directories trunk Identity Themes Models Default Distro Grub + Directories trunk Identity Themes Models Default Distro 5 Kdm + Directories trunk Identity Themes Models Default Distro 5 Ksplash + Directories trunk Identity Themes Models Default Distro 5 Gsplash Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Gsplash</file> Directory - Directories trunk Identity Themes Models Default Distro Gsplash + The <file>trunk/Identity/Themes/Models/Default/Distro/5/Kdm</file> Directory + Directories trunk Identity Themes Models Default Distro 5 Kdm Goals • @@ -1811,13 +1751,13 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes
- Directories trunk Identity Themes Models Default Distro Kdm - Directories trunk Identity Themes Models Default Distro Ksplash - Directories trunk Identity Themes Models Default Distro Gsplash + Directories trunk Identity Themes Models Default Distro 5 Ksplash + Directories trunk Identity Themes Models Default Distro 5 Rhgb + Directories trunk Identity Themes Models Default Distro 5 Kdm Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Kdm</file> Directory - Directories trunk Identity Themes Models Default Distro Kdm + The <file>trunk/Identity/Themes/Models/Default/Distro/5/Ksplash</file> Directory + Directories trunk Identity Themes Models Default Distro 5 Ksplash Goals • @@ -1845,13 +1785,13 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes
- Directories trunk Identity Themes Models Default Distro Ksplash - Directories trunk Identity Themes Models Default Distro Rhgb - Directories trunk Identity Themes Models Default Distro Kdm + Directories trunk Identity Themes Models Default Distro 5 Rhgb + Directories trunk Identity Themes Models Default Distro 5 Syslinux + Directories trunk Identity Themes Models Default Distro 5 Ksplash Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Ksplash</file> Directory - Directories trunk Identity Themes Models Default Distro Ksplash + The <file>trunk/Identity/Themes/Models/Default/Distro/5/Rhgb</file> Directory + Directories trunk Identity Themes Models Default Distro 5 Rhgb Goals • @@ -1879,13 +1819,13 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes
- Directories trunk Identity Themes Models Default Distro Rhgb + Directories trunk Identity Themes Models Default Distro 5 Syslinux Directories trunk Identity Themes Models Default Posters - Directories trunk Identity Themes Models Default Distro Ksplash + Directories trunk Identity Themes Models Default Distro 5 Rhgb Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Rhgb</file> Directory - Directories trunk Identity Themes Models Default Distro Rhgb + The <file>trunk/Identity/Themes/Models/Default/Distro/5/Syslinux</file> Directory + Directories trunk Identity Themes Models Default Distro 5 Syslinux Goals • @@ -1908,14 +1848,18 @@ trunk/Identity/Themes/Motifs/THEMENAME/THEMEVERSION/Brushes See also - - + + • + + ... + +
Directories trunk Identity Themes Models Default Posters Directories trunk Identity Themes Motifs - Directories trunk Identity Themes Models Default Distro Rhgb + Directories trunk Identity Themes Models Default Distro 5 Syslinux Directories
The <file>trunk/Identity/Themes/Models/Default/Posters</file> Directory @@ -2412,7 +2356,11 @@ priority=10 Directories
The <file>trunk/Locales</file> Directory - Directories trunk LocalesThe trunk/Locales directory exists to store the translation messages used to produce content in different languages. + Directories trunk Locales + Goals + The trunk/Locales directory structure provides the localization work line and its main goal is provide the translation messages required to produce content in different languages. + Description + Translation messages inside the repository are stored as portable objects (e.g., .po, .pot) and machine objects (.mo) under trunk/Locales directory structure. Translation messages are organized using the directory structure of the component being translated. For example, if we want to provide translation messages for trunk/Manuals/Repository, then the trunk/Locales/Manuals/Repository directory needs to be created. Once the locale directory exists for the component we want to provide translation messages for, it is necessary to create the translation files where translation messages are. The translation files follows the concepts of xml2po and GNU gettext tools. The basic translation process is as follow: first, translatable strings are extracted from files and a portable object template (.pot) is created or updated with the information. Using the portable object template, a portable object (.po) is created or updated for translator to locale the messages retrived. Finally, a machine object (.mo) is created from portable object to sotore the translated messages. @@ -2420,13 +2368,17 @@ priority=10 When translatable strings are retrived from XML files, using the xml2po command, there is no need to create the machine object as we do when translatable strings ar retrived from shell files, using the xgettext command. The xml2po produces a temporal machine object in order to create a translated XML file. Once the translated XML file has been created the machine object is no longer needed. On the other hand, the machine object produced by the xgettext command is required by the system in order for the show shell script localized messages. Another difference between xml2po and xgettext we need to be aware of is the directory structure used to store machine objects. In xml2po, the machine object is created in the current working directory as .xml2po.mo and can be safetly removed once the translated XML file has been created. In the case of xgettext, the machine object needs to be stored in the $TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo file in order for the system to interpret it and should not be removed since it is the file that contain the translation messages themselves. Automation of localization tasks is achived through the locale functionality of command-line interface. - - - Directories trunk Scripts Functions Locale - Directories trunk Scripts Functions Locale - - - + Usage + + • + + ... + + + See also + + •Directories trunk Scripts Functions Locale +
@@ -2438,12 +2390,7 @@ priority=10 The <file>trunk/Manual</file> Directory Directories trunk Manual Goals - - • - - ... - - + This trunk/Manual directory structure provides the documentation work line. The main goal of documentation work line is describe what each directory inside the CentOS Artwork Repository is for, the conceptual ideas behind them and, if possible, how automation scripts make use of them. Description •