diff --git a/Manuals/Repository/Docbook/Identity.docbook b/Manuals/Repository/Docbook/Identity.docbook index 39602b1..34f5212 100644 --- a/Manuals/Repository/Docbook/Identity.docbook +++ b/Manuals/Repository/Docbook/Identity.docbook @@ -1,4 +1,4 @@ - + Visual Identity @@ -6,131 +6,10 @@ ... - - The CentOS Project - ... - - - Mission - ... - - - - Special Interest Groups (SIGs) - ... - - The CentOS Artwork SIG - - Inside the CentOS Project, The CentOS Artwork SIG - produces The CentOS Project corporate visual - identity through image files, mainly. On the - other hand, The CentOS Project produces The CentOS - Distribution and uses the image files produced by - The CentOS Artwork SIG to cover the artwork needs - inside The CentOS Distirbution and other corporate - visual manifestations like web sites and - showrooms. - - - - The contents produced by The CentOS Artwork SIG - (e.g., graphic desings, documentaion, scripts and - translations) are copyright of The CentOS Artwork - SIG and the content produced by The CentOS Project - (e.g., The CentOS Distribution) is copyright of - The CentOS Project. - - - - The content produced by The CentOS Project and The - CentOS Artwork SIG are both released as a GPL work - in order for them to integrate one another. - - - - - - - - The CentOS Logo - ... - - - - Introduction - - - The CentOS Logo is the main visual manifestaion of The - CentOS Project. The CentOS Project uses The CentOS Logo to - connect all its visual manifestions (e.g., GNU/Linux - Distributions, Websites, Stationery, etc.) and, this way, - it provides recognition among other similar projects - available on the Internet. - - - - Both The CentOS Logo and all the visual manifestations - that derivate from it are available for you to study and - propose improvement around a good citizen's will at The - CentOS Community environment, but you are not allowed to - redistribute them elsewhere, without the given permission - of The CentOS Project. - - - - If you need to redistribute either The CentOS Logo or any - visual manifestation derived from it, write your - intentions to the The CentOS Developers mailing list - (centos-devel@centos.org). - - - - - - ... - ... - - - - - - - The CentOS Distribution - ... - - - Release Schema - ... - - - - ... - ... - - - - - - The CentOS Web - ... - - - ... - ... - - - - - - The CentOS Showroom - ... - - - ... - ... - - - + &identity-project; + &identity-logo; + &identity-distribution; + &identity-web; + &identity-showroom; diff --git a/Manuals/Repository/Docbook/Identity.ent b/Manuals/Repository/Docbook/Identity.ent index 7be8037..72e19e3 100644 --- a/Manuals/Repository/Docbook/Identity.ent +++ b/Manuals/Repository/Docbook/Identity.ent @@ -1 +1,8 @@ - + + + + + + + + diff --git a/Manuals/Repository/Docbook/Introduction.docbook b/Manuals/Repository/Docbook/Introduction.docbook index e6178ab..2c738cc 100644 --- a/Manuals/Repository/Docbook/Introduction.docbook +++ b/Manuals/Repository/Docbook/Introduction.docbook @@ -5,33 +5,34 @@ - Welcome to The CentOS Artwork Repository - Manual. + Welcome to The CentOS Artwork Repository User's + Guide. - The CentOS Artwork Repository Manual describes how The CentOS - Project corporate visual identity is organized and produced - inside the CentOS Artwork Repository (). If you - are looking for a comprehensive, task-oriented guide for + The CentOS Artwork Repository User's Guide describes how The + CentOS Project corporate visual identity is organized and + produced inside The CentOS + Artwork Repository. If you are looking for a + comprehensive, task-oriented guide for understanding how The CentOS Project corporate visual identity is produced, this is the manual for you. - This guide assumes you have a basic understanding of The + This manual assumes you have a basic understanding of The CentOS Distribution. If you need help with CentOS, refer to - the help page on The CentOS Wiki () for a list of different - places you can find help. + the help page on The + CentOS Wiki for a list of different places you can + find help. - &intro-history; - &intro-copying; &intro-docconvs; + &intro-copying; + &intro-history; &intro-usage; &intro-feedback; diff --git a/Manuals/Repository/Docbook/Introduction.ent b/Manuals/Repository/Docbook/Introduction.ent index b63ae4a..b6449a7 100644 --- a/Manuals/Repository/Docbook/Introduction.ent +++ b/Manuals/Repository/Docbook/Introduction.ent @@ -1,6 +1,7 @@ - - - - - - + + + + + + + diff --git a/Manuals/Repository/Docbook/Introduction/Copying.docbook b/Manuals/Repository/Docbook/Introduction/Copying.docbook index b51a071..2420c5d 100644 --- a/Manuals/Repository/Docbook/Introduction/Copying.docbook +++ b/Manuals/Repository/Docbook/Introduction/Copying.docbook @@ -1,6 +1,6 @@ - Copying Conditions + Repository Copying Conditions Copyright © 2009, 2010, 2011 The CentOS Artwork SIG @@ -11,77 +11,6 @@ of this license document, but changing it is not allowed. - + &intro-copying-preamble; - Preamble - - - The CentOS Artwork Repository organizes files in a very - specific way to implement The CentOS Project corporate visual - identity. This very specific organization of files must be - considered part of centos-art.sh script, a - bash script that automate most of the frequent tasks inside - the repository. - - - - The centos-art.sh script and the - organization of files it needs to work are not in the public - domain; they are copyrighted and there are restrictions on - their distribution, but these restrictions are designed to - permit everything that a good cooperating citizen would want - to do. What is not allowed is to try to prevent others from - further sharing any version of this program that they might - get from you. - - - - Specifically, we want to make sure that you have the right to - give away copies of centos-art.sh script - and the organization of files it needs to work, that you - receive source code or else can get it if you want it, that - you can change this program or use pieces of it in new free - programs, and that you know you can do these things. - - - - To make sure that everyone has such rights, we have to forbid - you to deprive anyone else of these rights. For example, if - you distribute copies of the centos-art.sh - script, you must give the recipients all the rights that you - have. You must make sure that they, too, receive or can get - the source code. And you must tell them their rights. - - - - Also, for our own protection, we must make certain that - everyone finds out that there is no warranty for the - centos-art.sh script. If this program is - modified by someone else and passed on, we want their - recipients to know that what they have is not what we - distributed, so that any problems introduced by others will - not reflect on our reputation. - - - - The centos-art.sh script is released as a - GPL work. Individual packages used by - centos-art.sh script include their own - licenses and the centos-art.sh script - license applies to all packages that it does not clash with. - If there is a clash between the - centos-art.sh script license and individual - package licenses, the individual package license applies - instead. - - - - The precise conditions of the license for the - centos-art.sh script are found in the . This manual specifically is covered - by the . - - - - diff --git a/Manuals/Repository/Docbook/Introduction/Docconvs.docbook b/Manuals/Repository/Docbook/Introduction/Docconvs.docbook index 8cbaf70..9efcdb9 100644 --- a/Manuals/Repository/Docbook/Introduction/Docconvs.docbook +++ b/Manuals/Repository/Docbook/Introduction/Docconvs.docbook @@ -2,115 +2,225 @@ Document Convenctions - In this manual the personal pronoun we - is used to repesent The CentOS Artwork SIG, - the group of persons that build The CentOS Project corporate - visual identity through the CentOS Artwork Repository. - - In this manual, certain words are represented in different - fonts, typefaces, sizes, and weights. This highlighting is - systematic; different words are represented in the same style to - indicate their inclusion in a specific category. The types of - words that are represented this way include the following: - - - - command - - Linux commands (and other operating system - commands, when used) are represented this way. This - style should indicate to you that you can type the - word or phrase on the command line and press Enter to - invoke a command. Sometimes a command contains words - that would be displayed in a different style on their - own (such as file names). In these cases, they are - considered to be part of the command, so the entire - phrase is displayed as a command. For example: - - Use the centos-art identity - --render='path/to/dir' command to produce - contents inside the trunk/Identity directory - structure. + + In this manual, certain words are represented in different + fonts, typefaces, sizes, and weights. This highlighting is + systematic; different words are represented in the same style + to indicate their inclusion in a specific category. The types + of words that are represented this way include the + following: + + + + + command + + + Linux commands (and other operating system + commands, when used) are represented this way. + This style should indicate to you that you can + type the word or phrase on the command line and + press Enter to invoke a command. Sometimes a + command contains words that would be displayed in + a different style on their own (such as file + names). In these cases, they are considered to be + part of the command, so the entire phrase is + displayed as a command. + + + Example: + + + + + + Use the centos-art render trunk/Manuals/Repository/Docbook + --filter="repository" command to produce + the CentOS Artwork Repository User's Guide. + + + - - - - - file name - - File names, directory names, paths, and RPM - package names are represented this way. This style - indicates that a particular file or directory exists - with that name on your system. Examples: - - The init.sh file in - trunk/Scripts/Bash/Cli/ - directory is the initialization script, written in - Bash, used to automate most of tasks in the - repository. - - The centos-art command uses - the ImageMagick RPM package to - convert images from PNG format to other - formats. - - - - - - key - - A key on the keyboard is shown in this style. - For example: - - To use TAB completion to list - particular files in a directory, type @command{ls}, - then a character, and finally the Tab key. Your - terminal displays the list of files in the working - directory that begin with that character. - - - - - key-combination - - A combination of keystrokes is represented in - this way. For example: - - The CtrlAltBackspace - key combination exits your graphical session and - returns you to the graphical login screen or the - console. + + + + + file name + + + File names, directory names, paths, and RPM + package names are represented this way. This style + indicates that a particular file or directory + exists with that name on your system. + + + Example: + + + + + + The init.sh file in trunk/Scripts/Bash/Cli/ + directory is the initialization script, written in + Bash, used to automate most of tasks in the + repository. + + + + + The centos-art command uses the + ImageMagick RPM package to + convert images from PNG format to other + formats. + + + + + + + + + key + + + A key on the keyboard is shown in this style. + + + Example: + + + + + To use Tab completion to list + particular files in a directory, type + ls, then a character, and finally + the Tab key. Your terminal displays + the list of files in the working directory that begin + with that character. + + + + + + + keycombination + + + A combination of keystrokes is represented in this + way. + + + Example: + + + + + The CtrlAltBackspace + key combination exits your graphical session and + returns you to the graphical login screen or the + console. + + + - + - - - - computer output - - Text in this style indicates text displayed to a - shell prompt such as error messages and responses to - commands. For example: + - The ls command displays the - contents of a directory. For example: + + computer output + + + Text in this style indicates text displayed to a shell + prompt such as error messages and responses to + commands. For example, the ls + command displays the contents of a directory using + this style: + -Config help_renameEntry.sh -help_copyEntry.sh help_restoreCrossReferences.sh -help_deleteCrossReferences.sh help_searchIndex.sh +render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh +render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh +render_getDirOutput.sh render.sh - The output returned in response to the command (in this - case, the contents of the directory) is shown in this - style. - - - + + The output returned in response to the command (in + this case, the contents of the directory) is shown in + this style. + + + + + + prompt + + + A prompt, which is a computer's way of signifying that it + is ready for you to input something, is shown in this + style. Examples: + + + + $ + + + + + # + + + + + [centos@projects centos]$ + + + + + projects login: + + + + + + + + + + user input + + + Text that the user types, either on the command line or + into a text box on a GUI screen, is displayed in this + style. In the following example, + text is displayed in this style: To + boot your system into the text based installation program, + you must type in the text command + at the boot: prompt. + + + + + + replaceable + + + Text used in examples that is meant to be replaced with + data provided by the user is displayed in this style. In + the following example, + version-number is displayed in + this style: The directory for the kernel source is + /usr/src/kernels/version-number/, + where version-number is the + version and type of kernel installed on this system. + + + + Additionally, we use several different strategies to draw your attention to certain pieces of information. In order of diff --git a/Manuals/Repository/Docbook/Introduction/History.docbook b/Manuals/Repository/Docbook/Introduction/History.docbook index 3b362bc..56f5ca4 100644 --- a/Manuals/Repository/Docbook/Introduction/History.docbook +++ b/Manuals/Repository/Docbook/Introduction/History.docbook @@ -1,14 +1,15 @@ - History + Repository History - The CentOS Artwork Repository started during a discussion - about how to automate the slide images of Anaconda, at CentOS - Developers mailing list (centos-devel@centos.org) - around 2008. In such discussion, Ralph Angenendt rose up his - hand to ask —Do you have something to show?—. + around 2008, on a discussion about how to automate slide + images used by Anaconda. In such discussion, Ralph Angenendt + rose up his hand to ask —Do you have something to + show?—. diff --git a/Manuals/Repository/Docbook/Introduction/Repoconvs.docbook b/Manuals/Repository/Docbook/Introduction/Repoconvs.docbook index 7b8258c..25e57de 100644 --- a/Manuals/Repository/Docbook/Introduction/Repoconvs.docbook +++ b/Manuals/Repository/Docbook/Introduction/Repoconvs.docbook @@ -1,37 +1,46 @@ - + Repository Convenctions - The CentOS Artwork Repository is supported by Subversion - (http://subversion.tigris.org/), a version control system which - allows you to keep old versions of files and directories (usually - source code), keep a log of who, when, and why changes occurred, - etc., like CVS, RCS or SCCS. + + The CentOS Artwork Repository is supported by Subversion, a + version control system which allows you to keep old versions + of files and directories (usually source code), keep a log of + who, when, and why changes occurred, etc., like CVS, RCS or + SCCS. + - When using Subversion there is one "source repository" and - many "working copies" of that source repository. The working - copies are independent one another, can be distributed all around - the world and provide a local place for designers, documentors, - translators and programmers to perform their work in a - descentralized way. The source repository, on the other hand, - provides a central place for all independent working copies to - interchange data and provides the information required to permit - extracting previous versions of files at any time. + + When using Subversion there is one "source repository" and + many "working copies" of that source repository. The working + copies are independent one another, can be distributed all + around the world and provide a local place for designers, + documentors, translators and programmers to perform their work + in a descentralized way. The source repository, on the other + hand, provides a central place for all independent working + copies to interchange data and provides the information + required to permit extracting previous versions of files at + any time. + - + Policy - The CentOS Artwork Repository is a collaborative tool - that anyone can have access to. However, changing that tool in - any form is something that should be requested in the CentOS - Developers mailing list (centos-devel@centos.org). Generally, - people download working copies from CentOS Artwork Repository, - study the repository organization, make some changes in their - working copies, make some tests to verify such changes do work - the way expected and finally request access to commit them up - to the CentOS Artwork Repository (i.e., the source repository) - for others to benefit from them. + + The CentOS Artwork Repository is a collaborative tool that + anyone can have access to. However, changing that tool in + any form is something that should be requested in the + CentOS Developers mailing list (centos-devel@centos.org). + Generally, people download working copies from CentOS + Artwork Repository, study the repository organization, + make some changes in their working copies, make some tests + to verify such changes do work the way expected and + finally request access to commit them up to the CentOS + Artwork Repository (i.e., the source repository) for + others to benefit from them. + Once you've received access to commit your changes, there is no need for you to request permission again to commit @@ -72,7 +81,7 @@ - + Work Lines @@ -129,7 +138,7 @@ - + Relation Between Directories @@ -191,7 +200,7 @@ - + Syncronizing Paths @@ -267,8 +276,7 @@ - + Extending Repository Organization @@ -309,27 +317,32 @@ class="directory">trunk/Scripts stores automation scripts. - To better illustrate this desition process, you can - consider to examin the trunk/Identity/Images/Themes/TreeFlower/3 - directory structure as example. This directory can be read - as: the theme development line of version 3 of - TreeFlower artistic motif. Additional, we can - say that TreeFlower artistic motif is part of - themes, as themes are part of The CentOS Project corporate - visual identity. + + To better illustrate this desition process, you can + consider to examin the trunk/Identity/Images/Themes/TreeFlower/3 + directory structure as example. This directory can be + read as: the theme development line of version + 3 of TreeFlower artistic + motif. Additional, we can say that + TreeFlower artistic motif is part of + themes, as themes are part of The CentOS Project corporate + visual identity. + - The relationship between conceptual ideas can be - stablished by reading each repository documentation entry - individually, from trunk directory to a deeper - directory in the path. For reading repository documentation - entries we use the help functionality of - centos-art.sh script. + + The relationship between conceptual ideas can be + stablished by reading each repository documentation entry + individually, from trunk directory to a deeper + directory in the path. For reading repository + documentation entries we use the help + functionality of centos-art.sh script. + - + File Names @@ -354,9 +367,9 @@ - + - Repository Layout + Layout The CentOS Artwork Repository is organized through a convenctional trunk, branches diff --git a/Manuals/Repository/Docbook/Manuals/Texinfo/structure.docbook b/Manuals/Repository/Docbook/Manuals/Texinfo/structure.docbook index f79669a..544b088 100644 --- a/Manuals/Repository/Docbook/Manuals/Texinfo/structure.docbook +++ b/Manuals/Repository/Docbook/Manuals/Texinfo/structure.docbook @@ -62,7 +62,7 @@ Licenses — This chapter includes licenses from trunk/Scripts/Functions/Help/Texinfo/Templates/$LANG/Licenses/ + class="directory">trunk/Scripts/Functions/Help/Texinfo/Templates/language/Licenses/ directory. In the normal work flow, you don't need to touch this chapter. It is created when the document structure is created and should ramain that way. If you @@ -105,7 +105,7 @@ trunk/Manuals/Repository/Texinfo -|-- $LANG +|-- en_US | |-- Directories | | |-- chapter-menu.texinfo | | |-- chapter-nodes.texinfo