-
-
-
-
-
-
-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 "
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/Repository/en_US/Introduction/authors.texinfo b/Manuals/Repository/en_US/Introduction/authors.texinfo new file mode 100755 index 0000000..f62bdd3 --- /dev/null +++ b/Manuals/Repository/en_US/Introduction/authors.texinfo @@ -0,0 +1,41 @@ +This section records authoring information of CentOS Artwork +Repository along the years: + +@subheading Graphic Design + +@itemize +@item Guideon de Kok +@item @email{al@@art.centos.org,Alain Reguera Delgado} +@item @email{mm@@art.centos.org,Marcus Moeller} +@end itemize + +@subheading Documentation + +@itemize +@item @email{al@@art.centos.org,Alain Reguera Delgado} +@item @email{ralph@@dev.centos.org,Ralph Angenendt} +@end itemize + +@subheading Localization + +@itemize +@item @email{al@@art.centos.org,Alain Reguera Delgado} (Spanish) +@end itemize + +@subheading Automation + +@itemize +@item @email{al@@art.centos.org,Alain Reguera Delgado} +@end itemize + +@subheading Infrastructure +@itemize +@item @email{karan@@dev.centos.org,Karanbirn Singh} +@item @email{ralph@@dev.centos.org,Ralph Angenendt} +@end itemize + +@subheading Packaging +@itemize +@item @email{karan@@dev.centos.org,Karanbirn Singh} +@item @email{ralph@@dev.centos.org,Ralph Angenendt} +@end itemize diff --git a/Manuals/Repository/en_US/Introduction/chapter-intro.texinfo b/Manuals/Repository/en_US/Introduction/chapter-intro.texinfo new file mode 100644 index 0000000..96fb6b2 --- /dev/null +++ b/Manuals/Repository/en_US/Introduction/chapter-intro.texinfo @@ -0,0 +1,21 @@ +Welcome to 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, task-oriented guide for +understanding how The CentOS Project Corporate Visual Identity is +produced, this is the manual for you. + +This manual discusses the following intermedite topics: + +@itemize +@item The CentOS Brand +@item The CentOS Corporate Visual Structure +@item The CentOS Corporate Visual Style +@end itemize + +This guide assumes you have a basic understanding of your CentOS +system. 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. diff --git a/Manuals/Repository/en_US/Introduction/chapter-menu.texinfo b/Manuals/Repository/en_US/Introduction/chapter-menu.texinfo new file mode 100644 index 0000000..39781c3 --- /dev/null +++ b/Manuals/Repository/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/Repository/en_US/Introduction/chapter-nodes.texinfo b/Manuals/Repository/en_US/Introduction/chapter-nodes.texinfo new file mode 100644 index 0000000..dff1350 --- /dev/null +++ b/Manuals/Repository/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/Repository/en_US/Introduction/chapter.texinfo b/Manuals/Repository/en_US/Introduction/chapter.texinfo new file mode 100644 index 0000000..de11d5f --- /dev/null +++ b/Manuals/Repository/en_US/Introduction/chapter.texinfo @@ -0,0 +1,6 @@ +@node Introduction +@chapter Introduction +@cindex Introduction +@include Introduction/chapter-intro.texinfo +@include Introduction/chapter-menu.texinfo +@include Introduction/chapter-nodes.texinfo diff --git a/Manuals/Repository/en_US/Introduction/copying.texinfo b/Manuals/Repository/en_US/Introduction/copying.texinfo new file mode 100755 index 0000000..b8dc0f2 --- /dev/null +++ b/Manuals/Repository/en_US/Introduction/copying.texinfo @@ -0,0 +1,89 @@ +Copyright @copyright{} 2009, 2010, 2011 The CentOS Project. + +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/Repository/en_US/Introduction/doc-convenctions.texinfo b/Manuals/Repository/en_US/Introduction/doc-convenctions.texinfo new file mode 100644 index 0000000..9a9cca6 --- /dev/null +++ b/Manuals/Repository/en_US/Introduction/doc-convenctions.texinfo @@ -0,0 +1,109 @@ +In this manual the personal pronoun @emph{we} is used to repesent +@emph{The CentOS Artwork SIG}. This is, the group of persons building +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: + +@table @command +@item 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 identity --render='path/to/dir'} command +to produce contents inside the @file{trunk/Identity} directory +structure. +@end table + +@table @file +@item 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. +@end table + +@table @key +@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. +@end table + +@table @key +@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. +@end table + +@table @code +@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/Repository/en_US/Introduction/feedback.texinfo b/Manuals/Repository/en_US/Introduction/feedback.texinfo new file mode 100644 index 0000000..1c7f597 --- /dev/null +++ b/Manuals/Repository/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/Repository/en_US/Introduction/history.texinfo b/Manuals/Repository/en_US/Introduction/history.texinfo new file mode 100755 index 0000000..d96b914 --- /dev/null +++ b/Manuals/Repository/en_US/Introduction/history.texinfo @@ -0,0 +1,139 @@ +This section records noteworthy changes of CentOS Artwork Repository +through years. + +@subheading 2008 + +The CentOS Artwork Repository started at CentOS Developers mailing +(@email{centos-devel@@centos.org}) during a discussion about how +to automate the slide images of Anaconda. 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 ---together 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 +Delagdo 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 + +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, not just 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 rendition script was named @command{render.sh}. + +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. + +The concepts about corporate identity began to be considered. As +referece, it was used the book ``Corporate Identity'' by Wally Olins +(1989) and Wikipedia +(@url{http://en.wikipedia.org/Corporate_identity}). This way, the +rendition script main's goal becomes to: automate production of a +monolithic corporate visual identity structure, based on the mission +and the release schema of The CentOS Project. + +The directory structures started to be documented inside the +repository using text files without markup. Later, documentation in +flat text files was moved to LaTeX format and this way ``The CentOS +Artwork Repository Manual'' started to take form. + +@subheading 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 created to organize automation of most +frequent tasks inside the repository. There was no need to have links +all around the repository if a command-line interface could be created +(through symbolic links, in the @file{~/bin} directory) and be called +anywhere inside the repository as it would be a regular command. + +Inside @command{centos-art.sh}, functionalities started to get +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. + +The @command{centos-art.sh} script was redesigned to handle +command-line options trough @command{getopt} option parser. + +The repository directory structure was updated to improve the +implementation of concepts related to corporate visual identity. +Specially in the area related to themes which were divided into +``design models'' and ``artistic motifs'' to eliminate the content +duplication produced by having both image structure and image visual +style in the same file. Now, themes are produced as result of +arbitrary combinations of both design models (structures) and artistic +motifs (visual styles). + +In the documentation area, the documentation files 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, copied) interactively throuch +@command{centos-art.sh}. Additionally, the @command{texi2html} program +was used to produced XHTML output customized by CSS from The CentOS +Webenv. + +@subheading 2011 + +The @command{centos-art.sh} script was redesigned to start translating +SVG and other XML-based files (e.g., XHTML and Docbook files) through +the @command{xml2po} program and shell scripts files (e.g., Bash +scripts) through GNU @command{gettext} tools. This configuration +provided a stronger interface for graphic designers, translators and +programmers to produce localized content. The SED files are no longer +used to handle translations. + +Improve option parsing through @command{getopt}. + +Consolidate the @code{render}, @code{help} and @code{locale} +functionalities as the most frequent tasks performed inside the +repository. Additionally, the @code{prepare} and @code{tuneup} +functionalities are maintained as useful tasks. + +The @command{centos-art.sh} script is updated to organize +functionalities in two groups: ``the administrative functionalities'' +and ``the productive functionalities''. The administrative +functionalities cover actions like: copying, deleting and renaming +directory structures inside the repository. Also, preparing your +workstation for using @command{centos-art.sh} script, making +backups of the distribution theme currently installed, installing +themes created inside repository and restoring themes from backup. On +the other hand, the productive functionalities cover actions like: +content rendition, content localization, content documentation and +content maintainance. diff --git a/Manuals/Repository/en_US/Introduction/repo-convenctions.texinfo b/Manuals/Repository/en_US/Introduction/repo-convenctions.texinfo new file mode 100644 index 0000000..48b2fae --- /dev/null +++ b/Manuals/Repository/en_US/Introduction/repo-convenctions.texinfo @@ -0,0 +1,537 @@ +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 @emph{source repository} and many +@emph{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 works 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. + +@subsection Repository policy +@cindex Repository 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 @email{centos-devel@@centos.org} mailing +list. 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 +@emph{good community citizen}. + +As a good community citizen one understand of a person who respects +the work already done for 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 +everything goes the way it needs to go in order for the CentOS Artwork +Repository to comply its mission which is: to provide a colaborative +tool for The CentOS Community where The CentOS Project Corporate +Identity is built and maintained from The CentOS Community itself. + +It is also important to remember that all source files inside CentOS +Artwork Repository should comply the terms of GNU General Public +License (@pxref{GNU General Public License}) in order for them to +remain inside the repository. + +@subsection Repository organization +@cindex Repository organization + +The CentOS Artwork Repository uses a @file{trunk}, @file{branches}, +and @file{tags} organization. + +@table @file +@item trunk + +The @file{trunk} directory organizes the main development line of +CentOS Artwork Repository. @xref{Directories trunk}, for more +information. + +@item branches + +The @file{branches} directory oranizes intermediate development lines +taken from the main development line. @xref{Directories branches}, +for more information. + +@item tags + +The @file{tags} directory organizes frozen development lines taken +either from the main or the intermediate lines of development. +@xref{Directories tags}, for more information. +@end table + +@subsection Repository file names +@cindex Repository file names + +Inside the CentOS Artwork Repository, file names are all written in +lowercase (e.g., @samp{01-welcome.png}, @samp{splash.png}, +@samp{anaconda_header.png}, etc.) and directory names are all written +capitalized (e.g., @samp{Identity}, @samp{Themes}, @samp{Motifs}, +@samp{TreeFlower}, etc.). + +@subsection Repository work lines + +Inside CentOS Artwork Repository there are four major work lines of +production which are: @emph{graphic design}, @emph{documentation}, +@emph{localization} and @emph{automation}. These work lines describe +different areas of content production. Content production inside these +specific areas may vary as much as persons be working on them. +Producing content in too many different ways may result innapropriate +in a collaborative environment like CentOS Artwork Repository where +content produced in one area depends somehow from content produced in +another different area. So, a @emph{content production standard} is +required for each available work line. + +@subsubsection Graphic design +@cindex Graphic design work line + +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. + +Inside CentOS Artwork Repository graphic design is performed through +Inkscape (@url{http://www.inkscape.org/}) and GIMP +(@url{http://www.gimp.org/}). The Inkscape tool is used to create and +manipulate scalable vector graphics and export them to PNG format; it +also provides a command-line interface that we use to perform massive +exportation from SVG files to PNG files in automation scripts. On the +other hand, GIMP is used to create and manipulate rastered images, +create brushes, patterns and palettes of colors. + +@quotation +@strong{Tip} Combine both Inkscape and GIMP specific functionalities +and possibilities to produce very beautiful images. +@end quotation + +The CentOS Project Corporate Visual Identity is made of different +visual manifestations (e.g., Distributions, Web sites, Stationery, +etc.). Visual manifestations implement the corporate identity +concepts by mean of images. To produce these images, we decompose +image production in @emph{design models} and @emph{artistic motifs}. + +Design models provide the structural information of images (i.e., +dimension, position of common elements in the visible area, +translation markers, etc.) and they are generally produced as scalable +vector graphics to take advantage of SVG standard, an XML-based +standard. + +Artistic motifs provide the visual style (i.e., the background +information, the look and feel) some design models need to complete +the final image produced by automation scripts. Artistic motifs are +generally produced as rastered images. + +The result produced from combining one design model with one artistic +motif is what we know as a @emph{theme}. Inside themes directory +structure (@pxref{Directories trunk Identity Images Themes}), you can find +several design models and several artistic motifs independently one +another that can be albitrarily combined through @emph{theme +rendition}, a flexible way to produce images for different visual +manifestations in very specific visual styles. Inside themes directory +structure, theme rendition is performed in +@file{trunk/Identity/Images/Themes} directory structure, the required +design models are taken from @file{trunk/Identity/Models/Themes} +directory structure and the action itself is controlled by the +@code{render} functionality of @command{centos-art.sh} script. + +In addition to theme rendition you can find @emph{direct rendition}, +too. Direct rendition is another way of image production where there +is no artistic motif at all but design models only. Direct rendition +is very useful to produce simple content that doesn't need specific +background information. Some of these contents are brands, icons and +illustrations. Direct rendition is performed in +@file{trunk/Identity/Images}, the required design models are taken +from @file{trunk/Identity/Models} directory structure and the action +itself is controlled by the @code{render} functionality of +@command{centos-art.sh} script. + +@xref{Directories trunk Identity}, for more information about The +CentOS Corporate Identity and how graphic design fits on it. + +@subsubsection Documentation +@cindex Documentation work line + +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 CentOS Artwork Repository documentation is supported by Texinfo, a +documentation system that uses a single source file to produce both +online information and printed output. + +The repository documentation is organized under @file{trunk/Manual} +directory and uses the repository directory structre as reference. +Each directory in the repository has a documentation entry associated +in the documentation manual. Documentation entries are stored under +@file{trunk/Manual/Directories} directory and the action itself is +controlled by the @code{help} functionality of @command{centos-art.sh} +script. + +The @code{help} functionality let you create, edit and delete +documentation entries in a way that you don't need to take care of +updating menus, nodes and cross reference information inside the +manual structure; the functionality takes care of it for you. +However, if you need to write repository documentation that have +nothing to do with repository directories (e.g., Preface, Introduction +and similar) you need to do it manually, there is no functionality to +automate such process yet. + +@xref{Directories trunk Manuals}, for more information on +documentation. + +@subsubsection Localization +@cindex Localization work line + +The localization work line exists to provide the translation messages +required to produce content in different languages. Translation +messages inside the repository are stored as portable objects (e.g., +.po, .pot) and machine objects (.mo) under @file{trunk/Locales} +directory structure. + +The procedure used to localize content is taken from @command{gettext} +standard specification. Basically, translatable strings are retrived +from source files in order to create portable objects and machine +objects for them. These portable objects are editable files that +contain the information used by translators to localize the +translatable strings retrived from source files. On the other hand, +machine objects are produced to be machine-redable only, as its name +implies, and are produced from portable objects. + +Since @command{gettext} needs to extract translatable strings form +source files in order to let translators to localize them, we are +limitted to use source files supported by @command{gettext} program. +This is not a limitation at all since @command{gettext} supports most +popular programming laguages (e.g., C, C++, Java, Bash, Python, Perl, +PHP and GNU Awk just to mention a few ones). Nevertheless, formats +like SVG, XHTML and Docbook don't figure as supported formats in the +list of @command{gettext} supported source files. + +To translate XML based source files like SVG, XHTML and Docbook we use +the @command{xml2po} program instead. The @command{xml2po} comes with +the @file{gnome-doc-utils} package and retrives translatable strings +from one XML file to produce portable objects for them. + +@quotation +@strong{Note} +Portable objects produced by @command{xml2po} have the same format +that portable objects produced by @command{gettext}. This make the +localization process quite consistent from translators' point of view. +No matter what the source file be, the translator will always face the +same translation file format (i.e., the portable object format). +@end quotation + +With the portable object in place, the @command{xml2po} program is +used again to create the final translated XML, just with the same +definition of the source file where translatable strings were taken +from (e.g., if we extract translatable strings from a SVG file, as +result we get the same SVG file but with translatable strings already +localized ---obviously, for this to happen translators need to +localize translatable strings inside the portable object first, +localization won't appear as art of magic---). When using +@command{xml2po}, the machine object is used as temporal file to +produce the final translated XML file. + +@quotation +@strong{Tip} If you want to have your content localized inside CentOS +Artwork Repository be sure to use source files supported either by +@command{gettext} or @command{xml2po} programs. +@end quotation + +@xref{Directories trunk Locales}, for more information. + +@subsubsection Automation +@cindex Automation work line + +The automation work line exists to standardize content production in +CentOS Artwork Repository. There is no need to type several tasks, +time after time, if they can be programmed into just one executable +script. + +The automation work line takes place under @file{trunk/Scripts} +directory structure. Here is developed the @command{centos-art.sh} +script, a bash script specially designed to automate most frequent +tasks (e.g., rendition, documentation and localization) inside the +repository. Basically, the @command{centos-art.sh} script is divided +in several functionalities independent one another that perform +specific tasks and relay on repository organization to work as +expected. + +@quotation +@strong{Tip} If you need to improve the way content is produced, look +inside automation scripts and make your improvement there for everyone +to benefit. +@end quotation + +@xref{Directories trunk Scripts}, for more information on automation. + +@subsection Connection between directories +@cindex Connection between directories +@cindex Master paths +@cindex Auxiliar paths + +In order to produce content in CentOS Artwork Repository, it is +required that all work lines be connected somehow. This is the way +automation scripts can know where to retrive the information they need +to work with (e.g., design model, translation messages, output +location, etc.). We build this kind of connection using two path +constructions named @emph{master paths} and @emph{auxiliar paths}. + +The master path points only to directories that contain the source +files (e.g., SVG files) required to produce 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. + +The 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 to store the content produced from master path. +When an auxiliar path points to a file, that file has no other purpose +but to document the master path it refers to. + +The relation between auxiliar paths and master paths is realized +combining two path informations which are: the master path itself and +one second level directory structure from the repository. Generally, +the master path is considered the path identifier and the second level +directory structure taken from the repository is considered the common +part of the path where the identifier is appended. + +@float Figure, Path construction +@verbatim +-----+---------------+----------------------------+------+----------- +Path | Suffix | Identifier |Prefix| Type +-----+---------------+----------------------------+------+----------- + A | |trunk/Identity/Models/Brands| | Directory +-----+---------------+----------------------------+------+----------- + B | trunk/Manual/|trunk/Identity/Models/Brands|.texinfo | File +-----+---------------+----------------------------+------+----------- + C | trunk/Locales/|trunk/Identity/Models/Brands| | Directory +-----+---------------+----------------------------+------+----------- + D | |trunk/Identity/Images/Brands| | Directory +-----+---------------+----------------------------+------+----------- + E | trunk/Locales/|trunk/Identity/Images/Brands|.texinfo | File +-----+---------------+----------------------------+------+----------- + + A = Master path. + B = Auxiliar path to documentation entry. + C = Auxiliar path to translation messages. + D = Auxiliar path to final content output. + E = Auxiliar path to documentation entry. +@end verbatim +@caption{Path construction.} +@end float + +The path information described above (@pxref{Path construction}) is +used by direct rendition and can be taken as reference to add other +components that are equally produced in the repository. To add new +components that make use of direct rendition inside the repository, +change just the component name used above (e.g., @file{Brands}) to +that one you want to add, without changing the path structure around +it. + +The file organization used by theme rendition extends direct rendition +by separating design models information from backgrounds information. +To better understand this configuration, you can consider it as two +independent lists, one of design models and one of artistic motifs, +which are arbitrary combined between themselves in order to render +images in specific ways. The possibilities of this configuration are +endless and let us describe visual manifestations very well. For +example, consider the organization used to produce @file{Anaconda} +images; for CentOS distribution major release 5; using @file{Default} +design models and version @file{3} of @file{Flame} artistic motif: + +@float Figure, Path construction extended +@verbatim +-----+---------------+------------------------------------------------------+------+----------- +Path | Suffix | Identifier |Prefix| Type +-----+---------------+------------------------------------------------------+------+----------- + A | |trunk/Identity/Models/Themes/Default/Distro/5/Anaconda| | Directory +-----+---------------+------------------------------------------------------+------+----------- + B | trunk/Manual/|trunk/Identity/Models/Themes/Default/Distro/5/Anaconda|.texinfo | File +-----+---------------+------------------------------------------------------+------+----------- + C | trunk/Locales/|trunk/Identity/Models/Themes/Default/Distro/5/Anaconda| | Directory +-----+---------------+------------------------------------------------------+------+----------- + D | |trunk/Identity/Images/Themes/Flame/3/Distro/5/Anaconda| | Directory +-----+---------------+------------------------------------------------------+------+----------- + E | trunk/Locales/|trunk/Identity/Images/Themes/Flame/3/Distro/5/Anaconda|.texinfo | File +-----+---------------+------------------------------------------------------+------+----------- + + A = Master path. + B = Auxiliar path to documentation entry. + C = Auxiliar path to translation messages. + D = Auxiliar path to final content output. + E = Auxiliar path to documentation entry. +@end verbatim +@caption{Path construction extended.} +@end float + +The path information described above (@pxref{Path construction +extended}) is used by theme rendition and can be taken as reference to +add other components that are equally produced in the repository. + +In this configuration we can change both design model name (e.g., +@file{Default}) and artistic motif name (e.g., @file{Flame/3}) to +something else in order to achieve a different result. The only +limitations impossed are the storage space provided in the server +machine and your own creativeness as graphic designer. + +@quotation +@strong{Note} +A theme ready for implementation may consume from 100 MB to 400 MB of +storage space. The exact space consumed by a theme depends on the +amount of screen resolutions the theme supports. The more screen +resolutions the theme supports, the more storage space demanded for +it. +@end quotation + +In this configuration we saw how to build the path information for +@file{Anaconda} component as part of CentOS Distribution visual +manifestation, but that is not the only component we have inside +CentOS Distribution visual manifestation. There are other components +like Syslinux, Grub, Rhgb, Gdm, Kdm, Gsplash and Ksplash that share a +similar file organization to that described above for @file{Anaconda} +component. + +@subsection Syncronizing path information +@cindex Syncronizing path information + +Syncronizing path information is the action that keeps all path +information up to date in the repository. This action implies both +@emph{file movement} and @emph{file content replacement} in this very +specific order. File movement is related to duplicate, delete and +rename files and directories in the repository. File content +replacement is related to replace information, path information in +this case, inside files in the repository. + +The order followed to syncronize path information is relevant because +the versioned nature of the files we are working with. We don't +perform file content replacement first because that would imply a +repository change which will immediatly demmand a commit in order for +actions like duplicate, delete or rename to take place. However, if we +perform file movement first, it is possible to commit both file moved +and file content replacements as if they were just one change. In this +case the file content replacement takes palce in the target location +that have been duplicated or renamed, not the one use as source +location. This configuration is specially useful when files are +renamed (i.e., one file is copied from a source location to a target +location and then the source location of it is removed from +repository). + +@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 + +When one master path is 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 way, +automation scripts are able to know where to retrive translation +messages from, where to store final output images to and where to look +for documentation. If relation between master paths and auxiliar paths +is lost, there is no way for automation scripts to know where to +retrive the information they need. + +The 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 update direction to rename path information must be from +master path to auxiliar path and never the opposite. + +The relation between master and auxiliar paths is useful to keep +repository organized but introduce some complications when we work +with files that use master path information as reference to build +structural information. This is the case of repository documentation +manual source files where inclusions, menus, nodes and cross +references are built using master path information as reference. Now, +to see what kind of complication we are talking about, consider what +would happen to a structural definitions (i.e., inlusions, menus, +nodes and cross refereces) already set in the manual from one master +path that is suddenly renamed to something different. If the path +information is not syncronized, at this point, we lose connection +between the master path and the auxiliar path created to store the +related documentation entry, as well as the related structural +definitions that end up pointing to a master path that no longer +exist. + +The syncronization of path information is aimed to solve these kind of +issues. + +@subsection Extending repository organization +@cindex Extending repository organization + +Occasionly, you may find that new components of The CentOS Project +Corporate 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: +@emph{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/GettingHelp}), 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 Identity Structure (@pxref{Directories +trunk Identity}) The CentOS Mission and The CentOS Release Schema. The +rest is just 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, you need to define the conceptual idea +first and later create the directory. There are some locations inside +the repository that already define some concepts you probably want to +reuse. For example, @file{trunk/Identity/Images/Themes} to store theme +artistic motifs, @file{trunk/Identity/Models/Themes} to store theme +design models, @file{trunk/Manual} to store documentation files, +@file{trunk/Locales} to store translation messages, +@file{trunk/Scripts} to store automation scripts and so on. + +To illustrate this desition process let's consider the +@file{trunk/Identity/Images/Themes/TreeFlower/3} directory structure +as example. This directory can be read as: the theme development line +of version @file{3} of @file{TreeFlower} artistic motif. Additional, +we can identify that artistic motifs are part of themes as well as +themes are part of The CentOS Project Corporate Identity. These +concepts are better described independently in each documentation +entry related to the directory structure as it is respectively shown +in the list of commands bellow. + +@verbatim +centos-art help --read turnk +centos-art help --read turnk/Identity +centos-art help --read turnk/Identity/Themes +centos-art help --read turnk/Identity/Images/Themes +centos-art help --read turnk/Identity/Images/Themes/TreeFlower +centos-art help --read turnk/Identity/Images/Themes/TreeFlower/3 +@end verbatim + +The concepts behind other location can be found in the same way +described above, just change the path information used above to the +one you are trying to know concepts for. diff --git a/Manuals/Repository/en_US/Licenses/chapter-menu.texinfo b/Manuals/Repository/en_US/Licenses/chapter-menu.texinfo new file mode 100755 index 0000000..b8240ba --- /dev/null +++ b/Manuals/Repository/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/Repository/en_US/Licenses/chapter-nodes.texinfo b/Manuals/Repository/en_US/Licenses/chapter-nodes.texinfo new file mode 100755 index 0000000..2d3afa7 --- /dev/null +++ b/Manuals/Repository/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/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/Templates/en_US/Licenses/GFDL.texinfo diff --git a/Manuals/Repository/en_US/Licenses/chapter.texinfo b/Manuals/Repository/en_US/Licenses/chapter.texinfo new file mode 100755 index 0000000..27e70ae --- /dev/null +++ b/Manuals/Repository/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/Repository/en_US/repository-index.texinfo b/Manuals/Repository/en_US/repository-index.texinfo new file mode 100644 index 0000000..abe002c --- /dev/null +++ b/Manuals/Repository/en_US/repository-index.texinfo @@ -0,0 +1,3 @@ +@node Index +@unnumbered Index +@printindex cp diff --git a/Manuals/Repository/en_US/repository-menu.texinfo b/Manuals/Repository/en_US/repository-menu.texinfo new file mode 100644 index 0000000..89f2a86 --- /dev/null +++ b/Manuals/Repository/en_US/repository-menu.texinfo @@ -0,0 +1,6 @@ +@menu +* Introduction:: +* Directories:: +* Licenses:: +* Index:: +@end menu diff --git a/Manuals/Repository/en_US/repository-nodes.texinfo b/Manuals/Repository/en_US/repository-nodes.texinfo new file mode 100644 index 0000000..722d48f --- /dev/null +++ b/Manuals/Repository/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/Repository/en_US/repository.texinfo b/Manuals/Repository/en_US/repository.texinfo new file mode 100644 index 0000000..12a4203 --- /dev/null +++ b/Manuals/Repository/en_US/repository.texinfo @@ -0,0 +1,54 @@ +\input texinfo @c -*-texinfo-*- +@c $Id$ +@setfilename repository.info +@settitle CentOS Artwork Repository Reference +@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 CentOS Artwork Repository +@subtitle Reference +@author Alain Reguera Delgado +@page +@vskip 0pt plus 1filll +@insertcopying +@end titlepage + +@contents + +@c -- `Top' Node and Master Menu ------------------------------- + +@ifnottex +@node Top +@top CentOS Artwork Repository Reference +@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/Repository/es_ES/Directories/branches.texinfo b/Manuals/Repository/es_ES/Directories/branches.texinfo new file mode 100644 index 0000000..47252e0 --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/Directories/chapter-menu.texinfo b/Manuals/Repository/es_ES/Directories/chapter-menu.texinfo new file mode 100644 index 0000000..2cd6d67 --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/Directories/chapter-nodes.texinfo b/Manuals/Repository/es_ES/Directories/chapter-nodes.texinfo new file mode 100644 index 0000000..b45c868 --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/Directories/chapter.texinfo b/Manuals/Repository/es_ES/Directories/chapter.texinfo new file mode 100644 index 0000000..a3cb4f1 --- /dev/null +++ b/Manuals/Repository/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 los directorios para organizar +ficheros y describir ideas conceptuales relacionadas a la identidad +corporativa. Tales ideas conceptuales están explicadas en cada una de +las entradas de documentation asociadas a los directorios del repository. + +En este capítulo usted aprenderá cuales son los directorios del +repository, para qué son y cómo pude utilizarlos. De esta forma, +seleccione uno de los directorios siguientes para conocer más sobre +ellos: + +@include Directories/chapter-menu.texinfo +@include Directories/chapter-nodes.texinfo diff --git a/Manuals/Repository/es_ES/Directories/tags.texinfo b/Manuals/Repository/es_ES/Directories/tags.texinfo new file mode 100644 index 0000000..878663f --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/Directories/trunk.texinfo b/Manuals/Repository/es_ES/Directories/trunk.texinfo new file mode 100644 index 0000000..f24ee02 --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/Directories/trunk/Identity.texinfo b/Manuals/Repository/es_ES/Directories/trunk/Identity.texinfo new file mode 100644 index 0000000..f62b838 --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/Directories/trunk/Scripts.texinfo b/Manuals/Repository/es_ES/Directories/trunk/Scripts.texinfo new file mode 100644 index 0000000..a082d19 --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/Directories/trunk/Scripts/Functions.texinfo b/Manuals/Repository/es_ES/Directories/trunk/Scripts/Functions.texinfo new file mode 100644 index 0000000..ba9b35c --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/Directories/trunk/Scripts/Functions/Help.texinfo b/Manuals/Repository/es_ES/Directories/trunk/Scripts/Functions/Help.texinfo new file mode 100644 index 0000000..bf45a23 --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/Directories/trunk/Scripts/Functions/Help/Backends.texinfo b/Manuals/Repository/es_ES/Directories/trunk/Scripts/Functions/Help/Backends.texinfo new file mode 100644 index 0000000..1327702 --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/Licenses/chapter-menu.texinfo b/Manuals/Repository/es_ES/Licenses/chapter-menu.texinfo new file mode 100755 index 0000000..b8240ba --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/Licenses/chapter-nodes.texinfo b/Manuals/Repository/es_ES/Licenses/chapter-nodes.texinfo new file mode 100755 index 0000000..f7497c1 --- /dev/null +++ b/Manuals/Repository/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/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/Templates/es_ES/Licenses/GFDL.texinfo diff --git a/Manuals/Repository/es_ES/Licenses/chapter.texinfo b/Manuals/Repository/es_ES/Licenses/chapter.texinfo new file mode 100755 index 0000000..38edb4b --- /dev/null +++ b/Manuals/Repository/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/Repository/es_ES/repository-index.texinfo b/Manuals/Repository/es_ES/repository-index.texinfo new file mode 100755 index 0000000..d168d12 --- /dev/null +++ b/Manuals/Repository/es_ES/repository-index.texinfo @@ -0,0 +1,3 @@ +@node Index +@unnumbered Índice +@printindex cp diff --git a/Manuals/Repository/es_ES/repository-menu.texinfo b/Manuals/Repository/es_ES/repository-menu.texinfo new file mode 100644 index 0000000..a7cb577 --- /dev/null +++ b/Manuals/Repository/es_ES/repository-menu.texinfo @@ -0,0 +1,5 @@ +@menu +* Directories:: +* Licenses:: +* Index:: +@end menu diff --git a/Manuals/Repository/es_ES/repository-nodes.texinfo b/Manuals/Repository/es_ES/repository-nodes.texinfo new file mode 100644 index 0000000..3bf2339 --- /dev/null +++ b/Manuals/Repository/es_ES/repository-nodes.texinfo @@ -0,0 +1,2 @@ +@include Directories/chapter.texinfo +@include Licenses/chapter.texinfo diff --git a/Manuals/Repository/es_ES/repository.texinfo b/Manuals/Repository/es_ES/repository.texinfo new file mode 100644 index 0000000..e403531 --- /dev/null +++ b/Manuals/Repository/es_ES/repository.texinfo @@ -0,0 +1,58 @@ +\input texinfo @c -*-texinfo-*- +@c $Id$ +@c -- Header -------------------------------------------------- + +@setfilename repository.info +@settitle Referencia del 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 Repositorio Artístico de CentOS +@subtitle Referencia +@author The CentOS Project +@page +@vskip 0pt plus 1filll +@insertcopying +@end titlepage +@contents + +@c -- `Top' node and master menu ------------------------------- + +@ifnottex +@node Top +@top Referencia del 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/Repository/repository-init.pl b/Manuals/Repository/repository-init.pl new file mode 100755 index 0000000..468ae73 --- /dev/null +++ b/Manuals/Repository/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 "