From 24257a72d8f1cfe52f305aae6eac03144fc5610e Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: Nov 30 2013 18:12:24 +0000 Subject: Update both directory and documentation structure. - Previously, there was one directory for each documentation article. This update organizes documentation in a single book of two parts. The first part is devoted to CentOS corporate identity and the second part to CentOS repository. The first part is a conceptual introduction to second part which is the implementation of conceptual ideas described in the first part. --- diff --git a/Corporate/Locales/en_US/corporate-colors.svgz.po b/Corporate/Locales/en_US/corporate-colors.svgz.po deleted file mode 100644 index af06926..0000000 --- a/Corporate/Locales/en_US/corporate-colors.svgz.po +++ /dev/null @@ -1,338 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate-colors.svgz 0.6\n" -"POT-Creation-Date: 2013-11-25 15:31-0500\n" -"PO-Revision-Date: 2013-11-25 15:31-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "image/svg+xml" -msgstr "image/svg+xml" - -#, no-wrap -msgid "1" -msgstr "1" - -#, no-wrap -msgid "2" -msgstr "2" - -#, no-wrap -msgid "3" -msgstr "3" - -#, no-wrap -msgid "4" -msgstr "4" - -#, no-wrap -msgid "5" -msgstr "5" - -#, no-wrap -msgid "6" -msgstr "6" - -#, no-wrap -msgid "7" -msgstr "7" - -#, no-wrap -msgid "8" -msgstr "8" - -#, no-wrap -msgid "9" -msgstr "9" - -#, no-wrap -msgid "10" -msgstr "10" - -#, no-wrap -msgid "11" -msgstr "11" - -#, no-wrap -msgid "12" -msgstr "12" - -#, no-wrap -msgid "13" -msgstr "13" - -#, no-wrap -msgid "14" -msgstr "14" - -#, no-wrap -msgid "15" -msgstr "15" - -#, no-wrap -msgid "16" -msgstr "16" - -#, no-wrap -msgid "17" -msgstr "17" - -#, no-wrap -msgid "18" -msgstr "18" - -#, no-wrap -msgid "19" -msgstr "19" - -#, no-wrap -msgid "20" -msgstr "20" - -#, no-wrap -msgid "21" -msgstr "21" - -#, no-wrap -msgid "22" -msgstr "22" - -#, no-wrap -msgid "23" -msgstr "23" - -#, no-wrap -msgid "24" -msgstr "24" - -#, no-wrap -msgid "25" -msgstr "25" - -#, no-wrap -msgid "26" -msgstr "26" - -#, no-wrap -msgid "27" -msgstr "27" - -#, no-wrap -msgid "28" -msgstr "28" - -#, no-wrap -msgid "29" -msgstr "29" - -#, no-wrap -msgid "30" -msgstr "30" - -#, no-wrap -msgid "31" -msgstr "31" - -#, no-wrap -msgid "32" -msgstr "32" - -#, no-wrap -msgid "33" -msgstr "33" - -#, no-wrap -msgid "34" -msgstr "34" - -#, no-wrap -msgid "35" -msgstr "35" - -#, no-wrap -msgid "36" -msgstr "36" - -#, no-wrap -msgid "37" -msgstr "37" - -#, no-wrap -msgid "38" -msgstr "38" - -#, no-wrap -msgid "39" -msgstr "39" - -#, no-wrap -msgid "0" -msgstr "0" - -#, no-wrap -msgid "0 = ffffffff" -msgstr "0 = ffffffff" - -#, no-wrap -msgid "1 = eec73eff " -msgstr "1 = eec73eff " - -#, no-wrap -msgid "2 = f0a513ff" -msgstr "2 = f0a513ff" - -#, no-wrap -msgid "3 = fb8b00ff " -msgstr "3 = fb8b00ff " - -#, no-wrap -msgid "4 = f44800ff" -msgstr "4 = f44800ff" - -#, no-wrap -msgid "5 = f44800ff " -msgstr "5 = f44800ff " - -#, no-wrap -msgid "6 = fd3301ff" -msgstr "6 = fd3301ff" - -#, no-wrap -msgid "7 = d40000ff" -msgstr "7 = d40000ff" - -#, no-wrap -msgid "8 = 980101ff" -msgstr "8 = 980101ff" - -#, no-wrap -msgid "9 = fdd99bff" -msgstr "9 = fdd99bff" - -#, no-wrap -msgid "10 = 336699ff" -msgstr "10 = 336699ff" - -#, no-wrap -msgid "11 = 003366ff" -msgstr "11 = 003366ff" - -#, no-wrap -msgid "12 = b3defdff" -msgstr "12 = b3defdff" - -#, no-wrap -msgid "13 = 0197fdff" -msgstr "13 = 0197fdff" - -#, no-wrap -msgid "14 = 0169c9ff" -msgstr "14 = 0169c9ff" - -#, no-wrap -msgid "15 = 002b3dff" -msgstr "15 = 002b3dff" - -#, no-wrap -msgid "16 = ad7fa8ff" -msgstr "16 = ad7fa8ff" - -#, no-wrap -msgid "17 = 75507bff" -msgstr "17 = 75507bff" - -#, no-wrap -msgid "18 = 5c3566ff" -msgstr "18 = 5c3566ff" - -#, no-wrap -msgid "19 = eeeeeeff" -msgstr "19 = eeeeeeff" - -#, no-wrap -msgid "20 = ffff99ff" -msgstr "20 = ffff99ff" - -#, no-wrap -msgid "21 = ffff00ff " -msgstr "21 = ffff00ff " - -#, no-wrap -msgid "22 = fdca01ff " -msgstr "22 = fdca01ff " - -#, no-wrap -msgid "23 = 986601ff " -msgstr "23 = 986601ff " - -#, no-wrap -msgid "24 = ffff99ff " -msgstr "24 = ffff99ff " - -#, no-wrap -msgid "25 = 816647ff " -msgstr "25 = 816647ff " - -#, no-wrap -msgid "26 = 565248ff " -msgstr "26 = 565248ff " - -#, no-wrap -msgid "27 = aacceeff " -msgstr "27 = aacceeff " - -#, no-wrap -msgid "28 = 6699ccff" -msgstr "28 = 6699ccff" - -#, no-wrap -msgid "29 = d9bb7aff" -msgstr "29 = d9bb7aff" - -#, no-wrap -msgid "30 = ccff99ff " -msgstr "30 = ccff99ff " - -#, no-wrap -msgid "31 = 98fc66ff " -msgstr "31 = 98fc66ff " - -#, no-wrap -msgid "32 = 339900ff " -msgstr "32 = 339900ff " - -#, no-wrap -msgid "33 = 015a01ff" -msgstr "33 = 015a01ff" - -#, no-wrap -msgid "34 = 013397ff" -msgstr "34 = 013397ff" - -#, no-wrap -msgid "35 = aaaaaaff" -msgstr "35 = aaaaaaff" - -#, no-wrap -msgid "36 = 888888ff" -msgstr "36 = 888888ff" - -#, no-wrap -msgid "37 = 666666ff" -msgstr "37 = 666666ff" - -#, no-wrap -msgid "38 = 333333ff" -msgstr "38 = 333333ff" - -#, no-wrap -msgid "39 = 000000ff" -msgstr "39 = 000000ff" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Corporate/Locales/en_US/corporate-fonts.svgz.po b/Corporate/Locales/en_US/corporate-fonts.svgz.po deleted file mode 100644 index 8547f34..0000000 --- a/Corporate/Locales/en_US/corporate-fonts.svgz.po +++ /dev/null @@ -1,77 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate-fonts.svgz 0.6\n" -"POT-Creation-Date: 2013-11-26 22:08-0500\n" -"PO-Revision-Date: 2013-11-26 22:08-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "image/svg+xml" -msgstr "image/svg+xml" - -msgid "denmark.svg" -msgstr "denmark.svg" - -msgid "2011-07-23" -msgstr "2011-07-23" - -msgid "The CentOS Artwork SIG" -msgstr "The CentOS Artwork SIG" - -msgid "" -"https://projects.centos.org/svn/artwork/trunk/Identity/Models/Manuals/Fonts/" -"denmark.svg" -msgstr "" -"https://projects.centos.org/svn/artwork/trunk/Identity/Models/Manuals/Fonts/" -"denmark.svg" - -msgid "en_US" -msgstr "en_US" - -msgid "Identity" -msgstr "Identity" - -msgid "Models" -msgstr "Models" - -msgid "Manuals" -msgstr "Manuals" - -msgid "Fonts" -msgstr "Fonts" - -#, no-wrap -msgid "URW Gothic L" -msgstr "URW Gothic L" - -#, no-wrap -msgid "Aa" -msgstr "Aa" - -#, no-wrap -msgid "Denmark" -msgstr "Denmark" - -#, no-wrap -msgid "DejaVu LGC Sans" -msgstr "DejaVu LGC Sans" - -#, no-wrap -msgid "Regular" -msgstr "Regular" - -#, no-wrap -msgid "Bold" -msgstr "Bold" - -#, no-wrap -msgid "Oblique" -msgstr "Oblique" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Corporate/Locales/en_US/corporate-logo-howto.svgz.po b/Corporate/Locales/en_US/corporate-logo-howto.svgz.po deleted file mode 100644 index 4e19922..0000000 --- a/Corporate/Locales/en_US/corporate-logo-howto.svgz.po +++ /dev/null @@ -1,100 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate-logo-howto.svgz 0.6\n" -"POT-Creation-Date: 2013-11-26 22:06-0500\n" -"PO-Revision-Date: 2013-11-26 22:06-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "image/svg+xml" -msgstr "image/svg+xml" - -msgid "centos.svg" -msgstr "centos.svg" - -msgid "2011-08-02" -msgstr "2011-08-02" - -msgid "The CentOS Project" -msgstr "The CentOS Project" - -msgid "" -"https://projects.centos.org/svn/artwork/trunk/Identity/Models/Manuals/Brands/" -"Logos/centos.svg" -msgstr "" -"https://projects.centos.org/svn/artwork/trunk/Identity/Models/Manuals/Brands/" -"Logos/centos.svg" - -msgid "en_US" -msgstr "en_US" - -msgid "Identity" -msgstr "Identity" - -msgid "Models" -msgstr "Models" - -msgid "Manuals" -msgstr "Manuals" - -msgid "Brands" -msgstr "Brands" - -msgid "Logos" -msgstr "Logos" - -#, no-wrap -msgid "D" -msgstr "D" - -#, no-wrap -msgid "Content Area" -msgstr "Content Area" - -#, no-wrap -msgid "Protection Area" -msgstr "Protection Area" - -#, no-wrap -msgid "B = C % 34" -msgstr "B = C % 34" - -#, no-wrap -msgid "A = B" -msgstr "A = B" - -#, no-wrap -msgid "D = C % 16" -msgstr "D = C % 16" - -#, no-wrap -msgid "E = B * 2" -msgstr "E = B * 2" - -#, no-wrap -msgid "C" -msgstr "C" - -#, no-wrap -msgid "B" -msgstr "B" - -#, no-wrap -msgid "A" -msgstr "A" - -#, no-wrap -msgid "E" -msgstr "E" - -#, no-wrap -msgid "6" -msgstr "6" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Corporate/Locales/en_US/corporate-symbol-howto-1of4.svgz.po b/Corporate/Locales/en_US/corporate-symbol-howto-1of4.svgz.po deleted file mode 100644 index 2f78c53..0000000 --- a/Corporate/Locales/en_US/corporate-symbol-howto-1of4.svgz.po +++ /dev/null @@ -1,76 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate-symbol-howto-1of4.svgz 0.6\n" -"POT-Creation-Date: 2013-11-26 22:06-0500\n" -"PO-Revision-Date: 2013-11-26 22:06-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "image/svg+xml" -msgstr "image/svg+xml" - -msgid "figure-1.svg" -msgstr "figure-1.svg" - -msgid "2011-04-18" -msgstr "2011-04-18" - -msgid "The CentOS Project" -msgstr "The CentOS Project" - -msgid "http://www.centos.org/" -msgstr "http://www.centos.org/" - -msgid "en_US" -msgstr "en_US" - -msgid "Identity" -msgstr "Identity" - -msgid "Models" -msgstr "Models" - -msgid "Manual" -msgstr "Manual" - -msgid "Brands" -msgstr "Brands" - -msgid "Symbols" -msgstr "Symbols" - -#, no-wrap -msgid "A" -msgstr "A" - -#, no-wrap -msgid "B" -msgstr "B" - -#, no-wrap -msgid "A = 32mm" -msgstr "A = 32mm" - -#, no-wrap -msgid "B = 2mm" -msgstr "B = 2mm" - -#, no-wrap -msgid "A = 45mm" -msgstr "A = 45mm" - -#, no-wrap -msgid "A = 15mm" -msgstr "A = 15mm" - -#, no-wrap -msgid "B = 1mm" -msgstr "B = 1mm" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Corporate/Locales/en_US/corporate-symbol-howto-2of4.svgz.po b/Corporate/Locales/en_US/corporate-symbol-howto-2of4.svgz.po deleted file mode 100644 index 175e4ce..0000000 --- a/Corporate/Locales/en_US/corporate-symbol-howto-2of4.svgz.po +++ /dev/null @@ -1,80 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate-symbol-howto-2of4.svgz 0.6\n" -"POT-Creation-Date: 2013-11-26 22:06-0500\n" -"PO-Revision-Date: 2013-11-26 22:06-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "image/svg+xml" -msgstr "image/svg+xml" - -msgid "figure-2.svg" -msgstr "figure-2.svg" - -msgid "2011-04-18" -msgstr "2011-04-18" - -msgid "The CentOS Project" -msgstr "The CentOS Project" - -msgid "http://www.centos.org/" -msgstr "http://www.centos.org/" - -msgid "en_US" -msgstr "en_US" - -msgid "Identity" -msgstr "Identity" - -msgid "Models" -msgstr "Models" - -msgid "Manual" -msgstr "Manual" - -msgid "Brands" -msgstr "Brands" - -msgid "Symbols" -msgstr "Symbols" - -#, no-wrap -msgid "3. Fill 90° squares with color." -msgstr "3. Fill 90° squares with color." - -#, no-wrap -msgid "1. Create 90° square set." -msgstr "1. Create 90° square set." - -#, no-wrap -msgid "2. Create 45° square set." -msgstr "2. Create 45° square set." - -#, no-wrap -msgid "4. Align both 90° and 45° square sets." -msgstr "4. Align both 90° and 45° square sets." - -#, no-wrap -msgid "9CCD2A" -msgstr "9CCD2A" - -#, no-wrap -msgid "932279" -msgstr "932279" - -#, no-wrap -msgid "EFA724" -msgstr "EFA724" - -#, no-wrap -msgid "262577" -msgstr "262577" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Corporate/Locales/en_US/corporate-symbol-howto-3of4.svgz.po b/Corporate/Locales/en_US/corporate-symbol-howto-3of4.svgz.po deleted file mode 100644 index cb099ab..0000000 --- a/Corporate/Locales/en_US/corporate-symbol-howto-3of4.svgz.po +++ /dev/null @@ -1,80 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate-symbol-howto-3of4.svgz 0.6\n" -"POT-Creation-Date: 2013-11-26 22:06-0500\n" -"PO-Revision-Date: 2013-11-26 22:06-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "image/svg+xml" -msgstr "image/svg+xml" - -msgid "figure-3.svg" -msgstr "figure-3.svg" - -msgid "2011-04-18" -msgstr "2011-04-18" - -msgid "The CentOS Project" -msgstr "The CentOS Project" - -msgid "http://www.centos.org/" -msgstr "http://www.centos.org/" - -msgid "en_US" -msgstr "en_US" - -msgid "Identity" -msgstr "Identity" - -msgid "Models" -msgstr "Models" - -msgid "Manual" -msgstr "Manual" - -msgid "Brands" -msgstr "Brands" - -msgid "Symbols" -msgstr "Symbols" - -#, no-wrap -msgid "5. Create semi-transparent guide." -msgstr "5. Create semi-transparent guide." - -#, no-wrap -msgid "8. Set arrows color information." -msgstr "8. Set arrows color information." - -#, no-wrap -msgid "6. Draw arrow over the guide." -msgstr "6. Draw arrow over the guide." - -#, no-wrap -msgid "7. Duplicate and rotate arrows." -msgstr "7. Duplicate and rotate arrows." - -#, no-wrap -msgid "9CCD2A" -msgstr "9CCD2A" - -#, no-wrap -msgid "932279" -msgstr "932279" - -#, no-wrap -msgid "EFA724" -msgstr "EFA724" - -#, no-wrap -msgid "262577" -msgstr "262577" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Corporate/Locales/en_US/corporate-symbol-howto-4of4.svgz.po b/Corporate/Locales/en_US/corporate-symbol-howto-4of4.svgz.po deleted file mode 100644 index e03dbd3..0000000 --- a/Corporate/Locales/en_US/corporate-symbol-howto-4of4.svgz.po +++ /dev/null @@ -1,64 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate-symbol-howto-4of4.svgz 0.6\n" -"POT-Creation-Date: 2013-11-26 22:06-0500\n" -"PO-Revision-Date: 2013-11-26 22:06-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "image/svg+xml" -msgstr "image/svg+xml" - -msgid "figure-4.svg" -msgstr "figure-4.svg" - -msgid "2011-04-18" -msgstr "2011-04-18" - -msgid "The CentOS Project" -msgstr "The CentOS Project" - -msgid "http://www.centos.org/" -msgstr "http://www.centos.org/" - -msgid "en_US" -msgstr "en_US" - -msgid "Identity" -msgstr "Identity" - -msgid "Models" -msgstr "Models" - -msgid "Manual" -msgstr "Manual" - -msgid "Brands" -msgstr "Brands" - -msgid "Symbols" -msgstr "Symbols" - -#, no-wrap -msgid "9. The final squares set." -msgstr "9. The final squares set." - -#, no-wrap -msgid "12. Move arrow set lower to bottom." -msgstr "12. Move arrow set lower to bottom." - -#, no-wrap -msgid "10. The final arrows set." -msgstr "10. The final arrows set." - -#, no-wrap -msgid "11. Align squares and arrows final sets." -msgstr "11. Align squares and arrows final sets." - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Corporate/Locales/en_US/corporate-themes.svgz.po b/Corporate/Locales/en_US/corporate-themes.svgz.po deleted file mode 100644 index 4d414fc..0000000 --- a/Corporate/Locales/en_US/corporate-themes.svgz.po +++ /dev/null @@ -1,50 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate-themes.svgz 0.6\n" -"POT-Creation-Date: 2013-11-25 15:32-0500\n" -"PO-Revision-Date: 2013-11-25 15:32-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "image/svg+xml" -msgstr "image/svg+xml" - -#, no-wrap -msgid "PO" -msgstr "PO" - -#, no-wrap -msgid "FILES" -msgstr "FILES" - -#, no-wrap -msgid "ARTISTIC MOTIFS" -msgstr "ARTISTIC MOTIFS" - -#, no-wrap -msgid "(PNG FILES)" -msgstr "(PNG FILES)" - -#, no-wrap -msgid "SVGZ" -msgstr "SVGZ" - -#, no-wrap -msgid "FINAL IMAGES" -msgstr "FINAL IMAGES" - -#, no-wrap -msgid "${LANG}" -msgstr "${LANG}" - -#, no-wrap -msgid "AUTOMATION SCRIPTS" -msgstr "AUTOMATION SCRIPTS" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Corporate/Locales/en_US/corporate.asciidoc.po b/Corporate/Locales/en_US/corporate.asciidoc.po deleted file mode 100644 index b223b5a..0000000 --- a/Corporate/Locales/en_US/corporate.asciidoc.po +++ /dev/null @@ -1,868 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate.asciidoc 0.6\n" -"POT-Creation-Date: 2013-11-26 22:11-0500\n" -"PO-Revision-Date: 2013-11-26 22:11-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -msgid "@@image: 'corporate.png'; md5=74237f14692aec6fe7c2818dc165c565" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -msgid "" -"@@image: 'corporate-logo-howto.png'; md5=62edef37b7167fc07cbbd78789f2d6ea" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -msgid "@@image: 'corporate-fonts.png'; md5=6817553208dfeabfe31081bb95073731" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -msgid "" -"@@image: '../corporate-colors.png'; md5=66b784d031893eb05fbbf1b514cea60d" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -msgid "" -"@@image: '../corporate-clothes-head.png'; " -"md5=9225ce1a9deceb35a95dee726efcce40" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -msgid "" -"@@image: '../corporate-clothes-torso.png'; " -"md5=1f3991d8b08b9a03d4819e1c0803a5a8" -msgstr "" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -msgid "@@image: 'corporate-themes.png'; md5=cd1fe57ab37ee9857780087149cb6b5f" -msgstr "" - -msgid "The CentOS Project Corporate Visual Identity" -msgstr "The CentOS Project Corporate Visual Identity" - -msgid "Jul 2013" -msgstr "Jul 2013" - -msgid "Alain" -msgstr "Alain" - -msgid "Reguera" -msgstr "Reguera" - -msgid "Delgado" -msgstr "Delgado" - -msgid "al@centos.org.cu" -msgstr "al@centos.org.cu" - -msgid "ARD" -msgstr "ARD" - -msgid "1.0" -msgstr "1.0" - -msgid "" -"The CentOS Project Corporate Identity is the “persona” of the organization " -"known as The CentOS Project. The CentOS Project Corporate Identity plays a " -"significant role in the way The CentOS Project, as organization, presents " -"itself to both internal and external stakeholders. In general terms, The " -"CentOS Project Corporate Identity expresses the values and ambitions of The " -"CentOS Project organization, its business, and its characteristics." -msgstr "" -"The CentOS Project Corporate Identity is the “persona” of the organization " -"known as The CentOS Project. The CentOS Project Corporate Identity plays a " -"significant role in the way The CentOS Project, as organization, presents " -"itself to both internal and external stakeholders. In general terms, The " -"CentOS Project Corporate Identity expresses the values and ambitions of The " -"CentOS Project organization, its business, and its characteristics." - -#, fuzzy -msgid "" -"The CentOS Project Corporate Identity provides visibility, recognizability, " -"reputation, structure and identification to The CentOS Project organization " -"by means of Corporate Design, Corporate Communication, and Corporate " -"Behavior." -msgstr "" -"The CentOS Project Corporate Identity provides visibility, recognizability, " -"reputation, structure and identification to The CentOS Project organization " -"by means of Corporate Design, Corporate Communication, and Corporate " -"Behaviour." - -msgid "The CentOS Project Corporate Identity" -msgstr "The CentOS Project Corporate Identity" - -msgid "corporate.png" -msgstr "corporate.png" - -msgid "Corporate Mission" -msgstr "Corporate Mission" - -msgid "" -"The CentOS Project exists to produce The CentOS Distribution, an Enterprise-" -"class Linux Distribution derived from sources freely provided to the public " -"by a prominent North American Enterprise Linux vendor. The CentOS " -"Distribution conforms fully with the upstream vendors redistribution policy " -"and aims to be 100% binary compatible. (The CentOS Distribution mainly " -"changes packages to remove upstream vendor branding and artwork.)." -msgstr "" -"The CentOS Project exists to produce The CentOS Distribution, an Enterprise-" -"class Linux Distribution derived from sources freely provided to the public " -"by a prominent North American Enterprise Linux vendor. The CentOS " -"Distribution conforms fully with the upstream vendors redistribution policy " -"and aims to be 100% binary compatible. (The CentOS Distribution mainly " -"changes packages to remove upstream vendor branding and artwork.)." - -msgid "" -"The CentOS Distribution is developed by a small but growing team of core " -"developers. In turn the core developers are supported by an active user " -"community including system administrators, network administrators, " -"enterprise users, managers, core Linux contributors and Linux enthusiasts " -"from around the world." -msgstr "" -"The CentOS Distribution is developed by a small but growing team of core " -"developers. In turn the core developers are supported by an active user " -"community including system administrators, network administrators, " -"enterprise users, managers, core Linux contributors and Linux enthusiasts " -"from around the world." - -msgid "" -"The CentOS Distribution has numerous advantages including: an active and " -"growing user community, quickly rebuilt, tested, and QA'ed errata packages, " -"an extensive mirror network, developers who are contactable and responsive " -"of a reliable Enterprise-class Linux Distribution, multiple free support " -"avenues including a Wiki, " -"IRC " -"Chat, Email Lists, " -"Forums, and a " -"dynamic FAQ." -msgstr "" -"The CentOS Distribution has numerous advantages including: an active and " -"growing user community, quickly rebuilt, tested, and QA'ed errata packages, " -"an extensive mirror network, developers who are contactable and responsive " -"of a reliable Enterprise-class Linux Distribution, multiple free support " -"avenues including a Wiki, " -"IRC " -"Chat, Email Lists, " -"Forums, and a " -"dynamic FAQ." - -msgid "Corporate Graphic Design" -msgstr "Corporate Graphic Design" - -#, fuzzy -msgid "" -"Corporate graphic design is focused on the presentation of corporate " -"messages with efficiency and efficacy. Corporate graphic design is a " -"cornerstone of corporate visual identity. When the organization doesn't take " -"control over the corporate messages it produces, the organization is letting " -"that area of its identity to the unknown and the result might be good or not " -"so good, it is hard to know. Even the organization doesn't take control over " -"its corporate messages they are always talking about the organization. " -"Taking control of corporate messages presentation is a decision the " -"organization needs to take by itself, based on its need of better describe " -"what it is. To work out the corporate graphic design of an organization it " -"is required to identify which are the visual manifestations the organization " -"reflects its existence on." -msgstr "" -"When the organization doesn't take control over the corporate messages it " -"produces, the organization is letting that area of its identity to the " -"unknown and the results might be good or not so good, it is hard to know. " -"The issue to see here is that even the organization doesn't take control " -"over its corporate messages, they are always talking about the organization. " -"Taking control of corporate messages is a decision the organization needs to " -"take by itself, based on its need of better describe what it is." - -msgid "" -"The CentOS Artwork SIG has identified the following visual manifestations " -"for The CentOS Project organization:" -msgstr "" - -msgid "GNU/Linux Distribution — to control the operating system appearance." -msgstr "" - -msgid "Web environment — to control the web applications appearance." -msgstr "" - -msgid "Promotion — to control the industrial media appearance." -msgstr "" - -#, fuzzy -msgid "Corporate Brand" -msgstr "Corporate Behaviour" - -msgid "" -"The corporate brand is the graphical identification of an organization. The " -"CentOS Artwork SIG uses The CentOS Brand to connect all the visual " -"manifestations The CentOS Project is made of (e.g., GNU/Linux Distributions, " -"Websites, Stationery, etc.) and, this way, it provides visual recognition " -"among similar projects available on the Internet." -msgstr "" - -msgid "" -"The CentOS Brand is composed of a graphical component known as The CentOS " -"Symbol and a typographical component known as The CentOS Type. When The " -"CentOS Symbol and The CentOS Type are put together, they create what we know " -"as The CentOS Logo. All the components that make The CentOS Brand can be " -"used together or separately, considering that, in hierarchy order, The " -"CentOS Logo is rather preferred than The CentOS Symbol, as well as The " -"CentOS Symbol is rather preferred than The CentOS Type alone." -msgstr "" - -#, fuzzy -msgid "corporate-logo-howto.png" -msgstr "corporate.png" - -msgid "" -"The CentOS Brand must be exactly the same every time it is printed out, no " -"matter what the medium is. A route to reproduce The CentOS Brand this way " -"must be used so as to avoid reproduction mistakes of any kind when final " -"images are branded with it. To prevent such mistakes, The CentOS Artwork SIG " -"uses configuration files and the render " -"module of centos-art.sh script to " -"produce PNG brand images of different sizes and colors that can be combined " -"later with other images instead of manipulating The CentOS Brand in SVG " -"format inside each different design model that requires it. This also grants " -"a single point of change for all brands already applied on final images. In " -"this environment, if you make a change to brands SVG files, they will be " -"propagated to all final images the next time you render them." -msgstr "" - -msgid "" -"The CentOS Symbol is the graphical part of The CentOS Logo. As The CentOS " -"Logo, The CentOS Symbol is used to “brand” images produced by The CentOS " -"Project and provide visual connection between images so they can be " -"monolithically recognized as part of The CentOS Project. The CentOS Symbol " -"must be exactly the same every time it is printed out and a route to " -"reproduce it in such a way must be available so as to avoid reproduction " -"mistakes when images are branded with it." -msgstr "" - -msgid "" -"The CentOS Type is the typographical part of The CentOS Logo. The CentOS " -"Type is used to “brand” images produce by The CentOS Project and provide " -"visual connection between images so they can be monolithically recognized as " -"part of The CentOS Project. The CentOS Type alone provides less recognition " -"than The CentOS Logo and The CentOS Symbol. Frequently, The CentOS Type is " -"used to advert the major release of CentOS Distribution on the first images " -"shown as part of Distribution installation process. The CentOS Symbol and " -"any release information printed out with it must have exactly the same " -"proportions every time they are printed out." -msgstr "" - -#, fuzzy -msgid "Corporate Fonts" -msgstr "Corporate Mission" - -msgid "" -"The CentOS Artwork SIG uses the following font files in their corporate " -"graphic designs:" -msgstr "" - -#, fuzzy -msgid "corporate-fonts.png" -msgstr "corporate.png" - -#, fuzzy -msgid "Corporate Colors" -msgstr "Corporate Behaviour" - -msgid "" -"In addition to colors used in The CentOS Symbol (9ccd2aff, 932279ff, " -"262577ff, efa724ff) and The CentOS Default Background Color (204c8dff), The " -"CentOS Artwork SIG uses the following colors in their corporate graphic " -"designs:" -msgstr "" - -#, fuzzy -msgid "corporate-colors.png" -msgstr "corporate.png" - -msgid "" -"Artistic motifs have not any limitation in the number of colors used. If you " -"are a graphic designer creating artistic motifs for The CentOS Project, feel " -"free to take your creativeness at its limit by creating color-full artistic " -"motifs. For final bootup images which require a reduced number of colors, " -"create palette of colors for them with the appropriate number of colors and " -"let the render module of centos-art.sh script to do the rest." -msgstr "" - -#, fuzzy -msgid "Corporate Clothes" -msgstr "Corporate Structure" - -msgid "" -"The CentOS clothes identify the The CentOS Project representative people at " -"public presentations." -msgstr "" - -#, fuzzy -msgid "corporate-clothes-cap.png" -msgstr "corporate.png" - -#, fuzzy -msgid "corporate-clothes-shirt.png" -msgstr "corporate.png" - -#, fuzzy -msgid "Corporate Themes" -msgstr "Corporate Mission" - -msgid "" -"The CentOS themes organize visual styles for all the visual manifestation " -"The CentOS Project is made of. In order to automate the process of rendering " -"images based on customizable patterns, themes have been divided into “design " -"models”, “localization files,” and “artistic motifs.”" -msgstr "" - -#, fuzzy -msgid "corporate-themes.png" -msgstr "corporate.png" - -#, fuzzy -msgid "Design Models" -msgstr "The CentOS Web" - -msgid "" -"Design models are compressed SVG files created with Inkscape. They describe " -"the image files used to implement the CentOS project visual manifestations. " -"For example, in the specific case of CentOS distribution, each final image " -"you want to re-brand has a design model associated used to set the final " -"image dimensions, whether or not it has round borders, and what background " -"to use on it. Design models are created once and rarely modified through " -"time. They are only modified if the visual manifestation they refer to " -"changes or needs to be tuned up." -msgstr "" - -msgid "Localization Files" -msgstr "" - -msgid "" -"Localization files provide localization for messages inside design models. " -"For example, if you decide to use slide images in CentOS installer, you need " -"to create one design model for each slide image you want to produce in " -"English language. Then, using locale " -"module, you create PO files for each design model you have. PO files are " -"created using the current language information of your terminal (e.g., see " -"value of LANG variable). Then you use the locale module again to edit the PO files and provide " -"string translations from English to your preferred language. Once " -"translations are on the PO files, you use the render module to produce images for your preferred language, " -"based on the artistic motif you initiate rendition for and the related " -"design models set in the rendition configuration file." -msgstr "" - -msgid "Artistic Motifs" -msgstr "" - -msgid "" -"Artistic motifs are PNG images holding the look and feel of each design " -"model available. One important characteristic of artistic motifs is " -"preserving one unique visual style for all the PNG images they are made of. " -"Artistic motifs aren't limited in number. It is possible to have several " -"artistic motifs and produce final images for all of them using one single " -"set of design models. Artistic motifs give plenty of room for graphic " -"designers' creativeness. As convention, artistic motifs are conceived " -"without any specific brand information on them. The brand information is set " -"using brand images later, when final images are produced." -msgstr "" - -msgid "Corporate Communication" -msgstr "Corporate Communication" - -msgid "" -"The CentOS Project corporate communication is focused on the effective " -"propagation of corporate messages. Propagation of corporate messages is " -"closely related to the media the organization uses as vehicle to distribute " -"its corporate messages." -msgstr "" -"The CentOS Project corporate communication is focused on the effective " -"propagation of corporate messages. Propagation of corporate messages is " -"closely related to the media the organization uses as vehicle to distribute " -"its corporate messages." - -msgid "" -"The CentOS Project corporate communication takes place through the following " -"visual manifestations:" -msgstr "" -"The CentOS Project corporate communication takes place through the following " -"visual manifestations:" - -msgid "The CentOS Distribution" -msgstr "The CentOS Distribution" - -msgid "" -"This visual manifestation communicates its existence through software " -"packages. There are packages that make a remarkable use of images, packages " -"that make a moderate use of images, and packages that don't use images at " -"all. This visual manifestation is focused on providing The CentOS Project " -"images required by software packages that do use images in a remarkable way, " -"specially those holding the upstream brand (e.g., anaconda, grub, syslinux, " -"gdm, kdebase)." -msgstr "" -"This visual manifestation communicates its existence through software " -"packages. There are packages that make a remarkable use of images, packages " -"that make a moderate use of images, and packages that don't use images at " -"all. This visual manifestation is focused on providing The CentOS Project " -"images required by software packages that do use images in a remarkable way, " -"specially those holding the upstream brand (e.g., anaconda, grub, syslinux, " -"gdm, kdebase)." - -#, fuzzy -msgid "" -"The Community Enterprise Operating System itself (communicates the essence " -"of The CentOS Project existence.)." -msgstr "" -"The Community Enterprise Operating System itself (communicates the essense " -"of The CentOS Project existence.)." - -msgid "" -"Release Schema (Lifetime) and all the stuff related (e.g., Release Notes, " -"Documentation, Erratas, etc.)." -msgstr "" -"Release Schema (Lifetime) and all the stuff related (e.g., Release Notes, " -"Documentation, Erratas, etc.)." - -msgid "The CentOS Web" -msgstr "The CentOS Web" - -msgid "" -"This visual manifestation communicates its existence through web " -"applications. These web applications are free software and come from " -"different providers which distribute their work with predefined visual " -"styles. Frequently, these predefined visual styles have no visual relation " -"among themselves and introduce some visual contradictions when they all are " -"put together. Removing these visual contradictions is object of work for " -"this visual manifestation." -msgstr "" -"This visual manifestation communicates its existence through web " -"applications. These web applications are free software and come from " -"different providers which distribute their work with predefined visual " -"styles. Frequently, these predefined visual styles have no visual relation " -"among themselves and introduce some visual contradictions when they all are " -"put together. Removing these visual contradictions is object of work for " -"this visual manifestation." - -msgid "The CentOS Chat." -msgstr "The CentOS Chat." - -msgid "The CentOS Mailing Lists." -msgstr "The CentOS Mailing Lists." - -msgid "The CentOS Forums." -msgstr "The CentOS Forums." - -msgid "The CentOS Wiki." -msgstr "The CentOS Wiki." - -msgid "Special Interest Groups (SIGs)." -msgstr "Special Interest Groups (SIGs)." - -msgid "Social Events, Interviews, Conferences, etc." -msgstr "Social Events, Interviews, Conferences, etc." - -msgid "" -"The extensive network of mirrors available for downloading ISO files as well " -"as RPMs and SRPMs used to build them up in different architectures." -msgstr "" -"The extensive network of mirrors available for downloading ISO files as well " -"as RPMs and SRPMs used to build them up in different architectures." - -msgid "The CentOS Showroom" -msgstr "The CentOS Showroom" - -msgid "" -"This visual manifestation communicates its existence through production of " -"industrial objects carrying The CentOS Brand. These branded objects are " -"directed to be distributed on social events and/or shops. They provide a way " -"of promotion and commercialization that may help to reduce The CentOS " -"Project expenses (e.g., electrical power, hosting, servers, full-time-" -"developers, etc.), in a similar way as donations may do." -msgstr "" -"This visual manifestation communicates its existence through production of " -"industrial objects carrying The CentOS Brand. These branded objects are " -"directed to be distributed on social events and/or shops. They provide a way " -"of promotion and commercialization that may help to reduce The CentOS " -"Project expenses (e.g., electrical power, hosting, servers, full-time-" -"developers, etc.), in a similar way as donations may do." - -msgid "Stationery (e.g., Posters, Stickers, CD Lables and Sleeves)." -msgstr "Stationery (e.g., Posters, Stickers, CD Lables and Sleeves)." - -msgid "Clothes (e.g., Shirts, T-shirts, Pullovers, Caps)." -msgstr "Clothes (e.g., Shirts, T-shirts, Pullovers, Caps)." - -#, fuzzy -msgid "Installation media (e.g., CDs, DVD, Pen-drives)." -msgstr "Installation media (e.g., CDs, DVD, Pendrives)." - -#, fuzzy -msgid "Corporate Behavior" -msgstr "Corporate Behaviour" - -#, fuzzy -msgid "" -"The CentOS Project corporate behavior is focused on the effective " -"interaction of each member involved in the organization (e.g., core " -"developers, community members, etc.). It is related to ethics and politics " -"used to do the things inside the organization. It is related to the sense of " -"direction chosen by the organization and the way the organization projects " -"itself to achieve it." -msgstr "" -"The CentOS Project corporate behaviour is focused on the effective " -"interaction of each member involved in the organization (e.g., core " -"developers, community members, etc.). It is related to ethics and politics " -"used to do the things inside the organization. It is related to the sense of " -"direction chosen by the organization and they way the organization projects " -"itself to achieve it." - -msgid "" -"The CentOS Project corporate behavior is based on a meritocracy (the more " -"you do the more you are allowed to do)." -msgstr "" - -msgid "Corporate Structure" -msgstr "Corporate Structure" - -msgid "" -"The CentOS Project corporate structure is based on a Monolithic Corporate " -"Visual Identity Structure. In this configuration, one unique name and one " -"unique visual style is used in all visual manifestation The CentOS Project " -"is made of." -msgstr "" -"The CentOS Project corporate structure is based on a Monolithic Corporate " -"Visual Identity Structure. In this configuration, one unique name and one " -"unique visual style is used in all visual manifestation The CentOS Project " -"is made of." - -msgid "" -"In a monolithic corporate visual identity structure, internal and external " -"stakeholders use to feel a strong sensation of uniformity, orientation, and " -"identification with the organization. No matter if you are visiting web " -"sites, using the distribution, or acting on social events, the one unique " -"name and one unique visual style connects them all to say: Hey! we are all " -"part of The CentOS Project." -msgstr "" -"In a monolithic corporate visual identity structure, internal and external " -"stakeholders use to feel a strong sensation of uniformity, orientation, and " -"identification with the organization. No matter if you are visiting web " -"sites, using the distribution, or acting on social events, the one unique " -"name and one unique visual style connects them all to say: Hey! we are all " -"part of The CentOS Project." - -msgid "" -"Other corporate structures for The CentOS Project have been considered as " -"well. Such is the case of producing one different visual style for each " -"major release of The CentOS Distribution. This structure isn't inconvenient " -"at all, but some visual contradictions could be introduced if it isn't " -"applied correctly and we need to be aware of it. To apply it correctly, we " -"need to know what The CentOS Project is made of." -msgstr "" -"Other corporate structures for The CentOS Project have been considered as " -"well. Such is the case of producing one different visual style for each " -"major release of The CentOS Distribution. This structure isn't inconvenient " -"at all, but some visual contradictions could be introduced if it isn't " -"applied correctly and we need to be aware of it. To apply it correctly, we " -"need to know what The CentOS Project is made of." - -#, fuzzy -msgid "" -"The CentOS Project, as organization, is mainly made of (but not limited to) " -"three visual manifestations: The CentOS Distribution, The CentOS Web and The " -"CentOS Showroom. Inside The CentOS Distribution visual manifestations, The " -"CentOS Project maintains near to four different major releases of The CentOS " -"Distribution, in parallel. However, inside The CentOS Web visual " -"manifestations, the content is produced for no specific release information " -"(e.g., there is no a complete web site for each major release of The CentOS " -"Distribution individually, but one web site to cover them all). Likewise, " -"the content produced in The CentOS Showroom is industrially created for no " -"specific release, but The CentOS Project in general." -msgstr "" -"The CentOS Project, as organization, is mainly made of (but not limited to) " -"three visual manifestions: The CentOS Distribution, The CentOS Web and The " -"CentOS Showroom. Inside The CentOS Distribution visual manifestations, The " -"CentOS Project maintains near to four different major releases of The CentOS " -"Distribution, parallely in time. However, inside The CentOS Web visual " -"manifestations, the content is produced for no specific release information " -"(e.g., there is no a complete web site for each major release of The CentOS " -"Distribution individually, but one web site to cover them all). Likewise, " -"the content produced in The CentOS Showroom is industrially created for no " -"specific release, but The CentOS Project in general." - -#, fuzzy -msgid "" -"In order to produce the The CentOS Project Monolithic Corporate Visual " -"Identity Structure correctly, we need to consider all the visual " -"manifestations The CentOS Project is made of, not just one of them. If one " -"different visual style is implemented for each major release of The CentOS " -"Distribution, which one of those different visual styles would be used to " -"cover the remaining visual manifestations The CentOS Project is made of (e." -"g., The CentOS Web and The CentOS Showroom)?" -msgstr "" -"In order to produce the The CentOS Project Monolithic Corporate Visual " -"Identity Structure correctly, we need to concider all the visual " -"manifestations The CentOS Project is made of, not just one of them. If one " -"different visual style is implemented for each major release of The CentOS " -"Distribution, which one of those different visual styles would be used to " -"cover the remaining visual manifestations The CentOS Project is made of (e." -"g., The CentOS Web and The CentOS Showroom)?" - -#, fuzzy -msgid "" -"Probably you are thinking: yes, I see your point, but The CentOS Brand " -"connects them all already, why would we need to join them up into the same " -"visual style too, isn't it more work to do, and harder to maintain? It is " -"true that The CentOS Brand does connect all the visual manifestations it is " -"present on, but that connection is even stronger if one unique visual style " -"backups it. In fact, whatever thing you do to strength the visual connection " -"among The CentOS Project visual manifestations would be very good in favor " -"of The CentOS Project recognition." -msgstr "" -"Harder to maintain, more work to do, probably. Specially when you consider " -"that The CentOS Project has proven stability and consistency through time " -"and, that, certainly, didn't come through swinging magical wands or " -"something but hardly working out to automate tasks and providing maintenance " -"through time. With that in mind, I consider The CentOS Project Corporate " -"Visual Identity Structure must be consequent with such stability and " -"consistency tradition. It is true that The CentOS Brand does connect all the " -"visual manifestations it is present on, but that connection is strengthened " -"if one unique visual style backups it. In fact, whatever thing you do to " -"strength the visual connection among The CentOS Project visual " -"manifestations would be very good in favor of The CentOS Project recognition." - -#, fuzzy -msgid "" -"Having just one visual style in all visual manifestations for eternity would " -"be a very boring thing and would give the idea of a visually out-of-date " -"project. So, there is no problem on creating new visual styles for each new " -"major release of The CentOS Distribution, in order to refresh The CentOS " -"Distribution visual style; the problem itself is in not propagating the new " -"visual style created for the new release of The CentOS Distribution to all " -"other visual manifestations The CentOS Project is made of, in a way The " -"CentOS Project could be recognized no matter what visual manifestation be in " -"front of us. Such lack of uniformity is what introduces the visual " -"contradiction The CentOS Artwork SIG is precisely trying to solve by mean of " -"automating the production of corporate themes inside The CentOS Artwork " -"Repository." -msgstr "" -"Obviously, having just one visual style in all visual manifestations for " -"eternity would be a very boring thing and would give the idea of a visually " -"outdated project. So, there is no problem on creating new visual styles for " -"each new major release of The CentOS Distribution, in order to refresh The " -"CentOS Distribution visual style; the problem itself is in not propagating " -"the new visual style created for the new release of The CentOS Distribution " -"to all other visual manifestations The CentOS Project is made of, in a way " -"The CentOS Project could be recognized no matter what visual manifestation " -"be in front of us. Such lack of uniformity is what introduces the visual " -"contradiction we would be precisely trying to solve by mean of themes " -"production in The CentOS Artwork Repository." - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" - -#~ msgid "" -#~ "The corporate design is focused on the effective presentation of " -#~ "corporate messages. As corporate messages we understand all the " -#~ "information emitted from the organization; and when we say all we mean everything that can be perceived through the human " -#~ "senses. The corporate design takes care of defining what this information " -#~ "is and controlling the way it goes out the organization producing it." -#~ msgstr "" -#~ "The corporate design is focused on the effective presentation of " -#~ "corporate messages. As corporate messages we understand all the " -#~ "information emitted from the organization; and when we say all we mean everything that can be perceived through the human " -#~ "senses. The corporate design takes care of defining what this information " -#~ "is and controlling the way it goes out the organization producing it." - -#~ msgid "" -#~ "In the very specific case of The CentOS Project, we'll concentrate our " -#~ "attention on corporate messages that reach us through the visual sense. " -#~ "This is, all the visual manifestations The CentOS Project is made of. As " -#~ "visual manifestations we understand all the visible media The CentOS " -#~ "Project uses to manifest its existence on. At this point it is necessary " -#~ "to consider what The CentOS Project is, what its mission is and what it " -#~ "is producing. This, in order to identify which visual manifestations the " -#~ "organization is demanding attention of corporate design for." -#~ msgstr "" -#~ "In the very specific case of The CentOS Project, we'll concentrate our " -#~ "attention on corporate messages that reach us through the visual sense. " -#~ "This is, all the visual manifestations The CentOS Project is made of. As " -#~ "visual manifestations we understand all the visible media The CentOS " -#~ "Project uses to manifest its existence on. At this point it is necessary " -#~ "to consider what The CentOS Project is, what its mission is and what it " -#~ "is producing. This, in order to identify which visual manifestations the " -#~ "organization is demanding attention of corporate design for." - -#, fuzzy -#~ msgid "The CentOS Visual Manifestations" -#~ msgstr "The CentOS Distribution" - -#, fuzzy -#~ msgid "" -#~ "Inside The CentOS Project applies corporate design to the following " -#~ "visual manifestations:" -#~ msgstr "" -#~ "Inside The CentOS Project we identify and apply corporate design to the " -#~ "following visual manifestations:" - -#~ msgid "" -#~ "The CentOS Distribution: This visual " -#~ "manifestation exists to cover all actions related to artwork production " -#~ "and re-branding, required by The CentOS Distribution in order to comply " -#~ "with upstream's redistribution guidelines." -#~ msgstr "" -#~ "The CentOS Distribution: This visual " -#~ "manifestation exists to cover all actions related to artwork production " -#~ "and re-branding, required by The CentOS Distribution in order to comply " -#~ "with upstream's redistribution guidelines." - -#~ msgid "" -#~ "The CentOS Web: This visual " -#~ "manifestation exists to cover all actions related to artwork production " -#~ "required by The CentOS Project to manifest its existence in the World " -#~ "Wide Web medium." -#~ msgstr "" -#~ "The CentOS Web: This visual " -#~ "manifestation exists to cover all actions related to artwork production " -#~ "required by The CentOS Project to manifest its existence in the World " -#~ "Wide Web medium." - -#~ msgid "" -#~ "The CentOS Showroom: This visual " -#~ "manifestation exists to cover all actions related to artwork production " -#~ "required by The CentOS Project to manifest its existence through media " -#~ "produced industrially (e.g., stationery, clothes, CDs, DVDs, etc.)." -#~ msgstr "" -#~ "The CentOS Showroom: This visual " -#~ "manifestation exists to cover all actions related to artwork production " -#~ "required by The CentOS Project to manifest its existence through media " -#~ "produced industrially (e.g., stationery, clothes, CDs, DVDs, etc.)." - -#, fuzzy -#~ msgid "" -#~ "These visual manifestations seem to cover most media required by The " -#~ "CentOS Project, as organization, to show its existence. However, other " -#~ "visual manifestations could be added in the future, as long as they be " -#~ "needed, to cover different areas like stands, buildings, offices, road " -#~ "transportation or whatever visual manifestation The CentOS Project " -#~ "touches to show its existence." -#~ msgstr "" -#~ "The visual manifestations identified above seem to cover most media " -#~ "required by The CentOS Project, as organization, to show its existence. " -#~ "However, other visual manifestations could be added in the future, as " -#~ "long as they be needed, to cover different areas like stands, buildings, " -#~ "offices, road transportation or whatever visual manifestation The CentOS " -#~ "Project touches to show its existence." - -#~ msgid "" -#~ "Once all visual manifestations have been identified and defined through " -#~ "design models, it is time to visually remark their connection with The " -#~ "CentOS Project. This kind of connection is realized by applying The " -#~ "CentOS Brand to design models inside visual manifestations supported " -#~ "through corporate design." -#~ msgstr "" -#~ "Once all visual manifestations have been identified and defined through " -#~ "design models, it is time to visually remark their connection with The " -#~ "CentOS Project. This kind of connection is realized by applying The " -#~ "CentOS Brand to design models inside visual manifestations supported " -#~ "through corporate design." - -#, fuzzy -#~ msgid "The CentOS Brand" -#~ msgstr "The CentOS Chat." - -#, fuzzy -#~ msgid "The CentOS Brand construction" -#~ msgstr "The CentOS Distribution" - -#, fuzzy -#~ msgid "The CentOS Symbol" -#~ msgstr "The CentOS Web" - -#, fuzzy -#~ msgid "The CentOS Symbol construction (1of4)" -#~ msgstr "The CentOS Distribution" - -#, fuzzy -#~ msgid "corporate-symbol-howto-1of4.png" -#~ msgstr "corporate.png" - -#, fuzzy -#~ msgid "The CentOS Symbol construction (2of4)" -#~ msgstr "The CentOS Distribution" - -#, fuzzy -#~ msgid "corporate-symbol-howto-2of4.png" -#~ msgstr "corporate.png" - -#, fuzzy -#~ msgid "The CentOS Symbol construction (3of4)" -#~ msgstr "The CentOS Distribution" - -#, fuzzy -#~ msgid "corporate-symbol-howto-3of4.png" -#~ msgstr "corporate.png" - -#, fuzzy -#~ msgid "The CentOS Symbol construction (4of4)" -#~ msgstr "The CentOS Distribution" - -#, fuzzy -#~ msgid "corporate-symbol-howto-4of4.png" -#~ msgstr "corporate.png" - -#, fuzzy -#~ msgid "The CentOS Type" -#~ msgstr "The CentOS Web" - -#, fuzzy -#~ msgid "The CentOS Logo" -#~ msgstr "The CentOS Showroom" - -#, fuzzy -#~ msgid "The CentOS Themes" -#~ msgstr "The CentOS Web" - -#, fuzzy -#~ msgid "The CentOS Motifs" -#~ msgstr "The CentOS Forums." - -#~ msgid "" -#~ "The CentOS Project corporate behaviour takes place through The CentOS " -#~ "Project corporate communication, as described above." -#~ msgstr "" -#~ "The CentOS Project corporate behaviour takes place through The CentOS " -#~ "Project corporate communication, as described above." - -#~ msgid "" -#~ "Probably you are thinking: yes, I see your point, but The CentOS Brand " -#~ "connects them all already, why would we need to join them up into the " -#~ "same visual style too, isn't it more work to do, and harder to maintain?" -#~ msgstr "" -#~ "Probably you are thinking: yes, I see your point, but The CentOS Brand " -#~ "connects them all already, why would we need to join them up into the " -#~ "same visual style too, isn't it more work to do, and harder to maintain?" - -#, fuzzy -#~ msgid "" -#~ "@@image: 'Final/corporate-logo-howto.png'; md5=THIS FILE DOESN'T EXIST" -#~ msgstr "@@image: 'corporate.png'; md5=THIS FILE DOESN'T EXIST" diff --git a/Corporate/Locales/en_US/corporate.svgz.po b/Corporate/Locales/en_US/corporate.svgz.po deleted file mode 100644 index 18e78bb..0000000 --- a/Corporate/Locales/en_US/corporate.svgz.po +++ /dev/null @@ -1,61 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate.svgz 0.6\n" -"POT-Creation-Date: 2013-11-26 22:08-0500\n" -"PO-Revision-Date: 2013-11-26 22:08-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "The CentOS Project Corporate Identity" -msgstr "The CentOS Project Corporate Identity" - -msgid "image/svg+xml" -msgstr "image/svg+xml" - -msgid "2013-07-23" -msgstr "2013-07-23" - -msgid "Alain Reguera Delgado" -msgstr "Alain Reguera Delgado" - -msgid "The CentOS Project" -msgstr "The CentOS Project" - -msgid "en_US" -msgstr "en_US" - -msgid "Identity" -msgstr "Identity" - -msgid "Models" -msgstr "Models" - -msgid "Manuals" -msgstr "Manuals" - -msgid "Corporate" -msgstr "Corporate" - -#, no-wrap -msgid "COMMUNICATION" -msgstr "COMMUNICATION" - -#, no-wrap -msgid "GRAPHIC DESIGN" -msgstr "GRAPHIC DESIGN" - -#, no-wrap -msgid "STRUCTURE" -msgstr "STRUCTURE" - -#, no-wrap -msgid "BEHAVIOUR" -msgstr "BEHAVIOUR" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Corporate/Locales/es_ES/corporate.asciidoc.po b/Corporate/Locales/es_ES/corporate.asciidoc.po deleted file mode 100644 index 964a12d..0000000 --- a/Corporate/Locales/es_ES/corporate.asciidoc.po +++ /dev/null @@ -1,372 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate.asciidoc 0.6\n" -"POT-Creation-Date: 2013-10-24 01:23-0400\n" -"PO-Revision-Date: 2013-10-24 01:23-0400\n" -"Last-Translator: Localization SIG \n" -"Language-Team: Spanish\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -msgid "@@image: 'corporate.png'; md5=9caa5d90bf85b562e8a815fe466d0783" -msgstr "" - -msgid "The CentOS Project Corporate Visual Identity" -msgstr "La Identidad Visual Corporativa Del Proyecto CentOS" - -msgid "Jul 2013" -msgstr "" - -msgid "Alain" -msgstr "" - -msgid "Reguera" -msgstr "" - -msgid "Delgado" -msgstr "" - -msgid "al@centos.org.cu" -msgstr "" - -msgid "ARD" -msgstr "" - -msgid "1.0" -msgstr "" - -msgid "" -"The CentOS Project Corporate Identity is the “persona” of the organization " -"known as The CentOS Project. The CentOS Project Corporate Identity plays a " -"significant role in the way The CentOS Project, as organization, presents " -"itself to both internal and external stakeholders. In general terms, The " -"CentOS Project Corporate Identity expresses the values and ambitions of The " -"CentOS Project organization, its business, and its characteristics." -msgstr "" - -msgid "" -"The CentOS Project Corporate Identity provides visibility, recognizability, " -"reputation, structure and identification to The CentOS Project organization " -"by means of Corporate Design, Corporate Communication, and Corporate " -"Behaviour." -msgstr "" - -msgid "The CentOS Project Corporate Identity" -msgstr "" - -msgid "corporate.png" -msgstr "" - -msgid "Corporate Mission" -msgstr "Misión Corporativa" - -msgid "" -"The CentOS Project exists to produce The CentOS Distribution, an Enterprise-" -"class Linux Distribution derived from sources freely provided to the public " -"by a prominent North American Enterprise Linux vendor. The CentOS " -"Distribution conforms fully with the upstream vendors redistribution policy " -"and aims to be 100% binary compatible. (The CentOS Distribution mainly " -"changes packages to remove upstream vendor branding and artwork.)." -msgstr "" - -msgid "" -"The CentOS Distribution is developed by a small but growing team of core " -"developers. In turn the core developers are supported by an active user " -"community including system administrators, network administrators, " -"enterprise users, managers, core Linux contributors and Linux enthusiasts " -"from around the world." -msgstr "" - -msgid "" -"The CentOS Distribution has numerous advantages including: an active and " -"growing user community, quickly rebuilt, tested, and QA'ed errata packages, " -"an extensive mirror network, developers who are contactable and responsive " -"of a reliable Enterprise-class Linux Distribution, multiple free support " -"avenues including a Wiki, " -"IRC " -"Chat, Email Lists, " -"Forums, and a " -"dynamic FAQ." -msgstr "" - -msgid "Corporate Graphic Design" -msgstr "Diseño Gráfico Corporativo" - -msgid "" -"The corporate design is focused on the effective presentation of corporate " -"messages. As corporate messages we understand all the information emitted " -"from the organization; and when we say all we mean " -"everything that can be perceived through the human senses. The corporate " -"design takes care of defining what this information is and controlling the " -"way it goes out the organization producing it." -msgstr "" - -msgid "" -"When the organization doesn't take control over the corporate messages it " -"produces, the organization is letting that area of its identity to the " -"unknown and the results might be good or not so good, it is hard to know. " -"The issue to see here is that even the organization doesn't take control " -"over its corporate messages, they are always talking about the organization. " -"Taking control of corporate messages is a decision the organization needs to " -"take by itself, based on its need of better describe what it is." -msgstr "" - -msgid "" -"In the very specific case of The CentOS Project, we'll concentrate our " -"attention on corporate messages that reach us through the visual sense. This " -"is, all the visual manifestations The CentOS Project is made of. As visual " -"manifestations we understand all the visible media The CentOS Project uses " -"to manifest its existence on. At this point it is necessary to consider what " -"The CentOS Project is, what its mission is and what it is producing. This, " -"in order to identify which visual manifestations the organization is " -"demanding attention of corporate design for." -msgstr "" - -msgid "" -"Inside The CentOS Project we identify and apply corporate design to the " -"following visual manifestations:" -msgstr "" - -msgid "" -"The CentOS Distribution: This visual " -"manifestation exists to cover all actions related to artwork production and " -"re-branding, required by The CentOS Distribution in order to comply with " -"upstream's redistribution guidelines." -msgstr "" - -msgid "" -"The CentOS Web: This visual " -"manifestation exists to cover all actions related to artwork production " -"required by The CentOS Project to manifest its existence in the World Wide " -"Web medium." -msgstr "" - -msgid "" -"The CentOS Showroom: This visual " -"manifestation exists to cover all actions related to artwork production " -"required by The CentOS Project to manifest its existence through media " -"produced industrially (e.g., stationery, clothes, CDs, DVDs, etc.)." -msgstr "" - -msgid "" -"The visual manifestations identified above seem to cover most media required " -"by The CentOS Project, as organization, to show its existence. However, " -"other visual manifestations could be added in the future, as long as they be " -"needed, to cover different areas like stands, buildings, offices, road " -"transportation or whatever visual manifestation The CentOS Project touches " -"to show its existence." -msgstr "" - -msgid "" -"Once all visual manifestations have been identified and defined through " -"design models, it is time to visually remark their connection with The " -"CentOS Project. This kind of connection is realized by applying The CentOS " -"Brand to design models inside visual manifestations supported through " -"corporate design." -msgstr "" - -msgid "Corporate Communication" -msgstr "Comunicación Corporativa" - -msgid "" -"The CentOS Project corporate communication is focused on the effective " -"propagation of corporate messages. Propagation of corporate messages is " -"closely related to the media the organization uses as vehicle to distribute " -"its corporate messages." -msgstr "" - -msgid "" -"The CentOS Project corporate communication takes place through the following " -"visual manifestations:" -msgstr "" - -msgid "The CentOS Distribution" -msgstr "La Distribución CentOS" - -msgid "" -"This visual manifestation communicates its existence through software " -"packages. There are packages that make a remarkable use of images, packages " -"that make a moderate use of images, and packages that don't use images at " -"all. This visual manifestation is focused on providing The CentOS Project " -"images required by software packages that do use images in a remarkable way, " -"specially those holding the upstream brand (e.g., anaconda, grub, syslinux, " -"gdm, kdebase)." -msgstr "" - -msgid "" -"The Community Enterprise Operating System itself (communicates the essense " -"of The CentOS Project existence.)." -msgstr "" - -msgid "" -"Release Schema (Lifetime) and all the stuff related (e.g., Release Notes, " -"Documentation, Erratas, etc.)." -msgstr "" - -msgid "The CentOS Web" -msgstr "La Web CentOS" - -msgid "" -"This visual manifestation communicates its existence through web " -"applications. These web applications are free software and come from " -"different providers which distribute their work with predefined visual " -"styles. Frequently, these predefined visual styles have no visual relation " -"among themselves and introduce some visual contradictions when they all are " -"put together. Removing these visual contradictions is object of work for " -"this visual manifestation." -msgstr "" - -msgid "The CentOS Chat." -msgstr "" - -msgid "The CentOS Mailing Lists." -msgstr "" - -msgid "The CentOS Forums." -msgstr "" - -msgid "The CentOS Wiki." -msgstr "" - -msgid "Special Interest Groups (SIGs)." -msgstr "" - -msgid "Social Events, Interviews, Conferences, etc." -msgstr "" - -msgid "" -"The extensive network of mirrors available for downloading ISO files as well " -"as RPMs and SRPMs used to build them up in different architectures." -msgstr "" - -msgid "The CentOS Showroom" -msgstr "El Mercado CentOS" - -msgid "" -"This visual manifestation communicates its existence through production of " -"industrial objects carrying The CentOS Brand. These branded objects are " -"directed to be distributed on social events and/or shops. They provide a way " -"of promotion and commercialization that may help to reduce The CentOS " -"Project expenses (e.g., electrical power, hosting, servers, full-time-" -"developers, etc.), in a similar way as donations may do." -msgstr "" - -msgid "Stationery (e.g., Posters, Stickers, CD Lables and Sleeves)." -msgstr "" - -msgid "Clothes (e.g., Shirts, T-shirts, Pullovers, Caps)." -msgstr "" - -msgid "Installation media (e.g., CDs, DVD, Pendrives)." -msgstr "" - -msgid "Corporate Behaviour" -msgstr "Comportamiento Corporativo" - -msgid "" -"The CentOS Project corporate behaviour is focused on the effective " -"interaction of each member involved in the organization (e.g., core " -"developers, community members, etc.). It is related to ethics and politics " -"used to do the things inside the organization. It is related to the sense of " -"direction chosen by the organization and they way the organization projects " -"itself to achieve it." -msgstr "" - -msgid "" -"The CentOS Project corporate behaviour takes place through The CentOS " -"Project corporate communication, as described above." -msgstr "" - -msgid "Corporate Structure" -msgstr "Estructura Corporativa" - -msgid "" -"The CentOS Project corporate structure is based on a Monolithic Corporate " -"Visual Identity Structure. In this configuration, one unique name and one " -"unique visual style is used in all visual manifestation The CentOS Project " -"is made of." -msgstr "" - -msgid "" -"In a monolithic corporate visual identity structure, internal and external " -"stakeholders use to feel a strong sensation of uniformity, orientation, and " -"identification with the organization. No matter if you are visiting web " -"sites, using the distribution, or acting on social events, the one unique " -"name and one unique visual style connects them all to say: Hey! we are all " -"part of The CentOS Project." -msgstr "" - -msgid "" -"Other corporate structures for The CentOS Project have been considered as " -"well. Such is the case of producing one different visual style for each " -"major release of The CentOS Distribution. This structure isn't inconvenient " -"at all, but some visual contradictions could be introduced if it isn't " -"applied correctly and we need to be aware of it. To apply it correctly, we " -"need to know what The CentOS Project is made of." -msgstr "" - -msgid "" -"The CentOS Project, as organization, is mainly made of (but not limited to) " -"three visual manifestions: The CentOS Distribution, The CentOS Web and The " -"CentOS Showroom. Inside The CentOS Distribution visual manifestations, The " -"CentOS Project maintains near to four different major releases of The CentOS " -"Distribution, parallely in time. However, inside The CentOS Web visual " -"manifestations, the content is produced for no specific release information " -"(e.g., there is no a complete web site for each major release of The CentOS " -"Distribution individually, but one web site to cover them all). Likewise, " -"the content produced in The CentOS Showroom is industrially created for no " -"specific release, but The CentOS Project in general." -msgstr "" - -msgid "" -"In order to produce the The CentOS Project Monolithic Corporate Visual " -"Identity Structure correctly, we need to concider all the visual " -"manifestations The CentOS Project is made of, not just one of them. If one " -"different visual style is implemented for each major release of The CentOS " -"Distribution, which one of those different visual styles would be used to " -"cover the remaining visual manifestations The CentOS Project is made of (e." -"g., The CentOS Web and The CentOS Showroom)?" -msgstr "" - -msgid "" -"Probably you are thinking: yes, I see your point, but The CentOS Brand " -"connects them all already, why would we need to join them up into the same " -"visual style too, isn't it more work to do, and harder to maintain?" -msgstr "" - -msgid "" -"Harder to maintain, more work to do, probably. Specially when you consider " -"that The CentOS Project has proven stability and consistency through time " -"and, that, certainly, didn't come through swinging magical wands or " -"something but hardly working out to automate tasks and providing maintenance " -"through time. With that in mind, I consider The CentOS Project Corporate " -"Visual Identity Structure must be consequent with such stability and " -"consistency tradition. It is true that The CentOS Brand does connect all the " -"visual manifestations it is present on, but that connection is strengthened " -"if one unique visual style backups it. In fact, whatever thing you do to " -"strength the visual connection among The CentOS Project visual " -"manifestations would be very good in favor of The CentOS Project recognition." -msgstr "" - -msgid "" -"Obviously, having just one visual style in all visual manifestations for " -"eternity would be a very boring thing and would give the idea of a visually " -"outdated project. So, there is no problem on creating new visual styles for " -"each new major release of The CentOS Distribution, in order to refresh The " -"CentOS Distribution visual style; the problem itself is in not propagating " -"the new visual style created for the new release of The CentOS Distribution " -"to all other visual manifestations The CentOS Project is made of, in a way " -"The CentOS Project could be recognized no matter what visual manifestation " -"be in front of us. Such lack of uniformity is what introduces the visual " -"contradiction we would be precisely trying to solve by mean of themes " -"production in The CentOS Artwork Repository." -msgstr "" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "Alain Reguera Delgado , 2013" diff --git a/Corporate/Locales/es_ES/corporate.svgz.po b/Corporate/Locales/es_ES/corporate.svgz.po deleted file mode 100644 index d3b6d92..0000000 --- a/Corporate/Locales/es_ES/corporate.svgz.po +++ /dev/null @@ -1,61 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: corporate.svgz 0.6\n" -"POT-Creation-Date: 2013-10-24 01:23-0400\n" -"PO-Revision-Date: 2013-10-24 01:23-0400\n" -"Last-Translator: Localization SIG \n" -"Language-Team: Spanish\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "The CentOS Project Corporate Identity" -msgstr "" - -msgid "image/svg+xml" -msgstr "" - -msgid "2013-07-23" -msgstr "" - -msgid "Alain Reguera Delgado" -msgstr "" - -msgid "The CentOS Project" -msgstr "" - -msgid "en_US" -msgstr "" - -msgid "Identity" -msgstr "" - -msgid "Models" -msgstr "" - -msgid "Manuals" -msgstr "" - -msgid "Corporate" -msgstr "" - -#, no-wrap -msgid "COMMUNICATION" -msgstr "COMUNICACIÓN" - -#, no-wrap -msgid "GRAPHIC DESIGN" -msgstr "DISEÑO GRÁFICO" - -#, no-wrap -msgid "STRUCTURE" -msgstr "ESTRUCTURA" - -#, no-wrap -msgid "BEHAVIOUR" -msgstr "COMPORTAMIENTO" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "" diff --git a/Corporate/corporate-clothes-head.svgz b/Corporate/corporate-clothes-head.svgz deleted file mode 100644 index ac335c1..0000000 Binary files a/Corporate/corporate-clothes-head.svgz and /dev/null differ diff --git a/Corporate/corporate-clothes-torso.svgz b/Corporate/corporate-clothes-torso.svgz deleted file mode 100644 index b042c8d..0000000 Binary files a/Corporate/corporate-clothes-torso.svgz and /dev/null differ diff --git a/Corporate/corporate-colors.svgz b/Corporate/corporate-colors.svgz deleted file mode 100644 index 9ad2de4..0000000 Binary files a/Corporate/corporate-colors.svgz and /dev/null differ diff --git a/Corporate/corporate-fonts.svgz b/Corporate/corporate-fonts.svgz deleted file mode 100644 index b612f4d..0000000 Binary files a/Corporate/corporate-fonts.svgz and /dev/null differ diff --git a/Corporate/corporate-logo-howto.svgz b/Corporate/corporate-logo-howto.svgz deleted file mode 100644 index 1b575a9..0000000 Binary files a/Corporate/corporate-logo-howto.svgz and /dev/null differ diff --git a/Corporate/corporate-symbol-howto-1of4.svgz b/Corporate/corporate-symbol-howto-1of4.svgz deleted file mode 100644 index 2b74847..0000000 Binary files a/Corporate/corporate-symbol-howto-1of4.svgz and /dev/null differ diff --git a/Corporate/corporate-symbol-howto-2of4.svgz b/Corporate/corporate-symbol-howto-2of4.svgz deleted file mode 100644 index a350cc7..0000000 Binary files a/Corporate/corporate-symbol-howto-2of4.svgz and /dev/null differ diff --git a/Corporate/corporate-symbol-howto-3of4.svgz b/Corporate/corporate-symbol-howto-3of4.svgz deleted file mode 100644 index 0d1dba5..0000000 Binary files a/Corporate/corporate-symbol-howto-3of4.svgz and /dev/null differ diff --git a/Corporate/corporate-symbol-howto-4of4.svgz b/Corporate/corporate-symbol-howto-4of4.svgz deleted file mode 100644 index 842a1d9..0000000 Binary files a/Corporate/corporate-symbol-howto-4of4.svgz and /dev/null differ diff --git a/Corporate/corporate-themes.svgz b/Corporate/corporate-themes.svgz deleted file mode 100644 index 618070c..0000000 Binary files a/Corporate/corporate-themes.svgz and /dev/null differ diff --git a/Corporate/corporate.asciidoc b/Corporate/corporate.asciidoc deleted file mode 100644 index 8e3ef7a..0000000 --- a/Corporate/corporate.asciidoc +++ /dev/null @@ -1,370 +0,0 @@ -The CentOS Project Corporate Visual Identity -============================================ -Alain Reguera Delgado -v1.0, Jul 2013 - -Abstract --------- - -The CentOS Project Corporate Identity is the ``persona'' of the -organization known as The CentOS Project. The CentOS Project -Corporate Identity plays a significant role in the way The CentOS -Project, as organization, presents itself to both internal and -external stakeholders. In general terms, The CentOS Project Corporate -Identity expresses the values and ambitions of The CentOS Project -organization, its business, and its characteristics. - -The CentOS Project Corporate Identity provides visibility, -recognizability, reputation, structure and identification to The -CentOS Project organization by means of Corporate Design, Corporate -Communication, and Corporate Behavior. - -[[corporate_identity]] -.The CentOS Project Corporate Identity -image::corporate.png[alt="The CentOS Project Corporate Identity"] - -Corporate Mission ------------------ - -The CentOS Project exists to produce The CentOS Distribution, an -Enterprise-class Linux Distribution derived from sources freely -provided to the public by a prominent North American Enterprise Linux -vendor. The CentOS Distribution conforms fully with the upstream -vendors redistribution policy and aims to be 100% binary compatible. -(The CentOS Distribution mainly changes packages to remove upstream -vendor branding and artwork.). - -The CentOS Distribution is developed by a small but growing team of -core developers. In turn the core developers are supported by an -active user community including system administrators, network -administrators, enterprise users, managers, core Linux contributors -and Linux enthusiasts from around the world. - -The CentOS Distribution has numerous advantages including: an active -and growing user community, quickly rebuilt, tested, and QA'ed errata -packages, an extensive mirror network, developers who are contactable -and responsive of a reliable Enterprise-class Linux Distribution, -multiple free support avenues including a -http://wiki.centos.org/[Wiki], -http://www.centos.org/modules/tinycontent/index.php?id=8[IRC Chat], -http://lists.centos.org/[Email Lists], -http://www.centos.org/modules/newbb/[Forums], and a dynamic -http://www.centos.org/modules/smartfaq/[FAQ]. - -Corporate Graphic Design ------------------------- - -Corporate graphic design is focused on the presentation of corporate -messages with efficiency and efficacy. Corporate graphic design is a -cornerstone of corporate visual identity. When the organization -doesn't take control over the corporate messages it produces, the -organization is letting that area of its identity to the unknown and -the result might be good or not so good, it is hard to know. Even the -organization doesn't take control over its corporate messages they are -always talking about the organization. Taking control of corporate -messages presentation is a decision the organization needs to take by -itself, based on its need of better describe what it is. To work out -the corporate graphic design of an organization it is required to -identify which are the visual manifestations the organization reflects -its existence on. - -The CentOS Artwork SIG has identified the following visual -manifestations for The CentOS Project organization: - -* GNU/Linux Distribution -- to control the operating system appearance. -* Web environment -- to control the web applications appearance. -* Promotion -- to control the industrial media appearance. - -[[centos-brand]] -Corporate Brand -~~~~~~~~~~~~~~~ - -The corporate brand is the graphical identification of an -organization. The CentOS Artwork SIG uses The CentOS Brand to connect -all the visual manifestations The CentOS Project is made of (e.g., -GNU/Linux Distributions, Websites, Stationery, etc.) and, this way, it -provides visual recognition among similar projects available on the -Internet. - -The CentOS Brand is composed of a graphical component known as The -CentOS Symbol and a typographical component known as The CentOS Type. -When The CentOS Symbol and The CentOS Type are put together, they -create what we know as The CentOS Logo. All the components that make -The CentOS Brand can be used together or separately, considering that, -in hierarchy order, The CentOS Logo is rather preferred than The -CentOS Symbol, as well as The CentOS Symbol is rather preferred than -The CentOS Type alone. - -image:corporate-logo-howto.png[corporate-logo-howto.png] - -The CentOS Brand must be exactly the same every time it is printed -out, no matter what the medium is. A route to reproduce The CentOS -Brand this way must be used so as to avoid reproduction mistakes of -any kind when final images are branded with it. To prevent such -mistakes, The CentOS Artwork SIG uses configuration files and the -*render* module of *centos-art.sh* script to produce PNG brand images -of different sizes and colors that can be combined later with other -images instead of manipulating The CentOS Brand in SVG format inside -each different design model that requires it. This also grants a -single point of change for all brands already applied on final images. -In this environment, if you make a change to brands SVG files, they -will be propagated to all final images the next time you render them. - -The CentOS Symbol is the graphical part of The CentOS Logo. As The -CentOS Logo, The CentOS Symbol is used to ``brand'' images produced by -The CentOS Project and provide visual connection between images so -they can be monolithically recognized as part of The CentOS Project. -The CentOS Symbol must be exactly the same every time it is printed -out and a route to reproduce it in such a way must be available so as -to avoid reproduction mistakes when images are branded with it. - -The CentOS Type is the typographical part of The CentOS Logo. The -CentOS Type is used to ``brand'' images produce by The CentOS Project -and provide visual connection between images so they can be -monolithically recognized as part of The CentOS Project. The CentOS -Type alone provides less recognition than The CentOS Logo and The -CentOS Symbol. Frequently, The CentOS Type is used to advert the major -release of CentOS Distribution on the first images shown as part of -Distribution installation process. The CentOS Symbol and any release -information printed out with it must have exactly the same proportions -every time they are printed out. - -Corporate Fonts -~~~~~~~~~~~~~~~ - -The CentOS Artwork SIG uses the following font files in their -corporate graphic designs: - -image:corporate-fonts.png[corporate-fonts.png] - -Corporate Colors -~~~~~~~~~~~~~~~~ - -In addition to colors used in The CentOS Symbol (9ccd2aff, 932279ff, -262577ff, efa724ff) and The CentOS Default Background Color -(204c8dff), The CentOS Artwork SIG uses the following colors in their -corporate graphic designs: - -image:../corporate-colors.png[corporate-colors.png] - -Artistic motifs have not any limitation in the number of colors used. -If you are a graphic designer creating artistic motifs for The CentOS -Project, feel free to take your creativeness at its limit by creating -color-full artistic motifs. For final bootup images which require a -reduced number of colors, create palette of colors for them with the -appropriate number of colors and let the *render* module of -*centos-art.sh* script to do the rest. - -[[centos-clothes]] -Corporate Clothes -~~~~~~~~~~~~~~~~~ - -The CentOS clothes identify the The CentOS Project representative -people at public presentations. - -image:../corporate-clothes-head.png[corporate-clothes-cap.png] - -image:../corporate-clothes-torso.png[corporate-clothes-shirt.png] - -[[corporate-themes]] -Corporate Themes -~~~~~~~~~~~~~~~~ - -The CentOS themes organize visual styles for all the visual -manifestation The CentOS Project is made of. In order to automate the -process of rendering images based on customizable patterns, themes -have been divided into ``design models'', ``localization files,'' and -``artistic motifs.'' - -image:corporate-themes.png[corporate-themes.png] - -[[corporate-themes-models]] -Design Models -^^^^^^^^^^^^^ - -Design models are compressed SVG files created with Inkscape. They -describe the image files used to implement the CentOS project visual -manifestations. For example, in the specific case of CentOS -distribution, each final image you want to re-brand has a design model -associated used to set the final image dimensions, whether or not it -has round borders, and what background to use on it. Design models -are created once and rarely modified through time. They are only -modified if the visual manifestation they refer to changes or needs to -be tuned up. - -[[corporate-themes-l10n]] -Localization Files -^^^^^^^^^^^^^^^^^^ - -Localization files provide localization for messages inside design -models. For example, if you decide to use slide images in CentOS -installer, you need to create one design model for each slide image -you want to produce in English language. Then, using *locale* module, -you create PO files for each design model you have. PO files are -created using the current language information of your terminal (e.g., -see value of +LANG+ variable). Then you use the *locale* module again -to edit the PO files and provide string translations from English to -your preferred language. Once translations are on the PO files, you -use the *render* module to produce images for your preferred language, -based on the artistic motif you initiate rendition for and the related -design models set in the rendition configuration file. - -[[corporate-themes-motifs]] -Artistic Motifs -^^^^^^^^^^^^^^^ - -Artistic motifs are PNG images holding the look and feel of each -design model available. One important characteristic of artistic -motifs is preserving one unique visual style for all the PNG images -they are made of. Artistic motifs aren't limited in number. It is -possible to have several artistic motifs and produce final images for -all of them using one single set of design models. Artistic motifs -give plenty of room for graphic designers' creativeness. As -convention, artistic motifs are conceived without any specific brand -information on them. The brand information is set using brand images -later, when final images are produced. - -[[corporate-communication]] -Corporate Communication ------------------------ - -The CentOS Project corporate communication is focused on the effective -propagation of corporate messages. Propagation of corporate messages -is closely related to the media the organization uses as vehicle to -distribute its corporate messages. - -The CentOS Project corporate communication takes place through the -following visual manifestations: - -The CentOS Distribution -~~~~~~~~~~~~~~~~~~~~~~~ - -This visual manifestation communicates its existence through software -packages. There are packages that make a remarkable use of images, -packages that make a moderate use of images, and packages that don't -use images at all. This visual manifestation is focused on providing -The CentOS Project images required by software packages that do use -images in a remarkable way, specially those holding the upstream brand -(e.g., _anaconda_, _grub_, _syslinux_, _gdm_, _kdebase_). - -- The Community Enterprise Operating System itself (communicates the - essence of The CentOS Project existence.). - -- Release Schema (Lifetime) and all the stuff related (e.g., Release - Notes, Documentation, Erratas, etc.). - -The CentOS Web -~~~~~~~~~~~~~~ - -This visual manifestation communicates its existence through web -applications. These web applications are free software and come from -different providers which distribute their work with predefined visual -styles. Frequently, these predefined visual styles have no visual -relation among themselves and introduce some visual contradictions -when they all are put together. Removing these visual contradictions -is object of work for this visual manifestation. - -- The CentOS Chat. -- The CentOS Mailing Lists. -- The CentOS Forums. -- The CentOS Wiki. -- Special Interest Groups (SIGs). -- Social Events, Interviews, Conferences, etc. -- The extensive network of mirrors available for downloading ISO files - as well as RPMs and SRPMs used to build them up in different - architectures. - -The CentOS Showroom -~~~~~~~~~~~~~~~~~~~ - -This visual manifestation communicates its existence through -production of industrial objects carrying The CentOS Brand. These -branded objects are directed to be distributed on social events and/or -shops. They provide a way of promotion and commercialization that may -help to reduce The CentOS Project expenses (e.g., electrical power, -hosting, servers, full-time-developers, etc.), in a similar way as -donations may do. - -- Stationery (e.g., Posters, Stickers, CD Lables and Sleeves). -- Clothes (e.g., Shirts, T-shirts, Pullovers, Caps). -- Installation media (e.g., CDs, DVD, Pen-drives). - -Corporate Behavior -------------------- - -The CentOS Project corporate behavior is focused on the effective -interaction of each member involved in the organization (e.g., core -developers, community members, etc.). It is related to ethics and -politics used to do the things inside the organization. It is related -to the sense of direction chosen by the organization and the way the -organization projects itself to achieve it. - -The CentOS Project corporate behavior is based on a meritocracy (the -more you do the more you are allowed to do). - -Corporate Structure -------------------- -The CentOS Project corporate structure is based on a Monolithic -Corporate Visual Identity Structure. In this configuration, one unique -name and one unique visual style is used in all visual manifestation -The CentOS Project is made of. - -In a monolithic corporate visual identity structure, internal and -external stakeholders use to feel a strong sensation of uniformity, -orientation, and identification with the organization. No matter if -you are visiting web sites, using the distribution, or acting on -social events, the one unique name and one unique visual style -connects them all to say: Hey! we are all part of The CentOS Project. - -Other corporate structures for The CentOS Project have been considered -as well. Such is the case of producing one different visual style for -each major release of The CentOS Distribution. This structure isn't -inconvenient at all, but some visual contradictions could be -introduced if it isn't applied correctly and we need to be aware of -it. To apply it correctly, we need to know what The CentOS Project is -made of. - -The CentOS Project, as organization, is mainly made of (but not -limited to) three visual manifestations: The CentOS Distribution, The -CentOS Web and The CentOS Showroom. Inside The CentOS Distribution -visual manifestations, The CentOS Project maintains near to four -different major releases of The CentOS Distribution, in parallel. -However, inside The CentOS Web visual manifestations, the content is -produced for no specific release information (e.g., there is no a -complete web site for each major release of The CentOS Distribution -individually, but one web site to cover them all). Likewise, the -content produced in The CentOS Showroom is industrially created for no -specific release, but The CentOS Project in general. - -In order to produce the The CentOS Project Monolithic Corporate Visual -Identity Structure correctly, we need to consider all the visual -manifestations The CentOS Project is made of, not just one of them. -If one different visual style is implemented for each major release of -The CentOS Distribution, which one of those different visual styles -would be used to cover the remaining visual manifestations The CentOS -Project is made of (e.g., The CentOS Web and The CentOS Showroom)? - -Probably you are thinking: yes, I see your point, but The CentOS Brand -connects them all already, why would we need to join them up into the -same visual style too, isn't it more work to do, and harder to -maintain? It is true that The CentOS Brand does connect all the -visual manifestations it is present on, but that connection is even -stronger if one unique visual style backups it. In fact, whatever -thing you do to strength the visual connection among The CentOS -Project visual manifestations would be very good in favor of The -CentOS Project recognition. - -Having just one visual style in all visual manifestations for eternity -would be a very boring thing and would give the idea of a visually -out-of-date project. So, there is no problem on creating new visual -styles for each new major release of The CentOS Distribution, in order -to refresh The CentOS Distribution visual style; the problem itself is -in not propagating the new visual style created for the new release of -The CentOS Distribution to all other visual manifestations The CentOS -Project is made of, in a way The CentOS Project could be recognized no -matter what visual manifestation be in front of us. Such lack of -uniformity is what introduces the visual contradiction The CentOS -Artwork SIG is precisely trying to solve by mean of automating the -production of corporate themes inside The CentOS Artwork Repository. - -// vim: set syntax=asciidoc: diff --git a/Corporate/corporate.svgz b/Corporate/corporate.svgz deleted file mode 100644 index bf60578..0000000 Binary files a/Corporate/corporate.svgz and /dev/null differ diff --git a/Corporate/render.conf b/Corporate/render.conf deleted file mode 100644 index 4978f22..0000000 --- a/Corporate/render.conf +++ /dev/null @@ -1,127 +0,0 @@ -[corporate.png] -render-type = "svg" -render-flow = "base" -render-from = "corporate.svgz" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/corporate.svgz.po" -command = "/usr/bin/convert -colors 32" - -[corporate-fonts.png] -render-type = "svg" -render-flow = "base" -render-from = "corporate-fonts.svgz" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/corporate-fonts.svgz.po" -command = "/usr/bin/convert -colors 128" - -[corporate-logo-howto.png] -render-type = "svg" -render-flow = "base" -render-from = "corporate-logo-howto.svgz" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/corporate-logo-howto.svgz.po" -command = "/usr/bin/convert -colors 128" - -[corporate-symbol-howto-1of4.png] -render-type = "svg" -render-flow = "base" -render-from = "corporate-symbol-howto-1of4.svgz" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/corporate-symbol-howto-1of4.svgz.po" -command = "/usr/bin/convert -colors 128" - -[corporate-symbol-howto-2of4.png] -render-type = "svg" -render-flow = "base" -render-from = "corporate-symbol-howto-2of4.svgz" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/corporate-symbol-howto-2of4.svgz.po" -command = "/usr/bin/convert -colors 128" - -[corporate-symbol-howto-3of4.png] -render-type = "svg" -render-flow = "base" -render-from = "corporate-symbol-howto-3of4.svgz" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/corporate-symbol-howto-3of4.svgz.po" -command = "/usr/bin/convert -colors 128" - -[corporate-symbol-howto-4of4.png] -render-type = "svg" -render-flow = "base" -render-from = "corporate-symbol-howto-4of4.svgz" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/corporate-symbol-howto-4of4.svgz.po" -command = "/usr/bin/convert -colors 128" - -[corporate-themes.png] -render-type = "svg" -render-flow = "base" -render-from = "corporate-themes.svgz" -export-id = "CENTOSARTWORK" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/corporate-themes.svgz.po" -command = "/usr/bin/convert -colors 128" - -[corporate-clothes-head.png] -render-type = "svg" -render-flow = "base" -render-from = "corporate-clothes-head.svgz" -export-id = "CENTOSARTWORK" -command = "/usr/bin/convert" - -[corporate-clothes-torso.png] -render-type = "svg" -render-flow = "base" -render-from = "corporate-clothes-torso.svgz" -export-id = "CENTOSARTWORK" -command = "/usr/bin/convert" - -[corporate-colors.png] -render-type = "svg" -render-flow = "base" -render-from = "corporate-colors.svgz" -export-id = "CENTOSARTWORK" -command = "/usr/bin/convert" - -[corporate-symbol.png] -render-type = "svg" -render-flow = "extended" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Symbols/Webenv/centos.svgz" -export-id = "CENTOSARTWORK" -heights = "200" -fgcolors = "ad7fa8" -bgcolors = "ffffff-0" -formats = "png" - -[corporate-type.png] -render-type = "svg" -render-flow = "base" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.svgz" -export-id = "CENTOSARTWORK" -heights = "200" -fgcolors = "ad7fa8" -bgcolors = "ffffff-0" -formats = "png" - -[corporate-type-release.png] -render-type = "svg" -render-flow = "extended" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/{Webenv/centos.svgz,Numbers/6.svgz}" -export-id = "CENTOSARTWORK" -heights = "200" -fgcolors = "ad7fa8" -bgcolors = "ffffff-0" -formats = "png" - -[corporate-logo.png] -render-type = "svg" -render-flow = "extended" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.svgz}" -export-id = "CENTOSARTWORK" -heights = "200" -fgcolors = "ad7fa8" -bgcolors = "ffffff-0" -formats = "png" - -[corporate.html] -render-type = "asciidoc" -render-flow = "article" -render-from = "corporate.asciidoc" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/corporate.asciidoc.po" -images-from = "${TCAR_BASEDIR}/Artworks/Icons/Webenv/Final" -styles-from = "${TCAR_BASEDIR}/Artworks/Webenv/Docbook/1.69.1/Css" -formats = "xhtml" -render-page = "single chunks" diff --git a/Documentation/Locales/en_US/corporate-colors.svgz.po b/Documentation/Locales/en_US/corporate-colors.svgz.po new file mode 100644 index 0000000..af06926 --- /dev/null +++ b/Documentation/Locales/en_US/corporate-colors.svgz.po @@ -0,0 +1,338 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate-colors.svgz 0.6\n" +"POT-Creation-Date: 2013-11-25 15:31-0500\n" +"PO-Revision-Date: 2013-11-25 15:31-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "image/svg+xml" +msgstr "image/svg+xml" + +#, no-wrap +msgid "1" +msgstr "1" + +#, no-wrap +msgid "2" +msgstr "2" + +#, no-wrap +msgid "3" +msgstr "3" + +#, no-wrap +msgid "4" +msgstr "4" + +#, no-wrap +msgid "5" +msgstr "5" + +#, no-wrap +msgid "6" +msgstr "6" + +#, no-wrap +msgid "7" +msgstr "7" + +#, no-wrap +msgid "8" +msgstr "8" + +#, no-wrap +msgid "9" +msgstr "9" + +#, no-wrap +msgid "10" +msgstr "10" + +#, no-wrap +msgid "11" +msgstr "11" + +#, no-wrap +msgid "12" +msgstr "12" + +#, no-wrap +msgid "13" +msgstr "13" + +#, no-wrap +msgid "14" +msgstr "14" + +#, no-wrap +msgid "15" +msgstr "15" + +#, no-wrap +msgid "16" +msgstr "16" + +#, no-wrap +msgid "17" +msgstr "17" + +#, no-wrap +msgid "18" +msgstr "18" + +#, no-wrap +msgid "19" +msgstr "19" + +#, no-wrap +msgid "20" +msgstr "20" + +#, no-wrap +msgid "21" +msgstr "21" + +#, no-wrap +msgid "22" +msgstr "22" + +#, no-wrap +msgid "23" +msgstr "23" + +#, no-wrap +msgid "24" +msgstr "24" + +#, no-wrap +msgid "25" +msgstr "25" + +#, no-wrap +msgid "26" +msgstr "26" + +#, no-wrap +msgid "27" +msgstr "27" + +#, no-wrap +msgid "28" +msgstr "28" + +#, no-wrap +msgid "29" +msgstr "29" + +#, no-wrap +msgid "30" +msgstr "30" + +#, no-wrap +msgid "31" +msgstr "31" + +#, no-wrap +msgid "32" +msgstr "32" + +#, no-wrap +msgid "33" +msgstr "33" + +#, no-wrap +msgid "34" +msgstr "34" + +#, no-wrap +msgid "35" +msgstr "35" + +#, no-wrap +msgid "36" +msgstr "36" + +#, no-wrap +msgid "37" +msgstr "37" + +#, no-wrap +msgid "38" +msgstr "38" + +#, no-wrap +msgid "39" +msgstr "39" + +#, no-wrap +msgid "0" +msgstr "0" + +#, no-wrap +msgid "0 = ffffffff" +msgstr "0 = ffffffff" + +#, no-wrap +msgid "1 = eec73eff " +msgstr "1 = eec73eff " + +#, no-wrap +msgid "2 = f0a513ff" +msgstr "2 = f0a513ff" + +#, no-wrap +msgid "3 = fb8b00ff " +msgstr "3 = fb8b00ff " + +#, no-wrap +msgid "4 = f44800ff" +msgstr "4 = f44800ff" + +#, no-wrap +msgid "5 = f44800ff " +msgstr "5 = f44800ff " + +#, no-wrap +msgid "6 = fd3301ff" +msgstr "6 = fd3301ff" + +#, no-wrap +msgid "7 = d40000ff" +msgstr "7 = d40000ff" + +#, no-wrap +msgid "8 = 980101ff" +msgstr "8 = 980101ff" + +#, no-wrap +msgid "9 = fdd99bff" +msgstr "9 = fdd99bff" + +#, no-wrap +msgid "10 = 336699ff" +msgstr "10 = 336699ff" + +#, no-wrap +msgid "11 = 003366ff" +msgstr "11 = 003366ff" + +#, no-wrap +msgid "12 = b3defdff" +msgstr "12 = b3defdff" + +#, no-wrap +msgid "13 = 0197fdff" +msgstr "13 = 0197fdff" + +#, no-wrap +msgid "14 = 0169c9ff" +msgstr "14 = 0169c9ff" + +#, no-wrap +msgid "15 = 002b3dff" +msgstr "15 = 002b3dff" + +#, no-wrap +msgid "16 = ad7fa8ff" +msgstr "16 = ad7fa8ff" + +#, no-wrap +msgid "17 = 75507bff" +msgstr "17 = 75507bff" + +#, no-wrap +msgid "18 = 5c3566ff" +msgstr "18 = 5c3566ff" + +#, no-wrap +msgid "19 = eeeeeeff" +msgstr "19 = eeeeeeff" + +#, no-wrap +msgid "20 = ffff99ff" +msgstr "20 = ffff99ff" + +#, no-wrap +msgid "21 = ffff00ff " +msgstr "21 = ffff00ff " + +#, no-wrap +msgid "22 = fdca01ff " +msgstr "22 = fdca01ff " + +#, no-wrap +msgid "23 = 986601ff " +msgstr "23 = 986601ff " + +#, no-wrap +msgid "24 = ffff99ff " +msgstr "24 = ffff99ff " + +#, no-wrap +msgid "25 = 816647ff " +msgstr "25 = 816647ff " + +#, no-wrap +msgid "26 = 565248ff " +msgstr "26 = 565248ff " + +#, no-wrap +msgid "27 = aacceeff " +msgstr "27 = aacceeff " + +#, no-wrap +msgid "28 = 6699ccff" +msgstr "28 = 6699ccff" + +#, no-wrap +msgid "29 = d9bb7aff" +msgstr "29 = d9bb7aff" + +#, no-wrap +msgid "30 = ccff99ff " +msgstr "30 = ccff99ff " + +#, no-wrap +msgid "31 = 98fc66ff " +msgstr "31 = 98fc66ff " + +#, no-wrap +msgid "32 = 339900ff " +msgstr "32 = 339900ff " + +#, no-wrap +msgid "33 = 015a01ff" +msgstr "33 = 015a01ff" + +#, no-wrap +msgid "34 = 013397ff" +msgstr "34 = 013397ff" + +#, no-wrap +msgid "35 = aaaaaaff" +msgstr "35 = aaaaaaff" + +#, no-wrap +msgid "36 = 888888ff" +msgstr "36 = 888888ff" + +#, no-wrap +msgid "37 = 666666ff" +msgstr "37 = 666666ff" + +#, no-wrap +msgid "38 = 333333ff" +msgstr "38 = 333333ff" + +#, no-wrap +msgid "39 = 000000ff" +msgstr "39 = 000000ff" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/corporate-fonts.svgz.po b/Documentation/Locales/en_US/corporate-fonts.svgz.po new file mode 100644 index 0000000..8547f34 --- /dev/null +++ b/Documentation/Locales/en_US/corporate-fonts.svgz.po @@ -0,0 +1,77 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate-fonts.svgz 0.6\n" +"POT-Creation-Date: 2013-11-26 22:08-0500\n" +"PO-Revision-Date: 2013-11-26 22:08-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "image/svg+xml" +msgstr "image/svg+xml" + +msgid "denmark.svg" +msgstr "denmark.svg" + +msgid "2011-07-23" +msgstr "2011-07-23" + +msgid "The CentOS Artwork SIG" +msgstr "The CentOS Artwork SIG" + +msgid "" +"https://projects.centos.org/svn/artwork/trunk/Identity/Models/Manuals/Fonts/" +"denmark.svg" +msgstr "" +"https://projects.centos.org/svn/artwork/trunk/Identity/Models/Manuals/Fonts/" +"denmark.svg" + +msgid "en_US" +msgstr "en_US" + +msgid "Identity" +msgstr "Identity" + +msgid "Models" +msgstr "Models" + +msgid "Manuals" +msgstr "Manuals" + +msgid "Fonts" +msgstr "Fonts" + +#, no-wrap +msgid "URW Gothic L" +msgstr "URW Gothic L" + +#, no-wrap +msgid "Aa" +msgstr "Aa" + +#, no-wrap +msgid "Denmark" +msgstr "Denmark" + +#, no-wrap +msgid "DejaVu LGC Sans" +msgstr "DejaVu LGC Sans" + +#, no-wrap +msgid "Regular" +msgstr "Regular" + +#, no-wrap +msgid "Bold" +msgstr "Bold" + +#, no-wrap +msgid "Oblique" +msgstr "Oblique" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/corporate-logo-howto.svgz.po b/Documentation/Locales/en_US/corporate-logo-howto.svgz.po new file mode 100644 index 0000000..4e19922 --- /dev/null +++ b/Documentation/Locales/en_US/corporate-logo-howto.svgz.po @@ -0,0 +1,100 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate-logo-howto.svgz 0.6\n" +"POT-Creation-Date: 2013-11-26 22:06-0500\n" +"PO-Revision-Date: 2013-11-26 22:06-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "image/svg+xml" +msgstr "image/svg+xml" + +msgid "centos.svg" +msgstr "centos.svg" + +msgid "2011-08-02" +msgstr "2011-08-02" + +msgid "The CentOS Project" +msgstr "The CentOS Project" + +msgid "" +"https://projects.centos.org/svn/artwork/trunk/Identity/Models/Manuals/Brands/" +"Logos/centos.svg" +msgstr "" +"https://projects.centos.org/svn/artwork/trunk/Identity/Models/Manuals/Brands/" +"Logos/centos.svg" + +msgid "en_US" +msgstr "en_US" + +msgid "Identity" +msgstr "Identity" + +msgid "Models" +msgstr "Models" + +msgid "Manuals" +msgstr "Manuals" + +msgid "Brands" +msgstr "Brands" + +msgid "Logos" +msgstr "Logos" + +#, no-wrap +msgid "D" +msgstr "D" + +#, no-wrap +msgid "Content Area" +msgstr "Content Area" + +#, no-wrap +msgid "Protection Area" +msgstr "Protection Area" + +#, no-wrap +msgid "B = C % 34" +msgstr "B = C % 34" + +#, no-wrap +msgid "A = B" +msgstr "A = B" + +#, no-wrap +msgid "D = C % 16" +msgstr "D = C % 16" + +#, no-wrap +msgid "E = B * 2" +msgstr "E = B * 2" + +#, no-wrap +msgid "C" +msgstr "C" + +#, no-wrap +msgid "B" +msgstr "B" + +#, no-wrap +msgid "A" +msgstr "A" + +#, no-wrap +msgid "E" +msgstr "E" + +#, no-wrap +msgid "6" +msgstr "6" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/corporate-symbol-howto-1of4.svgz.po b/Documentation/Locales/en_US/corporate-symbol-howto-1of4.svgz.po new file mode 100644 index 0000000..2f78c53 --- /dev/null +++ b/Documentation/Locales/en_US/corporate-symbol-howto-1of4.svgz.po @@ -0,0 +1,76 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate-symbol-howto-1of4.svgz 0.6\n" +"POT-Creation-Date: 2013-11-26 22:06-0500\n" +"PO-Revision-Date: 2013-11-26 22:06-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "image/svg+xml" +msgstr "image/svg+xml" + +msgid "figure-1.svg" +msgstr "figure-1.svg" + +msgid "2011-04-18" +msgstr "2011-04-18" + +msgid "The CentOS Project" +msgstr "The CentOS Project" + +msgid "http://www.centos.org/" +msgstr "http://www.centos.org/" + +msgid "en_US" +msgstr "en_US" + +msgid "Identity" +msgstr "Identity" + +msgid "Models" +msgstr "Models" + +msgid "Manual" +msgstr "Manual" + +msgid "Brands" +msgstr "Brands" + +msgid "Symbols" +msgstr "Symbols" + +#, no-wrap +msgid "A" +msgstr "A" + +#, no-wrap +msgid "B" +msgstr "B" + +#, no-wrap +msgid "A = 32mm" +msgstr "A = 32mm" + +#, no-wrap +msgid "B = 2mm" +msgstr "B = 2mm" + +#, no-wrap +msgid "A = 45mm" +msgstr "A = 45mm" + +#, no-wrap +msgid "A = 15mm" +msgstr "A = 15mm" + +#, no-wrap +msgid "B = 1mm" +msgstr "B = 1mm" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/corporate-symbol-howto-2of4.svgz.po b/Documentation/Locales/en_US/corporate-symbol-howto-2of4.svgz.po new file mode 100644 index 0000000..175e4ce --- /dev/null +++ b/Documentation/Locales/en_US/corporate-symbol-howto-2of4.svgz.po @@ -0,0 +1,80 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate-symbol-howto-2of4.svgz 0.6\n" +"POT-Creation-Date: 2013-11-26 22:06-0500\n" +"PO-Revision-Date: 2013-11-26 22:06-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "image/svg+xml" +msgstr "image/svg+xml" + +msgid "figure-2.svg" +msgstr "figure-2.svg" + +msgid "2011-04-18" +msgstr "2011-04-18" + +msgid "The CentOS Project" +msgstr "The CentOS Project" + +msgid "http://www.centos.org/" +msgstr "http://www.centos.org/" + +msgid "en_US" +msgstr "en_US" + +msgid "Identity" +msgstr "Identity" + +msgid "Models" +msgstr "Models" + +msgid "Manual" +msgstr "Manual" + +msgid "Brands" +msgstr "Brands" + +msgid "Symbols" +msgstr "Symbols" + +#, no-wrap +msgid "3. Fill 90° squares with color." +msgstr "3. Fill 90° squares with color." + +#, no-wrap +msgid "1. Create 90° square set." +msgstr "1. Create 90° square set." + +#, no-wrap +msgid "2. Create 45° square set." +msgstr "2. Create 45° square set." + +#, no-wrap +msgid "4. Align both 90° and 45° square sets." +msgstr "4. Align both 90° and 45° square sets." + +#, no-wrap +msgid "9CCD2A" +msgstr "9CCD2A" + +#, no-wrap +msgid "932279" +msgstr "932279" + +#, no-wrap +msgid "EFA724" +msgstr "EFA724" + +#, no-wrap +msgid "262577" +msgstr "262577" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/corporate-symbol-howto-3of4.svgz.po b/Documentation/Locales/en_US/corporate-symbol-howto-3of4.svgz.po new file mode 100644 index 0000000..cb099ab --- /dev/null +++ b/Documentation/Locales/en_US/corporate-symbol-howto-3of4.svgz.po @@ -0,0 +1,80 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate-symbol-howto-3of4.svgz 0.6\n" +"POT-Creation-Date: 2013-11-26 22:06-0500\n" +"PO-Revision-Date: 2013-11-26 22:06-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "image/svg+xml" +msgstr "image/svg+xml" + +msgid "figure-3.svg" +msgstr "figure-3.svg" + +msgid "2011-04-18" +msgstr "2011-04-18" + +msgid "The CentOS Project" +msgstr "The CentOS Project" + +msgid "http://www.centos.org/" +msgstr "http://www.centos.org/" + +msgid "en_US" +msgstr "en_US" + +msgid "Identity" +msgstr "Identity" + +msgid "Models" +msgstr "Models" + +msgid "Manual" +msgstr "Manual" + +msgid "Brands" +msgstr "Brands" + +msgid "Symbols" +msgstr "Symbols" + +#, no-wrap +msgid "5. Create semi-transparent guide." +msgstr "5. Create semi-transparent guide." + +#, no-wrap +msgid "8. Set arrows color information." +msgstr "8. Set arrows color information." + +#, no-wrap +msgid "6. Draw arrow over the guide." +msgstr "6. Draw arrow over the guide." + +#, no-wrap +msgid "7. Duplicate and rotate arrows." +msgstr "7. Duplicate and rotate arrows." + +#, no-wrap +msgid "9CCD2A" +msgstr "9CCD2A" + +#, no-wrap +msgid "932279" +msgstr "932279" + +#, no-wrap +msgid "EFA724" +msgstr "EFA724" + +#, no-wrap +msgid "262577" +msgstr "262577" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/corporate-symbol-howto-4of4.svgz.po b/Documentation/Locales/en_US/corporate-symbol-howto-4of4.svgz.po new file mode 100644 index 0000000..e03dbd3 --- /dev/null +++ b/Documentation/Locales/en_US/corporate-symbol-howto-4of4.svgz.po @@ -0,0 +1,64 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate-symbol-howto-4of4.svgz 0.6\n" +"POT-Creation-Date: 2013-11-26 22:06-0500\n" +"PO-Revision-Date: 2013-11-26 22:06-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "image/svg+xml" +msgstr "image/svg+xml" + +msgid "figure-4.svg" +msgstr "figure-4.svg" + +msgid "2011-04-18" +msgstr "2011-04-18" + +msgid "The CentOS Project" +msgstr "The CentOS Project" + +msgid "http://www.centos.org/" +msgstr "http://www.centos.org/" + +msgid "en_US" +msgstr "en_US" + +msgid "Identity" +msgstr "Identity" + +msgid "Models" +msgstr "Models" + +msgid "Manual" +msgstr "Manual" + +msgid "Brands" +msgstr "Brands" + +msgid "Symbols" +msgstr "Symbols" + +#, no-wrap +msgid "9. The final squares set." +msgstr "9. The final squares set." + +#, no-wrap +msgid "12. Move arrow set lower to bottom." +msgstr "12. Move arrow set lower to bottom." + +#, no-wrap +msgid "10. The final arrows set." +msgstr "10. The final arrows set." + +#, no-wrap +msgid "11. Align squares and arrows final sets." +msgstr "11. Align squares and arrows final sets." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/corporate-themes.svgz.po b/Documentation/Locales/en_US/corporate-themes.svgz.po new file mode 100644 index 0000000..4d414fc --- /dev/null +++ b/Documentation/Locales/en_US/corporate-themes.svgz.po @@ -0,0 +1,50 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate-themes.svgz 0.6\n" +"POT-Creation-Date: 2013-11-25 15:32-0500\n" +"PO-Revision-Date: 2013-11-25 15:32-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "image/svg+xml" +msgstr "image/svg+xml" + +#, no-wrap +msgid "PO" +msgstr "PO" + +#, no-wrap +msgid "FILES" +msgstr "FILES" + +#, no-wrap +msgid "ARTISTIC MOTIFS" +msgstr "ARTISTIC MOTIFS" + +#, no-wrap +msgid "(PNG FILES)" +msgstr "(PNG FILES)" + +#, no-wrap +msgid "SVGZ" +msgstr "SVGZ" + +#, no-wrap +msgid "FINAL IMAGES" +msgstr "FINAL IMAGES" + +#, no-wrap +msgid "${LANG}" +msgstr "${LANG}" + +#, no-wrap +msgid "AUTOMATION SCRIPTS" +msgstr "AUTOMATION SCRIPTS" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/corporate.asciidoc.po b/Documentation/Locales/en_US/corporate.asciidoc.po new file mode 100644 index 0000000..b223b5a --- /dev/null +++ b/Documentation/Locales/en_US/corporate.asciidoc.po @@ -0,0 +1,868 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-26 22:11-0500\n" +"PO-Revision-Date: 2013-11-26 22:11-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +msgid "@@image: 'corporate.png'; md5=74237f14692aec6fe7c2818dc165c565" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +msgid "" +"@@image: 'corporate-logo-howto.png'; md5=62edef37b7167fc07cbbd78789f2d6ea" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +msgid "@@image: 'corporate-fonts.png'; md5=6817553208dfeabfe31081bb95073731" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +msgid "" +"@@image: '../corporate-colors.png'; md5=66b784d031893eb05fbbf1b514cea60d" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +msgid "" +"@@image: '../corporate-clothes-head.png'; " +"md5=9225ce1a9deceb35a95dee726efcce40" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +msgid "" +"@@image: '../corporate-clothes-torso.png'; " +"md5=1f3991d8b08b9a03d4819e1c0803a5a8" +msgstr "" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +msgid "@@image: 'corporate-themes.png'; md5=cd1fe57ab37ee9857780087149cb6b5f" +msgstr "" + +msgid "The CentOS Project Corporate Visual Identity" +msgstr "The CentOS Project Corporate Visual Identity" + +msgid "Jul 2013" +msgstr "Jul 2013" + +msgid "Alain" +msgstr "Alain" + +msgid "Reguera" +msgstr "Reguera" + +msgid "Delgado" +msgstr "Delgado" + +msgid "al@centos.org.cu" +msgstr "al@centos.org.cu" + +msgid "ARD" +msgstr "ARD" + +msgid "1.0" +msgstr "1.0" + +msgid "" +"The CentOS Project Corporate Identity is the “persona” of the organization " +"known as The CentOS Project. The CentOS Project Corporate Identity plays a " +"significant role in the way The CentOS Project, as organization, presents " +"itself to both internal and external stakeholders. In general terms, The " +"CentOS Project Corporate Identity expresses the values and ambitions of The " +"CentOS Project organization, its business, and its characteristics." +msgstr "" +"The CentOS Project Corporate Identity is the “persona” of the organization " +"known as The CentOS Project. The CentOS Project Corporate Identity plays a " +"significant role in the way The CentOS Project, as organization, presents " +"itself to both internal and external stakeholders. In general terms, The " +"CentOS Project Corporate Identity expresses the values and ambitions of The " +"CentOS Project organization, its business, and its characteristics." + +#, fuzzy +msgid "" +"The CentOS Project Corporate Identity provides visibility, recognizability, " +"reputation, structure and identification to The CentOS Project organization " +"by means of Corporate Design, Corporate Communication, and Corporate " +"Behavior." +msgstr "" +"The CentOS Project Corporate Identity provides visibility, recognizability, " +"reputation, structure and identification to The CentOS Project organization " +"by means of Corporate Design, Corporate Communication, and Corporate " +"Behaviour." + +msgid "The CentOS Project Corporate Identity" +msgstr "The CentOS Project Corporate Identity" + +msgid "corporate.png" +msgstr "corporate.png" + +msgid "Corporate Mission" +msgstr "Corporate Mission" + +msgid "" +"The CentOS Project exists to produce The CentOS Distribution, an Enterprise-" +"class Linux Distribution derived from sources freely provided to the public " +"by a prominent North American Enterprise Linux vendor. The CentOS " +"Distribution conforms fully with the upstream vendors redistribution policy " +"and aims to be 100% binary compatible. (The CentOS Distribution mainly " +"changes packages to remove upstream vendor branding and artwork.)." +msgstr "" +"The CentOS Project exists to produce The CentOS Distribution, an Enterprise-" +"class Linux Distribution derived from sources freely provided to the public " +"by a prominent North American Enterprise Linux vendor. The CentOS " +"Distribution conforms fully with the upstream vendors redistribution policy " +"and aims to be 100% binary compatible. (The CentOS Distribution mainly " +"changes packages to remove upstream vendor branding and artwork.)." + +msgid "" +"The CentOS Distribution is developed by a small but growing team of core " +"developers. In turn the core developers are supported by an active user " +"community including system administrators, network administrators, " +"enterprise users, managers, core Linux contributors and Linux enthusiasts " +"from around the world." +msgstr "" +"The CentOS Distribution is developed by a small but growing team of core " +"developers. In turn the core developers are supported by an active user " +"community including system administrators, network administrators, " +"enterprise users, managers, core Linux contributors and Linux enthusiasts " +"from around the world." + +msgid "" +"The CentOS Distribution has numerous advantages including: an active and " +"growing user community, quickly rebuilt, tested, and QA'ed errata packages, " +"an extensive mirror network, developers who are contactable and responsive " +"of a reliable Enterprise-class Linux Distribution, multiple free support " +"avenues including a Wiki, " +"IRC " +"Chat, Email Lists, " +"Forums, and a " +"dynamic FAQ." +msgstr "" +"The CentOS Distribution has numerous advantages including: an active and " +"growing user community, quickly rebuilt, tested, and QA'ed errata packages, " +"an extensive mirror network, developers who are contactable and responsive " +"of a reliable Enterprise-class Linux Distribution, multiple free support " +"avenues including a Wiki, " +"IRC " +"Chat, Email Lists, " +"Forums, and a " +"dynamic FAQ." + +msgid "Corporate Graphic Design" +msgstr "Corporate Graphic Design" + +#, fuzzy +msgid "" +"Corporate graphic design is focused on the presentation of corporate " +"messages with efficiency and efficacy. Corporate graphic design is a " +"cornerstone of corporate visual identity. When the organization doesn't take " +"control over the corporate messages it produces, the organization is letting " +"that area of its identity to the unknown and the result might be good or not " +"so good, it is hard to know. Even the organization doesn't take control over " +"its corporate messages they are always talking about the organization. " +"Taking control of corporate messages presentation is a decision the " +"organization needs to take by itself, based on its need of better describe " +"what it is. To work out the corporate graphic design of an organization it " +"is required to identify which are the visual manifestations the organization " +"reflects its existence on." +msgstr "" +"When the organization doesn't take control over the corporate messages it " +"produces, the organization is letting that area of its identity to the " +"unknown and the results might be good or not so good, it is hard to know. " +"The issue to see here is that even the organization doesn't take control " +"over its corporate messages, they are always talking about the organization. " +"Taking control of corporate messages is a decision the organization needs to " +"take by itself, based on its need of better describe what it is." + +msgid "" +"The CentOS Artwork SIG has identified the following visual manifestations " +"for The CentOS Project organization:" +msgstr "" + +msgid "GNU/Linux Distribution — to control the operating system appearance." +msgstr "" + +msgid "Web environment — to control the web applications appearance." +msgstr "" + +msgid "Promotion — to control the industrial media appearance." +msgstr "" + +#, fuzzy +msgid "Corporate Brand" +msgstr "Corporate Behaviour" + +msgid "" +"The corporate brand is the graphical identification of an organization. The " +"CentOS Artwork SIG uses The CentOS Brand to connect all the visual " +"manifestations The CentOS Project is made of (e.g., GNU/Linux Distributions, " +"Websites, Stationery, etc.) and, this way, it provides visual recognition " +"among similar projects available on the Internet." +msgstr "" + +msgid "" +"The CentOS Brand is composed of a graphical component known as The CentOS " +"Symbol and a typographical component known as The CentOS Type. When The " +"CentOS Symbol and The CentOS Type are put together, they create what we know " +"as The CentOS Logo. All the components that make The CentOS Brand can be " +"used together or separately, considering that, in hierarchy order, The " +"CentOS Logo is rather preferred than The CentOS Symbol, as well as The " +"CentOS Symbol is rather preferred than The CentOS Type alone." +msgstr "" + +#, fuzzy +msgid "corporate-logo-howto.png" +msgstr "corporate.png" + +msgid "" +"The CentOS Brand must be exactly the same every time it is printed out, no " +"matter what the medium is. A route to reproduce The CentOS Brand this way " +"must be used so as to avoid reproduction mistakes of any kind when final " +"images are branded with it. To prevent such mistakes, The CentOS Artwork SIG " +"uses configuration files and the render " +"module of centos-art.sh script to " +"produce PNG brand images of different sizes and colors that can be combined " +"later with other images instead of manipulating The CentOS Brand in SVG " +"format inside each different design model that requires it. This also grants " +"a single point of change for all brands already applied on final images. In " +"this environment, if you make a change to brands SVG files, they will be " +"propagated to all final images the next time you render them." +msgstr "" + +msgid "" +"The CentOS Symbol is the graphical part of The CentOS Logo. As The CentOS " +"Logo, The CentOS Symbol is used to “brand” images produced by The CentOS " +"Project and provide visual connection between images so they can be " +"monolithically recognized as part of The CentOS Project. The CentOS Symbol " +"must be exactly the same every time it is printed out and a route to " +"reproduce it in such a way must be available so as to avoid reproduction " +"mistakes when images are branded with it." +msgstr "" + +msgid "" +"The CentOS Type is the typographical part of The CentOS Logo. The CentOS " +"Type is used to “brand” images produce by The CentOS Project and provide " +"visual connection between images so they can be monolithically recognized as " +"part of The CentOS Project. The CentOS Type alone provides less recognition " +"than The CentOS Logo and The CentOS Symbol. Frequently, The CentOS Type is " +"used to advert the major release of CentOS Distribution on the first images " +"shown as part of Distribution installation process. The CentOS Symbol and " +"any release information printed out with it must have exactly the same " +"proportions every time they are printed out." +msgstr "" + +#, fuzzy +msgid "Corporate Fonts" +msgstr "Corporate Mission" + +msgid "" +"The CentOS Artwork SIG uses the following font files in their corporate " +"graphic designs:" +msgstr "" + +#, fuzzy +msgid "corporate-fonts.png" +msgstr "corporate.png" + +#, fuzzy +msgid "Corporate Colors" +msgstr "Corporate Behaviour" + +msgid "" +"In addition to colors used in The CentOS Symbol (9ccd2aff, 932279ff, " +"262577ff, efa724ff) and The CentOS Default Background Color (204c8dff), The " +"CentOS Artwork SIG uses the following colors in their corporate graphic " +"designs:" +msgstr "" + +#, fuzzy +msgid "corporate-colors.png" +msgstr "corporate.png" + +msgid "" +"Artistic motifs have not any limitation in the number of colors used. If you " +"are a graphic designer creating artistic motifs for The CentOS Project, feel " +"free to take your creativeness at its limit by creating color-full artistic " +"motifs. For final bootup images which require a reduced number of colors, " +"create palette of colors for them with the appropriate number of colors and " +"let the render module of centos-art.sh script to do the rest." +msgstr "" + +#, fuzzy +msgid "Corporate Clothes" +msgstr "Corporate Structure" + +msgid "" +"The CentOS clothes identify the The CentOS Project representative people at " +"public presentations." +msgstr "" + +#, fuzzy +msgid "corporate-clothes-cap.png" +msgstr "corporate.png" + +#, fuzzy +msgid "corporate-clothes-shirt.png" +msgstr "corporate.png" + +#, fuzzy +msgid "Corporate Themes" +msgstr "Corporate Mission" + +msgid "" +"The CentOS themes organize visual styles for all the visual manifestation " +"The CentOS Project is made of. In order to automate the process of rendering " +"images based on customizable patterns, themes have been divided into “design " +"models”, “localization files,” and “artistic motifs.”" +msgstr "" + +#, fuzzy +msgid "corporate-themes.png" +msgstr "corporate.png" + +#, fuzzy +msgid "Design Models" +msgstr "The CentOS Web" + +msgid "" +"Design models are compressed SVG files created with Inkscape. They describe " +"the image files used to implement the CentOS project visual manifestations. " +"For example, in the specific case of CentOS distribution, each final image " +"you want to re-brand has a design model associated used to set the final " +"image dimensions, whether or not it has round borders, and what background " +"to use on it. Design models are created once and rarely modified through " +"time. They are only modified if the visual manifestation they refer to " +"changes or needs to be tuned up." +msgstr "" + +msgid "Localization Files" +msgstr "" + +msgid "" +"Localization files provide localization for messages inside design models. " +"For example, if you decide to use slide images in CentOS installer, you need " +"to create one design model for each slide image you want to produce in " +"English language. Then, using locale " +"module, you create PO files for each design model you have. PO files are " +"created using the current language information of your terminal (e.g., see " +"value of LANG variable). Then you use the locale module again to edit the PO files and provide " +"string translations from English to your preferred language. Once " +"translations are on the PO files, you use the render module to produce images for your preferred language, " +"based on the artistic motif you initiate rendition for and the related " +"design models set in the rendition configuration file." +msgstr "" + +msgid "Artistic Motifs" +msgstr "" + +msgid "" +"Artistic motifs are PNG images holding the look and feel of each design " +"model available. One important characteristic of artistic motifs is " +"preserving one unique visual style for all the PNG images they are made of. " +"Artistic motifs aren't limited in number. It is possible to have several " +"artistic motifs and produce final images for all of them using one single " +"set of design models. Artistic motifs give plenty of room for graphic " +"designers' creativeness. As convention, artistic motifs are conceived " +"without any specific brand information on them. The brand information is set " +"using brand images later, when final images are produced." +msgstr "" + +msgid "Corporate Communication" +msgstr "Corporate Communication" + +msgid "" +"The CentOS Project corporate communication is focused on the effective " +"propagation of corporate messages. Propagation of corporate messages is " +"closely related to the media the organization uses as vehicle to distribute " +"its corporate messages." +msgstr "" +"The CentOS Project corporate communication is focused on the effective " +"propagation of corporate messages. Propagation of corporate messages is " +"closely related to the media the organization uses as vehicle to distribute " +"its corporate messages." + +msgid "" +"The CentOS Project corporate communication takes place through the following " +"visual manifestations:" +msgstr "" +"The CentOS Project corporate communication takes place through the following " +"visual manifestations:" + +msgid "The CentOS Distribution" +msgstr "The CentOS Distribution" + +msgid "" +"This visual manifestation communicates its existence through software " +"packages. There are packages that make a remarkable use of images, packages " +"that make a moderate use of images, and packages that don't use images at " +"all. This visual manifestation is focused on providing The CentOS Project " +"images required by software packages that do use images in a remarkable way, " +"specially those holding the upstream brand (e.g., anaconda, grub, syslinux, " +"gdm, kdebase)." +msgstr "" +"This visual manifestation communicates its existence through software " +"packages. There are packages that make a remarkable use of images, packages " +"that make a moderate use of images, and packages that don't use images at " +"all. This visual manifestation is focused on providing The CentOS Project " +"images required by software packages that do use images in a remarkable way, " +"specially those holding the upstream brand (e.g., anaconda, grub, syslinux, " +"gdm, kdebase)." + +#, fuzzy +msgid "" +"The Community Enterprise Operating System itself (communicates the essence " +"of The CentOS Project existence.)." +msgstr "" +"The Community Enterprise Operating System itself (communicates the essense " +"of The CentOS Project existence.)." + +msgid "" +"Release Schema (Lifetime) and all the stuff related (e.g., Release Notes, " +"Documentation, Erratas, etc.)." +msgstr "" +"Release Schema (Lifetime) and all the stuff related (e.g., Release Notes, " +"Documentation, Erratas, etc.)." + +msgid "The CentOS Web" +msgstr "The CentOS Web" + +msgid "" +"This visual manifestation communicates its existence through web " +"applications. These web applications are free software and come from " +"different providers which distribute their work with predefined visual " +"styles. Frequently, these predefined visual styles have no visual relation " +"among themselves and introduce some visual contradictions when they all are " +"put together. Removing these visual contradictions is object of work for " +"this visual manifestation." +msgstr "" +"This visual manifestation communicates its existence through web " +"applications. These web applications are free software and come from " +"different providers which distribute their work with predefined visual " +"styles. Frequently, these predefined visual styles have no visual relation " +"among themselves and introduce some visual contradictions when they all are " +"put together. Removing these visual contradictions is object of work for " +"this visual manifestation." + +msgid "The CentOS Chat." +msgstr "The CentOS Chat." + +msgid "The CentOS Mailing Lists." +msgstr "The CentOS Mailing Lists." + +msgid "The CentOS Forums." +msgstr "The CentOS Forums." + +msgid "The CentOS Wiki." +msgstr "The CentOS Wiki." + +msgid "Special Interest Groups (SIGs)." +msgstr "Special Interest Groups (SIGs)." + +msgid "Social Events, Interviews, Conferences, etc." +msgstr "Social Events, Interviews, Conferences, etc." + +msgid "" +"The extensive network of mirrors available for downloading ISO files as well " +"as RPMs and SRPMs used to build them up in different architectures." +msgstr "" +"The extensive network of mirrors available for downloading ISO files as well " +"as RPMs and SRPMs used to build them up in different architectures." + +msgid "The CentOS Showroom" +msgstr "The CentOS Showroom" + +msgid "" +"This visual manifestation communicates its existence through production of " +"industrial objects carrying The CentOS Brand. These branded objects are " +"directed to be distributed on social events and/or shops. They provide a way " +"of promotion and commercialization that may help to reduce The CentOS " +"Project expenses (e.g., electrical power, hosting, servers, full-time-" +"developers, etc.), in a similar way as donations may do." +msgstr "" +"This visual manifestation communicates its existence through production of " +"industrial objects carrying The CentOS Brand. These branded objects are " +"directed to be distributed on social events and/or shops. They provide a way " +"of promotion and commercialization that may help to reduce The CentOS " +"Project expenses (e.g., electrical power, hosting, servers, full-time-" +"developers, etc.), in a similar way as donations may do." + +msgid "Stationery (e.g., Posters, Stickers, CD Lables and Sleeves)." +msgstr "Stationery (e.g., Posters, Stickers, CD Lables and Sleeves)." + +msgid "Clothes (e.g., Shirts, T-shirts, Pullovers, Caps)." +msgstr "Clothes (e.g., Shirts, T-shirts, Pullovers, Caps)." + +#, fuzzy +msgid "Installation media (e.g., CDs, DVD, Pen-drives)." +msgstr "Installation media (e.g., CDs, DVD, Pendrives)." + +#, fuzzy +msgid "Corporate Behavior" +msgstr "Corporate Behaviour" + +#, fuzzy +msgid "" +"The CentOS Project corporate behavior is focused on the effective " +"interaction of each member involved in the organization (e.g., core " +"developers, community members, etc.). It is related to ethics and politics " +"used to do the things inside the organization. It is related to the sense of " +"direction chosen by the organization and the way the organization projects " +"itself to achieve it." +msgstr "" +"The CentOS Project corporate behaviour is focused on the effective " +"interaction of each member involved in the organization (e.g., core " +"developers, community members, etc.). It is related to ethics and politics " +"used to do the things inside the organization. It is related to the sense of " +"direction chosen by the organization and they way the organization projects " +"itself to achieve it." + +msgid "" +"The CentOS Project corporate behavior is based on a meritocracy (the more " +"you do the more you are allowed to do)." +msgstr "" + +msgid "Corporate Structure" +msgstr "Corporate Structure" + +msgid "" +"The CentOS Project corporate structure is based on a Monolithic Corporate " +"Visual Identity Structure. In this configuration, one unique name and one " +"unique visual style is used in all visual manifestation The CentOS Project " +"is made of." +msgstr "" +"The CentOS Project corporate structure is based on a Monolithic Corporate " +"Visual Identity Structure. In this configuration, one unique name and one " +"unique visual style is used in all visual manifestation The CentOS Project " +"is made of." + +msgid "" +"In a monolithic corporate visual identity structure, internal and external " +"stakeholders use to feel a strong sensation of uniformity, orientation, and " +"identification with the organization. No matter if you are visiting web " +"sites, using the distribution, or acting on social events, the one unique " +"name and one unique visual style connects them all to say: Hey! we are all " +"part of The CentOS Project." +msgstr "" +"In a monolithic corporate visual identity structure, internal and external " +"stakeholders use to feel a strong sensation of uniformity, orientation, and " +"identification with the organization. No matter if you are visiting web " +"sites, using the distribution, or acting on social events, the one unique " +"name and one unique visual style connects them all to say: Hey! we are all " +"part of The CentOS Project." + +msgid "" +"Other corporate structures for The CentOS Project have been considered as " +"well. Such is the case of producing one different visual style for each " +"major release of The CentOS Distribution. This structure isn't inconvenient " +"at all, but some visual contradictions could be introduced if it isn't " +"applied correctly and we need to be aware of it. To apply it correctly, we " +"need to know what The CentOS Project is made of." +msgstr "" +"Other corporate structures for The CentOS Project have been considered as " +"well. Such is the case of producing one different visual style for each " +"major release of The CentOS Distribution. This structure isn't inconvenient " +"at all, but some visual contradictions could be introduced if it isn't " +"applied correctly and we need to be aware of it. To apply it correctly, we " +"need to know what The CentOS Project is made of." + +#, fuzzy +msgid "" +"The CentOS Project, as organization, is mainly made of (but not limited to) " +"three visual manifestations: The CentOS Distribution, The CentOS Web and The " +"CentOS Showroom. Inside The CentOS Distribution visual manifestations, The " +"CentOS Project maintains near to four different major releases of The CentOS " +"Distribution, in parallel. However, inside The CentOS Web visual " +"manifestations, the content is produced for no specific release information " +"(e.g., there is no a complete web site for each major release of The CentOS " +"Distribution individually, but one web site to cover them all). Likewise, " +"the content produced in The CentOS Showroom is industrially created for no " +"specific release, but The CentOS Project in general." +msgstr "" +"The CentOS Project, as organization, is mainly made of (but not limited to) " +"three visual manifestions: The CentOS Distribution, The CentOS Web and The " +"CentOS Showroom. Inside The CentOS Distribution visual manifestations, The " +"CentOS Project maintains near to four different major releases of The CentOS " +"Distribution, parallely in time. However, inside The CentOS Web visual " +"manifestations, the content is produced for no specific release information " +"(e.g., there is no a complete web site for each major release of The CentOS " +"Distribution individually, but one web site to cover them all). Likewise, " +"the content produced in The CentOS Showroom is industrially created for no " +"specific release, but The CentOS Project in general." + +#, fuzzy +msgid "" +"In order to produce the The CentOS Project Monolithic Corporate Visual " +"Identity Structure correctly, we need to consider all the visual " +"manifestations The CentOS Project is made of, not just one of them. If one " +"different visual style is implemented for each major release of The CentOS " +"Distribution, which one of those different visual styles would be used to " +"cover the remaining visual manifestations The CentOS Project is made of (e." +"g., The CentOS Web and The CentOS Showroom)?" +msgstr "" +"In order to produce the The CentOS Project Monolithic Corporate Visual " +"Identity Structure correctly, we need to concider all the visual " +"manifestations The CentOS Project is made of, not just one of them. If one " +"different visual style is implemented for each major release of The CentOS " +"Distribution, which one of those different visual styles would be used to " +"cover the remaining visual manifestations The CentOS Project is made of (e." +"g., The CentOS Web and The CentOS Showroom)?" + +#, fuzzy +msgid "" +"Probably you are thinking: yes, I see your point, but The CentOS Brand " +"connects them all already, why would we need to join them up into the same " +"visual style too, isn't it more work to do, and harder to maintain? It is " +"true that The CentOS Brand does connect all the visual manifestations it is " +"present on, but that connection is even stronger if one unique visual style " +"backups it. In fact, whatever thing you do to strength the visual connection " +"among The CentOS Project visual manifestations would be very good in favor " +"of The CentOS Project recognition." +msgstr "" +"Harder to maintain, more work to do, probably. Specially when you consider " +"that The CentOS Project has proven stability and consistency through time " +"and, that, certainly, didn't come through swinging magical wands or " +"something but hardly working out to automate tasks and providing maintenance " +"through time. With that in mind, I consider The CentOS Project Corporate " +"Visual Identity Structure must be consequent with such stability and " +"consistency tradition. It is true that The CentOS Brand does connect all the " +"visual manifestations it is present on, but that connection is strengthened " +"if one unique visual style backups it. In fact, whatever thing you do to " +"strength the visual connection among The CentOS Project visual " +"manifestations would be very good in favor of The CentOS Project recognition." + +#, fuzzy +msgid "" +"Having just one visual style in all visual manifestations for eternity would " +"be a very boring thing and would give the idea of a visually out-of-date " +"project. So, there is no problem on creating new visual styles for each new " +"major release of The CentOS Distribution, in order to refresh The CentOS " +"Distribution visual style; the problem itself is in not propagating the new " +"visual style created for the new release of The CentOS Distribution to all " +"other visual manifestations The CentOS Project is made of, in a way The " +"CentOS Project could be recognized no matter what visual manifestation be in " +"front of us. Such lack of uniformity is what introduces the visual " +"contradiction The CentOS Artwork SIG is precisely trying to solve by mean of " +"automating the production of corporate themes inside The CentOS Artwork " +"Repository." +msgstr "" +"Obviously, having just one visual style in all visual manifestations for " +"eternity would be a very boring thing and would give the idea of a visually " +"outdated project. So, there is no problem on creating new visual styles for " +"each new major release of The CentOS Distribution, in order to refresh The " +"CentOS Distribution visual style; the problem itself is in not propagating " +"the new visual style created for the new release of The CentOS Distribution " +"to all other visual manifestations The CentOS Project is made of, in a way " +"The CentOS Project could be recognized no matter what visual manifestation " +"be in front of us. Such lack of uniformity is what introduces the visual " +"contradiction we would be precisely trying to solve by mean of themes " +"production in The CentOS Artwork Repository." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" + +#~ msgid "" +#~ "The corporate design is focused on the effective presentation of " +#~ "corporate messages. As corporate messages we understand all the " +#~ "information emitted from the organization; and when we say all we mean everything that can be perceived through the human " +#~ "senses. The corporate design takes care of defining what this information " +#~ "is and controlling the way it goes out the organization producing it." +#~ msgstr "" +#~ "The corporate design is focused on the effective presentation of " +#~ "corporate messages. As corporate messages we understand all the " +#~ "information emitted from the organization; and when we say all we mean everything that can be perceived through the human " +#~ "senses. The corporate design takes care of defining what this information " +#~ "is and controlling the way it goes out the organization producing it." + +#~ msgid "" +#~ "In the very specific case of The CentOS Project, we'll concentrate our " +#~ "attention on corporate messages that reach us through the visual sense. " +#~ "This is, all the visual manifestations The CentOS Project is made of. As " +#~ "visual manifestations we understand all the visible media The CentOS " +#~ "Project uses to manifest its existence on. At this point it is necessary " +#~ "to consider what The CentOS Project is, what its mission is and what it " +#~ "is producing. This, in order to identify which visual manifestations the " +#~ "organization is demanding attention of corporate design for." +#~ msgstr "" +#~ "In the very specific case of The CentOS Project, we'll concentrate our " +#~ "attention on corporate messages that reach us through the visual sense. " +#~ "This is, all the visual manifestations The CentOS Project is made of. As " +#~ "visual manifestations we understand all the visible media The CentOS " +#~ "Project uses to manifest its existence on. At this point it is necessary " +#~ "to consider what The CentOS Project is, what its mission is and what it " +#~ "is producing. This, in order to identify which visual manifestations the " +#~ "organization is demanding attention of corporate design for." + +#, fuzzy +#~ msgid "The CentOS Visual Manifestations" +#~ msgstr "The CentOS Distribution" + +#, fuzzy +#~ msgid "" +#~ "Inside The CentOS Project applies corporate design to the following " +#~ "visual manifestations:" +#~ msgstr "" +#~ "Inside The CentOS Project we identify and apply corporate design to the " +#~ "following visual manifestations:" + +#~ msgid "" +#~ "The CentOS Distribution: This visual " +#~ "manifestation exists to cover all actions related to artwork production " +#~ "and re-branding, required by The CentOS Distribution in order to comply " +#~ "with upstream's redistribution guidelines." +#~ msgstr "" +#~ "The CentOS Distribution: This visual " +#~ "manifestation exists to cover all actions related to artwork production " +#~ "and re-branding, required by The CentOS Distribution in order to comply " +#~ "with upstream's redistribution guidelines." + +#~ msgid "" +#~ "The CentOS Web: This visual " +#~ "manifestation exists to cover all actions related to artwork production " +#~ "required by The CentOS Project to manifest its existence in the World " +#~ "Wide Web medium." +#~ msgstr "" +#~ "The CentOS Web: This visual " +#~ "manifestation exists to cover all actions related to artwork production " +#~ "required by The CentOS Project to manifest its existence in the World " +#~ "Wide Web medium." + +#~ msgid "" +#~ "The CentOS Showroom: This visual " +#~ "manifestation exists to cover all actions related to artwork production " +#~ "required by The CentOS Project to manifest its existence through media " +#~ "produced industrially (e.g., stationery, clothes, CDs, DVDs, etc.)." +#~ msgstr "" +#~ "The CentOS Showroom: This visual " +#~ "manifestation exists to cover all actions related to artwork production " +#~ "required by The CentOS Project to manifest its existence through media " +#~ "produced industrially (e.g., stationery, clothes, CDs, DVDs, etc.)." + +#, fuzzy +#~ msgid "" +#~ "These visual manifestations seem to cover most media required by The " +#~ "CentOS Project, as organization, to show its existence. However, other " +#~ "visual manifestations could be added in the future, as long as they be " +#~ "needed, to cover different areas like stands, buildings, offices, road " +#~ "transportation or whatever visual manifestation The CentOS Project " +#~ "touches to show its existence." +#~ msgstr "" +#~ "The visual manifestations identified above seem to cover most media " +#~ "required by The CentOS Project, as organization, to show its existence. " +#~ "However, other visual manifestations could be added in the future, as " +#~ "long as they be needed, to cover different areas like stands, buildings, " +#~ "offices, road transportation or whatever visual manifestation The CentOS " +#~ "Project touches to show its existence." + +#~ msgid "" +#~ "Once all visual manifestations have been identified and defined through " +#~ "design models, it is time to visually remark their connection with The " +#~ "CentOS Project. This kind of connection is realized by applying The " +#~ "CentOS Brand to design models inside visual manifestations supported " +#~ "through corporate design." +#~ msgstr "" +#~ "Once all visual manifestations have been identified and defined through " +#~ "design models, it is time to visually remark their connection with The " +#~ "CentOS Project. This kind of connection is realized by applying The " +#~ "CentOS Brand to design models inside visual manifestations supported " +#~ "through corporate design." + +#, fuzzy +#~ msgid "The CentOS Brand" +#~ msgstr "The CentOS Chat." + +#, fuzzy +#~ msgid "The CentOS Brand construction" +#~ msgstr "The CentOS Distribution" + +#, fuzzy +#~ msgid "The CentOS Symbol" +#~ msgstr "The CentOS Web" + +#, fuzzy +#~ msgid "The CentOS Symbol construction (1of4)" +#~ msgstr "The CentOS Distribution" + +#, fuzzy +#~ msgid "corporate-symbol-howto-1of4.png" +#~ msgstr "corporate.png" + +#, fuzzy +#~ msgid "The CentOS Symbol construction (2of4)" +#~ msgstr "The CentOS Distribution" + +#, fuzzy +#~ msgid "corporate-symbol-howto-2of4.png" +#~ msgstr "corporate.png" + +#, fuzzy +#~ msgid "The CentOS Symbol construction (3of4)" +#~ msgstr "The CentOS Distribution" + +#, fuzzy +#~ msgid "corporate-symbol-howto-3of4.png" +#~ msgstr "corporate.png" + +#, fuzzy +#~ msgid "The CentOS Symbol construction (4of4)" +#~ msgstr "The CentOS Distribution" + +#, fuzzy +#~ msgid "corporate-symbol-howto-4of4.png" +#~ msgstr "corporate.png" + +#, fuzzy +#~ msgid "The CentOS Type" +#~ msgstr "The CentOS Web" + +#, fuzzy +#~ msgid "The CentOS Logo" +#~ msgstr "The CentOS Showroom" + +#, fuzzy +#~ msgid "The CentOS Themes" +#~ msgstr "The CentOS Web" + +#, fuzzy +#~ msgid "The CentOS Motifs" +#~ msgstr "The CentOS Forums." + +#~ msgid "" +#~ "The CentOS Project corporate behaviour takes place through The CentOS " +#~ "Project corporate communication, as described above." +#~ msgstr "" +#~ "The CentOS Project corporate behaviour takes place through The CentOS " +#~ "Project corporate communication, as described above." + +#~ msgid "" +#~ "Probably you are thinking: yes, I see your point, but The CentOS Brand " +#~ "connects them all already, why would we need to join them up into the " +#~ "same visual style too, isn't it more work to do, and harder to maintain?" +#~ msgstr "" +#~ "Probably you are thinking: yes, I see your point, but The CentOS Brand " +#~ "connects them all already, why would we need to join them up into the " +#~ "same visual style too, isn't it more work to do, and harder to maintain?" + +#, fuzzy +#~ msgid "" +#~ "@@image: 'Final/corporate-logo-howto.png'; md5=THIS FILE DOESN'T EXIST" +#~ msgstr "@@image: 'corporate.png'; md5=THIS FILE DOESN'T EXIST" diff --git a/Documentation/Locales/en_US/corporate.svgz.po b/Documentation/Locales/en_US/corporate.svgz.po new file mode 100644 index 0000000..18e78bb --- /dev/null +++ b/Documentation/Locales/en_US/corporate.svgz.po @@ -0,0 +1,61 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate.svgz 0.6\n" +"POT-Creation-Date: 2013-11-26 22:08-0500\n" +"PO-Revision-Date: 2013-11-26 22:08-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "The CentOS Project Corporate Identity" +msgstr "The CentOS Project Corporate Identity" + +msgid "image/svg+xml" +msgstr "image/svg+xml" + +msgid "2013-07-23" +msgstr "2013-07-23" + +msgid "Alain Reguera Delgado" +msgstr "Alain Reguera Delgado" + +msgid "The CentOS Project" +msgstr "The CentOS Project" + +msgid "en_US" +msgstr "en_US" + +msgid "Identity" +msgstr "Identity" + +msgid "Models" +msgstr "Models" + +msgid "Manuals" +msgstr "Manuals" + +msgid "Corporate" +msgstr "Corporate" + +#, no-wrap +msgid "COMMUNICATION" +msgstr "COMMUNICATION" + +#, no-wrap +msgid "GRAPHIC DESIGN" +msgstr "GRAPHIC DESIGN" + +#, no-wrap +msgid "STRUCTURE" +msgstr "STRUCTURE" + +#, no-wrap +msgid "BEHAVIOUR" +msgstr "BEHAVIOUR" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/licenses-gfdl.asciidoc b/Documentation/Locales/en_US/licenses-gfdl.asciidoc new file mode 100644 index 0000000..7c9b686 --- /dev/null +++ b/Documentation/Locales/en_US/licenses-gfdl.asciidoc @@ -0,0 +1,876 @@ +msgid "" +msgstr "" +"Project-Id-Version: gfdl.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-13 13:44-0500\n" +"PO-Revision-Date: 2013-11-13 13:44-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "GNU Free Documentation License" +msgstr "GNU Free Documentation License" + +msgid "November 2002" +msgstr "November 2002" + +msgid "Free" +msgstr "Free" + +msgid "Software" +msgstr "Software" + +msgid "Foundation" +msgstr "Foundation" + +msgid "http://www.fsf.org/" +msgstr "http://www.fsf.org/" + +msgid "FSF" +msgstr "FSF" + +msgid "1.2" +msgstr "1.2" + +msgid "" +"Copyright © 2000, 2001, 2002 Free Software Foundation, Inc. 675 Mass Ave, " +"Cambridge, MA 02139, USA" +msgstr "" +"Copyright © 2000, 2001, 2002 Free Software Foundation, Inc. 675 Mass Ave, " +"Cambridge, MA 02139, USA" + +msgid "" +"Everyone is permitted to copy and distribute verbatim copies of this license " +"document, but changing it is not allowed." +msgstr "" +"Everyone is permitted to copy and distribute verbatim copies of this license " +"document, but changing it is not allowed." + +msgid "Preamble" +msgstr "Preamble" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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 " +"GNU General Public License, which is a copyleft license designed for free " +"software." +msgstr "" +"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 " +"GNU General Public License, which is a copyleft license designed for free " +"software." + +msgid "" +"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." +msgstr "" +"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." + +msgid "Applicability and definitions" +msgstr "Applicability and definitions" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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 “<< transparent>>” is called " +"“Opaque”." +msgstr "" +"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 “<< transparent>>” is called " +"“Opaque”." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "Verbatim copying" +msgstr "Verbatim copying" + +msgid "" +"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 ." +msgstr "" +"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 ." + +msgid "" +"You may also lend copies, under the same conditions stated above, and you " +"may publicly display copies." +msgstr "" +"You may also lend copies, under the same conditions stated above, and you " +"may publicly display copies." + +msgid "Copying in quantity" +msgstr "Copying in quantity" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "Modifications" +msgstr "Modifications" + +msgid "" +"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 :" +msgstr "" +"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 :" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"State on the the name of the publisher of the " +", as the publisher." +msgstr "" +"State on the the name of the publisher of the " +", as the publisher." + +msgid "Preserve all the copyright notices of the Document." +msgstr "Preserve all the copyright notices of the Document." + +msgid "" +"Add an appropriate copyright notice for your modifications adjacent to the " +"other copyright notices." +msgstr "" +"Add an appropriate copyright notice for your modifications adjacent to the " +"other copyright notices." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"Preserve in that license notice the full lists of and required given in the " +"Document's license notice." +msgstr "" +"Preserve in that license notice the full lists of and required given in the " +"Document's license notice." + +msgid "Include an unaltered copy of this License." +msgstr "Include an unaltered copy of this License." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"Delete any section Entitled “Endorsements”. Such a section may not be " +"included in the ." +msgstr "" +"Delete any section Entitled “Endorsements”. Such a section may not be " +"included in the ." + +msgid "" +"Do not retitle any existing section to be Entitled “Endorsements” or to " +"conflict in title with any ." +msgstr "" +"Do not retitle any existing section to be Entitled “Endorsements” or to " +"conflict in title with any ." + +msgid "Preserve any Warranty Disclaimers." +msgstr "Preserve any Warranty Disclaimers." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"You may add a section Entitled “Endorsements”, provided it contains nothing " +"but endorsements of your by various " +"parties&ndash;for example, statements of peer review or that the text " +"has been approved by an organization as the authoritative definition of a " +"standard." +msgstr "" +"You may add a section Entitled “Endorsements”, provided it contains nothing " +"but endorsements of your by various " +"parties&ndash;for example, statements of peer review or that the text " +"has been approved by an organization as the authoritative definition of a " +"standard." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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 ." +msgstr "" +"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 ." + +msgid "Combining documents" +msgstr "Combining documents" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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”." +msgstr "" +"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”." + +msgid "Collection of documents" +msgstr "Collection of documents" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "Aggregation with independent works" +msgstr "Aggregation with independent works" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "Translations" +msgstr "Translations" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "Termination" +msgstr "Termination" + +msgid "" +"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." +msgstr "" +"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." + +msgid "Future Revisions of this License" +msgstr "Future Revisions of this License" + +msgid "" +"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 http://www.gnu.org/copyleft/." +msgstr "" +"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 http://www.gnu.org/copyleft/." + +msgid "" +"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." +msgstr "" +"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." + +msgid "How to use this License for your documents" +msgstr "How to use this License for your documents" + +msgid "" +"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:" +msgstr "" +"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:" + +#, no-wrap +msgid "" +"Copyright (C) YEAR YOUR NAME.\n" +"\n" +"Permission is granted to copy, distribute and/or modify this\n" +"document under the terms of the GNU Free Documentation License,\n" +"Version 1.2 or any later version published by the Free Software\n" +"Foundation; with no Invariant Sections, no Front-Cover Texts, and\n" +"no Back-Cover Texts. A copy of the license is included in the\n" +"section entitled ``GNU Free Documentation License''." +msgstr "" +"Copyright (C) YEAR YOUR NAME.\n" +"\n" +"Permission is granted to copy, distribute and/or modify this\n" +"document under the terms of the GNU Free Documentation License,\n" +"Version 1.2 or any later version published by the Free Software\n" +"Foundation; with no Invariant Sections, no Front-Cover Texts, and\n" +"no Back-Cover Texts. A copy of the license is included in the\n" +"section entitled ``GNU Free Documentation License''." + +msgid "" +"If you have , Front-Cover Texts and " +"Back-Cover Texts, replace the “with…Texts”. line with this:" +msgstr "" +"If you have , Front-Cover Texts and " +"Back-Cover Texts, replace the “with…Texts”. line with this:" + +#, no-wrap +msgid "" +"with the Invariant Sections being LIST THEIR TITLES, with the\n" +"Front-Cover Texts being LIST, and with the Back-Cover Texts being\n" +"LIST." +msgstr "" +"with the Invariant Sections being LIST THEIR TITLES, with the\n" +"Front-Cover Texts being LIST, and with the Back-Cover Texts being\n" +"LIST." + +msgid "" +"If you have without , or some other combination of the three, merge those two " +"alternatives to suit the situation." +msgstr "" +"If you have without , or some other combination of the three, merge those two " +"alternatives to suit the situation." + +msgid "" +"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." +msgstr "" +"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." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/licenses-gpl.asciidoc b/Documentation/Locales/en_US/licenses-gpl.asciidoc new file mode 100644 index 0000000..0a61c7a --- /dev/null +++ b/Documentation/Locales/en_US/licenses-gpl.asciidoc @@ -0,0 +1,784 @@ +msgid "" +msgstr "" +"Project-Id-Version: gpl.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-13 13:44-0500\n" +"PO-Revision-Date: 2013-11-13 13:44-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "GNU General Public License" +msgstr "GNU General Public License" + +msgid "June 1991" +msgstr "June 1991" + +msgid "Free" +msgstr "Free" + +msgid "Software" +msgstr "Software" + +msgid "Foundation" +msgstr "Foundation" + +msgid "FSF" +msgstr "FSF" + +msgid "2" +msgstr "2" + +msgid "" +"Copyright © 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, " +"Cambridge, MA 02139, USA" +msgstr "" +"Copyright © 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, " +"Cambridge, MA 02139, USA" + +msgid "" +"Everyone is permitted to copy and distribute verbatim copies of this license " +"document, but changing it is not allowed." +msgstr "" +"Everyone is permitted to copy and distribute verbatim copies of this license " +"document, but changing it is not allowed." + +msgid "Preamble" +msgstr "Preamble" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "We protect your rights with two steps:" +msgstr "We protect your rights with two steps:" + +msgid "copyright the software, and" +msgstr "copyright the software, and" + +msgid "" +"offer you this license which gives you legal permission to copy, distribute " +"and/or modify the software." +msgstr "" +"offer you this license which gives you legal permission to copy, distribute " +"and/or modify the software." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"The precise terms and conditions for copying, distribution and modification " +"follow." +msgstr "" +"The precise terms and conditions for copying, distribution and modification " +"follow." + +msgid "Terms and Conditions for Copying, Distribution and Modification" +msgstr "Terms and Conditions for Copying, Distribution and Modification" + +#, fuzzy +msgid "Section 0" +msgstr "Section 10" + +msgid "" +"This License applies to any program or other work which contains a notice " +"placed by the copyright holder saying it may be distributed under the terms " +"of this General Public License. The “Program”, below, refers to any such " +"program or work, and a “work based on the Program” means either the Program " +"or any derivative work under copyright law: that is to say, a work " +"containing the Program or a portion of it, either verbatim or with " +"modifications and/or translated into another language. (Hereinafter, " +"translation is included without limitation in the term “modification”.) Each " +"licensee is addressed as “you”." +msgstr "" + +msgid "" +"Activities other than copying, distribution and modification are not covered " +"by this License; they are outside its scope. The act of running the Program " +"is not restricted, and the output from the Program is covered only if its " +"contents constitute a work based on the Program (independent of having been " +"made by running the Program). Whether that is true depends on what the " +"Program does." +msgstr "" + +msgid "Section 1" +msgstr "Section 1" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "Section 2" +msgstr "Section 2" + +msgid "" +"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:" +msgstr "" +"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:" + +msgid "" +"You must cause the modified files to carry prominent notices stating that " +"you changed the files and the date of any change." +msgstr "" +"You must cause the modified files to carry prominent notices stating that " +"you changed the files and the date of any change." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "Exception" +msgstr "Exception" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "Section 3" +msgstr "Section 3" + +msgid "" +"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:" +msgstr "" +"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:" + +msgid "" +"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," +msgstr "" +"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," + +msgid "" +"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," +msgstr "" +"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," + +msgid "" +"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.)" +msgstr "" +"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.)" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "Section 4" +msgstr "Section 4" + +msgid "" +"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." +msgstr "" +"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." + +msgid "Section 5" +msgstr "Section 5" + +msgid "" +"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." +msgstr "" +"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." + +msgid "Section 6" +msgstr "Section 6" + +msgid "" +"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." +msgstr "" +"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." + +msgid "Section 7" +msgstr "Section 7" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"This section is intended to make thoroughly clear what is believed to be a " +"consequence of the rest of this License." +msgstr "" +"This section is intended to make thoroughly clear what is believed to be a " +"consequence of the rest of this License." + +msgid "Section 8" +msgstr "Section 8" + +msgid "" +"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." +msgstr "" +"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." + +msgid "Section 9" +msgstr "Section 9" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "Section 10" +msgstr "Section 10" + +msgid "" +"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." +msgstr "" +"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." + +msgid "NO WARRANTY" +msgstr "NO WARRANTY" + +msgid "Section 11" +msgstr "Section 11" + +msgid "" +"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." +msgstr "" +"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." + +msgid "Section 12" +msgstr "Section 12" + +msgid "" +"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." +msgstr "" +"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." + +msgid "End of Terms and Conditions." +msgstr "End of Terms and Conditions." + +msgid "How to Apply These Terms to Your New Programs" +msgstr "How to Apply These Terms to Your New Programs" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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 <quote>" +"copyright</quote> line and a pointer to where the full notice is found." +msgstr "" +"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 <quote>" +"copyright</quote> line and a pointer to where the full notice is found." + +#, no-wrap +msgid "" +"<one line to give the program's name and a brief idea of what it does.>\n" +"Copyright (C) 19yy <name of author>\n" +"\n" +"This program is free software; you can redistribute it and/or modify\n" +"it under the terms of the GNU General Public License as published by\n" +"the Free Software Foundation; either version 2 of the License, or\n" +"(at your option) any later version.\n" +"\n" +"This program is distributed in the hope that it will be useful,\n" +"but WITHOUT ANY WARRANTY; without even the implied warranty of\n" +"MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n" +"GNU General Public License for more details.\n" +"\n" +"You should have received a copy of the GNU General Public License\n" +"along with this program; if not, write to the Free Software\n" +"Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA." +msgstr "" +"<one line to give the program's name and a brief idea of what it does.>\n" +"Copyright (C) 19yy <name of author>\n" +"\n" +"This program is free software; you can redistribute it and/or modify\n" +"it under the terms of the GNU General Public License as published by\n" +"the Free Software Foundation; either version 2 of the License, or\n" +"(at your option) any later version.\n" +"\n" +"This program is distributed in the hope that it will be useful,\n" +"but WITHOUT ANY WARRANTY; without even the implied warranty of\n" +"MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n" +"GNU General Public License for more details.\n" +"\n" +"You should have received a copy of the GNU General Public License\n" +"along with this program; if not, write to the Free Software\n" +"Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA." + +msgid "" +"Also add information on how to contact you by electronic and paper mail." +msgstr "" +"Also add information on how to contact you by electronic and paper mail." + +msgid "" +"If the program is interactive, make it output a short notice like this when " +"it starts in an interactive mode:" +msgstr "" +"If the program is interactive, make it output a short notice like this when " +"it starts in an interactive mode:" + +#, no-wrap +msgid "" +"Gnomovision version 69, Copyright (C) 19yy name of author\n" +"Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n" +"This is free software, and you are welcome to redistribute it\n" +"under certain conditions; type `show c' for details." +msgstr "" +"Gnomovision version 69, Copyright (C) 19yy name of author\n" +"Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n" +"This is free software, and you are welcome to redistribute it\n" +"under certain conditions; type `show c' for details." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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:" +msgstr "" +"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:" + +#, no-wrap +msgid "" +"Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n" +"`Gnomovision' (which makes passes at compilers) written by James Hacker.\n" +"\n" +"<signature of Ty Coon>, 1 April 1989\n" +"Ty Coon, President of Vice" +msgstr "" +"Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n" +"`Gnomovision' (which makes passes at compilers) written by James Hacker.\n" +"\n" +"<signature of Ty Coon>, 1 April 1989\n" +"Ty Coon, President of Vice" + +msgid "" +"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." +msgstr "" +"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." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" + +#~ msgid "" +#~ " <" +#~ "sect2 id=\"licenses-gpl-1-9\" xreflabel=\"Section 9\">" +#~ msgstr "" +#~ " <" +#~ "sect2 id=\"licenses-gpl-1-9\" xreflabel=\"Section 9\">" diff --git a/Documentation/Locales/en_US/repository-infra.svgz.po b/Documentation/Locales/en_US/repository-infra.svgz.po new file mode 100644 index 0000000..8da01ef --- /dev/null +++ b/Documentation/Locales/en_US/repository-infra.svgz.po @@ -0,0 +1,38 @@ +msgid "" +msgstr "" +"Project-Id-Version: repository-infra.svgz 0.6\n" +"POT-Creation-Date: 2013-11-15 10:06-0500\n" +"PO-Revision-Date: 2013-11-15 10:06-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "image/svg+xml" +msgstr "image/svg+xml" + +#, no-wrap +msgid "INTERNET" +msgstr "INTERNET" + +#, no-wrap +msgid "SSL/TLS" +msgstr "SSL/TLS" + +#, no-wrap +msgid "WORKING COPY" +msgstr "WORKING COPY" + +#, no-wrap +msgid "CENTRAL " +msgstr "CENTRAL " + +#, no-wrap +msgid "REPOSITORY" +msgstr "REPOSITORY" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/repository-version-schema.svgz.po b/Documentation/Locales/en_US/repository-version-schema.svgz.po new file mode 100644 index 0000000..b0df349 --- /dev/null +++ b/Documentation/Locales/en_US/repository-version-schema.svgz.po @@ -0,0 +1,157 @@ +msgid "" +msgstr "" +"Project-Id-Version: repository-version-schema.svgz 0.6\n" +"POT-Creation-Date: 2013-11-15 10:06-0500\n" +"PO-Revision-Date: 2013-11-15 10:06-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "repository-version-schema.svgz" +msgstr "repository-version-schema.svgz" + +msgid "image/svg+xml" +msgstr "image/svg+xml" + +msgid "2013-11-13" +msgstr "2013-11-13" + +msgid "Alain Reguera Delgado" +msgstr "Alain Reguera Delgado" + +msgid "The CentOS Project" +msgstr "The CentOS Project" + +msgid "http://www.centos.org/" +msgstr "http://www.centos.org/" + +msgid "en_US" +msgstr "en_US" + +msgid "Identity" +msgstr "Identity" + +msgid "Models" +msgstr "Models" + +msgid "Manual" +msgstr "Manual" + +msgid "Scripts" +msgstr "Scripts" + +msgid "Bash" +msgstr "Bash" + +msgid "Functions" +msgstr "Functions" + +msgid "Path" +msgstr "Path" + +#, no-wrap +msgid "2.0" +msgstr "2.0" + +#, no-wrap +msgid "2.1" +msgstr "2.1" + +#, no-wrap +msgid "2.2" +msgstr "2.2" + +#, no-wrap +msgid "2.3" +msgstr "2.3" + +#, no-wrap +msgid "2.4" +msgstr "2.4" + +#, no-wrap +msgid "2.5" +msgstr "2.5" + +#, no-wrap +msgid "Development updates every month" +msgstr "Development updates every month" + +#, no-wrap +msgid "2.6" +msgstr "2.6" + +#, no-wrap +msgid "2" +msgstr "2" + +#, no-wrap +msgid "1.0" +msgstr "1.0" + +#, no-wrap +msgid "1.1" +msgstr "1.1" + +#, no-wrap +msgid "1.2" +msgstr "1.2" + +#, no-wrap +msgid "1.3" +msgstr "1.3" + +#, no-wrap +msgid "1.4" +msgstr "1.4" + +#, no-wrap +msgid "1.5" +msgstr "1.5" + +#, no-wrap +msgid "1.6" +msgstr "1.6" + +#, no-wrap +msgid "3" +msgstr "3" + +#, no-wrap +msgid "3.0" +msgstr "3.0" + +#, no-wrap +msgid "3.1" +msgstr "3.1" + +#, no-wrap +msgid "0.6" +msgstr "0.6" + +#, no-wrap +msgid "0.5" +msgstr "0.5" + +#, no-wrap +msgid "1" +msgstr "1" + +#, no-wrap +msgid "Release every 6 months" +msgstr "Release every 6 months" + +#, no-wrap +msgid "No maintainance updates" +msgstr "No maintainance updates" + +#, no-wrap +msgid "master" +msgstr "master" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Documentation/Locales/en_US/repository.asciidoc.po b/Documentation/Locales/en_US/repository.asciidoc.po new file mode 100644 index 0000000..7ab6841 --- /dev/null +++ b/Documentation/Locales/en_US/repository.asciidoc.po @@ -0,0 +1,192 @@ +msgid "" +msgstr "" +"Project-Id-Version: repository.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-15 10:06-0500\n" +"PO-Revision-Date: 2013-11-15 10:06-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: English\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +msgid "@@image: 'repository-infra.png'; md5=48f2ca34b510c9d776366cd19eb88e1a" +msgstr "" + +msgid "The CentOS Artwork Repository" +msgstr "The CentOS Artwork Repository" + +msgid "Nov 2013" +msgstr "Nov 2013" + +msgid "Alain" +msgstr "Alain" + +msgid "Reguera" +msgstr "Reguera" + +msgid "Delgado" +msgstr "Delgado" + +msgid "al@centos.org.cu" +msgstr "al@centos.org.cu" + +msgid "ARD" +msgstr "ARD" + +msgid "1.0" +msgstr "1.0" + +msgid "Mission" +msgstr "Mission" + +msgid "" +"The CentOS Artwork Repository exists to produce The CentOS Project corporate " +"visual identity." +msgstr "" +"The CentOS Artwork Repository exists to produce The CentOS Project corporate " +"visual identity." + +msgid "Infrastructure" +msgstr "Infrastructure" + +msgid "" +"The CentOS Artwork Repository is made of one “central repository” and many " +"“working copies” of that central repository. The working copies are " +"independent one another, can be distributed all around the world and provide " +"a local place for designers, documenters, translators and programmers to " +"perform their work in a decentralized way. The central repository, on the " +"other hand, provides a common place for all independent working copies to " +"exchange data in the community." +msgstr "" +"The CentOS Artwork Repository is made of one “central repository” and many " +"“working copies” of that central repository. The working copies are " +"independent one another, can be distributed all around the world and provide " +"a local place for designers, documenters, translators and programmers to " +"perform their work in a decentralized way. The central repository, on the " +"other hand, provides a common place for all independent working copies to " +"exchange data in the community." + +msgid "repository-infra.png" +msgstr "repository-infra.png" + +msgid "Subversion" +msgstr "Subversion" + +msgid "" +"The current infrastructure that holds &TCAR;, on the Internet, is made " +"of the following components:" +msgstr "" +"The current infrastructure that holds &TCAR;, on the Internet, is made " +"of the following components:" + +msgid "" +"Subversion — Modern " +"Version Control System designed to replace CVS." +msgstr "" +"Subversion — Modern " +"Version Control System designed to replace CVS." + +msgid "" +"Trac — Enhanced wiki and " +"issue tracking system." +msgstr "" +"Trac — Enhanced wiki and " +"issue tracking system." + +msgid "" +"Httpd+WebDav as data exchanging route between the workstations and the " +"central repository, through the Internet. Httpd was configured to provide " +"service through SSL, so all traffic between the workstations and the server " +"be protected while it travels across the Internet." +msgstr "" +"Httpd+WebDav as data exchanging route between the workstations and the " +"central repository, through the Internet. Httpd was configured to provide " +"service through SSL, so all traffic between the workstations and the server " +"be protected while it travels across the Internet." + +msgid "" +"The access rights are controlled by using a combination of both Subversion's " +"authorization files and Httpd's password files. These files can be managed " +"consistently through Trac's WebAdmin plug-in." +msgstr "" +"The access rights are controlled by using a combination of both Subversion's " +"authorization files and Httpd's password files. These files can be managed " +"consistently through Trac's WebAdmin plug-in." + +msgid "" +"In this infrastructure, the first level of directories in the repository " +"provides the Subversion's standard trunk-branches-tags layout. The second " +"level of directories provides organization for different work lines, as " +"described in <xref linkend=\"repo-convs-worklines\" />. All other " +"subsequent directory levels from second level on exist to organize specific " +"concepts related to the work line they belong to." +msgstr "" +"In this infrastructure, the first level of directories in the repository " +"provides the Subversion's standard trunk-branches-tags layout. The second " +"level of directories provides organization for different work lines, as " +"described in <xref linkend=\"repo-convs-worklines\" />. All other " +"subsequent directory levels from second level on exist to organize specific " +"concepts related to the work line they belong to." + +msgid "Git" +msgstr "Git" + +msgid "" +"In addition to current Subversion infrastructure, we are working on a Git " +"infrastructure with the intention of migrating the current Subversion " +"infrastructure up to it, progressively. The Git infrastructure we are " +"working on is made of the following components:" +msgstr "" +"In addition to current Subversion infrastructure, we are working on a Git " +"infrastructure with the intention of migrating the current Subversion " +"infrastructure up to it, progressively. The Git infrastructure we are " +"working on is made of the following components:" + +msgid "Git — Fast version control system." +msgstr "Git — Fast version control system." + +msgid "Gitolite — Highly flexible server for git directory version tracker." +msgstr "Gitolite — Highly flexible server for git directory version tracker." + +msgid "Gitweb — Simple web interface to git repositories." +msgstr "Gitweb — Simple web interface to git repositories." + +msgid "MantisBT — Web-based issue tracking system." +msgstr "MantisBT — Web-based issue tracking system." + +msgid "" +"The data exchanging route between the working copies and the central " +"repository takes place through SSH." +msgstr "" +"The data exchanging route between the working copies and the central " +"repository takes place through SSH." + +msgid "" +"The access rights are controlled by using a combination of SSH public keys " +"and Gitolite's repository configuration file." +msgstr "" +"The access rights are controlled by using a combination of SSH public keys " +"and Gitolite's repository configuration file." + +msgid "" +"In this infrastructure, the first level of directories in the repository " +"provides organization for different work lines, as described in <xref " +"linkend=\"repo-convs-worklines\" />. All other subsequent directory " +"levels from second level on exist to organize specific concepts related to " +"the work line they belong to." +msgstr "" +"In this infrastructure, the first level of directories in the repository " +"provides organization for different work lines, as described in <xref " +"linkend=\"repo-convs-worklines\" />. All other subsequent directory " +"levels from second level on exist to organize specific concepts related to " +"the work line they belong to." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" + +#~ msgid "@@image: 'repository-infra.png'; md5=THIS FILE DOESN'T EXIST" +#~ msgstr "@@image: 'repository-infra.png'; md5=THIS FILE DOESN'T EXIST" diff --git a/Documentation/Locales/es_ES/corporate.asciidoc.po b/Documentation/Locales/es_ES/corporate.asciidoc.po new file mode 100644 index 0000000..964a12d --- /dev/null +++ b/Documentation/Locales/es_ES/corporate.asciidoc.po @@ -0,0 +1,372 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate.asciidoc 0.6\n" +"POT-Creation-Date: 2013-10-24 01:23-0400\n" +"PO-Revision-Date: 2013-10-24 01:23-0400\n" +"Last-Translator: Localization SIG \n" +"Language-Team: Spanish\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#. When image changes, this message will be marked fuzzy or untranslated for you. +#. It doesn't matter what you translate it to: it's not used at all. +msgid "@@image: 'corporate.png'; md5=9caa5d90bf85b562e8a815fe466d0783" +msgstr "" + +msgid "The CentOS Project Corporate Visual Identity" +msgstr "La Identidad Visual Corporativa Del Proyecto CentOS" + +msgid "Jul 2013" +msgstr "" + +msgid "Alain" +msgstr "" + +msgid "Reguera" +msgstr "" + +msgid "Delgado" +msgstr "" + +msgid "al@centos.org.cu" +msgstr "" + +msgid "ARD" +msgstr "" + +msgid "1.0" +msgstr "" + +msgid "" +"The CentOS Project Corporate Identity is the “persona” of the organization " +"known as The CentOS Project. The CentOS Project Corporate Identity plays a " +"significant role in the way The CentOS Project, as organization, presents " +"itself to both internal and external stakeholders. In general terms, The " +"CentOS Project Corporate Identity expresses the values and ambitions of The " +"CentOS Project organization, its business, and its characteristics." +msgstr "" + +msgid "" +"The CentOS Project Corporate Identity provides visibility, recognizability, " +"reputation, structure and identification to The CentOS Project organization " +"by means of Corporate Design, Corporate Communication, and Corporate " +"Behaviour." +msgstr "" + +msgid "The CentOS Project Corporate Identity" +msgstr "" + +msgid "corporate.png" +msgstr "" + +msgid "Corporate Mission" +msgstr "Misión Corporativa" + +msgid "" +"The CentOS Project exists to produce The CentOS Distribution, an Enterprise-" +"class Linux Distribution derived from sources freely provided to the public " +"by a prominent North American Enterprise Linux vendor. The CentOS " +"Distribution conforms fully with the upstream vendors redistribution policy " +"and aims to be 100% binary compatible. (The CentOS Distribution mainly " +"changes packages to remove upstream vendor branding and artwork.)." +msgstr "" + +msgid "" +"The CentOS Distribution is developed by a small but growing team of core " +"developers. In turn the core developers are supported by an active user " +"community including system administrators, network administrators, " +"enterprise users, managers, core Linux contributors and Linux enthusiasts " +"from around the world." +msgstr "" + +msgid "" +"The CentOS Distribution has numerous advantages including: an active and " +"growing user community, quickly rebuilt, tested, and QA'ed errata packages, " +"an extensive mirror network, developers who are contactable and responsive " +"of a reliable Enterprise-class Linux Distribution, multiple free support " +"avenues including a Wiki, " +"IRC " +"Chat, Email Lists, " +"Forums, and a " +"dynamic FAQ." +msgstr "" + +msgid "Corporate Graphic Design" +msgstr "Diseño Gráfico Corporativo" + +msgid "" +"The corporate design is focused on the effective presentation of corporate " +"messages. As corporate messages we understand all the information emitted " +"from the organization; and when we say all we mean " +"everything that can be perceived through the human senses. The corporate " +"design takes care of defining what this information is and controlling the " +"way it goes out the organization producing it." +msgstr "" + +msgid "" +"When the organization doesn't take control over the corporate messages it " +"produces, the organization is letting that area of its identity to the " +"unknown and the results might be good or not so good, it is hard to know. " +"The issue to see here is that even the organization doesn't take control " +"over its corporate messages, they are always talking about the organization. " +"Taking control of corporate messages is a decision the organization needs to " +"take by itself, based on its need of better describe what it is." +msgstr "" + +msgid "" +"In the very specific case of The CentOS Project, we'll concentrate our " +"attention on corporate messages that reach us through the visual sense. This " +"is, all the visual manifestations The CentOS Project is made of. As visual " +"manifestations we understand all the visible media The CentOS Project uses " +"to manifest its existence on. At this point it is necessary to consider what " +"The CentOS Project is, what its mission is and what it is producing. This, " +"in order to identify which visual manifestations the organization is " +"demanding attention of corporate design for." +msgstr "" + +msgid "" +"Inside The CentOS Project we identify and apply corporate design to the " +"following visual manifestations:" +msgstr "" + +msgid "" +"The CentOS Distribution: This visual " +"manifestation exists to cover all actions related to artwork production and " +"re-branding, required by The CentOS Distribution in order to comply with " +"upstream's redistribution guidelines." +msgstr "" + +msgid "" +"The CentOS Web: This visual " +"manifestation exists to cover all actions related to artwork production " +"required by The CentOS Project to manifest its existence in the World Wide " +"Web medium." +msgstr "" + +msgid "" +"The CentOS Showroom: This visual " +"manifestation exists to cover all actions related to artwork production " +"required by The CentOS Project to manifest its existence through media " +"produced industrially (e.g., stationery, clothes, CDs, DVDs, etc.)." +msgstr "" + +msgid "" +"The visual manifestations identified above seem to cover most media required " +"by The CentOS Project, as organization, to show its existence. However, " +"other visual manifestations could be added in the future, as long as they be " +"needed, to cover different areas like stands, buildings, offices, road " +"transportation or whatever visual manifestation The CentOS Project touches " +"to show its existence." +msgstr "" + +msgid "" +"Once all visual manifestations have been identified and defined through " +"design models, it is time to visually remark their connection with The " +"CentOS Project. This kind of connection is realized by applying The CentOS " +"Brand to design models inside visual manifestations supported through " +"corporate design." +msgstr "" + +msgid "Corporate Communication" +msgstr "Comunicación Corporativa" + +msgid "" +"The CentOS Project corporate communication is focused on the effective " +"propagation of corporate messages. Propagation of corporate messages is " +"closely related to the media the organization uses as vehicle to distribute " +"its corporate messages." +msgstr "" + +msgid "" +"The CentOS Project corporate communication takes place through the following " +"visual manifestations:" +msgstr "" + +msgid "The CentOS Distribution" +msgstr "La Distribución CentOS" + +msgid "" +"This visual manifestation communicates its existence through software " +"packages. There are packages that make a remarkable use of images, packages " +"that make a moderate use of images, and packages that don't use images at " +"all. This visual manifestation is focused on providing The CentOS Project " +"images required by software packages that do use images in a remarkable way, " +"specially those holding the upstream brand (e.g., anaconda, grub, syslinux, " +"gdm, kdebase)." +msgstr "" + +msgid "" +"The Community Enterprise Operating System itself (communicates the essense " +"of The CentOS Project existence.)." +msgstr "" + +msgid "" +"Release Schema (Lifetime) and all the stuff related (e.g., Release Notes, " +"Documentation, Erratas, etc.)." +msgstr "" + +msgid "The CentOS Web" +msgstr "La Web CentOS" + +msgid "" +"This visual manifestation communicates its existence through web " +"applications. These web applications are free software and come from " +"different providers which distribute their work with predefined visual " +"styles. Frequently, these predefined visual styles have no visual relation " +"among themselves and introduce some visual contradictions when they all are " +"put together. Removing these visual contradictions is object of work for " +"this visual manifestation." +msgstr "" + +msgid "The CentOS Chat." +msgstr "" + +msgid "The CentOS Mailing Lists." +msgstr "" + +msgid "The CentOS Forums." +msgstr "" + +msgid "The CentOS Wiki." +msgstr "" + +msgid "Special Interest Groups (SIGs)." +msgstr "" + +msgid "Social Events, Interviews, Conferences, etc." +msgstr "" + +msgid "" +"The extensive network of mirrors available for downloading ISO files as well " +"as RPMs and SRPMs used to build them up in different architectures." +msgstr "" + +msgid "The CentOS Showroom" +msgstr "El Mercado CentOS" + +msgid "" +"This visual manifestation communicates its existence through production of " +"industrial objects carrying The CentOS Brand. These branded objects are " +"directed to be distributed on social events and/or shops. They provide a way " +"of promotion and commercialization that may help to reduce The CentOS " +"Project expenses (e.g., electrical power, hosting, servers, full-time-" +"developers, etc.), in a similar way as donations may do." +msgstr "" + +msgid "Stationery (e.g., Posters, Stickers, CD Lables and Sleeves)." +msgstr "" + +msgid "Clothes (e.g., Shirts, T-shirts, Pullovers, Caps)." +msgstr "" + +msgid "Installation media (e.g., CDs, DVD, Pendrives)." +msgstr "" + +msgid "Corporate Behaviour" +msgstr "Comportamiento Corporativo" + +msgid "" +"The CentOS Project corporate behaviour is focused on the effective " +"interaction of each member involved in the organization (e.g., core " +"developers, community members, etc.). It is related to ethics and politics " +"used to do the things inside the organization. It is related to the sense of " +"direction chosen by the organization and they way the organization projects " +"itself to achieve it." +msgstr "" + +msgid "" +"The CentOS Project corporate behaviour takes place through The CentOS " +"Project corporate communication, as described above." +msgstr "" + +msgid "Corporate Structure" +msgstr "Estructura Corporativa" + +msgid "" +"The CentOS Project corporate structure is based on a Monolithic Corporate " +"Visual Identity Structure. In this configuration, one unique name and one " +"unique visual style is used in all visual manifestation The CentOS Project " +"is made of." +msgstr "" + +msgid "" +"In a monolithic corporate visual identity structure, internal and external " +"stakeholders use to feel a strong sensation of uniformity, orientation, and " +"identification with the organization. No matter if you are visiting web " +"sites, using the distribution, or acting on social events, the one unique " +"name and one unique visual style connects them all to say: Hey! we are all " +"part of The CentOS Project." +msgstr "" + +msgid "" +"Other corporate structures for The CentOS Project have been considered as " +"well. Such is the case of producing one different visual style for each " +"major release of The CentOS Distribution. This structure isn't inconvenient " +"at all, but some visual contradictions could be introduced if it isn't " +"applied correctly and we need to be aware of it. To apply it correctly, we " +"need to know what The CentOS Project is made of." +msgstr "" + +msgid "" +"The CentOS Project, as organization, is mainly made of (but not limited to) " +"three visual manifestions: The CentOS Distribution, The CentOS Web and The " +"CentOS Showroom. Inside The CentOS Distribution visual manifestations, The " +"CentOS Project maintains near to four different major releases of The CentOS " +"Distribution, parallely in time. However, inside The CentOS Web visual " +"manifestations, the content is produced for no specific release information " +"(e.g., there is no a complete web site for each major release of The CentOS " +"Distribution individually, but one web site to cover them all). Likewise, " +"the content produced in The CentOS Showroom is industrially created for no " +"specific release, but The CentOS Project in general." +msgstr "" + +msgid "" +"In order to produce the The CentOS Project Monolithic Corporate Visual " +"Identity Structure correctly, we need to concider all the visual " +"manifestations The CentOS Project is made of, not just one of them. If one " +"different visual style is implemented for each major release of The CentOS " +"Distribution, which one of those different visual styles would be used to " +"cover the remaining visual manifestations The CentOS Project is made of (e." +"g., The CentOS Web and The CentOS Showroom)?" +msgstr "" + +msgid "" +"Probably you are thinking: yes, I see your point, but The CentOS Brand " +"connects them all already, why would we need to join them up into the same " +"visual style too, isn't it more work to do, and harder to maintain?" +msgstr "" + +msgid "" +"Harder to maintain, more work to do, probably. Specially when you consider " +"that The CentOS Project has proven stability and consistency through time " +"and, that, certainly, didn't come through swinging magical wands or " +"something but hardly working out to automate tasks and providing maintenance " +"through time. With that in mind, I consider The CentOS Project Corporate " +"Visual Identity Structure must be consequent with such stability and " +"consistency tradition. It is true that The CentOS Brand does connect all the " +"visual manifestations it is present on, but that connection is strengthened " +"if one unique visual style backups it. In fact, whatever thing you do to " +"strength the visual connection among The CentOS Project visual " +"manifestations would be very good in favor of The CentOS Project recognition." +msgstr "" + +msgid "" +"Obviously, having just one visual style in all visual manifestations for " +"eternity would be a very boring thing and would give the idea of a visually " +"outdated project. So, there is no problem on creating new visual styles for " +"each new major release of The CentOS Distribution, in order to refresh The " +"CentOS Distribution visual style; the problem itself is in not propagating " +"the new visual style created for the new release of The CentOS Distribution " +"to all other visual manifestations The CentOS Project is made of, in a way " +"The CentOS Project could be recognized no matter what visual manifestation " +"be in front of us. Such lack of uniformity is what introduces the visual " +"contradiction we would be precisely trying to solve by mean of themes " +"production in The CentOS Artwork Repository." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "Alain Reguera Delgado , 2013" diff --git a/Documentation/Locales/es_ES/corporate.svgz.po b/Documentation/Locales/es_ES/corporate.svgz.po new file mode 100644 index 0000000..d3b6d92 --- /dev/null +++ b/Documentation/Locales/es_ES/corporate.svgz.po @@ -0,0 +1,61 @@ +msgid "" +msgstr "" +"Project-Id-Version: corporate.svgz 0.6\n" +"POT-Creation-Date: 2013-10-24 01:23-0400\n" +"PO-Revision-Date: 2013-10-24 01:23-0400\n" +"Last-Translator: Localization SIG \n" +"Language-Team: Spanish\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "The CentOS Project Corporate Identity" +msgstr "" + +msgid "image/svg+xml" +msgstr "" + +msgid "2013-07-23" +msgstr "" + +msgid "Alain Reguera Delgado" +msgstr "" + +msgid "The CentOS Project" +msgstr "" + +msgid "en_US" +msgstr "" + +msgid "Identity" +msgstr "" + +msgid "Models" +msgstr "" + +msgid "Manuals" +msgstr "" + +msgid "Corporate" +msgstr "" + +#, no-wrap +msgid "COMMUNICATION" +msgstr "COMUNICACIÓN" + +#, no-wrap +msgid "GRAPHIC DESIGN" +msgstr "DISEÑO GRÁFICO" + +#, no-wrap +msgid "STRUCTURE" +msgstr "ESTRUCTURA" + +#, no-wrap +msgid "BEHAVIOUR" +msgstr "COMPORTAMIENTO" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "" diff --git a/Documentation/Locales/es_ES/licenses-gfdl.asciidoc b/Documentation/Locales/es_ES/licenses-gfdl.asciidoc new file mode 100644 index 0000000..ada2c1b --- /dev/null +++ b/Documentation/Locales/es_ES/licenses-gfdl.asciidoc @@ -0,0 +1,586 @@ +msgid "" +msgstr "" +"Project-Id-Version: gfdl.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-13 13:44-0500\n" +"PO-Revision-Date: 2013-11-13 13:44-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: Spanish\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "GNU Free Documentation License" +msgstr "Licencia de Documentación Libre de GNU" + +msgid "November 2002" +msgstr "Noviembre 2002" + +msgid "Free" +msgstr "" + +msgid "Software" +msgstr "" + +msgid "Foundation" +msgstr "" + +msgid "http://www.fsf.org/" +msgstr "" + +msgid "FSF" +msgstr "" + +msgid "1.2" +msgstr "" + +msgid "" +"Copyright © 2000, 2001, 2002 Free Software Foundation, Inc. 675 Mass Ave, " +"Cambridge, MA 02139, USA" +msgstr "" + +msgid "" +"Everyone is permitted to copy and distribute verbatim copies of this license " +"document, but changing it is not allowed." +msgstr "" +"Todos están permitidos de copiar y distribuir copias exactas de este " +"documento, pero modificarlo no está permitido." + +msgid "Preamble" +msgstr "Preámbulo" + +msgid "" +"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." +msgstr "" +"El propósito de esta Licencia es permitir que un manual, libro de " +"texto, u otro documento escrito sea «libre» en el sentido de libertad: " +"asegurar a todo el mundo la libertad efectiva de copiarlo y " +"redistribuirlo, con o sin modificaciones, de manera comercial o no. En " +"segundo término, esta Licencia proporciona al autor y al editor una " +"manera de obtener reconocimiento por su trabajo, sin que se le " +"considere responsable de las modificaciones realizadas por otros. " + +msgid "" +"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 " +"GNU General Public License, which is a copyleft license designed for free " +"software." +msgstr "" +"Esta Licencia es de tipo «copyleft», lo que significa que los trabajos " +"derivados del documento deben a su vez ser libres en el mismo sentido. " +"Complementa la Licencia Pública General de GNU, que es una licencia " +"tipo copyleft diseñada para el software libre. " + +msgid "" +"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." +msgstr "" +"Hemos diseñado esta Licencia para usarla en manuales de software " +"libre, ya que el software libre necesita documentación libre: Un " +"programa libre debe venir con los manuales que ofrezcan la mismas " +"libertades que da el software. Pero esta licencia no se limita a " +"manuales de software; puede ser usada para cualquier trabajo textual, " +"sin tener en cuenta su temática o si se publica como libro impreso. " +"Recomendamos esta licencia principalmente para trabajos cuyo fin sea " +"instructivo o de referencia." + +msgid "Applicability and definitions" +msgstr "Aplicación y definiciones" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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 “<< transparent>>” is called " +"“Opaque”." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "Verbatim copying" +msgstr "" + +msgid "" +"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 ." +msgstr "" + +msgid "" +"You may also lend copies, under the same conditions stated above, and you " +"may publicly display copies." +msgstr "" + +msgid "Copying in quantity" +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "Modifications" +msgstr "" + +msgid "" +"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 :" +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"State on the the name of the publisher of the " +", as the publisher." +msgstr "" + +msgid "Preserve all the copyright notices of the Document." +msgstr "" + +msgid "" +"Add an appropriate copyright notice for your modifications adjacent to the " +"other copyright notices." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"Preserve in that license notice the full lists of and required given in the " +"Document's license notice." +msgstr "" + +msgid "Include an unaltered copy of this License." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"Delete any section Entitled “Endorsements”. Such a section may not be " +"included in the ." +msgstr "" + +msgid "" +"Do not retitle any existing section to be Entitled “Endorsements” or to " +"conflict in title with any ." +msgstr "" + +msgid "Preserve any Warranty Disclaimers." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"You may add a section Entitled “Endorsements”, provided it contains nothing " +"but endorsements of your by various " +"parties&ndash;for example, statements of peer review or that the text " +"has been approved by an organization as the authoritative definition of a " +"standard." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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 ." +msgstr "" + +msgid "Combining documents" +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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”." +msgstr "" + +msgid "Collection of documents" +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "Aggregation with independent works" +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "Translations" +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "Termination" +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "Future Revisions of this License" +msgstr "" + +msgid "" +"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 http://www.gnu.org/copyleft/." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "How to use this License for your documents" +msgstr "" + +msgid "" +"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:" +msgstr "" + +#, no-wrap +msgid "" +"Copyright (C) YEAR YOUR NAME.\n" +"\n" +"Permission is granted to copy, distribute and/or modify this\n" +"document under the terms of the GNU Free Documentation License,\n" +"Version 1.2 or any later version published by the Free Software\n" +"Foundation; with no Invariant Sections, no Front-Cover Texts, and\n" +"no Back-Cover Texts. A copy of the license is included in the\n" +"section entitled ``GNU Free Documentation License''." +msgstr "" + +msgid "" +"If you have , Front-Cover Texts and " +"Back-Cover Texts, replace the “with…Texts”. line with this:" +msgstr "" + +#, no-wrap +msgid "" +"with the Invariant Sections being LIST THEIR TITLES, with the\n" +"Front-Cover Texts being LIST, and with the Back-Cover Texts being\n" +"LIST." +msgstr "" + +msgid "" +"If you have without , or some other combination of the three, merge those two " +"alternatives to suit the situation." +msgstr "" + +msgid "" +"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." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "" diff --git a/Documentation/Locales/es_ES/licenses-gpl.asciidoc b/Documentation/Locales/es_ES/licenses-gpl.asciidoc new file mode 100644 index 0000000..686864e --- /dev/null +++ b/Documentation/Locales/es_ES/licenses-gpl.asciidoc @@ -0,0 +1,755 @@ +msgid "" +msgstr "" +"Project-Id-Version: gpl.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-13 13:44-0500\n" +"PO-Revision-Date: 2013-11-13 13:44-0500\n" +"Last-Translator: Localization SIG \n" +"Language-Team: Spanish\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +msgid "GNU General Public License" +msgstr "Licencia Pública General de GNU" + +msgid "June 1991" +msgstr "Junio 1991" + +msgid "Free" +msgstr "" + +msgid "Software" +msgstr "" + +msgid "Foundation" +msgstr "" + +msgid "FSF" +msgstr "" + +msgid "2" +msgstr "" + +msgid "" +"Copyright © 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, " +"Cambridge, MA 02139, USA" +msgstr "" + +msgid "" +"Everyone is permitted to copy and distribute verbatim copies of this license " +"document, but changing it is not allowed." +msgstr "" +"Todos están permitidos de copiar y distribuir copias exactas de este " +"documento, pero modificarlo no está permitido." + +msgid "Preamble" +msgstr "Preámbulo" + +msgid "" +"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." +msgstr "" +"Las licencias que cubren la mayor parte del software están diseñadas para " +"quitarle a usted la libertad de compartirlo y modificarlo. Por el contrario, " +"la Licencia Pública General de GNU pretende garantizarle la libertad de " +"compartir y modificar software libre, para asegurar que el software es libre " +"para todos sus usuarios. Esta Licencia Pública General se aplica a la mayor " +"parte del software del la Free Software Foundation y a cualquier otro " +"programa si sus autores se comprometen a utilizarla. (Existe otro software " +"de la Free Software Foundation que está cubierto por la Licencia Pública " +"General de GNU para Bibliotecas). Si quiere, también puede aplicarla a sus " +"propios programas." + +msgid "" +"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." +msgstr "" +"Cuando hablamos de software libre, estamos refiriéndonos a libertad, no a " +"precio. Nuestras Licencias Públicas Generales están diseñadas para " +"asegurarnos de que tenga la libertad de distribuir copias de software libre " +"(y cobrar por ese servicio si quiere), de que reciba el código fuente o que " +"pueda conseguirlo si lo quiere, de que pueda modificar el software o usar " +"fragmentos de él en programas nuevos libres, y de que sepa que puede hacer " +"todas estas cosas. " + +msgid "" +"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." +msgstr "" +"Para proteger sus derechos necesitamos algunas restricciones que prohíban a " +"cualquiera negarle a usted estos derechos o pedirle que renuncie a ellos. " +"Estas restricciones se traducen en ciertas obligaciones que le afectan si " +"distribuye copias del software, o si lo modifica. " + +msgid "" +"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." +msgstr "" +"Por ejemplo, si distribuye copias de uno de estos programas, sea " +"gratuitamente, o a cambio de una contraprestación, debe dar a los receptores " +"todos los derechos que tiene. Debe asegurarse de que ellos también reciben, " +"o pueden conseguir, el código fuente. Y debe mostrarles estas condiciones de " +"forma que conozcan sus derechos. " + +msgid "We protect your rights with two steps:" +msgstr "Protegemos sus derechos con la combinación de dos medidas:" + +msgid "copyright the software, and" +msgstr "Derechos de copia del software (copyright), y " + +msgid "" +"offer you this license which gives you legal permission to copy, distribute " +"and/or modify the software." +msgstr "" +"Le ofrecemos esta licencia, que le da permiso legal para copiar, distribuir " +"y/o modificar el software. " + +msgid "" +"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." +msgstr "" +"También, para la protección de cada autor y la nuestra propia, queremos " +"asegurarnos de que todo el mundo comprende que no se proporciona ninguna " +"garantía para este software libre. Si el software se modifica por cualquiera " +"y éste a su vez lo distribuye, queremos que sus receptores sepan que lo que " +"tienen no es el original, de forma que cualquier problema introducido por " +"otros no afecte a la reputación de los autores originales. " + +msgid "" +"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." +msgstr "" +"Finalmente, cualquier programa libre está constantemente amenazado por " +"patentes sobre el software. Queremos evitar el peligro de que los " +"redistribuidores de un programa libre obtengan patentes por su cuenta, " +"convirtiendo de facto el programa en propietario. Para evitar esto, hemos " +"dejado claro que cualquier patente debe ser pedida para el uso libre de " +"cualquiera, o no ser pedida. " + +msgid "" +"The precise terms and conditions for copying, distribution and modification " +"follow." +msgstr "" +"Los términos precisos y las condiciones para la copia, distribución y " +"modificación se exponen a continuación. " + +msgid "Terms and Conditions for Copying, Distribution and Modification" +msgstr "Términos y condiciones para la copia, distribución y modificación" + +msgid "Section 0" +msgstr "Sección 0" + +msgid "" +"This License applies to any program or other work which contains a notice " +"placed by the copyright holder saying it may be distributed under the terms " +"of this General Public License. The “Program”, below, refers to any such " +"program or work, and a “work based on the Program” means either the Program " +"or any derivative work under copyright law: that is to say, a work " +"containing the Program or a portion of it, either verbatim or with " +"modifications and/or translated into another language. (Hereinafter, " +"translation is included without limitation in the term “modification”.) Each " +"licensee is addressed as “you”." +msgstr "" +"Esta Licencia se aplica a cualquier programa u otro tipo de obra que " +"contenga una notificación colocada por el propietario del copyright diciendo " +"que puede distribuirse bajo los términos de esta Licencia Pública General. " +"El «Programa», en adelante, se referirá a cualquier programa u obra, y «obra " +"basada en el Programa» se referirá bien al Programa o a cualquier trabajo " +"derivado de él según la ley de derechos de autor (copyright): Esto es, una " +"obra o trabajo que contenga el programa o una porción de él, bien en forma " +"literal o con modificaciones y/o traducido en otro lenguaje. Aquí y después, " +"la traducción está incluida sin limitación en el término «modificación». Cada " +"concesionario (licenciatario) será denominado «usted». " + +msgid "" +"Activities other than copying, distribution and modification are not covered " +"by this License; they are outside its scope. The act of running the Program " +"is not restricted, and the output from the Program is covered only if its " +"contents constitute a work based on the Program (independent of having been " +"made by running the Program). Whether that is true depends on what the " +"Program does." +msgstr "" +"Cualquier otra actividad que no sea la copia, distribución o modificación no " +"está cubierta por esta Licencia, está fuera de su ámbito. El acto de " +"ejecutar el Programa no está restringido, y los resultados del Programa " +"están cubiertos únicamente si sus contenidos constituyen un trabajo basado " +"en el Programa, independientemente de haberlo producido mediante la " +"ejecución del programa. El que esto se cumpla, depende de lo que haga el " +"programa. " + +msgid "Section 1" +msgstr "Sección 1" + +msgid "" +"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." +msgstr "" +"Usted puede copiar y distribuir copias literales del código fuente del " +"Programa, según lo has recibido, en cualquier medio, supuesto que de forma " +"adecuada y bien visible publique en cada copia un anuncio de copyright " +"adecuado y un repudio de garantía, mantenga intactos todos los anuncios que " +"se refieran a esta Licencia y a la ausencia de garantía, y proporcione a " +"cualquier otro receptor del programa una copia de esta Licencia junto con " +"el Programa. " + +msgid "" +"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." +msgstr "" +"Puede cobrar un precio por el acto físico de transferir una copia, y puede, " +"según su libre albedrío, ofrecer garantía a cambio de unos honorarios. " + +msgid "Section 2" +msgstr "Sección 2" + +msgid "" +"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:" +msgstr "" +"Puede modificar su copia o copias del Programa o de cualquier porción de él, " +"formando de esta manera un trabajo basado en el Programa, y copiar y " +"distribuir esa modificación o trabajo bajo los términos de la anterior, probado que además usted cumpla con todas " +"las siguientes condiciones: " + +msgid "" +"You must cause the modified files to carry prominent notices stating that " +"you changed the files and the date of any change." +msgstr "" +"Debe hacer que los ficheros modificados lleven anuncios prominentes " +"indicando que los ha cambiado y la fecha de cualquier cambio." + +msgid "" +"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." +msgstr "" +"Debe hacer que cualquier trabajo que distribuya o publique y que en todo o " +"en parte contenga o sea derivado del Programa o de cualquier parte de él sea " +"licenciada como un todo, sin carga alguna, a todas las terceras partes y " +"bajo los términos de esta Licencia. " + +msgid "" +"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." +msgstr "" + +msgid "Exception" +msgstr "Excepción" + +msgid "" +"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." +msgstr "" +"Si el propio Programa es interactivo pero normalmente no muestra ese " +"anuncio, no se requiere que su trabajo basado en el Programa muestre ningún " +"anuncio. " + +msgid "" +"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." +msgstr "" +"Estos requisitos se aplican al trabajo modificado como un todo. Si partes " +"identificables de ese trabajo no son derivadas del Programa, y pueden, " +"razonablemente, ser consideradas trabajos independientes y separados por " +"ellos mismos, entonces esta Licencia y sus términos no se aplican a esas " +"partes cuando sean distribuidas como trabajos separados. Pero cuando " +"distribuya esas mismas secciones como partes de un todo que es un trabajo " +"basado en el Programa, la distribución del todo debe ser según los términos " +"de esta licencia, cuyos permisos para otros licenciatarios se extienden al " +"todo completo, y por lo tanto a todas y cada una de sus partes, con " +"independencia de quién la escribió. " + +msgid "" +"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." +msgstr "" +"Por lo tanto, no es la intención de este apartado reclamar derechos o " +"desafiar sus derechos sobre trabajos escritos totalmente por usted mismo. El " +"intento es ejercer el derecho a controlar la distribución de trabajos " +"derivados o colectivos basados en el Programa. " + +msgid "" +"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." +msgstr "" +"Además, el simple hecho de reunir un trabajo no basado en el Programa con el " +"Programa (o con un trabajo basado en el Programa) en un volumen de " +"almacenamiento o en un medio de distribución no hace que dicho trabajo entre " +"dentro del ámbito cubierto por esta Licencia. " + +msgid "Section 3" +msgstr "Sección 3" + +msgid "" +"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:" +msgstr "" +"Puede copiar y distribuir el Programa (o un trabajo basado en él, según se " +"especifica en la Sección 2, como código objeto o en formato ejecutable según " +"los términos de las y anteriores, supuesto que además cumpla una de las " +"siguientes condiciones: " + +msgid "" +"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," +msgstr "" +"Acompañarlo con el código fuente leíble completo correspondiente, leíble por " +"máquinas, que debe ser distribuido según los términos de las y mencionadas " +"antes en un medio habitualmente utilizado para el intercambio de software, " +"o, " + +msgid "" +"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," +msgstr "" +"Acompañarlo con una oferta por escrito, válida durante al menos tres años, " +"de proporcionar a cualquier tercera parte una copia completa en formato " +"electrónico del código fuente correspondiente, a un coste no mayor que el de " +"realizar físicamente la distribución del fuente, que será distribuido bajo " +"las condiciones descritas en los apartados 1 y 2 anteriores, en un medio " +"habitualmente utilizado para el intercambio de programas, o " + +msgid "" +"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.)" +msgstr "" +"Acompañarlo con la información que recibiste ofreciendo distribuir el código " +"fuente correspondiente. (Esta opción se permite sólo para distribución no " +"comercial y sólo si usted recibió el programa como código objeto o en " +"formato ejecutable con tal oferta, de acuerdo con la Subsección b anterior). " + +msgid "" +"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." +msgstr "" +"Por código fuente de un trabajo se entiende la forma preferida del trabajo " +"cuando se le hacen modificaciones. Para un trabajo ejecutable, se entiende " +"por código fuente completo todo el código fuente para todos los módulos que " +"contiene, más cualquier fichero asociado de definición de interfaces, más " +"los guiones utilizados para controlar la compilación e instalación del " +"ejecutable. Como excepción especial el código fuente distribuido no necesita " +"incluir nada que sea distribuido normalmente (bien como fuente, bien en " +"forma binaria) con los componentes principales (compilador, núcleo y " +"similares) del sistema operativo en el cual funciona el ejecutable, a no ser " +"que el propio componente acompañe al ejecutable. " + +msgid "" +"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." +msgstr "" +"Si la distribución del ejecutable o del código objeto se hace mediante la " +"oferta acceso para copiarlo de un cierto lugar, entonces se considera la " +"oferta de acceso para copiar el código fuente del mismo lugar como " +"distribución del código fuente, incluso aunque terceras partes no estén " +"forzadas a copiar el fuente junto con el código objeto." + +msgid "Section 4" +msgstr "Sección 4" + +msgid "" +"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." +msgstr "" +"No puede copiar, modificar, sublicenciar o distribuir el Programa excepto " +"como prevé expresamente esta Licencia. Cualquier intento de copiar, " +"modificar sublicenciar o distribuir el Programa de otra forma es inválida, y " +"hará que cesen automáticamente los derechos que te proporciona esta " +"Licencia. En cualquier caso, las partes que hayan recibido copias o derechos " +"de usted bajo esta Licencia no cesarán en sus derechos mientras esas partes " +"continúen cumpliéndola." + +msgid "Section 5" +msgstr "Sección 5" + +msgid "" +"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." +msgstr "" +"No está obligado a aceptar esta licencia, ya que no la ha firmado. Sin " +"embargo, no hay hada más que le proporcione permiso para modificar o " +"distribuir el Programa o sus trabajos derivados. Estas acciones están " +"prohibidas por la ley si no acepta esta Licencia. Por lo tanto, si modifica " +"o distribuye el Programa (o cualquier trabajo basado en el Programa), está " +"indicando que acepta esta Licencia para poder hacerlo, y todos sus términos " +"y condiciones para copiar, distribuir o modificar el Programa o trabajos " +"basados en él." + +msgid "Section 6" +msgstr "Sección 6" + +msgid "" +"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." +msgstr "" +"Cada vez que redistribuya el Programa (o cualquier trabajo basado en el " +"Programa), el receptor recibe automáticamente una licencia del " +"licenciatario original para copiar, distribuir o modificar el Programa, de " +"forma sujeta a estos términos y condiciones. No puede imponer al receptor " +"ninguna restricción más sobre el ejercicio de los derechos aquí " +"garantizados. No es usted responsable de hacer cumplir esta licencia por " +"terceras partes." + +msgid "Section 7" +msgstr "Sección 7" + +msgid "" +"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." +msgstr "" +"Si como consecuencia de una resolución judicial o de una alegación de " +"infracción de patente o por cualquier otra razón (no limitada a asuntos " +"relacionados con patentes) se le imponen condiciones (ya sea por mandato " +"judicial, por acuerdo o por cualquier otra causa) que contradigan las " +"condiciones de esta Licencia, ello no le exime de cumplir las condiciones de " +"esta Licencia. Si no puede realizar distribuciones de forma que se " +"satisfagan simultáneamente sus obligaciones bajo esta licencia y cualquier " +"otra obligación pertinente entonces, como consecuencia, no puede distribuir " +"el Programa de ninguna forma. Por ejemplo, si una patente no permite la " +"redistribución libre de derechos de autor del Programa por parte de todos " +"aquellos que reciban copias directa o indirectamente a través de usted, " +"entonces la única forma en que podría satisfacer tanto esa condición como " +"esta Licencia sería evitar completamente la distribución del Programa. " + +msgid "" +"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." +msgstr "" +"Si cualquier porción de este apartado se considera inválida o imposible de " +"cumplir bajo cualquier circunstancia particular ha de cumplirse el resto y " +"la sección por entero ha de cumplirse en cualquier otra circunstancia. " + +msgid "" +"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." +msgstr "" +"No es el propósito de este apartado inducirle a infringir ninguna " +"reivindicación de patente ni de ningún otro derecho de propiedad o impugnar " +"la validez de ninguna de dichas reivindicaciones. Este apartado tiene el " +"único propósito de proteger la integridad del sistema de distribución de " +"software libre, que se realiza mediante prácticas de licencia pública. Mucha " +"gente ha hecho contribuciones generosas a la gran variedad de software " +"distribuido mediante ese sistema con la confianza de que el sistema se " +"aplicará consistentemente. Será el autor/donante quien decida si quiere " +"distribuir software mediante cualquier otro sistema y una licencia no puede " +"imponer esa elección. " + +msgid "" +"This section is intended to make thoroughly clear what is believed to be a " +"consequence of the rest of this License." +msgstr "" +"Este apartado pretende dejar completamente claro lo que se cree que es una " +"consecuencia del resto de esta Licencia. " + +msgid "Section 8" +msgstr "Sección 8" + +msgid "" +"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." +msgstr "" +"Si la distribución y/o uso de el Programa está restringida en ciertos " +"países, bien por patentes o por interfaces bajo copyright, el tenedor del " +"copyright que coloca este Programa bajo esta Licencia puede añadir una " +"limitación explícita de distribución geográfica excluyendo esos países, de " +"forma que la distribución se permita sólo en o entre los países no excluidos " +"de esta manera. En ese caso, esta Licencia incorporará la limitación como si " +"estuviese escrita en el cuerpo de esta Licencia." + +msgid "Section 9" +msgstr "Sección 9" + +msgid "" +"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." +msgstr "" +"La Free Software Foundation puede publicar versiones revisadas y/o nuevas de " +"la Licencia Pública General de tiempo en tiempo. Dichas nuevas versiones " +"serán similares en espíritu a la presente versión, pero pueden ser " +"diferentes en detalles para considerar nuevos problemas o situaciones. " + +msgid "" +"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." +msgstr "" +"Cada versión recibe un número de versión que la distingue de otras. Si el " +"Programa especifica un número de versión de esta Licencia que se aplica " +"aplica a éste y a «cualquier versión posterior», usted tiene la opción de " +"seguir los términos y condiciones, bien de esa versión, bien de cualquier " +"versión posterior publicada por la Free Software Foundation. Si el Programa " +"no especifica un número de versión de esta Licencia, usted puede escoger " +"cualquier versión publicada por la Free Software Foundation. " + +msgid "Section 10" +msgstr "Sección 10" + +msgid "" +"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." +msgstr "" +"Si quiere incorporar partes del Programa en otros programas libres cuyas " +"condiciones de distribución son diferentes, escribe al autor para pedirle " +"permiso. Si el software tiene copyright de la Free Software Foundation, " +"escribe a la Free Software Foundation: algunas veces hacemos excepciones en " +"estos casos. Nuestra decisión estará guiada por el doble objetivo de de " +"preservar la libertad de todos los derivados de nuestro software libre y " +"promover el que se comparta y reutilice el software en general." + +msgid "NO WARRANTY" +msgstr "AUSENCIA GARANTÍA" + +msgid "Section 11" +msgstr "Sección 11" + +msgid "" +"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." +msgstr "" +"DEBIDO A QUE EL PROGRAMA SE LICENCIA LIBRE DE CARGAS, NO SE OFRECE NINGUNA " +"GARANTÍA SOBRE EL PROGRAMA, EN TODA LA EXTENSIÓN PERMITIDA POR LA " +"LEGISLACIÓN APLICABLE. EXCEPTO CUANDO SE INDIQUE DE OTRA FORMA POR ESCRITO, " +"LOS PROPIETARIOS DEL COPYRIGHT Y/U OTRAS PARTES PROPORCIONAN EL PROGRAMA «TAL " +"CUAL», SIN GARANTÍA DE NINGUNA CLASE, BIEN EXPRESA O IMPLÍCITA, CON " +"INCLUSIÓN, PERO SIN LIMITACIÓN A LAS GARANTÍAS MERCANTILES IMPLÍCITAS O A LA " +"CONVENIENCIA PARA UN PROPÓSITO PARTICULAR. CUALQUIER RIESGO REFERENTE A LA " +"CALIDAD Y PRESTACIONES DEL PROGRAMA ES ASUMIDO POR USTED. SI SE PROBASE QUE " +"EL PROGRAMA ES DEFECTUOSO, USTED ASUME EL COSTE DE CUALQUIER SERVICIO, " +"REPARACIÓN O CORRECCIÓN NECESARIO." + +msgid "Section 12" +msgstr "Sección 12" + +msgid "" +"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." +msgstr "" +"EN NINGÚN CASO, SALVO QUE LO REQUIERA LA LEGISLACIÓN APLICABLE O HAYA SIDO " +"ACORDADO POR ESCRITO, NINGÚN TENEDOR DEL COPYRIGHT NI NINGUNA OTRA PARTE QUE " +"MODIFIQUE Y/O REDISTRIBUYA EL PROGRAMA SEGÚN SE PERMITE EN ESTA LICENCIA " +"SERÁ RESPONSABLE ANTE USTED POR DAÑOS, INCLUYENDO CUALQUIER DAÑO GENERAL, " +"ESPECIAL, INCIDENTAL O RESULTANTE PRODUCIDO POR EL USO O LA IMPOSIBILIDAD DE " +"USO DEL PROGRAMA (CON INCLUSIÓN, PERO SIN LIMITACIÓN A LA PÉRDIDA DE DATOS O " +"A LA GENERACIÓN INCORRECTA DE DATOS O A PÉRDIDAS SUFRIDAS POR USTED O POR " +"TERCERAS PARTES O A UN FALLO DEL PROGRAMA AL FUNCIONAR EN COMBINACIÓN CON " +"CUALQUIER OTRO PROGRAMA), INCLUSO SI DICHO TENEDOR U OTRA PARTE HA SIDO " +"ADVERTIDO DE LA POSIBILIDAD DE DICHOS DAÑOS. " + +msgid "End of Terms and Conditions." +msgstr "Fin de los términos y condiciones" + +msgid "How to Apply These Terms to Your New Programs" +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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 <quote>" +"copyright</quote> line and a pointer to where the full notice is found." +msgstr "" + +#, no-wrap +msgid "" +"<one line to give the program's name and a brief idea of what it does.>\n" +"Copyright (C) 19yy <name of author>\n" +"\n" +"This program is free software; you can redistribute it and/or modify\n" +"it under the terms of the GNU General Public License as published by\n" +"the Free Software Foundation; either version 2 of the License, or\n" +"(at your option) any later version.\n" +"\n" +"This program is distributed in the hope that it will be useful,\n" +"but WITHOUT ANY WARRANTY; without even the implied warranty of\n" +"MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n" +"GNU General Public License for more details.\n" +"\n" +"You should have received a copy of the GNU General Public License\n" +"along with this program; if not, write to the Free Software\n" +"Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA." +msgstr "" + +msgid "" +"Also add information on how to contact you by electronic and paper mail." +msgstr "" + +msgid "" +"If the program is interactive, make it output a short notice like this when " +"it starts in an interactive mode:" +msgstr "" + +#, no-wrap +msgid "" +"Gnomovision version 69, Copyright (C) 19yy name of author\n" +"Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n" +"This is free software, and you are welcome to redistribute it\n" +"under certain conditions; type `show c' for details." +msgstr "" + +msgid "" +"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." +msgstr "" + +msgid "" +"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:" +msgstr "" + +#, no-wrap +msgid "" +"Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n" +"`Gnomovision' (which makes passes at compilers) written by James Hacker.\n" +"\n" +"<signature of Ty Coon>, 1 April 1989\n" +"Ty Coon, President of Vice" +msgstr "" + +msgid "" +"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." +msgstr "" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "" diff --git a/Documentation/identity-clothes-head.svgz b/Documentation/identity-clothes-head.svgz new file mode 100644 index 0000000..ac335c1 Binary files /dev/null and b/Documentation/identity-clothes-head.svgz differ diff --git a/Documentation/identity-clothes-torso.svgz b/Documentation/identity-clothes-torso.svgz new file mode 100644 index 0000000..b042c8d Binary files /dev/null and b/Documentation/identity-clothes-torso.svgz differ diff --git a/Documentation/identity-colors.svgz b/Documentation/identity-colors.svgz new file mode 100644 index 0000000..9ad2de4 Binary files /dev/null and b/Documentation/identity-colors.svgz differ diff --git a/Documentation/identity-fonts.svgz b/Documentation/identity-fonts.svgz new file mode 100644 index 0000000..b612f4d Binary files /dev/null and b/Documentation/identity-fonts.svgz differ diff --git a/Documentation/identity-logo-howto.svgz b/Documentation/identity-logo-howto.svgz new file mode 100644 index 0000000..1b575a9 Binary files /dev/null and b/Documentation/identity-logo-howto.svgz differ diff --git a/Documentation/identity-symbol-howto-1of4.svgz b/Documentation/identity-symbol-howto-1of4.svgz new file mode 100644 index 0000000..2b74847 Binary files /dev/null and b/Documentation/identity-symbol-howto-1of4.svgz differ diff --git a/Documentation/identity-symbol-howto-2of4.svgz b/Documentation/identity-symbol-howto-2of4.svgz new file mode 100644 index 0000000..a350cc7 Binary files /dev/null and b/Documentation/identity-symbol-howto-2of4.svgz differ diff --git a/Documentation/identity-symbol-howto-3of4.svgz b/Documentation/identity-symbol-howto-3of4.svgz new file mode 100644 index 0000000..0d1dba5 Binary files /dev/null and b/Documentation/identity-symbol-howto-3of4.svgz differ diff --git a/Documentation/identity-symbol-howto-4of4.svgz b/Documentation/identity-symbol-howto-4of4.svgz new file mode 100644 index 0000000..842a1d9 Binary files /dev/null and b/Documentation/identity-symbol-howto-4of4.svgz differ diff --git a/Documentation/identity-themes.svgz b/Documentation/identity-themes.svgz new file mode 100644 index 0000000..618070c Binary files /dev/null and b/Documentation/identity-themes.svgz differ diff --git a/Documentation/identity.asciidoc b/Documentation/identity.asciidoc new file mode 100644 index 0000000..935f64f --- /dev/null +++ b/Documentation/identity.asciidoc @@ -0,0 +1,365 @@ +The CentOS Project Corporate Visual Identity +============================================ + +The CentOS Project Corporate Identity is the ``persona'' of the +organization known as The CentOS Project. The CentOS Project +Corporate Identity plays a significant role in the way The CentOS +Project, as organization, presents itself to both internal and +external stakeholders. In general terms, The CentOS Project Corporate +Identity expresses the values and ambitions of The CentOS Project +organization, its business, and its characteristics. + +The CentOS Project Corporate Identity provides visibility, +recognizability, reputation, structure and identification to The +CentOS Project organization by means of Corporate Design, Corporate +Communication, and Corporate Behavior. + +[[corporate_identity]] +.The CentOS Project Corporate Identity +image::corporate.png[alt="The CentOS Project Corporate Identity"] + +Corporate Mission +----------------- + +The CentOS Project exists to produce The CentOS Distribution, an +Enterprise-class Linux Distribution derived from sources freely +provided to the public by a prominent North American Enterprise Linux +vendor. The CentOS Distribution conforms fully with the upstream +vendors redistribution policy and aims to be 100% binary compatible. +(The CentOS Distribution mainly changes packages to remove upstream +vendor branding and artwork.). + +The CentOS Distribution is developed by a small but growing team of +core developers. In turn the core developers are supported by an +active user community including system administrators, network +administrators, enterprise users, managers, core Linux contributors +and Linux enthusiasts from around the world. + +The CentOS Distribution has numerous advantages including: an active +and growing user community, quickly rebuilt, tested, and QA'ed errata +packages, an extensive mirror network, developers who are contactable +and responsive of a reliable Enterprise-class Linux Distribution, +multiple free support avenues including a +http://wiki.centos.org/[Wiki], +http://www.centos.org/modules/tinycontent/index.php?id=8[IRC Chat], +http://lists.centos.org/[Email Lists], +http://www.centos.org/modules/newbb/[Forums], and a dynamic +http://www.centos.org/modules/smartfaq/[FAQ]. + +Corporate Graphic Design +------------------------ + +Corporate graphic design is focused on the presentation of corporate +messages with efficiency and efficacy. Corporate graphic design is a +cornerstone of corporate visual identity. When the organization +doesn't take control over the corporate messages it produces, the +organization is letting that area of its identity to the unknown and +the result might be good or not so good, it is hard to know. Even the +organization doesn't take control over its corporate messages they are +always talking about the organization. Taking control of corporate +messages presentation is a decision the organization needs to take by +itself, based on its need of better describe what it is. To work out +the corporate graphic design of an organization it is required to +identify which are the visual manifestations the organization reflects +its existence on. + +The CentOS Artwork SIG has identified the following visual +manifestations for The CentOS Project organization: + +* GNU/Linux Distribution -- to control the operating system appearance. +* Web environment -- to control the web applications appearance. +* Promotion -- to control the industrial media appearance. + +[[centos-brand]] +Corporate Brand +~~~~~~~~~~~~~~~ + +The corporate brand is the graphical identification of an +organization. The CentOS Artwork SIG uses The CentOS Brand to connect +all the visual manifestations The CentOS Project is made of (e.g., +GNU/Linux Distributions, Websites, Stationery, etc.) and, this way, it +provides visual recognition among similar projects available on the +Internet. + +The CentOS Brand is composed of a graphical component known as The +CentOS Symbol and a typographical component known as The CentOS Type. +When The CentOS Symbol and The CentOS Type are put together, they +create what we know as The CentOS Logo. All the components that make +The CentOS Brand can be used together or separately, considering that, +in hierarchy order, The CentOS Logo is rather preferred than The +CentOS Symbol, as well as The CentOS Symbol is rather preferred than +The CentOS Type alone. + +image:corporate-logo-howto.png[corporate-logo-howto.png] + +The CentOS Brand must be exactly the same every time it is printed +out, no matter what the medium is. A route to reproduce The CentOS +Brand this way must be used so as to avoid reproduction mistakes of +any kind when final images are branded with it. To prevent such +mistakes, The CentOS Artwork SIG uses configuration files and the +*render* module of *centos-art.sh* script to produce PNG brand images +of different sizes and colors that can be combined later with other +images instead of manipulating The CentOS Brand in SVG format inside +each different design model that requires it. This also grants a +single point of change for all brands already applied on final images. +In this environment, if you make a change to brands SVG files, they +will be propagated to all final images the next time you render them. + +The CentOS Symbol is the graphical part of The CentOS Logo. As The +CentOS Logo, The CentOS Symbol is used to ``brand'' images produced by +The CentOS Project and provide visual connection between images so +they can be monolithically recognized as part of The CentOS Project. +The CentOS Symbol must be exactly the same every time it is printed +out and a route to reproduce it in such a way must be available so as +to avoid reproduction mistakes when images are branded with it. + +The CentOS Type is the typographical part of The CentOS Logo. The +CentOS Type is used to ``brand'' images produce by The CentOS Project +and provide visual connection between images so they can be +monolithically recognized as part of The CentOS Project. The CentOS +Type alone provides less recognition than The CentOS Logo and The +CentOS Symbol. Frequently, The CentOS Type is used to advert the major +release of CentOS Distribution on the first images shown as part of +Distribution installation process. The CentOS Symbol and any release +information printed out with it must have exactly the same proportions +every time they are printed out. + +Corporate Fonts +~~~~~~~~~~~~~~~ + +The CentOS Artwork SIG uses the following font files in their +corporate graphic designs: + +image:corporate-fonts.png[corporate-fonts.png] + +Corporate Colors +~~~~~~~~~~~~~~~~ + +In addition to colors used in The CentOS Symbol (9ccd2aff, 932279ff, +262577ff, efa724ff) and The CentOS Default Background Color +(204c8dff), The CentOS Artwork SIG uses the following colors in their +corporate graphic designs: + +image:../corporate-colors.png[corporate-colors.png] + +Artistic motifs have not any limitation in the number of colors used. +If you are a graphic designer creating artistic motifs for The CentOS +Project, feel free to take your creativeness at its limit by creating +color-full artistic motifs. For final bootup images which require a +reduced number of colors, create palette of colors for them with the +appropriate number of colors and let the *render* module of +*centos-art.sh* script to do the rest. + +[[centos-clothes]] +Corporate Clothes +~~~~~~~~~~~~~~~~~ + +The CentOS clothes identify the The CentOS Project representative +people at public presentations. + +image:../corporate-clothes-head.png[corporate-clothes-cap.png] + +image:../corporate-clothes-torso.png[corporate-clothes-shirt.png] + +[[corporate-themes]] +Corporate Themes +~~~~~~~~~~~~~~~~ + +The CentOS themes organize visual styles for all the visual +manifestation The CentOS Project is made of. In order to automate the +process of rendering images based on customizable patterns, themes +have been divided into ``design models'', ``localization files,'' and +``artistic motifs.'' + +image:corporate-themes.png[corporate-themes.png] + +[[corporate-themes-models]] +Design Models +^^^^^^^^^^^^^ + +Design models are compressed SVG files created with Inkscape. They +describe the image files used to implement the CentOS project visual +manifestations. For example, in the specific case of CentOS +distribution, each final image you want to re-brand has a design model +associated used to set the final image dimensions, whether or not it +has round borders, and what background to use on it. Design models +are created once and rarely modified through time. They are only +modified if the visual manifestation they refer to changes or needs to +be tuned up. + +[[corporate-themes-l10n]] +Localization Files +^^^^^^^^^^^^^^^^^^ + +Localization files provide localization for messages inside design +models. For example, if you decide to use slide images in CentOS +installer, you need to create one design model for each slide image +you want to produce in English language. Then, using *locale* module, +you create PO files for each design model you have. PO files are +created using the current language information of your terminal (e.g., +see value of +LANG+ variable). Then you use the *locale* module again +to edit the PO files and provide string translations from English to +your preferred language. Once translations are on the PO files, you +use the *render* module to produce images for your preferred language, +based on the artistic motif you initiate rendition for and the related +design models set in the rendition configuration file. + +[[corporate-themes-motifs]] +Artistic Motifs +^^^^^^^^^^^^^^^ + +Artistic motifs are PNG images holding the look and feel of each +design model available. One important characteristic of artistic +motifs is preserving one unique visual style for all the PNG images +they are made of. Artistic motifs aren't limited in number. It is +possible to have several artistic motifs and produce final images for +all of them using one single set of design models. Artistic motifs +give plenty of room for graphic designers' creativeness. As +convention, artistic motifs are conceived without any specific brand +information on them. The brand information is set using brand images +later, when final images are produced. + +[[corporate-communication]] +Corporate Communication +----------------------- + +The CentOS Project corporate communication is focused on the effective +propagation of corporate messages. Propagation of corporate messages +is closely related to the media the organization uses as vehicle to +distribute its corporate messages. + +The CentOS Project corporate communication takes place through the +following visual manifestations: + +The CentOS Distribution +~~~~~~~~~~~~~~~~~~~~~~~ + +This visual manifestation communicates its existence through software +packages. There are packages that make a remarkable use of images, +packages that make a moderate use of images, and packages that don't +use images at all. This visual manifestation is focused on providing +The CentOS Project images required by software packages that do use +images in a remarkable way, specially those holding the upstream brand +(e.g., _anaconda_, _grub_, _syslinux_, _gdm_, _kdebase_). + +- The Community Enterprise Operating System itself (communicates the + essence of The CentOS Project existence.). + +- Release Schema (Lifetime) and all the stuff related (e.g., Release + Notes, Documentation, Erratas, etc.). + +The CentOS Web +~~~~~~~~~~~~~~ + +This visual manifestation communicates its existence through web +applications. These web applications are free software and come from +different providers which distribute their work with predefined visual +styles. Frequently, these predefined visual styles have no visual +relation among themselves and introduce some visual contradictions +when they all are put together. Removing these visual contradictions +is object of work for this visual manifestation. + +- The CentOS Chat. +- The CentOS Mailing Lists. +- The CentOS Forums. +- The CentOS Wiki. +- Special Interest Groups (SIGs). +- Social Events, Interviews, Conferences, etc. +- The extensive network of mirrors available for downloading ISO files + as well as RPMs and SRPMs used to build them up in different + architectures. + +The CentOS Showroom +~~~~~~~~~~~~~~~~~~~ + +This visual manifestation communicates its existence through +production of industrial objects carrying The CentOS Brand. These +branded objects are directed to be distributed on social events and/or +shops. They provide a way of promotion and commercialization that may +help to reduce The CentOS Project expenses (e.g., electrical power, +hosting, servers, full-time-developers, etc.), in a similar way as +donations may do. + +- Stationery (e.g., Posters, Stickers, CD Lables and Sleeves). +- Clothes (e.g., Shirts, T-shirts, Pullovers, Caps). +- Installation media (e.g., CDs, DVD, Pen-drives). + +Corporate Behavior +------------------- + +The CentOS Project corporate behavior is focused on the effective +interaction of each member involved in the organization (e.g., core +developers, community members, etc.). It is related to ethics and +politics used to do the things inside the organization. It is related +to the sense of direction chosen by the organization and the way the +organization projects itself to achieve it. + +The CentOS Project corporate behavior is based on a meritocracy (the +more you do the more you are allowed to do). + +Corporate Structure +------------------- +The CentOS Project corporate structure is based on a Monolithic +Corporate Visual Identity Structure. In this configuration, one unique +name and one unique visual style is used in all visual manifestation +The CentOS Project is made of. + +In a monolithic corporate visual identity structure, internal and +external stakeholders use to feel a strong sensation of uniformity, +orientation, and identification with the organization. No matter if +you are visiting web sites, using the distribution, or acting on +social events, the one unique name and one unique visual style +connects them all to say: Hey! we are all part of The CentOS Project. + +Other corporate structures for The CentOS Project have been considered +as well. Such is the case of producing one different visual style for +each major release of The CentOS Distribution. This structure isn't +inconvenient at all, but some visual contradictions could be +introduced if it isn't applied correctly and we need to be aware of +it. To apply it correctly, we need to know what The CentOS Project is +made of. + +The CentOS Project, as organization, is mainly made of (but not +limited to) three visual manifestations: The CentOS Distribution, The +CentOS Web and The CentOS Showroom. Inside The CentOS Distribution +visual manifestations, The CentOS Project maintains near to four +different major releases of The CentOS Distribution, in parallel. +However, inside The CentOS Web visual manifestations, the content is +produced for no specific release information (e.g., there is no a +complete web site for each major release of The CentOS Distribution +individually, but one web site to cover them all). Likewise, the +content produced in The CentOS Showroom is industrially created for no +specific release, but The CentOS Project in general. + +In order to produce the The CentOS Project Monolithic Corporate Visual +Identity Structure correctly, we need to consider all the visual +manifestations The CentOS Project is made of, not just one of them. +If one different visual style is implemented for each major release of +The CentOS Distribution, which one of those different visual styles +would be used to cover the remaining visual manifestations The CentOS +Project is made of (e.g., The CentOS Web and The CentOS Showroom)? + +Probably you are thinking: yes, I see your point, but The CentOS Brand +connects them all already, why would we need to join them up into the +same visual style too, isn't it more work to do, and harder to +maintain? It is true that The CentOS Brand does connect all the +visual manifestations it is present on, but that connection is even +stronger if one unique visual style backups it. In fact, whatever +thing you do to strength the visual connection among The CentOS +Project visual manifestations would be very good in favor of The +CentOS Project recognition. + +Having just one visual style in all visual manifestations for eternity +would be a very boring thing and would give the idea of a visually +out-of-date project. So, there is no problem on creating new visual +styles for each new major release of The CentOS Distribution, in order +to refresh The CentOS Distribution visual style; the problem itself is +in not propagating the new visual style created for the new release of +The CentOS Distribution to all other visual manifestations The CentOS +Project is made of, in a way The CentOS Project could be recognized no +matter what visual manifestation be in front of us. Such lack of +uniformity is what introduces the visual contradiction The CentOS +Artwork SIG is precisely trying to solve by mean of automating the +production of corporate themes inside The CentOS Artwork Repository. + +// vim: set syntax=asciidoc: diff --git a/Documentation/identity.svgz b/Documentation/identity.svgz new file mode 100644 index 0000000..bf60578 Binary files /dev/null and b/Documentation/identity.svgz differ diff --git a/Documentation/licenses-gfdl.asciidoc b/Documentation/licenses-gfdl.asciidoc new file mode 100644 index 0000000..815a86c --- /dev/null +++ b/Documentation/licenses-gfdl.asciidoc @@ -0,0 +1,457 @@ += GNU Free Documentation License +Free Software Foundation +Version 1.2, November 2002 + +Copyright (C) 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. + +[[licenses-gfdl-section-1]] +== 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 GNU General Public License, 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. + +[[licenses-gfdl-section-2]] + +== 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. + +anchor:modified-version[Modified Version] + +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. + +anchor:secondary-section[Secondary Section] + +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. + +anchor:invariant-sections[Invariant Sections] + +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. + +anchor:cover-texts[Cover Texts] + +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. + +anchor:transparent[Transparent] + +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 ``<< +transparent>>'' 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. + +anchor:title-page[Title Page] + +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. + +[[licenses-gfdl-section-3]] + +== 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. + +[[licenses-gfdl-section-4]] + +== 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. + +[[licenses-gfdl-section-5]] + +== 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 +<>: + +a. 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. + +b. 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. + +c. State on the <> the name of the publisher of the +<>, as the publisher. + +d. Preserve all the copyright notices of the Document. + +e. Add an appropriate copyright notice for your modifications adjacent +to the other copyright notices. + +f. 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. + +g. Preserve in that license notice the full lists of +<> and required <> given in the +Document's license notice. + +h. Include an unaltered copy of this License. + +i. 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. + +j. 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. + +k. 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. + +l. 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. + +m. Delete any section Entitled ``Endorsements''. Such a section may +not be included in the <>. + +n. Do not retitle any existing section to be Entitled ``Endorsements'' +or to conflict in title with any <>. + +o. 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 <>. + +[[licenses-gfdl-section-6]] + +== 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''. + +[[licenses-gfdl-section-7]] + +== 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. + +[[licenses-gfdl-section-8]] + +== 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. + +[[licenses-gfdl-section-9]] + +== 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. + +[[licenses-gfdl-section-10]] + +== 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. + +[[licenses-gfdl-section-11]] + +== 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 +http://www.gnu.org/copyleft/[http://www.gnu.org/copyleft/]. + +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. + +[[licenses-gfdl-section-12]] + +== Appendix A. 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/Documentation/licenses-gpl.asciidoc b/Documentation/licenses-gpl.asciidoc new file mode 100644 index 0000000..19bc03f --- /dev/null +++ b/Documentation/licenses-gpl.asciidoc @@ -0,0 +1,426 @@ += GNU General Public License +Free Software Foundation +Version 2, June 1991 + +Copyright (C) 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. + +[[licenses-gpl-0]] + +== 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: + +1. copyright the software, and +2. 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. + +[[licenses-gpl-1]] + +== Terms and Conditions for Copying, Distribution and Modification + +[[licenses-gpl-1-0]] + +=== Section 0 + +This License applies to any program or other work which contains a +notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The ``Program'', +below, refers to any such program or work, and a ``work based on the +Program'' means either the Program or any derivative work under +copyright law: that is to say, a work containing the Program or a +portion of it, either verbatim or with modifications and/or translated +into another language. (Hereinafter, translation is included without +limitation in the term ``modification''.) Each licensee is addressed +as ``you''. + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + +[[licenses-gpl-1-1]] + +=== 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. + +[[licenses-gpl-1-2]] + +=== 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: + +a. You must cause the modified files to carry prominent notices +stating that you changed the files and the date of any change. + +b. 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. + +c. 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. + +[NOTE] +.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. + +[[licenses-gpl-1-3]] + +=== 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: + +a. 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, + +b. 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, + +c. 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. + +[[licenses-gpl-1-4]] + +=== 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. + +[[licenses-gpl-1-5]] + +=== 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. + +[[licenses-gpl-1-6]] + +=== 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. + +[[licenses-gpl-1-7]] + +=== 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. + +[[licenses-gpl-1-8]] + +=== 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. + +[[licenses-gpl-1-9]] + +=== 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. + +[[licenses-gpl-1-10]] + +=== 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. + +[[licenses-gpl-1-11]] + +=== 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. + +[[licenses-gpl-1-12]] + +=== 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._ + +[[licenses-gpl-2]] + +== Appendix A. 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. + +---------------------------------------------------------------------- + +Copyright (C) 19yy + +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. + +, 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/Documentation/repository-infra.svgz b/Documentation/repository-infra.svgz new file mode 100644 index 0000000..8626f1d Binary files /dev/null and b/Documentation/repository-infra.svgz differ diff --git a/Documentation/repository-version-schema.svgz b/Documentation/repository-version-schema.svgz new file mode 100644 index 0000000..13a04db Binary files /dev/null and b/Documentation/repository-version-schema.svgz differ diff --git a/Documentation/repository.asciidoc b/Documentation/repository.asciidoc new file mode 100644 index 0000000..20a3d95 --- /dev/null +++ b/Documentation/repository.asciidoc @@ -0,0 +1,1283 @@ +The CentOS Artwork Repository +============================= + +Organizations have 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 The +CentOS Community for helping on The CentOS Project 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 The CentOS Project 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. + +The CentOS Artwork Repository phases the question ``What can I do +for The CentOS Project?'' 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 The CentOS Artwork +Repository (through an automation script probably) to rebrand/update +the content of those packages inside The CentOS Distribution that must +include information specific to The CentOS Project itself (e.g., boot +loader, distribution installer, release notes, display managers, +release notes, web browsers default page, etc.). + +Most production tasks inside The CentOS Artwork Repository are focused +on the files needed to implement The CentOS Project corporate visual +identity.footnote:[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 The CentOS Project manifests its existence on.] 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 The CentOS Distribution are already covered by The CentOS +Project 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 The +CentOS Artwork Repository. + +In addition to visual manifestations, there are also emotional +feelings and ethical behaviours that must be considered as part of The +CentOS Project corporate identity. A pleasant experience in this area +includes The CentOS Wiki, specifically the way it was conceived and +administered. When the The CentOS Wiki was published, The CentOS +Project 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 The CentOS +Distribution, and reducing to zero the contraditions of precoceived +minds with respect, reason and passion. As result of this experience, +we found that The CentOS Community 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 The CentOS Community be able of moving through it. + +The CentOS Artwork Repository extends the feelings and ethicals +behaviours from The CentOS Wiki to itself by identifying the visual +manifestations The CentOS Project 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 The CentOS +Project and The CentOS Artwork Repository 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 ;-). + +[[corporate-mission]] +== Repository Mission + +The CentOS Artwork Repository exists to produce The CentOS Project +corporate visual identity. + +== Repository Infrastructure + +The CentOS Artwork Repository is made of one ``central repository'' +and many ``working copies'' of that central repository. The working +copies are independent one another, can be distributed all around the +world and provide a local place for designers, documenters, +translators and programmers to perform their work in a decentralized +way. The central repository, on the other hand, provides a common +place for all independent working copies to exchange data in the +community. + +image:repository-infra.png[repository-infra.png] + +=== Subversion + +The current infrastructure that holds The CentOS Artwork Repository on +the Internet, is made of the following components: + + * http://subversion.tigris.org/[Subversion] -- Modern Version Control System designed to replace CVS. + * http://trac.edgewall.org/[Trac] -- Enhanced wiki and issue tracking system. + * Httpd+WebDav as data exchanging route between the workstations and + the central repository, through the Internet. Httpd was configured + to provide service through SSL, so all traffic between the + workstations and the server be protected while it travels across + the Internet. The access rights are controlled by using a + combination of both Subversion's authorization files and Httpd's + password files. These files can be managed consistently through + Trac's WebAdmin plug-in. + +In this infrastructure, the first level of directories in the +repository provides the Subversion's standard trunk-branches-tags +layout. The second level of directories provides organization for +different work lines, as described in <>. All +other subsequent directory levels from second level on exist to +organize specific concepts related to the work line they belong to. + +=== Git + +In addition to current Subversion infrastructure, we are working on a +Git infrastructure with the intention of migrating the current +Subversion infrastructure up to it, progressively. The Git +infrastructure we are working on is made of the following components: + +* Git -- Fast version control system. +* Gitolite -- Highly flexible server for git directory version + tracker. +* Gitweb -- Simple web interface to git repositories. +* MantisBT -- Web-based issue tracking system. +* The data exchanging route between the working copies and the central + repository takes place through SSH. The access rights are controlled + by using a combination of SSH public keys and Gitolite's repository + configuration file. + +In this infrastructure, the first level of directories in the +repository provides organization for different work lines, as +described in <>. All other subsequent directory +levels from second level on exist to organize specific concepts +related to the work line they belong to. + +[[repo-convs-worklines]] +== Repository Work Lines + +The content production inside The CentOS Artwork Repository has been +divided into individual work lines that relate one another based on +the idea of doing one thing well. In this model, the content produced +individually by each work line is combined one another later to +achieve higher purposes (e.g., corporate identity for The CentOS +Project). The repository work lines, as conceived here, provide a +reliable environment for people to work synchronized and +decentralized. + +The action of combining work lines inside The CentOS Artwork +Repository is also known as the ``Production Cycle'' of CentOS +corporate visual identity. The rest of this section describes the +work lines available in the repository and how they integrate one +another. + +[[repo-convs-worklines-artworks]] +=== Graphic Design + +Graphic Design is the first component The CentOS Artwork SIG works out +in order to produce The CentOS Project corporate visual identity. +Through this work line, graphic designers create ``design models'' and +``artistic motifs'' for all the visual manifestation The CentOS +Project is made of. Once design models and artistic motifs are set in +place, graphic designers use the *render* module of *centos-art.sh* +script to combine them all into final images. + +The mission of Artworks work line is define all the visual +manifestations the The CentOS Project is made of and provide design +models and artistic motifs for them in order to produce the final +image files required to transmit the visual style that identifies The +CentOS Project as unique organization. + +The graphic design process takes place in the +Artworks/+ directory +stored at the first level of the repository directory structure. This +directory organizes themes (design models and artistic models), +palettes, brushes, icons, brands and customizations for the web +environment. + +To know more about The CentOS Project corporate visual identity, read +the article named +``_link:../../../Corporate/Final/en_US/index.html[The CentOS Project +Corporate Visual Identity]._'' + +[[repo-convs-worklines-l10n]] + +=== Localization + +Localization is the second component that must be worked out in the +production cycle of CentOS corporate visual identity. Through this +work line translators localize source files (e.g., SVG, DocBook, Shell +scripts) which are later used to produce localized images, localized +documentation and localized automation scripts. To localize source +files, translators use the *locale* module of *centos-art.sh* script +which takes care of retrieving translatable strings from source files +and provide a consistent localization interface based on GNU *gettext* +multi-lingual message production tool set and *xml2po* command. + +The mission of Localization work line is extending the visual identity +(produced in English language) to as many native languages as +possible, in order for people which doesn't understand English +language to feel more comfortable with The CentOS Project in their own +native languages. + +The localization process takes place inside the +Locales/+ directory +of each component that requires localization. This directory contains +the component related PO files organized in language-specific +directories. To know more about the specific localization process +read the *locale* module documentation. + +[[repo-convs-worlines-manuals]] + +=== Documentation + +Documentation is the third component that must be worked out in the +production cycle of corporate visual identity. Through this work line +documenters settle down the conceptual and practical uses around The +CentOS Artwork Repository and all the content produced inside it. To +write documentation, documenters use Asciidoc as source documentation +format and the *render* module of *centos-art.sh* script to transform +Asciidoc source documentation format into final output formats, +including man pages and html. + +The mission of Documentation work line is describe the standard +procedures The CentOS Artwork Repository relies on, as well as +conceive a place to help you understand what The CentOS Artwork +Repository is and what can you do with it. + +The Documentation work line takes place inside the +Documentation/+ +directory inside major components stored in the first directory level +of the repository (e.g., Artworks, Automation and Packages). + +[[repo-convs-worlines-packages]] +=== Packages + +The packages work line is the fourth component that must be worked out +in the corporate identity production cycle. Through this work line +packager gather final images, final translations and final +documentation related to artworks and put them all together inside RPM +packages. For this purpose, packagers use the *package* module of +*centos-art.sh* script which provides a consistent interface for +building packages inside the repository. + +The mission of Packages work line is package the information The +CentOS Project requires to re-brand The CentOS Distribution according +Red Hat redistribution guidelines. It is also the mission of this work +line to make The CentOS Artwork Repository easy to install, configure +and use by most graphic designers, documenters, programmers and +translators. + +The packages work line takes place in the +Packages/+ directory stored +at the first level of the repository directory structure. This +directory organizes both SOURCES and SPECS files used to build RPMS +and SRPMS files. In this directory, SOURCES and SPECS files are under +version control but RPMS and SRPMS produced from them are not. + +[[repo-convs-worklines-scripts]] +=== Automation + +The automation work line is the fifth and last component that must be +worked out in the corporate identity production cycle. This work line +closes the production cycle and provides the production standards +graphic designers, documenters, translators and packagers need to make +their work consistent and reusable. For this purpose, programmers +develop the *centos-art.sh* script. + +The mission of Automation work line is standardize the interaction of +work lines in a reliable way. + +The Automation work line takes place in the +Automation/+ directory +stored at the first level of the repository directory structure. +Presently, most of the automation work is done in Bash. + +== Preparing Your Workstation + +Once your workstation has been installed, it is time for you to +configure it. The configuration of your workstation consists on +defining your workplace, download a working copy from The CentOS Artwork Repository and +finally, run the *prepare* functionality of +*centos-art.sh* script to install/update the software +needed, render images, create links, and anything else needed. + +=== Define Your Workplace + +Once you've installed the workstation and it is up and running, you +need to register the user name you'll use for working. In this task +you need to use the commands *useradd* and *passwd* to create the user +name and set a password for it, respectively. These commands require +administrative privileges to be executed, so you need to login as +``root'' superuser for doing so. + +[CAUTION] +Do not use the ``root'' username for regular tasks inside your working +copy of The CentOS Artwork Repository. This is dangerous and might +provoke irreversible damages to your workstation. + +When you've registered your user name in the workstation, it provides +an identifier for you to open a user's session in the workstation and +a place to store the information you produce, as well. This place is +known as your home directory and is unique for each user registered in +the workstation. For example, if you register the user name john in +your workstation, your home directory would be located at ++/home/john/+. + +At this point it is important to define where to download the working +copy of The CentOS Artwork Repository inside your home directory. +This decision deserves special attention and should be implemented +carefully in order to grant a standard environment that could be +distributed. Let's see some alternatives. + +==== Different absolute paths + +Consider that you store your working copy under ++/home/john/Projects/artwork/+ and I store mine under ++/home/al/Projects/artwork/+, we'll end up refering the same files +inside our working copies through different absolute paths. This +alternative generates a contradiction when files which hold path +information inside are committed up to the central repository from +different working copies. The contradiction comes from the question: +which is the correct absolute path to use inside such files, yours or +mine? (None of them is, of course.) + +==== One unique absolute path + +Another case would be that where you and I ourselves use one unique +home directory (e.g., +/home/centos/Projects/artwork/+) to store the +working copy of The CentOS Artwork Repository in our own workstations, +but configure the subversion client to use different user names to +commit changes up from the working copy to the central repository. +This alternative might be not so good in situations where you and I +have to share the same workstation. In such cases, it would be +required that we both share the password information of the same +system user (the ``centos'' user in our example) which, in addition, +gives access to that user's subversion client configuration and this +way provokes the whole sense of using different subversion credentials +for committing changes to be lost. + +==== Different absolute paths, dynamic expansion, symbolic links, relative links, and environment variables + +With this solution it is possible to store working copies of The +CentOS Artwork Repository on different locations inside the same +workstation without lose relation between files. Here we use the +TCAR_WORKDIR environment variable to set the location of the working +copy inside the workstation. Later the centos-art.sh scripts uses this +value as reference to determine where the working copy is. This value +is also the one used for dynamic expansion inside design models and +other similar files. In the case of web projects where different +components are required to produce the final content, we create +symbolic links between them and use relative paths so it is possible +to reuse them and retain the relation between them in different +contexts. + +For example, lets consider the organization of XHTML manuals rendered +from DocBook source files. When you render a DocBook manual inside The +CentOS Artwork Repository it creates XHTML files. This XHTML files +use images and common style sheets for better presentation. Both of +these images and styles components live outside the XHTML structure +so, in order to make them available relatively to the XHTML structure, +we created symbolic links from the XHTML structure to the outside +location where they are in. The creation of symbolic links takes +place automatically when each DockBook manual is rendered through +*centos-art.sh*, which uses the value of TCAR_WORKDIR environment +variable as reference to determine the absolute path of the working +copy. + +Because absolute paths are no longer stored inside permanent files and +*centos-art.sh* script uses the TCAR_WORKDIR environment variable to +determine where the working copy is stored in the workstation, it +should be safe to download working copies of The CentOS Artwork +Repository anywhere in the workstation. One just have to be sure that +the value of TCAR_WORKDIR environment variable does match the location +of the working copy you are using. + +=== Download Your Working Copy + +In order to use The CentOS Artwork Repository you need to download a +working copy from the central repository into your workstation. To +download such working copy use the following command: + +---------------------------------------------------------------------- +git clone gitolite@centos.org.cu/centos-artwork.git +---------------------------------------------------------------------- + +This command will create your working copy inside your home directory, +specifically in a directory named artwork.git. Inside this directory you +will find all the files you need to work with inside The CentOS +Artwork Repository. If you want to have your working copy in a +location different to that one shown above. + +The first time you download the working copy it contains no image +files, nor documentation, or localized content inside it. This is +because all the files provided in the working copy are source files +(e.g., the files needed to produce other files) and it is up to you to +render them in order to produce the final files (e.g., images and +documentation) used to implement The CentOS Project corporate visual +identity. + +=== Configure Administrative Tasks + +Most of the administrative tasks you need to perform in your working +copy of The CentOS Artwork Repository are standardized inside the +*prepare* functionality of *centos-art.sh* script. Inside +*centos-art.sh* script, all administrative task are invoked through +the *sudo* command. Thus, in order for the *centos-art.sh* script to +perform administrative tasks, you need to update the *sudo*'s +configuration in a way that such administrative actions be allowed. + +At time of this writing the *centos-art.sh* script +implements just one administrative task, that is package management. +Nevertheless, in the future, other administrative tasks might be +included as well (e.g., installing themes locally from the working +copy for testing purposes.). + +To update the *sudo*'s configuration, execute the *visudo* command as +``root''. Later, uncoment the Cmnd_Alias related +to ``SOFTWARE'' and add a line for your username allowing software +commands. This configuration is illustrated in . + +[[repo-ws-config-sudoers-example]] +.The /etc/sudoers configuration file +====================================================================== +---------------------------------------------------------------------- +## Installation and management of software +Cmnd_Alias SOFTWARE = /bin/rpm, /usr/bin/up2date, /usr/bin/yum + +## Next comes the main part: which users can run what software on +## which machines (the sudoers file can be shared between multiple +## systems). +## Syntax: +## +## user MACHINE=COMMANDS +## +## The COMMANDS section may have other options added to it. +## +## Allow root to run any commands anywhere +root ALL=(ALL) ALL + +## Allow the centos user to run installation and management of +## software anywhere. +al ALL=(ALL) SOFTWARE +---------------------------------------------------------------------- +====================================================================== + +[[repo-ws-config-runout]] +=== Run Preparation Tool + +Once you've both downloaded a working copy from The CentOS Artwork +Repository and configured the *sudo* configuration file successfully, +run the *prepare* functionality of *centos-art.sh* script to complete +the configuration process using the following command: + +---------------------------------------------------------------------- +~/artwork/Scripts/Bash/centos-art.sh prepare +---------------------------------------------------------------------- + +[[repo-convs-filename-rfiles]] +== Repository File Names + +Inside The CentOS Artwork Repository, file names are always written in +lowercase. Digits (e.g., 0, 1, 2), hyphen (-), dot (.) and low line +(_) characters are also accepted. In case you use hyphen and dot +characters, don't use them as first character in the file name. + +=== File Names Written Correctly + +The following file names are written correctly: + +* +01-welcome.png+ +* +splash.png+ +* +anaconda_header.png+ + +=== File Names Written Incorrectly + +* +01-Welcome.png+ +* +-welcome.png+ +* +Splash.png+ +* +AnacondaHeader.png+ + +== Repository Link Names + +Inside The CentOS Artwork Repository, links are always symbolic and +follow the same name convention used by regular files, as described in +<>. + +== Repository Directory Names + +Inside The CentOS Artwork Repository, directory names are all written +capitalized and sometimes in cammel case. Digits (e.g., 0, 1, 2), +hyphen (-), dot (.) and low line (_) characters are also accepted. In +case you use hyphen and dot characters, don't use them as first +character in the directory name. + +=== Directory Names Written Correctly + +The following directory names are written correctly: + +* +Identity+ +* +Themes+ +* +Motifs+ +* +TreeFlower+ +* +0.0.1+ +* +0.0.1-35+ + +=== Directory Names Written Incorrectly + +The following directory names are written incorrectly: + +* +identity+ +* +theMes+ +* +MOTIFS+ +* +treeFlower+ +* +.0.1+ +* +.0.1-35+ + +== Repository Directory Structure + +Occasionly, you may find that new components of The CentOS Project +corporate visual identity need to be added to the repository in order +to work them out. If that is the case, the first question we need to +ask ourselves, before starting to create directories blindly all over, +is: _What is the right place to store it?_ + +To create a directory structure inside the repository you need to +define the concept behind it first. Later you need to create a new +directory inside the repository, remembering that there are locations +inside the repository that already define concepts you probably would +prefer to reuse. For example, the +Artworks/Themes/Motifs+ directory +stores artistic motifs of different themes, the ++Artworks/Themes/Models+ directory stores design models for themes, +the +Documentation+ directory stores documentation, +Locales+ stores +translation messages, and the +Automation+ stores automation scripts. + +The best suggestion we can probably give you would be to send a mail +with your questions to the mailto:centos-devel@centos.org[CentOS +developers mailing list] +(mailto:centos-devel@centos.org[centos-devel@centos.org]). This is +the place where development of The CentOS Artwork Repository takes place and surely, in +community, it will be possible to find a place for your new component +inside the repository. + +The following sub-sections describe relevant directories of The CentOS +Artwork Repository that you can use as reference to know where the +files you are looking for are stored in and where you can store new +files, as well. + +=== The +Artworks/+ Directory + +This directory contains files affecting the visual style of The CentOS +Project. This directory organizes Brushes, Gradients, Fonts, Palettes, +Patterns Themes and the web environment customizable files. + +=== The +Artworks/Brands/+ Directory + +This directory ... + +=== The +Artworks/Brushes/+ Directory + +This directory contains GIMP brushes. Brushes stored in this directory +will be available inside GIMP's brushes dialog. + +=== The +Artworks/Documentation/+ Directory + + +This directory ... + +=== The +Artworks/Fonts/+ Directory + +This directory contains font files. Font files stored in this +directory will be available to be used from applications like GIMP and +Inkscape. + +=== The +Artworks/Gradients/+ Directory + +This directory contains GIMP gradients. Gradients stored in this +directory will be available inside GIMP's gradients dialog. This +directory organizes gradient files inside + +=== The +Artworks/Icons/+ Directory + +This directory ... + +=== The +Artworks/Palettes/+ Directory + +This directory ... + +=== The +Artworks/Patterns/+ Directory + +This directory contains GIMP patterns. Patterns stored in this +directory will be available inside GIMP's patterns dialog. + +=== The +Artworks/Themes/+ Directory + +This directory ... + +=== The +Artworks/Webenv/+ Directory + +This directory ... + +=== The +Automation/+ Directory + +This directory ... + +== Repository Authoring + +The content produced inside The CentOS Artwork Repository is copyright +of The CentOS Project. This is something you, as author, should be +aware of because you are contributing your creation's rights to +someone else; The CentOS Project in this case. This way, your work is +distributed using ``The CentOS Project'' as copyright holder, not your +name (even you remain as natural author of the work). Because The +CentOS Project is the copyright holder, is the license chosen by The +CentOS Project the one applied to your work, so it is the one you need +to agree with before making a creation inside The CentOS Artwork +Repository. + +The CentOS Project is a community project controlled by its own +community of users. Inside the community, The CentOS Administrators +group is the higher authority and the only one able to set core +decision like the kind of license used inside the project and +subproject like The CentOS Artwork Repository. + +The redistribution conditions of The CentOS Artwork Repository are +described in ... + +== Repository Publishing + +When you perform changes inside your working copy, those changes are +local to your working copy only. In order for you to share your +changes with others, you need to push them up to the central +repository the working copy you are using was initially downloaded +from. To push your changes up to the central repository see +git-push(1) man page. + +Initially, you won't be able to publish your changes to The CentOS +Artwork Repository immediately. It is necessary that you prove your +interest in contributing first sending a mail to the +http://lists.centos.org/mailman/listinfo/centos-devel[CentOS +Developers mailing list] +(mailto:centos-devel@centos.org[centos-devel@centos.org]), preferably +in conjunction with a description of the changes you pretend to +commit. This restriction is necessary in order to protect the source +repository from spammers. + +Once you've received access to publish your changes, they will remain +valid to you and there is no need for you to request permission to +publish new changes as long as you behave as a good cooperating +citizen. + +As a good cooperating citizen one understand of a person who respects +the work already done by others and share ideas with authors before +changing relevant parts of their work, specially in situations when +the access required to realize the changes has been granted already. +Of course, there is a time when conversation has taken place already, +the paths has been traced and changing the work is so obvious that +there is no need for you to talk about it; that's because you already +did, you already built the trust to keep going. As complement, the +mailing list mentioned above is available for sharing ideas in a way +that good relationship between community citizens could be constantly +balanced. + +The relationship between community citizens is monitored by repository +administrators. Repository administrators are responsible of granting +that everything goes the way it needs to go in order for The CentOS Artwork Repository to +accomplish its mission (see <>). + +== Repository Copying Conditions + +The CentOS Project uses The CentOS Artwork Repository to produce The +CentOS Project corporate visual identity. + +The The CentOS Artwork Repository is not in the public domain; it is +copyrighted and there are restrictions on their distribution, but +these restrictions are designed to permit everything that a good +cooperating citizen would want to do. What is not allowed is to try +to prevent others from further sharing any version of this work that +they might get from you. + +Specifically, we want to make sure that you have the right to give +away copies of The CentOS Artwork Repository, that you receive source +code or else can get it if you want it, that you can change this work +or use pieces of it in new free works, and that you know you can do +these things. + +To make sure that everyone has such rights, we have to forbid you to +deprive anyone else of these rights. For example, if you distribute +copies of the The CentOS Artwork Repository, you must give the +recipients all the rights that you have. You must make sure that +they, too, receive or can get the source code. And you must tell them +their rights. + +Also, for our own protection, we must make certain that everyone finds +out that there is no warranty for the The CentOS Artwork Repository. +If this work is modified by someone else and passed on, we want their +recipients to know that what they have is not what we distributed, so +that any problems introduced by others will not reflect on our +reputation. + +The The CentOS Artwork Repository is released as a GPL work. +Individual packages used by The CentOS Artwork Repository include +their own licenses and the The CentOS Artwork Repository license +applies to all packages that it does not clash with. If there is a +clash between the The CentOS Artwork Repository license and individual +package licenses, the individual package license applies instead. + +The precise conditions of the license for the The CentOS Artwork +Repository are found in (...). This manual specifically is covered by +the conditions found in (...). + +[[repo-history]] +== History + +=== 2008 + +The CentOS Artwork Repository started at +mailto:centos-devel@centos.org[The CentOS Developers Mailing List] +around 2008, on a discussion about how to automate slide images used +by Anaconda (The CentOS Distribution installer). In such discussion, +http://wiki.centos.org/RalphAngenendt[Ralph Angenendt] rose up his +hand to ask --Do you have something to show?. + +To answer the question, +http://wiki.centos.org/AlainRegueraDelgado[Alain Reguera Delgado] +suggested a bash script which combined SVG and SED files in order to +produce PNG images in different languages --in conjunction with +the proposition of creating a Subversion repository where translations +and image production could be distributed inside The CentOS Community. + +http://wiki.centos.org/KaranbirSingh[Karanbir Singh] considered the +idea intresting and provided the infrastructure necessary to support +the effort. This way, https://projects.centos.org/trac/artwork[The +CentOS Artwork SIG] and https://projects.centos.org/svn/artwork[The +CentOS Artwork Repository] 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 The CentOS Artwork Repository, both using a +Trac web interface. + +Once The CentOS Artwork Repository was available, Alain Reguera +Delgado uploaded the bash script used to produce the Anaconda +slides;footnote:[See +https://projects.centos.org/trac/artwork/browser/Main/render.sh?rev=15] +Ralph Angenendt documented it very well;footnote:[See +https://projects.centos.org/trac/artwork/wiki/HowToTranslateSlides] +and people started to download working copies of The CentOS Artwork +Repository to produce slide images in their own +languages.footnote:[See +http://www.google.com/search?q=anaconda+slides+site%3Alists.centos.org] + +From this time on The CentOS Artwork Repository has been evolving into +an automated production environment where The CentOS Community can +conceive The CentOS Project corporate visual identity. + +The exact changes commited to The CentOS Artwork Repository through +history can be found in the +https://projects.centos.org/trac/artwork/timeline[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 <>. + +=== 2009 + +Around 2009, the rendition script was at a very rustic state where +only slide images could be produced, so it was redesigned to extend +the image production to other areas, different from slide images. In +this configuration, one SVG file was used as input to produce a +translated instance of it which, in turn, was used to produce one +translated PNG image as output. The SVG translated instance was +created through SED replacement commands. The translated PNG image was +created from the SVG translated instance using Inkscape command-line +interface. + +The repository directory structure was prepared to receive the +rendition script using design templates and translation files in the +same location. There was one directory structure for each art work +that needed to be produced. In this configuration, if you would want +to produce the same art work with a different visual style or +structure, it was needed to create a new directory structure for it +because both the image structure and the image visual style were +together in the design template. + +The rendition script was moved to a common place and linked from +different directory structures. There was no need to have the same +code in different directory structures if it could be in just one +place and then be linked from different locations. + +Corporate identity concepts began to be considered. As referece, it +was used the book "Corporate Identity" by Wally Olins (1989) and +http://en.wikipedia.org/Corporate_identity[Wikipedia related links]. +This way, the rendition script main's goal becomes to: _automate the +production process of a monolithic corporate visual identity +structure, based on the mission and the release schema of The CentOS +Project_. + +The repository directory structures began to be documented by mean of +flat text files. Later, documentation in flat text files was moved +onto LaTeX format and this way The CentOS Artwork User Guide was +initiated. + +=== 2010 + +Around 2010, the rendition script changed its name from *render.sh* to +*centos-art.sh* and became a collection of functionalities where +rendition was just one among others (e.g., documentation and +localization). + +The *centos-art.sh* was initially conceived to automate frequent tasks +inside the repository based in the idea of Unix toolbox: to create +small and specialized tools that do one thing well. This way, +functionalities inside *centos-art.sh* began to be identified and +separated one another. For example, when images were rendered, there +was no need to load functionalities related to documentation manual. +This layout moved us onto ``common functionalities'' and ``specific +functionalities'' inside *centos-art.sh* script. Common +functionalities are loaded when *centos-art.sh* script is initiated +and are available to specific functionalities. + +Suddenly, no need was found to keep all the links spreaded around the +repository in order to execute the *centos-art.sh* script from +different locations. The *centos-art* command-line interface was used +instead. The *centos-art* command-line interface is a symbolic link +stored inside the +\~/bin+ directory pointing to *centos-art.sh* +script. As default configuration, inside The CentOS Distribution, the +path to +\~/bin+ is included in the search path for commands (see PATH +environment variable). This way, using the *centos-art* command-line +interface, it is possible to execute the *centos-art.sh* script from +virtually anywhere inside the workstation, just as we frequently do +with regular commands. + +Start using GNU getopt as default option parser inside the +*centos-art.sh* script. + +The repository directory structure was updated to improve the +implementation of corporate visual identity concepts. Specially in +the area related to themes. Having both structure and style in the +same file introduced content duplication when producing art works. +Because of this reason, they were separated into two different +directory structures: the design models and the artistic motifs +directory structures. From this point on, the *centos-art.sh* was +able to produce themes as result of arbitrary combinations between +design models (structure) and artistic motifs (visual styles). + +In the documentation area, the documents in LaTeX format were migrated +to Texinfo format. In this configuration, each directory structure in +the repository has a documentation entry associated in a Texinfo +structure which can be read, edited and administered (e.g., renamed, +deleted and copied) interactively through *centos-art.sh* script. +Additionally, the texi2html program was used to produced customized +XHTML output in conjunction with CSS from The CentOS Web Environment. + +=== 2011 + +Around 2011, the *centos-art.sh* script was +redesigned to start translating XML-based files (e.g., SVG and Docbook +files) through *xml2po* program and shell scripts +(e.g., Bash scripts) through GNU gettext tools. This configuration +provided a stronger localization interface for graphic designers, +translators and programmers. The SED replacement files are no longer +used to handle localization. + +The *render*, *help* and +*locale* functionalities consolidated themselves as +the most frequent tasks performed in The CentOS Artwork Repository working copy. +Additionally, the *prepare* and +*tuneup* functionalities were also maintained as +useful tasks. + +In the documentation area, it was introduced the transformation of +localized DocBook XML DTD instances through the +*render* and *locale* +functionalities. In this configuration, you use +*locale* functionality to localize DocBook source +files to your prefered language and later, using the +*render* functionality, you can produce the +localized XTHML and PDF output as specified in a XSLT layer. +Unfortunly, the transformation DocBook XML -> FO -> PDF (through +PassiveTex) seems to be buggy inside CentOS 5.5, so it was commented +inside the *centos-art.sh* script. Most documentation +is now organized in DocBook format, even Texinfo format remains as the +only format with automated production tasks. + +In the automation area, the *centos-art.sh* script +introduced the capability of reading configuration files. The main +goal here was moving some command-line options from functionalities +onto a more persistent medium. Most configuration files were set to +define the position of brands inside images and documentation manual +specific options. + +[[repo-history-2012]] +=== 2012 + +The CentOS Artwork Repository development was eventually stopped at +November 2011 until July 2012 when we needed to make the +*centos-art.sh* script a bit more customizable than it presently was. +For example, it was considered as a need that functionalities inside +the *centos-art.sh* script must be not just conceived independent one +another but reusable in different contexts as well. + +[[repo-history-2012-1]] +==== Make Localization Of *centos-art.sh* Script Specific To Different Contexts + +The procedure used to locale messages inside the *centos-art.sh* +script has to be re-designed in order to accept such pluggable +behavior into the script. We couldn't publish unique ++centos-art.sh.po+ and +centos-art.sh.mo+ files because they may +contain different information in different contexts. For example, if +you are using the *render* and +*help* functionalities you only need translation +messages for them and not those from other functionalities that may +exist in the central repository but you didn't download nor use into +your working copy. + +One solution for this could be to have independent PO files for each +functionality of *centos-art.sh* script which are +combined to create the final PO and MO files that +*gettext* uses to retrive translated strings +when *centos-art.sh* script is running. For this +solution to be effective, you must be selective about the +functionalities and locales directories you download into your working +copy. For example, if you want to use the render functionality and its +locale messages only, you must download the required directories and +exclude others. + +[NOTE] +====================================================================== +In case you don't want to be selective and download the whole +repository, the creation of the +centos-art.sh.po+, ++centos-art.sh.pot+ and ++centos-art.sh.mo+ files will occur automatically +the first time you run the *prepare* functionality +(which require the *locale* functionality to be +available), or later, by running the following command: + +---------------------------------------------------------------------- +centos-art locale Scripts/Bash --update +---------------------------------------------------------------------- + +For more information about the *prepare* and *locale* functionalities, +see their respective manuals. +====================================================================== + +[[repo-history-2012-2]] +.Directory structure of a rendering-only context +====================================================================== +---------------------------------------------------------------------- +/home/centos/Projects/artwork/ +|-- Locales/ +| `-- Scripts/ +| `-- Bash/ +| `-- es_ES/ +| |-- Functions/ +| | |-- Commons/ +| | | |-- messages.po +| | | `-- messages.pot +| | |-- Locales/ +| | | |-- messages.po +| | | `-- messages.pot +| | `-- Render/ +| | |-- messages.po +| | `-- messages.pot +| |-- LC_MESSAGES/ +| | `-- centos-art.sh.mo +| |-- centos-art.sh.po +| `-- centos-art.sh.pot +`-- Scripts/ + `-- Bash/ + |-- Functions/ + | |-- Commons/ + | |-- Locales/ + | `-- Render/ + `-- centos-art.sh +---------------------------------------------------------------------- +====================================================================== + +As shown in <>, both *Commons* and *Locales* +functionalities will always be required directories. The +Commons+ +directory contains the common functionalities and the *Locales* +directory contains the standard procedures you need to run in order to +build the final +centos-art.sh.mo+ file used by *gettext* to retrive +translation strings when the *centos-art.sh* script is running. +Remember that +centos-art.sh.pot+, +centos-art.sh.po+ files aren't +under version control and they are built by combining each +funtionality message.po file into a PO and later a MO file. + +A practical example of using the solution described above may be found +when you are working on the corporate identity of The CentOS Project +and then need to start a new corporate identity project for another +organization. You want to keep the directory structure of The CentOS +Artwork Repository and its automation tool, the *centos-art.sh* +script. Your new project requires you to introduce new +functionalities to *centos-art.sh* which don't fit the needs of The +CentOS Project (e.g., you want to introduce a *report* functionality +to mesure how much connect time do you consume through your PPP +internface.) or you just want to keep the directory structure of your +new project as simple as possible. + +To go through this it is possible to mix specific parts of different +central repositories into one single working copy. This is the +working copy you'll use to manage your new project. In +<>, we see how the +Render+, +Locales+ and ++Commons+ directories which come from the The CentOS Artwork +Repository has been integrated into the working copy of your new +project. + +---------------------------------------------------------------------- +/home/al/Projects/Myapp/ +|-- Locales/ +| `-- Scripts/ +| `-- Bash/ +| `-- es_ES/ +| |-- Functions/ +| | |-- Commons/ <--| from https://projects.centos.org/svn/artwork/ +| | | |-- messages.po +| | | `-- messages.pot +| | |-- Locales/ <--| from https://projects.centos.org/svn/artwork/ +| | | |-- messages.po +| | | `-- messages.pot +| | |-- Render/ <--| from https://projects.centos.org/svn/artwork/ +| | | |-- messages.po +| | | `-- messages.pot +| | `-- Report/ +| | |-- messages.po +| | `-- messages.pot +| |-- LC_MESSAGES/ +| | `-- myapp.sh.mo +| |-- myapp.sh.po +| `-- myapp.sh.pot +`-- Scripts/ + `-- Bash/ + |-- Functions/ + | |-- Commons/ <--| from https://projects.centos.org/svn/artwork/ + | |-- Locales/ <--| from https://projects.centos.org/svn/artwork/ + | |-- Render/ <--| from https://projects.centos.org/svn/artwork/ + | `-- Report/ + `-- myapp.sh +---------------------------------------------------------------------- + +At this point, your working copy contains files from two different +central repositories. One repository provides the files of your new +organization project and the other one provides the files related to +the *render* functionality from The CentOS Artwork Repository. In +this environment, all updates commited to the +Render+, +Locales+ and ++Commons+ directories at The CentOS Artwork Repository will be +available to you too, the next time you update your working copy. +Likewise, if you change something in any of these directories and +commit your changes, your changes will be available to poeple working +in The CentOS Artwork Repository the next time they update their +working copies. + +Understanding the need of mixing different central repositories into a +single working copy is an important step for reusing the +functionalities that come with centos-art.sh script, but it is not +enough if you want to customize the information produced by it. By +default, the centos-art.sh script uses information related to The +CentOS Project. You probably need to change this if you are producing +images to a different organization than The CentOS Project. For +example, some of the information you might need to change would be the +copyright holder, brands, domain names, mailing lists, and so forth. +To change this information you need to duplicate the file ++centos-art.sh+ and rename it to something else. Later, you need to +edit the renamed version and change variables inside according your +needs. In <>, we used the name *myapp.sh* instead +of *centos-art.sh* so the information we set inside it could reflect +the specific needs that motivated the creation of a new project +without affecting those from The CentOS Project. + +Most of the information you need to change in your duplicated version +of +centos-art.sh+ file is controlled by a set of read-only variables. +You modify these variables here and they will be available all along +the script execution time. For example, you can change the value of +CLI_WRKCOPY variable inside your duplicated version of +centos-art.sh+ +to change the absolute path you use to store your working copy. + +==== Enhance The CentOS Logo Construction + +The CentOS Logo is made of two different components known as The +CentOS Symbol and The CentOS Type. Presently (at the end of +September), to produce these components, we create one SVG image for +each PNG image we want to produce, store it in ++Identity/Models/Brands/Logos+ directory structure and run the +command: + +---------------------------------------------------------------------- +centos-art render Identity/Images/Brands/Logos* +---------------------------------------------------------------------- + +This model works and scales well in situations when there isn't a need +to reuse final images among themselves. However, when you need to +reuse images among themselves, a better solution is required. The goal +here would be: don't create SVG images for PNG +images you can build based on other PNG images. + +This might be achieved through one of the following ways: + +- Create a new specific functionality to achieved the goal. Needed + because the *render* specific functionality uses SVG files as + reference to build images (i.e., one SVG image produces one PNG + image). + +- Modify *render* functionality to work in different modes based on + file type or file extension. The first mode would use SVG files as + reference to build PNG images (just as it was doing so far). The + second mode would use a configuration file named +render.conf+ as + reference inside the design models directory you want to produce + images for so as to build the related PNG images. In this second + case, the configuration file specifies how final PNG images will be + produced (e.g., by appending or overlapping them one another). + +For example, consider the following command-line: + +---------------------------------------------------------------------- +centos-art render Identity/Images/Brands/Logos +---------------------------------------------------------------------- + +This command should evaluate which type of rendition will be done, +based on whether the source file is a scalable vector graphic (SVG) or +a configuration file. To make this decision, the *centos-art.sh* +script looks for SVG files first, and configuration files later. When +SVG files are found, the *centos-art.sh* script uses a list of SVG +files and process them one by one excluding any related configuration +file that could exist. On the other hand, if no SVG file is found +inside the related design model directory structure, the +*centos-art.sh* script will use the configuration file with the name ++render.conf+ to create images as specified inside it. When neither a +SVG or a configuration file is found inside the design model directory +structure, the *centos-art.sh* script finishes its execution without +any error message. For example, if no SVG file is found inside ++Identity/Models/Brands/Logos/+ directory and the ++Identity/Models/Brands/Logos/images.conf+ configuration file exists +therein with the following content: + +---------------------------------------------------------------------- +[centos.png] +models = "Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz" +formats = "xpm jpg" +heights = "48 78" +fgcolor = "000000 ffffff" +bgcolor = "ffffff-0" +command = "/usr/bin/convert +append" + +[centos-artwork.png] +models = "Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz Identity/Models/Brands/Types/artwork.svgz" +formats = "xpm jpg" +heights = "48 78" +fgcolor = "000000 ffffff" +bgcolor = "ffffff-0" +command = "/usr/bin/convert +append" +---------------------------------------------------------------------- + +The *centos-art.sh* script should produce the +following image files: + +---------------------------------------------------------------------- +Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.jpg +Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.png +Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.xpm +Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.png +Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.jpg +Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.xmp +Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.jpg +Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.png +Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.xpm +Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.png +Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.jpg +Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.xmp +Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.jpg +Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.png +Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.xpm +Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.png +Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.jpg +Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.xmp +Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.jpg +Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.png +Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.xpm +Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.png +Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.jpg +Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.xmp +---------------------------------------------------------------------- + +The final location for storing images output inside the repository is +determined by using the design model directory provided as argument. +Basically, the *centos-art.sh* script changes the +path components from Models to Images and adds foreground color, +background color, height value and image name to it to differentiate +rendered images. + +In case you need to restrict the amount of files you want to produce +including their formats, heights, colors and commands, you need to +modify the content of the related +render.conf+ configuration file. +There is not any command-line option available for such tasks. The +most *render* command-line options can do for you is when there are +more than one configuration file inside the same design model +directory and you need to specify which one of them will be used as +reference. In such case you can use the + option. + +When images are produced through configuration files, the +*centos-art.sh* script takes the order provided in +the list of design models to build the list of images you will work +with through the command specified. For example, the order in which +images will be appended or overlapped. + +Localization of logo images will not be and must not be supported in +any way. That would bring disastrous confusion in the area of visual +recognition. + +=== 2013 + +Development of CentOS Artwork Repository was eventually stopped at +November, 2012, when I moved myself from Cienfuegos to Havana city for +working. I returned on May 14th of 2013 and continued developing The +CentOS Artwork Repository at home. Considered a +Git+Gitolite+Gitweb+MantisBT infrastructure for CentOS Artwork +Repository and started working on it in my workstation. This, in +order to implement a distributed work flow for The CentOS Artwork +Repository based on Git version control system. + +[[repository-history-2013-UpdateRepositoryLayout]] +==== Update Repository Directories Structure + +I face the following situation: I am working on a documentation +project named ``solinfo-network''. While I was organizing it, I found +that the directory structure of The CentOS Artwork Repository fits +quite well the needs of ``solinfo-network'' documentation project. +However, I don't want to duplicate automation scripts in two separate +projects, but share them between themselves (i.e., changes committed +to automation scripts are pushed to one single place, not two.). + +When we use Subversion repositories, it is possible to checkout +specific parts of different repositories into a new repository. This +is very useful if we need to create several projects that share the +same component and we don't want to duplicate the common component in +two or more different projects but ``share'' it between them. + +When we use Git repository, it is not possible to checkout specific +parts of a repository but the complete tree. So, in order to share +common components of a repository we need to create one repository for +each common component we want to share and then use Git +submodulessee progit-book, page 152. This +requires that brand new repositories be created for each component we +want to share. + +In both situations, including Git and Subversion repositories, it is +necessary that we define very well the structure of each component we +want to share, so it can be ``plugged'' nicely into other projects. +Likewise, other projects must have the same directory structure the +pluggable component was design to fit in. If these two conditions can +be reached, it would be possible to reuse repositories components and +concentrate efforts. The current directory structure The CentOS +Artwork Repository is set in allows components inside Subversion +repositories to be reused by related working copies. However, we +cannot do the same if it is stored in a Git repository. In order for +Git repositories to be able to share components with other Git +repositories, The CentOS Artwork Repository directory structure needs +to be reorganized to better delineate each component the repository is +made of. + +// vim: set syntax=asciidoc: diff --git a/Documentation/tcar-ug.asciidoc b/Documentation/tcar-ug.asciidoc new file mode 100644 index 0000000..73ddbb7 --- /dev/null +++ b/Documentation/tcar-ug.asciidoc @@ -0,0 +1,7 @@ +The CentOS Artwork User's Guide +=============================== +CentOS Artwork SIG +v0.1, Nov 30 2013 + +include::identity.asciidoc[] +include::repository.asciidoc[] diff --git a/Documentation/tcar-ug.conf b/Documentation/tcar-ug.conf new file mode 100644 index 0000000..cb20593 --- /dev/null +++ b/Documentation/tcar-ug.conf @@ -0,0 +1,143 @@ +[repository-infra.png] +render-type = "svg" +render-flow = "base" +render-from = "repository-infra.svgz" +export-id = "CENTOSARTWORK" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/repository-infra.svgz.po" +command = "/usr/bin/convert -colors 128" + +[repository-version-schema.png] +render-type = "svg" +render-flow = "base" +render-from = "repository-version-schema.svgz" +export-id = "CENTOSARTWORK" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/repository-version-schema.svgz.po" +command = "/usr/bin/convert -colors 128" + +[identity.png] +render-type = "svg" +render-flow = "base" +render-from = "identity.svgz" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/identity.svgz.po" +command = "/usr/bin/convert -colors 32" + +[identity-fonts.png] +render-type = "svg" +render-flow = "base" +render-from = "identity-fonts.svgz" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/identity-fonts.svgz.po" +command = "/usr/bin/convert -colors 128" + +[identity-logo-howto.png] +render-type = "svg" +render-flow = "base" +render-from = "identity-logo-howto.svgz" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/identity-logo-howto.svgz.po" +command = "/usr/bin/convert -colors 128" + +[identity-symbol-howto-1of4.png] +render-type = "svg" +render-flow = "base" +render-from = "identity-symbol-howto-1of4.svgz" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/identity-symbol-howto-1of4.svgz.po" +command = "/usr/bin/convert -colors 128" + +[identity-symbol-howto-2of4.png] +render-type = "svg" +render-flow = "base" +render-from = "identity-symbol-howto-2of4.svgz" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/identity-symbol-howto-2of4.svgz.po" +command = "/usr/bin/convert -colors 128" + +[identity-symbol-howto-3of4.png] +render-type = "svg" +render-flow = "base" +render-from = "identity-symbol-howto-3of4.svgz" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/identity-symbol-howto-3of4.svgz.po" +command = "/usr/bin/convert -colors 128" + +[identity-symbol-howto-4of4.png] +render-type = "svg" +render-flow = "base" +render-from = "identity-symbol-howto-4of4.svgz" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/identity-symbol-howto-4of4.svgz.po" +command = "/usr/bin/convert -colors 128" + +[identity-themes.png] +render-type = "svg" +render-flow = "base" +render-from = "identity-themes.svgz" +export-id = "CENTOSARTWORK" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/identity-themes.svgz.po" +command = "/usr/bin/convert -colors 128" + +[identity-clothes-head.png] +render-type = "svg" +render-flow = "base" +render-from = "identity-clothes-head.svgz" +export-id = "CENTOSARTWORK" +command = "/usr/bin/convert" + +[identity-clothes-torso.png] +render-type = "svg" +render-flow = "base" +render-from = "identity-clothes-torso.svgz" +export-id = "CENTOSARTWORK" +command = "/usr/bin/convert" + +[identity-colors.png] +render-type = "svg" +render-flow = "base" +render-from = "identity-colors.svgz" +export-id = "CENTOSARTWORK" +command = "/usr/bin/convert" + +[identity-symbol.png] +render-type = "svg" +render-flow = "extended" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Symbols/Webenv/centos.svgz" +export-id = "CENTOSARTWORK" +heights = "200" +fgcolors = "ad7fa8" +bgcolors = "ffffff-0" +formats = "png" + +[identity-type.png] +render-type = "svg" +render-flow = "base" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.svgz" +export-id = "CENTOSARTWORK" +heights = "200" +fgcolors = "ad7fa8" +bgcolors = "ffffff-0" +formats = "png" + +[identity-type-release.png] +render-type = "svg" +render-flow = "extended" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/{Webenv/centos.svgz,Numbers/6.svgz}" +export-id = "CENTOSARTWORK" +heights = "200" +fgcolors = "ad7fa8" +bgcolors = "ffffff-0" +formats = "png" + +[identity-logo.png] +render-type = "svg" +render-flow = "extended" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.svgz}" +export-id = "CENTOSARTWORK" +heights = "200" +fgcolors = "ad7fa8" +bgcolors = "ffffff-0" +formats = "png" + +[tcar-ug.html] +render-type = "asciidoc" +render-flow = "article" +render-from = "identity.asciidoc" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/tcar-ug.asciidoc.po" +images-from = "${TCAR_BASEDIR}/Artworks/Icons/Webenv/Final" +styles-from = "${TCAR_BASEDIR}/Artworks/Webenv/Docbook/1.69.1/Css" +formats = "xhtml" +render-page = "single chunks" diff --git a/Licenses/Locales/en_US/gfdl.asciidoc.po b/Licenses/Locales/en_US/gfdl.asciidoc.po deleted file mode 100644 index 7c9b686..0000000 --- a/Licenses/Locales/en_US/gfdl.asciidoc.po +++ /dev/null @@ -1,876 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: gfdl.asciidoc 0.6\n" -"POT-Creation-Date: 2013-11-13 13:44-0500\n" -"PO-Revision-Date: 2013-11-13 13:44-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "GNU Free Documentation License" -msgstr "GNU Free Documentation License" - -msgid "November 2002" -msgstr "November 2002" - -msgid "Free" -msgstr "Free" - -msgid "Software" -msgstr "Software" - -msgid "Foundation" -msgstr "Foundation" - -msgid "http://www.fsf.org/" -msgstr "http://www.fsf.org/" - -msgid "FSF" -msgstr "FSF" - -msgid "1.2" -msgstr "1.2" - -msgid "" -"Copyright © 2000, 2001, 2002 Free Software Foundation, Inc. 675 Mass Ave, " -"Cambridge, MA 02139, USA" -msgstr "" -"Copyright © 2000, 2001, 2002 Free Software Foundation, Inc. 675 Mass Ave, " -"Cambridge, MA 02139, USA" - -msgid "" -"Everyone is permitted to copy and distribute verbatim copies of this license " -"document, but changing it is not allowed." -msgstr "" -"Everyone is permitted to copy and distribute verbatim copies of this license " -"document, but changing it is not allowed." - -msgid "Preamble" -msgstr "Preamble" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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 " -"GNU General Public License, which is a copyleft license designed for free " -"software." -msgstr "" -"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 " -"GNU General Public License, which is a copyleft license designed for free " -"software." - -msgid "" -"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." -msgstr "" -"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." - -msgid "Applicability and definitions" -msgstr "Applicability and definitions" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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 “<< transparent>>” is called " -"“Opaque”." -msgstr "" -"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 “<< transparent>>” is called " -"“Opaque”." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "Verbatim copying" -msgstr "Verbatim copying" - -msgid "" -"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 ." -msgstr "" -"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 ." - -msgid "" -"You may also lend copies, under the same conditions stated above, and you " -"may publicly display copies." -msgstr "" -"You may also lend copies, under the same conditions stated above, and you " -"may publicly display copies." - -msgid "Copying in quantity" -msgstr "Copying in quantity" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "Modifications" -msgstr "Modifications" - -msgid "" -"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 :" -msgstr "" -"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 :" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"State on the the name of the publisher of the " -", as the publisher." -msgstr "" -"State on the the name of the publisher of the " -", as the publisher." - -msgid "Preserve all the copyright notices of the Document." -msgstr "Preserve all the copyright notices of the Document." - -msgid "" -"Add an appropriate copyright notice for your modifications adjacent to the " -"other copyright notices." -msgstr "" -"Add an appropriate copyright notice for your modifications adjacent to the " -"other copyright notices." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"Preserve in that license notice the full lists of and required given in the " -"Document's license notice." -msgstr "" -"Preserve in that license notice the full lists of and required given in the " -"Document's license notice." - -msgid "Include an unaltered copy of this License." -msgstr "Include an unaltered copy of this License." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"Delete any section Entitled “Endorsements”. Such a section may not be " -"included in the ." -msgstr "" -"Delete any section Entitled “Endorsements”. Such a section may not be " -"included in the ." - -msgid "" -"Do not retitle any existing section to be Entitled “Endorsements” or to " -"conflict in title with any ." -msgstr "" -"Do not retitle any existing section to be Entitled “Endorsements” or to " -"conflict in title with any ." - -msgid "Preserve any Warranty Disclaimers." -msgstr "Preserve any Warranty Disclaimers." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"You may add a section Entitled “Endorsements”, provided it contains nothing " -"but endorsements of your by various " -"parties&ndash;for example, statements of peer review or that the text " -"has been approved by an organization as the authoritative definition of a " -"standard." -msgstr "" -"You may add a section Entitled “Endorsements”, provided it contains nothing " -"but endorsements of your by various " -"parties&ndash;for example, statements of peer review or that the text " -"has been approved by an organization as the authoritative definition of a " -"standard." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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 ." -msgstr "" -"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 ." - -msgid "Combining documents" -msgstr "Combining documents" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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”." -msgstr "" -"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”." - -msgid "Collection of documents" -msgstr "Collection of documents" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "Aggregation with independent works" -msgstr "Aggregation with independent works" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "Translations" -msgstr "Translations" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "Termination" -msgstr "Termination" - -msgid "" -"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." -msgstr "" -"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." - -msgid "Future Revisions of this License" -msgstr "Future Revisions of this License" - -msgid "" -"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 http://www.gnu.org/copyleft/." -msgstr "" -"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 http://www.gnu.org/copyleft/." - -msgid "" -"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." -msgstr "" -"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." - -msgid "How to use this License for your documents" -msgstr "How to use this License for your documents" - -msgid "" -"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:" -msgstr "" -"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:" - -#, no-wrap -msgid "" -"Copyright (C) YEAR YOUR NAME.\n" -"\n" -"Permission is granted to copy, distribute and/or modify this\n" -"document under the terms of the GNU Free Documentation License,\n" -"Version 1.2 or any later version published by the Free Software\n" -"Foundation; with no Invariant Sections, no Front-Cover Texts, and\n" -"no Back-Cover Texts. A copy of the license is included in the\n" -"section entitled ``GNU Free Documentation License''." -msgstr "" -"Copyright (C) YEAR YOUR NAME.\n" -"\n" -"Permission is granted to copy, distribute and/or modify this\n" -"document under the terms of the GNU Free Documentation License,\n" -"Version 1.2 or any later version published by the Free Software\n" -"Foundation; with no Invariant Sections, no Front-Cover Texts, and\n" -"no Back-Cover Texts. A copy of the license is included in the\n" -"section entitled ``GNU Free Documentation License''." - -msgid "" -"If you have , Front-Cover Texts and " -"Back-Cover Texts, replace the “with…Texts”. line with this:" -msgstr "" -"If you have , Front-Cover Texts and " -"Back-Cover Texts, replace the “with…Texts”. line with this:" - -#, no-wrap -msgid "" -"with the Invariant Sections being LIST THEIR TITLES, with the\n" -"Front-Cover Texts being LIST, and with the Back-Cover Texts being\n" -"LIST." -msgstr "" -"with the Invariant Sections being LIST THEIR TITLES, with the\n" -"Front-Cover Texts being LIST, and with the Back-Cover Texts being\n" -"LIST." - -msgid "" -"If you have without , or some other combination of the three, merge those two " -"alternatives to suit the situation." -msgstr "" -"If you have without , or some other combination of the three, merge those two " -"alternatives to suit the situation." - -msgid "" -"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." -msgstr "" -"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." - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Licenses/Locales/en_US/gpl.asciidoc.po b/Licenses/Locales/en_US/gpl.asciidoc.po deleted file mode 100644 index 0a61c7a..0000000 --- a/Licenses/Locales/en_US/gpl.asciidoc.po +++ /dev/null @@ -1,784 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: gpl.asciidoc 0.6\n" -"POT-Creation-Date: 2013-11-13 13:44-0500\n" -"PO-Revision-Date: 2013-11-13 13:44-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "GNU General Public License" -msgstr "GNU General Public License" - -msgid "June 1991" -msgstr "June 1991" - -msgid "Free" -msgstr "Free" - -msgid "Software" -msgstr "Software" - -msgid "Foundation" -msgstr "Foundation" - -msgid "FSF" -msgstr "FSF" - -msgid "2" -msgstr "2" - -msgid "" -"Copyright © 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, " -"Cambridge, MA 02139, USA" -msgstr "" -"Copyright © 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, " -"Cambridge, MA 02139, USA" - -msgid "" -"Everyone is permitted to copy and distribute verbatim copies of this license " -"document, but changing it is not allowed." -msgstr "" -"Everyone is permitted to copy and distribute verbatim copies of this license " -"document, but changing it is not allowed." - -msgid "Preamble" -msgstr "Preamble" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "We protect your rights with two steps:" -msgstr "We protect your rights with two steps:" - -msgid "copyright the software, and" -msgstr "copyright the software, and" - -msgid "" -"offer you this license which gives you legal permission to copy, distribute " -"and/or modify the software." -msgstr "" -"offer you this license which gives you legal permission to copy, distribute " -"and/or modify the software." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"The precise terms and conditions for copying, distribution and modification " -"follow." -msgstr "" -"The precise terms and conditions for copying, distribution and modification " -"follow." - -msgid "Terms and Conditions for Copying, Distribution and Modification" -msgstr "Terms and Conditions for Copying, Distribution and Modification" - -#, fuzzy -msgid "Section 0" -msgstr "Section 10" - -msgid "" -"This License applies to any program or other work which contains a notice " -"placed by the copyright holder saying it may be distributed under the terms " -"of this General Public License. The “Program”, below, refers to any such " -"program or work, and a “work based on the Program” means either the Program " -"or any derivative work under copyright law: that is to say, a work " -"containing the Program or a portion of it, either verbatim or with " -"modifications and/or translated into another language. (Hereinafter, " -"translation is included without limitation in the term “modification”.) Each " -"licensee is addressed as “you”." -msgstr "" - -msgid "" -"Activities other than copying, distribution and modification are not covered " -"by this License; they are outside its scope. The act of running the Program " -"is not restricted, and the output from the Program is covered only if its " -"contents constitute a work based on the Program (independent of having been " -"made by running the Program). Whether that is true depends on what the " -"Program does." -msgstr "" - -msgid "Section 1" -msgstr "Section 1" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "Section 2" -msgstr "Section 2" - -msgid "" -"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:" -msgstr "" -"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:" - -msgid "" -"You must cause the modified files to carry prominent notices stating that " -"you changed the files and the date of any change." -msgstr "" -"You must cause the modified files to carry prominent notices stating that " -"you changed the files and the date of any change." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "Exception" -msgstr "Exception" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "Section 3" -msgstr "Section 3" - -msgid "" -"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:" -msgstr "" -"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:" - -msgid "" -"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," -msgstr "" -"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," - -msgid "" -"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," -msgstr "" -"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," - -msgid "" -"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.)" -msgstr "" -"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.)" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "Section 4" -msgstr "Section 4" - -msgid "" -"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." -msgstr "" -"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." - -msgid "Section 5" -msgstr "Section 5" - -msgid "" -"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." -msgstr "" -"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." - -msgid "Section 6" -msgstr "Section 6" - -msgid "" -"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." -msgstr "" -"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." - -msgid "Section 7" -msgstr "Section 7" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"This section is intended to make thoroughly clear what is believed to be a " -"consequence of the rest of this License." -msgstr "" -"This section is intended to make thoroughly clear what is believed to be a " -"consequence of the rest of this License." - -msgid "Section 8" -msgstr "Section 8" - -msgid "" -"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." -msgstr "" -"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." - -msgid "Section 9" -msgstr "Section 9" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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." -msgstr "" -"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." - -msgid "Section 10" -msgstr "Section 10" - -msgid "" -"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." -msgstr "" -"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." - -msgid "NO WARRANTY" -msgstr "NO WARRANTY" - -msgid "Section 11" -msgstr "Section 11" - -msgid "" -"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." -msgstr "" -"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." - -msgid "Section 12" -msgstr "Section 12" - -msgid "" -"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." -msgstr "" -"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." - -msgid "End of Terms and Conditions." -msgstr "End of Terms and Conditions." - -msgid "How to Apply These Terms to Your New Programs" -msgstr "How to Apply These Terms to Your New Programs" - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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 <quote>" -"copyright</quote> line and a pointer to where the full notice is found." -msgstr "" -"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 <quote>" -"copyright</quote> line and a pointer to where the full notice is found." - -#, no-wrap -msgid "" -"<one line to give the program's name and a brief idea of what it does.>\n" -"Copyright (C) 19yy <name of author>\n" -"\n" -"This program is free software; you can redistribute it and/or modify\n" -"it under the terms of the GNU General Public License as published by\n" -"the Free Software Foundation; either version 2 of the License, or\n" -"(at your option) any later version.\n" -"\n" -"This program is distributed in the hope that it will be useful,\n" -"but WITHOUT ANY WARRANTY; without even the implied warranty of\n" -"MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n" -"GNU General Public License for more details.\n" -"\n" -"You should have received a copy of the GNU General Public License\n" -"along with this program; if not, write to the Free Software\n" -"Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA." -msgstr "" -"<one line to give the program's name and a brief idea of what it does.>\n" -"Copyright (C) 19yy <name of author>\n" -"\n" -"This program is free software; you can redistribute it and/or modify\n" -"it under the terms of the GNU General Public License as published by\n" -"the Free Software Foundation; either version 2 of the License, or\n" -"(at your option) any later version.\n" -"\n" -"This program is distributed in the hope that it will be useful,\n" -"but WITHOUT ANY WARRANTY; without even the implied warranty of\n" -"MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n" -"GNU General Public License for more details.\n" -"\n" -"You should have received a copy of the GNU General Public License\n" -"along with this program; if not, write to the Free Software\n" -"Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA." - -msgid "" -"Also add information on how to contact you by electronic and paper mail." -msgstr "" -"Also add information on how to contact you by electronic and paper mail." - -msgid "" -"If the program is interactive, make it output a short notice like this when " -"it starts in an interactive mode:" -msgstr "" -"If the program is interactive, make it output a short notice like this when " -"it starts in an interactive mode:" - -#, no-wrap -msgid "" -"Gnomovision version 69, Copyright (C) 19yy name of author\n" -"Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n" -"This is free software, and you are welcome to redistribute it\n" -"under certain conditions; type `show c' for details." -msgstr "" -"Gnomovision version 69, Copyright (C) 19yy name of author\n" -"Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n" -"This is free software, and you are welcome to redistribute it\n" -"under certain conditions; type `show c' for details." - -msgid "" -"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." -msgstr "" -"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." - -msgid "" -"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:" -msgstr "" -"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:" - -#, no-wrap -msgid "" -"Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n" -"`Gnomovision' (which makes passes at compilers) written by James Hacker.\n" -"\n" -"<signature of Ty Coon>, 1 April 1989\n" -"Ty Coon, President of Vice" -msgstr "" -"Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n" -"`Gnomovision' (which makes passes at compilers) written by James Hacker.\n" -"\n" -"<signature of Ty Coon>, 1 April 1989\n" -"Ty Coon, President of Vice" - -msgid "" -"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." -msgstr "" -"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." - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" - -#~ msgid "" -#~ " <" -#~ "sect2 id=\"licenses-gpl-1-9\" xreflabel=\"Section 9\">" -#~ msgstr "" -#~ " <" -#~ "sect2 id=\"licenses-gpl-1-9\" xreflabel=\"Section 9\">" diff --git a/Licenses/Locales/es_ES/gfdl.asciidoc.po b/Licenses/Locales/es_ES/gfdl.asciidoc.po deleted file mode 100644 index ada2c1b..0000000 --- a/Licenses/Locales/es_ES/gfdl.asciidoc.po +++ /dev/null @@ -1,586 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: gfdl.asciidoc 0.6\n" -"POT-Creation-Date: 2013-11-13 13:44-0500\n" -"PO-Revision-Date: 2013-11-13 13:44-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: Spanish\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "GNU Free Documentation License" -msgstr "Licencia de Documentación Libre de GNU" - -msgid "November 2002" -msgstr "Noviembre 2002" - -msgid "Free" -msgstr "" - -msgid "Software" -msgstr "" - -msgid "Foundation" -msgstr "" - -msgid "http://www.fsf.org/" -msgstr "" - -msgid "FSF" -msgstr "" - -msgid "1.2" -msgstr "" - -msgid "" -"Copyright © 2000, 2001, 2002 Free Software Foundation, Inc. 675 Mass Ave, " -"Cambridge, MA 02139, USA" -msgstr "" - -msgid "" -"Everyone is permitted to copy and distribute verbatim copies of this license " -"document, but changing it is not allowed." -msgstr "" -"Todos están permitidos de copiar y distribuir copias exactas de este " -"documento, pero modificarlo no está permitido." - -msgid "Preamble" -msgstr "Preámbulo" - -msgid "" -"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." -msgstr "" -"El propósito de esta Licencia es permitir que un manual, libro de " -"texto, u otro documento escrito sea «libre» en el sentido de libertad: " -"asegurar a todo el mundo la libertad efectiva de copiarlo y " -"redistribuirlo, con o sin modificaciones, de manera comercial o no. En " -"segundo término, esta Licencia proporciona al autor y al editor una " -"manera de obtener reconocimiento por su trabajo, sin que se le " -"considere responsable de las modificaciones realizadas por otros. " - -msgid "" -"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 " -"GNU General Public License, which is a copyleft license designed for free " -"software." -msgstr "" -"Esta Licencia es de tipo «copyleft», lo que significa que los trabajos " -"derivados del documento deben a su vez ser libres en el mismo sentido. " -"Complementa la Licencia Pública General de GNU, que es una licencia " -"tipo copyleft diseñada para el software libre. " - -msgid "" -"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." -msgstr "" -"Hemos diseñado esta Licencia para usarla en manuales de software " -"libre, ya que el software libre necesita documentación libre: Un " -"programa libre debe venir con los manuales que ofrezcan la mismas " -"libertades que da el software. Pero esta licencia no se limita a " -"manuales de software; puede ser usada para cualquier trabajo textual, " -"sin tener en cuenta su temática o si se publica como libro impreso. " -"Recomendamos esta licencia principalmente para trabajos cuyo fin sea " -"instructivo o de referencia." - -msgid "Applicability and definitions" -msgstr "Aplicación y definiciones" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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 “<< transparent>>” is called " -"“Opaque”." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "Verbatim copying" -msgstr "" - -msgid "" -"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 ." -msgstr "" - -msgid "" -"You may also lend copies, under the same conditions stated above, and you " -"may publicly display copies." -msgstr "" - -msgid "Copying in quantity" -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "Modifications" -msgstr "" - -msgid "" -"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 :" -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"State on the the name of the publisher of the " -", as the publisher." -msgstr "" - -msgid "Preserve all the copyright notices of the Document." -msgstr "" - -msgid "" -"Add an appropriate copyright notice for your modifications adjacent to the " -"other copyright notices." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"Preserve in that license notice the full lists of and required given in the " -"Document's license notice." -msgstr "" - -msgid "Include an unaltered copy of this License." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"Delete any section Entitled “Endorsements”. Such a section may not be " -"included in the ." -msgstr "" - -msgid "" -"Do not retitle any existing section to be Entitled “Endorsements” or to " -"conflict in title with any ." -msgstr "" - -msgid "Preserve any Warranty Disclaimers." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"You may add a section Entitled “Endorsements”, provided it contains nothing " -"but endorsements of your by various " -"parties&ndash;for example, statements of peer review or that the text " -"has been approved by an organization as the authoritative definition of a " -"standard." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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 ." -msgstr "" - -msgid "Combining documents" -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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”." -msgstr "" - -msgid "Collection of documents" -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "Aggregation with independent works" -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "Translations" -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "Termination" -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "Future Revisions of this License" -msgstr "" - -msgid "" -"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 http://www.gnu.org/copyleft/." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "How to use this License for your documents" -msgstr "" - -msgid "" -"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:" -msgstr "" - -#, no-wrap -msgid "" -"Copyright (C) YEAR YOUR NAME.\n" -"\n" -"Permission is granted to copy, distribute and/or modify this\n" -"document under the terms of the GNU Free Documentation License,\n" -"Version 1.2 or any later version published by the Free Software\n" -"Foundation; with no Invariant Sections, no Front-Cover Texts, and\n" -"no Back-Cover Texts. A copy of the license is included in the\n" -"section entitled ``GNU Free Documentation License''." -msgstr "" - -msgid "" -"If you have , Front-Cover Texts and " -"Back-Cover Texts, replace the “with…Texts”. line with this:" -msgstr "" - -#, no-wrap -msgid "" -"with the Invariant Sections being LIST THEIR TITLES, with the\n" -"Front-Cover Texts being LIST, and with the Back-Cover Texts being\n" -"LIST." -msgstr "" - -msgid "" -"If you have without , or some other combination of the three, merge those two " -"alternatives to suit the situation." -msgstr "" - -msgid "" -"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." -msgstr "" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "" diff --git a/Licenses/Locales/es_ES/gpl.asciidoc.po b/Licenses/Locales/es_ES/gpl.asciidoc.po deleted file mode 100644 index 686864e..0000000 --- a/Licenses/Locales/es_ES/gpl.asciidoc.po +++ /dev/null @@ -1,755 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: gpl.asciidoc 0.6\n" -"POT-Creation-Date: 2013-11-13 13:44-0500\n" -"PO-Revision-Date: 2013-11-13 13:44-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: Spanish\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "GNU General Public License" -msgstr "Licencia Pública General de GNU" - -msgid "June 1991" -msgstr "Junio 1991" - -msgid "Free" -msgstr "" - -msgid "Software" -msgstr "" - -msgid "Foundation" -msgstr "" - -msgid "FSF" -msgstr "" - -msgid "2" -msgstr "" - -msgid "" -"Copyright © 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, " -"Cambridge, MA 02139, USA" -msgstr "" - -msgid "" -"Everyone is permitted to copy and distribute verbatim copies of this license " -"document, but changing it is not allowed." -msgstr "" -"Todos están permitidos de copiar y distribuir copias exactas de este " -"documento, pero modificarlo no está permitido." - -msgid "Preamble" -msgstr "Preámbulo" - -msgid "" -"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." -msgstr "" -"Las licencias que cubren la mayor parte del software están diseñadas para " -"quitarle a usted la libertad de compartirlo y modificarlo. Por el contrario, " -"la Licencia Pública General de GNU pretende garantizarle la libertad de " -"compartir y modificar software libre, para asegurar que el software es libre " -"para todos sus usuarios. Esta Licencia Pública General se aplica a la mayor " -"parte del software del la Free Software Foundation y a cualquier otro " -"programa si sus autores se comprometen a utilizarla. (Existe otro software " -"de la Free Software Foundation que está cubierto por la Licencia Pública " -"General de GNU para Bibliotecas). Si quiere, también puede aplicarla a sus " -"propios programas." - -msgid "" -"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." -msgstr "" -"Cuando hablamos de software libre, estamos refiriéndonos a libertad, no a " -"precio. Nuestras Licencias Públicas Generales están diseñadas para " -"asegurarnos de que tenga la libertad de distribuir copias de software libre " -"(y cobrar por ese servicio si quiere), de que reciba el código fuente o que " -"pueda conseguirlo si lo quiere, de que pueda modificar el software o usar " -"fragmentos de él en programas nuevos libres, y de que sepa que puede hacer " -"todas estas cosas. " - -msgid "" -"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." -msgstr "" -"Para proteger sus derechos necesitamos algunas restricciones que prohíban a " -"cualquiera negarle a usted estos derechos o pedirle que renuncie a ellos. " -"Estas restricciones se traducen en ciertas obligaciones que le afectan si " -"distribuye copias del software, o si lo modifica. " - -msgid "" -"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." -msgstr "" -"Por ejemplo, si distribuye copias de uno de estos programas, sea " -"gratuitamente, o a cambio de una contraprestación, debe dar a los receptores " -"todos los derechos que tiene. Debe asegurarse de que ellos también reciben, " -"o pueden conseguir, el código fuente. Y debe mostrarles estas condiciones de " -"forma que conozcan sus derechos. " - -msgid "We protect your rights with two steps:" -msgstr "Protegemos sus derechos con la combinación de dos medidas:" - -msgid "copyright the software, and" -msgstr "Derechos de copia del software (copyright), y " - -msgid "" -"offer you this license which gives you legal permission to copy, distribute " -"and/or modify the software." -msgstr "" -"Le ofrecemos esta licencia, que le da permiso legal para copiar, distribuir " -"y/o modificar el software. " - -msgid "" -"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." -msgstr "" -"También, para la protección de cada autor y la nuestra propia, queremos " -"asegurarnos de que todo el mundo comprende que no se proporciona ninguna " -"garantía para este software libre. Si el software se modifica por cualquiera " -"y éste a su vez lo distribuye, queremos que sus receptores sepan que lo que " -"tienen no es el original, de forma que cualquier problema introducido por " -"otros no afecte a la reputación de los autores originales. " - -msgid "" -"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." -msgstr "" -"Finalmente, cualquier programa libre está constantemente amenazado por " -"patentes sobre el software. Queremos evitar el peligro de que los " -"redistribuidores de un programa libre obtengan patentes por su cuenta, " -"convirtiendo de facto el programa en propietario. Para evitar esto, hemos " -"dejado claro que cualquier patente debe ser pedida para el uso libre de " -"cualquiera, o no ser pedida. " - -msgid "" -"The precise terms and conditions for copying, distribution and modification " -"follow." -msgstr "" -"Los términos precisos y las condiciones para la copia, distribución y " -"modificación se exponen a continuación. " - -msgid "Terms and Conditions for Copying, Distribution and Modification" -msgstr "Términos y condiciones para la copia, distribución y modificación" - -msgid "Section 0" -msgstr "Sección 0" - -msgid "" -"This License applies to any program or other work which contains a notice " -"placed by the copyright holder saying it may be distributed under the terms " -"of this General Public License. The “Program”, below, refers to any such " -"program or work, and a “work based on the Program” means either the Program " -"or any derivative work under copyright law: that is to say, a work " -"containing the Program or a portion of it, either verbatim or with " -"modifications and/or translated into another language. (Hereinafter, " -"translation is included without limitation in the term “modification”.) Each " -"licensee is addressed as “you”." -msgstr "" -"Esta Licencia se aplica a cualquier programa u otro tipo de obra que " -"contenga una notificación colocada por el propietario del copyright diciendo " -"que puede distribuirse bajo los términos de esta Licencia Pública General. " -"El «Programa», en adelante, se referirá a cualquier programa u obra, y «obra " -"basada en el Programa» se referirá bien al Programa o a cualquier trabajo " -"derivado de él según la ley de derechos de autor (copyright): Esto es, una " -"obra o trabajo que contenga el programa o una porción de él, bien en forma " -"literal o con modificaciones y/o traducido en otro lenguaje. Aquí y después, " -"la traducción está incluida sin limitación en el término «modificación». Cada " -"concesionario (licenciatario) será denominado «usted». " - -msgid "" -"Activities other than copying, distribution and modification are not covered " -"by this License; they are outside its scope. The act of running the Program " -"is not restricted, and the output from the Program is covered only if its " -"contents constitute a work based on the Program (independent of having been " -"made by running the Program). Whether that is true depends on what the " -"Program does." -msgstr "" -"Cualquier otra actividad que no sea la copia, distribución o modificación no " -"está cubierta por esta Licencia, está fuera de su ámbito. El acto de " -"ejecutar el Programa no está restringido, y los resultados del Programa " -"están cubiertos únicamente si sus contenidos constituyen un trabajo basado " -"en el Programa, independientemente de haberlo producido mediante la " -"ejecución del programa. El que esto se cumpla, depende de lo que haga el " -"programa. " - -msgid "Section 1" -msgstr "Sección 1" - -msgid "" -"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." -msgstr "" -"Usted puede copiar y distribuir copias literales del código fuente del " -"Programa, según lo has recibido, en cualquier medio, supuesto que de forma " -"adecuada y bien visible publique en cada copia un anuncio de copyright " -"adecuado y un repudio de garantía, mantenga intactos todos los anuncios que " -"se refieran a esta Licencia y a la ausencia de garantía, y proporcione a " -"cualquier otro receptor del programa una copia de esta Licencia junto con " -"el Programa. " - -msgid "" -"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." -msgstr "" -"Puede cobrar un precio por el acto físico de transferir una copia, y puede, " -"según su libre albedrío, ofrecer garantía a cambio de unos honorarios. " - -msgid "Section 2" -msgstr "Sección 2" - -msgid "" -"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:" -msgstr "" -"Puede modificar su copia o copias del Programa o de cualquier porción de él, " -"formando de esta manera un trabajo basado en el Programa, y copiar y " -"distribuir esa modificación o trabajo bajo los términos de la anterior, probado que además usted cumpla con todas " -"las siguientes condiciones: " - -msgid "" -"You must cause the modified files to carry prominent notices stating that " -"you changed the files and the date of any change." -msgstr "" -"Debe hacer que los ficheros modificados lleven anuncios prominentes " -"indicando que los ha cambiado y la fecha de cualquier cambio." - -msgid "" -"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." -msgstr "" -"Debe hacer que cualquier trabajo que distribuya o publique y que en todo o " -"en parte contenga o sea derivado del Programa o de cualquier parte de él sea " -"licenciada como un todo, sin carga alguna, a todas las terceras partes y " -"bajo los términos de esta Licencia. " - -msgid "" -"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." -msgstr "" - -msgid "Exception" -msgstr "Excepción" - -msgid "" -"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." -msgstr "" -"Si el propio Programa es interactivo pero normalmente no muestra ese " -"anuncio, no se requiere que su trabajo basado en el Programa muestre ningún " -"anuncio. " - -msgid "" -"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." -msgstr "" -"Estos requisitos se aplican al trabajo modificado como un todo. Si partes " -"identificables de ese trabajo no son derivadas del Programa, y pueden, " -"razonablemente, ser consideradas trabajos independientes y separados por " -"ellos mismos, entonces esta Licencia y sus términos no se aplican a esas " -"partes cuando sean distribuidas como trabajos separados. Pero cuando " -"distribuya esas mismas secciones como partes de un todo que es un trabajo " -"basado en el Programa, la distribución del todo debe ser según los términos " -"de esta licencia, cuyos permisos para otros licenciatarios se extienden al " -"todo completo, y por lo tanto a todas y cada una de sus partes, con " -"independencia de quién la escribió. " - -msgid "" -"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." -msgstr "" -"Por lo tanto, no es la intención de este apartado reclamar derechos o " -"desafiar sus derechos sobre trabajos escritos totalmente por usted mismo. El " -"intento es ejercer el derecho a controlar la distribución de trabajos " -"derivados o colectivos basados en el Programa. " - -msgid "" -"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." -msgstr "" -"Además, el simple hecho de reunir un trabajo no basado en el Programa con el " -"Programa (o con un trabajo basado en el Programa) en un volumen de " -"almacenamiento o en un medio de distribución no hace que dicho trabajo entre " -"dentro del ámbito cubierto por esta Licencia. " - -msgid "Section 3" -msgstr "Sección 3" - -msgid "" -"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:" -msgstr "" -"Puede copiar y distribuir el Programa (o un trabajo basado en él, según se " -"especifica en la Sección 2, como código objeto o en formato ejecutable según " -"los términos de las y anteriores, supuesto que además cumpla una de las " -"siguientes condiciones: " - -msgid "" -"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," -msgstr "" -"Acompañarlo con el código fuente leíble completo correspondiente, leíble por " -"máquinas, que debe ser distribuido según los términos de las y mencionadas " -"antes en un medio habitualmente utilizado para el intercambio de software, " -"o, " - -msgid "" -"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," -msgstr "" -"Acompañarlo con una oferta por escrito, válida durante al menos tres años, " -"de proporcionar a cualquier tercera parte una copia completa en formato " -"electrónico del código fuente correspondiente, a un coste no mayor que el de " -"realizar físicamente la distribución del fuente, que será distribuido bajo " -"las condiciones descritas en los apartados 1 y 2 anteriores, en un medio " -"habitualmente utilizado para el intercambio de programas, o " - -msgid "" -"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.)" -msgstr "" -"Acompañarlo con la información que recibiste ofreciendo distribuir el código " -"fuente correspondiente. (Esta opción se permite sólo para distribución no " -"comercial y sólo si usted recibió el programa como código objeto o en " -"formato ejecutable con tal oferta, de acuerdo con la Subsección b anterior). " - -msgid "" -"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." -msgstr "" -"Por código fuente de un trabajo se entiende la forma preferida del trabajo " -"cuando se le hacen modificaciones. Para un trabajo ejecutable, se entiende " -"por código fuente completo todo el código fuente para todos los módulos que " -"contiene, más cualquier fichero asociado de definición de interfaces, más " -"los guiones utilizados para controlar la compilación e instalación del " -"ejecutable. Como excepción especial el código fuente distribuido no necesita " -"incluir nada que sea distribuido normalmente (bien como fuente, bien en " -"forma binaria) con los componentes principales (compilador, núcleo y " -"similares) del sistema operativo en el cual funciona el ejecutable, a no ser " -"que el propio componente acompañe al ejecutable. " - -msgid "" -"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." -msgstr "" -"Si la distribución del ejecutable o del código objeto se hace mediante la " -"oferta acceso para copiarlo de un cierto lugar, entonces se considera la " -"oferta de acceso para copiar el código fuente del mismo lugar como " -"distribución del código fuente, incluso aunque terceras partes no estén " -"forzadas a copiar el fuente junto con el código objeto." - -msgid "Section 4" -msgstr "Sección 4" - -msgid "" -"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." -msgstr "" -"No puede copiar, modificar, sublicenciar o distribuir el Programa excepto " -"como prevé expresamente esta Licencia. Cualquier intento de copiar, " -"modificar sublicenciar o distribuir el Programa de otra forma es inválida, y " -"hará que cesen automáticamente los derechos que te proporciona esta " -"Licencia. En cualquier caso, las partes que hayan recibido copias o derechos " -"de usted bajo esta Licencia no cesarán en sus derechos mientras esas partes " -"continúen cumpliéndola." - -msgid "Section 5" -msgstr "Sección 5" - -msgid "" -"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." -msgstr "" -"No está obligado a aceptar esta licencia, ya que no la ha firmado. Sin " -"embargo, no hay hada más que le proporcione permiso para modificar o " -"distribuir el Programa o sus trabajos derivados. Estas acciones están " -"prohibidas por la ley si no acepta esta Licencia. Por lo tanto, si modifica " -"o distribuye el Programa (o cualquier trabajo basado en el Programa), está " -"indicando que acepta esta Licencia para poder hacerlo, y todos sus términos " -"y condiciones para copiar, distribuir o modificar el Programa o trabajos " -"basados en él." - -msgid "Section 6" -msgstr "Sección 6" - -msgid "" -"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." -msgstr "" -"Cada vez que redistribuya el Programa (o cualquier trabajo basado en el " -"Programa), el receptor recibe automáticamente una licencia del " -"licenciatario original para copiar, distribuir o modificar el Programa, de " -"forma sujeta a estos términos y condiciones. No puede imponer al receptor " -"ninguna restricción más sobre el ejercicio de los derechos aquí " -"garantizados. No es usted responsable de hacer cumplir esta licencia por " -"terceras partes." - -msgid "Section 7" -msgstr "Sección 7" - -msgid "" -"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." -msgstr "" -"Si como consecuencia de una resolución judicial o de una alegación de " -"infracción de patente o por cualquier otra razón (no limitada a asuntos " -"relacionados con patentes) se le imponen condiciones (ya sea por mandato " -"judicial, por acuerdo o por cualquier otra causa) que contradigan las " -"condiciones de esta Licencia, ello no le exime de cumplir las condiciones de " -"esta Licencia. Si no puede realizar distribuciones de forma que se " -"satisfagan simultáneamente sus obligaciones bajo esta licencia y cualquier " -"otra obligación pertinente entonces, como consecuencia, no puede distribuir " -"el Programa de ninguna forma. Por ejemplo, si una patente no permite la " -"redistribución libre de derechos de autor del Programa por parte de todos " -"aquellos que reciban copias directa o indirectamente a través de usted, " -"entonces la única forma en que podría satisfacer tanto esa condición como " -"esta Licencia sería evitar completamente la distribución del Programa. " - -msgid "" -"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." -msgstr "" -"Si cualquier porción de este apartado se considera inválida o imposible de " -"cumplir bajo cualquier circunstancia particular ha de cumplirse el resto y " -"la sección por entero ha de cumplirse en cualquier otra circunstancia. " - -msgid "" -"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." -msgstr "" -"No es el propósito de este apartado inducirle a infringir ninguna " -"reivindicación de patente ni de ningún otro derecho de propiedad o impugnar " -"la validez de ninguna de dichas reivindicaciones. Este apartado tiene el " -"único propósito de proteger la integridad del sistema de distribución de " -"software libre, que se realiza mediante prácticas de licencia pública. Mucha " -"gente ha hecho contribuciones generosas a la gran variedad de software " -"distribuido mediante ese sistema con la confianza de que el sistema se " -"aplicará consistentemente. Será el autor/donante quien decida si quiere " -"distribuir software mediante cualquier otro sistema y una licencia no puede " -"imponer esa elección. " - -msgid "" -"This section is intended to make thoroughly clear what is believed to be a " -"consequence of the rest of this License." -msgstr "" -"Este apartado pretende dejar completamente claro lo que se cree que es una " -"consecuencia del resto de esta Licencia. " - -msgid "Section 8" -msgstr "Sección 8" - -msgid "" -"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." -msgstr "" -"Si la distribución y/o uso de el Programa está restringida en ciertos " -"países, bien por patentes o por interfaces bajo copyright, el tenedor del " -"copyright que coloca este Programa bajo esta Licencia puede añadir una " -"limitación explícita de distribución geográfica excluyendo esos países, de " -"forma que la distribución se permita sólo en o entre los países no excluidos " -"de esta manera. En ese caso, esta Licencia incorporará la limitación como si " -"estuviese escrita en el cuerpo de esta Licencia." - -msgid "Section 9" -msgstr "Sección 9" - -msgid "" -"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." -msgstr "" -"La Free Software Foundation puede publicar versiones revisadas y/o nuevas de " -"la Licencia Pública General de tiempo en tiempo. Dichas nuevas versiones " -"serán similares en espíritu a la presente versión, pero pueden ser " -"diferentes en detalles para considerar nuevos problemas o situaciones. " - -msgid "" -"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." -msgstr "" -"Cada versión recibe un número de versión que la distingue de otras. Si el " -"Programa especifica un número de versión de esta Licencia que se aplica " -"aplica a éste y a «cualquier versión posterior», usted tiene la opción de " -"seguir los términos y condiciones, bien de esa versión, bien de cualquier " -"versión posterior publicada por la Free Software Foundation. Si el Programa " -"no especifica un número de versión de esta Licencia, usted puede escoger " -"cualquier versión publicada por la Free Software Foundation. " - -msgid "Section 10" -msgstr "Sección 10" - -msgid "" -"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." -msgstr "" -"Si quiere incorporar partes del Programa en otros programas libres cuyas " -"condiciones de distribución son diferentes, escribe al autor para pedirle " -"permiso. Si el software tiene copyright de la Free Software Foundation, " -"escribe a la Free Software Foundation: algunas veces hacemos excepciones en " -"estos casos. Nuestra decisión estará guiada por el doble objetivo de de " -"preservar la libertad de todos los derivados de nuestro software libre y " -"promover el que se comparta y reutilice el software en general." - -msgid "NO WARRANTY" -msgstr "AUSENCIA GARANTÍA" - -msgid "Section 11" -msgstr "Sección 11" - -msgid "" -"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." -msgstr "" -"DEBIDO A QUE EL PROGRAMA SE LICENCIA LIBRE DE CARGAS, NO SE OFRECE NINGUNA " -"GARANTÍA SOBRE EL PROGRAMA, EN TODA LA EXTENSIÓN PERMITIDA POR LA " -"LEGISLACIÓN APLICABLE. EXCEPTO CUANDO SE INDIQUE DE OTRA FORMA POR ESCRITO, " -"LOS PROPIETARIOS DEL COPYRIGHT Y/U OTRAS PARTES PROPORCIONAN EL PROGRAMA «TAL " -"CUAL», SIN GARANTÍA DE NINGUNA CLASE, BIEN EXPRESA O IMPLÍCITA, CON " -"INCLUSIÓN, PERO SIN LIMITACIÓN A LAS GARANTÍAS MERCANTILES IMPLÍCITAS O A LA " -"CONVENIENCIA PARA UN PROPÓSITO PARTICULAR. CUALQUIER RIESGO REFERENTE A LA " -"CALIDAD Y PRESTACIONES DEL PROGRAMA ES ASUMIDO POR USTED. SI SE PROBASE QUE " -"EL PROGRAMA ES DEFECTUOSO, USTED ASUME EL COSTE DE CUALQUIER SERVICIO, " -"REPARACIÓN O CORRECCIÓN NECESARIO." - -msgid "Section 12" -msgstr "Sección 12" - -msgid "" -"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." -msgstr "" -"EN NINGÚN CASO, SALVO QUE LO REQUIERA LA LEGISLACIÓN APLICABLE O HAYA SIDO " -"ACORDADO POR ESCRITO, NINGÚN TENEDOR DEL COPYRIGHT NI NINGUNA OTRA PARTE QUE " -"MODIFIQUE Y/O REDISTRIBUYA EL PROGRAMA SEGÚN SE PERMITE EN ESTA LICENCIA " -"SERÁ RESPONSABLE ANTE USTED POR DAÑOS, INCLUYENDO CUALQUIER DAÑO GENERAL, " -"ESPECIAL, INCIDENTAL O RESULTANTE PRODUCIDO POR EL USO O LA IMPOSIBILIDAD DE " -"USO DEL PROGRAMA (CON INCLUSIÓN, PERO SIN LIMITACIÓN A LA PÉRDIDA DE DATOS O " -"A LA GENERACIÓN INCORRECTA DE DATOS O A PÉRDIDAS SUFRIDAS POR USTED O POR " -"TERCERAS PARTES O A UN FALLO DEL PROGRAMA AL FUNCIONAR EN COMBINACIÓN CON " -"CUALQUIER OTRO PROGRAMA), INCLUSO SI DICHO TENEDOR U OTRA PARTE HA SIDO " -"ADVERTIDO DE LA POSIBILIDAD DE DICHOS DAÑOS. " - -msgid "End of Terms and Conditions." -msgstr "Fin de los términos y condiciones" - -msgid "How to Apply These Terms to Your New Programs" -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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 <quote>" -"copyright</quote> line and a pointer to where the full notice is found." -msgstr "" - -#, no-wrap -msgid "" -"<one line to give the program's name and a brief idea of what it does.>\n" -"Copyright (C) 19yy <name of author>\n" -"\n" -"This program is free software; you can redistribute it and/or modify\n" -"it under the terms of the GNU General Public License as published by\n" -"the Free Software Foundation; either version 2 of the License, or\n" -"(at your option) any later version.\n" -"\n" -"This program is distributed in the hope that it will be useful,\n" -"but WITHOUT ANY WARRANTY; without even the implied warranty of\n" -"MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n" -"GNU General Public License for more details.\n" -"\n" -"You should have received a copy of the GNU General Public License\n" -"along with this program; if not, write to the Free Software\n" -"Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA." -msgstr "" - -msgid "" -"Also add information on how to contact you by electronic and paper mail." -msgstr "" - -msgid "" -"If the program is interactive, make it output a short notice like this when " -"it starts in an interactive mode:" -msgstr "" - -#, no-wrap -msgid "" -"Gnomovision version 69, Copyright (C) 19yy name of author\n" -"Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n" -"This is free software, and you are welcome to redistribute it\n" -"under certain conditions; type `show c' for details." -msgstr "" - -msgid "" -"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." -msgstr "" - -msgid "" -"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:" -msgstr "" - -#, no-wrap -msgid "" -"Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n" -"`Gnomovision' (which makes passes at compilers) written by James Hacker.\n" -"\n" -"<signature of Ty Coon>, 1 April 1989\n" -"Ty Coon, President of Vice" -msgstr "" - -msgid "" -"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." -msgstr "" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "" diff --git a/Licenses/gfdl.asciidoc b/Licenses/gfdl.asciidoc deleted file mode 100644 index 815a86c..0000000 --- a/Licenses/gfdl.asciidoc +++ /dev/null @@ -1,457 +0,0 @@ -= GNU Free Documentation License -Free Software Foundation -Version 1.2, November 2002 - -Copyright (C) 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. - -[[licenses-gfdl-section-1]] -== 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 GNU General Public License, 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. - -[[licenses-gfdl-section-2]] - -== 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. - -anchor:modified-version[Modified Version] - -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. - -anchor:secondary-section[Secondary Section] - -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. - -anchor:invariant-sections[Invariant Sections] - -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. - -anchor:cover-texts[Cover Texts] - -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. - -anchor:transparent[Transparent] - -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 ``<< -transparent>>'' 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. - -anchor:title-page[Title Page] - -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. - -[[licenses-gfdl-section-3]] - -== 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. - -[[licenses-gfdl-section-4]] - -== 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. - -[[licenses-gfdl-section-5]] - -== 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 -<>: - -a. 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. - -b. 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. - -c. State on the <> the name of the publisher of the -<>, as the publisher. - -d. Preserve all the copyright notices of the Document. - -e. Add an appropriate copyright notice for your modifications adjacent -to the other copyright notices. - -f. 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. - -g. Preserve in that license notice the full lists of -<> and required <> given in the -Document's license notice. - -h. Include an unaltered copy of this License. - -i. 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. - -j. 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. - -k. 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. - -l. 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. - -m. Delete any section Entitled ``Endorsements''. Such a section may -not be included in the <>. - -n. Do not retitle any existing section to be Entitled ``Endorsements'' -or to conflict in title with any <>. - -o. 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 <>. - -[[licenses-gfdl-section-6]] - -== 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''. - -[[licenses-gfdl-section-7]] - -== 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. - -[[licenses-gfdl-section-8]] - -== 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. - -[[licenses-gfdl-section-9]] - -== 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. - -[[licenses-gfdl-section-10]] - -== 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. - -[[licenses-gfdl-section-11]] - -== 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 -http://www.gnu.org/copyleft/[http://www.gnu.org/copyleft/]. - -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. - -[[licenses-gfdl-section-12]] - -== Appendix A. 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/Licenses/gpl.asciidoc b/Licenses/gpl.asciidoc deleted file mode 100644 index 19bc03f..0000000 --- a/Licenses/gpl.asciidoc +++ /dev/null @@ -1,426 +0,0 @@ -= GNU General Public License -Free Software Foundation -Version 2, June 1991 - -Copyright (C) 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. - -[[licenses-gpl-0]] - -== 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: - -1. copyright the software, and -2. 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. - -[[licenses-gpl-1]] - -== Terms and Conditions for Copying, Distribution and Modification - -[[licenses-gpl-1-0]] - -=== Section 0 - -This License applies to any program or other work which contains a -notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The ``Program'', -below, refers to any such program or work, and a ``work based on the -Program'' means either the Program or any derivative work under -copyright law: that is to say, a work containing the Program or a -portion of it, either verbatim or with modifications and/or translated -into another language. (Hereinafter, translation is included without -limitation in the term ``modification''.) Each licensee is addressed -as ``you''. - -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. - -[[licenses-gpl-1-1]] - -=== 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. - -[[licenses-gpl-1-2]] - -=== 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: - -a. You must cause the modified files to carry prominent notices -stating that you changed the files and the date of any change. - -b. 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. - -c. 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. - -[NOTE] -.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. - -[[licenses-gpl-1-3]] - -=== 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: - -a. 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, - -b. 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, - -c. 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. - -[[licenses-gpl-1-4]] - -=== 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. - -[[licenses-gpl-1-5]] - -=== 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. - -[[licenses-gpl-1-6]] - -=== 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. - -[[licenses-gpl-1-7]] - -=== 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. - -[[licenses-gpl-1-8]] - -=== 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. - -[[licenses-gpl-1-9]] - -=== 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. - -[[licenses-gpl-1-10]] - -=== 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. - -[[licenses-gpl-1-11]] - -=== 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. - -[[licenses-gpl-1-12]] - -=== 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._ - -[[licenses-gpl-2]] - -== Appendix A. 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. - ----------------------------------------------------------------------- - -Copyright (C) 19yy - -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. - -, 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/Licenses/render.conf b/Licenses/render.conf deleted file mode 100644 index a5d2d47..0000000 --- a/Licenses/render.conf +++ /dev/null @@ -1,15 +0,0 @@ -[gfdl.html] -render-type = "asciidoc" -render-flow = "article" -render-from = "gfdl.asciidoc" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/gfdl.asciidoc.po" -formats = "xhtml" -render-page = "single" - -[gpl.html] -render-type = "asciidoc" -render-flow = "article" -render-from = "gpl.asciidoc" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/gpl.asciidoc.po" -formats = "xhtml" -render-page = "single" diff --git a/Repository/Locales/en_US/repository-infra.svgz.po b/Repository/Locales/en_US/repository-infra.svgz.po deleted file mode 100644 index 8da01ef..0000000 --- a/Repository/Locales/en_US/repository-infra.svgz.po +++ /dev/null @@ -1,38 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: repository-infra.svgz 0.6\n" -"POT-Creation-Date: 2013-11-15 10:06-0500\n" -"PO-Revision-Date: 2013-11-15 10:06-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "image/svg+xml" -msgstr "image/svg+xml" - -#, no-wrap -msgid "INTERNET" -msgstr "INTERNET" - -#, no-wrap -msgid "SSL/TLS" -msgstr "SSL/TLS" - -#, no-wrap -msgid "WORKING COPY" -msgstr "WORKING COPY" - -#, no-wrap -msgid "CENTRAL " -msgstr "CENTRAL " - -#, no-wrap -msgid "REPOSITORY" -msgstr "REPOSITORY" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Repository/Locales/en_US/repository-version-schema.svgz.po b/Repository/Locales/en_US/repository-version-schema.svgz.po deleted file mode 100644 index b0df349..0000000 --- a/Repository/Locales/en_US/repository-version-schema.svgz.po +++ /dev/null @@ -1,157 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: repository-version-schema.svgz 0.6\n" -"POT-Creation-Date: 2013-11-15 10:06-0500\n" -"PO-Revision-Date: 2013-11-15 10:06-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -msgid "repository-version-schema.svgz" -msgstr "repository-version-schema.svgz" - -msgid "image/svg+xml" -msgstr "image/svg+xml" - -msgid "2013-11-13" -msgstr "2013-11-13" - -msgid "Alain Reguera Delgado" -msgstr "Alain Reguera Delgado" - -msgid "The CentOS Project" -msgstr "The CentOS Project" - -msgid "http://www.centos.org/" -msgstr "http://www.centos.org/" - -msgid "en_US" -msgstr "en_US" - -msgid "Identity" -msgstr "Identity" - -msgid "Models" -msgstr "Models" - -msgid "Manual" -msgstr "Manual" - -msgid "Scripts" -msgstr "Scripts" - -msgid "Bash" -msgstr "Bash" - -msgid "Functions" -msgstr "Functions" - -msgid "Path" -msgstr "Path" - -#, no-wrap -msgid "2.0" -msgstr "2.0" - -#, no-wrap -msgid "2.1" -msgstr "2.1" - -#, no-wrap -msgid "2.2" -msgstr "2.2" - -#, no-wrap -msgid "2.3" -msgstr "2.3" - -#, no-wrap -msgid "2.4" -msgstr "2.4" - -#, no-wrap -msgid "2.5" -msgstr "2.5" - -#, no-wrap -msgid "Development updates every month" -msgstr "Development updates every month" - -#, no-wrap -msgid "2.6" -msgstr "2.6" - -#, no-wrap -msgid "2" -msgstr "2" - -#, no-wrap -msgid "1.0" -msgstr "1.0" - -#, no-wrap -msgid "1.1" -msgstr "1.1" - -#, no-wrap -msgid "1.2" -msgstr "1.2" - -#, no-wrap -msgid "1.3" -msgstr "1.3" - -#, no-wrap -msgid "1.4" -msgstr "1.4" - -#, no-wrap -msgid "1.5" -msgstr "1.5" - -#, no-wrap -msgid "1.6" -msgstr "1.6" - -#, no-wrap -msgid "3" -msgstr "3" - -#, no-wrap -msgid "3.0" -msgstr "3.0" - -#, no-wrap -msgid "3.1" -msgstr "3.1" - -#, no-wrap -msgid "0.6" -msgstr "0.6" - -#, no-wrap -msgid "0.5" -msgstr "0.5" - -#, no-wrap -msgid "1" -msgstr "1" - -#, no-wrap -msgid "Release every 6 months" -msgstr "Release every 6 months" - -#, no-wrap -msgid "No maintainance updates" -msgstr "No maintainance updates" - -#, no-wrap -msgid "master" -msgstr "master" - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" diff --git a/Repository/Locales/en_US/repository.asciidoc.po b/Repository/Locales/en_US/repository.asciidoc.po deleted file mode 100644 index 7ab6841..0000000 --- a/Repository/Locales/en_US/repository.asciidoc.po +++ /dev/null @@ -1,192 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: repository.asciidoc 0.6\n" -"POT-Creation-Date: 2013-11-15 10:06-0500\n" -"PO-Revision-Date: 2013-11-15 10:06-0500\n" -"Last-Translator: Localization SIG \n" -"Language-Team: English\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#. When image changes, this message will be marked fuzzy or untranslated for you. -#. It doesn't matter what you translate it to: it's not used at all. -msgid "@@image: 'repository-infra.png'; md5=48f2ca34b510c9d776366cd19eb88e1a" -msgstr "" - -msgid "The CentOS Artwork Repository" -msgstr "The CentOS Artwork Repository" - -msgid "Nov 2013" -msgstr "Nov 2013" - -msgid "Alain" -msgstr "Alain" - -msgid "Reguera" -msgstr "Reguera" - -msgid "Delgado" -msgstr "Delgado" - -msgid "al@centos.org.cu" -msgstr "al@centos.org.cu" - -msgid "ARD" -msgstr "ARD" - -msgid "1.0" -msgstr "1.0" - -msgid "Mission" -msgstr "Mission" - -msgid "" -"The CentOS Artwork Repository exists to produce The CentOS Project corporate " -"visual identity." -msgstr "" -"The CentOS Artwork Repository exists to produce The CentOS Project corporate " -"visual identity." - -msgid "Infrastructure" -msgstr "Infrastructure" - -msgid "" -"The CentOS Artwork Repository is made of one “central repository” and many " -"“working copies” of that central repository. The working copies are " -"independent one another, can be distributed all around the world and provide " -"a local place for designers, documenters, translators and programmers to " -"perform their work in a decentralized way. The central repository, on the " -"other hand, provides a common place for all independent working copies to " -"exchange data in the community." -msgstr "" -"The CentOS Artwork Repository is made of one “central repository” and many " -"“working copies” of that central repository. The working copies are " -"independent one another, can be distributed all around the world and provide " -"a local place for designers, documenters, translators and programmers to " -"perform their work in a decentralized way. The central repository, on the " -"other hand, provides a common place for all independent working copies to " -"exchange data in the community." - -msgid "repository-infra.png" -msgstr "repository-infra.png" - -msgid "Subversion" -msgstr "Subversion" - -msgid "" -"The current infrastructure that holds &TCAR;, on the Internet, is made " -"of the following components:" -msgstr "" -"The current infrastructure that holds &TCAR;, on the Internet, is made " -"of the following components:" - -msgid "" -"Subversion — Modern " -"Version Control System designed to replace CVS." -msgstr "" -"Subversion — Modern " -"Version Control System designed to replace CVS." - -msgid "" -"Trac — Enhanced wiki and " -"issue tracking system." -msgstr "" -"Trac — Enhanced wiki and " -"issue tracking system." - -msgid "" -"Httpd+WebDav as data exchanging route between the workstations and the " -"central repository, through the Internet. Httpd was configured to provide " -"service through SSL, so all traffic between the workstations and the server " -"be protected while it travels across the Internet." -msgstr "" -"Httpd+WebDav as data exchanging route between the workstations and the " -"central repository, through the Internet. Httpd was configured to provide " -"service through SSL, so all traffic between the workstations and the server " -"be protected while it travels across the Internet." - -msgid "" -"The access rights are controlled by using a combination of both Subversion's " -"authorization files and Httpd's password files. These files can be managed " -"consistently through Trac's WebAdmin plug-in." -msgstr "" -"The access rights are controlled by using a combination of both Subversion's " -"authorization files and Httpd's password files. These files can be managed " -"consistently through Trac's WebAdmin plug-in." - -msgid "" -"In this infrastructure, the first level of directories in the repository " -"provides the Subversion's standard trunk-branches-tags layout. The second " -"level of directories provides organization for different work lines, as " -"described in <xref linkend=\"repo-convs-worklines\" />. All other " -"subsequent directory levels from second level on exist to organize specific " -"concepts related to the work line they belong to." -msgstr "" -"In this infrastructure, the first level of directories in the repository " -"provides the Subversion's standard trunk-branches-tags layout. The second " -"level of directories provides organization for different work lines, as " -"described in <xref linkend=\"repo-convs-worklines\" />. All other " -"subsequent directory levels from second level on exist to organize specific " -"concepts related to the work line they belong to." - -msgid "Git" -msgstr "Git" - -msgid "" -"In addition to current Subversion infrastructure, we are working on a Git " -"infrastructure with the intention of migrating the current Subversion " -"infrastructure up to it, progressively. The Git infrastructure we are " -"working on is made of the following components:" -msgstr "" -"In addition to current Subversion infrastructure, we are working on a Git " -"infrastructure with the intention of migrating the current Subversion " -"infrastructure up to it, progressively. The Git infrastructure we are " -"working on is made of the following components:" - -msgid "Git — Fast version control system." -msgstr "Git — Fast version control system." - -msgid "Gitolite — Highly flexible server for git directory version tracker." -msgstr "Gitolite — Highly flexible server for git directory version tracker." - -msgid "Gitweb — Simple web interface to git repositories." -msgstr "Gitweb — Simple web interface to git repositories." - -msgid "MantisBT — Web-based issue tracking system." -msgstr "MantisBT — Web-based issue tracking system." - -msgid "" -"The data exchanging route between the working copies and the central " -"repository takes place through SSH." -msgstr "" -"The data exchanging route between the working copies and the central " -"repository takes place through SSH." - -msgid "" -"The access rights are controlled by using a combination of SSH public keys " -"and Gitolite's repository configuration file." -msgstr "" -"The access rights are controlled by using a combination of SSH public keys " -"and Gitolite's repository configuration file." - -msgid "" -"In this infrastructure, the first level of directories in the repository " -"provides organization for different work lines, as described in <xref " -"linkend=\"repo-convs-worklines\" />. All other subsequent directory " -"levels from second level on exist to organize specific concepts related to " -"the work line they belong to." -msgstr "" -"In this infrastructure, the first level of directories in the repository " -"provides organization for different work lines, as described in <xref " -"linkend=\"repo-convs-worklines\" />. All other subsequent directory " -"levels from second level on exist to organize specific concepts related to " -"the work line they belong to." - -#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. -msgid "translator-credits" -msgstr "translator-credits" - -#~ msgid "@@image: 'repository-infra.png'; md5=THIS FILE DOESN'T EXIST" -#~ msgstr "@@image: 'repository-infra.png'; md5=THIS FILE DOESN'T EXIST" diff --git a/Repository/render.conf b/Repository/render.conf deleted file mode 100644 index ac7e48b..0000000 --- a/Repository/render.conf +++ /dev/null @@ -1,25 +0,0 @@ -[repository-infra.png] -render-type = "svg" -render-flow = "base" -render-from = "repository-infra.svgz" -export-id = "CENTOSARTWORK" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/repository-infra.svgz.po" -command = "/usr/bin/convert -colors 128" - -[repository-version-schema.png] -render-type = "svg" -render-flow = "base" -render-from = "repository-version-schema.svgz" -export-id = "CENTOSARTWORK" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/repository-version-schema.svgz.po" -command = "/usr/bin/convert -colors 128" - -[repository.html] -render-type = "asciidoc" -render-flow = "article" -render-from = "repository.asciidoc" -locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/repository.asciidoc.po" -images-from = "${TCAR_BASEDIR}/Artworks/Icons/Webenv/Final" -styles-from = "${TCAR_BASEDIR}/Artworks/Webenv/Docbook/1.69.1/Css" -formats = "xhtml" -render-page = "single chunks" diff --git a/Repository/repository-infra.svgz b/Repository/repository-infra.svgz deleted file mode 100644 index 8626f1d..0000000 Binary files a/Repository/repository-infra.svgz and /dev/null differ diff --git a/Repository/repository-version-schema.svgz b/Repository/repository-version-schema.svgz deleted file mode 100644 index 13a04db..0000000 Binary files a/Repository/repository-version-schema.svgz and /dev/null differ diff --git a/Repository/repository.asciidoc b/Repository/repository.asciidoc deleted file mode 100644 index b77a23f..0000000 --- a/Repository/repository.asciidoc +++ /dev/null @@ -1,1287 +0,0 @@ -The CentOS Artwork Repository -============================= -Alain Reguera Delgado -v1.0, Nov 2013 - -== Overview - -Organizations have 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 The -CentOS Community for helping on The CentOS Project 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 The CentOS Project 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. - -The CentOS Artwork Repository phases the question ``What can I do -for The CentOS Project?'' 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 The CentOS Artwork -Repository (through an automation script probably) to rebrand/update -the content of those packages inside The CentOS Distribution that must -include information specific to The CentOS Project itself (e.g., boot -loader, distribution installer, release notes, display managers, -release notes, web browsers default page, etc.). - -Most production tasks inside The CentOS Artwork Repository are focused -on the files needed to implement The CentOS Project corporate visual -identity.footnote:[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 The CentOS Project manifests its existence on.] 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 The CentOS Distribution are already covered by The CentOS -Project 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 The -CentOS Artwork Repository. - -In addition to visual manifestations, there are also emotional -feelings and ethical behaviours that must be considered as part of The -CentOS Project corporate identity. A pleasant experience in this area -includes The CentOS Wiki, specifically the way it was conceived and -administered. When the The CentOS Wiki was published, The CentOS -Project 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 The CentOS -Distribution, and reducing to zero the contraditions of precoceived -minds with respect, reason and passion. As result of this experience, -we found that The CentOS Community 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 The CentOS Community be able of moving through it. - -The CentOS Artwork Repository extends the feelings and ethicals -behaviours from The CentOS Wiki to itself by identifying the visual -manifestations The CentOS Project 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 The CentOS -Project and The CentOS Artwork Repository 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 ;-). - -[[corporate-mission]] -== Repository Mission - -The CentOS Artwork Repository exists to produce The CentOS Project -corporate visual identity. - -== Repository Infrastructure - -The CentOS Artwork Repository is made of one ``central repository'' -and many ``working copies'' of that central repository. The working -copies are independent one another, can be distributed all around the -world and provide a local place for designers, documenters, -translators and programmers to perform their work in a decentralized -way. The central repository, on the other hand, provides a common -place for all independent working copies to exchange data in the -community. - -image:repository-infra.png[repository-infra.png] - -=== Subversion - -The current infrastructure that holds The CentOS Artwork Repository on -the Internet, is made of the following components: - - * http://subversion.tigris.org/[Subversion] -- Modern Version Control System designed to replace CVS. - * http://trac.edgewall.org/[Trac] -- Enhanced wiki and issue tracking system. - * Httpd+WebDav as data exchanging route between the workstations and - the central repository, through the Internet. Httpd was configured - to provide service through SSL, so all traffic between the - workstations and the server be protected while it travels across - the Internet. The access rights are controlled by using a - combination of both Subversion's authorization files and Httpd's - password files. These files can be managed consistently through - Trac's WebAdmin plug-in. - -In this infrastructure, the first level of directories in the -repository provides the Subversion's standard trunk-branches-tags -layout. The second level of directories provides organization for -different work lines, as described in <>. All -other subsequent directory levels from second level on exist to -organize specific concepts related to the work line they belong to. - -=== Git - -In addition to current Subversion infrastructure, we are working on a -Git infrastructure with the intention of migrating the current -Subversion infrastructure up to it, progressively. The Git -infrastructure we are working on is made of the following components: - -* Git -- Fast version control system. -* Gitolite -- Highly flexible server for git directory version - tracker. -* Gitweb -- Simple web interface to git repositories. -* MantisBT -- Web-based issue tracking system. -* The data exchanging route between the working copies and the central - repository takes place through SSH. The access rights are controlled - by using a combination of SSH public keys and Gitolite's repository - configuration file. - -In this infrastructure, the first level of directories in the -repository provides organization for different work lines, as -described in <>. All other subsequent directory -levels from second level on exist to organize specific concepts -related to the work line they belong to. - -[[repo-convs-worklines]] -== Repository Work Lines - -The content production inside The CentOS Artwork Repository has been -divided into individual work lines that relate one another based on -the idea of doing one thing well. In this model, the content produced -individually by each work line is combined one another later to -achieve higher purposes (e.g., corporate identity for The CentOS -Project). The repository work lines, as conceived here, provide a -reliable environment for people to work synchronized and -decentralized. - -The action of combining work lines inside The CentOS Artwork -Repository is also known as the ``Production Cycle'' of CentOS -corporate visual identity. The rest of this section describes the -work lines available in the repository and how they integrate one -another. - -[[repo-convs-worklines-artworks]] -=== Graphic Design - -Graphic Design is the first component The CentOS Artwork SIG works out -in order to produce The CentOS Project corporate visual identity. -Through this work line, graphic designers create ``design models'' and -``artistic motifs'' for all the visual manifestation The CentOS -Project is made of. Once design models and artistic motifs are set in -place, graphic designers use the *render* module of *centos-art.sh* -script to combine them all into final images. - -The mission of Artworks work line is define all the visual -manifestations the The CentOS Project is made of and provide design -models and artistic motifs for them in order to produce the final -image files required to transmit the visual style that identifies The -CentOS Project as unique organization. - -The graphic design process takes place in the +Artworks/+ directory -stored at the first level of the repository directory structure. This -directory organizes themes (design models and artistic models), -palettes, brushes, icons, brands and customizations for the web -environment. - -To know more about The CentOS Project corporate visual identity, read -the article named -``_link:../../../Corporate/Final/en_US/index.html[The CentOS Project -Corporate Visual Identity]._'' - -[[repo-convs-worklines-l10n]] - -=== Localization - -Localization is the second component that must be worked out in the -production cycle of CentOS corporate visual identity. Through this -work line translators localize source files (e.g., SVG, DocBook, Shell -scripts) which are later used to produce localized images, localized -documentation and localized automation scripts. To localize source -files, translators use the *locale* module of *centos-art.sh* script -which takes care of retrieving translatable strings from source files -and provide a consistent localization interface based on GNU *gettext* -multi-lingual message production tool set and *xml2po* command. - -The mission of Localization work line is extending the visual identity -(produced in English language) to as many native languages as -possible, in order for people which doesn't understand English -language to feel more comfortable with The CentOS Project in their own -native languages. - -The localization process takes place inside the +Locales/+ directory -of each component that requires localization. This directory contains -the component related PO files organized in language-specific -directories. To know more about the specific localization process -read the *locale* module documentation. - -[[repo-convs-worlines-manuals]] - -=== Documentation - -Documentation is the third component that must be worked out in the -production cycle of corporate visual identity. Through this work line -documenters settle down the conceptual and practical uses around The -CentOS Artwork Repository and all the content produced inside it. To -write documentation, documenters use Asciidoc as source documentation -format and the *render* module of *centos-art.sh* script to transform -Asciidoc source documentation format into final output formats, -including man pages and html. - -The mission of Documentation work line is describe the standard -procedures The CentOS Artwork Repository relies on, as well as -conceive a place to help you understand what The CentOS Artwork -Repository is and what can you do with it. - -The Documentation work line takes place inside the +Documentation/+ -directory inside major components stored in the first directory level -of the repository (e.g., Artworks, Automation and Packages). - -[[repo-convs-worlines-packages]] -=== Packages - -The packages work line is the fourth component that must be worked out -in the corporate identity production cycle. Through this work line -packager gather final images, final translations and final -documentation related to artworks and put them all together inside RPM -packages. For this purpose, packagers use the *package* module of -*centos-art.sh* script which provides a consistent interface for -building packages inside the repository. - -The mission of Packages work line is package the information The -CentOS Project requires to re-brand The CentOS Distribution according -Red Hat redistribution guidelines. It is also the mission of this work -line to make The CentOS Artwork Repository easy to install, configure -and use by most graphic designers, documenters, programmers and -translators. - -The packages work line takes place in the +Packages/+ directory stored -at the first level of the repository directory structure. This -directory organizes both SOURCES and SPECS files used to build RPMS -and SRPMS files. In this directory, SOURCES and SPECS files are under -version control but RPMS and SRPMS produced from them are not. - -[[repo-convs-worklines-scripts]] -=== Automation - -The automation work line is the fifth and last component that must be -worked out in the corporate identity production cycle. This work line -closes the production cycle and provides the production standards -graphic designers, documenters, translators and packagers need to make -their work consistent and reusable. For this purpose, programmers -develop the *centos-art.sh* script. - -The mission of Automation work line is standardize the interaction of -work lines in a reliable way. - -The Automation work line takes place in the +Automation/+ directory -stored at the first level of the repository directory structure. -Presently, most of the automation work is done in Bash. - -== Preparing Your Workstation - -Once your workstation has been installed, it is time for you to -configure it. The configuration of your workstation consists on -defining your workplace, download a working copy from The CentOS Artwork Repository and -finally, run the *prepare* functionality of -*centos-art.sh* script to install/update the software -needed, render images, create links, and anything else needed. - -=== Define Your Workplace - -Once you've installed the workstation and it is up and running, you -need to register the user name you'll use for working. In this task -you need to use the commands *useradd* and *passwd* to create the user -name and set a password for it, respectively. These commands require -administrative privileges to be executed, so you need to login as -``root'' superuser for doing so. - -[CAUTION] -Do not use the ``root'' username for regular tasks inside your working -copy of The CentOS Artwork Repository. This is dangerous and might -provoke irreversible damages to your workstation. - -When you've registered your user name in the workstation, it provides -an identifier for you to open a user's session in the workstation and -a place to store the information you produce, as well. This place is -known as your home directory and is unique for each user registered in -the workstation. For example, if you register the user name john in -your workstation, your home directory would be located at -+/home/john/+. - -At this point it is important to define where to download the working -copy of The CentOS Artwork Repository inside your home directory. -This decision deserves special attention and should be implemented -carefully in order to grant a standard environment that could be -distributed. Let's see some alternatives. - -==== Different absolute paths - -Consider that you store your working copy under -+/home/john/Projects/artwork/+ and I store mine under -+/home/al/Projects/artwork/+, we'll end up refering the same files -inside our working copies through different absolute paths. This -alternative generates a contradiction when files which hold path -information inside are committed up to the central repository from -different working copies. The contradiction comes from the question: -which is the correct absolute path to use inside such files, yours or -mine? (None of them is, of course.) - -==== One unique absolute path - -Another case would be that where you and I ourselves use one unique -home directory (e.g., +/home/centos/Projects/artwork/+) to store the -working copy of The CentOS Artwork Repository in our own workstations, -but configure the subversion client to use different user names to -commit changes up from the working copy to the central repository. -This alternative might be not so good in situations where you and I -have to share the same workstation. In such cases, it would be -required that we both share the password information of the same -system user (the ``centos'' user in our example) which, in addition, -gives access to that user's subversion client configuration and this -way provokes the whole sense of using different subversion credentials -for committing changes to be lost. - -==== Different absolute paths, dynamic expansion, symbolic links, relative links, and environment variables - -With this solution it is possible to store working copies of The -CentOS Artwork Repository on different locations inside the same -workstation without lose relation between files. Here we use the -TCAR_WORKDIR environment variable to set the location of the working -copy inside the workstation. Later the centos-art.sh scripts uses this -value as reference to determine where the working copy is. This value -is also the one used for dynamic expansion inside design models and -other similar files. In the case of web projects where different -components are required to produce the final content, we create -symbolic links between them and use relative paths so it is possible -to reuse them and retain the relation between them in different -contexts. - -For example, lets consider the organization of XHTML manuals rendered -from DocBook source files. When you render a DocBook manual inside The -CentOS Artwork Repository it creates XHTML files. This XHTML files -use images and common style sheets for better presentation. Both of -these images and styles components live outside the XHTML structure -so, in order to make them available relatively to the XHTML structure, -we created symbolic links from the XHTML structure to the outside -location where they are in. The creation of symbolic links takes -place automatically when each DockBook manual is rendered through -*centos-art.sh*, which uses the value of TCAR_WORKDIR environment -variable as reference to determine the absolute path of the working -copy. - -Because absolute paths are no longer stored inside permanent files and -*centos-art.sh* script uses the TCAR_WORKDIR environment variable to -determine where the working copy is stored in the workstation, it -should be safe to download working copies of The CentOS Artwork -Repository anywhere in the workstation. One just have to be sure that -the value of TCAR_WORKDIR environment variable does match the location -of the working copy you are using. - -=== Download Your Working Copy - -In order to use The CentOS Artwork Repository you need to download a -working copy from the central repository into your workstation. To -download such working copy use the following command: - ----------------------------------------------------------------------- -git clone gitolite@centos.org.cu/centos-artwork.git ----------------------------------------------------------------------- - -This command will create your working copy inside your home directory, -specifically in a directory named artwork.git. Inside this directory you -will find all the files you need to work with inside The CentOS -Artwork Repository. If you want to have your working copy in a -location different to that one shown above. - -The first time you download the working copy it contains no image -files, nor documentation, or localized content inside it. This is -because all the files provided in the working copy are source files -(e.g., the files needed to produce other files) and it is up to you to -render them in order to produce the final files (e.g., images and -documentation) used to implement The CentOS Project corporate visual -identity. - -=== Configure Administrative Tasks - -Most of the administrative tasks you need to perform in your working -copy of The CentOS Artwork Repository are standardized inside the -*prepare* functionality of *centos-art.sh* script. Inside -*centos-art.sh* script, all administrative task are invoked through -the *sudo* command. Thus, in order for the *centos-art.sh* script to -perform administrative tasks, you need to update the *sudo*'s -configuration in a way that such administrative actions be allowed. - -At time of this writing the *centos-art.sh* script -implements just one administrative task, that is package management. -Nevertheless, in the future, other administrative tasks might be -included as well (e.g., installing themes locally from the working -copy for testing purposes.). - -To update the *sudo*'s configuration, execute the *visudo* command as -``root''. Later, uncoment the Cmnd_Alias related -to ``SOFTWARE'' and add a line for your username allowing software -commands. This configuration is illustrated in . - -[[repo-ws-config-sudoers-example]] -.The /etc/sudoers configuration file -====================================================================== ----------------------------------------------------------------------- -## Installation and management of software -Cmnd_Alias SOFTWARE = /bin/rpm, /usr/bin/up2date, /usr/bin/yum - -## Next comes the main part: which users can run what software on -## which machines (the sudoers file can be shared between multiple -## systems). -## Syntax: -## -## user MACHINE=COMMANDS -## -## The COMMANDS section may have other options added to it. -## -## Allow root to run any commands anywhere -root ALL=(ALL) ALL - -## Allow the centos user to run installation and management of -## software anywhere. -al ALL=(ALL) SOFTWARE ----------------------------------------------------------------------- -====================================================================== - -[[repo-ws-config-runout]] -=== Run Preparation Tool - -Once you've both downloaded a working copy from The CentOS Artwork -Repository and configured the *sudo* configuration file successfully, -run the *prepare* functionality of *centos-art.sh* script to complete -the configuration process using the following command: - ----------------------------------------------------------------------- -~/artwork/Scripts/Bash/centos-art.sh prepare ----------------------------------------------------------------------- - -[[repo-convs-filename-rfiles]] -== Repository File Names - -Inside The CentOS Artwork Repository, file names are always written in -lowercase. Digits (e.g., 0, 1, 2), hyphen (-), dot (.) and low line -(_) characters are also accepted. In case you use hyphen and dot -characters, don't use them as first character in the file name. - -=== File Names Written Correctly - -The following file names are written correctly: - -* +01-welcome.png+ -* +splash.png+ -* +anaconda_header.png+ - -=== File Names Written Incorrectly - -* +01-Welcome.png+ -* +-welcome.png+ -* +Splash.png+ -* +AnacondaHeader.png+ - -== Repository Link Names - -Inside The CentOS Artwork Repository, links are always symbolic and -follow the same name convention used by regular files, as described in -<>. - -== Repository Directory Names - -Inside The CentOS Artwork Repository, directory names are all written -capitalized and sometimes in cammel case. Digits (e.g., 0, 1, 2), -hyphen (-), dot (.) and low line (_) characters are also accepted. In -case you use hyphen and dot characters, don't use them as first -character in the directory name. - -=== Directory Names Written Correctly - -The following directory names are written correctly: - -* +Identity+ -* +Themes+ -* +Motifs+ -* +TreeFlower+ -* +0.0.1+ -* +0.0.1-35+ - -=== Directory Names Written Incorrectly - -The following directory names are written incorrectly: - -* +identity+ -* +theMes+ -* +MOTIFS+ -* +treeFlower+ -* +.0.1+ -* +.0.1-35+ - -== Repository Directory Structure - -Occasionly, you may find that new components of The CentOS Project -corporate visual identity need to be added to the repository in order -to work them out. If that is the case, the first question we need to -ask ourselves, before starting to create directories blindly all over, -is: _What is the right place to store it?_ - -To create a directory structure inside the repository you need to -define the concept behind it first. Later you need to create a new -directory inside the repository, remembering that there are locations -inside the repository that already define concepts you probably would -prefer to reuse. For example, the +Artworks/Themes/Motifs+ directory -stores artistic motifs of different themes, the -+Artworks/Themes/Models+ directory stores design models for themes, -the +Documentation+ directory stores documentation, +Locales+ stores -translation messages, and the +Automation+ stores automation scripts. - -The best suggestion we can probably give you would be to send a mail -with your questions to the mailto:centos-devel@centos.org[CentOS -developers mailing list] -(mailto:centos-devel@centos.org[centos-devel@centos.org]). This is -the place where development of The CentOS Artwork Repository takes place and surely, in -community, it will be possible to find a place for your new component -inside the repository. - -The following sub-sections describe relevant directories of The CentOS -Artwork Repository that you can use as reference to know where the -files you are looking for are stored in and where you can store new -files, as well. - -=== The +Artworks/+ Directory - -This directory contains files affecting the visual style of The CentOS -Project. This directory organizes Brushes, Gradients, Fonts, Palettes, -Patterns Themes and the web environment customizable files. - -=== The +Artworks/Brands/+ Directory - -This directory ... - -=== The +Artworks/Brushes/+ Directory - -This directory contains GIMP brushes. Brushes stored in this directory -will be available inside GIMP's brushes dialog. - -=== The +Artworks/Documentation/+ Directory - - -This directory ... - -=== The +Artworks/Fonts/+ Directory - -This directory contains font files. Font files stored in this -directory will be available to be used from applications like GIMP and -Inkscape. - -=== The +Artworks/Gradients/+ Directory - -This directory contains GIMP gradients. Gradients stored in this -directory will be available inside GIMP's gradients dialog. This -directory organizes gradient files inside - -=== The +Artworks/Icons/+ Directory - -This directory ... - -=== The +Artworks/Palettes/+ Directory - -This directory ... - -=== The +Artworks/Patterns/+ Directory - -This directory contains GIMP patterns. Patterns stored in this -directory will be available inside GIMP's patterns dialog. - -=== The +Artworks/Themes/+ Directory - -This directory ... - -=== The +Artworks/Webenv/+ Directory - -This directory ... - -=== The +Automation/+ Directory - -This directory ... - -== Repository Authoring - -The content produced inside The CentOS Artwork Repository is copyright -of The CentOS Project. This is something you, as author, should be -aware of because you are contributing your creation's rights to -someone else; The CentOS Project in this case. This way, your work is -distributed using ``The CentOS Project'' as copyright holder, not your -name (even you remain as natural author of the work). Because The -CentOS Project is the copyright holder, is the license chosen by The -CentOS Project the one applied to your work, so it is the one you need -to agree with before making a creation inside The CentOS Artwork -Repository. - -The CentOS Project is a community project controlled by its own -community of users. Inside the community, The CentOS Administrators -group is the higher authority and the only one able to set core -decision like the kind of license used inside the project and -subproject like The CentOS Artwork Repository. - -The redistribution conditions of The CentOS Artwork Repository are -described in ... - -== Repository Publishing - -When you perform changes inside your working copy, those changes are -local to your working copy only. In order for you to share your -changes with others, you need to push them up to the central -repository the working copy you are using was initially downloaded -from. To push your changes up to the central repository see -git-push(1) man page. - -Initially, you won't be able to publish your changes to The CentOS -Artwork Repository immediately. It is necessary that you prove your -interest in contributing first sending a mail to the -http://lists.centos.org/mailman/listinfo/centos-devel[CentOS -Developers mailing list] -(mailto:centos-devel@centos.org[centos-devel@centos.org]), preferably -in conjunction with a description of the changes you pretend to -commit. This restriction is necessary in order to protect the source -repository from spammers. - -Once you've received access to publish your changes, they will remain -valid to you and there is no need for you to request permission to -publish new changes as long as you behave as a good cooperating -citizen. - -As a good cooperating citizen one understand of a person who respects -the work already done by others and share ideas with authors before -changing relevant parts of their work, specially in situations when -the access required to realize the changes has been granted already. -Of course, there is a time when conversation has taken place already, -the paths has been traced and changing the work is so obvious that -there is no need for you to talk about it; that's because you already -did, you already built the trust to keep going. As complement, the -mailing list mentioned above is available for sharing ideas in a way -that good relationship between community citizens could be constantly -balanced. - -The relationship between community citizens is monitored by repository -administrators. Repository administrators are responsible of granting -that everything goes the way it needs to go in order for The CentOS Artwork Repository to -accomplish its mission (see <>). - -== Repository Copying Conditions - -The CentOS Project uses The CentOS Artwork Repository to produce The -CentOS Project corporate visual identity. - -The The CentOS Artwork Repository is not in the public domain; it is -copyrighted and there are restrictions on their distribution, but -these restrictions are designed to permit everything that a good -cooperating citizen would want to do. What is not allowed is to try -to prevent others from further sharing any version of this work that -they might get from you. - -Specifically, we want to make sure that you have the right to give -away copies of The CentOS Artwork Repository, that you receive source -code or else can get it if you want it, that you can change this work -or use pieces of it in new free works, and that you know you can do -these things. - -To make sure that everyone has such rights, we have to forbid you to -deprive anyone else of these rights. For example, if you distribute -copies of the The CentOS Artwork Repository, you must give the -recipients all the rights that you have. You must make sure that -they, too, receive or can get the source code. And you must tell them -their rights. - -Also, for our own protection, we must make certain that everyone finds -out that there is no warranty for the The CentOS Artwork Repository. -If this work is modified by someone else and passed on, we want their -recipients to know that what they have is not what we distributed, so -that any problems introduced by others will not reflect on our -reputation. - -The The CentOS Artwork Repository is released as a GPL work. -Individual packages used by The CentOS Artwork Repository include -their own licenses and the The CentOS Artwork Repository license -applies to all packages that it does not clash with. If there is a -clash between the The CentOS Artwork Repository license and individual -package licenses, the individual package license applies instead. - -The precise conditions of the license for the The CentOS Artwork -Repository are found in (...). This manual specifically is covered by -the conditions found in (...). - -[[repo-history]] -== History - -=== 2008 - -The CentOS Artwork Repository started at -mailto:centos-devel@centos.org[The CentOS Developers Mailing List] -around 2008, on a discussion about how to automate slide images used -by Anaconda (The CentOS Distribution installer). In such discussion, -http://wiki.centos.org/RalphAngenendt[Ralph Angenendt] rose up his -hand to ask --Do you have something to show?. - -To answer the question, -http://wiki.centos.org/AlainRegueraDelgado[Alain Reguera Delgado] -suggested a bash script which combined SVG and SED files in order to -produce PNG images in different languages --in conjunction with -the proposition of creating a Subversion repository where translations -and image production could be distributed inside The CentOS Community. - -http://wiki.centos.org/KaranbirSingh[Karanbir Singh] considered the -idea intresting and provided the infrastructure necessary to support -the effort. This way, https://projects.centos.org/trac/artwork[The -CentOS Artwork SIG] and https://projects.centos.org/svn/artwork[The -CentOS Artwork Repository] 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 The CentOS Artwork Repository, both using a -Trac web interface. - -Once The CentOS Artwork Repository was available, Alain Reguera -Delgado uploaded the bash script used to produce the Anaconda -slides;footnote:[See -https://projects.centos.org/trac/artwork/browser/Main/render.sh?rev=15] -Ralph Angenendt documented it very well;footnote:[See -https://projects.centos.org/trac/artwork/wiki/HowToTranslateSlides] -and people started to download working copies of The CentOS Artwork -Repository to produce slide images in their own -languages.footnote:[See -http://www.google.com/search?q=anaconda+slides+site%3Alists.centos.org] - -From this time on The CentOS Artwork Repository has been evolving into -an automated production environment where The CentOS Community can -conceive The CentOS Project corporate visual identity. - -The exact changes commited to The CentOS Artwork Repository through -history can be found in the -https://projects.centos.org/trac/artwork/timeline[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 <>. - -=== 2009 - -Around 2009, the rendition script was at a very rustic state where -only slide images could be produced, so it was redesigned to extend -the image production to other areas, different from slide images. In -this configuration, one SVG file was used as input to produce a -translated instance of it which, in turn, was used to produce one -translated PNG image as output. The SVG translated instance was -created through SED replacement commands. The translated PNG image was -created from the SVG translated instance using Inkscape command-line -interface. - -The repository directory structure was prepared to receive the -rendition script using design templates and translation files in the -same location. There was one directory structure for each art work -that needed to be produced. In this configuration, if you would want -to produce the same art work with a different visual style or -structure, it was needed to create a new directory structure for it -because both the image structure and the image visual style were -together in the design template. - -The rendition script was moved to a common place and linked from -different directory structures. There was no need to have the same -code in different directory structures if it could be in just one -place and then be linked from different locations. - -Corporate identity concepts began to be considered. As referece, it -was used the book "Corporate Identity" by Wally Olins (1989) and -http://en.wikipedia.org/Corporate_identity[Wikipedia related links]. -This way, the rendition script main's goal becomes to: _automate the -production process of a monolithic corporate visual identity -structure, based on the mission and the release schema of The CentOS -Project_. - -The repository directory structures began to be documented by mean of -flat text files. Later, documentation in flat text files was moved -onto LaTeX format and this way The CentOS Artwork User Guide was -initiated. - -=== 2010 - -Around 2010, the rendition script changed its name from *render.sh* to -*centos-art.sh* and became a collection of functionalities where -rendition was just one among others (e.g., documentation and -localization). - -The *centos-art.sh* was initially conceived to automate frequent tasks -inside the repository based in the idea of Unix toolbox: to create -small and specialized tools that do one thing well. This way, -functionalities inside *centos-art.sh* began to be identified and -separated one another. For example, when images were rendered, there -was no need to load functionalities related to documentation manual. -This layout moved us onto ``common functionalities'' and ``specific -functionalities'' inside *centos-art.sh* script. Common -functionalities are loaded when *centos-art.sh* script is initiated -and are available to specific functionalities. - -Suddenly, no need was found to keep all the links spreaded around the -repository in order to execute the *centos-art.sh* script from -different locations. The *centos-art* command-line interface was used -instead. The *centos-art* command-line interface is a symbolic link -stored inside the +\~/bin+ directory pointing to *centos-art.sh* -script. As default configuration, inside The CentOS Distribution, the -path to +\~/bin+ is included in the search path for commands (see PATH -environment variable). This way, using the *centos-art* command-line -interface, it is possible to execute the *centos-art.sh* script from -virtually anywhere inside the workstation, just as we frequently do -with regular commands. - -Start using GNU getopt as default option parser inside the -*centos-art.sh* script. - -The repository directory structure was updated to improve the -implementation of corporate visual identity concepts. Specially in -the area related to themes. Having both structure and style in the -same file introduced content duplication when producing art works. -Because of this reason, they were separated into two different -directory structures: the design models and the artistic motifs -directory structures. From this point on, the *centos-art.sh* was -able to produce themes as result of arbitrary combinations between -design models (structure) and artistic motifs (visual styles). - -In the documentation area, the documents in LaTeX format were migrated -to Texinfo format. In this configuration, each directory structure in -the repository has a documentation entry associated in a Texinfo -structure which can be read, edited and administered (e.g., renamed, -deleted and copied) interactively through *centos-art.sh* script. -Additionally, the texi2html program was used to produced customized -XHTML output in conjunction with CSS from The CentOS Web Environment. - -=== 2011 - -Around 2011, the *centos-art.sh* script was -redesigned to start translating XML-based files (e.g., SVG and Docbook -files) through *xml2po* program and shell scripts -(e.g., Bash scripts) through GNU gettext tools. This configuration -provided a stronger localization interface for graphic designers, -translators and programmers. The SED replacement files are no longer -used to handle localization. - -The *render*, *help* and -*locale* functionalities consolidated themselves as -the most frequent tasks performed in The CentOS Artwork Repository working copy. -Additionally, the *prepare* and -*tuneup* functionalities were also maintained as -useful tasks. - -In the documentation area, it was introduced the transformation of -localized DocBook XML DTD instances through the -*render* and *locale* -functionalities. In this configuration, you use -*locale* functionality to localize DocBook source -files to your prefered language and later, using the -*render* functionality, you can produce the -localized XTHML and PDF output as specified in a XSLT layer. -Unfortunly, the transformation DocBook XML -> FO -> PDF (through -PassiveTex) seems to be buggy inside CentOS 5.5, so it was commented -inside the *centos-art.sh* script. Most documentation -is now organized in DocBook format, even Texinfo format remains as the -only format with automated production tasks. - -In the automation area, the *centos-art.sh* script -introduced the capability of reading configuration files. The main -goal here was moving some command-line options from functionalities -onto a more persistent medium. Most configuration files were set to -define the position of brands inside images and documentation manual -specific options. - -[[repo-history-2012]] -=== 2012 - -The CentOS Artwork Repository development was eventually stopped at -November 2011 until July 2012 when we needed to make the -*centos-art.sh* script a bit more customizable than it presently was. -For example, it was considered as a need that functionalities inside -the *centos-art.sh* script must be not just conceived independent one -another but reusable in different contexts as well. - -[[repo-history-2012-1]] -==== Make Localization Of *centos-art.sh* Script Specific To Different Contexts - -The procedure used to locale messages inside the *centos-art.sh* -script has to be re-designed in order to accept such pluggable -behavior into the script. We couldn't publish unique -+centos-art.sh.po+ and +centos-art.sh.mo+ files because they may -contain different information in different contexts. For example, if -you are using the *render* and -*help* functionalities you only need translation -messages for them and not those from other functionalities that may -exist in the central repository but you didn't download nor use into -your working copy. - -One solution for this could be to have independent PO files for each -functionality of *centos-art.sh* script which are -combined to create the final PO and MO files that -*gettext* uses to retrive translated strings -when *centos-art.sh* script is running. For this -solution to be effective, you must be selective about the -functionalities and locales directories you download into your working -copy. For example, if you want to use the render functionality and its -locale messages only, you must download the required directories and -exclude others. - -[NOTE] -====================================================================== -In case you don't want to be selective and download the whole -repository, the creation of the +centos-art.sh.po+, -+centos-art.sh.pot+ and -+centos-art.sh.mo+ files will occur automatically -the first time you run the *prepare* functionality -(which require the *locale* functionality to be -available), or later, by running the following command: - ----------------------------------------------------------------------- -centos-art locale Scripts/Bash --update ----------------------------------------------------------------------- - -For more information about the *prepare* and *locale* functionalities, -see their respective manuals. -====================================================================== - -[[repo-history-2012-2]] -.Directory structure of a rendering-only context -====================================================================== ----------------------------------------------------------------------- -/home/centos/Projects/artwork/ -|-- Locales/ -| `-- Scripts/ -| `-- Bash/ -| `-- es_ES/ -| |-- Functions/ -| | |-- Commons/ -| | | |-- messages.po -| | | `-- messages.pot -| | |-- Locales/ -| | | |-- messages.po -| | | `-- messages.pot -| | `-- Render/ -| | |-- messages.po -| | `-- messages.pot -| |-- LC_MESSAGES/ -| | `-- centos-art.sh.mo -| |-- centos-art.sh.po -| `-- centos-art.sh.pot -`-- Scripts/ - `-- Bash/ - |-- Functions/ - | |-- Commons/ - | |-- Locales/ - | `-- Render/ - `-- centos-art.sh ----------------------------------------------------------------------- -====================================================================== - -As shown in <>, both *Commons* and *Locales* -functionalities will always be required directories. The +Commons+ -directory contains the common functionalities and the *Locales* -directory contains the standard procedures you need to run in order to -build the final +centos-art.sh.mo+ file used by *gettext* to retrive -translation strings when the *centos-art.sh* script is running. -Remember that +centos-art.sh.pot+, +centos-art.sh.po+ files aren't -under version control and they are built by combining each -funtionality message.po file into a PO and later a MO file. - -A practical example of using the solution described above may be found -when you are working on the corporate identity of The CentOS Project -and then need to start a new corporate identity project for another -organization. You want to keep the directory structure of The CentOS -Artwork Repository and its automation tool, the *centos-art.sh* -script. Your new project requires you to introduce new -functionalities to *centos-art.sh* which don't fit the needs of The -CentOS Project (e.g., you want to introduce a *report* functionality -to mesure how much connect time do you consume through your PPP -internface.) or you just want to keep the directory structure of your -new project as simple as possible. - -To go through this it is possible to mix specific parts of different -central repositories into one single working copy. This is the -working copy you'll use to manage your new project. In -<>, we see how the +Render+, +Locales+ and -+Commons+ directories which come from the The CentOS Artwork -Repository has been integrated into the working copy of your new -project. - ----------------------------------------------------------------------- -/home/al/Projects/Myapp/ -|-- Locales/ -| `-- Scripts/ -| `-- Bash/ -| `-- es_ES/ -| |-- Functions/ -| | |-- Commons/ <--| from https://projects.centos.org/svn/artwork/ -| | | |-- messages.po -| | | `-- messages.pot -| | |-- Locales/ <--| from https://projects.centos.org/svn/artwork/ -| | | |-- messages.po -| | | `-- messages.pot -| | |-- Render/ <--| from https://projects.centos.org/svn/artwork/ -| | | |-- messages.po -| | | `-- messages.pot -| | `-- Report/ -| | |-- messages.po -| | `-- messages.pot -| |-- LC_MESSAGES/ -| | `-- myapp.sh.mo -| |-- myapp.sh.po -| `-- myapp.sh.pot -`-- Scripts/ - `-- Bash/ - |-- Functions/ - | |-- Commons/ <--| from https://projects.centos.org/svn/artwork/ - | |-- Locales/ <--| from https://projects.centos.org/svn/artwork/ - | |-- Render/ <--| from https://projects.centos.org/svn/artwork/ - | `-- Report/ - `-- myapp.sh ----------------------------------------------------------------------- - -At this point, your working copy contains files from two different -central repositories. One repository provides the files of your new -organization project and the other one provides the files related to -the *render* functionality from The CentOS Artwork Repository. In -this environment, all updates commited to the +Render+, +Locales+ and -+Commons+ directories at The CentOS Artwork Repository will be -available to you too, the next time you update your working copy. -Likewise, if you change something in any of these directories and -commit your changes, your changes will be available to poeple working -in The CentOS Artwork Repository the next time they update their -working copies. - -Understanding the need of mixing different central repositories into a -single working copy is an important step for reusing the -functionalities that come with centos-art.sh script, but it is not -enough if you want to customize the information produced by it. By -default, the centos-art.sh script uses information related to The -CentOS Project. You probably need to change this if you are producing -images to a different organization than The CentOS Project. For -example, some of the information you might need to change would be the -copyright holder, brands, domain names, mailing lists, and so forth. -To change this information you need to duplicate the file -+centos-art.sh+ and rename it to something else. Later, you need to -edit the renamed version and change variables inside according your -needs. In <>, we used the name *myapp.sh* instead -of *centos-art.sh* so the information we set inside it could reflect -the specific needs that motivated the creation of a new project -without affecting those from The CentOS Project. - -Most of the information you need to change in your duplicated version -of +centos-art.sh+ file is controlled by a set of read-only variables. -You modify these variables here and they will be available all along -the script execution time. For example, you can change the value of -CLI_WRKCOPY variable inside your duplicated version of +centos-art.sh+ -to change the absolute path you use to store your working copy. - -==== Enhance The CentOS Logo Construction - -The CentOS Logo is made of two different components known as The -CentOS Symbol and The CentOS Type. Presently (at the end of -September), to produce these components, we create one SVG image for -each PNG image we want to produce, store it in -+Identity/Models/Brands/Logos+ directory structure and run the -command: - ----------------------------------------------------------------------- -centos-art render Identity/Images/Brands/Logos* ----------------------------------------------------------------------- - -This model works and scales well in situations when there isn't a need -to reuse final images among themselves. However, when you need to -reuse images among themselves, a better solution is required. The goal -here would be: don't create SVG images for PNG -images you can build based on other PNG images. - -This might be achieved through one of the following ways: - -- Create a new specific functionality to achieved the goal. Needed - because the *render* specific functionality uses SVG files as - reference to build images (i.e., one SVG image produces one PNG - image). - -- Modify *render* functionality to work in different modes based on - file type or file extension. The first mode would use SVG files as - reference to build PNG images (just as it was doing so far). The - second mode would use a configuration file named +render.conf+ as - reference inside the design models directory you want to produce - images for so as to build the related PNG images. In this second - case, the configuration file specifies how final PNG images will be - produced (e.g., by appending or overlapping them one another). - -For example, consider the following command-line: - ----------------------------------------------------------------------- -centos-art render Identity/Images/Brands/Logos ----------------------------------------------------------------------- - -This command should evaluate which type of rendition will be done, -based on whether the source file is a scalable vector graphic (SVG) or -a configuration file. To make this decision, the *centos-art.sh* -script looks for SVG files first, and configuration files later. When -SVG files are found, the *centos-art.sh* script uses a list of SVG -files and process them one by one excluding any related configuration -file that could exist. On the other hand, if no SVG file is found -inside the related design model directory structure, the -*centos-art.sh* script will use the configuration file with the name -+render.conf+ to create images as specified inside it. When neither a -SVG or a configuration file is found inside the design model directory -structure, the *centos-art.sh* script finishes its execution without -any error message. For example, if no SVG file is found inside -+Identity/Models/Brands/Logos/+ directory and the -+Identity/Models/Brands/Logos/images.conf+ configuration file exists -therein with the following content: - ----------------------------------------------------------------------- -[centos.png] -models = "Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz" -formats = "xpm jpg" -heights = "48 78" -fgcolor = "000000 ffffff" -bgcolor = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-artwork.png] -models = "Identity/Models/Brands/Symbols/centos-symbol-forlogos.svgz Identity/Models/Brands/Types/centos.svgz Identity/Models/Brands/Types/artwork.svgz" -formats = "xpm jpg" -heights = "48 78" -fgcolor = "000000 ffffff" -bgcolor = "ffffff-0" -command = "/usr/bin/convert +append" ----------------------------------------------------------------------- - -The *centos-art.sh* script should produce the -following image files: - ----------------------------------------------------------------------- -Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.jpg -Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.png -Identity/Images/Brands/Logos/000000/ffffff-0/48/centos.xpm -Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.png -Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.jpg -Identity/Images/Brands/Logos/000000/ffffff-0/48/centos-artwork.xmp -Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.jpg -Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.png -Identity/Images/Brands/Logos/000000/ffffff-0/78/centos.xpm -Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.png -Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.jpg -Identity/Images/Brands/Logos/000000/ffffff-0/78/centos-artwork.xmp -Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.jpg -Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.png -Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos.xpm -Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.png -Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.jpg -Identity/Images/Brands/Logos/ffffff/ffffff-0/48/centos-artwork.xmp -Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.jpg -Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.png -Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos.xpm -Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.png -Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.jpg -Identity/Images/Brands/Logos/ffffff/ffffff-0/78/centos-artwork.xmp ----------------------------------------------------------------------- - -The final location for storing images output inside the repository is -determined by using the design model directory provided as argument. -Basically, the *centos-art.sh* script changes the -path components from Models to Images and adds foreground color, -background color, height value and image name to it to differentiate -rendered images. - -In case you need to restrict the amount of files you want to produce -including their formats, heights, colors and commands, you need to -modify the content of the related +render.conf+ configuration file. -There is not any command-line option available for such tasks. The -most *render* command-line options can do for you is when there are -more than one configuration file inside the same design model -directory and you need to specify which one of them will be used as -reference. In such case you can use the - option. - -When images are produced through configuration files, the -*centos-art.sh* script takes the order provided in -the list of design models to build the list of images you will work -with through the command specified. For example, the order in which -images will be appended or overlapped. - -Localization of logo images will not be and must not be supported in -any way. That would bring disastrous confusion in the area of visual -recognition. - -=== 2013 - -Development of CentOS Artwork Repository was eventually stopped at -November, 2012, when I moved myself from Cienfuegos to Havana city for -working. I returned on May 14th of 2013 and continued developing The -CentOS Artwork Repository at home. Considered a -Git+Gitolite+Gitweb+MantisBT infrastructure for CentOS Artwork -Repository and started working on it in my workstation. This, in -order to implement a distributed work flow for The CentOS Artwork -Repository based on Git version control system. - -[[repository-history-2013-UpdateRepositoryLayout]] -==== Update Repository Directories Structure - -I face the following situation: I am working on a documentation -project named ``solinfo-network''. While I was organizing it, I found -that the directory structure of The CentOS Artwork Repository fits -quite well the needs of ``solinfo-network'' documentation project. -However, I don't want to duplicate automation scripts in two separate -projects, but share them between themselves (i.e., changes committed -to automation scripts are pushed to one single place, not two.). - -When we use Subversion repositories, it is possible to checkout -specific parts of different repositories into a new repository. This -is very useful if we need to create several projects that share the -same component and we don't want to duplicate the common component in -two or more different projects but ``share'' it between them. - -When we use Git repository, it is not possible to checkout specific -parts of a repository but the complete tree. So, in order to share -common components of a repository we need to create one repository for -each common component we want to share and then use Git -submodulessee progit-book, page 152. This -requires that brand new repositories be created for each component we -want to share. - -In both situations, including Git and Subversion repositories, it is -necessary that we define very well the structure of each component we -want to share, so it can be ``plugged'' nicely into other projects. -Likewise, other projects must have the same directory structure the -pluggable component was design to fit in. If these two conditions can -be reached, it would be possible to reuse repositories components and -concentrate efforts. The current directory structure The CentOS -Artwork Repository is set in allows components inside Subversion -repositories to be reused by related working copies. However, we -cannot do the same if it is stored in a Git repository. In order for -Git repositories to be able to share components with other Git -repositories, The CentOS Artwork Repository directory structure needs -to be reorganized to better delineate each component the repository is -made of. - -// vim: set syntax=asciidoc: