diff --git a/Manuals/Common_content/Entities.ent b/Manuals/Common_content/Entities.ent new file mode 100644 index 0000000..e42c505 --- /dev/null +++ b/Manuals/Common_content/Entities.ent @@ -0,0 +1,52 @@ + + + + + + + + + + + + + + +&TC; Project"> + + + +&TC; Mirrors"> + + + + + + + +&TCA; Repository"> +&TCA; SIG"> + +The CentOS Artwork Repository User's Guide"> + +centos-artwork@centos.org mailing list"> +centos-devel@centos.org mailing list"> +centos-info@centos.org mailing list"> + +&TC; Wiki"> +&TC; Mailing Lists"> + + + +"> +"> +"> +"> + +&TC; Documentation"> diff --git a/Manuals/Common_content/Licenses.docbook b/Manuals/Common_content/Licenses.docbook new file mode 100644 index 0000000..dfc86ce --- /dev/null +++ b/Manuals/Common_content/Licenses.docbook @@ -0,0 +1,6 @@ + + Licenses + &licenses-gpl; + &licenses-gfdl; + + diff --git a/Manuals/Common_content/Licenses.ent b/Manuals/Common_content/Licenses.ent new file mode 100644 index 0000000..29e0b56 --- /dev/null +++ b/Manuals/Common_content/Licenses.ent @@ -0,0 +1,3 @@ + + + diff --git a/Manuals/Common_content/Licenses/gfdl.docbook b/Manuals/Common_content/Licenses/gfdl.docbook new file mode 100644 index 0000000..a8fef02 --- /dev/null +++ b/Manuals/Common_content/Licenses/gfdl.docbook @@ -0,0 +1,605 @@ + + + GNU Free Documentation License + + Version 1.2, November 2002 + + Copyright © 2000, 2001, 2002 Free Software Foundation, + Inc. 675 Mass Ave, Cambridge, MA 02139, USA + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + + + Preamble + + The purpose of this License is to make a manual, + textbook, or other functional and useful document + free in 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. + + This License is a kind of copyleft, which + means that derivative works of the document must themselves be + free in the same sense. It complements the , which is a copyleft license + designed for free software. + + We have designed this License in order to use it for + manuals for free software, because free software needs free + documentation: a free program should come with manuals + providing the same freedoms that the software does. But this + License is not limited to software manuals; it can be used for + any textual work, regardless of subject matter or whether it + is published as a printed book. We recommend this License + principally for works whose purpose is instruction or + reference. + + + + + + Applicability and definitions + + This License applies to any manual or other work, in any + medium, that contains a notice placed by the copyright holder + saying it can be distributed under the terms of this License. + Such a notice grants a world-wide, royalty-free license, + unlimited in duration, to use that work under the conditions + stated herein. 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. + + A + Modified Version of 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. + + A + Secondary Section is 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 may not explain any mathematics.) The relationship could be + a matter of historical connection with the subject or with + related matters, or of legal, commercial, philosophical, + ethical or political position regarding them. + + The Invariant Sections are certain + whose titles are + designated, as being those of Invariant Sections, in the + notice that says that the Document is released under this + License. If a section does not fit the above definition of + Secondary then it is not allowed to be designated as + Invariant. The Document may contain zero Invariant Sections. + If the Document does not identify any Invariant Section then + there are none. + + The + Cover Texts are 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. + + A + Transparent copy 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 file format whose + markup, or absence of markup, has been arranged to thwart or + discourage subsequent modification by readers is not . An image format is not if used for any substantial amount of + text. A copy that is not is called Opaque. + + Examples of suitable formats for copies + include plain ASCII without markup, Texinfo input format, + LaTeX input format, SGML or XML using a publicly available + DTD, and standard-conforming simple HTML, PostScript or PDF + designed for human modification. Examples of transparent + image formats include PNG, XCF and JPG. Opaque formats + include proprietary formats that can be read and edited only + by proprietary word processors, SGML or XML for which the DTD + and/or processing tools are not generally available, and the + machine-generated HTML, PostScript or PDF produced by some + word processors for output purposes only. + + The Title + Page means, 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 Page means the text near the most + prominent appearance of the work's title, preceding the + beginning of the body of the text. + + A section Entitled XYZ means 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 XYZ according to + this definition. + + The Document may include Warranty Disclaimers next to + the notice which states that this License applies to the + Document. These Warranty Disclaimers are considered to be + included by reference in this License, but only as regards + disclaiming warranties: any other implication that these + Warranty Disclaimers may have is void and has no effect on the + meaning of this License. + + + + + + Verbatim copying + + You may copy and distribute the Document in any medium, + either commercially or noncommercially, provided that this + License, the copyright notices, and the license notice saying + this License applies to the Document are reproduced in all + copies, and that you add no other conditions whatsoever to + those of this License. You may not use technical measures to + obstruct or control the reading or further copying of the + copies you make or distribute. However, you may accept + compensation in exchange for copies. If you distribute a + large enough number of copies you must also follow the + conditions in section . + + You may also lend copies, under the same conditions + stated above, and you may publicly display copies. + + + + + + Copying in quantity + + If you publish printed copies (or copies in media that + commonly have printed covers) of the Document, numbering more + than 100, and the Document's license notice requires Cover + Texts, you must enclose the copies in covers that carry, + clearly and legibly, all these : + Front-Cover Texts on the front cover, and Back-Cover Texts on + the back cover. Both covers must also clearly and legibly + identify you as the publisher of these copies. The front + cover must present the full title with all words of the title + equally prominent and visible. You may add other material on + the covers in addition. Copying with changes limited to the + covers, as long as they preserve the title of the Document and + satisfy these conditions, can be treated as verbatim copying + in other respects. + + If the required texts for either cover are too + voluminous to fit legibly, you should put the first ones + listed (as many as fit reasonably) on the actual cover, and + continue the rest onto adjacent pages. + + If you publish or distribute Opaque copies of the + Document numbering more than 100, you must either include a + machine-readable copy along with each Opaque copy, + or state in or with each Opaque copy a computer-network + location from which the general network-using public has + access to download using public-standard network protocols a + complete copy of the Document, free of added + material. If you use the latter option, you must take + reasonably prudent steps, when you begin distribution of + Opaque copies in quantity, to ensure that this + copy will remain thus accessible at the stated location until + at least one year after the last time you distribute an Opaque + copy (directly or through your agents or retailers) of that + edition to the public. + + It is requested, but not required, that you contact the + authors of the Document well before redistributing any large + number of copies, to give them a chance to provide you with an + updated version of the Document. + + + + + + Modifications + + + You may copy and distribute a of the Document under the + conditions of sections and above, provided that + you release the under + precisely this License, with the filling the role of the + Document, thus licensing distribution and modification of + the to whoever + possesses a copy of it. In addition, you must do these + things in the : + + + + + + Use in the (and on + the covers, if any) a title distinct from that of the + Document, and from those of previous versions (which + should, if there were any, be listed in the History + section of the Document). You may use the same title + as a previous version if the original publisher of + that version gives permission. + + + List on the , as + authors, one or more persons or entities responsible + for authorship of the modifications in the , together with at least + five of the principal authors of the Document (all of + its principal authors, if it has fewer than five), + unless they release you from this requirement. + + + + State on the the + name of the publisher of the , as the + publisher. + + + + Preserve all the copyright notices of the + Document. + + + + Add an appropriate copyright notice for your + modifications adjacent to the other copyright + notices. + + + + Include, immediately after the copyright + notices, a license notice giving the public permission + to use the under the terms of this + License, in the form shown in the Addendum + below. + + + + Preserve in that license notice the full lists + of and required + given in the Document's + license notice. + + + + Include an unaltered copy of this License. + + + + Preserve the section Entitled + History, Preserve its Title, and add to + it an item stating at least the title, year, new + authors, and publisher of the as given on the . If there is no section + Entitled History in the Document, create + one stating the title, year, authors, and publisher of + the Document as given on its , then add an item describing the as stated in the previous + sentence. + + + + Preserve the network location, if any, given in + the Document for public access to a copy of the Document, and + likewise the network locations given in the Document + for previous versions it was based on. These may be + placed in the History section. 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. + + + + For any section Entitled + Acknowledgements or + 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. + + + + Preserve all the of the Document, + unaltered in their text and in their titles. Section + numbers or the equivalent are not considered part of + the section titles. + + + + Delete any section Entitled + Endorsements. Such a section may not + be included in the . + + + + Do not retitle any existing section to be + Entitled Endorsements or to conflict in + title with any . + + + Preserve any Warranty Disclaimers. + + + + + If the includes new + front-matter sections or appendices that qualify as and contain no material + copied from the Document, you may at your option designate + some or all of these sections as invariant. To do this, + add their titles to the list of in the 's license notice. These + titles must be distinct from any other section + titles. + + + + You may add a section Entitled + Endorsements, provided it contains nothing + but endorsements of your by various parties–for example, statements of + peer review or that the text has been approved by an + organization as the authoritative definition of a + standard. + + + + You may add a passage of up to five words as a Front-Cover + Text, and a passage of up to 25 words as a Back-Cover + Text, to the end of the list of in the . Only one passage of + Front-Cover Text and one of Back-Cover Text may be added + by (or through arrangements made by) any one entity. If + the Document already includes a cover text for the same + cover, previously added by you or by arrangement made by + the same entity you are acting on behalf of, you may not + add another; but you may replace the old one, on explicit + permission from the previous publisher that added the old + one. + + + + The author(s) and publisher(s) of the Document do not by + this License give permission to use their names for + publicity for or to assert or imply endorsement of any + . + + + + + + + Combining documents + + You may combine the Document with other documents + released under this License, under the terms defined in + section above for + modified versions, provided that you include in the + combination all of the of + all of the original documents, unmodified, and list them all + as of your combined work + in its license notice, and that you preserve all their + Warranty Disclaimers. + + The combined work need only contain one copy of this + License, and multiple identical may be replaced with a single + copy. If there are multiple with the same name but + different contents, make the title of each such section unique + by adding at the end of it, in parentheses, the name of the + original author or publisher of that section if known, or else + a unique number. Make the same adjustment to the section + titles in the list of in + the license notice of the combined work. + + In the combination, you must combine any sections + Entitled History in 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. + + + + + + Collection of documents + + You may make a collection consisting of the Document and + other documents released under this License, and replace the + individual copies of this License in the various documents + with a single copy that is included in the collection, + provided that you follow the rules of this License for + verbatim copying of each of the documents in all other + respects. + + You may extract a single document from such a + collection, and distribute it individually under this License, + provided you insert a copy of this License into the extracted + document, and follow this License in all other respects + regarding verbatim copying of that document. + + + + + + Aggregation with independent works + + A compilation of the Document or its derivatives with + other separate and independent documents or works, in or on a + volume of a storage or distribution medium, is called an + aggregate if 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. + + If the Cover Text requirement of section is applicable to these + copies of the Document, then if the Document is less than one + half of the entire aggregate, the Document's may be placed on covers that bracket + the Document within the aggregate, or the electronic + equivalent of covers if the Document is in electronic form. + Otherwise they must appear on printed covers that bracket the + whole aggregate. + + + + + + Translations + + Translation is considered a kind of modification, so you + may distribute translations of the Document under the terms of + section . Replacing + with translations + requires special permission from their copyright holders, but + you may include translations of some or all in addition to the original + versions of these . You + may include a translation of this License, and all the license + notices in the Document, and any Warranty Disclaimers, + provided that you also include the original English version of + this License and the original versions of those notices and + disclaimers. In case of a disagreement between the + translation and the original version of this License or a + notice or disclaimer, the original version will + prevail. + + If a section in the Document is Entitled + Acknowledgements, Dedications, + or History, the requirement (section ) to Preserve its Title + (section ) will + typically require changing the actual title. + + + + + + Termination + + You may not copy, modify, sublicense, or distribute the + Document except as expressly provided for under this License. + Any other attempt to copy, modify, sublicense or distribute + the Document is void, and will automatically terminate your + rights under this License. However, parties who have received + copies, or rights, from you under this License will not have + their licenses terminated so long as such parties remain in + full compliance. + + + + + + Future Revisions of this License + + The Free Software Foundation may publish new, revised + versions of the GNU Free Documentation License from time to + time. Such new versions will be similar in spirit to the + present version, but may differ in detail to address new + problems or concerns. See . + + Each version of the License is given a distinguishing + version number. If the Document specifies that a particular + numbered version of this License or any later + version applies 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. + + + + + + How to use this License for your documents + + To use this License in a document you have written, + include a copy of the License in the document and put the + following copyright and license notices just after the title + page: + + +Copyright (C) YEAR YOUR NAME. + +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 GNU Free Documentation License. + + + If you have , + Front-Cover Texts and Back-Cover Texts, replace the + with...Texts. line with this: + + +with the Invariant Sections being LIST THEIR TITLES, with the +Front-Cover Texts being LIST, and with the Back-Cover Texts being +LIST. + + + If you have + without , or some other + combination of the three, merge those two alternatives to suit + the situation. + + If your document contains nontrivial examples of program + code, we recommend releasing these examples in parallel under + your choice of free software license, such as the GNU General + Public License, to permit their use in free software. + + + + diff --git a/Manuals/Common_content/Licenses/gpl.docbook b/Manuals/Common_content/Licenses/gpl.docbook new file mode 100644 index 0000000..fe1c604 --- /dev/null +++ b/Manuals/Common_content/Licenses/gpl.docbook @@ -0,0 +1,537 @@ + + + GNU General Public License + + + Version 2, June 1991 + + + + Copyright © 1989, 1991 Free Software Foundation, Inc. + 675 Mass Ave, Cambridge, MA 02139, USA + + + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not + allowed. + + + + + Preamble + + + The licenses for most software are designed to take away your + freedom to share and change it. By contrast, the GNU General + Public License is intended to guarantee your freedom to share + and change free software–to make sure the software is + free for all its users. This General Public License applies + to most of the Free Software Foundation's software and to any + other program whose authors commit to using it. (Some other + Free Software Foundation software is covered by the GNU + Library General Public License instead.) You can apply it to + your programs, too. + + + + When we speak of free software, we are referring to freedom, + not price. Our General Public Licenses are designed to make + sure that you have the freedom to distribute copies of free + software (and charge for this service if you wish), that you + receive source code or can get it if you want it, that you can + change the software or use pieces of it in new free programs; + and that you know you can do these things. + + + + To protect your rights, we need to make restrictions that + forbid anyone to deny you these rights or to ask you to + surrender the rights. These restrictions translate to certain + responsibilities for you if you distribute copies of the + software, or if you modify it. + + + + For example, if you distribute copies of such a program, + whether gratis or for a fee, 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 show them + these terms so they know their rights. + + + + We protect your rights with two steps: + + + + + copyright the software, and + + + offer you this license which gives you legal + permission to copy, distribute and/or modify the + software. + + + + + Also, for each author's protection and ours, we want to make + certain that everyone understands that there is no warranty + for this free software. If the software is modified by + someone else and passed on, we want its recipients to know + that what they have is not the original, so that any problems + introduced by others will not reflect on the original authors' + reputations. + + + + Finally, any free program is threatened constantly by software + patents. We wish to avoid the danger that redistributors of a + free program will individually obtain patent licenses, in + effect making the program proprietary. To prevent this, we + have made it clear that any patent must be licensed for + everyone's free use or not licensed at all. + + + + The precise terms and conditions for copying, distribution and + modification follow. + + + + + + + Terms and Conditions for Copying, Distribution and Modification + + + + Section 1 + + + You may copy and distribute verbatim copies of the Program's + source code as you receive it, in any medium, provided that + you conspicuously and appropriately publish on each copy an + appropriate copyright notice and disclaimer of warranty; keep + intact all the notices that refer to this License and to the + absence of any warranty; and give any other recipients of the + Program a copy of this License along with the Program. + + + + You may charge a fee for the physical act of transferring a + copy, and you may at your option offer warranty protection in + exchange for a fee. + + + + + + + Section 2 + + + You may modify your copy or copies of the Program or any + portion of it, thus forming a work based on the Program, and + copy and distribute such modifications or work under the terms + of above, provided that + you also meet all of these conditions: + + + + + + You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any + change. + + + + + You must cause any work that you distribute or publish, that + in whole or in part contains or is derived from the Program or + any part thereof, to be licensed as a whole at no charge to + all third parties under the terms of this License. + + + + + If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display + an announcement including an appropriate copyright notice and + a notice that there is no warranty (or else, saying that you + provide a warranty) and that users may redistribute the + program under these conditions, and telling the user how to + view a copy of this License. + + + + + + Exception + + If the Program itself is interactive but does not normally + print such an announcement, your work based on the Program is + not required to print an announcement. + + + + + These requirements apply to the modified work as a whole. If + identifiable sections of that work are not derived from the + Program, and can be reasonably considered independent and + separate works in themselves, then this License, and its + terms, do not apply to those sections when you distribute them + as separate works. But when you distribute the same sections + as part of a whole which is a work based on the Program, the + distribution of the whole must be on the terms of this + License, whose permissions for other licensees extend to the + entire whole, and thus to each and every part regardless of + who wrote it. + + + + Thus, it is not the intent of this section to claim rights or + contest your rights to work written entirely by you; rather, + the intent is to exercise the right to control the + distribution of derivative or collective works based on the + Program. + + + + In addition, mere aggregation of another work not based on the + Program with the Program (or with a work based on the Program) + on a volume of a storage or distribution medium does not bring + the other work under the scope of this License. + + + + + + + Section 3 + + + You may copy and distribute the Program (or a work based on + it, under ) in object code + or executable form under the terms of and above provided that you also do + one of the following: + + + + + + Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of + and above on a medium customarily + used for software interchange; or, + + + + + + Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of and above on a medium customarily + used for software interchange; or, + + + + + + Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with + such an offer, in accord with Subsection b above.) + + + + + + The source code for a work means the preferred form of the + work for making modifications to it. For an executable work, + complete source code means all the source code for all modules + it contains, plus any associated interface definition files, + plus the scripts used to control compilation and installation + of the executable. However, as a special exception, the + source code distributed need not include anything that is + normally distributed (in either source or binary form) with + the major components (compiler, kernel, and so on) of the + operating system on which the executable runs, unless that + component itself accompanies the executable. + + + + If distribution of executable or object code is made by + offering access to copy from a designated place, then offering + equivalent access to copy the source code from the same place + counts as distribution of the source code, even though third + parties are not compelled to copy the source along with the + object code. + + + + + + + Section 4 + + + You may not copy, modify, sublicense, or distribute the + Program except as expressly provided under this License. Any + attempt otherwise to copy, modify, sublicense or distribute + the Program is void, and will automatically terminate your + rights under this License. However, parties who have received + copies, or rights, from you under this License will not have + their licenses terminated so long as such parties remain in + full compliance. + + + + + + + Section 5 + + + You are not required to accept this License, since you have + not signed it. However, nothing else grants you permission to + modify or distribute the Program or its derivative works. + These actions are prohibited by law if you do not accept this + License. Therefore, by modifying or distributing the Program + (or any work based on the Program), you indicate your + acceptance of this License to do so, and all its terms and + conditions for copying, distributing or modifying the Program + or works based on it. + + + + + + + Section 6 + + Each time you redistribute the Program (or any work based on + the Program), the recipient automatically receives a license from + the original licensor to copy, distribute or modify the Program + subject to these terms and conditions. You may not impose any + further restrictions on the recipients' exercise of the rights + granted herein. You are not responsible for enforcing compliance + by third parties to this License. + + + + + + Section 7 + + If, as a consequence of a court judgment or allegation of + patent infringement or for any other reason (not limited to patent + issues), conditions are imposed on you (whether by court order, + agreement or otherwise) that contradict the conditions of this + License, they do not excuse you from the conditions of this + License. If you cannot distribute so as to satisfy simultaneously + your obligations under this License and any other pertinent + obligations, then as a consequence you may not distribute the + Program at all. For example, if a patent license would not permit + royalty-free redistribution of the Program by all those who + receive copies directly or indirectly through you, then the only + way you could satisfy both it and this License would be to refrain + entirely from distribution of the Program. + + If any portion of this section is held invalid or + unenforceable under any particular circumstance, the balance of + the section is intended to apply and the section as a whole is + intended to apply in other circumstances. + + It is not the purpose of this section to induce you to + infringe any patents or other property right claims or to contest + validity of any such claims; this section has the sole purpose of + protecting the integrity of the free software distribution system, + which is implemented by public license practices. Many people + have made generous contributions to the wide range of software + distributed through that system in reliance on consistent + application of that system; it is up to the author/donor to decide + if he or she is willing to distribute software through any other + system and a licensee cannot impose that choice. + + This section is intended to make thoroughly clear what is + believed to be a consequence of the rest of this License. + + + + + + Section 8 + + If the distribution and/or use of the Program is restricted + in certain countries either by patents or by copyrighted + interfaces, the original copyright holder who places the Program + under this License may add an explicit geographical distribution + limitation excluding those countries, so that distribution is + permitted only in or among countries not thus excluded. In such + case, this License incorporates the limitation as if written in + the body of this License. + + + + + + Section 9 + + The Free Software Foundation may publish revised and/or new + versions of the General Public License from time to time. Such + new versions will be similar in spirit to the present version, but + may differ in detail to address new problems or concerns. + + Each version is given a distinguishing version number. If + the Program specifies a version number of this License which + applies to it and 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. + + + + + + Section 10 + + If you wish to incorporate parts of the Program into other + free programs whose distribution conditions are different, write + to the author to ask for permission. For software which is + copyrighted by the Free Software Foundation, write to the Free + Software Foundation; we sometimes make exceptions for this. Our + decision will be guided by the two goals of preserving the free + status of all derivatives of our free software and of promoting + the sharing and reuse of software generally. + + + + + + NO WARRANTY + Section 11 + + BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO + WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE + LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT + HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM AS IS WITHOUT + 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. + + + + + + Section 12 + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO + IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY + MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE + LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, + INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR + INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF + DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU + OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY + OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN + ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + + End of Terms and Conditions. + + + + + + + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of + the greatest possible use to the public, the best way to + achieve this is to make it free software which everyone can + redistribute and change under these terms. + + To do so, attach the following notices to the program. + It is safest to attach them to the start of each source file + to most effectively convey the exclusion of warranty; and each + file should have at least the copyright line + and a pointer to where the full notice is found. + + +<one line to give the program's name and a brief idea of what it does.> +Copyright (C) 19yy <name of author> + +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., 675 Mass Ave, Cambridge, MA 02139, USA. + + + Also add information on how to contact you by electronic + and paper mail. + + If the program is interactive, make it output a short + notice like this when it starts in an interactive mode: + + +Gnomovision version 69, Copyright (C) 19yy name of author +Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. +This is free software, and you are welcome to redistribute it +under certain conditions; type `show c' for details. + + + The hypothetical commands `show w' and `show c' should + show the appropriate parts of the General Public License. Of + course, the commands you use may be called something other + than `show w' and `show c'; they could even be mouse-clicks or + menu items–whatever suits your program. + + You should also get your employer (if you work as a + programmer) or your school, if any, to sign a copyright + disclaimer for the program, if necessary. Here is a + sample; alter the names: + + +Yoyodyne, Inc., hereby disclaims all copyright interest in the program +`Gnomovision' (which makes passes at compilers) written by James Hacker. + +<signature of Ty Coon>, 1 April 1989 +Ty Coon, President of Vice + + + This General Public License does not permit + incorporating your program into proprietary programs. If your + program is a subroutine library, you may consider it more + useful to permit linking proprietary applications with the + library. If this is what you want to do, use the GNU Library + General Public License instead of this License. + + + + diff --git a/Manuals/Common_content/Preface.docbook b/Manuals/Common_content/Preface.docbook new file mode 100644 index 0000000..4a20b77 --- /dev/null +++ b/Manuals/Common_content/Preface.docbook @@ -0,0 +1,89 @@ + + + Preface + + + Welcome to &TCARUG;, the official documentation of &TCAR;. + + + + This book describes the corporate visual identity of &TCP; and + the way it is produced. If you are interested in making &TCP; + a more beautiful project, this book is definitly for you. + + + + To make the information in this book managable, it has been + organized in the following parts: + + + + + + describes the convenctions you should + follow to keep everything organized and consistent inside the + repository directory structure, how to to install and + configure a working copy inside your workstation. At the end + of this part you will find a history of most relevant changes + committed to the repository along the years. + + + + + + describes the corporate visual + identity of the organization known as &TCP; and the production + tasks related to image rendition inside &TCAR;. If you are a + graphic designer, this part of the book might result + interesting to you. + + + + + + describes production tasks related to + content internationalization and localization inside &TCAR;. + If you are a translator, this part of the book might result + interesting to you. + + + + + + describes production tasks related + to content documentation inside &TCAR;. If you are a + documentor, this part of the book might result interesting to + you. + + + + + + describes automation of production + tasks inside &TCAR;. If you are a programmer, this part of the + book might result interesting to you. + + + + + + organizes the licenses mentioned + in this book. + + + + + + + This book assumes you have a basic understanding of &TCD;. If + you need help with it, go to the Help page inside + &TCWIKI; for or a list of different places you can find help. + + + &preface-overview; + &preface-history; + &preface-docconvs; + &preface-feedback; + + diff --git a/Manuals/Common_content/Preface.ent b/Manuals/Common_content/Preface.ent new file mode 100644 index 0000000..9b60f8b --- /dev/null +++ b/Manuals/Common_content/Preface.ent @@ -0,0 +1,5 @@ + + + + + diff --git a/Manuals/Common_content/Preface/docconvs.docbook b/Manuals/Common_content/Preface/docconvs.docbook new file mode 100644 index 0000000..8eda7bc --- /dev/null +++ b/Manuals/Common_content/Preface/docconvs.docbook @@ -0,0 +1,225 @@ +
+ + Document Convenctions + + + In this manual, certain words are represented in different + fonts, typefaces, sizes, and weights. This highlighting is + systematic; different words are represented in the same style + to indicate their inclusion in a specific category. The types + of words that are represented this way include the + following: + + + + + command + + + Linux commands (and other operating system commands, when + used) are represented this way. This style should + indicate to you that you can type the word or phrase on + the command line and press Enter to + invoke a command. Sometimes a command contains words that + would be displayed in a different style on their own (such + as file names). In these cases, they are considered to be + part of the command, so the entire phrase is displayed as + a command. For example: + + + + Use the centos-art render + trunk/Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda + --filter="01-welcome" command to produce the first + slide image used by Anaconda in the branch 5 of &TCD; + using the version 4 of TreeFlower artistic motif. + + + + + + file name + + + File names, directory names, paths, and RPM package names + are represented this way. This style indicates that a + particular file or directory exists with that name on your + system. Examples: + + + + The init.sh file in trunk/Scripts/Bash/Cli/ + directory is the initialization script, written in Bash, + used to automate most of tasks in the repository. + + + + The centos-art command uses the + ImageMagick RPM package to convert + images from PNG format to other formats. + + + + + + key + + + A key on the keyboard is shown in this style. For + example: + + + + To use Tab completion to list particular + files in a directory, type ls, then a + character, and finally the Tab key. Your + terminal displays the list of files in the working + directory that begin with that character. + + + + + + keycombination + + + A combination of keystrokes is represented in this way. + For example: + + + + The CtrlAltBackspace + key combination exits your graphical session and returns + you to the graphical login screen or the console. + + + + + + computer output + + + Text in this style indicates text displayed to a shell + prompt such as error messages and responses to commands. + For example, the ls command displays + the contents of a directory using this style: + + + +render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh +render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh +render_getDirOutput.sh render.sh + + + + The output returned in response to the command (in this + case, the contents of the directory) is shown in this + style. + + + + + + prompt + + + A prompt, which is a computer's way of signifying that it + is ready for you to input something, is shown in this + style. Examples: + + + + + + $ + + + + + # + + + + + [centos@projects centos]$ + + + + + projects login: + + + + + + + + user input + + + Text that the user types, either on the command line or + into a text box on a GUI screen, is displayed in this + style. In the following example, + text is displayed in this style: To + boot your system into the text based installation program, + you must type in the text command + at the boot: prompt. + + + + + + replaceable + + + Text used in examples that is meant to be replaced with + data provided by the user is displayed in this style. In + the following example, + version-number is displayed in + this style: The directory for the kernel source is + /usr/src/kernels/version-number/, + where version-number is the + version and type of kernel installed on this system. + + + + + + Additionally, we use several different strategies to draw + your attention to certain pieces of information. In order of + urgency, these items are marked as a note, tip, important, + caution, or warning. For example: + + + Remember that Linux is case sensitive. In other words, a + rose is not a ROSE is not a rOsE. + + + + The directory /usr/share/doc/ contains + additional documentation for packages installed on your + system. + + + + If you modify the DHCP configuration file, the changes + do not take effect until you restart the DHCP daemon. + + + + Do not perform routine tasks as root — use a + regular user account unless you need to use the root account + for system administration tasks. + + + + Be careful to remove only the necessary partitions. + Removing other partitions could result in data loss or a + corrupted system environment. + + +
diff --git a/Manuals/Common_content/Preface/feedback.docbook b/Manuals/Common_content/Preface/feedback.docbook new file mode 100644 index 0000000..b6f8334 --- /dev/null +++ b/Manuals/Common_content/Preface/feedback.docbook @@ -0,0 +1,14 @@ +
+ + Send In Your Feedback + + + If you find a bug in &TCAR; or this manual, we would like to + hear about it. To report bugs related to this manual, send an + e-mail to the centos-devel@centos.org mailing + list. When you write the bug report, take care of being + specific about the problem you are reporting on (e.g., where + it is, the section number, etc.) so we can found it easily. + + +
diff --git a/Manuals/Common_content/Preface/history.docbook b/Manuals/Common_content/Preface/history.docbook new file mode 100644 index 0000000..2197f1f --- /dev/null +++ b/Manuals/Common_content/Preface/history.docbook @@ -0,0 +1,65 @@ +
+ History + + &TCAR; started at The CentOS Developers + Mailing List around 2008, on a discussion about how to + automate slide images used by Anaconda (&TCD; installer). In + such discussion, Ralph + Angenendt rose up his hand to ask —Do you have + something to show?—. + + + + To answer the question, Alain Reguera + Delgado suggested a bash script which combined SVG and + SED files in order to produce PNG images in different + languages —in conjunction with the proposition of + creating a Subversion repository where translations and image + production could be distributed inside &TCC;—. + + + + Karanbir + Singh considered the idea intresting and provided the + infrastructure necessary to support the effort. This way, + &TCAS; and &TCAR; were officially created and made world wide + available. In this configuration, users were able to register + themselves and administrators were able to assign access + rights to registered users inside &TCAR;, both using a web + interface. + + + + Once &TCAR; was available, Alain Reguera Delgado uploaded the + bash script used to produce the Anaconda + slides;See Ralph Angenendt documented it very + well;See and people started to download working + copies of &TCAR; to produce slide images in their own + languages.See the following Google + search. + + + + From this time on &TCAR; has been evolving into an automated + production environment where &TCC; can conceive &TCP; + corporate visual identity. + + + + The exact changes commited to &TCAR; through history can be + found in the repository + logs so you can know the real history about it. For + those of you who just want to get a glance of changes + committed, see . + + +
diff --git a/Manuals/Common_content/Preface/overview.docbook b/Manuals/Common_content/Preface/overview.docbook new file mode 100644 index 0000000..702dfdd --- /dev/null +++ b/Manuals/Common_content/Preface/overview.docbook @@ -0,0 +1,119 @@ +
+ Overview + + + The corporations always have a corporate identity, even when + they don't take an intentional control over it. It is a choise + from the corporation to define how much control to take over + its identity. This kind of control is expensive and not all + corporations are able to maintain it. However, it is + necessary that, based on pragmatic facts, the corporation + assume an acceptable degree of compromise with its identity in + order to create a consistent idea of itself in a way that can + be progresively improved through time. + + + + During the years (2003-2009), we've seen a growing interest + inside &TCC; for helping on &TCP; development. Some people + seem to be very clear about what the project needs are and how + to maintain it being a very stable project, but others however + don't to get what &TCP; is (even it is explained time after + time) and sometimes decide to put their efforts in the wrong + direction making everything to be a waste of time and source + of distraction from what is really needed. + + + + &TCAR; phases the question What can I do for + &TCP;? by identifying different work lines you can + join in and providing automated production mechanisms that + complement one another according to each work line needs so + consistent results can be achieved inside a distributed + environment under version control. For example, consider an + environment where there are graphic designers to produce + images, documentors to produce documentation manuals (whose + can use images produced by graphic designers), programmers to + produce automation scripts (needed to standardize production + tasks) and translators to localize source files created by + graphic designers, documetors and programmers. Once such + environment has been implemented, it would be possible for + packagers to take localized images and localized documentation + from &TCAR; (through an automation script probably) to + rebrand/update the content of those packages inside &TCD; that + must include information specific to &TCP; itself (e.g., boot + loader, distribution installer, release notes, display + managers, release notes, web browsers default page, etc.). + + + + Most production tasks inside &TCAR; are focused on the files + needed to implement &TCP; corporate visual identity. + + Notice that, here, visual identity means everything + perceived through the human's visual sences (i.e., the + human eyes), but the corporate identity is a wider concept + that extends to all human senses (i.e., visibilty (eyes), + audition (ears), scent (nose), touch (fingers), and savour + (tongue)), not just that one related to visual aspects. + Nevertheless, we need to be consequent with the media + where &TCP; manifests its existence on, as described in + . + This includes everything from file edition + (e.g., text width, text indentation, line numbering, text + tabulation, etc.) up to how the web sites, distribution, and + industrial stuff (e.g., pullovers, caps, installation media, + etc.) look and feel. Notice that, more specific details like + typography, window design, icons, menu items, etc., inside + &TCD; are already covered by &TCP; upstream provider. In our + effort to be 100% binary compatible with the upstream provider + and also keeping maintainance low, we stand over those + specific details as much as possible assuming them as default. + However, if you feel brave enough (and prove your ability to + keep yourself being that way) it would be possible to open a + work line for you to maintain variants of such very specific + details inside &TCAR;. + + + + In addition to visual manifestations, there are also emotional + feelings and ethical behaviours that must be considered as + part of &TCP; corporate identity. A pleasant experience in + this area includes &TCWIKI;, specifically the way it was + conceived and administered. When the &TCWIKI; was published, + &TCP; published a list of needs with it so anyone could + contribute based on them. Not much time after that, the list + of tasks triggered some souls' motivations ruled by the good + will of initiating the translation of that content published + inside the wiki, redesigning its visual style, proposing the + TreeFlower theme for &TCD;, and reducing to zero the + contraditions of precoceived minds with respect, reason and + passion. As result of this experience, we found that &TCC; + posseses an incredible strong creative force, however, a long + path must be traveled before it can be focalized into the + right direction because: it isn't enough just telling what the + right direction is, it is also necessary to provide the + vehicles for &TCC; be able of moving through it. + + + + &TCAR; extends the feelings and ethicals behaviours from + &TCWIKI; to itself by identifying the visual manifestations + &TCP; is made of (i.e., tracing a direction) and allowing + people to develop them through standardized procedures inside + a colaborative environment (i.e., providing the vehicles). + + + + Finally, if you find yourself needing to do something for + &TCP; and &TCAR; isn't the place for it, be sure to define + what that something exactly is and also make it a community + effort so it can be validated as something useful to the + community itself. Otherwise, the effort would loose its + initial sense soon enough so as to be considered seriously. + Notice that the way these needs are described may take + different forms: they can be written and organized inside a + book, an article, or even a well documented program ;-). + + +
diff --git a/Manuals/Tcar-ug/Commons.ent b/Manuals/Tcar-ug/Commons.ent deleted file mode 100644 index e42c505..0000000 --- a/Manuals/Tcar-ug/Commons.ent +++ /dev/null @@ -1,52 +0,0 @@ - - - - - - - - - - - - - - -&TC; Project"> - - - -&TC; Mirrors"> - - - - - - - -&TCA; Repository"> -&TCA; SIG"> - -The CentOS Artwork Repository User's Guide"> - -centos-artwork@centos.org mailing list"> -centos-devel@centos.org mailing list"> -centos-info@centos.org mailing list"> - -&TC; Wiki"> -&TC; Mailing Lists"> - - - -"> -"> -"> -"> - -&TC; Documentation"> diff --git a/Manuals/Tcar-ug/Licenses.docbook b/Manuals/Tcar-ug/Licenses.docbook deleted file mode 100644 index dfc86ce..0000000 --- a/Manuals/Tcar-ug/Licenses.docbook +++ /dev/null @@ -1,6 +0,0 @@ - - Licenses - &licenses-gpl; - &licenses-gfdl; - - diff --git a/Manuals/Tcar-ug/Licenses.ent b/Manuals/Tcar-ug/Licenses.ent deleted file mode 100644 index 29e0b56..0000000 --- a/Manuals/Tcar-ug/Licenses.ent +++ /dev/null @@ -1,3 +0,0 @@ - - - diff --git a/Manuals/Tcar-ug/Licenses/gfdl.docbook b/Manuals/Tcar-ug/Licenses/gfdl.docbook deleted file mode 100644 index a8fef02..0000000 --- a/Manuals/Tcar-ug/Licenses/gfdl.docbook +++ /dev/null @@ -1,605 +0,0 @@ - - - GNU Free Documentation License - - Version 1.2, November 2002 - - Copyright © 2000, 2001, 2002 Free Software Foundation, - Inc. 675 Mass Ave, Cambridge, MA 02139, USA - - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - - - Preamble - - The purpose of this License is to make a manual, - textbook, or other functional and useful document - free in 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. - - This License is a kind of copyleft, which - means that derivative works of the document must themselves be - free in the same sense. It complements the , which is a copyleft license - designed for free software. - - We have designed this License in order to use it for - manuals for free software, because free software needs free - documentation: a free program should come with manuals - providing the same freedoms that the software does. But this - License is not limited to software manuals; it can be used for - any textual work, regardless of subject matter or whether it - is published as a printed book. We recommend this License - principally for works whose purpose is instruction or - reference. - - - - - - Applicability and definitions - - This License applies to any manual or other work, in any - medium, that contains a notice placed by the copyright holder - saying it can be distributed under the terms of this License. - Such a notice grants a world-wide, royalty-free license, - unlimited in duration, to use that work under the conditions - stated herein. 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. - - A - Modified Version of 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. - - A - Secondary Section is 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 may not explain any mathematics.) The relationship could be - a matter of historical connection with the subject or with - related matters, or of legal, commercial, philosophical, - ethical or political position regarding them. - - The Invariant Sections are certain - whose titles are - designated, as being those of Invariant Sections, in the - notice that says that the Document is released under this - License. If a section does not fit the above definition of - Secondary then it is not allowed to be designated as - Invariant. The Document may contain zero Invariant Sections. - If the Document does not identify any Invariant Section then - there are none. - - The - Cover Texts are 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. - - A - Transparent copy 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 file format whose - markup, or absence of markup, has been arranged to thwart or - discourage subsequent modification by readers is not . An image format is not if used for any substantial amount of - text. A copy that is not is called Opaque. - - Examples of suitable formats for copies - include plain ASCII without markup, Texinfo input format, - LaTeX input format, SGML or XML using a publicly available - DTD, and standard-conforming simple HTML, PostScript or PDF - designed for human modification. Examples of transparent - image formats include PNG, XCF and JPG. Opaque formats - include proprietary formats that can be read and edited only - by proprietary word processors, SGML or XML for which the DTD - and/or processing tools are not generally available, and the - machine-generated HTML, PostScript or PDF produced by some - word processors for output purposes only. - - The Title - Page means, 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 Page means the text near the most - prominent appearance of the work's title, preceding the - beginning of the body of the text. - - A section Entitled XYZ means 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 XYZ according to - this definition. - - The Document may include Warranty Disclaimers next to - the notice which states that this License applies to the - Document. These Warranty Disclaimers are considered to be - included by reference in this License, but only as regards - disclaiming warranties: any other implication that these - Warranty Disclaimers may have is void and has no effect on the - meaning of this License. - - - - - - Verbatim copying - - You may copy and distribute the Document in any medium, - either commercially or noncommercially, provided that this - License, the copyright notices, and the license notice saying - this License applies to the Document are reproduced in all - copies, and that you add no other conditions whatsoever to - those of this License. You may not use technical measures to - obstruct or control the reading or further copying of the - copies you make or distribute. However, you may accept - compensation in exchange for copies. If you distribute a - large enough number of copies you must also follow the - conditions in section . - - You may also lend copies, under the same conditions - stated above, and you may publicly display copies. - - - - - - Copying in quantity - - If you publish printed copies (or copies in media that - commonly have printed covers) of the Document, numbering more - than 100, and the Document's license notice requires Cover - Texts, you must enclose the copies in covers that carry, - clearly and legibly, all these : - Front-Cover Texts on the front cover, and Back-Cover Texts on - the back cover. Both covers must also clearly and legibly - identify you as the publisher of these copies. The front - cover must present the full title with all words of the title - equally prominent and visible. You may add other material on - the covers in addition. Copying with changes limited to the - covers, as long as they preserve the title of the Document and - satisfy these conditions, can be treated as verbatim copying - in other respects. - - If the required texts for either cover are too - voluminous to fit legibly, you should put the first ones - listed (as many as fit reasonably) on the actual cover, and - continue the rest onto adjacent pages. - - If you publish or distribute Opaque copies of the - Document numbering more than 100, you must either include a - machine-readable copy along with each Opaque copy, - or state in or with each Opaque copy a computer-network - location from which the general network-using public has - access to download using public-standard network protocols a - complete copy of the Document, free of added - material. If you use the latter option, you must take - reasonably prudent steps, when you begin distribution of - Opaque copies in quantity, to ensure that this - copy will remain thus accessible at the stated location until - at least one year after the last time you distribute an Opaque - copy (directly or through your agents or retailers) of that - edition to the public. - - It is requested, but not required, that you contact the - authors of the Document well before redistributing any large - number of copies, to give them a chance to provide you with an - updated version of the Document. - - - - - - Modifications - - - You may copy and distribute a of the Document under the - conditions of sections and above, provided that - you release the under - precisely this License, with the filling the role of the - Document, thus licensing distribution and modification of - the to whoever - possesses a copy of it. In addition, you must do these - things in the : - - - - - - Use in the (and on - the covers, if any) a title distinct from that of the - Document, and from those of previous versions (which - should, if there were any, be listed in the History - section of the Document). You may use the same title - as a previous version if the original publisher of - that version gives permission. - - - List on the , as - authors, one or more persons or entities responsible - for authorship of the modifications in the , together with at least - five of the principal authors of the Document (all of - its principal authors, if it has fewer than five), - unless they release you from this requirement. - - - - State on the the - name of the publisher of the , as the - publisher. - - - - Preserve all the copyright notices of the - Document. - - - - Add an appropriate copyright notice for your - modifications adjacent to the other copyright - notices. - - - - Include, immediately after the copyright - notices, a license notice giving the public permission - to use the under the terms of this - License, in the form shown in the Addendum - below. - - - - Preserve in that license notice the full lists - of and required - given in the Document's - license notice. - - - - Include an unaltered copy of this License. - - - - Preserve the section Entitled - History, Preserve its Title, and add to - it an item stating at least the title, year, new - authors, and publisher of the as given on the . If there is no section - Entitled History in the Document, create - one stating the title, year, authors, and publisher of - the Document as given on its , then add an item describing the as stated in the previous - sentence. - - - - Preserve the network location, if any, given in - the Document for public access to a copy of the Document, and - likewise the network locations given in the Document - for previous versions it was based on. These may be - placed in the History section. 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. - - - - For any section Entitled - Acknowledgements or - 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. - - - - Preserve all the of the Document, - unaltered in their text and in their titles. Section - numbers or the equivalent are not considered part of - the section titles. - - - - Delete any section Entitled - Endorsements. Such a section may not - be included in the . - - - - Do not retitle any existing section to be - Entitled Endorsements or to conflict in - title with any . - - - Preserve any Warranty Disclaimers. - - - - - If the includes new - front-matter sections or appendices that qualify as and contain no material - copied from the Document, you may at your option designate - some or all of these sections as invariant. To do this, - add their titles to the list of in the 's license notice. These - titles must be distinct from any other section - titles. - - - - You may add a section Entitled - Endorsements, provided it contains nothing - but endorsements of your by various parties–for example, statements of - peer review or that the text has been approved by an - organization as the authoritative definition of a - standard. - - - - You may add a passage of up to five words as a Front-Cover - Text, and a passage of up to 25 words as a Back-Cover - Text, to the end of the list of in the . Only one passage of - Front-Cover Text and one of Back-Cover Text may be added - by (or through arrangements made by) any one entity. If - the Document already includes a cover text for the same - cover, previously added by you or by arrangement made by - the same entity you are acting on behalf of, you may not - add another; but you may replace the old one, on explicit - permission from the previous publisher that added the old - one. - - - - The author(s) and publisher(s) of the Document do not by - this License give permission to use their names for - publicity for or to assert or imply endorsement of any - . - - - - - - - Combining documents - - You may combine the Document with other documents - released under this License, under the terms defined in - section above for - modified versions, provided that you include in the - combination all of the of - all of the original documents, unmodified, and list them all - as of your combined work - in its license notice, and that you preserve all their - Warranty Disclaimers. - - The combined work need only contain one copy of this - License, and multiple identical may be replaced with a single - copy. If there are multiple with the same name but - different contents, make the title of each such section unique - by adding at the end of it, in parentheses, the name of the - original author or publisher of that section if known, or else - a unique number. Make the same adjustment to the section - titles in the list of in - the license notice of the combined work. - - In the combination, you must combine any sections - Entitled History in 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. - - - - - - Collection of documents - - You may make a collection consisting of the Document and - other documents released under this License, and replace the - individual copies of this License in the various documents - with a single copy that is included in the collection, - provided that you follow the rules of this License for - verbatim copying of each of the documents in all other - respects. - - You may extract a single document from such a - collection, and distribute it individually under this License, - provided you insert a copy of this License into the extracted - document, and follow this License in all other respects - regarding verbatim copying of that document. - - - - - - Aggregation with independent works - - A compilation of the Document or its derivatives with - other separate and independent documents or works, in or on a - volume of a storage or distribution medium, is called an - aggregate if 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. - - If the Cover Text requirement of section is applicable to these - copies of the Document, then if the Document is less than one - half of the entire aggregate, the Document's may be placed on covers that bracket - the Document within the aggregate, or the electronic - equivalent of covers if the Document is in electronic form. - Otherwise they must appear on printed covers that bracket the - whole aggregate. - - - - - - Translations - - Translation is considered a kind of modification, so you - may distribute translations of the Document under the terms of - section . Replacing - with translations - requires special permission from their copyright holders, but - you may include translations of some or all in addition to the original - versions of these . You - may include a translation of this License, and all the license - notices in the Document, and any Warranty Disclaimers, - provided that you also include the original English version of - this License and the original versions of those notices and - disclaimers. In case of a disagreement between the - translation and the original version of this License or a - notice or disclaimer, the original version will - prevail. - - If a section in the Document is Entitled - Acknowledgements, Dedications, - or History, the requirement (section ) to Preserve its Title - (section ) will - typically require changing the actual title. - - - - - - Termination - - You may not copy, modify, sublicense, or distribute the - Document except as expressly provided for under this License. - Any other attempt to copy, modify, sublicense or distribute - the Document is void, and will automatically terminate your - rights under this License. However, parties who have received - copies, or rights, from you under this License will not have - their licenses terminated so long as such parties remain in - full compliance. - - - - - - Future Revisions of this License - - The Free Software Foundation may publish new, revised - versions of the GNU Free Documentation License from time to - time. Such new versions will be similar in spirit to the - present version, but may differ in detail to address new - problems or concerns. See . - - Each version of the License is given a distinguishing - version number. If the Document specifies that a particular - numbered version of this License or any later - version applies 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. - - - - - - How to use this License for your documents - - To use this License in a document you have written, - include a copy of the License in the document and put the - following copyright and license notices just after the title - page: - - -Copyright (C) YEAR YOUR NAME. - -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 GNU Free Documentation License. - - - If you have , - Front-Cover Texts and Back-Cover Texts, replace the - with...Texts. line with this: - - -with the Invariant Sections being LIST THEIR TITLES, with the -Front-Cover Texts being LIST, and with the Back-Cover Texts being -LIST. - - - If you have - without , or some other - combination of the three, merge those two alternatives to suit - the situation. - - If your document contains nontrivial examples of program - code, we recommend releasing these examples in parallel under - your choice of free software license, such as the GNU General - Public License, to permit their use in free software. - - - - diff --git a/Manuals/Tcar-ug/Licenses/gpl.docbook b/Manuals/Tcar-ug/Licenses/gpl.docbook deleted file mode 100644 index fe1c604..0000000 --- a/Manuals/Tcar-ug/Licenses/gpl.docbook +++ /dev/null @@ -1,537 +0,0 @@ - - - GNU General Public License - - - Version 2, June 1991 - - - - Copyright © 1989, 1991 Free Software Foundation, Inc. - 675 Mass Ave, Cambridge, MA 02139, USA - - - - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not - allowed. - - - - - Preamble - - - The licenses for most software are designed to take away your - freedom to share and change it. By contrast, the GNU General - Public License is intended to guarantee your freedom to share - and change free software–to make sure the software is - free for all its users. This General Public License applies - to most of the Free Software Foundation's software and to any - other program whose authors commit to using it. (Some other - Free Software Foundation software is covered by the GNU - Library General Public License instead.) You can apply it to - your programs, too. - - - - When we speak of free software, we are referring to freedom, - not price. Our General Public Licenses are designed to make - sure that you have the freedom to distribute copies of free - software (and charge for this service if you wish), that you - receive source code or can get it if you want it, that you can - change the software or use pieces of it in new free programs; - and that you know you can do these things. - - - - To protect your rights, we need to make restrictions that - forbid anyone to deny you these rights or to ask you to - surrender the rights. These restrictions translate to certain - responsibilities for you if you distribute copies of the - software, or if you modify it. - - - - For example, if you distribute copies of such a program, - whether gratis or for a fee, 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 show them - these terms so they know their rights. - - - - We protect your rights with two steps: - - - - - copyright the software, and - - - offer you this license which gives you legal - permission to copy, distribute and/or modify the - software. - - - - - Also, for each author's protection and ours, we want to make - certain that everyone understands that there is no warranty - for this free software. If the software is modified by - someone else and passed on, we want its recipients to know - that what they have is not the original, so that any problems - introduced by others will not reflect on the original authors' - reputations. - - - - Finally, any free program is threatened constantly by software - patents. We wish to avoid the danger that redistributors of a - free program will individually obtain patent licenses, in - effect making the program proprietary. To prevent this, we - have made it clear that any patent must be licensed for - everyone's free use or not licensed at all. - - - - The precise terms and conditions for copying, distribution and - modification follow. - - - - - - - Terms and Conditions for Copying, Distribution and Modification - - - - Section 1 - - - You may copy and distribute verbatim copies of the Program's - source code as you receive it, in any medium, provided that - you conspicuously and appropriately publish on each copy an - appropriate copyright notice and disclaimer of warranty; keep - intact all the notices that refer to this License and to the - absence of any warranty; and give any other recipients of the - Program a copy of this License along with the Program. - - - - You may charge a fee for the physical act of transferring a - copy, and you may at your option offer warranty protection in - exchange for a fee. - - - - - - - Section 2 - - - You may modify your copy or copies of the Program or any - portion of it, thus forming a work based on the Program, and - copy and distribute such modifications or work under the terms - of above, provided that - you also meet all of these conditions: - - - - - - You must cause the modified files to carry prominent notices - stating that you changed the files and the date of any - change. - - - - - You must cause any work that you distribute or publish, that - in whole or in part contains or is derived from the Program or - any part thereof, to be licensed as a whole at no charge to - all third parties under the terms of this License. - - - - - If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display - an announcement including an appropriate copyright notice and - a notice that there is no warranty (or else, saying that you - provide a warranty) and that users may redistribute the - program under these conditions, and telling the user how to - view a copy of this License. - - - - - - Exception - - If the Program itself is interactive but does not normally - print such an announcement, your work based on the Program is - not required to print an announcement. - - - - - These requirements apply to the modified work as a whole. If - identifiable sections of that work are not derived from the - Program, and can be reasonably considered independent and - separate works in themselves, then this License, and its - terms, do not apply to those sections when you distribute them - as separate works. But when you distribute the same sections - as part of a whole which is a work based on the Program, the - distribution of the whole must be on the terms of this - License, whose permissions for other licensees extend to the - entire whole, and thus to each and every part regardless of - who wrote it. - - - - Thus, it is not the intent of this section to claim rights or - contest your rights to work written entirely by you; rather, - the intent is to exercise the right to control the - distribution of derivative or collective works based on the - Program. - - - - In addition, mere aggregation of another work not based on the - Program with the Program (or with a work based on the Program) - on a volume of a storage or distribution medium does not bring - the other work under the scope of this License. - - - - - - - Section 3 - - - You may copy and distribute the Program (or a work based on - it, under ) in object code - or executable form under the terms of and above provided that you also do - one of the following: - - - - - - Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of - and above on a medium customarily - used for software interchange; or, - - - - - - Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of and above on a medium customarily - used for software interchange; or, - - - - - - Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with - such an offer, in accord with Subsection b above.) - - - - - - The source code for a work means the preferred form of the - work for making modifications to it. For an executable work, - complete source code means all the source code for all modules - it contains, plus any associated interface definition files, - plus the scripts used to control compilation and installation - of the executable. However, as a special exception, the - source code distributed need not include anything that is - normally distributed (in either source or binary form) with - the major components (compiler, kernel, and so on) of the - operating system on which the executable runs, unless that - component itself accompanies the executable. - - - - If distribution of executable or object code is made by - offering access to copy from a designated place, then offering - equivalent access to copy the source code from the same place - counts as distribution of the source code, even though third - parties are not compelled to copy the source along with the - object code. - - - - - - - Section 4 - - - You may not copy, modify, sublicense, or distribute the - Program except as expressly provided under this License. Any - attempt otherwise to copy, modify, sublicense or distribute - the Program is void, and will automatically terminate your - rights under this License. However, parties who have received - copies, or rights, from you under this License will not have - their licenses terminated so long as such parties remain in - full compliance. - - - - - - - Section 5 - - - You are not required to accept this License, since you have - not signed it. However, nothing else grants you permission to - modify or distribute the Program or its derivative works. - These actions are prohibited by law if you do not accept this - License. Therefore, by modifying or distributing the Program - (or any work based on the Program), you indicate your - acceptance of this License to do so, and all its terms and - conditions for copying, distributing or modifying the Program - or works based on it. - - - - - - - Section 6 - - Each time you redistribute the Program (or any work based on - the Program), the recipient automatically receives a license from - the original licensor to copy, distribute or modify the Program - subject to these terms and conditions. You may not impose any - further restrictions on the recipients' exercise of the rights - granted herein. You are not responsible for enforcing compliance - by third parties to this License. - - - - - - Section 7 - - If, as a consequence of a court judgment or allegation of - patent infringement or for any other reason (not limited to patent - issues), conditions are imposed on you (whether by court order, - agreement or otherwise) that contradict the conditions of this - License, they do not excuse you from the conditions of this - License. If you cannot distribute so as to satisfy simultaneously - your obligations under this License and any other pertinent - obligations, then as a consequence you may not distribute the - Program at all. For example, if a patent license would not permit - royalty-free redistribution of the Program by all those who - receive copies directly or indirectly through you, then the only - way you could satisfy both it and this License would be to refrain - entirely from distribution of the Program. - - If any portion of this section is held invalid or - unenforceable under any particular circumstance, the balance of - the section is intended to apply and the section as a whole is - intended to apply in other circumstances. - - It is not the purpose of this section to induce you to - infringe any patents or other property right claims or to contest - validity of any such claims; this section has the sole purpose of - protecting the integrity of the free software distribution system, - which is implemented by public license practices. Many people - have made generous contributions to the wide range of software - distributed through that system in reliance on consistent - application of that system; it is up to the author/donor to decide - if he or she is willing to distribute software through any other - system and a licensee cannot impose that choice. - - This section is intended to make thoroughly clear what is - believed to be a consequence of the rest of this License. - - - - - - Section 8 - - If the distribution and/or use of the Program is restricted - in certain countries either by patents or by copyrighted - interfaces, the original copyright holder who places the Program - under this License may add an explicit geographical distribution - limitation excluding those countries, so that distribution is - permitted only in or among countries not thus excluded. In such - case, this License incorporates the limitation as if written in - the body of this License. - - - - - - Section 9 - - The Free Software Foundation may publish revised and/or new - versions of the General Public License from time to time. Such - new versions will be similar in spirit to the present version, but - may differ in detail to address new problems or concerns. - - Each version is given a distinguishing version number. If - the Program specifies a version number of this License which - applies to it and 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. - - - - - - Section 10 - - If you wish to incorporate parts of the Program into other - free programs whose distribution conditions are different, write - to the author to ask for permission. For software which is - copyrighted by the Free Software Foundation, write to the Free - Software Foundation; we sometimes make exceptions for this. Our - decision will be guided by the two goals of preserving the free - status of all derivatives of our free software and of promoting - the sharing and reuse of software generally. - - - - - - NO WARRANTY - Section 11 - - BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO - WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE - LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT - HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM AS IS WITHOUT - 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. - - - - - - Section 12 - - IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO - IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY - MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE - LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, - INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR - INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF - DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU - OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY - OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - - End of Terms and Conditions. - - - - - - - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of - the greatest possible use to the public, the best way to - achieve this is to make it free software which everyone can - redistribute and change under these terms. - - To do so, attach the following notices to the program. - It is safest to attach them to the start of each source file - to most effectively convey the exclusion of warranty; and each - file should have at least the copyright line - and a pointer to where the full notice is found. - - -<one line to give the program's name and a brief idea of what it does.> -Copyright (C) 19yy <name of author> - -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., 675 Mass Ave, Cambridge, MA 02139, USA. - - - Also add information on how to contact you by electronic - and paper mail. - - If the program is interactive, make it output a short - notice like this when it starts in an interactive mode: - - -Gnomovision version 69, Copyright (C) 19yy name of author -Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. -This is free software, and you are welcome to redistribute it -under certain conditions; type `show c' for details. - - - The hypothetical commands `show w' and `show c' should - show the appropriate parts of the General Public License. Of - course, the commands you use may be called something other - than `show w' and `show c'; they could even be mouse-clicks or - menu items–whatever suits your program. - - You should also get your employer (if you work as a - programmer) or your school, if any, to sign a copyright - disclaimer for the program, if necessary. Here is a - sample; alter the names: - - -Yoyodyne, Inc., hereby disclaims all copyright interest in the program -`Gnomovision' (which makes passes at compilers) written by James Hacker. - -<signature of Ty Coon>, 1 April 1989 -Ty Coon, President of Vice - - - This General Public License does not permit - incorporating your program into proprietary programs. If your - program is a subroutine library, you may consider it more - useful to permit linking proprietary applications with the - library. If this is what you want to do, use the GNU Library - General Public License instead of this License. - - - - diff --git a/Manuals/Tcar-ug/Preface.docbook b/Manuals/Tcar-ug/Preface.docbook deleted file mode 100644 index 4a20b77..0000000 --- a/Manuals/Tcar-ug/Preface.docbook +++ /dev/null @@ -1,89 +0,0 @@ - - - Preface - - - Welcome to &TCARUG;, the official documentation of &TCAR;. - - - - This book describes the corporate visual identity of &TCP; and - the way it is produced. If you are interested in making &TCP; - a more beautiful project, this book is definitly for you. - - - - To make the information in this book managable, it has been - organized in the following parts: - - - - - - describes the convenctions you should - follow to keep everything organized and consistent inside the - repository directory structure, how to to install and - configure a working copy inside your workstation. At the end - of this part you will find a history of most relevant changes - committed to the repository along the years. - - - - - - describes the corporate visual - identity of the organization known as &TCP; and the production - tasks related to image rendition inside &TCAR;. If you are a - graphic designer, this part of the book might result - interesting to you. - - - - - - describes production tasks related to - content internationalization and localization inside &TCAR;. - If you are a translator, this part of the book might result - interesting to you. - - - - - - describes production tasks related - to content documentation inside &TCAR;. If you are a - documentor, this part of the book might result interesting to - you. - - - - - - describes automation of production - tasks inside &TCAR;. If you are a programmer, this part of the - book might result interesting to you. - - - - - - organizes the licenses mentioned - in this book. - - - - - - - This book assumes you have a basic understanding of &TCD;. If - you need help with it, go to the Help page inside - &TCWIKI; for or a list of different places you can find help. - - - &preface-overview; - &preface-history; - &preface-docconvs; - &preface-feedback; - - diff --git a/Manuals/Tcar-ug/Preface.ent b/Manuals/Tcar-ug/Preface.ent deleted file mode 100644 index 9b60f8b..0000000 --- a/Manuals/Tcar-ug/Preface.ent +++ /dev/null @@ -1,5 +0,0 @@ - - - - - diff --git a/Manuals/Tcar-ug/Preface/docconvs.docbook b/Manuals/Tcar-ug/Preface/docconvs.docbook deleted file mode 100644 index 8eda7bc..0000000 --- a/Manuals/Tcar-ug/Preface/docconvs.docbook +++ /dev/null @@ -1,225 +0,0 @@ -
- - Document Convenctions - - - In this manual, certain words are represented in different - fonts, typefaces, sizes, and weights. This highlighting is - systematic; different words are represented in the same style - to indicate their inclusion in a specific category. The types - of words that are represented this way include the - following: - - - - - command - - - Linux commands (and other operating system commands, when - used) are represented this way. This style should - indicate to you that you can type the word or phrase on - the command line and press Enter to - invoke a command. Sometimes a command contains words that - would be displayed in a different style on their own (such - as file names). In these cases, they are considered to be - part of the command, so the entire phrase is displayed as - a command. For example: - - - - Use the centos-art render - trunk/Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda - --filter="01-welcome" command to produce the first - slide image used by Anaconda in the branch 5 of &TCD; - using the version 4 of TreeFlower artistic motif. - - - - - - file name - - - File names, directory names, paths, and RPM package names - are represented this way. This style indicates that a - particular file or directory exists with that name on your - system. Examples: - - - - The init.sh file in trunk/Scripts/Bash/Cli/ - directory is the initialization script, written in Bash, - used to automate most of tasks in the repository. - - - - The centos-art command uses the - ImageMagick RPM package to convert - images from PNG format to other formats. - - - - - - key - - - A key on the keyboard is shown in this style. For - example: - - - - To use Tab completion to list particular - files in a directory, type ls, then a - character, and finally the Tab key. Your - terminal displays the list of files in the working - directory that begin with that character. - - - - - - keycombination - - - A combination of keystrokes is represented in this way. - For example: - - - - The CtrlAltBackspace - key combination exits your graphical session and returns - you to the graphical login screen or the console. - - - - - - computer output - - - Text in this style indicates text displayed to a shell - prompt such as error messages and responses to commands. - For example, the ls command displays - the contents of a directory using this style: - - - -render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh -render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh -render_getDirOutput.sh render.sh - - - - The output returned in response to the command (in this - case, the contents of the directory) is shown in this - style. - - - - - - prompt - - - A prompt, which is a computer's way of signifying that it - is ready for you to input something, is shown in this - style. Examples: - - - - - - $ - - - - - # - - - - - [centos@projects centos]$ - - - - - projects login: - - - - - - - - user input - - - Text that the user types, either on the command line or - into a text box on a GUI screen, is displayed in this - style. In the following example, - text is displayed in this style: To - boot your system into the text based installation program, - you must type in the text command - at the boot: prompt. - - - - - - replaceable - - - Text used in examples that is meant to be replaced with - data provided by the user is displayed in this style. In - the following example, - version-number is displayed in - this style: The directory for the kernel source is - /usr/src/kernels/version-number/, - where version-number is the - version and type of kernel installed on this system. - - - - - - Additionally, we use several different strategies to draw - your attention to certain pieces of information. In order of - urgency, these items are marked as a note, tip, important, - caution, or warning. For example: - - - Remember that Linux is case sensitive. In other words, a - rose is not a ROSE is not a rOsE. - - - - The directory /usr/share/doc/ contains - additional documentation for packages installed on your - system. - - - - If you modify the DHCP configuration file, the changes - do not take effect until you restart the DHCP daemon. - - - - Do not perform routine tasks as root — use a - regular user account unless you need to use the root account - for system administration tasks. - - - - Be careful to remove only the necessary partitions. - Removing other partitions could result in data loss or a - corrupted system environment. - - -
diff --git a/Manuals/Tcar-ug/Preface/feedback.docbook b/Manuals/Tcar-ug/Preface/feedback.docbook deleted file mode 100644 index b6f8334..0000000 --- a/Manuals/Tcar-ug/Preface/feedback.docbook +++ /dev/null @@ -1,14 +0,0 @@ -
- - Send In Your Feedback - - - If you find a bug in &TCAR; or this manual, we would like to - hear about it. To report bugs related to this manual, send an - e-mail to the centos-devel@centos.org mailing - list. When you write the bug report, take care of being - specific about the problem you are reporting on (e.g., where - it is, the section number, etc.) so we can found it easily. - - -
diff --git a/Manuals/Tcar-ug/Preface/history.docbook b/Manuals/Tcar-ug/Preface/history.docbook deleted file mode 100644 index 2197f1f..0000000 --- a/Manuals/Tcar-ug/Preface/history.docbook +++ /dev/null @@ -1,65 +0,0 @@ -
- History - - &TCAR; started at The CentOS Developers - Mailing List around 2008, on a discussion about how to - automate slide images used by Anaconda (&TCD; installer). In - such discussion, Ralph - Angenendt rose up his hand to ask —Do you have - something to show?—. - - - - To answer the question, Alain Reguera - Delgado suggested a bash script which combined SVG and - SED files in order to produce PNG images in different - languages —in conjunction with the proposition of - creating a Subversion repository where translations and image - production could be distributed inside &TCC;—. - - - - Karanbir - Singh considered the idea intresting and provided the - infrastructure necessary to support the effort. This way, - &TCAS; and &TCAR; were officially created and made world wide - available. In this configuration, users were able to register - themselves and administrators were able to assign access - rights to registered users inside &TCAR;, both using a web - interface. - - - - Once &TCAR; was available, Alain Reguera Delgado uploaded the - bash script used to produce the Anaconda - slides;See Ralph Angenendt documented it very - well;See and people started to download working - copies of &TCAR; to produce slide images in their own - languages.See the following Google - search. - - - - From this time on &TCAR; has been evolving into an automated - production environment where &TCC; can conceive &TCP; - corporate visual identity. - - - - The exact changes commited to &TCAR; through history can be - found in the repository - logs so you can know the real history about it. For - those of you who just want to get a glance of changes - committed, see . - - -
diff --git a/Manuals/Tcar-ug/Preface/overview.docbook b/Manuals/Tcar-ug/Preface/overview.docbook deleted file mode 100644 index 702dfdd..0000000 --- a/Manuals/Tcar-ug/Preface/overview.docbook +++ /dev/null @@ -1,119 +0,0 @@ -
- Overview - - - The corporations always have a corporate identity, even when - they don't take an intentional control over it. It is a choise - from the corporation to define how much control to take over - its identity. This kind of control is expensive and not all - corporations are able to maintain it. However, it is - necessary that, based on pragmatic facts, the corporation - assume an acceptable degree of compromise with its identity in - order to create a consistent idea of itself in a way that can - be progresively improved through time. - - - - During the years (2003-2009), we've seen a growing interest - inside &TCC; for helping on &TCP; development. Some people - seem to be very clear about what the project needs are and how - to maintain it being a very stable project, but others however - don't to get what &TCP; is (even it is explained time after - time) and sometimes decide to put their efforts in the wrong - direction making everything to be a waste of time and source - of distraction from what is really needed. - - - - &TCAR; phases the question What can I do for - &TCP;? by identifying different work lines you can - join in and providing automated production mechanisms that - complement one another according to each work line needs so - consistent results can be achieved inside a distributed - environment under version control. For example, consider an - environment where there are graphic designers to produce - images, documentors to produce documentation manuals (whose - can use images produced by graphic designers), programmers to - produce automation scripts (needed to standardize production - tasks) and translators to localize source files created by - graphic designers, documetors and programmers. Once such - environment has been implemented, it would be possible for - packagers to take localized images and localized documentation - from &TCAR; (through an automation script probably) to - rebrand/update the content of those packages inside &TCD; that - must include information specific to &TCP; itself (e.g., boot - loader, distribution installer, release notes, display - managers, release notes, web browsers default page, etc.). - - - - Most production tasks inside &TCAR; are focused on the files - needed to implement &TCP; corporate visual identity. - - Notice that, here, visual identity means everything - perceived through the human's visual sences (i.e., the - human eyes), but the corporate identity is a wider concept - that extends to all human senses (i.e., visibilty (eyes), - audition (ears), scent (nose), touch (fingers), and savour - (tongue)), not just that one related to visual aspects. - Nevertheless, we need to be consequent with the media - where &TCP; manifests its existence on, as described in - . - This includes everything from file edition - (e.g., text width, text indentation, line numbering, text - tabulation, etc.) up to how the web sites, distribution, and - industrial stuff (e.g., pullovers, caps, installation media, - etc.) look and feel. Notice that, more specific details like - typography, window design, icons, menu items, etc., inside - &TCD; are already covered by &TCP; upstream provider. In our - effort to be 100% binary compatible with the upstream provider - and also keeping maintainance low, we stand over those - specific details as much as possible assuming them as default. - However, if you feel brave enough (and prove your ability to - keep yourself being that way) it would be possible to open a - work line for you to maintain variants of such very specific - details inside &TCAR;. - - - - In addition to visual manifestations, there are also emotional - feelings and ethical behaviours that must be considered as - part of &TCP; corporate identity. A pleasant experience in - this area includes &TCWIKI;, specifically the way it was - conceived and administered. When the &TCWIKI; was published, - &TCP; published a list of needs with it so anyone could - contribute based on them. Not much time after that, the list - of tasks triggered some souls' motivations ruled by the good - will of initiating the translation of that content published - inside the wiki, redesigning its visual style, proposing the - TreeFlower theme for &TCD;, and reducing to zero the - contraditions of precoceived minds with respect, reason and - passion. As result of this experience, we found that &TCC; - posseses an incredible strong creative force, however, a long - path must be traveled before it can be focalized into the - right direction because: it isn't enough just telling what the - right direction is, it is also necessary to provide the - vehicles for &TCC; be able of moving through it. - - - - &TCAR; extends the feelings and ethicals behaviours from - &TCWIKI; to itself by identifying the visual manifestations - &TCP; is made of (i.e., tracing a direction) and allowing - people to develop them through standardized procedures inside - a colaborative environment (i.e., providing the vehicles). - - - - Finally, if you find yourself needing to do something for - &TCP; and &TCAR; isn't the place for it, be sure to define - what that something exactly is and also make it a community - effort so it can be validated as something useful to the - community itself. Otherwise, the effort would loose its - initial sense soon enough so as to be considered seriously. - Notice that the way these needs are described may take - different forms: they can be written and organized inside a - book, an article, or even a well documented program ;-). - - -