diff --git a/Manuals/Tcar-ug/Introduction.docbook b/Manuals/Tcar-ug/Introduction.docbook deleted file mode 100644 index 5ebf6ba..0000000 --- a/Manuals/Tcar-ug/Introduction.docbook +++ /dev/null @@ -1,71 +0,0 @@ - - - Preface - - - Welcome to &TCARUG;, the official documentation of &TCAR;. - - - - To make the information in this book managable, it has been - organized in the following parts: - - - - - - describes the repository directory - structure. - - - - - - describes the identity work line. - This part is closely related to graphic design and considers - &TCP; as organization to find the aspects that could affect - its visual identity. - - - - - - describes the localization work line. - - - - - - describes the documentation work - line. - - - - - - describes the automation work line. - - - - - - organizes the licenses mentioned - inside this book. - - - - - - - This manual assumes you have a basic understanding of &TCD;. - If you need help with it, go to the Help page inside The - CentOS Wiki for or a list of different places you can find - help. - - - &intro-history; - &intro-docconvs; - &intro-feedback; - - diff --git a/Manuals/Tcar-ug/Introduction.ent b/Manuals/Tcar-ug/Introduction.ent deleted file mode 100644 index 9385011..0000000 --- a/Manuals/Tcar-ug/Introduction.ent +++ /dev/null @@ -1,4 +0,0 @@ - - - - diff --git a/Manuals/Tcar-ug/Introduction/docconvs.docbook b/Manuals/Tcar-ug/Introduction/docconvs.docbook deleted file mode 100644 index 0f522c7..0000000 --- a/Manuals/Tcar-ug/Introduction/docconvs.docbook +++ /dev/null @@ -1,225 +0,0 @@ -
- - Document Convenctions - - - 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 render - trunk/Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda - --filter="01-welcome" command to produce the first - slide image used by Anaconda in the branch 5 of &TCD; - using the version 4 of TreeFlower artistic motif. - - - - - - 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 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. - For 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 using this style: - - - -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. - - - - - - 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 - urgency, these items are marked as a note, tip, important, - caution, or warning. For example: - - - Remember that Linux is case sensitive. In other words, a - rose is not a ROSE is not a rOsE. - - - - The directory /usr/share/doc/ contains - additional documentation for packages installed on your - system. - - - - If you modify the DHCP configuration file, the changes - do not take effect until you restart the DHCP daemon. - - - - Do not perform routine tasks as root — use a - regular user account unless you need to use the root account - for system administration tasks. - - - - Be careful to remove only the necessary partitions. - Removing other partitions could result in data loss or a - corrupted system environment. - - -
diff --git a/Manuals/Tcar-ug/Introduction/feedback.docbook b/Manuals/Tcar-ug/Introduction/feedback.docbook deleted file mode 100644 index d79b82f..0000000 --- a/Manuals/Tcar-ug/Introduction/feedback.docbook +++ /dev/null @@ -1,18 +0,0 @@ -
- - Send In Your Feedback - - - If you find an error in the &TCAR;, or if you have thought of - a way to make this manual better, we would like to hear from - you! Share your suggestions in &TCAML;. - - - - When you make a suggestion, try to be as specific as possible. - For example, if you have found an error in the manual, include - the section number and some of the surrounding text so we can - find it easily. - - -
diff --git a/Manuals/Tcar-ug/Introduction/history.docbook b/Manuals/Tcar-ug/Introduction/history.docbook deleted file mode 100644 index 81e7b49..0000000 --- a/Manuals/Tcar-ug/Introduction/history.docbook +++ /dev/null @@ -1,44 +0,0 @@ -
- History - - &TCAR; started at The CentOS Developers - Mailing List around 2008, on a discussion about how to - automate slide images used by Anaconda (&TCD; installer). In - such discussion, Ralph Angenendt rose up his hand to ask - —Do you have something to show?—. - - - - To answer the question, Alain Reguera Delgado suggested a bash - script which combined SVG and SED files in order to produce - PNG images in different languages —in conjunction with - the proposition of creating a Subversion repository where - translations and image production could be distributed inside - &TCC;—. - - - - Karanbirn Sighn considered the idea intresting and provided - the infrastructure necessary to support the effort. This way, - &TCAS; and &TCAR; were officially created and world wide - available. - - - - Once &TCAR; was available, Alain Reguera Delgado uploaded the - bash script used to produce the Anaconda slides; Ralph - Angenendt documented it very well; and people started to - download working copies of the repository to produce slide - images in their own languages. - - - - From this time on, the &TCAR; has been under constant - development to automate the production of &TCP; corporate - visual identity. The list of all changes is available in the - repository's log messages. A resumen of relevant changes is - made available yearly in . - - -
diff --git a/Manuals/Tcar-ug/Preface.docbook b/Manuals/Tcar-ug/Preface.docbook new file mode 100644 index 0000000..5ebf6ba --- /dev/null +++ b/Manuals/Tcar-ug/Preface.docbook @@ -0,0 +1,71 @@ + + + Preface + + + Welcome to &TCARUG;, the official documentation of &TCAR;. + + + + To make the information in this book managable, it has been + organized in the following parts: + + + + + + describes the repository directory + structure. + + + + + + describes the identity work line. + This part is closely related to graphic design and considers + &TCP; as organization to find the aspects that could affect + its visual identity. + + + + + + describes the localization work line. + + + + + + describes the documentation work + line. + + + + + + describes the automation work line. + + + + + + organizes the licenses mentioned + inside this book. + + + + + + + This manual assumes you have a basic understanding of &TCD;. + If you need help with it, go to the Help page inside The + CentOS Wiki for or a list of different places you can find + help. + + + &intro-history; + &intro-docconvs; + &intro-feedback; + + diff --git a/Manuals/Tcar-ug/Preface.ent b/Manuals/Tcar-ug/Preface.ent new file mode 100644 index 0000000..baf283a --- /dev/null +++ b/Manuals/Tcar-ug/Preface.ent @@ -0,0 +1,4 @@ + + + + diff --git a/Manuals/Tcar-ug/Preface/docconvs.docbook b/Manuals/Tcar-ug/Preface/docconvs.docbook new file mode 100644 index 0000000..8eda7bc --- /dev/null +++ b/Manuals/Tcar-ug/Preface/docconvs.docbook @@ -0,0 +1,225 @@ +
+ + Document Convenctions + + + 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 render + trunk/Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda + --filter="01-welcome" command to produce the first + slide image used by Anaconda in the branch 5 of &TCD; + using the version 4 of TreeFlower artistic motif. + + + + + + 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 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. + For 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 using this style: + + + +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. + + + + + + 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 + urgency, these items are marked as a note, tip, important, + caution, or warning. For example: + + + Remember that Linux is case sensitive. In other words, a + rose is not a ROSE is not a rOsE. + + + + The directory /usr/share/doc/ contains + additional documentation for packages installed on your + system. + + + + If you modify the DHCP configuration file, the changes + do not take effect until you restart the DHCP daemon. + + + + Do not perform routine tasks as root — use a + regular user account unless you need to use the root account + for system administration tasks. + + + + Be careful to remove only the necessary partitions. + Removing other partitions could result in data loss or a + corrupted system environment. + + +
diff --git a/Manuals/Tcar-ug/Preface/feedback.docbook b/Manuals/Tcar-ug/Preface/feedback.docbook new file mode 100644 index 0000000..fbcfa3b --- /dev/null +++ b/Manuals/Tcar-ug/Preface/feedback.docbook @@ -0,0 +1,18 @@ +
+ + Send In Your Feedback + + + If you find an error in the &TCAR;, or if you have thought of + a way to make this manual better, we would like to hear from + you! Share your suggestions in &TCAML;. + + + + When you make a suggestion, try to be as specific as possible. + For example, if you have found an error in the manual, include + the section number and some of the surrounding text so we can + find it easily. + + +
diff --git a/Manuals/Tcar-ug/Preface/history.docbook b/Manuals/Tcar-ug/Preface/history.docbook new file mode 100644 index 0000000..81e7b49 --- /dev/null +++ b/Manuals/Tcar-ug/Preface/history.docbook @@ -0,0 +1,44 @@ +
+ History + + &TCAR; started at The CentOS Developers + Mailing List around 2008, on a discussion about how to + automate slide images used by Anaconda (&TCD; installer). In + such discussion, Ralph Angenendt rose up his hand to ask + —Do you have something to show?—. + + + + To answer the question, Alain Reguera Delgado suggested a bash + script which combined SVG and SED files in order to produce + PNG images in different languages —in conjunction with + the proposition of creating a Subversion repository where + translations and image production could be distributed inside + &TCC;—. + + + + Karanbirn Sighn considered the idea intresting and provided + the infrastructure necessary to support the effort. This way, + &TCAS; and &TCAR; were officially created and world wide + available. + + + + Once &TCAR; was available, Alain Reguera Delgado uploaded the + bash script used to produce the Anaconda slides; Ralph + Angenendt documented it very well; and people started to + download working copies of the repository to produce slide + images in their own languages. + + + + From this time on, the &TCAR; has been under constant + development to automate the production of &TCP; corporate + visual identity. The list of all changes is available in the + repository's log messages. A resumen of relevant changes is + made available yearly in . + + +