-
-
-
-
-
-
-EOT
-}
-
-# / in
-
-
-
-
-
-
-
-EOT
-}
-
-sub T2H_XHTML_print_page_foot
-{
- my $fh = shift;
- my @date=localtime(time);
- my $year=$date[5] += 1900;
- my $program_string = program_string();
- print $fh <$program_string
-
-
-
- '; - -# formatting functions - -$def_line = \&t2h_xhtml_def_line; -$index_summary = \&t2h_xhtml_index_summary; -$image = \&t2h_xhtml_image; - -# need / in
\n" if (@$nonalpha and @$alpha); - if (@$nonalpha) - { - $nonalpha_text = join("\n \n", @$nonalpha) . "\n"; - } - if (@$alpha) - { - $alpha_text = join("\n \n", @$alpha) . "\n \n"; - } - #I18n - return "
| " . &$I('Jump to') . ": | " . - $nonalpha_text . $join . $alpha_text . ' |
|---|
| }; - - if (ref($button) eq 'CODE') - { - &$button($fh, $vertical); - } - elsif (ref($button) eq 'SCALAR') - { - print $fh "$$button" if defined($$button); - } - elsif (ref($button) eq 'ARRAY') - { - my $text = $button->[1]; - my $button_href = $button->[0]; - if (defined($button_href) and !ref($button_href) - and defined($text) and (ref($text) eq 'SCALAR') and defined($$text)) - { # use given text - if ($Texi2HTML::HREF{$button_href}) - { - print $fh "" . - &$anchor('', - $Texi2HTML::HREF{$button_href}, - $$text - ) - ; - } - else - { - print $fh $$text; - } - } - } - elsif ($button eq ' ') - { # handle space button - print $fh - $ICONS && $ACTIVE_ICONS{' '} ? - &$button_icon_img($button, $ACTIVE_ICONS{' '}) : - $NAVIGATION_TEXT{' '}; - #next; - } - elsif ($Texi2HTML::HREF{$button}) - { # button is active - my $btitle = $BUTTONS_GOTO{$button} ? - 'title="' . ucfirst($BUTTONS_GOTO{$button}) . '"' : ''; - if ($ICONS && $ACTIVE_ICONS{$button}) - { # use icon - print $fh '' . - &$anchor('', - $Texi2HTML::HREF{$button}, - &$button_icon_img($button, - $ACTIVE_ICONS{$button}, - #$Texi2HTML::NAME{$button}), - $Texi2HTML::NO_TEXI{$button}), - $btitle - ); - } - else - { # use text - print $fh - '[' . - &$anchor('', - $Texi2HTML::HREF{$button}, - $NAVIGATION_TEXT{$button}, - $btitle - ) . - ']'; - } - } - else - { # button is passive - print $fh - $ICONS && $PASSIVE_ICONS{$button} ? - &$button_icon_img($button, - $PASSIVE_ICONS{$button}, - #$Texi2HTML::NAME{$button}) : - $Texi2HTML::NO_TEXI{$button}) : - - "[" . $NAVIGATION_TEXT{$button} . "]"; - } - print $fh " | \n"; - print $fh "
personaof the organization known as The CentOS + Project. The CentOS Project Corporate Identity plays a + significant role in the way The CentOS Project, as + organization, presents itself to both internal and external + stakeholders. In general terms, The CentOS Project Corporate + Identity expresses the values and ambitions of The CentOS + Project organization, its business, and its characteristics. +
freein the sense of freedom: to assure + everyone the effective freedom to copy and redistribute it, + with or without modifying it, either commercially or + noncommercially. Secondarily, this License preserves for the + author and publisher a way to get credit for their work, while + not being considered responsible for modifications made by + others.
copyleft, which + means that derivative works of the document must themselves be + free in the same sense. It complements the
Document, below, refers to + any such manual or work. Any member of the public is a + licensee, and is addressed as
you. You accept + the license if you copy, modify or distribute the work in a + way requiring permission under copyright law.
Modified Versionof the Document means any work + containing the Document or a portion of it, either copied + verbatim, or with modifications and/or translated into another + language.
Secondary Sectionis a named appendix or a + front-matter section of the Document that deals exclusively + with the relationship of the publishers or authors of the + Document to the Document's overall subject (or to related + matters) and contains nothing that could fall directly within + that overall subject. (Thus, if the Document is in part a + textbook of mathematics, a
Invariant Sectionsare certain +
Cover Textsare certain short passages of text + that are listed, as Front-Cover Texts or Back-Cover Texts, in + the notice that says that the Document is released under this + License. A Front-Cover Text may be at most 5 words, and a + Back-Cover Text may be at most 25 words.
Transparentcopy of the Document means a + machine-readable copy, represented in a format whose + specification is available to the general public, that is + suitable for revising the document straightforwardly with + generic text editors or (for images composed of pixels) + generic paint programs or (for drawings) some widely available + drawing editor, and that is suitable for input to text + formatters or for automatic translation to a variety of + formats suitable for input to text formatters. A copy made in + an otherwise
is called
Opaque.
Title + Pagemeans, for a printed book, the title page itself, + plus such following pages as are needed to hold, legibly, the + material this License requires to appear in the title page. + For works in formats which do not have any title page as such, +
Title Pagemeans the text near the most + prominent appearance of the work's title, preceding the + beginning of the body of the text.
Entitled XYZmeans a named + subunit of the Document whose title either is precisely XYZ or + contains XYZ in parentheses following text that translates XYZ + in another language. (Here XYZ stands for a specific section + name mentioned below, such as
Acknowledgements, +
Dedications,
Endorsements, or +
History.) To
Preserve the Title+ of such a section when you modify the Document means that it + remains a section
Entitled XYZaccording to + this definition.
History, Preserve its Title, and add to + it an item stating at least the title, year, new + authors, and publisher of the
Historyin the Document, create + one stating the title, year, authors, and publisher of + the Document as given on its
Historysection. You may + omit a network location for a work that was published + at least four years before the Document itself, or if + the original publisher of the version it refers to + gives permission.
Acknowledgementsor +
Dedications, Preserve the Title of the + section, and preserve in the section all the substance + and tone of each of the contributor acknowledgements + and/or dedications given therein.
Endorsements. Such a section may not + be included in the
Endorsementsor to conflict in + title with any
Endorsements, provided it contains nothing but + endorsements of your
Historyin the various original + documents, forming one section Entitled +
History; likewise combine any sections Entitled +
Acknowledgements, and any sections Entitled +
Dedications. You must delete all sections + Entitled
Endorsements.
aggregateif the copyright resulting from the + compilation is not used to limit the legal rights of the + compilation's users beyond what the individual works permit. + When the Document is included in an aggregate, this License + does not apply to the other works in the aggregate which are + not themselves derivative works of the Document.
Acknowledgements,
Dedications, + or
History, the requirement (section
or any later + versionapplies to it, you have the option of + following the terms and conditions either of that specified + version or of any later version that has been published (not + as a draft) by the Free Software Foundation. If the Document + does not specify a version number of this License, you may + choose any version ever published (not as a draft) by the Free + Software Foundation.
GNU Free Documentation License. +
with...Texts. line with this:
any later version, you have the + option of following the terms and conditions either of that + version or of any later version published by the Free Software + Foundation. If the Program does not specify a version number of + this License, you may choose any version ever published by the + Free Software Foundation.
AS ISWITHOUT + WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT + NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND + FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE + QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE + PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY + SERVICING, REPAIR OR CORRECTION.
copyrightline + and a pointer to where the full notice is found.
copyright + disclaimerfor the program, if necessary. Here is a + sample; alter the names:
common + functionalitiesand
specific + functionalitiesinside +
source + repositoryand many
working copiesof + 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. +
trunk, +
branchesand
tagslayout. In + this configuration the
connectedbetween themselves is known as +
texinfobackend of
help
+ functionality which provides a restricted implementation of
+ path syncronization to this specific area of documentation
+ through the ,
+ and options you can take as
+ reference to implement it in other areas.
+ texinfobackend for other areas that + demand it and then, create a higher implmentation that + combines them all as needed. This way, if we try to rename a + repository directory the higher action will define which are + all the restricted actions that should be performed in order + to make the full path syncronization. +
Title
+Title
+Title
+@end verbatim + +In the example above, h1 can vary from h1 to h6. Closing tag must be +present and also match the openning tag. The value of @option{name} +and @option{href} options from the anchor element are set dynamically +using the md5sum output of combining the page location, the +@code{head-} string and the heading string. If any of the components +used to build the heading reference changes, you need to run the the +@code{tuneup} functionality of @command{centos-art.sh} script in order +for the anchor elements to use the correct information. + +@subheading Examples + +@table @command +@item centos-art tuneup trunk/Scripts + +Update the copyright and license notice of all the shell scripts we +have in @file{trunk/Scripts} directory structure. + +@item centos-art tuneup trunk/Identity/Models/Brands --filter="symbol" +Update metadata and remove unused definitions from all design models +in @file{trunk/Identity/Models/Brands} which have the word +@samp{symbol} in the file name. + +@item centos-art tuneup trunk/Identity/Webenv/App/Home +Update headings and the related table of contents to all web pages +inside @file{trunk/Identity/Webenv/App/Home}, recusively. +@end table + +@subheading Author + +Written by Alain Reguera Delgado. + +@subheading Reporting bugs + +Report bugs to @email{centos-artwork@@centos.org} mailing list. + +@subheading Copyright + +Copyright @copyright{} 2009, 2010, 2011 The CentOS Project. + +This is free software. You may redistribute copies of it under the +terms of the GNU General Public License (@pxref{GNU General Public +License}). There is NO WARRANTY, to the extent permitted by law. + +@subheading See also + +@itemize +@item @ref{Directories trunk Scripts Functions} +@item @ref{Directories trunk Scripts} +@item @ref{Directories trunk} +@end itemize diff --git a/Manuals/TCAR-UG/Texinfo/en_US/Introduction/authors.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/authors.texinfo new file mode 100755 index 0000000..bca9b4b --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/authors.texinfo @@ -0,0 +1,9 @@ +This section records members of The CentOS Artwork SIG, the people +involved in building the The CentOS Artworks Repository: + +@itemize +@item @email{al@@art.centos.org,Alain Reguera Delgado} +@item @email{mm@@art.centos.org,Marcus Moeller} +@item @email{ralph@@dev.centos.org,Ralph Angenendt} +@item @email{karan@@dev.centos.org,Karanbirn Singh} +@end itemize diff --git a/Manuals/TCAR-UG/Texinfo/en_US/Introduction/chapter-menu.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/chapter-menu.texinfo new file mode 100644 index 0000000..39781c3 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/chapter-menu.texinfo @@ -0,0 +1,8 @@ +@menu +* History:: +* Authors:: +* Copying Conditions:: +* Document Convenctions:: +* Repository Convenctions:: +* Feedback:: +@end menu diff --git a/Manuals/TCAR-UG/Texinfo/en_US/Introduction/chapter-nodes.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/chapter-nodes.texinfo new file mode 100644 index 0000000..dff1350 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/chapter-nodes.texinfo @@ -0,0 +1,30 @@ +@node History +@section History +@cindex History +@include Introduction/history.texinfo + +@node Authors +@section Authors +@cindex Authors +@include Introduction/authors.texinfo + +@node Copying Conditions +@section Copying Conditions +@cindex Copying conditions +@include Introduction/copying.texinfo + +@node Document Convenctions +@section Document Convenctions +@cindex Document convenctions +@include Introduction/doc-convenctions.texinfo + +@node Repository Convenctions +@section Repository Convenctions +@cindex Repository convenctions +@include Introduction/repo-convenctions.texinfo + +@node Feedback +@section Send in Your Feedback +@cindex Feedback +@include Introduction/feedback.texinfo + diff --git a/Manuals/TCAR-UG/Texinfo/en_US/Introduction/chapter.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/chapter.texinfo new file mode 100644 index 0000000..bb60856 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/chapter.texinfo @@ -0,0 +1,20 @@ +@node Introduction +@chapter Introduction +@cindex Introduction + +Welcome to The CentOS Artwork Repository manual. + +The CentOS Artwork Repository manual describes how The CentOS Project +corporate visual identity is organized and produced inside The CentOS +Artwork Repository (@url{https://projects.centos.org/svn/artwork/}). +If you are looking for a comprehensive guide for understanding how The +CentOS Project corporate visual identity is produced, this is the +manual for you. + +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 (@url{http://wiki.centos.org/Help}) for a list of +different places you can find help. + +@include Introduction/chapter-menu.texinfo +@include Introduction/chapter-nodes.texinfo diff --git a/Manuals/TCAR-UG/Texinfo/en_US/Introduction/copying.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/copying.texinfo new file mode 100755 index 0000000..4f6dff2 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/copying.texinfo @@ -0,0 +1,89 @@ +Copyright @copyright{} 2009, 2010, 2011 The CentOS Artwork SIG + +Everyone is permitted to copy and distribute verbatim copies of this +license document, but changing it is not allowed. + +@subheading 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 is part of @command{centos-art.sh} +script, a bash script that automate most of the frequent tasks inside +the repository. + +The @command{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 @command{centos-art.sh} script, 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 @command{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 @command{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 @command{centos-art.sh} +script are found in the General Public Licenses (@pxref{GNU General +Public License}). This manual specifically is covered by the GNU Free +Documentation License (@pxref{GNU Free Documentation License}). + +@subheading 1. The CentOS Brand + +The CentOS Brand (@pxref{Directories trunk Identity Models Brands}) is +the main visual manifestaion of The CentOS Project. The CentOS Project +uses The CentOS Brand to connect all its visual manifestions (e.g., +GNU/Linux Distributions, Websites, Stationery, etc.) and, this way, it +provides recognition among other similar projects. + +Both The CentOS Brand 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 Brand or any the visual +manifestatinos that derivate from it, write your intentions to the +@email{centos-devel@@centos.org} mailing list. + +@subheading 2. The CentOS Artwork SIG + +The CentOS Artwork @acronym{SIG,Special Interest Group} is a group +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. diff --git a/Manuals/TCAR-UG/Texinfo/en_US/Introduction/doc-convenctions.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/doc-convenctions.texinfo new file mode 100644 index 0000000..a23d8de --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/doc-convenctions.texinfo @@ -0,0 +1,101 @@ +In this manual the personal pronoun @emph{we} is used to repesent +@emph{The CentOS Artwork SIG}, the group of people involved in +building the The CentOS Artworks Repository (@pxref{Authors}). + +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: + +@table @strong +@item @command{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 @command{centos-art render path/to/dir} command to produce +contents inside the @file{trunk/Identity} directory structure. + +@item @file{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 @file{init.sh} file in @file{trunk/Scripts/Bash/Cli/} directory is +the initialization script, written in Bash, used to automate most of +tasks in the repository. + +The @command{centos-art} command uses the @file{ImageMagick} RPM +package to convert images from PNG format to other formats. + +@item @key{key} + +A key on the keyboard is shown in this style. For example: + +To use @key{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. + +@item @key{key-combination} + +A combination of keystrokes is represented in this way. For example: + +The @key{Ctrl-Alt-Backspace} key combination exits your graphical +session and returns you to the graphical login screen or the console. + +@item @code{computer output} + +Text in this style indicates text displayed to a shell prompt such as +error messages and responses to commands. For example: + +The @command{ls} command displays the contents of a directory. For example: + +@verbatim +Config help_renameEntry.sh +help_copyEntry.sh help_restoreCrossReferences.sh +help_deleteCrossReferences.sh help_searchIndex.sh +@end verbatim + +The output returned in response to the command (in this case, the +contents of the directory) is shown in this style. +@end table + +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: + +@quotation +@strong{Note} Remember that Linux is case sensitive. In other words, a +rose is not a ROSE is not a rOsE. +@end quotation + +@quotation +@strong{Tip} The directory @file{/usr/share/doc/} contains additional +documentation for packages installed on your system. +@end quotation + +@quotation +@strong{Important} If you modify the DHCP configuration file, the +changes do not take effect until you restart the DHCP daemon. +@end quotation + +@quotation +@strong{Caution} Do not perform routine tasks as root --- use a +regular user account unless you need to use the root account for +system administration tasks. +@end quotation + +@quotation +@strong{Warning} Be careful to remove only the necessary partitions. +Removing other partitions could result in data loss or a corrupted +system environment. +@end quotation diff --git a/Manuals/TCAR-UG/Texinfo/en_US/Introduction/feedback.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/feedback.texinfo new file mode 100644 index 0000000..1c7f597 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/feedback.texinfo @@ -0,0 +1,9 @@ +If you find an error in the @emph{CentOS Artwork Repository}, or if +you have thought of a way to make this manual better, we would like to +hear from you! Share your suggestions in the appropriate mailing list +(@url{http://lists.centos.org/}) and/or bug tracker +(@url{http://bugs.centos.org/}). + +When you make 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/Texinfo/en_US/Introduction/history.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/history.texinfo new file mode 100755 index 0000000..7bfcada --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/history.texinfo @@ -0,0 +1,142 @@ +The CentOS Artwork Repository started during a discussion about how to +automate the slide images of Anaconda, at CentOS Developers mailing +list (@email{centos-devel@@centos.org}) around 2008. 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 The CentOS Community---. + +Karanbirn Sighn considered the idea intresting and provided the +infrastructure necessary to support the effort. This way the CentOS +Artwork SIG (@url{https://projects.centos.org/trac/artwork/}) and the +CentOS Artwork Repository +(@url{https://projects.centos.org/svn/artwork/}) were officially +created. + +Once the CentOS Artwork Repository was available, Alain Reguera +Delgado uploaded the bash script for rendering Anaconda slides; Ralph +Angenendt documented it very well; and people started to download +working copies of CentOS Artwork Repository to produce slide images in +their own languages. + +@subheading 2009 + +Around 2009, the rendition script was at a very rustic state where +only slide images could be produced, so it was redesigned to extend +the image production to other areas, different from slide images. In +this configuration, one SVG file was used as input to produce a +translated instance of it which, in turn, was used to produce one +translated PNG image as output. The SVG translated instance was +created through SED replacement commands. The translated PNG image was +created from the SVG translated instance using Inkscape command-line +interface. + +The repository directory structure was prepared to receive the +rendition script using design templates and translation files in the +same location. There was one directory structure for each artwork that +needed to be produced. In this configuration, if you would want to +produce the same artwork with a different visual style or structure, +it was needed to create a new directory structure for it because both +the image structure and the image visual style were together in the +design template. + +The rendition script was moved to a common place and linked from +different directory structures. There was no need to have the same +code in different directory structures if it could be in just one +place and then be linked from different locations. + +Corporate identity concepts began to be considered. As referece, it +was used the book ``Corporate Identity'' by Wally Olins (1989) and +Wikipedia related links (e.g., +@url{http://en.wikipedia.org/Corporate_identity}). This way, the +rendition script main's goal becomes into: automate production of a +monolithic corporate visual identity structure, based on the mission +and the release schema of The CentOS Project. + +The repository directory structures began to be documented by mean of +flat text files. Later, documentation in flat text files was moved +onto LaTeX format and this way the ``The CentOS Artwork Repository'' +documentation manual is initiated. + +@subheading 2010 + +Around 2010, the rendition script changed its name from +@command{render.sh} to @command{centos-art.sh} and became a collection +of functionalities where rendition was just one among others (e.g., +documenting and localizing). + +The @command{centos-art.sh} was initially conceived to automate +frequent tasks inside the repository based in the idea of Unix +toolbox: @emph{to create small and specialized tools that do one thing +well}. This way, functionalities inside @command{centos-art.sh} began +to be identified and separated one another. For example, when images +were rendered, there was no need to load functionalities related to +documentation manual. This layout moved us onto ``common +functionalities'' and ``specific functionalities'' inside +@command{centos-art.sh} script. Common functionalities are loaded when +@command{centos-art.sh} script is initiated and are available to +specific functionalities. + +Suddenly, no need was found to keep all the links spreaded around the +repository in order to execute the @command{centos-art.sh} script from +different locations. The @command{centos-art} command-line interface +was used instead. The @command{centos-art} command-line interface is a +symbolic link stored inside the @file{~/bin} directory that point to +@command{centos-art.sh} script. As default configuration, inside The +CentOS Distribution, the path to @file{~/bin} is included in the +search path for commands (see @env{PATH} environment variable). This +way, using the @command{centos-art} command-line interface, it is +possible for us to execute the @command{centos-art.sh} script from +virtually anywhere inside the workstation, just as we frequently do +with regular commands. + +Start using GNU @command{getopt} as default option parser inside the +@command{centos-art.sh} script. + +The repository directory structure was updated to improve the +implementation of corporate visual identity concepts. Specially in +the area related to themes. Having both structure and style in the +same file introduced content duplication when producing art works. +Because of this reason, they were divided out to separate directory +structures: the design models and artistic motifs directory +structures. From this point on, the @command{centos-art.sh} is able +to produce themes as result of arbitrary combinations between design +models (structures) and artistic motifs (visual styles). + +In the documentation area, the documents in LaTeX format were migrated +to Texinfo format. In this configuration, each directory structure in +the repository has a documentation entry associated in a Texinfo +structure which can be read, edited and administered (e.g., renamed, +deleted and copied) interactively through @command{centos-art.sh} +script. Additionally, the @command{texi2html} program was used to +produced customized XHTML output in conjunction with CSS from The +CentOS Webenv. + +@subheading 2011 + +Around 2011, the @command{centos-art.sh} script was redesigned to +start translating XML-based files (e.g., SVG and Docbook files) +through @command{xml2po} program and shell scripts (e.g., Bash +scripts) through GNU @command{gettext} tools. This configuration +provided a stronger localization interface for graphic designers, +translators and programmers. The SED replacement files are no longer +used to handle localization. + +The @code{render}, @code{help} and @code{locale} functionalities were +consolidated as the most frequent tasks performed inside the +repository. Additionally, the @code{prepare} and @code{tuneup} +functionalities are also maintained as useful tasks. + +In the documentation area, support for producing localized +transformations of DocBook XML DTD instances was added through the +@code{render} and @code{locale} functionalities. The @code{render} +functionality uses the @command{xsltproc} command-line XSLT parser in +conjunction with the styles provided by the @file{docbook-style-xsl} +package, both of them included inside The CentOS Distribution. The +@code{locale} functionality creates the localized @acronym{PO,Portable +Objects} the @code{render} functionality needs to produce localized +transformations of DocBook XML DTD instances. diff --git a/Manuals/TCAR-UG/Texinfo/en_US/Introduction/repo-convenctions.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/repo-convenctions.texinfo new file mode 100644 index 0000000..323113b --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Introduction/repo-convenctions.texinfo @@ -0,0 +1,286 @@ +The CentOS Artwork Repository is supported by Subversion +(@url{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. + +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. + +@subheading Policy +@cindex 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 +(@email{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 other changes from your +working copy to CentOS Artwork Repository as long as you behave as a +good cooperating citizen. Otherwise, your rights to commit changes +might be temporarly revoked or permanently banished. + +As a good cooperating citizen one understand of a person who respects +the work already done by others and share ideas with authors before +changing relevant parts of their work, specially in situations when +the access required to realize the changes has been granted already. +Of course, there is a time when conversation has taken place, the +paths has been traced and changing the work is so obvious that there +is no need for you to talk about it; that's because you already did, +you already built the trust to keep going. Anyway, the mailing list +mentioned above is available for sharing ideas in a way that good +relationship between community citizens could be constantly balanced. + +The relationship between community citizens is monitored by repository +administrators. Repository administrators are responsible of granting +that everything goes the way it needs to go in order for the CentOS +Artwork Repository to accomplish its mission which is: to provide a +colaborative tool for The CentOS Community where The CentOS Project +corporate visual identity is built and maintained by The CentOS +Community itself. + +It is also important to remember that all the program and +documentation source files inside CentOS Artwork Repository must +comply the terms of @ref{GNU General Public License} and @ref{GNU Free +Documentation License} respectively in order for them to remain inside +the repository. + +@subheading Work lines +@cindex Work lines + +Content production inside the repository is organized by work lines. +There are three major work lines of production inside The CentOS +Artwork Repository, which are: Graphic design, Documentation and +Localization. The specific way of producing content inside each +specific work line is standardized by mean of centos-art.sh script +(which in turn, can be considered a work line by itself [e.g., the +Automation work line]). The centos-art.sh script provides one specific +functionality for automating each major work line of content +production (e.g., render for producing images, help for manage +documentation, and locale for localizing contents). + +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. The graphic design work line is organized in +@pxref{Directories trunk Identity}. + +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. +The documentation work line is organized in @pxref{Directories trunk +Manuals}. + +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). The localization work line is +organized in @pxref{Directories trunk Manuals}. + +The automation work line exists to standardize content production +inside the working copies of CentOS Artwork Repository. Here is +developed the centos-art.sh script, a bash script specially designed +to automate most frequent tasks (e.g., rendition, documentation and +localization) inside the repository. There is no need to type several +tasks, time after time, if they can be programmed into just one +executable script. The automation work line is organized in +@pxref{Directories trunk Manuals}. + +@subheading Relation between directories +@cindex Relation between directories +@cindex Master paths +@cindex Auxiliar paths + +In order for automation scripts to produce content inside a working +copy of CentOS Artwork Repository, it is required that all work lines +be related somehow. The relation is used by automation scripts to know +where to retrive the information they need to work with (e.g., design +model, translation messages, output locations, etc.). This kind of +relation is built using two path constructions named ``master paths'' +and ``auxiliar paths''. + +The master path points only to directories that contain source files +(e.g., SVG files) required to produce output base content (e.g., PNG +files) through automation scripts. Each master path inside the +repository may have several auxiliar paths associated, but auxiliar +paths can only have one master path associated. + +Master paths used for producing images through SVG rendition are +organized under @file{trunk/Identity/Models} directory structure and +the auxiliar paths under @file{trunk/Identity/Images}, +@file{trunk/Locales} and @file{trunk/Manuals} directory structures. + +Auxiliar paths can point either to directories or files. When an +auxiliar path points to a directory, that directory contains +information that modifies somehow the content produced from master +paths (e.g., translation messages) or provides the output information +required to know where the content produced from the master path +should be stored. When an auxiliar path points to a file, that file +has no other purpose but to document the master path it refers to. + +Auxiliar paths should never be modified under any reason but to +satisfy the relationship with the master path. Liberal change of +auxiliar paths may suppress the conceptual idea they were initially +created for; and certainly, automation scripts may stop working as +expected. + +The relationship between auxiliar paths and master paths is built by +combining the master path and the second level directory structures of +the repository. The master path is considered the path identifier and +the repository second level directory structure is considered the +common part of the path where the path identifier is appended to. So, +if we have the master path @file{trunk/Identity/Models/Brands}, we'll +end up having, at least, the @file{trunk/Identity/Images/Brands} +auxiliar path for storing output files and, optionally, one path under +trunk/Manuals for storing documentation and one path under +@file{trunk/Locales} for storing localizations. + +@subheading Syncronizing path information +@cindex Syncronizing path information + +Once both master paths and their auxiliar paths have been set, they +shouldn't be changed. Assuming one master path must be changed it is +required that all related auxiliar paths be changed, too. This is +required in order for master paths to retain their relation with +auxiliar paths. This process of keeping relation between master paths +and auxiliar paths is known as path syncronization. + +Path syncronization is required for automation scripts to know where +to store final output, where to retrive translation messages, +documentation, and any information that might be desired. If the +relation between master paths and auxiliar paths is lost, there is no +way for centos-art.sh script to know where to retrive the information +it needs to work with. Path syncronization is the way we use to +organize and extend the information stored in the repository. + +Path syncronization may imply both movement of files and replacement +of content inside files. Movement of files is related to actions like +renaming files and directories inside the repository. Replacement of +content inside files is related to actions like replacing information +(e.g., paths information) inside files in order to keep file contents +and file locations consistent one another. + +The order followed to syncronize path information is very important +because the versioned nature of the repository files we are working +with. When a renaming action must be performed, we avoid making +replacements inside files first and file movements later. This would +require two commit actions: one for the files' internal changes and +another for the file movement itself. Otherwise, we prefer to perform +file movements first and file internal replacements later. This way it +is possible to commit both changes as if they were just one. + +@quotation +@strong{Warning} There is no support for URLs actions inside +@command{centos-art.sh} script. The @command{centos-art.sh} script is +designed to work with local files inside the working copy only. If you +need to perform URL actions directly, use Subversion commands instead. +@end quotation + +At this moment there is no full implementation of path syncronization +process inside @command{centos-art.sh} script except by ``texinfo'' +backend of help functionality which provides a restricted +implementation of path syncronization to this specific area of +documentation through the @option{--copy}, @option{--delete} and +@option{--rename} options. The plan for a full implementation of path +syncronization would be to create individual restricted +implementations like this one for other areas that demand it and then, +create a higher implmentation that combines all restricted +implementations as needed. This way, if we try to rename a repository +directory the higer action will define which are all the restricted +actions that should be performed in order for make a full path +syncronization. For example, if the directory we are renaming is part +of graphic design work line, it is required to syncronize related +paths in documentation and localization work lines. Likewise, if the +directory we are renaming is in documentation work line, it is +required to syncronize related paths in graphic design and +localization work lines. In all these cases, the direction used for +syncronizing paths must be from master path to auxiliar path and never +the opposite (i.e., rename the master path first and auxiliar paths +later). + +A practical example, through which you can notice the usefulness of +keeping paths syncronized, is what happen when documentation entries +are renamed (@pxref{Directories trunk Scripts Functions Help}). + +@subheading Extending repository organization +@cindex Extending repository organization + +Occasionly, you may find that new components of The CentOS Project +corporate visual identity need to be added to the repository in order +to work them out. If that is the case, the first question we need to +ask ourselves, before start to create directories blindly all over, +is: What is the right place to store it? + +The best place to find answers is in The CentOS Community (see page +@url{http://wiki.centos.org/Help}), but going there with hands empty +is not good idea. It may give the impression you don't really care +about. Instead, consider the following suggestions to find your own +comprehension in order to make your own propositions based on it. + +When extending respository structure it is very useful to bear in mind +The CentOS Project corporate visual identity structure, The CentOS +Mission and The CentOS Release Schema. The rest is a matter of +choosing appropriate names. It is also worth to know that each +directory in the repository responds to a conceptual idea that +justifies its existence. + +To build a directory structure inside the repository, you need to +define the conceptual idea first and later create the directory, +remembering that there are locations inside the repository that define +conceptual ideas you probably would prefer to reuse. For example, the +@file{trunk/Identity/Images/Themes} directory stores theme artistic +motifs, the @file{trunk/Identity/Models/Themes} directory stores theme +design models, the trunk/Manuals directory stores documentation files, +the @file{trunk/Locales} stores translation messages, and the +@file{trunk/Scripts} stores automation scripts. + +To better illustrate this desition process, you can consider to examin +the @file{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 @code{help} functionality of +@command{centos-art.sh} script (@pxref{Directories trunk Scripts +Functions Help}). + +@subheading File names convenction +@cindex File names convenction + +Inside the CentOS Artwork Repository, generally, file names are all +written in lowercase (e.g., @file{01-welcome.png}, @file{splash.png}, +@file{anaconda_header.png}, etc.) and directory names are all written +capitalized (e.g., @file{Identity}, @file{Themes}, @file{Motifs}) and +sometimes in cammel case (e.g., @file{TreeFlower}, etc.). + +In the very specific case of repository documentation entries, file +names follow the directory naming convenction. This is because they +are documenting directories and that is something we want to remark. +So, to better describe what we are documenting, documentation entries +follow the name convenction used by the item they document. + +@subheading Layout +@cindex Layout + +The CentOS Artwork Repository is organized through a convenctional +``trunk'', ``branches'' and ``tags'' layout. For a complete reference +of each directory inside the repository @pxref{Directories}. diff --git a/Manuals/TCAR-UG/Texinfo/en_US/Licenses/chapter-menu.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Licenses/chapter-menu.texinfo new file mode 100755 index 0000000..b8240ba --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Licenses/chapter-menu.texinfo @@ -0,0 +1,4 @@ +@menu +* GNU General Public License:: +* GNU Free Documentation License:: +@end menu diff --git a/Manuals/TCAR-UG/Texinfo/en_US/Licenses/chapter-nodes.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Licenses/chapter-nodes.texinfo new file mode 100755 index 0000000..2a33229 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Licenses/chapter-nodes.texinfo @@ -0,0 +1,9 @@ +@node GNU General Public License +@section GNU General Public License +@cindex GNU General Public License +@include trunk/Scripts/Functions/Help/Texinfo/Templates/en_US/Licenses/GPL.texinfo + +@node GNU Free Documentation License +@section GNU Free Documentation License +@cindex GNU Free Documentation License +@include trunk/Scripts/Functions/Help/Texinfo/Templates/en_US/Licenses/GFDL.texinfo diff --git a/Manuals/TCAR-UG/Texinfo/en_US/Licenses/chapter.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/Licenses/chapter.texinfo new file mode 100755 index 0000000..27e70ae --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/Licenses/chapter.texinfo @@ -0,0 +1,5 @@ +@node Licenses +@chapter Licenses +@cindex Licenses +@include Licenses/chapter-menu.texinfo +@include Licenses/chapter-nodes.texinfo diff --git a/Manuals/TCAR-UG/Texinfo/en_US/repository-index.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/repository-index.texinfo new file mode 100644 index 0000000..abe002c --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/repository-index.texinfo @@ -0,0 +1,3 @@ +@node Index +@unnumbered Index +@printindex cp diff --git a/Manuals/TCAR-UG/Texinfo/en_US/repository-menu.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/repository-menu.texinfo new file mode 100644 index 0000000..89f2a86 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/repository-menu.texinfo @@ -0,0 +1,6 @@ +@menu +* Introduction:: +* Directories:: +* Licenses:: +* Index:: +@end menu diff --git a/Manuals/TCAR-UG/Texinfo/en_US/repository-nodes.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/repository-nodes.texinfo new file mode 100644 index 0000000..722d48f --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/repository-nodes.texinfo @@ -0,0 +1,3 @@ +@include Introduction/chapter.texinfo +@include Directories/chapter.texinfo +@include Licenses/chapter.texinfo diff --git a/Manuals/TCAR-UG/Texinfo/en_US/repository.texinfo b/Manuals/TCAR-UG/Texinfo/en_US/repository.texinfo new file mode 100644 index 0000000..6e5fd30 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/en_US/repository.texinfo @@ -0,0 +1,54 @@ +\input texinfo @c -*-texinfo-*- +@c $Id$ +@setfilename repository.info +@settitle The CentOS Artwork Repository +@afourpaper +@finalout + +@c -- Summary Description and Copyright ----------------------- +@copying +This manuals documents relevant information regarding the deployment, +organization, and administration of CentOS Artwork Repository. + +Copyright @copyright{} 2009, 2010, 2011 The CentOS Artwork SIG + +Permission is granted to copy, distribute and/or modify this document +under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no +Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A +copy of the license is included in the section entitled @ref{GNU Free +Documentation License}. +@end copying + +@c -- Titlepage, Contents, Copyright --------------------------- + +@titlepage +@title The CentOS Artwork Repository +@subtitle Reference Manual +@author Alain Reguera Delgado +@page +@vskip 0pt plus 1filll +@insertcopying +@end titlepage + +@contents + +@c -- `Top' Node and Master Menu ------------------------------- + +@ifnottex +@node Top +@top The CentOS Artwork Repository +@insertcopying +@end ifnottex + +@include repository-menu.texinfo + +@c -- The Body of the Document -------------------------------- + +@include repository-nodes.texinfo + +@c -- The End of the Document --------------------------------- + +@include repository-index.texinfo + +@bye diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Directories/branches.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/branches.texinfo new file mode 100644 index 0000000..47252e0 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/branches.texinfo @@ -0,0 +1,21 @@ +@subheading Objetivos + +El directorio @file{branches} organiza @dots{} + +@subheading Descripción + +@itemize +@item ... +@end itemize + +@subheading Uso + +@itemize +@item ... +@end itemize + +@subheading Vea además + +@itemize +@item @dots{} +@end itemize diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Directories/chapter-menu.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/chapter-menu.texinfo new file mode 100644 index 0000000..2cd6d67 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/chapter-menu.texinfo @@ -0,0 +1,10 @@ +@menu +* Directories branches:: +* Directories tags:: +* Directories trunk:: +* Directories trunk Identity:: +* Directories trunk Scripts:: +* Directories trunk Scripts Functions:: +* Directories trunk Scripts Functions Help:: +* Directories trunk Scripts Functions Help Backends:: +@end menu diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Directories/chapter-nodes.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/chapter-nodes.texinfo new file mode 100644 index 0000000..b45c868 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/chapter-nodes.texinfo @@ -0,0 +1,40 @@ +@node Directories branches +@section El directorio @file{branches} +@cindex Directories branches +@include Directories/branches.texinfo + +@node Directories tags +@section El directorio @file{tags} +@cindex Directories tags +@include Directories/tags.texinfo + +@node Directories trunk +@section El directorio @file{trunk} +@cindex Directories trunk +@include Directories/trunk.texinfo + +@node Directories trunk Identity +@section El directorio @file{trunk/Identity} +@cindex Directories trunk Identity +@include Directories/trunk/Identity.texinfo + +@node Directories trunk Scripts +@section El directorio @file{trunk/Scripts} +@cindex Directories trunk Scripts +@include Directories/trunk/Scripts.texinfo + +@node Directories trunk Scripts Functions +@section El directorio @file{trunk/Scripts/Functions} +@cindex Directories trunk Scripts Functions +@include Directories/trunk/Scripts/Functions.texinfo + +@node Directories trunk Scripts Functions Help +@section El directorio @file{trunk/Scripts/Functions/Help} +@cindex Directories trunk Scripts Functions Help +@include Directories/trunk/Scripts/Functions/Help.texinfo + +@node Directories trunk Scripts Functions Help Backends +@section El directorio @file{trunk/Scripts/Functions/Help/Backends} +@cindex Directories trunk Scripts Functions Help Backends +@include Directories/trunk/Scripts/Functions/Help/Backends.texinfo + diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Directories/chapter.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/chapter.texinfo new file mode 100644 index 0000000..cb021d9 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/chapter.texinfo @@ -0,0 +1,16 @@ +@node Directories +@chapter Los directorios del repositorio +@cindex Directorios + +El Repositorio Artístico de CentOS usa directorios para organizar +ficheros y describir ideas relacionadas a la identidad corporativa de +El Proyecto CentOS. Tales ideas están explicadas en cada una de las +entradas de documentation asociadas a los directorios del repositorio. + +En este capítulo usted aprenderá cuáles son los directorios del +repositorio, para qué son y cómo pude utilizarlos. Para comenzar, +seleccione uno de los directorios siguientes para conocer más sobre +él: + +@include Directories/chapter-menu.texinfo +@include Directories/chapter-nodes.texinfo diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Directories/tags.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/tags.texinfo new file mode 100644 index 0000000..878663f --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/tags.texinfo @@ -0,0 +1,21 @@ +@subheading Objetivos + +El directorio @file{tags} organiza @dots{} + +@subheading Descripción + +@itemize +@item ... +@end itemize + +@subheading Uso + +@itemize +@item ... +@end itemize + +@subheading Vea además + +@itemize +@item @dots{} +@end itemize diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk.texinfo new file mode 100644 index 0000000..f24ee02 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk.texinfo @@ -0,0 +1,21 @@ +@subheading Objetivos + +El directorio @file{trunk} organiza @dots{} + +@subheading Descripción + +@itemize +@item ... +@end itemize + +@subheading Uso + +@itemize +@item ... +@end itemize + +@subheading Vea además + +@itemize +@item @dots{} +@end itemize diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Identity.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Identity.texinfo new file mode 100644 index 0000000..f62b838 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Identity.texinfo @@ -0,0 +1,21 @@ +@subheading Objetivos + +El directorio @file{trunk/Identity} organiza @dots{} + +@subheading Descripción + +@itemize +@item ... +@end itemize + +@subheading Uso + +@itemize +@item ... +@end itemize + +@subheading Vea además + +@itemize +@item @ref{Directories trunk} +@end itemize diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts.texinfo new file mode 100644 index 0000000..a082d19 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts.texinfo @@ -0,0 +1,21 @@ +@subheading Objetivos + +El directorio @file{trunk/Scripts} organiza @dots{} + +@subheading Descripción + +@itemize +@item ... +@end itemize + +@subheading Uso + +@itemize +@item ... +@end itemize + +@subheading Vea además + +@itemize +@item @ref{Directories trunk} +@end itemize diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts/Functions.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts/Functions.texinfo new file mode 100644 index 0000000..ba9b35c --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts/Functions.texinfo @@ -0,0 +1,22 @@ +@subheading Objetivos + +El directorio @file{trunk/Scripts/Functions} organiza @dots{} + +@subheading Descripción + +@itemize +@item ... +@end itemize + +@subheading Uso + +@itemize +@item ... +@end itemize + +@subheading Vea además + +@itemize +@item @ref{Directories trunk Scripts} +@item @ref{Directories trunk} +@end itemize diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts/Functions/Help.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts/Functions/Help.texinfo new file mode 100644 index 0000000..bf45a23 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts/Functions/Help.texinfo @@ -0,0 +1,40 @@ +@subheading Nombre + +El directorio @file{trunk/Scripts/Functions/Help} organiza @dots{} + +@subheading Sinopsis + +@dots{} + +@subheading Descripción + +@dots{} + +@subheading Ejemplos + +@dots{} + +@subheading Autor + +Escrito por @dots{} + +@subheading Reporte de errores + +Reporte los errores a la lista de correo @email{centos-artwork@@centos.org}. + +@subheading Derecho de copia + +Copyright @copyright{} 2009, 2010, 2011 The CentOS Project + +Esto es software libre. Usted pude redistribuir copias de ello bajo +los términos de la Licencia Pública General GNU (@pxref{GNU +General Public License}). Hasta donde la ley se extiende, NO HAY +GARANTÍA. + +@subheading Vea además + +@itemize +@item @ref{Directories trunk Scripts Functions} +@item @ref{Directories trunk Scripts} +@item @ref{Directories trunk} +@end itemize diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts/Functions/Help/Backends.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts/Functions/Help/Backends.texinfo new file mode 100644 index 0000000..1327702 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Directories/trunk/Scripts/Functions/Help/Backends.texinfo @@ -0,0 +1,24 @@ +@subheading Objetivos + +El directorio @file{trunk/Scripts/Functions/Help/Backends} organiza @dots{} + +@subheading Descripción + +@itemize +@item ... +@end itemize + +@subheading Uso + +@itemize +@item ... +@end itemize + +@subheading Vea además + +@itemize +@item @ref{Directories trunk Scripts Functions Help} +@item @ref{Directories trunk Scripts Functions} +@item @ref{Directories trunk Scripts} +@item @ref{Directories trunk} +@end itemize diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Licenses/chapter-menu.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Licenses/chapter-menu.texinfo new file mode 100755 index 0000000..b8240ba --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Licenses/chapter-menu.texinfo @@ -0,0 +1,4 @@ +@menu +* GNU General Public License:: +* GNU Free Documentation License:: +@end menu diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Licenses/chapter-nodes.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Licenses/chapter-nodes.texinfo new file mode 100755 index 0000000..7148d15 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Licenses/chapter-nodes.texinfo @@ -0,0 +1,9 @@ +@node GNU General Public License +@section Licencia Pública General de GNU +@cindex Licencia pública general GNU +@include trunk/Scripts/Functions/Help/Texinfo/Templates/es_ES/Licenses/GPL.texinfo + +@node GNU Free Documentation License +@section Licencia de Documentación Libre de GNU +@cindex Licencia documentación libre GNU +@include trunk/Scripts/Functions/Help/Texinfo/Templates/es_ES/Licenses/GFDL.texinfo diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/Licenses/chapter.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/Licenses/chapter.texinfo new file mode 100755 index 0000000..38edb4b --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/Licenses/chapter.texinfo @@ -0,0 +1,5 @@ +@node Licenses +@chapter Licencias +@cindex Licencias +@include Licenses/chapter-menu.texinfo +@include Licenses/chapter-nodes.texinfo diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/repository-index.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/repository-index.texinfo new file mode 100755 index 0000000..d168d12 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/repository-index.texinfo @@ -0,0 +1,3 @@ +@node Index +@unnumbered Índice +@printindex cp diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/repository-menu.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/repository-menu.texinfo new file mode 100644 index 0000000..a7cb577 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/repository-menu.texinfo @@ -0,0 +1,5 @@ +@menu +* Directories:: +* Licenses:: +* Index:: +@end menu diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/repository-nodes.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/repository-nodes.texinfo new file mode 100644 index 0000000..3bf2339 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/repository-nodes.texinfo @@ -0,0 +1,2 @@ +@include Directories/chapter.texinfo +@include Licenses/chapter.texinfo diff --git a/Manuals/TCAR-UG/Texinfo/es_ES/repository.texinfo b/Manuals/TCAR-UG/Texinfo/es_ES/repository.texinfo new file mode 100644 index 0000000..e45d8b3 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/es_ES/repository.texinfo @@ -0,0 +1,58 @@ +\input texinfo @c -*-texinfo-*- +@c $Id$ +@c -- Header -------------------------------------------------- + +@setfilename repository.info +@settitle El Repositorio Artístico de CentOS +@documentlanguage es +@afourpaper +@finalout + +@c -- Summary description and copyright ----------------------- + +@copying +Este manual documenta información relevante al desempeño, organización +y administración del repositorio artístico del proyecto CentOS. + +Copyright @copyright{} 2009, 2010, 2011 The CentOS Artwork SIG + +Se otorga permiso para copiar, distribuir y/o modificar este documento +bajo los términos de la Licencia de Documentación Libre de GNU, +Versión 1.1 o cualquier otra versión posterior publicada por la +Free Software Foundation; con las Secciones Invariantes, con Textos de +Cubierta Delantera, y con los Textos de Cubierta Trasera. Una copia +de la licencia está incluida en la sección titulada @ref{GNU Free +Documentation License}. +@end copying + +@c -- Titlepage, contents, copyright --------------------------- + +@titlepage +@title El Repositorio Artístico de CentOS +@subtitle Manual de Referencia +@author The CentOS Project +@page +@vskip 0pt plus 1filll +@insertcopying +@end titlepage +@contents + +@c -- `Top' node and master menu ------------------------------- + +@ifnottex +@node Top +@top El Repositorio Artístico de CentOS +@insertcopying +@end ifnottex + +@include repository-menu.texinfo + +@c -- The body of the document -------------------------------- + +@include repository-nodes.texinfo + +@c -- The end of the document --------------------------------- + +@include repository-index.texinfo + +@bye diff --git a/Manuals/TCAR-UG/Texinfo/repository-init.pl b/Manuals/TCAR-UG/Texinfo/repository-init.pl new file mode 100755 index 0000000..cff5a53 --- /dev/null +++ b/Manuals/TCAR-UG/Texinfo/repository-init.pl @@ -0,0 +1,389 @@ +#!/usr/bin/perl +# +# repository.init -- This file initializes Texi2HTML program to +# produce the repository documentation manual using the CentOS Web +# Environment XHTML and CSS standard definition. +# +# Copyright (C) 2009-2011 Alain Reguera Delgado +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, but +# WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +# General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, write to the Free Software +# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 +# USA. +# ---------------------------------------------------------------------- +# $Id$ +# ---------------------------------------------------------------------- + +# -iso +# if set, ISO8859 characters are used for special symbols (like +# copyright, etc) +$USE_ISO = 1; + +# -I +# add a directory to the list of directories where @include files are +# searched for (besides the directory of the file). additional '-I' +# args are appended to this list. (APA: Don't implicitely search ., +# to conform with the docs!) my @INCLUDE_DIRS = ("."); +@INCLUDE_DIRS = ("/home/centos/artwork"); + +# Extension used on output files. +$EXTENSION = "xhtml"; + +# Horizontal rules. +$DEFAULT_RULE = '';
+$SMALL_RULE = $DEFAULT_RULE;
+$MIDDLE_RULE = $DEFAULT_RULE;
+$BIG_RULE = $DEFAULT_RULE;
+
+# -split section|chapter|node|none
+# if $SPLIT is set to 'section' (resp. 'chapter') one html file per
+# section (resp. chapter) is generated. If $SPLIT is set to 'node' one
+# html file per node or sectionning element is generated. In all these
+# cases separate pages for Top, Table of content (Toc), Overview and
+# About are generated. Otherwise a monolithic html file that contains
+# the whole document is created.
+$SPLIT = 'section';
+
+# -sec-nav|-nosec-nav
+# if this is set then navigation panels are printed at the beginning
+# of each section. If the document is split at nodes then navigation
+# panels are printed at the end if there were more than $WORDS_IN_PAGE
+# words on page.
+#
+# If the document is split at sections this is ignored.
+#
+# This is most useful if you do not want to have section navigation
+# with -split chapter. There will be chapter navigation panel at the
+# beginning and at the end of chapters anyway.
+$SECTION_NAVIGATION = 1;
+
+# Layout control
+$print_page_head = \&T2H_XHTML_print_page_head;
+$print_page_foot = \&T2H_XHTML_print_page_foot;
+$print_frame = \&T2H_XHTML_print_frame;
+$button_icon_img = \&T2H_XHTML_button_icon_img;
+$print_navigation = \&T2H_XHTML_print_navigation;
+
+#FIXME update once it is more stabilized in texi2html.init
+sub T2H_XHTML_print_page_head
+{
+ my $fh = shift;
+ my $longtitle = "$Texi2HTML::THISDOC{'title_unformatted'}";
+ $longtitle .= ": $Texi2HTML::UNFORMATTED{'This'}" if exists $Texi2HTML::UNFORMATTED{'This'};
+ print $fh <
+
+
+
+
+
+
+EOT
+}
+
+# / in
+
+
+
+
+
+
+
+EOT
+}
+
+sub T2H_XHTML_print_page_foot
+{
+ my $fh = shift;
+ my @date=localtime(time);
+ my $year=$date[5] += 1900;
+ my $program_string = program_string();
+ print $fh <$program_string
+
+
+
+ '; + +# formatting functions + +$def_line = \&t2h_xhtml_def_line; +$index_summary = \&t2h_xhtml_index_summary; +$image = \&t2h_xhtml_image; + +# need / in
\n" if (@$nonalpha and @$alpha); + if (@$nonalpha) + { + $nonalpha_text = join("\n \n", @$nonalpha) . "\n"; + } + if (@$alpha) + { + $alpha_text = join("\n \n", @$alpha) . "\n \n"; + } + #I18n + return "
| " . &$I('Jump to') . ": | " . + $nonalpha_text . $join . $alpha_text . ' |
|---|
| }; + + if (ref($button) eq 'CODE') + { + &$button($fh, $vertical); + } + elsif (ref($button) eq 'SCALAR') + { + print $fh "$$button" if defined($$button); + } + elsif (ref($button) eq 'ARRAY') + { + my $text = $button->[1]; + my $button_href = $button->[0]; + if (defined($button_href) and !ref($button_href) + and defined($text) and (ref($text) eq 'SCALAR') and defined($$text)) + { # use given text + if ($Texi2HTML::HREF{$button_href}) + { + print $fh "" . + &$anchor('', + $Texi2HTML::HREF{$button_href}, + $$text + ) + ; + } + else + { + print $fh $$text; + } + } + } + elsif ($button eq ' ') + { # handle space button + print $fh + $ICONS && $ACTIVE_ICONS{' '} ? + &$button_icon_img($button, $ACTIVE_ICONS{' '}) : + $NAVIGATION_TEXT{' '}; + #next; + } + elsif ($Texi2HTML::HREF{$button}) + { # button is active + my $btitle = $BUTTONS_GOTO{$button} ? + 'title="' . ucfirst($BUTTONS_GOTO{$button}) . '"' : ''; + if ($ICONS && $ACTIVE_ICONS{$button}) + { # use icon + print $fh '' . + &$anchor('', + $Texi2HTML::HREF{$button}, + &$button_icon_img($button, + $ACTIVE_ICONS{$button}, + #$Texi2HTML::NAME{$button}), + $Texi2HTML::NO_TEXI{$button}), + $btitle + ); + } + else + { # use text + print $fh + '[' . + &$anchor('', + $Texi2HTML::HREF{$button}, + $NAVIGATION_TEXT{$button}, + $btitle + ) . + ']'; + } + } + else + { # button is passive + print $fh + $ICONS && $PASSIVE_ICONS{$button} ? + &$button_icon_img($button, + $PASSIVE_ICONS{$button}, + #$Texi2HTML::NAME{$button}) : + $Texi2HTML::NO_TEXI{$button}) : + + "[" . $NAVIGATION_TEXT{$button} . "]"; + } + print $fh " | \n"; + print $fh "