diff --git a/Artworks/Brands/Logos/Webenv/centos.org.cu/render.conf b/Artworks/Brands/Logos/Webenv/centos.org.cu/render.conf deleted file mode 100644 index 7875a57..0000000 --- a/Artworks/Brands/Logos/Webenv/centos.org.cu/render.conf +++ /dev/null @@ -1,62 +0,0 @@ -# This file contains the information used to build The CentOS Logo in -# different sizes, colors and formats. - -[centos-logo.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.org.cu/centos.svgz}" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-artwork-logo.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.org.cu/{centos,artwork}.svgz}" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-wiki-logo.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/{centos.org.cu/centos,centos.org/wiki}.svgz}" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-bugs-logo.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.org.cu/{centos,bugs}.svgz}" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-people-logo.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.org.cu/{centos,people}.svgz}" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-lists-logo.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.org.cu/{centos,lists}.svgz}" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" diff --git a/Artworks/Brands/Logos/Webenv/centos.org/render.conf b/Artworks/Brands/Logos/Webenv/centos.org/render.conf deleted file mode 100644 index 914a693..0000000 --- a/Artworks/Brands/Logos/Webenv/centos.org/render.conf +++ /dev/null @@ -1,52 +0,0 @@ -# This file contains the information used to build The CentOS Logo in -# different sizes, colors and formats. - -[centos-logo.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.org/centos.svgz}" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-artwork-logo.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.org/{centos,artwork}.svgz}" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-wiki-logo.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.org/{centos,wiki}.svgz}" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-bugs-logo.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.org/{centos,bugs}.svgz}" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-people-logo.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.org/{centos,people}.svgz}" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" diff --git a/Artworks/Brands/Logos/Webenv/render.conf b/Artworks/Brands/Logos/Webenv/render.conf new file mode 100644 index 0000000..54bf495 --- /dev/null +++ b/Artworks/Brands/Logos/Webenv/render.conf @@ -0,0 +1,13 @@ +# This file contains the information used to build The CentOS Logo in +# different sizes, colors and formats. + +[centos-logo.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Symbols/Webenv/centos.svgz,Types/Webenv/centos.svgz}" +render-flow = "extended" +export-id = "CENTOSARTWORK" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" diff --git a/Artworks/Brands/Symbols/Default/render.conf b/Artworks/Brands/Symbols/Default/render.conf index b3cb8e7..3d512f1 100644 --- a/Artworks/Brands/Symbols/Default/render.conf +++ b/Artworks/Brands/Symbols/Default/render.conf @@ -6,6 +6,6 @@ render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Symbols/Default/centos.svgz" render-flow = "extended" formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +heights = "11 16 20 22 24 26 32 36 38 40 48 52 64 72 78 96 112 124 128 148 164 196 200 512" fgcolors = "000000 ffffff" bgcolors = "ffffff-0" diff --git a/Artworks/Brands/Symbols/Webenv/centos.svgz b/Artworks/Brands/Symbols/Webenv/centos.svgz index 5685050..2e8520d 100644 Binary files a/Artworks/Brands/Symbols/Webenv/centos.svgz and b/Artworks/Brands/Symbols/Webenv/centos.svgz differ diff --git a/Artworks/Brands/Symbols/Webenv/render.conf b/Artworks/Brands/Symbols/Webenv/render.conf index ec75634..346692c 100644 --- a/Artworks/Brands/Symbols/Webenv/render.conf +++ b/Artworks/Brands/Symbols/Webenv/render.conf @@ -7,5 +7,5 @@ render-from = "${TCAR_BASEDIR}/Artworks/Brands/Symbols/Webenv/centos.svgz" render-flow = "extended" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "ffffff" bgcolors = "ffffff-0" diff --git a/Artworks/Brands/Types/Default/message.svgz b/Artworks/Brands/Types/Default/message.svgz index d8ebf14..8ff9751 100644 Binary files a/Artworks/Brands/Types/Default/message.svgz and b/Artworks/Brands/Types/Default/message.svgz differ diff --git a/Artworks/Brands/Types/Default/render.conf b/Artworks/Brands/Types/Default/render.conf index cd554ff..6f8dde3 100644 --- a/Artworks/Brands/Types/Default/render.conf +++ b/Artworks/Brands/Types/Default/render.conf @@ -3,24 +3,26 @@ render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Default/centos.svgz" render-flow = "extended" formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +heights = "11 16 20 22 24 32 36 38 40 48 52 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [message.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Default/message.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +heights = "11 16 20 22 24 32 36 38 40 48 52 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [url.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Default/url.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +heights = "11 16 20 22 24 32 36 38 40 48 52 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" diff --git a/Artworks/Brands/Types/Default/url.svgz b/Artworks/Brands/Types/Default/url.svgz index 12eb2e8..c7207db 100644 Binary files a/Artworks/Brands/Types/Default/url.svgz and b/Artworks/Brands/Types/Default/url.svgz differ diff --git a/Artworks/Brands/Types/Numbers/0.svgz b/Artworks/Brands/Types/Numbers/0.svgz index 30a4796..4cadd9e 100644 Binary files a/Artworks/Brands/Types/Numbers/0.svgz and b/Artworks/Brands/Types/Numbers/0.svgz differ diff --git a/Artworks/Brands/Types/Numbers/1.svgz b/Artworks/Brands/Types/Numbers/1.svgz index 22738a5..b426b3e 100644 Binary files a/Artworks/Brands/Types/Numbers/1.svgz and b/Artworks/Brands/Types/Numbers/1.svgz differ diff --git a/Artworks/Brands/Types/Numbers/2.svgz b/Artworks/Brands/Types/Numbers/2.svgz index 945612d..108be63 100644 Binary files a/Artworks/Brands/Types/Numbers/2.svgz and b/Artworks/Brands/Types/Numbers/2.svgz differ diff --git a/Artworks/Brands/Types/Numbers/3.svgz b/Artworks/Brands/Types/Numbers/3.svgz index 600a8d0..fa094ff 100644 Binary files a/Artworks/Brands/Types/Numbers/3.svgz and b/Artworks/Brands/Types/Numbers/3.svgz differ diff --git a/Artworks/Brands/Types/Numbers/4.svgz b/Artworks/Brands/Types/Numbers/4.svgz index a09d77f..3171d36 100644 Binary files a/Artworks/Brands/Types/Numbers/4.svgz and b/Artworks/Brands/Types/Numbers/4.svgz differ diff --git a/Artworks/Brands/Types/Numbers/5.svgz b/Artworks/Brands/Types/Numbers/5.svgz index 257cf16..2e58f09 100644 Binary files a/Artworks/Brands/Types/Numbers/5.svgz and b/Artworks/Brands/Types/Numbers/5.svgz differ diff --git a/Artworks/Brands/Types/Numbers/6.svgz b/Artworks/Brands/Types/Numbers/6.svgz index a5775ad..a5c0020 100644 Binary files a/Artworks/Brands/Types/Numbers/6.svgz and b/Artworks/Brands/Types/Numbers/6.svgz differ diff --git a/Artworks/Brands/Types/Numbers/7.svgz b/Artworks/Brands/Types/Numbers/7.svgz index f330841..97a015f 100644 Binary files a/Artworks/Brands/Types/Numbers/7.svgz and b/Artworks/Brands/Types/Numbers/7.svgz differ diff --git a/Artworks/Brands/Types/Numbers/8.svgz b/Artworks/Brands/Types/Numbers/8.svgz index bd4e690..48f4e0c 100644 Binary files a/Artworks/Brands/Types/Numbers/8.svgz and b/Artworks/Brands/Types/Numbers/8.svgz differ diff --git a/Artworks/Brands/Types/Numbers/9.svgz b/Artworks/Brands/Types/Numbers/9.svgz index 8eb0d51..e13294a 100644 Binary files a/Artworks/Brands/Types/Numbers/9.svgz and b/Artworks/Brands/Types/Numbers/9.svgz differ diff --git a/Artworks/Brands/Types/Numbers/dot.svgz b/Artworks/Brands/Types/Numbers/dot.svgz index 6739124..9d165a0 100644 Binary files a/Artworks/Brands/Types/Numbers/dot.svgz and b/Artworks/Brands/Types/Numbers/dot.svgz differ diff --git a/Artworks/Brands/Types/Numbers/render.conf b/Artworks/Brands/Types/Numbers/render.conf index ccea04f..09d7522 100644 --- a/Artworks/Brands/Types/Numbers/render.conf +++ b/Artworks/Brands/Types/Numbers/render.conf @@ -2,97 +2,108 @@ render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/0.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [1.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/1.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [2.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/2.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [3.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/3.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [4.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/4.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [5.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/5.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [6.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/6.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [7.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/7.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [8.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/8.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [9.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/9.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" [dot.png] render-type = "svg" render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Numbers/dot.svgz" render-flow = "extended" +export-id = "CENTOSARTWORK" formats = "xpm pdf jpg tif" heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" bgcolors = "ffffff-0" diff --git a/Artworks/Brands/Types/Webenv/artwork.svgz b/Artworks/Brands/Types/Webenv/artwork.svgz new file mode 100644 index 0000000..6c38bb8 Binary files /dev/null and b/Artworks/Brands/Types/Webenv/artwork.svgz differ diff --git a/Artworks/Brands/Types/Webenv/bugs.svgz b/Artworks/Brands/Types/Webenv/bugs.svgz new file mode 100644 index 0000000..8ae8cd6 Binary files /dev/null and b/Artworks/Brands/Types/Webenv/bugs.svgz differ diff --git a/Artworks/Brands/Types/Webenv/centos.org.cu/artwork.svgz b/Artworks/Brands/Types/Webenv/centos.org.cu/artwork.svgz deleted file mode 100644 index 3c99931..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org.cu/artwork.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org.cu/bugs.svgz b/Artworks/Brands/Types/Webenv/centos.org.cu/bugs.svgz deleted file mode 100644 index bb2cb9b..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org.cu/bugs.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org.cu/centos.svgz b/Artworks/Brands/Types/Webenv/centos.org.cu/centos.svgz deleted file mode 100644 index 3372ffa..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org.cu/centos.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org.cu/lists.svgz b/Artworks/Brands/Types/Webenv/centos.org.cu/lists.svgz deleted file mode 100644 index 620c94c..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org.cu/lists.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org.cu/people.svgz b/Artworks/Brands/Types/Webenv/centos.org.cu/people.svgz deleted file mode 100644 index cf48081..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org.cu/people.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org.cu/render.conf b/Artworks/Brands/Types/Webenv/centos.org.cu/render.conf deleted file mode 100644 index 99bf1a5..0000000 --- a/Artworks/Brands/Types/Webenv/centos.org.cu/render.conf +++ /dev/null @@ -1,41 +0,0 @@ -# This file contains the information used to build The CentOS Logo in -# different sizes, colors and formats. - -[centos.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org.cu/centos.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" - -[centos-artwork.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org.cu/{centos,artwork}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-bugs.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org.cu/{centos,bugs}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-people.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org.cu/{centos,people}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" diff --git a/Artworks/Brands/Types/Webenv/centos.org/artwork.svgz b/Artworks/Brands/Types/Webenv/centos.org/artwork.svgz deleted file mode 100644 index 1c75af0..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org/artwork.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org/bugs.svgz b/Artworks/Brands/Types/Webenv/centos.org/bugs.svgz deleted file mode 100644 index 9118e72..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org/bugs.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org/centos.svgz b/Artworks/Brands/Types/Webenv/centos.org/centos.svgz deleted file mode 100644 index 870e8fd..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org/centos.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org/cranberry.svgz b/Artworks/Brands/Types/Webenv/centos.org/cranberry.svgz deleted file mode 100644 index 63911e3..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org/cranberry.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org/dasha.svgz b/Artworks/Brands/Types/Webenv/centos.org/dasha.svgz deleted file mode 100644 index 9d226fa..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org/dasha.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org/livecd.svgz b/Artworks/Brands/Types/Webenv/centos.org/livecd.svgz deleted file mode 100644 index 409924d..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org/livecd.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org/pandora.svgz b/Artworks/Brands/Types/Webenv/centos.org/pandora.svgz deleted file mode 100644 index df736e4..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org/pandora.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org/people.svgz b/Artworks/Brands/Types/Webenv/centos.org/people.svgz deleted file mode 100644 index 641bd0e..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org/people.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org/render.conf b/Artworks/Brands/Types/Webenv/centos.org/render.conf deleted file mode 100644 index f31e238..0000000 --- a/Artworks/Brands/Types/Webenv/centos.org/render.conf +++ /dev/null @@ -1,92 +0,0 @@ -# This file contains the information used to build The CentOS Logo in -# different sizes, colors and formats. - -[centos-artwork.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,artwork}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-bugs.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,bugs}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-cranberry.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,cranberry}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-dasha.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,dasha}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-livecd.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,livecd}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-pandora.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,pandora}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-people.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,people}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-wiki.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,wiki}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" - -[centos-xfs-support.png] -render-type = "svg" -render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.org/{centos,xfs-support}.svgz" -render-flow = "extended" -formats = "xpm pdf jpg tif" -heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" -fgcolors = "000000 ffffff" -bgcolors = "ffffff-0" -command = "/usr/bin/convert +append" diff --git a/Artworks/Brands/Types/Webenv/centos.org/wiki.svgz b/Artworks/Brands/Types/Webenv/centos.org/wiki.svgz deleted file mode 100644 index 8afac7a..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org/wiki.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.org/xfs-support.svgz b/Artworks/Brands/Types/Webenv/centos.org/xfs-support.svgz deleted file mode 100644 index 9250955..0000000 Binary files a/Artworks/Brands/Types/Webenv/centos.org/xfs-support.svgz and /dev/null differ diff --git a/Artworks/Brands/Types/Webenv/centos.svgz b/Artworks/Brands/Types/Webenv/centos.svgz new file mode 100644 index 0000000..8585b56 Binary files /dev/null and b/Artworks/Brands/Types/Webenv/centos.svgz differ diff --git a/Artworks/Brands/Types/Webenv/cranberry.svgz b/Artworks/Brands/Types/Webenv/cranberry.svgz new file mode 100644 index 0000000..125f19e Binary files /dev/null and b/Artworks/Brands/Types/Webenv/cranberry.svgz differ diff --git a/Artworks/Brands/Types/Webenv/dasha.svgz b/Artworks/Brands/Types/Webenv/dasha.svgz new file mode 100644 index 0000000..443bb38 Binary files /dev/null and b/Artworks/Brands/Types/Webenv/dasha.svgz differ diff --git a/Artworks/Brands/Types/Webenv/documentation.svgz b/Artworks/Brands/Types/Webenv/documentation.svgz new file mode 100644 index 0000000..25d9698 Binary files /dev/null and b/Artworks/Brands/Types/Webenv/documentation.svgz differ diff --git a/Artworks/Brands/Types/Webenv/livecd.svgz b/Artworks/Brands/Types/Webenv/livecd.svgz new file mode 100644 index 0000000..1dcacef Binary files /dev/null and b/Artworks/Brands/Types/Webenv/livecd.svgz differ diff --git a/Artworks/Brands/Types/Webenv/pandora.svgz b/Artworks/Brands/Types/Webenv/pandora.svgz new file mode 100644 index 0000000..7d57714 Binary files /dev/null and b/Artworks/Brands/Types/Webenv/pandora.svgz differ diff --git a/Artworks/Brands/Types/Webenv/people.svgz b/Artworks/Brands/Types/Webenv/people.svgz new file mode 100644 index 0000000..3d81773 Binary files /dev/null and b/Artworks/Brands/Types/Webenv/people.svgz differ diff --git a/Artworks/Brands/Types/Webenv/projects.svgz b/Artworks/Brands/Types/Webenv/projects.svgz new file mode 100644 index 0000000..46577e9 Binary files /dev/null and b/Artworks/Brands/Types/Webenv/projects.svgz differ diff --git a/Artworks/Brands/Types/Webenv/render.conf b/Artworks/Brands/Types/Webenv/render.conf new file mode 100644 index 0000000..948fd2a --- /dev/null +++ b/Artworks/Brands/Types/Webenv/render.conf @@ -0,0 +1,156 @@ +# This file contains the information used to build The CentOS Logo in +# different sizes, colors and formats. + +[centos.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/centos.svgz" +render-flow = "extended" +export-id = "CENTOSARTWORK" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[artwork.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/artwork.svgz" +render-flow = "extended" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[bugs.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/bugs.svgz" +render-flow = "extended" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[cranberry.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/cranberry.svgz" +render-flow = "extended" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[dasha.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/dasha.svgz" +render-flow = "extended" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[livecd.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/livecd.svgz" +render-flow = "extended" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[pandora.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/pandora.svgz" +render-flow = "extended" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[people.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/people.svgz" +render-flow = "extended" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[wiki.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/wiki.svgz" +render-flow = "extended" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[xfs-support.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/xfs-support.svgz" +render-flow = "extended" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[projects.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/projects.svgz" +render-flow = "extended" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[documentation.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/Types/Webenv/documentation.svgz" +render-flow = "extended" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[centos-5.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Types/Webenv/centos.svgz,Types/Numbers/5.svgz}" +render-flow = "extended" +export-id = "CENTOSARTWORK" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[centos-6.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Types/Webenv/centos.svgz,Types/Numbers/6.svgz}" +render-flow = "extended" +export-id = "CENTOSARTWORK" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" + +[centos-7.png] +render-type = "svg" +render-from = "${TCAR_BASEDIR}/Artworks/Brands/{Types/Webenv/centos.svgz,Types/Numbers/7.svgz}" +render-flow = "extended" +export-id = "CENTOSARTWORK" +formats = "xpm pdf jpg tif" +heights = "16 20 22 24 32 36 38 40 48 64 72 78 96 112 124 128 148 164 196 200 512" +fgcolors = "000000 ffffff ad7fa8 75507b 5c3566 729fcf 3465a4 204a87 fce94f edd400 c4a000 8ae234 73d216 4e9a06 fcaf3e f57900 ce5c00 e9b96e c17d11 8f5902 ef2929 cc0000 a40000 eeeeec d3d7cf babdb6 888a85 555753 2e3436" +bgcolors = "ffffff-0" +command = "/usr/bin/convert +append" diff --git a/Artworks/Brands/Types/Webenv/wiki.svgz b/Artworks/Brands/Types/Webenv/wiki.svgz new file mode 100644 index 0000000..0d6178b Binary files /dev/null and b/Artworks/Brands/Types/Webenv/wiki.svgz differ diff --git a/Artworks/Brands/Types/Webenv/xfs-support.svgz b/Artworks/Brands/Types/Webenv/xfs-support.svgz new file mode 100644 index 0000000..ceaedd2 Binary files /dev/null and b/Artworks/Brands/Types/Webenv/xfs-support.svgz differ diff --git a/Artworks/Documentation/Corporate/Locales/en_US/corporate-colors.svgz.po b/Artworks/Documentation/Corporate/Locales/en_US/corporate-colors.svgz.po new file mode 100644 index 0000000..af06926 --- /dev/null +++ b/Artworks/Documentation/Corporate/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/Artworks/Documentation/Corporate/Locales/en_US/corporate-fonts.svgz.po b/Artworks/Documentation/Corporate/Locales/en_US/corporate-fonts.svgz.po new file mode 100644 index 0000000..8547f34 --- /dev/null +++ b/Artworks/Documentation/Corporate/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/Artworks/Documentation/Corporate/Locales/en_US/corporate-logo-howto.svgz.po b/Artworks/Documentation/Corporate/Locales/en_US/corporate-logo-howto.svgz.po new file mode 100644 index 0000000..4e19922 --- /dev/null +++ b/Artworks/Documentation/Corporate/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/Artworks/Documentation/Corporate/Locales/en_US/corporate-symbol-howto-1of4.svgz.po b/Artworks/Documentation/Corporate/Locales/en_US/corporate-symbol-howto-1of4.svgz.po new file mode 100644 index 0000000..2f78c53 --- /dev/null +++ b/Artworks/Documentation/Corporate/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/Artworks/Documentation/Corporate/Locales/en_US/corporate-symbol-howto-2of4.svgz.po b/Artworks/Documentation/Corporate/Locales/en_US/corporate-symbol-howto-2of4.svgz.po new file mode 100644 index 0000000..175e4ce --- /dev/null +++ b/Artworks/Documentation/Corporate/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/Artworks/Documentation/Corporate/Locales/en_US/corporate-symbol-howto-3of4.svgz.po b/Artworks/Documentation/Corporate/Locales/en_US/corporate-symbol-howto-3of4.svgz.po new file mode 100644 index 0000000..cb099ab --- /dev/null +++ b/Artworks/Documentation/Corporate/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/Artworks/Documentation/Corporate/Locales/en_US/corporate-symbol-howto-4of4.svgz.po b/Artworks/Documentation/Corporate/Locales/en_US/corporate-symbol-howto-4of4.svgz.po new file mode 100644 index 0000000..e03dbd3 --- /dev/null +++ b/Artworks/Documentation/Corporate/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/Artworks/Documentation/Corporate/Locales/en_US/corporate-themes.svgz.po b/Artworks/Documentation/Corporate/Locales/en_US/corporate-themes.svgz.po new file mode 100644 index 0000000..4d414fc --- /dev/null +++ b/Artworks/Documentation/Corporate/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/Artworks/Documentation/Corporate/Locales/en_US/corporate.asciidoc.po b/Artworks/Documentation/Corporate/Locales/en_US/corporate.asciidoc.po index 1271ca3..b223b5a 100644 --- a/Artworks/Documentation/Corporate/Locales/en_US/corporate.asciidoc.po +++ b/Artworks/Documentation/Corporate/Locales/en_US/corporate.asciidoc.po @@ -1,8 +1,8 @@ msgid "" msgstr "" "Project-Id-Version: corporate.asciidoc 0.6\n" -"POT-Creation-Date: 2013-10-23 21:07-0400\n" -"PO-Revision-Date: 2013-10-23 21:07-0400\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" @@ -12,8 +12,44 @@ 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.png'; md5=THIS FILE DOESN'T EXIST" -msgstr "@@image: 'corporate.png'; md5=THIS FILE DOESN'T EXIST" +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" @@ -40,32 +76,31 @@ 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." +"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." +"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 Behaviour." +"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." +"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" @@ -77,272 +112,353 @@ 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." +"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 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 "" -"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 "" -"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 "" -"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." - -msgid "" -"Inside The CentOS Project we identify and apply 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.)." - -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 "" -"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." +"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." +"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." +"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:" +"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:" +"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, " +"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, " +"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 " -"essense of The CentOS Project existence.)." +"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.)." +"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.)." +"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.)." +"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." +"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." +"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." @@ -363,33 +479,29 @@ 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." +"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." +"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." +"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." +"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)." @@ -397,197 +509,360 @@ 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)." -msgid "Installation media (e.g., CDs, DVD, Pendrives)." +#, fuzzy +msgid "Installation media (e.g., CDs, DVD, Pen-drives)." msgstr "Installation media (e.g., CDs, DVD, Pendrives)." -msgid "Corporate Behaviour" +#, fuzzy +msgid "Corporate Behavior" msgstr "Corporate Behaviour" +#, fuzzy msgid "" -"The CentOS Project corporate behaviour is focused on the effective " +"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 " -"they way the organization projects itself to achieve it." +"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." +"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 behaviour takes place through The " -"CentOS Project corporate communication, as described above." +"The CentOS Project corporate behavior is based on a meritocracy (the more " +"you do the more you are allowed to do)." msgstr "" -"The CentOS Project corporate behaviour takes place through The " -"CentOS Project corporate communication, as described above." 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." - -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 "" -"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." - -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 "" -"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)?" - -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?" - -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 "" -"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." - -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 "" -"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." +"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/Artworks/Documentation/Corporate/Locales/en_US/corporate.svgz.po b/Artworks/Documentation/Corporate/Locales/en_US/corporate.svgz.po index c1d2621..18e78bb 100644 --- a/Artworks/Documentation/Corporate/Locales/en_US/corporate.svgz.po +++ b/Artworks/Documentation/Corporate/Locales/en_US/corporate.svgz.po @@ -1,8 +1,8 @@ msgid "" msgstr "" "Project-Id-Version: corporate.svgz 0.6\n" -"POT-Creation-Date: 2013-10-23 21:07-0400\n" -"PO-Revision-Date: 2013-10-23 21:07-0400\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" diff --git a/Artworks/Documentation/Corporate/corporate-clothes-head.svgz b/Artworks/Documentation/Corporate/corporate-clothes-head.svgz new file mode 100644 index 0000000..ac335c1 Binary files /dev/null and b/Artworks/Documentation/Corporate/corporate-clothes-head.svgz differ diff --git a/Artworks/Documentation/Corporate/corporate-clothes-torso.svgz b/Artworks/Documentation/Corporate/corporate-clothes-torso.svgz new file mode 100644 index 0000000..b042c8d Binary files /dev/null and b/Artworks/Documentation/Corporate/corporate-clothes-torso.svgz differ diff --git a/Artworks/Documentation/Corporate/corporate-colors.svgz b/Artworks/Documentation/Corporate/corporate-colors.svgz new file mode 100644 index 0000000..9ad2de4 Binary files /dev/null and b/Artworks/Documentation/Corporate/corporate-colors.svgz differ diff --git a/Artworks/Documentation/Corporate/corporate-fonts.svgz b/Artworks/Documentation/Corporate/corporate-fonts.svgz new file mode 100644 index 0000000..b612f4d Binary files /dev/null and b/Artworks/Documentation/Corporate/corporate-fonts.svgz differ diff --git a/Artworks/Documentation/Corporate/corporate-themes.svgz b/Artworks/Documentation/Corporate/corporate-themes.svgz new file mode 100644 index 0000000..618070c Binary files /dev/null and b/Artworks/Documentation/Corporate/corporate-themes.svgz differ diff --git a/Artworks/Documentation/Corporate/corporate.asciidoc b/Artworks/Documentation/Corporate/corporate.asciidoc index 752a283..8e3ef7a 100644 --- a/Artworks/Documentation/Corporate/corporate.asciidoc +++ b/Artworks/Documentation/Corporate/corporate.asciidoc @@ -17,7 +17,7 @@ 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 Behaviour. +Communication, and Corporate Behavior. [[corporate_identity]] .The CentOS Project Corporate Identity @@ -54,62 +54,177 @@ http://www.centos.org/modules/smartfaq/[FAQ]. Corporate Graphic Design ------------------------ -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. - -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. - -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. - -Inside The CentOS Project we identify and apply corporate design to the following -visual manifestations: - -- *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. - -- *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. - -- *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.). - -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. - -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. - +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 ----------------------- @@ -133,7 +248,7 @@ 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 - essense of The CentOS Project existence.). + essence of The CentOS Project existence.). - Release Schema (Lifetime) and all the stuff related (e.g., Release Notes, Documentation, Erratas, etc.). @@ -172,19 +287,20 @@ 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, Pendrives). +- Installation media (e.g., CDs, DVD, Pen-drives). -Corporate Behaviour +Corporate Behavior ------------------- -The CentOS Project corporate behaviour is focused on the effective + +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 they way the +to the sense of direction chosen by the organization and the way the organization projects itself to achieve it. -The CentOS Project corporate behaviour takes place through The CentOS -Project corporate communication, as described above. +The CentOS Project corporate behavior is based on a meritocracy (the +more you do the more you are allowed to do). Corporate Structure ------------------- @@ -209,19 +325,19 @@ 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 manifestions: The CentOS Distribution, The +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, 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. +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 concider all the 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 @@ -231,32 +347,24 @@ 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? - -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. - -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. +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/Artworks/Documentation/Corporate/render.conf b/Artworks/Documentation/Corporate/render.conf index 2f1cfbc..4978f22 100644 --- a/Artworks/Documentation/Corporate/render.conf +++ b/Artworks/Documentation/Corporate/render.conf @@ -5,6 +5,117 @@ 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" diff --git a/Artworks/Documentation/Fonts/dejavu-lgc.svgz b/Artworks/Documentation/Fonts/dejavu-lgc.svgz deleted file mode 100644 index 55fb02d..0000000 Binary files a/Artworks/Documentation/Fonts/dejavu-lgc.svgz and /dev/null differ diff --git a/Artworks/Documentation/Fonts/denmark.svgz b/Artworks/Documentation/Fonts/denmark.svgz deleted file mode 100644 index 2acea0f..0000000 Binary files a/Artworks/Documentation/Fonts/denmark.svgz and /dev/null differ diff --git a/Artworks/Documentation/Licenses/Locales/en_US/gfdl.asciidoc.po b/Artworks/Documentation/Licenses/Locales/en_US/gfdl.asciidoc.po new file mode 100644 index 0000000..7c9b686 --- /dev/null +++ b/Artworks/Documentation/Licenses/Locales/en_US/gfdl.asciidoc.po @@ -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/Artworks/Documentation/Licenses/Locales/en_US/gpl.asciidoc.po b/Artworks/Documentation/Licenses/Locales/en_US/gpl.asciidoc.po new file mode 100644 index 0000000..0a61c7a --- /dev/null +++ b/Artworks/Documentation/Licenses/Locales/en_US/gpl.asciidoc.po @@ -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/Artworks/Documentation/Licenses/Locales/es_ES/gfdl.asciidoc.po b/Artworks/Documentation/Licenses/Locales/es_ES/gfdl.asciidoc.po new file mode 100644 index 0000000..ada2c1b --- /dev/null +++ b/Artworks/Documentation/Licenses/Locales/es_ES/gfdl.asciidoc.po @@ -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/Artworks/Documentation/Licenses/Locales/es_ES/gpl.asciidoc.po b/Artworks/Documentation/Licenses/Locales/es_ES/gpl.asciidoc.po new file mode 100644 index 0000000..686864e --- /dev/null +++ b/Artworks/Documentation/Licenses/Locales/es_ES/gpl.asciidoc.po @@ -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/Artworks/Documentation/Licenses/gfdl.asciidoc b/Artworks/Documentation/Licenses/gfdl.asciidoc new file mode 100644 index 0000000..815a86c --- /dev/null +++ b/Artworks/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/Artworks/Documentation/Licenses/gpl.asciidoc b/Artworks/Documentation/Licenses/gpl.asciidoc new file mode 100644 index 0000000..19bc03f --- /dev/null +++ b/Artworks/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/Artworks/Documentation/Licenses/render.conf b/Artworks/Documentation/Licenses/render.conf new file mode 100644 index 0000000..a5d2d47 --- /dev/null +++ b/Artworks/Documentation/Licenses/render.conf @@ -0,0 +1,15 @@ +[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/Artworks/Documentation/Repository/DirStructure/dirStructure.svgz b/Artworks/Documentation/Repository/DirStructure/dirStructure.svgz deleted file mode 100644 index 7653a2e..0000000 Binary files a/Artworks/Documentation/Repository/DirStructure/dirStructure.svgz and /dev/null differ diff --git a/Artworks/Documentation/Repository/Infra/infra.svgz b/Artworks/Documentation/Repository/Infra/infra.svgz deleted file mode 100644 index 308a021..0000000 Binary files a/Artworks/Documentation/Repository/Infra/infra.svgz and /dev/null differ diff --git a/Artworks/Documentation/Repository/Locales/en_US/repository-infra.svgz.po b/Artworks/Documentation/Repository/Locales/en_US/repository-infra.svgz.po new file mode 100644 index 0000000..8da01ef --- /dev/null +++ b/Artworks/Documentation/Repository/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/Artworks/Documentation/Repository/Locales/en_US/repository-version-schema.svgz.po b/Artworks/Documentation/Repository/Locales/en_US/repository-version-schema.svgz.po new file mode 100644 index 0000000..b0df349 --- /dev/null +++ b/Artworks/Documentation/Repository/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/Artworks/Documentation/Repository/Locales/en_US/repository.asciidoc.po b/Artworks/Documentation/Repository/Locales/en_US/repository.asciidoc.po new file mode 100644 index 0000000..7ab6841 --- /dev/null +++ b/Artworks/Documentation/Repository/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/Artworks/Documentation/Repository/UserGuide/Asciidoc/Repository/centos-artwork.asciidoc b/Artworks/Documentation/Repository/UserGuide/Asciidoc/Repository/centos-artwork.asciidoc deleted file mode 100644 index e69de29..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Asciidoc/Repository/centos-artwork.asciidoc +++ /dev/null diff --git a/Artworks/Documentation/Repository/UserGuide/Asciidoc/Repository/centos-artwork.conf b/Artworks/Documentation/Repository/UserGuide/Asciidoc/Repository/centos-artwork.conf deleted file mode 100644 index e69de29..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Asciidoc/Repository/centos-artwork.conf +++ /dev/null diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-author.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-author.docbook deleted file mode 100644 index 3d8d6a9..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-author.docbook +++ /dev/null @@ -1,6 +0,0 @@ - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-copyright-holder.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-copyright-holder.docbook deleted file mode 100644 index ac998b8..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-copyright-holder.docbook +++ /dev/null @@ -1 +0,0 @@ -&TCP;. All rights reserved. diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-copyright-year.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-copyright-year.docbook deleted file mode 100644 index df9b499..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-copyright-year.docbook +++ /dev/null @@ -1 +0,0 @@ -YEAR diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-copyright.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-copyright.docbook deleted file mode 100644 index 78f0186..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-copyright.docbook +++ /dev/null @@ -1,4 +0,0 @@ - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-legalnotice.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-legalnotice.docbook deleted file mode 100644 index 5cb78bc..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-legalnotice.docbook +++ /dev/null @@ -1,10 +0,0 @@ - - - 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 . - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-revhistory-revision.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-revhistory-revision.docbook deleted file mode 100644 index 7b09a2c..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo-revhistory-revision.docbook +++ /dev/null @@ -1,8 +0,0 @@ - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo.docbook deleted file mode 100644 index 2cb60f9..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-bookinfo.docbook +++ /dev/null @@ -1,8 +0,0 @@ - - - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-subtitle.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-subtitle.docbook deleted file mode 100644 index b60a07e..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-subtitle.docbook +++ /dev/null @@ -1 +0,0 @@ -BOOKSUBTITLE diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-title.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-title.docbook deleted file mode 100644 index b54b481..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book-title.docbook +++ /dev/null @@ -1,2 +0,0 @@ -BOOKTITLE - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book.docbook deleted file mode 100644 index b447fc9..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book.docbook +++ /dev/null @@ -1,11 +0,0 @@ - - - - - - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book.ent b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book.ent deleted file mode 100644 index af62731..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Book.ent +++ /dev/null @@ -1,58 +0,0 @@ - - - - - - - - - - - - - - - - - - -&TC; Project"> - - - -&TC; Mirrors"> - - - - - - - -&TCA; Repository"> -&TCA; SIG"> - -The CentOS Artwork Repository User's Guide"> - -centos-artwork@centos.org mailing list"> -centos-devel@centos.org mailing list"> -centos-info@centos.org mailing list"> - - -&TC; Wiki"> -&TC; Mailing Lists"> - - - -"> -"> -"> -"> - -&TC; Documentation"> - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part-partintro.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part-partintro.docbook deleted file mode 100644 index c8467b4..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part-partintro.docbook +++ /dev/null @@ -1,3 +0,0 @@ - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part.docbook deleted file mode 100644 index 7f13f50..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part.docbook +++ /dev/null @@ -1,8 +0,0 @@ - - - PART_TITLE - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part/Chapter.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part/Chapter.docbook deleted file mode 100644 index 19f5bf7..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part/Chapter.docbook +++ /dev/null @@ -1,7 +0,0 @@ - - - CHAPTER_TITLE - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part/Chapter/section.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part/Chapter/section.docbook deleted file mode 100644 index 1ca0bd5..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Part/Chapter/section.docbook +++ /dev/null @@ -1,13 +0,0 @@ - - - SECTION_TITLE - - - Write the section content here. - - - - ... - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface.docbook deleted file mode 100644 index 42c8578..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface.docbook +++ /dev/null @@ -1,9 +0,0 @@ - - - Preface - - &preface-overview; - &preface-docconvs; - &preface-feedback; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface/docconvs.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface/docconvs.docbook deleted file mode 100644 index 17509ca..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface/docconvs.docbook +++ /dev/null @@ -1,225 +0,0 @@ -
- - Document Convenctions - - - In this manual, certain words are represented in different - fonts, typefaces, sizes, and weights. This highlighting is - systematic; different words are represented in the same style - to indicate their inclusion in a specific category. The types - of words that are represented this way include the - following: - - - - - command - - - Linux commands (and other operating system commands, when - used) are represented this way. This style should - indicate to you that you can type the word or phrase on - the command line and press Enter to - invoke a command. Sometimes a command contains words that - would be displayed in a different style on their own (such - as file names). In these cases, they are considered to be - part of the command, so the entire phrase is displayed as - a command. For example: - - - - Use the centos-art render - Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda - --filter="01-welcome" command to produce the first - slide image used by Anaconda in the branch 5 of &TCD; - using the version 4 of TreeFlower artistic motif. - - - - - - file name - - - File names, directory names, paths, and RPM package names - are represented this way. This style indicates that a - particular file or directory exists with that name on your - system. Examples: - - - - The init.sh file in Scripts/Bash/Cli/ - directory is the initialization script, written in Bash, - used to automate most of tasks in the repository. - - - - The centos-art command uses the - ImageMagick RPM package to convert - images from PNG format to other formats. - - - - - - key - - - A key on the keyboard is shown in this style. For - example: - - - - To use Tab completion to list particular - files in a directory, type ls, then a - character, and finally the Tab key. Your - terminal displays the list of files in the working - directory that begin with that character. - - - - - - keycombination - - - A combination of keystrokes is represented in this way. - For example: - - - - The CtrlAltBackspace - key combination exits your graphical session and returns - you to the graphical login screen or the console. - - - - - - computer output - - - Text in this style indicates text displayed to a shell - prompt such as error messages and responses to commands. - For example, the ls command displays - the contents of a directory using this style: - - - -render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh -render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh -render_getDirOutput.sh render.sh - - - - The output returned in response to the command (in this - case, the contents of the directory) is shown in this - style. - - - - - - prompt - - - A prompt, which is a computer's way of signifying that it - is ready for you to input something, is shown in this - style. Examples: - - - - - - $ - - - - - # - - - - - [centos@projects centos]$ - - - - - projects login: - - - - - - - - user input - - - Text that the user types, either on the command line or - into a text box on a GUI screen, is displayed in this - style. In the following example, - text is displayed in this style: To - boot your system into the text based installation program, - you must type in the text command - at the boot: prompt. - - - - - - replaceable - - - Text used in examples that is meant to be replaced with - data provided by the user is displayed in this style. In - the following example, - version-number is displayed in - this style: The directory for the kernel source is - /usr/src/kernels/version-number/, - where version-number is the - version and type of kernel installed on this system. - - - - - - Additionally, we use several different strategies to draw - your attention to certain pieces of information. In order of - urgency, these items are marked as a note, tip, important, - caution, or warning. For example: - - - Remember that Linux is case sensitive. In other words, a - rose is not a ROSE is not a rOsE. - - - - The directory /usr/share/doc/ contains - additional documentation for packages installed on your - system. - - - - If you modify the DHCP configuration file, the changes - do not take effect until you restart the DHCP daemon. - - - - Do not perform routine tasks as root — use a - regular user account unless you need to use the root account - for system administration tasks. - - - - Be careful to remove only the necessary partitions. - Removing other partitions could result in data loss or a - corrupted system environment. - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface/feedback.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface/feedback.docbook deleted file mode 100644 index 14cc875..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface/feedback.docbook +++ /dev/null @@ -1,43 +0,0 @@ -
- - Send In Your Feedback - - - &TCAR; is an ongoing work which might contain errors and - require new features. If you find errors inside &TCAR; or have - any suggestion, we want to know about it. - - - - To report errors and suggestions about &TCAR; you need to do - the following: - - - - - - Register yourself in the bug tracker. - - - - - Log in the bug tracker using your account. - - - - - Write a new ticket in the bug tracker using your account. - - - - - While you are writing your feedback report, please keep in - mind that it is very useful that you be specific about the - issue you are reporting in order for others be able of - reproducing it and, this way, find a solution for it. For - example, consider to include all the error messages you see in - your screen and the exact order of commands you used to - perform actions when using the centos-art.sh script. - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface/overview.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface/overview.docbook deleted file mode 100644 index 34d81db..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Book/Preface/overview.docbook +++ /dev/null @@ -1,13 +0,0 @@ -
- - Overview - - - Summarize, in a few paragraphs, what this book is all about. - - - - ... - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Licenses/Gfdl/gfdl.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Licenses/Gfdl/gfdl.docbook deleted file mode 100644 index 89b468a..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Licenses/Gfdl/gfdl.docbook +++ /dev/null @@ -1,608 +0,0 @@ - - - - - - GNU Free Documentation License - - Version 1.2, November 2002 - - Copyright © 2000, 2001, 2002 Free Software Foundation, - Inc. 675 Mass Ave, Cambridge, MA 02139, USA - - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - - - Preamble - - The purpose of this License is to make a manual, - textbook, or other functional and useful document - free in the sense of freedom: to assure - everyone the effective freedom to copy and redistribute it, - with or without modifying it, either commercially or - noncommercially. Secondarily, this License preserves for the - author and publisher a way to get credit for their work, while - not being considered responsible for modifications made by - others. - - This License is a kind of copyleft, which - means that derivative works of the document must themselves be - free in the same sense. It complements the , which is a copyleft license - designed for free software. - - We have designed this License in order to use it for - manuals for free software, because free software needs free - documentation: a free program should come with manuals - providing the same freedoms that the software does. But this - License is not limited to software manuals; it can be used for - any textual work, regardless of subject matter or whether it - is published as a printed book. We recommend this License - principally for works whose purpose is instruction or - reference. - - - - - - Applicability and definitions - - This License applies to any manual or other work, in any - medium, that contains a notice placed by the copyright holder - saying it can be distributed under the terms of this License. - Such a notice grants a world-wide, royalty-free license, - unlimited in duration, to use that work under the conditions - stated herein. The Document, below, refers to - any such manual or work. Any member of the public is a - licensee, and is addressed as you. You accept - the license if you copy, modify or distribute the work in a - way requiring permission under copyright law. - - A - Modified Version of the Document means any work - containing the Document or a portion of it, either copied - verbatim, or with modifications and/or translated into another - language. - - A - Secondary Section is a named appendix or a - front-matter section of the Document that deals exclusively - with the relationship of the publishers or authors of the - Document to the Document's overall subject (or to related - matters) and contains nothing that could fall directly within - that overall subject. (Thus, if the Document is in part a - textbook of mathematics, a may not explain any mathematics.) The relationship could be - a matter of historical connection with the subject or with - related matters, or of legal, commercial, philosophical, - ethical or political position regarding them. - - The Invariant Sections are certain - whose titles are - designated, as being those of Invariant Sections, in the - notice that says that the Document is released under this - License. If a section does not fit the above definition of - Secondary then it is not allowed to be designated as - Invariant. The Document may contain zero Invariant Sections. - If the Document does not identify any Invariant Section then - there are none. - - The - Cover Texts are certain short passages of text - that are listed, as Front-Cover Texts or Back-Cover Texts, in - the notice that says that the Document is released under this - License. A Front-Cover Text may be at most 5 words, and a - Back-Cover Text may be at most 25 words. - - A - Transparent copy of the Document means a - machine-readable copy, represented in a format whose - specification is available to the general public, that is - suitable for revising the document straightforwardly with - generic text editors or (for images composed of pixels) - generic paint programs or (for drawings) some widely available - drawing editor, and that is suitable for input to text - formatters or for automatic translation to a variety of - formats suitable for input to text formatters. A copy made in - an otherwise file format whose - markup, or absence of markup, has been arranged to thwart or - discourage subsequent modification by readers is not . An image format is not if used for any substantial amount of - text. A copy that is not is called Opaque. - - Examples of suitable formats for copies - include plain ASCII without markup, Texinfo input format, - LaTeX input format, SGML or XML using a publicly available - DTD, and standard-conforming simple HTML, PostScript or PDF - designed for human modification. Examples of transparent - image formats include PNG, XCF and JPG. Opaque formats - include proprietary formats that can be read and edited only - by proprietary word processors, SGML or XML for which the DTD - and/or processing tools are not generally available, and the - machine-generated HTML, PostScript or PDF produced by some - word processors for output purposes only. - - The Title - Page means, for a printed book, the title page itself, - plus such following pages as are needed to hold, legibly, the - material this License requires to appear in the title page. - For works in formats which do not have any title page as such, - Title Page means the text near the most - prominent appearance of the work's title, preceding the - beginning of the body of the text. - - A section Entitled XYZ means a named - subunit of the Document whose title either is precisely XYZ or - contains XYZ in parentheses following text that translates XYZ - in another language. (Here XYZ stands for a specific section - name mentioned below, such as Acknowledgements, - Dedications, Endorsements, or - History.) To Preserve the Title - of such a section when you modify the Document means that it - remains a section Entitled XYZ according to - this definition. - - The Document may include Warranty Disclaimers next to - the notice which states that this License applies to the - Document. These Warranty Disclaimers are considered to be - included by reference in this License, but only as regards - disclaiming warranties: any other implication that these - Warranty Disclaimers may have is void and has no effect on the - meaning of this License. - - - - - - Verbatim copying - - You may copy and distribute the Document in any medium, - either commercially or noncommercially, provided that this - License, the copyright notices, and the license notice saying - this License applies to the Document are reproduced in all - copies, and that you add no other conditions whatsoever to - those of this License. You may not use technical measures to - obstruct or control the reading or further copying of the - copies you make or distribute. However, you may accept - compensation in exchange for copies. If you distribute a - large enough number of copies you must also follow the - conditions in section . - - You may also lend copies, under the same conditions - stated above, and you may publicly display copies. - - - - - - Copying in quantity - - If you publish printed copies (or copies in media that - commonly have printed covers) of the Document, numbering more - than 100, and the Document's license notice requires Cover - Texts, you must enclose the copies in covers that carry, - clearly and legibly, all these : - Front-Cover Texts on the front cover, and Back-Cover Texts on - the back cover. Both covers must also clearly and legibly - identify you as the publisher of these copies. The front - cover must present the full title with all words of the title - equally prominent and visible. You may add other material on - the covers in addition. Copying with changes limited to the - covers, as long as they preserve the title of the Document and - satisfy these conditions, can be treated as verbatim copying - in other respects. - - If the required texts for either cover are too - voluminous to fit legibly, you should put the first ones - listed (as many as fit reasonably) on the actual cover, and - continue the rest onto adjacent pages. - - If you publish or distribute Opaque copies of the - Document numbering more than 100, you must either include a - machine-readable copy along with each Opaque copy, - or state in or with each Opaque copy a computer-network - location from which the general network-using public has - access to download using public-standard network protocols a - complete copy of the Document, free of added - material. If you use the latter option, you must take - reasonably prudent steps, when you begin distribution of - Opaque copies in quantity, to ensure that this - copy will remain thus accessible at the stated location until - at least one year after the last time you distribute an Opaque - copy (directly or through your agents or retailers) of that - edition to the public. - - It is requested, but not required, that you contact the - authors of the Document well before redistributing any large - number of copies, to give them a chance to provide you with an - updated version of the Document. - - - - - - Modifications - - - You may copy and distribute a of the Document under the - conditions of sections and above, provided that - you release the under - precisely this License, with the filling the role of the - Document, thus licensing distribution and modification of - the to whoever - possesses a copy of it. In addition, you must do these - things in the : - - - - - - Use in the (and on - the covers, if any) a title distinct from that of the - Document, and from those of previous versions (which - should, if there were any, be listed in the History - section of the Document). You may use the same title - as a previous version if the original publisher of - that version gives permission. - - - List on the , as - authors, one or more persons or entities responsible - for authorship of the modifications in the , together with at least - five of the principal authors of the Document (all of - its principal authors, if it has fewer than five), - unless they release you from this requirement. - - - - State on the the - name of the publisher of the , as the - publisher. - - - - Preserve all the copyright notices of the - Document. - - - - Add an appropriate copyright notice for your - modifications adjacent to the other copyright - notices. - - - - Include, immediately after the copyright - notices, a license notice giving the public permission - to use the under the terms of this - License, in the form shown in the Addendum - below. - - - - Preserve in that license notice the full lists - of and required - given in the Document's - license notice. - - - - Include an unaltered copy of this License. - - - - Preserve the section Entitled - History, Preserve its Title, and add to - it an item stating at least the title, year, new - authors, and publisher of the as given on the . If there is no section - Entitled History in the Document, create - one stating the title, year, authors, and publisher of - the Document as given on its , then add an item describing the as stated in the previous - sentence. - - - - Preserve the network location, if any, given in - the Document for public access to a copy of the Document, and - likewise the network locations given in the Document - for previous versions it was based on. These may be - placed in the History section. You may - omit a network location for a work that was published - at least four years before the Document itself, or if - the original publisher of the version it refers to - gives permission. - - - - For any section Entitled - Acknowledgements or - Dedications, Preserve the Title of the - section, and preserve in the section all the substance - and tone of each of the contributor acknowledgements - and/or dedications given therein. - - - - Preserve all the of the Document, - unaltered in their text and in their titles. Section - numbers or the equivalent are not considered part of - the section titles. - - - - Delete any section Entitled - Endorsements. Such a section may not - be included in the . - - - - Do not retitle any existing section to be - Entitled Endorsements or to conflict in - title with any . - - - Preserve any Warranty Disclaimers. - - - - - If the includes new - front-matter sections or appendices that qualify as and contain no material - copied from the Document, you may at your option designate - some or all of these sections as invariant. To do this, - add their titles to the list of in the 's license notice. These - titles must be distinct from any other section - titles. - - - - You may add a section Entitled - Endorsements, provided it contains nothing - but endorsements of your by various parties–for example, statements of - peer review or that the text has been approved by an - organization as the authoritative definition of a - standard. - - - - You may add a passage of up to five words as a Front-Cover - Text, and a passage of up to 25 words as a Back-Cover - Text, to the end of the list of in the . Only one passage of - Front-Cover Text and one of Back-Cover Text may be added - by (or through arrangements made by) any one entity. If - the Document already includes a cover text for the same - cover, previously added by you or by arrangement made by - the same entity you are acting on behalf of, you may not - add another; but you may replace the old one, on explicit - permission from the previous publisher that added the old - one. - - - - The author(s) and publisher(s) of the Document do not by - this License give permission to use their names for - publicity for or to assert or imply endorsement of any - . - - - - - - - Combining documents - - You may combine the Document with other documents - released under this License, under the terms defined in - section above for - modified versions, provided that you include in the - combination all of the of - all of the original documents, unmodified, and list them all - as of your combined work - in its license notice, and that you preserve all their - Warranty Disclaimers. - - The combined work need only contain one copy of this - License, and multiple identical may be replaced with a single - copy. If there are multiple with the same name but - different contents, make the title of each such section unique - by adding at the end of it, in parentheses, the name of the - original author or publisher of that section if known, or else - a unique number. Make the same adjustment to the section - titles in the list of in - the license notice of the combined work. - - In the combination, you must combine any sections - Entitled History in the various original - documents, forming one section Entitled - History; likewise combine any sections Entitled - Acknowledgements, and any sections Entitled - Dedications. You must delete all sections - Entitled Endorsements. - - - - - - Collection of documents - - You may make a collection consisting of the Document and - other documents released under this License, and replace the - individual copies of this License in the various documents - with a single copy that is included in the collection, - provided that you follow the rules of this License for - verbatim copying of each of the documents in all other - respects. - - You may extract a single document from such a - collection, and distribute it individually under this License, - provided you insert a copy of this License into the extracted - document, and follow this License in all other respects - regarding verbatim copying of that document. - - - - - - Aggregation with independent works - - A compilation of the Document or its derivatives with - other separate and independent documents or works, in or on a - volume of a storage or distribution medium, is called an - aggregate if the copyright resulting from the - compilation is not used to limit the legal rights of the - compilation's users beyond what the individual works permit. - When the Document is included in an aggregate, this License - does not apply to the other works in the aggregate which are - not themselves derivative works of the Document. - - If the Cover Text requirement of section is applicable to these - copies of the Document, then if the Document is less than one - half of the entire aggregate, the Document's may be placed on covers that bracket - the Document within the aggregate, or the electronic - equivalent of covers if the Document is in electronic form. - Otherwise they must appear on printed covers that bracket the - whole aggregate. - - - - - - Translations - - Translation is considered a kind of modification, so you - may distribute translations of the Document under the terms of - section . Replacing - with translations - requires special permission from their copyright holders, but - you may include translations of some or all in addition to the original - versions of these . You - may include a translation of this License, and all the license - notices in the Document, and any Warranty Disclaimers, - provided that you also include the original English version of - this License and the original versions of those notices and - disclaimers. In case of a disagreement between the - translation and the original version of this License or a - notice or disclaimer, the original version will - prevail. - - If a section in the Document is Entitled - Acknowledgements, Dedications, - or History, the requirement (section ) to Preserve its Title - (section ) will - typically require changing the actual title. - - - - - - Termination - - You may not copy, modify, sublicense, or distribute the - Document except as expressly provided for under this License. - Any other attempt to copy, modify, sublicense or distribute - the Document is void, and will automatically terminate your - rights under this License. However, parties who have received - copies, or rights, from you under this License will not have - their licenses terminated so long as such parties remain in - full compliance. - - - - - - Future Revisions of this License - - The Free Software Foundation may publish new, revised - versions of the GNU Free Documentation License from time to - time. Such new versions will be similar in spirit to the - present version, but may differ in detail to address new - problems or concerns. See . - - Each version of the License is given a distinguishing - version number. If the Document specifies that a particular - numbered version of this License or any later - version applies to it, you have the option of - following the terms and conditions either of that specified - version or of any later version that has been published (not - as a draft) by the Free Software Foundation. If the Document - does not specify a version number of this License, you may - choose any version ever published (not as a draft) by the Free - Software Foundation. - - - - - - How to use this License for your documents - - To use this License in a document you have written, - include a copy of the License in the document and put the - following copyright and license notices just after the title - page: - - -Copyright (C) YEAR YOUR NAME. - -Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, -Version 1.2 or any later version published by the Free Software -Foundation; with no Invariant Sections, no Front-Cover Texts, and -no Back-Cover Texts. A copy of the license is included in the -section entitled GNU Free Documentation License. - - - If you have , - Front-Cover Texts and Back-Cover Texts, replace the - with...Texts. line with this: - - -with the Invariant Sections being LIST THEIR TITLES, with the -Front-Cover Texts being LIST, and with the Back-Cover Texts being -LIST. - - - If you have - without , or some other - combination of the three, merge those two alternatives to suit - the situation. - - If your document contains nontrivial examples of program - code, we recommend releasing these examples in parallel under - your choice of free software license, such as the GNU General - Public License, to permit their use in free software. - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Licenses/Gpl/gpl.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Licenses/Gpl/gpl.docbook deleted file mode 100644 index 7394198..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Default/Licenses/Gpl/gpl.docbook +++ /dev/null @@ -1,539 +0,0 @@ - - - - - GNU General Public License - - - Version 2, June 1991 - - - - Copyright © 1989, 1991 Free Software Foundation, Inc. - 675 Mass Ave, Cambridge, MA 02139, USA - - - - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not - allowed. - - - - - Preamble - - - The licenses for most software are designed to take away your - freedom to share and change it. By contrast, the GNU General - Public License is intended to guarantee your freedom to share - and change free software–to make sure the software is - free for all its users. This General Public License applies - to most of the Free Software Foundation's software and to any - other program whose authors commit to using it. (Some other - Free Software Foundation software is covered by the GNU - Library General Public License instead.) You can apply it to - your programs, too. - - - - When we speak of free software, we are referring to freedom, - not price. Our General Public Licenses are designed to make - sure that you have the freedom to distribute copies of free - software (and charge for this service if you wish), that you - receive source code or can get it if you want it, that you can - change the software or use pieces of it in new free programs; - and that you know you can do these things. - - - - To protect your rights, we need to make restrictions that - forbid anyone to deny you these rights or to ask you to - surrender the rights. These restrictions translate to certain - responsibilities for you if you distribute copies of the - software, or if you modify it. - - - - For example, if you distribute copies of such a program, - whether gratis or for a fee, you must give the recipients all - the rights that you have. You must make sure that they, too, - receive or can get the source code. And you must show them - these terms so they know their rights. - - - - We protect your rights with two steps: - - - - - copyright the software, and - - - offer you this license which gives you legal - permission to copy, distribute and/or modify the - software. - - - - - Also, for each author's protection and ours, we want to make - certain that everyone understands that there is no warranty - for this free software. If the software is modified by - someone else and passed on, we want its recipients to know - that what they have is not the original, so that any problems - introduced by others will not reflect on the original authors' - reputations. - - - - Finally, any free program is threatened constantly by software - patents. We wish to avoid the danger that redistributors of a - free program will individually obtain patent licenses, in - effect making the program proprietary. To prevent this, we - have made it clear that any patent must be licensed for - everyone's free use or not licensed at all. - - - - The precise terms and conditions for copying, distribution and - modification follow. - - - - - - - Terms and Conditions for Copying, Distribution and Modification - - - - Section 1 - - - You may copy and distribute verbatim copies of the Program's - source code as you receive it, in any medium, provided that - you conspicuously and appropriately publish on each copy an - appropriate copyright notice and disclaimer of warranty; keep - intact all the notices that refer to this License and to the - absence of any warranty; and give any other recipients of the - Program a copy of this License along with the Program. - - - - You may charge a fee for the physical act of transferring a - copy, and you may at your option offer warranty protection in - exchange for a fee. - - - - - - - Section 2 - - - You may modify your copy or copies of the Program or any - portion of it, thus forming a work based on the Program, and - copy and distribute such modifications or work under the terms - of above, provided that - you also meet all of these conditions: - - - - - - You must cause the modified files to carry prominent notices - stating that you changed the files and the date of any - change. - - - - - You must cause any work that you distribute or publish, that - in whole or in part contains or is derived from the Program or - any part thereof, to be licensed as a whole at no charge to - all third parties under the terms of this License. - - - - - If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display - an announcement including an appropriate copyright notice and - a notice that there is no warranty (or else, saying that you - provide a warranty) and that users may redistribute the - program under these conditions, and telling the user how to - view a copy of this License. - - - - - - Exception - - If the Program itself is interactive but does not normally - print such an announcement, your work based on the Program is - not required to print an announcement. - - - - - These requirements apply to the modified work as a whole. If - identifiable sections of that work are not derived from the - Program, and can be reasonably considered independent and - separate works in themselves, then this License, and its - terms, do not apply to those sections when you distribute them - as separate works. But when you distribute the same sections - as part of a whole which is a work based on the Program, the - distribution of the whole must be on the terms of this - License, whose permissions for other licensees extend to the - entire whole, and thus to each and every part regardless of - who wrote it. - - - - Thus, it is not the intent of this section to claim rights or - contest your rights to work written entirely by you; rather, - the intent is to exercise the right to control the - distribution of derivative or collective works based on the - Program. - - - - In addition, mere aggregation of another work not based on the - Program with the Program (or with a work based on the Program) - on a volume of a storage or distribution medium does not bring - the other work under the scope of this License. - - - - - - - Section 3 - - - You may copy and distribute the Program (or a work based on - it, under ) in object code - or executable form under the terms of and above provided that you also do - one of the following: - - - - - - Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of - and above on a medium customarily - used for software interchange; or, - - - - - - Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of and above on a medium customarily - used for software interchange; or, - - - - - - Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with - such an offer, in accord with Subsection b above.) - - - - - - The source code for a work means the preferred form of the - work for making modifications to it. For an executable work, - complete source code means all the source code for all modules - it contains, plus any associated interface definition files, - plus the scripts used to control compilation and installation - of the executable. However, as a special exception, the - source code distributed need not include anything that is - normally distributed (in either source or binary form) with - the major components (compiler, kernel, and so on) of the - operating system on which the executable runs, unless that - component itself accompanies the executable. - - - - If distribution of executable or object code is made by - offering access to copy from a designated place, then offering - equivalent access to copy the source code from the same place - counts as distribution of the source code, even though third - parties are not compelled to copy the source along with the - object code. - - - - - - - Section 4 - - - You may not copy, modify, sublicense, or distribute the - Program except as expressly provided under this License. Any - attempt otherwise to copy, modify, sublicense or distribute - the Program is void, and will automatically terminate your - rights under this License. However, parties who have received - copies, or rights, from you under this License will not have - their licenses terminated so long as such parties remain in - full compliance. - - - - - - - Section 5 - - - You are not required to accept this License, since you have - not signed it. However, nothing else grants you permission to - modify or distribute the Program or its derivative works. - These actions are prohibited by law if you do not accept this - License. Therefore, by modifying or distributing the Program - (or any work based on the Program), you indicate your - acceptance of this License to do so, and all its terms and - conditions for copying, distributing or modifying the Program - or works based on it. - - - - - - - Section 6 - - Each time you redistribute the Program (or any work based on - the Program), the recipient automatically receives a license from - the original licensor to copy, distribute or modify the Program - subject to these terms and conditions. You may not impose any - further restrictions on the recipients' exercise of the rights - granted herein. You are not responsible for enforcing compliance - by third parties to this License. - - - - - - Section 7 - - If, as a consequence of a court judgment or allegation of - patent infringement or for any other reason (not limited to patent - issues), conditions are imposed on you (whether by court order, - agreement or otherwise) that contradict the conditions of this - License, they do not excuse you from the conditions of this - License. If you cannot distribute so as to satisfy simultaneously - your obligations under this License and any other pertinent - obligations, then as a consequence you may not distribute the - Program at all. For example, if a patent license would not permit - royalty-free redistribution of the Program by all those who - receive copies directly or indirectly through you, then the only - way you could satisfy both it and this License would be to refrain - entirely from distribution of the Program. - - If any portion of this section is held invalid or - unenforceable under any particular circumstance, the balance of - the section is intended to apply and the section as a whole is - intended to apply in other circumstances. - - It is not the purpose of this section to induce you to - infringe any patents or other property right claims or to contest - validity of any such claims; this section has the sole purpose of - protecting the integrity of the free software distribution system, - which is implemented by public license practices. Many people - have made generous contributions to the wide range of software - distributed through that system in reliance on consistent - application of that system; it is up to the author/donor to decide - if he or she is willing to distribute software through any other - system and a licensee cannot impose that choice. - - This section is intended to make thoroughly clear what is - believed to be a consequence of the rest of this License. - - - - - - Section 8 - - If the distribution and/or use of the Program is restricted - in certain countries either by patents or by copyrighted - interfaces, the original copyright holder who places the Program - under this License may add an explicit geographical distribution - limitation excluding those countries, so that distribution is - permitted only in or among countries not thus excluded. In such - case, this License incorporates the limitation as if written in - the body of this License. - - - - - - Section 9 - - The Free Software Foundation may publish revised and/or new - versions of the General Public License from time to time. Such - new versions will be similar in spirit to the present version, but - may differ in detail to address new problems or concerns. - - Each version is given a distinguishing version number. If - the Program specifies a version number of this License which - applies to it and any later version, you have the - option of following the terms and conditions either of that - version or of any later version published by the Free Software - Foundation. If the Program does not specify a version number of - this License, you may choose any version ever published by the - Free Software Foundation. - - - - - - Section 10 - - If you wish to incorporate parts of the Program into other - free programs whose distribution conditions are different, write - to the author to ask for permission. For software which is - copyrighted by the Free Software Foundation, write to the Free - Software Foundation; we sometimes make exceptions for this. Our - decision will be guided by the two goals of preserving the free - status of all derivatives of our free software and of promoting - the sharing and reuse of software generally. - - - - - - NO WARRANTY - Section 11 - - BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO - WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE - LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT - HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM AS IS WITHOUT - WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT - NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND - FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE - QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE - PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY - SERVICING, REPAIR OR CORRECTION. - - - - - - Section 12 - - IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO - IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY - MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE - LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, - INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR - INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF - DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU - OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY - OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - - End of Terms and Conditions. - - - - - - - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of - the greatest possible use to the public, the best way to - achieve this is to make it free software which everyone can - redistribute and change under these terms. - - To do so, attach the following notices to the program. - It is safest to attach them to the start of each source file - to most effectively convey the exclusion of warranty; and each - file should have at least the copyright line - and a pointer to where the full notice is found. - - -<one line to give the program's name and a brief idea of what it does.> -Copyright (C) 19yy <name of author> - -This program is free software; you can redistribute it and/or modify -it under the terms of the GNU General Public License as published by -the Free Software Foundation; either version 2 of the License, or -(at your option) any later version. - -This program is distributed in the hope that it will be useful, -but WITHOUT ANY WARRANTY; without even the implied warranty of -MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -GNU General Public License for more details. - -You should have received a copy of the GNU General Public License -along with this program; if not, write to the Free Software -Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. - - - Also add information on how to contact you by electronic - and paper mail. - - If the program is interactive, make it output a short - notice like this when it starts in an interactive mode: - - -Gnomovision version 69, Copyright (C) 19yy name of author -Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. -This is free software, and you are welcome to redistribute it -under certain conditions; type `show c' for details. - - - The hypothetical commands `show w' and `show c' should - show the appropriate parts of the General Public License. Of - course, the commands you use may be called something other - than `show w' and `show c'; they could even be mouse-clicks or - menu items–whatever suits your program. - - You should also get your employer (if you work as a - programmer) or your school, if any, to sign a copyright - disclaimer for the program, if necessary. Here is a - sample; alter the names: - - -Yoyodyne, Inc., hereby disclaims all copyright interest in the program -`Gnomovision' (which makes passes at compilers) written by James Hacker. - -<signature of Ty Coon>, 1 April 1989 -Ty Coon, President of Vice - - - This General Public License does not permit - incorporating your program into proprietary programs. If your - program is a subroutine library, you may consider it more - useful to permit linking proprietary applications with the - library. If this is what you want to do, use the GNU Library - General Public License instead of this License. - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity.docbook deleted file mode 100644 index d36b086..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity.docbook +++ /dev/null @@ -1,17 +0,0 @@ - - - Corporate Visual Identity - - - - ... - - - - &identity-project; - &identity-brand; - &identity-distro; - &identity-web; - &identity-showroom; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity.ent b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity.ent deleted file mode 100644 index 144c375..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity.ent +++ /dev/null @@ -1,19 +0,0 @@ - - - - - - - - - - - - - - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand.docbook deleted file mode 100644 index 0c0ba19..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand.docbook +++ /dev/null @@ -1,11 +0,0 @@ - - - The CentOS Brand - - &identity-brand-intro; - &identity-brand-symbol; - &identity-brand-type; - &identity-brand-logo; - &identity-brand-motif; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/intro.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/intro.docbook deleted file mode 100644 index 84a602a..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/intro.docbook +++ /dev/null @@ -1,49 +0,0 @@ - - - Introduction - - - &TCBRAND; is the main visual manifestaion of &TCP;. &TCP; - uses &TCBRAND; to connect all the visual manifestions it is - made of (e.g., GNU/Linux Distributions, Web sites, Stationery, - etc.) and, this way, provides recognition - - - ... just as a GPG signature might do for RPM packages. - - - among similar projects available on the Internet. The CentOS - Brand is made of a graphical component (&TCSYMBOL;) and a - typographical component (&TCTYPE;) that, when put together, - make &TCLOGO;. The components that make &TCBRAND; can be used - together or separately, considering that, in hierarchy order, - &TCLOGO; is rather prefered than &TCSYMBOL;, as well as - &TCSYMBOL; is rather prefered than &TCTYPE;. - - - - In addition to those components mentioned above, &TCBRAND; - includes another component named &TCMOTIF;. &TCMOTIF; is - mainly used as background on images and is directly related to - the look and feel of all visual manifestations &TCP; shows its - existence on. In contrast with &TCLOGO;, &TCSYMBOL; and - &TCTYPE;; &TCMOTIF; might change from time to time providing a - vehicle to refresh how &TCP; looks and feels. - - - - &TCBRAND; and all the visual manifestations derivated from it - are available for you to study and propose improvement around - a good citizen's will inside &TCC;, but you are not allowed to - redistribute them elsewhere, without the given permission of - &TCP;. - - - - If you need to redistribute either &TCLOGO; or any visual - manifestation derived from it, write your intentions to the - The CentOS Developers mailing list (centos-devel@centos.org). - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/logo.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/logo.docbook deleted file mode 100644 index ee01fda..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/logo.docbook +++ /dev/null @@ -1,17 +0,0 @@ - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/motif.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/motif.docbook deleted file mode 100644 index 7341757..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/motif.docbook +++ /dev/null @@ -1,5 +0,0 @@ - - The CentOS Motif - ... - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/symbol.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/symbol.docbook deleted file mode 100644 index 7ddeb03..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/symbol.docbook +++ /dev/null @@ -1,15 +0,0 @@ - - - &TCS; - - - &TCS; is the graphical part of &TCL;. As &TCL;, &TCS; is used - to brand images produced by &TCP; and provide a - visual connection between images so they can be monolithically - recognized as part of &TCP;. &TCS; 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. - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/type.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/type.docbook deleted file mode 100644 index d76106b..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Brand/type.docbook +++ /dev/null @@ -1,17 +0,0 @@ - - - &TCT; - - - &TCT; is the typographical part of &TCL;. Comparing with both - &TCL; and &TCS;, &TCT; by its own, provides poor visual - connection between images that intend to be recognized as a - monolithic part of &TCP; and shouldn't be used alone. - Instead, &TCL; or &TCS; are preferred. &TCS; 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. - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Distribution.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Distribution.docbook deleted file mode 100644 index 0236910..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Distribution.docbook +++ /dev/null @@ -1,16 +0,0 @@ - - - The CentOS Distribution - ... - - - Release Schema - ... - - - - ... - ... - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project.docbook deleted file mode 100644 index 3634415..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project.docbook +++ /dev/null @@ -1,41 +0,0 @@ - - - The CentOS Project - - - 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 Behaviour. - - -
- The CentOS Project Corporate Identity. - - The CentOS Project Corporate Identity. - - - - - - -
- - &identity-project-mission; - &identity-project-design; - &identity-project-communication; - &identity-project-behaviour; - &identity-project-structure; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/behaviour.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/behaviour.docbook deleted file mode 100755 index bd22f04..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/behaviour.docbook +++ /dev/null @@ -1,21 +0,0 @@ - - - Corporate Behaviour - - - &TCP; 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. - - - - &TCP; corporate behaviour takes place through &TCP; corporate - communication, as described in . - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/communication.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/communication.docbook deleted file mode 100755 index c46dd12..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/communication.docbook +++ /dev/null @@ -1,141 +0,0 @@ - - - Corporate Communication - - - &TCP; 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. - - - - &TCP; corporate communication takes place through the - following visual manifestations: - - - - - - &TCD; - - - 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 &TCP; - 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 essense of &TCP; existence.). - - - - - Release Schema (Lifetime) and all the stuff related (e.g., - Release Notes, Documentation, Erratas, etc.). - - - - - - - - &TCW; - - - 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 - contraditions when they all are put together. Removing - these visual contraditions 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. - - - - - - - - &TCS; - - - This visual manifestation communicates its existence - through production of industrial objects carrying &TCBRAND;. - 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 - &TCP; 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, Pendrives). - - - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/design.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/design.docbook deleted file mode 100755 index 7429c7f..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/design.docbook +++ /dev/null @@ -1,96 +0,0 @@ - - - Corporate Graphic Design - - - 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. - - - - 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 - decition the organization needs to take by itself, based on - its need of better describe what it is. - - - - In the very specific case of &TCP;, we'll concentrate our - attention on corporate messages that reach us through the - visual sense. This is, all the visual manifestations &TCP; is - made of. As visual manifestaions we understand all the visible - media &TCP; uses to manifest its existence on. At this point - it is necessary to consider what &TCP; 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. - - - - Inside &TCP; we identify and apply corporate design to the - following visual manifestations: - - - - - - - &TCD; — This visual manifestation exists to cover all - actions related to artwork production and rebranding, required - by &TCD; in order to comply with upstream's redistribution - guidelines. This visual manifestation is described in . - - - - - - &TCW; — This visual manifestation exists to cover all - actions related to artwork production required by &TCP; to - manifest its existence in the World Wide Web medium. This - visual manifestation is described in . - - - - - - &TCS; — This visual manifestation exists to cover all - actions related to artwork production required by &TCP; to - manifest its existence through media produced industrially - (e.g., stationery, clothes, CDs, DVDs, etc.). This visual - manifestation is described in . - - - - - - The visual manifestations identified above seem to cover most - media required by &TCP;, 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 whaterver visual manifestation &TCP; - thouches to show its existence. - - - - Once all visual manifestations have been identified and - defined through design models, it is time to visually remark - their connection with &TCP;. This kind of connection is - realized by applying &TCBRAND; to design models inside visual - manifestations supported through corporate design. - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/mission.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/mission.docbook deleted file mode 100644 index 507873d..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/mission.docbook +++ /dev/null @@ -1,40 +0,0 @@ - - - Corporate Mission - - - &TCP; exists to produce &TCD;, an Enterprise-class Linux - Distribution derived from sources freely provided to the - public by a prominent North American Enterprise Linux vendor. - &TCD; conforms fully with the upstream vendors redistribution - policy and aims to be 100% binary compatible. (&TCD; mainly - changes packages to remove upstream vendor branding and - artwork.). - - - - &TCD; 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. - - - - &TCD; 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. - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/structure.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/structure.docbook deleted file mode 100755 index a0d20f9..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Project/structure.docbook +++ /dev/null @@ -1,91 +0,0 @@ - - - Corporate Structure - - - &TCP; corporate structure is based on a &MCVIS;. In this - configuration, one unique name and one unique visual style is - used in all visual manifestation &TCP; 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 &TCP;. - - - - Other corporate structures for &TCP; have been considered as - well. Such is the case of producing one different visual style - for each major release of &TCD;. 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 &TCP; - is made of. - - - - &TCP;, as organization, is mainly made of (but not limited to) - three visual manifestions: &TCD;, &TCW; and &TCS;. Inside - &TCD; visual manifestations, &TCP; maintains near to four - different major releases of &TCD;, parallely in time. - However, inside &TCW; 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 &TCD; - individually, but one web site to cover them all). Likewise, - the content produced in &TCS; is industrially created for no - specific release, but &TCP; in general. - - - - In order to produce the &TCPMCVIS; correctly, we need to - concider all the visual manifestations &TCP; is made of, not - just one of them. If one different visual style is - implemented for each major release of &TCD;, which one of - those different visual styles would be used to cover the - remaining visual manifestations &TCP; is made of (e.g., &TCW; - and &TCS;)? - - - - Probably you are thinking: yes, I see your point, but &TCBRAND; - 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? - - - - Harder to maintain, more work to do, probably. Specially when - you consider that &TCP; 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 maintainance through time. With - that in mind, we consider &TCPCVIS; must be consequent with - such stability and consistency tradition. It is true that - &TCBRAND; 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 &TCP; visual manifestations would - be very good in favor of &TCP; recognition. - - - - 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 dead project. So, there is - no problem on creating a brand new visual style for each new - major release of &TCD;, in order to refresh &TCD; visual - style; the problem itself is in not propagating the brand new - visual style created for the new release of &TCD; to all other - visual manifestations &TCP; is made of, in a way &TCP; could - be recognized no matter what visual manifestation be in front - of us. Such lack of uniformity is what introduces the visual - contradition we are precisely trying to solve by mean of - themes production in &TCAR;. - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Showroom.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Showroom.docbook deleted file mode 100644 index db87232..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Showroom.docbook +++ /dev/null @@ -1,11 +0,0 @@ - - - The CentOS Showroom - ... - - - ... - ... - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Web.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Web.docbook deleted file mode 100644 index 5a5ba5d..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Web.docbook +++ /dev/null @@ -1,7 +0,0 @@ - - - The CentOS Web - - &identity-web-intro; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Web/intro.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Web/intro.docbook deleted file mode 100644 index 956fa35..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Identity/Web/intro.docbook +++ /dev/null @@ -1,9 +0,0 @@ - - - Introduction - - - ... - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Locales.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Locales.docbook deleted file mode 100644 index 656b9d8..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Locales.docbook +++ /dev/null @@ -1,21 +0,0 @@ - - - Localization - - - ... - - - - ... - ... - - - ... - ... - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Locales.ent b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Locales.ent deleted file mode 100644 index 48245e8..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Locales.ent +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals.docbook deleted file mode 100644 index 44bacd4..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals.docbook +++ /dev/null @@ -1,30 +0,0 @@ - - - Documentation - - - - &TCAR; documentation work line is implemented through - documentation manuals. Documentation manuals are - implemented through different documentation formats - provided inside &TCD; (e.g., - Docbook, - Texinfo, - LaTeX, etc.). Structuring - tasks related to documentation systems (e.g., creating, - editing, deleting, copying, renaming, etc.) are - standardized through the help functionality - of centos-art.sh script, as described - in . This way, people - writting documentation don't need to deal with underlaying - tasks like creating files, updating menus, nodes, cross - references and wondering where to put everything in - &TCAR;. - - - - - &manuals-production; - &manuals-formats; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals.ent b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals.ent deleted file mode 100644 index c68bc34..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals.ent +++ /dev/null @@ -1,13 +0,0 @@ - - - - - - - - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats.docbook deleted file mode 100644 index 9fac62b..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats.docbook +++ /dev/null @@ -1,10 +0,0 @@ - - - Documentation Formats - - &manuals-formats-intro; - &manuals-formats-texinfo; - &manuals-formats-docbook; - &manuals-formats-latex; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/docbook.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/docbook.docbook deleted file mode 100644 index 1b7c5da..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/docbook.docbook +++ /dev/null @@ -1,51 +0,0 @@ - - - DocBook - - - This section describes the implementation of DocBook - documentation format inside the functionality of - centos-art.sh script. In this section we - assume you have a basic understanding of DocBook documentation - format. Otherwise, if you don't know what DocBook - documentation format is, take a look at DocBook website and then, - come back here. - - - - Document Structure - - ... - - - - - Document Templates - - ... - - - - - Document Expansions - - ... - - - - - Document Configuration - - ... - - - - - Document Localization - - ... - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/intro.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/intro.docbook deleted file mode 100644 index f3d96f4..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/intro.docbook +++ /dev/null @@ -1,24 +0,0 @@ - - - Introduction - - - &TCD; provides support for different documentation formats, - including Texinfo, LaTeX, DocBook and LinuxDoc. These formats - have their own specifications and requirements to create and - maintain documentation manuals written through them. Inside - &TCAR;, the functionality - provides the interface you use to create and maintain - documentation manuals without needing to take care the - underlaying structuring tasks. - - - - This chapter describes how the functionality implements the - different documentation source formats available inside &TCD;, - and the internationalization issues related to documentation - manuals produced through them. - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/latex.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/latex.docbook deleted file mode 100644 index b777161..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/latex.docbook +++ /dev/null @@ -1,47 +0,0 @@ - - - LaTeX - - - This section describes the implementation of LaTeX - documentation format inside the help - functionality of centos-art.sh script described in . In this section we assume you - have a basic understanding of LaTeX language. - - - - Document Structure - - ... - - - - - Document Templates - - ... - - - - - Document Expansions - - ... - - - - - Document Configuration - - ... - - - - - Document Localization - - ... - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/texinfo.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/texinfo.docbook deleted file mode 100644 index 801ec4b..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Formats/texinfo.docbook +++ /dev/null @@ -1,871 +0,0 @@ - - - Texinfo - - - This section describes the implementation of Texinfo - documentation format inside the functionality of - centos-art.sh script. In this section we - assume you have a basic understanding of Texinfo documentation - system. Otherwise, if you don't know what Texinfo - documentation system is, read the Texinfo manual first (e.g., - by running the info texinfo command) and - then, come back here. - - - - Document Structure - - The functionality of - centos-art.sh provides a document structure - that makes documentation manuals created through it to be - scalable and maintainable through time. This document - structure follows the idea of an upside-down tree to organize - chapters, sections, subsections and the like, as described in - . - - - - The - functionality creates documentation manuals source files in - the Documentation/Models/Texinfo/ - directory and saves output produced from them in the Documentation/Manuals/Texinfo/ - directory. To produce documentation manuals initial source - files, the functionality - uses Texinfo documentation templates, as described in . - - - - Inside the documentation models directory, source files are - stored inside language-specific directories. The - language-specific directories are necessary to implement - internationalization of Texinfo source files, as described in - . - - - - Inside the language-specific directory, the following files - exist to store the manual's main definitions (e.g., title, - subtitle, author, copyright notice, chapters, appendixes, - indexes and all similar stuff a documentation manual usually - has). In addition to these files, there is one directory for - each chapter created inside the manual. Inside each chapter - directory, you'll find the files controlling the section - definitions related each chapter they belong to. The section - files (a.k.a. documentation entries) are - suffixed with a texinfo - extension and named arbitrarily, as it is illustrated in . - Inside section files it is where you write the manual's - content itself. - - - - Texinfo document structure - - Texinfo document structure - - - Documentation/Models/Texinfo/${MANUAL_NAME} -`-- ${LANG} - |-- ${CHAPTER_NAME}/ - | `-- ${SECTION_NAME}.texinfo - |-- ${CHAPTER_NAME}-menu.texinfo - |-- ${CHAPTER_NAME}-nodes.texinfo - |-- ${CHAPTER_NAME}.texinfo - |-- Licenses -> Documentation/Models/Texinfo/Default/${LANG}/Licenses - |-- Licenses-menu.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses-menu.texinfo - |-- Licenses-nodes.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses-nodes.texinfo - |-- Licenses.texinfo -> Documentation/Models/Texinfo/Default/${LANG}/Licenses.texinfo - |-- ${MANUAL_NAME}.conf - |-- ${MANUAL_NAME}-index.texinfo - |-- ${MANUAL_NAME}-menu.texinfo - |-- ${MANUAL_NAME}-nodes.texinfo - `-- ${MANUAL_NAME}.texinfo - - - - - - - Texinfo (as in texinfo-4.8-14.el5) doesn't - support part sectioning inside documentation manuals, so - neither the functionality - does. Nevertheless, you can create several documentation - manuals and consider them as part of a bigger documentation - manual to workaround this issue. - - - - In this document structure, the creation of documentation - manuals, chapters and sections is not limitted. You can create - as many documenation manuals, chapters and sections as you - need. The only limitation would be the amount of free space - required to store the Texinfo source files and the output - files produced from them in your workstation. - - - - - - Document Templates - - Texinfo document templates provide the initial document - structure the - functionality needs in order to create and maintain document - structures, as described in . - - - - Texinfo document templates are language-specific. This means - that there is (or, at least, must be) one Texinfo document - template for each language you plan to support documentation - manuals for. By default, &TCAR; provides a default Texinfo - document template under en_US - directory. This template structure is used when your current - locale is English language or when you are creating/editing a - documentation manual in a language other than English, but no - language-specific document template for that language exists - in the Scripts/Documentation/Models/Texinfo/Default/ - directory. - - - - The Scripts/Documentation/Models/Texinfo/Default/ - directory organizes all Texinfo document templates using the - format LL_CC, where LL is the language code (as in ISO-639) - and CC the country code (as in ISO-3166). The directory - structure of Texinfo document templates is illustrated in the - - and implemented through the following files: - - - - - manual.texinfo - - - This file can be found inside the language-specific directory - and contains the manual's main definitions (e.g., document - title, document language, document authors, copyright notice, - etc.). - - - - - - manual-menu.texinfo - - - This file can be found inside the language-specific directory - and contains the menu definitions of chapters inside the - manual. When - functionality creates instances of this file, menu definitions - inside it are automatically updated when a new chapter is - created or deleted through the functionality. Generally, you - don't need to edit instances of this file once the - documentation manual has been created. - - - When a documentation manual is created for first time, this - file is copied from Texinfo document template directory - structure to the documentation manual being currently created. - At this specific moment, the instance created contains the - following Texinfo menu definition: - - - -@menu -* Licenses:: -* Index:: -@end menu - - - - Later, when chapters are added to or deleted from the - documentation manual, the content of this file varies adding - or deleting menu entries accordingly. Nevertheless, the two - entries shown above are ignored when new chapters are added to - or removed from the list, so they will always be present in - instances of this file. To preserve the manual consistency, - the functionality prevents - you from deleting any of these chapters once the documentation - manual has been created. - - - - - - - manual-nodes.texinfo - - - This file can be found inside the language-specific directory - and contains the node definitions of all chapters inside the - manual. When - functionality creates instances of this file, node definitions - inside it are automatically created based on menu definitions - (see manual-menu.texinfo file above) and - they don't include any content here. Instead, as part of the - node definition, the @include command is used to - connect each node with its content. Generally, you don't need - to edit instances of this file once the documentation manual - has been created. - - - - - - manual-index.texinfo - - - This file can be found inside the language-specific directory - and contains the Texinfo commands used to generated an - organized view of all indexes you defined inside documentation - entries so they can be quickly accessed. Generally, you don't - need to edit instnaces of this file once the documentation - manual has been created. - - - - - - manual.conf - - - This file contains the initial configuration of documentation - manuals written in Texinfo format. When a documentation manual - is created for first time, this file is copied into its target - directory so you be able to customize specific information - like menu order, title styles and template assignments - therein. The content of this file is described in . - - - - - - Chapters.texinfo - - - This file contains Texinfo's main chapter definition used - by functionality when new - chapters are created inside documentation manuals. When - chapters are created for first time, they come without any - introduction or documentation entry inside. - - - In case you need to add/update the chapters definition files, - edit the related chapter definition file inside the - documentation manual you are working on, not the template file - used to create it. To edit the chapter definition file, don't - provide any section information in the documentation entry. - For example, if you want to update the chapter introduction - related to trunk chapter inside - tcar-fs documentation manual, use the - tcar-fs::trunk: documentation entry. - - - - - - Chapters-menu.texinfo - - - This file is part of Texinfo's main chapter definition and - should be initially empty. Later, when chapters are created - for first time, this file is copied as it is (i.e., empty) - into the documentation manual to store the Texinfo menu - entries related to all documentation entries created inside - the chapter. The Texinfo menu entries related to documentation - entries are automatically created using Texinfo source files - as reference. - - - - - - Chapters-nodes.texinfo - - - This file is part of Texinfo's main chapter definition and - contains the node definition the - functionality uses as reference to create the list of Texinfo - nodes related to all documentation entries created inside the - chapter. The node definition of documentation entries is - automatically created from the menu definition of - documentation entries (see - Chapters-menu.texinfo file above), once it - has been updated from Texinfo source files. - - - - - - section.texinfo - - - This file contains the Texinfo section definition used by - functionality when new - documentation entries are created inside chapters of - documentation manuals. When documentation entries are created - for first time, they are created as empty documentation - entries that you need to fill up with content. Again, if you - want to update the content of sections inside the - documentation manual, update the related documentation entry - inside the documentation manual, not the template file used to - create it. - - - - The creation of documentation entries inside the documentation - manual is represented by the - ${SECTION_NAME}.texinfo file, as - described in . In - this example, ${SECTION_NAME} is a variable - string referring the file name of documentation entries. The - file names of documentation entries are made of letters, - numbers and the minus sign (which is generally used as word - separator). - - - - Documentation entries are not limited inside chapters of - documentation manuals. You can create as many documentation - entries as you need to describe the content of your manual. - - - - - - - There are other files which aren't related to manual's source - files, but to manual's output files. Such files are described - below and can be found either inside or outside the - language-specific directories so you can control common and - specific output settings through them. These files aren't - copied into the directory structure of new documentation - manuals created through the - functionality. Instead, they remain inside the template - directory structure so as to be reused each time the output of - documentation manuals is rendered. - - - - - manual-init.pl - - - This file can be found inside and outside language-specific - directories and contains the Texi2html initialization script. - When this file is outside the language-specific directory, it - contains common customizations to all language-specific - outputs (e.g., changing the output DTD). When this file is - inside the language-specific directory, it contains - translations for that language-specific output (e.g., special - words like See, Index, Contents, Top, etc., are localized - here). - - - - - - manual.sed - - - This file can be found inside and outside language-specific - directories and contains special transformations for Texi2html - output. Again, when this file is inside language-specific - directories the transformation are applied to that - language-specific XHTML output and when it is outside - language-specific directories the transformations are applied - to all language-specific XHTML outputs. Most transformations - achieved through this file are to produce admonitions since - Texinfo documentation format (as in - texinfo-4.8-14.el5) doesn't have an - internal command to build them. - - - - - - - Template for texinfo document structures - - Template for texinfo document structures - - - -Documentation/Models/Texinfo/Default/ -|-- ${LANG}/ -| |-- Chapters/ -| | |-- section.texinfo -| | `-- section-functions.texinfo -| |-- Chapters-menu.texinfo -| |-- Chapters-nodes.texinfo -| |-- Chapters.texinfo -| |-- Licenses/ -| | |-- GFDL.texinfo -| | `-- GPL.texinfo -| |-- Licenses-menu.texinfo -| |-- Licenses-nodes.texinfo -| |-- Licenses.texinfo -| |-- manual-index.texinfo -| |-- manual-init.pl -| |-- manual-menu.texinfo -| |-- manual-nodes.texinfo -| |-- manual.conf -| |-- manual.sed -| `-- manual.texinfo -|-- manual-init.pl -`-- manual.sed - - - - - - - - Inside the directory structure of Texinfo document templates, - the Chapters directory - stores section specific models used to create and maintain - section files inside manuals. File names beginning with - Chapters, at the same level of Chapters directory, are used to - create chapter specific files inside manuals. - - - - The Licenses directory - organizes the license information linked from all manuals. - Notice the license information is not copied into - documentation manuals when they are created, but referred from - models location where they are maintained. This configuration - permits all documentation manuals written in Texinfo format - inside &TCAR; to use the same license information. This way, - if a change is committed to license files, it will be - immediately propagated to all documentation manuals the next - time their output files be updated. - - - - - Document Expansions - - The document expansions are special constructions the functionality provides to - generate content dynamically inside Texinfo source files. - - - - The <code>SeeAlso</code> Expansion - - - This expansion creates a list of links with section entries - one level ahead from the section entry being currently - processed. In this construction, the TYPE variable can be - either itemize, enumerate or - menu. When no TYPE variable is provided, the - itemize value is considered as default. - - - @c -- <[centos-art(SeeAlso,TYPE) -@c -- ]> - - - This expansion might result useful when you are documenting - the repository file system. For example, if you are currently - editing the documentation entry related to Identity directory and want - to create a linkable list of all documentation entries in the - first level under it, the code you'll have once the - construction be expanded would look like the following: - - - -@c -- <[centos-art(SeeAlso) -@itemize -@item @ref{Trunk Identity Brushes} -@item @ref{Trunk Identity Fonts} -@item @ref{Trunk Identity Images} -@item @ref{Trunk Identity Models} -@item @ref{Trunk Identity Palettes} -@item @ref{Trunk Identity Patterns} -@item @ref{Trunk Identity Webenv} -@end itemize -@c -- ]> - - - - An interesting thing to notice here is that document - expansions are executed each time the related documentation - entry is edited or updated. Following with the example above, - if the documentation entries related to directories under - Identity changes - for some reason (e.g., they are removed from documentation - manual), the list generated as result of document expansion - will be updated automatically after editing the documentation - entry or updating the documentation manual structure. - - - - - - - - Document Configuration - - The document configuration is stored in the - ${MANUAL_NAME}.conf file, inside the - documentation manual directory structure. This file is - originally copied from manual.conf - template file when the documentation manual is created for - first time. The content of - ${MANUAL_NAME}.conf file is organized in - sections. Each section here is written in one line of its own - and have the form [section_name]. Under sections, - the configuration settings take place through - name="value" pairs set in one line each. Notice - that quotation marks around the option_value are required. - Comments are also possible using the # character - at the begining of lines. Comments and empty lines (including - tabs and white spaces) are ignored. In case more than one - section or option appear with the same name inside the - configuration file, the first one found will be used. Nested - section definitions are not supported. - - - [section_name] -# This is a comment. -option_name = "option_value" - - - The ${MANUAL_NAME}.conf file is specific - to document templates. If you are using Texinfo document - template to create documentation manuals, then the default - configuration file for that documentation manual is taken from - Texinfo document template directory structure. However, if you - are using a document template different to Texinfo document - template, the default configuration file will be taken from - the related document template directory structure you are - creating the documentation manual from. - - - - The <code>[main]</code> Section - - The [main] section organizes settings that let - you customize the way sections and menu definitions are - created inside the documentation manual. The following options - are available in this section: - - - - - manual_format - - - This option specifies the documentation format used by manual. - To write documentation manuals in Texinfo format, the value - of this option must always be: - - manual_format = "texinfo" - - - Once the documentation manual has been created, you must not - change the value of option. - This will produce an error because there is not a migration - feature available yet. In the future, when you change this - value, it must be possible to transform documentation manuals - from one format to another. - - - - - - - manual_section_style - - - This option specifies the title style used by sections inside - the manual. Possible values to this option are - `cap-each-word' to capitalize each word in the section title, - `cap-first-word' to capitalize the first word in the section - title only and `directory' to transform each word in the - section title into a directory path. From all these options, - `cap-each-word' is the one used as default. - - manual_section_style = "cap-each-word" - - - - - manual_section_order - - - This option specifies the order used by sections inside the - manual. By default new sections added to the manual are put on - the end to follow the section order in which they were - `created'. Other possible values to this option are `ordered' - and `reversed' to sort the list of sections alphabetically - from A-Z and Z-A, respectively. - - manual_section_order = "created" - - - - - - - The <code>[templates]</code> Section - - The [templates] section provides the assignment - relation between template files and documentation entry files - inside the manual. The template definition is set on the left - side using relative path and the documentation entry files are - described on the right side using a regular expression. The - first match wins. - - Chapters/section.texinfo = "^.+\.texinfo$" - - - - - - Document Localization - - To produce localized documentation manuals through Texinfo - documentation format it is necessary to create one - documentation manual for each language it is desired to - support documentation for. Documentation manuals created in - this configuration don't have a direct relation among - themselves except that one adopted by people writting them to - keep their content syncronized. In this configuration - translators take one documentation manual as reference (a.k.a. - the source manual) and produce several translated manuals - based on its content. To keep track of changes inside the - source manual, the underlaying version control system must be - used considering that there is no direct way to apply - gettext - - The gettext program translates - a natural language message into the user's language, by - looking up the translation in a message catalog. For more - information about the gettext - program, run info gettext. - - procedures to Texinfo source files. - - - - In order to maintain localization of Texinfo source files - through gettext procedures, it is necessary - to convert the Texinfo source files into XML format first. - This way it would be possible to make use of and functionalities to maintain - translation messages in different languages through portable - objects and producing localized XML files based on such - portable objects, respectively. Once the localized XML file - is available, it would be a matter of using an XSLT processor - (see the xsltproc command) to realize the - convertion from XML to a localize Texinfo (or possible other) - format. Nevertheless, this workaround fails because the - Document Type Definition (DTD) required to validate the XML - file produced from makeinfo (as in - texinfo-4.8-14.el5) is not availabe inside - &TCD; (release 5.5), nor it is the XSLT files required to - realize the transformation itself for such DTD. - - - - Another similar approach to maintain localization of Texinfo - source files through gettext procedures - would be to convert Texinfo source file to DocBook format; for - who the required DTD and XSLT files are available inside - &TCD;. This way, following a procedure similar to that one - describe for XML files above, it would be possible to end up - having localized DocBook files that can be used as source to - produce localized output for both online and printing media. - However, the DocBook output produced from - makeinfo command (as in - texinfo-4.8-14.el5) isn't a valid DocBook - document according to DocBook DTDs available inside &TCD; - (release 5.5) thus provoking the validation and transformation - of such a malformed document to fail. - - - - Document Language - - The language information of those documentation manuals - produced through Texinfo documentation format is declared by - Texinfo's @documentlanguage command. This - command receives one argument refering the language code (as - in ISO-639 standard) and must be set inside the manual's main - definition file. Generally, there is no need to change the - document language declaration once it has been created by the - functionality; unless you - mistakently create the manual for a locale code different to - that one you previously pretended to do in first place, of - course. - - - - The language information used in both Texinfo source files and - XHTML output produced by the - functionality is determined by the user's session - LANG environment variable. This variable can - be customized in the graphical login screen before login, or - once you've login by explicitly setting the value of - LANG environment variable inside the - ~/.bash_profile file. - - - - - To create documentation manuals in English language the - LANG environment variable must be set to - en_US.UTF-8 or something similar. Likewise, if - you want to create documentation manuals in a language other - than English, be sure the LANG environment - variable is set to the appropriate locale code. - - The appropriate locale code to set here can be found in - the output produced by the locale -a | - less command. - - - - - - When producing output from Texinfo source files using the - makeinfo command (as in the - texinfo-4.8-14.el5 package), the language - information set by @documentlanguage is ignored - in Info and HTML output, but cosidered by Tex program to - redefine various English words used in the PDF output (e.g., - Chapters, Index, - See, and so on) based on the current language - set in. - - - - - - Document Encoding - - The encoding information of documentation manuals produced - through Texinfo documentation format is declared by Texinfo's - @documentencoding command and can take either - US-ASCII, ISO-8859-1, - ISO-8859-15 or ISO-8859-2 as - argument. Nevertheless, you should be aware that the - functionality doesn't - declare the @documentencoding inside Texinfo - source files. Let's see why. - - - - When the @documentencoding command is set in - Texinfo source files, the terminal encoding you use to read - the Info output produced from such files must be set to that - encoding information you provided as argument to - @documentencoding command; this, before using an - Info reader to open the Info output file in the terminal. - Otherwise, when the terminal and the Texinfo source files - encoding definition differ one another, characters defined - through Texinfo's special way of producing floating accents - won't be displayed as expected (even when the - is provided to - makeinfo command). On the other hand, when - the @documentencoding command is not set in - Texinfo source files, it is possible to write and read - documentation manuals using the UTF-8 encoding without needing - to use Texinfo's special way of producing floating accents - because the terminal encoding would be able to interpret the - characters entered when the Texinfo source files were written - in first place. - - - - When Texinfo's special way of producing floating accents isn't - used, HTML entities are not produced in XHTML output produced - by texi2html, nor in the HTML output - produced by makeinfo, nor in PDF output. - In this last case, when producing PDF output, you can realize - what the floating accents are by trying to produce an - accentuated Spanish i letter (e.g., - í). When you do so, you'll note that that - construction puts the accentuation mark - over the i letter's dot, - instead of removing the i letter's dot and - put the accentuation mark on its place. In the case of XHTML - output, however, it is possible to produce well localized - XHTML output by setting - - - <meta http-equiv="content-type" content="text/html; charset=UTF-8" /> - - - on the head section of each XHTML output to instruct the web - browsers what encoding to use to display the document content. - Of course, in order to display the document content correctly, - the web browser should provide support for UTF-8 encoding. - - - - These contradictions provide the reasons over which it was - decided not to set the @documentencoding in those - Texinfo source files produced by the functionality. - - - - - - - - Conclusions - - - Texinfo documentation format is very good producing online - documentation for reading text terminals. It provides feautres - to export source files to different output formats both for - reading online and paper. However, localized documents becomes - hard to maintain because it is required one document structure - for each language you want to produce documentation for. - - - Intermediate formats like XML and Docbook provide an - alternative to centralize localization of Texinfo document - source files, but there is no supported way inside &TCD; to - transformed a localized XML file back into texinfo format, nor - a way of producing well formed Docbook documents from Texinfo - source files. Thus, one Texinfo source structure for each - language to support is the solution adopted by functionality. - - - - When using Texinfo documentation format it is difficult to - produce well localized PDF outputs, but it is possible to - produce well localized Info, Text, and XHTML outputs as long - as no document encoding be explicitly set inside Texinfo - source files and UTF-8 be used as default terminal character - encoding. - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production.docbook deleted file mode 100644 index 58451f0..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production.docbook +++ /dev/null @@ -1,12 +0,0 @@ - - - Documentation Production Cycle - - &manuals-production-intro; - &manuals-production-identifying-goals; - &manuals-production-identifying-title; - &manuals-production-identifying-structure; - &manuals-production-implementing-structure; - &manuals-production-maintaining-structure; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook deleted file mode 100644 index c47888c..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook +++ /dev/null @@ -1,50 +0,0 @@ - - - Identifying Document Goals - - - The first step in producing a documentation manual is to - clearly understand what you exactly need to document and why - you need to do so. The obvious answer to this question would - be to describe the basic ideas behind an implementation so it - can be useful once published. It is important that you find - out the reasons you need to do what you are doing and, also, - those helping you to retain the motivation to keep doing it in - the future. Otherwise, without such foundations, you'll surely - end up leaving the effort soon enough to make a lost cause - from your initial work. - - - - Before The CentOS Artwork Repository File - System documentation manual would exist, there was - an emerging need to understand what each directory inside the - growing directory layout was for, how it could be used and - each directory could be connected one another. At that moment, - the directory layout was very unstable and explaining the - whole idea behind it was not possible, there were too many - changing concepts floating around which needed to be - considered in the same changing way. So, to understand what - was happening, the The CentOS Artwork Repository - File System documentation manual was created. - - - - The The CentOS Artwork Repository File - System manual was conceived based on the idea of - documenting each directory inside the repository individually - and, later, by considering all directory documentations - altogether, it would be (hypothetically) possible to correct - the whole idea through an improvement cycle that would - consolidate the final idea we were trying to implement. - - - - Other documentation manuals can be based on reasons different - from those described above, however, no matter what those - reasons are, it will be helpful to make yourself a clean idea - about what you are going to document exactly before putting - your hands on it. - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/identifying-structure.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/identifying-structure.docbook deleted file mode 100644 index 8178a2e..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/identifying-structure.docbook +++ /dev/null @@ -1,145 +0,0 @@ - - Identifying Document Structure - - Once both the manual's title and the manual's directory name - have been defined, it is time for you to plan the document - structure through which the manual's content will be - organized. - - - - The specific document structure you choose for a documentation - manuals is affected by the documentation format you use to - write documentation source files. Nevertheless, no matter - what the documentation format be, the document structure - produced from the - functionality will always follow and upside-down tree - configuration for document structures. In this configuration, - documentation manuals can be organized through different - structural levels (e.g., parts, chapters, sections, - subsection, etc.) based on the support provided by the - documentation format you chose. - - - - The The CentOS Artwork Repository File - System documentation manual was conceived to - document each directory structure &TCAR; is made of, using - Texinfo as main documentation format. - - - - At this point we find that &TCAR; had more levels deep than - sectioning commands available inside documentation format. - This way it is not possible to use one sectioning command for - each directory level inside the repository directory structure - we need to document. Based on these issues, it is - imperative to re-accommodate the document structure in order - to be able of documenting every directory &TCAR; is made of, - using the sectioning levels supported by that documentation - format we chose, no matter how many levels deep the repository - directory structure had. - - - - As consequence, The CentOS Artwork Repository File - System ended up being organized through the - following documentation structure: - - - - - Chapter 1. The trunk - Directory - - - This chapter describes the trunk directory inside the - repository and all subdirectories inside it. The first level - of directories (i.e., the trunk directory itself) is - described inside the chapter entry. Deeper directory levels - are all documented through sections and have a file for their - own. It is also possible to write subsections and - subsubsections, however, they don't have a file for their own - as sections do. Subsections and Subsubsections should be - written as part of section files (i.e., when writting - sections). - - - - - - Chapter 2. The branches - Directory - - - This chapter describes the branches directory and all - directories inside it following the same structure described - for trunk directory - above. - - - - - - Chapter 3. The tags - Directory - - - This chapter describes the tags directory and all - directories inside it following the same structure described - for trunk directory - above. - - - - - - Appendix A. Licenses - - - This appendix is confined to organize licenses mentioned - in the manual. The content of this appendix is out of - documenatation manual scope itself and is shared among all - documentation manuals written through the functionality. - - - - - - Index - - - This chapter organizes links to those index definitions you - defined inside the documentation manual. The index information - displayed by this chapter is auto-generated each time the - manual's output files are created so this chapter is not - editable. - - - - - - - The document structure illustrated above is also considered - the default document structure used by the functionality of - centos-art.sh script when you produce new - documentation manuals inside &TCAR;. In contrast with document - structure illustrated above, the default document structure - used by functionality - doesn't include sectioning constructions like parts, chapters, - sections, subsections and the like in the document structure - created. Such structuring constructions should be specified by - you when building the documentation manual. The only - exceptions to this restriction are sectioning structures used - to organize contents like Index and - Licenses, which are considered inseparable - components of documentation manuals stored inside &TCAR;. - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/identifying-title.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/identifying-title.docbook deleted file mode 100644 index 2c8a8bd..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/identifying-title.docbook +++ /dev/null @@ -1,26 +0,0 @@ - - Identifying Document Title - - Once you've make yourself an clean idea of what the - documentation manual is for and the needs behind it, it is - time for you to define the manual's title and the manual's - directory name. Both manuals' title and manual's directory - name describe what the documentation manual is about. The - manual's title is used inside the documentation while the - manual's directory name is used to store the related source - files inside &TCAR; directory structure. Generally, the - manual's title is a phrase of few words and the manual's - directory name is the abbreviation of that phrase set as - manual's title. - - - - Following with our example, the manual's title chosen was - The CentOS Artwork Repository File - System and its directory name was set to - Tcar-fs to comply with the - file name convenctions described at . - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/implementing-structure.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/implementing-structure.docbook deleted file mode 100644 index 1feb428..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/implementing-structure.docbook +++ /dev/null @@ -1,12 +0,0 @@ - - - Implementing Document Structure - - - The document structure implementation is automated by the - functionality, as - described in . - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/intro.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/intro.docbook deleted file mode 100644 index 5b3f328..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/intro.docbook +++ /dev/null @@ -1,21 +0,0 @@ - - - Introduction - - - This chapter describes the procedure you should follow to - create and maintain documentation manuals inside &TCAR;. - - - - This chapter describes general concepts that can be applied - through the documentation formats supported inside the - help functionality of - centos-art.sh script. To illustrate the - production process related to documentation manuals inside - &TCAR;, this chapter uses the The CentOS Artwork - Repository File System (TCAR-FS) documentation - manual as example. - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/maintaining-structure.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/maintaining-structure.docbook deleted file mode 100644 index f503380..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Manuals/Production/maintaining-structure.docbook +++ /dev/null @@ -1,12 +0,0 @@ - - - Maintaining Document Structure - - - The document structure maintenance is implemented by the functionality, as described in - . - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface.docbook deleted file mode 100644 index 42c8578..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface.docbook +++ /dev/null @@ -1,9 +0,0 @@ - - - Preface - - &preface-overview; - &preface-docconvs; - &preface-feedback; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface.ent b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface.ent deleted file mode 100644 index ce36070..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface.ent +++ /dev/null @@ -1,4 +0,0 @@ - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface/docconvs.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface/docconvs.docbook deleted file mode 100644 index 17509ca..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface/docconvs.docbook +++ /dev/null @@ -1,225 +0,0 @@ -
- - Document Convenctions - - - In this manual, certain words are represented in different - fonts, typefaces, sizes, and weights. This highlighting is - systematic; different words are represented in the same style - to indicate their inclusion in a specific category. The types - of words that are represented this way include the - following: - - - - - command - - - Linux commands (and other operating system commands, when - used) are represented this way. This style should - indicate to you that you can type the word or phrase on - the command line and press Enter to - invoke a command. Sometimes a command contains words that - would be displayed in a different style on their own (such - as file names). In these cases, they are considered to be - part of the command, so the entire phrase is displayed as - a command. For example: - - - - Use the centos-art render - Identity/Images/Themes/TreeFlower/4/Distro/5/Anaconda - --filter="01-welcome" command to produce the first - slide image used by Anaconda in the branch 5 of &TCD; - using the version 4 of TreeFlower artistic motif. - - - - - - file name - - - File names, directory names, paths, and RPM package names - are represented this way. This style indicates that a - particular file or directory exists with that name on your - system. Examples: - - - - The init.sh file in Scripts/Bash/Cli/ - directory is the initialization script, written in Bash, - used to automate most of tasks in the repository. - - - - The centos-art command uses the - ImageMagick RPM package to convert - images from PNG format to other formats. - - - - - - key - - - A key on the keyboard is shown in this style. For - example: - - - - To use Tab completion to list particular - files in a directory, type ls, then a - character, and finally the Tab key. Your - terminal displays the list of files in the working - directory that begin with that character. - - - - - - keycombination - - - A combination of keystrokes is represented in this way. - For example: - - - - The CtrlAltBackspace - key combination exits your graphical session and returns - you to the graphical login screen or the console. - - - - - - computer output - - - Text in this style indicates text displayed to a shell - prompt such as error messages and responses to commands. - For example, the ls command displays - the contents of a directory using this style: - - - -render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh -render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh -render_getDirOutput.sh render.sh - - - - The output returned in response to the command (in this - case, the contents of the directory) is shown in this - style. - - - - - - prompt - - - A prompt, which is a computer's way of signifying that it - is ready for you to input something, is shown in this - style. Examples: - - - - - - $ - - - - - # - - - - - [centos@projects centos]$ - - - - - projects login: - - - - - - - - user input - - - Text that the user types, either on the command line or - into a text box on a GUI screen, is displayed in this - style. In the following example, - text is displayed in this style: To - boot your system into the text based installation program, - you must type in the text command - at the boot: prompt. - - - - - - replaceable - - - Text used in examples that is meant to be replaced with - data provided by the user is displayed in this style. In - the following example, - version-number is displayed in - this style: The directory for the kernel source is - /usr/src/kernels/version-number/, - where version-number is the - version and type of kernel installed on this system. - - - - - - Additionally, we use several different strategies to draw - your attention to certain pieces of information. In order of - urgency, these items are marked as a note, tip, important, - caution, or warning. For example: - - - Remember that Linux is case sensitive. In other words, a - rose is not a ROSE is not a rOsE. - - - - The directory /usr/share/doc/ contains - additional documentation for packages installed on your - system. - - - - If you modify the DHCP configuration file, the changes - do not take effect until you restart the DHCP daemon. - - - - Do not perform routine tasks as root — use a - regular user account unless you need to use the root account - for system administration tasks. - - - - Be careful to remove only the necessary partitions. - Removing other partitions could result in data loss or a - corrupted system environment. - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface/feedback.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface/feedback.docbook deleted file mode 100644 index b6f8334..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface/feedback.docbook +++ /dev/null @@ -1,14 +0,0 @@ -
- - Send In Your Feedback - - - If you find a bug in &TCAR; or this manual, we would like to - hear about it. To report bugs related to this manual, send an - e-mail to the centos-devel@centos.org mailing - list. When you write the bug report, take care of being - specific about the problem you are reporting on (e.g., where - it is, the section number, etc.) so we can found it easily. - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface/overview.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface/overview.docbook deleted file mode 100644 index b12e354..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Preface/overview.docbook +++ /dev/null @@ -1,84 +0,0 @@ -
- - Overview - - - Welcome to &TCARUG;, the official documentation of &TCAR;. - - - - This book describes the corporate visual identity of &TCP; and - the way it is produced. If you are interested in making &TCP; - a more beautiful project, this book is definitly for you. - - - - To make the information in this book managable, it has been - organized in the following parts: - - - - - - describes the convenctions you should - follow to keep everything organized and consistent inside the - repository directory structure, how to to install and - configure a working copy inside your workstation. At the end - of this part you will find a history of most relevant changes - committed to the repository along the years. - - - - - - describes the corporate visual - identity of the organization known as &TCP; and the production - tasks related to image rendition inside &TCAR;. If you are a - graphic designer, this part of the book might result - interesting to you. - - - - - - describes production tasks related to - content internationalization and localization inside &TCAR;. - If you are a translator, this part of the book might result - interesting to you. - - - - - - describes production tasks related - to content documentation inside &TCAR;. If you are a - documentor, this part of the book might result interesting to - you. - - - - - - describes automation of production - tasks inside &TCAR;. If you are a programmer, this part of the - book might result interesting to you. - - - - - - organizes the licenses mentioned - in this book. - - - - - - - This book assumes you have a basic understanding of &TCD;. If - you need help with it, go to the Help page inside - &TCWIKI; for or a list of different places you can find help. - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository.docbook deleted file mode 100644 index ea8dd86..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository.docbook +++ /dev/null @@ -1,9 +0,0 @@ - - - Repository - - &repo-convs; - &repo-ws; - &repo-history; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository.ent b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository.ent deleted file mode 100644 index f0a40a4..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository.ent +++ /dev/null @@ -1,26 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions.docbook deleted file mode 100644 index 792bcd5..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions.docbook +++ /dev/null @@ -1,17 +0,0 @@ - - - Repository Conventions - - &repo-convs-mission; - &repo-convs-infra; - &repo-convs-worklines; - &repo-convs-directories; - &repo-convs-filenames; - &repo-convs-relbdirs; - &repo-convs-syncpaths; - &repo-convs-extending; - &repo-convs-publishing; - &repo-convs-authoring; - &repo-convs-copying; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/authoring.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/authoring.docbook deleted file mode 100755 index 06a4394..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/authoring.docbook +++ /dev/null @@ -1,30 +0,0 @@ -
- - Repository Authoring - - - The content produced inside &TCAR; is copyright of &TCP;. - This is something you, as author, should be aware of because - you are contributing your creation's rights to someone else; - &TCP; in this case. This way, your work is distributed using - &TCP; as copyright holder, not your name (even - you remain as natural author of the work). Because &TCP; is - the copyright holder, is the license chosen by &TCP; the one - applied to your work, so it is the one you need to agree with - before making a creation inside &TCAR;. - - - - &TCP; 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 desition like the kind of license used inside the project - and subprojects like &TCAR;. - - - - The redistribution conditions of &TCAR; are described in . - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/copying.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/copying.docbook deleted file mode 100755 index 6ecabc2..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/copying.docbook +++ /dev/null @@ -1,60 +0,0 @@ -
- - Repository Copying Conditions - - - &TCP; uses &TCAR; to produce &TCP; corporate visual identity. - - - - The &TCAR; 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 &TCAR;, 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 &TCAR;, 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 &TCAR;. - 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 &TCAR; is released as a GPL work. Individual packages - used by &TCAR; include their own licenses and the &TCAR; - license applies to all packages that it does not clash with. - If there is a clash between the &TCAR; license and individual - package licenses, the individual package license applies - instead. - - - - The precise conditions of the license for the &TCAR; are found - in . This manual specifically - is covered by the conditions found in . - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/directories.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/directories.docbook deleted file mode 100755 index c980bb2..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/directories.docbook +++ /dev/null @@ -1,794 +0,0 @@ -
- - Repository Directory Structure - - - This section describes the directory structure of &TCAR;. You - can use this section as reference to know where the files you - are looking at are stored in and where you can store new - files, as well. This section organizes directories' - description using the same hierarchy the repository has. This - section begins describing the first level of directories in - the repository and continues with each relevant sub-directory - in the hierarchy, one by one. - - - - The directory structure this section describes is based on the - document &TCAR; Directory - Structure, available at: - Documentation/Models/Svg/Repository/directory-structure.svgz - - -
- The <filename class="directory">Artworks</filename> Directory - - This directory contains the files used to produce the - corporate visual identity of &TCP;. The information in this - directory is organized in Brushes, Gradients, Fonts, Images, - Models, Palettes, Patterns and Webenv directories. - - - - - Artworks/Brushes/ - - - This directory contains GIMP brushes. Brushes stored in this - directory will be available inside GIMP's brushes dialog. This - directory organizes brushes files inside Images and Models directories. Inside - Models directory we - find the GIMP projects used to build the brush images. - - - - - - Artworks/Patterns/ - - - This directory contains GIMP patterns. Patterns stored in this - directory will be available inside GIMP's patterns dialog. This - directory organizes patterns files inside Images and Models directories. Inside - Models directory we - find the GIMP projects used to build the pattern images. - - - - - - Artworks/Gradients/ - - - This directory contains GIMP gradients. Gradients stored in - this directory will be available inside GIMP's gradients - dialog. This directory organizes gradient files inside - Images and Models directories. Inside - Models directory we - find the GIMP projects used to build the gradient images. - - - - - - Artworks/Fonts/ - - - This directory contains font files. Font files stored in this - directory will be available to be used from applications like - GIMP and Inkscape. This directory organizes font files inside - Images and Models directories. Inside - Models directory we - find the Fontforge projects used to build the font files, - which are stored in the Images directory. - - - - - - Artworks/Images/ - - - This directory contains final images. The directory structure - used to organize files here is rather similar to that used in - Artworks/Models/ - directory structure. - - - - - - Artworks/Images/Themes/ - - - This directory contains image files rendered from design - models that use theme background images. In this location you - can also find design models used to create the background - images, too. - - - - Design models used to build themes' background images must not - be moved to Artworks/Models/Themes/ directory - structure. Design models used to build themes' background - images are theme-specific, so they must be inside Artworks/Images/Themes/ directory - structure. - - - - - - - Artworks/Images/Themes/${THEME_NAME}/ - - - This directory contains theme directory structure - organized in version number. Here, ${THEME_NAME} is a - string of letters representing the name of the theme. In - this string, all letters are written in lowercase except - the first one which must be written in uppercase. - - - - - - Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/ - - - This directory contains the theme directory structure - organized in theme components. Here, ${THEME_VERSION} is a - string with the form M.N, where M and N are integer - numbers from 0 to 9. M is required and .N is optional. - - - - - - Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Backgrounds/ - - - This directory contains theme-specific background images - and design models used to build them. This directory is a - key component of theme concept. It provides background - images to different sizes which are use on different theme - components, as defined by theme design models stored at - Artworks/Models/Themes - directory. - - - - Theme-specific background files - - - - Images/ - Models/ - Description - - - - - 160x600-final.png, 160x600-final.jpg - 160x600-final.svgz, - 160x600-final.xcf - Graphic design at 160x600 pixels, used to - produce the left-side bar of Firstboot - theme component. - - - 200x150-final.png, 200x150-final.jpg - 200x150-final.svgz, 200x150-final.xcf - Graphic design at 200x150 pixels, used to produce - the screenshot of both - Gdm and Kdm theme - components. - - - - 400x300-final.png, 400x300-final.jpg - 400x300-final.svgz, 400x300-final.xcf - Graphic design at 400x300 pixels, used to - produce the splash component of both - Gnome and Kde theme - components. - - - 490x200-final.png, 490x200-final.jpg - 490x200-final.svgz, 490x200-final.xcf - Graphic design at 490x200 pixels, used to - produce the splash image of Anaconda - theme component. - - - 510x300-final.png, 510x300-final.jpg - 510x300-final.svgz, 510x300-final.xcf - Graphic design at 510x300 pixels, used to - produce the slide images of Anaconda theme component. - - - 640x300-final.png, 640x300-final.jpg - 640x300-final.svgz, 640x300-final.xcf - Graphic design at 640x300 pixels, used to - produce the splash image of Syslinux - theme component. - - - 640x480-final.png, 640x480-final.jpg - 640x480-final.svgz, 640x480-final.xcf - Graphic design at 640x480 pixels, used to - produce the splash image of Grub theme - component. - - - 744x1052-final.png, 744x1052-final.jpg - 744x1052-final.svgz, 744x1052-final.xcf - Graphic design at 744x1052 pixels, used to - produce the Posters theme components. - - - 800x600-final.png, 800x600-final.jpg - 800x600-final.svgz, 800x600-final.xcf - Graphic design at 800x600 pixels, used to - produce the Concept theme component. - - - 800x88-final.png, 800x88-final.jpg - 800x88-final.svgz, 800x88-final.xcf - Graphic design at 800x88 pixels, used to - produce the heading image of Anaconda - theme component. - - - -
- - - Besides background files described in , you'll also find - background files for specific screen resolutions. The - number of files you find here may vary depending the - screen resolutions demanded by &TCD; at /usr/share/backgrounds/. - Resolution-specific background files follow the same name - convention described in the table above but change the - resolution numbers to show the screen resolution they - represent (e.g., 1360x768-final.png - for 1360x768 screen resolutions.). - - - The word -final is used on background files - to mark them as ready for applying. When you design - background images, you might need to create intermediate - images so as to reach desired effects by combining them - into a final one. Such intermediate images do not use the - word -final. Only the result of all your - combinations and tests must have the word - -final on its name. - - - - - - Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Backgrounds/Images/ - - - This directory contains theme-specific background images, - mostly in PNG and JPG formats. The files in this - directory are used by centos-art.sh - script to produce theme components. The relation between - image files and theme component is described in . - - - - - - Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Backgrounds/Models/ - - - This directory contains theme-specific background design - models, mostly in SVGZ and XCF formats. The files in this - directory are used to produce theme-specific background - images, only. - - - Design models in this directory must not be confused with - design models stored in Artworks/Models/Theme/ - directory. Design models stored in this directory are - theme-specific while design models stored in Artworks/Models/Theme/ are - common to all themes. - - - - - - Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Concept/ - - - This directory contains theme-specific conceptual ideas. - The images in this directory can be used to present the - theme's artistic motif in the community. These images - include can include theme name, theme version, theme - author, theme license, theme copyright and similar - information. - - - - - - Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Distro/ - - - This directory contains theme-specific images for each - component of &TCD;. In this location, images are organized - in distribution major release, distribution component and - language, if the current locale is different from English - language. - - - - - - Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Gradients/ - - - This directory contains theme-specific GIMP gradients. - - - - - - Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Palettes/ - - - This directory contains theme-specific GIMP palettes. - The centos-art.sh script uses theme-specific palettes to produce indexed - images with reduced number of colors used by specific - theme components, like Syslinux and - Grub. These components have specific color - requirements which we must comply with. - - - - , describes - the palettes files used inside themes and the number of - colors they require. - - - - Theme-specific palette files - - - - File - Description - - - - - syslinux.gpl - - This palette is used to produce Syslinux final image. - This palette must be created to hold 16 colors using GIMP's - palette format. Inside the palette file, the color - information is organized in an index that begins at 0 - and ends at 15. In this index, the color information - set at position 0 must be the background color used in - the image (e.g., the darkest color in the list) and - the color information set at position 7 must be the - foreground color used in the image (e.g., the lightest - color in the list). - - - - grub.gpl - This palette is used to produce Grub final image. - This palette must be created to hold 14 colors using - GIMP's palette format. Inside the palette file, color - information can be set in any order. - - - -
- - - - To produce optimum palettes of colors, open with GIMP the - full-colored PNG image you need to reduce colors to and - reduce colors using GIMP's indexing tool at - Mode → - Indexed... from - Image menu. Later, you import the set - of colors into a new palette using the GIMP palettes - editor and save it here. This way, you can grantee - centos-art.sh script will use the - correct color information when it produces images with - reduced colors for theme-specific components. - - - - - - When you create theme-specific palettes, it is necessary - that you fill the comment field of palette file using the - related color information in hexadecimal format. - Otherwise, centos-art.sh script won't be able to realize - image conversion from PNG to LSS format. - - - - - - - - Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Patterns/ - - - This directory contains theme-specific GIMP patterns. - - - - - - Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Screenshots/ - - - This directory contains theme-specific screenshots. It is - a series of images illustrating the theme already in - place. Here you'll find one screenshot for each relevant - component inside &TCD;. - - - - - - Artworks/Models/ - - - This directory contains design models (e.g., scalable vector - graphics using the .svgz extension) and image - configuration files (e.g., plain text using the .conf extension) used by - centos-art.sh script to produce images - inside Artworks/Images/. Relevant - components inside this directory include Brands, Icons, Themes - and Webenv. - - - - - - Artworks/Models/Brands/ - - - This directory organizes branding information for &TCP;. - Relevant components inside this directory include Logos/, - Symbols/, and Types/ directories. If you need to tune up &TCP; - branding information, this is the directory you need to go to. - To know more about &TCB;, see . - - - - - - Artworks/Models/Icons/ - - - This directory organizes icon design models for &TCP;. By - default, &TCD; uses the same icons set packaged inside the - SRPMs the upstream provider makes available. Only icons related - to branding information are changed in order to identify - &TCP; and comply with upstream redistribution guidelines. This - directory is not very used by now, it presently contains - design models for Tango's icons set. - - - - - - Artworks/Models/Themes/ - - - This directory contains design models organized by categories. - When you are producing theme-specific images, you can use the - option to instruct the - centos-art.sh script what of these - categories you want to use as reference to produce - theme-specific images. - - - - - - Artworks/Models/Themes/Default/ - - - This directory contains default design models used to produce - theme-specific images, when the - is not provided to - centos-art.sh script at theme-specific - images rendition time. This directory is also used as - reference by centos-art.sh script to build - the theme-specific directory structures inside Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/ - directory, when the - functionality is executed. So, if you find that some - directories in this location are empty, don't remove them. - They should be present in order for - centos-art.sh script to prepare - theme-specific directory structures correctly. - - - - - - Artworks/Models/Themes/Default/Concept/ - - - This directory contains design models used to produce the - conceptual presentation of each theme. This is a 800x600px - image that illustrate the background artistic motif along the - license and copyright information. All images produced from - this design model use the CC-SA license and &TCP; as copyright - holder. - - - - - - Artworks/Models/Themes/Default/Distro/ - - - This directory contains design models used to produce the - visual style of each component inside &TCD; for all its major - releases. The first sub-directory level under this directory - will contain the major release which components will be - produced for. Inside the release-specific directory you will - find one directory for each related distribution component, - including Grub, - Anaconda, - Gdm, - Syslinux, - Firstboot and others. - - - - The components you find inside &TCD; may vary from one major - release to another. They might be added or removed as required - in each new major release. Thus, it is very important to keep - the relation between components and major releases accurate - inside this directory. - - - - - - - Artworks/Models/Themes/Default/Media/ - - - This directory contains design models used to produce visual - style for installation media, including CDs, DVDs, LiveCDs and - LiveDVDs. We don't use release-specific directories in this - location because it is determined automatically from the - /etc/redhat-release file or the - option through the command-line - of centos-art.sh script. - - - - - - Artworks/Models/Themes/Default/Palettes/ - - - This directory contains the palettes of colors used by - centos-art.sh script when no one is found - inside Artworks/Images/Themes/${THEME_NAME}/${THEME_VERSION}/Palettes/ - directory. - - - - - - Artworks/Models/Themes/Default/Gradients/ - - - This directory is empty. It is used to build theme-specific - directory structures. Don't remove it. - - - - - - Artworks/Models/Themes/Default/Patterns/ - - - This directory is empty. It is used to build theme-specific - directory structures. Don't remove it. - - - - - - Artworks/Models/Themes/Default/Posters/ - - - This directory contains design models used by - centos-art.sh script to produce posters. - Posters are promotional stuff, generally printed in different - media and sizes to be shown on events. - - - - - - Artworks/Models/Webenv/ - - - This directory contains common design models used by &TCWE;. - These images include, admonition icons, heading backgrounds, - html backgrounds, admonition backgrounds and whatever - graphical information &TCWE; could need. - - - - - - Artworks/Palettes/ - - - This directory contains GIMP palettes that you always want to - have available in GIMP sessions. - - - - - - Artworks/Patterns/ - - - This directory contains GIMP patterns that you always want to - have available in GIMP sessions. - - - - - - Artworks/Webenv/ - - - This directory contains customizations for specific web - applications. The kind of files you find here vary from one - web application to another. Generally, you find .css and .html files here. Relevant - components inside this directory include Docbook, Httpd, - Mantis, Moin, PhpBB, Punbb, Puntal, Style-guide, Texi2html and - Trac. - - - - - -
- -
- The <filename class="directory">Documentation</filename> Directory - - This directory contains documentation related to &TCAR; - written in different formats. This directory is organized in - Models and Manuals. Models contain the documentation source - files and Manuals the final documentation ready to be read - through different media (e.g., online and paper). Here, the - language used to write documentation manuals is English. - - - - - Documentation/Models/ - - - This directory contains documentation source formats used - inside &TCAR;. - - - - - - Documentation/Models/${MANUAL_FORMAT}/ - - - This directory contains documentation manuals' name for - specific documentation formats. - - - - - - Documentation/Models/${MANUAL_FORMAT}/${MANUAL_NAME}/ - - - This directory contains the documentation manual directory - structure. Here is where source files are stored in. If you - want to modify content from a documentation manual, this is - the directory level you need to go to. - - - - - - Documentation/Manuals/ - - - This directory organizes documentation final files, organized - by documentation format, documentation manual name and - documentation language, if documentation files were produced - to a language different from English. - - - - - - - - Several documentation formats have been used to write &TCAR; - documentation manuals through time, including - Texinfo, - LaTeX and finally - DocBook. From these documentation - formats, DocBook is addressed to be the one adopted in the - near future as default documentation format inside &TCAR;. - Support for other documentation formats will remain inside - centos-art.sh script without further - improvements. This in order to dedicate more attention to - DocBook documentation format. - - - - The directory structure used by each documentation format is - not described in this section. To know more about - documentation formats and the directory structure used by - documentation manuals, read . - - -
- -
- The <filename class="directory">Localization</filename> Directory - - ... - -
- -
- The <filename class="directory">Automation</filename> Directory - - ... - -
- -
- The <filename class="directory">Packages</filename> Directory - - ... - -
- -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/extending.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/extending.docbook deleted file mode 100755 index a270e5a..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/extending.docbook +++ /dev/null @@ -1,44 +0,0 @@ -
- - Extending Repository Layout - - - Occasionly, you may find that new components of &TCPCVI; 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 build 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 - Identity/Images/Themes - directory stores artistic motifs of different themes, the - Identity/Models/Themes - directory stores design models for themes, the Manuals directory stores - documentation, the Locales stores translation - messages, and the Scripts stores automation - scripts. - - - - The best suggestion we can probably give you would be to send - a mail with your questions to the CentOS developers mailing - list (centos-devel@centos.org). - This is the place where development of &TCAR; takes place and - surely, in community, it will be possible to find a place for - your new component inside the repository. - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/filenames.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/filenames.docbook deleted file mode 100755 index c43fada..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/filenames.docbook +++ /dev/null @@ -1,185 +0,0 @@ -
- - Repository File Names - -
- Regular Files - - - Inside &TCAR;, 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. - - -
- Files Written Correctly - - The following file names are written correctly: - - - - - 01-welcome.png - - - - - splash.png - - - - - anaconda_header.png - - - -
- -
- Files Written Incorrectly - - The following file names are written incorrectly: - - - - - 01-Welcome.png - - - - - -welcome.png - - - - - Splash.png - - - - - AnacondaHeader.png - - - -
- -
- Exceptions - - When you name files, consider the following exceptions: - - - - - In the very specific case of repository documentation entries - written in Texinfo format, file names follow the directory - structure naming convenction. This is because they are - documenting directories and that is something - we want to remark. So, to better describe what we are - documenting, files related to documentation entries follow the - name convenction used by the item they document. - - - - -
- -
- -
- Symbolic Links - - Inside &TCAR;, symbolic link names follow the same - convenctions described in . - -
- -
- Directories - - Inside &TCAR;, 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. - - -
- Directories Written Correctly - - The following directory names are written correctly: - - - - - Identity, - Themes, - Motifs, - TreeFlower - - - - - Tcar-ug - - - - - 0.0.1, 0.0.1-35 - - - -
- -
- Directories Written Incorrectly - - The following directory names are written incorrectly: - - - - - identitY, - theMes, - MOTIFS, - treeFlower - - - - - tcar-ug - - - - - .0.1, .0.1-35 - - - -
- -
- Exceptions - - When you name directories, consider the following exceptions: - - - - - No one so far. - - - -
- -
- -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/infra.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/infra.docbook deleted file mode 100755 index 69f49ba..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/infra.docbook +++ /dev/null @@ -1,142 +0,0 @@ -
- - Repository Infrastructure - - - &TCAR; 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. - - -
- Repository infrastructure - - Repository infrastructure - - - - - - -
- -
- Subversion - - - The current infrastructure that holds &TCAR;, on the Internet, - is made of the following components: - - - - - - Subversion - — Modern Version Control System designed to replace CVS. - - - - - 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. - - -
- -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/mission.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/mission.docbook deleted file mode 100755 index 32c6a9d..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/mission.docbook +++ /dev/null @@ -1,9 +0,0 @@ -
- - Repository Mission - - - &TCAR; exists to produce &TCP; corporate visual identity. - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/publishing.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/publishing.docbook deleted file mode 100755 index 71bcd14..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/publishing.docbook +++ /dev/null @@ -1,59 +0,0 @@ -
- - 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 commit them up - to the central repository the working copy you are using was - initially downloaded from. To commit your changes up to the - central repository you use the commit - command from the Subversion's client you've installed in your - workstation. - - - - Initially, when you get registered inside &TCAR;, you won't be - able to publish your changes to &TCAR; immediatly. It is - necessary that you prove your interest in contributing first - sending a mail to the CentOS - Developers mailing list (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, 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 &TCAR; to accomplish its mission (see ). - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/relbdirs.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/relbdirs.docbook deleted file mode 100755 index 835f241..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/relbdirs.docbook +++ /dev/null @@ -1,157 +0,0 @@ -
- - Repository Path Relations - - - In order for automation scripts to produce content inside a - working copy of &TCAR;, it is required that all work lines be - related somehow. The automation scripts take the relation - between work lines as reference to determine the place the - information they will work with will be retrieve from (e.g., - scalable vector graphics, documentation, translations, etc.), - as well as the place where it will store the final files - produced as result of automation process (e.g., portable - network graphics, documentation ready for printing and reading - online, etc.). - - - In order to implement the relation between work lines it is - required to establish a path name convenction, so we can - conceptually organize different components and relate them one - another using predictable path constructions in a scalable - way. Based on this need, we identify three different path - types inside &TCAR;. These path types are: Output - Paths, Input Paths, and - Auxiliary Paths. - - -
- Output Paths - - - The output paths point to directories inside the working copy - which contain files produced from files inside the input - paths. For example, the following paths are consider as output - paths: - - - - - - Identity/Images/Brands/ - - - - - Documentation/Manuals/Tcar-ug/ - - - - - Identity/Images/Themes/Modern/2/Distro/5/Anaconda/ - - - - - - Output paths are also known as Render-able - Directories because they are the type of - path you should provide as argument to functionality so as to - produce content through it. - - -
- -
- Input Paths - - The input paths point to a directories inside the working copy - which contain files used to produce files inside output paths. - For example, the following paths are considered as input - paths: - - - - - - Identity/Models/Brands/ - - - - - Documentation/Models/Tcar-ug/ - - - - - Identity/Models/Themes/Default/Distro/5/Anaconda/ - - - -
- -
- Auxiliary Paths - - - The auxiliary paths point to directories inside the working - copy which contain files used to create modified instances of - inside input paths which are use in turn to produce files - inside output paths. For example, the following paths are - considered as auxiliary paths: - - - - - - Identity/Images/Brands/ - - - - - Locales/Documentation/Models/Docbook/Tcar-ug/es_ES/ - - - - - Locales/Identity/Models/Themes/Default/Distro/5/Anaconda/es_ES/ - - - - - - The relationship between input, output and auxiliary paths is - created by combining the first directory level of input paths - with the first directory level in the repository directory - layout. In the repository directory layout, the first level - includes the Identity, - Documentation and - Scripts directories. - These directories are always used to create input and output - paths. The Locales - directory, on the other hand, is always used to create - auxiliary paths only for input paths available under Identity, Documentation and Scripts directories. - - - - For example, if the LANG environment - variable is set to es_ES.UTF-8 and you execute - the functionality of - centos-art.sh script with the Documentation/Manuals/Docbook/Tcar-ug/ - input path as argument, it will produce &TCARUG; in Spanish - language using translation messages from - Locales/Documentation/Models/Docbook/Tcar-ug/es_ES/ - auxiliary path and would save final documentation files under - Documentation/Manuals/Docbook/Tcar-ug/es_ES/ - output path. - - -
- -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/syncpaths.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/syncpaths.docbook deleted file mode 100755 index d8e353d..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/syncpaths.docbook +++ /dev/null @@ -1,99 +0,0 @@ -
- - Syncronizing Repository Paths - - - Once both master and auxiliar paths have been related in the - repository, they shouldn't be changed except you absolutly - need to do so. In this cases, when you need to change master - or auxiliar paths, it is required that you also change the - relation between them so as to retain their bond. This - process of keeping master and auxiliar paths - connected between themselves is known as - path syncronization. - - - - Path syncronization is required for automation scripts to know - where to store final output, where to retrive translation - messages from, and whatever information you might need to - count with. If the relation between master paths and auxiliar - paths is lost, there is no way for automation scripts to know - where to retrive the information they need to work with or - where to store the output information produced from it. - Through path syncronization we organize and extend the content - production inside the repository. - - - - Path syncronization affects both movement of files and - replacement of content inside files. Movement of files is - related to actions like renaming files and directories inside - the repository. Replacement of content inside files is - related to actions like replacing information (e.g., paths - information) inside files in order to keep file contents and - file locations consistent one another after a file has been - moved. - - - - The order followed to syncronize path information is very - important because the versioned nature of the files we are - working with. When a renaming action needs to be performed - inside the repository, we avoid making replacements inside - files first and file movements later. This would demand two - commit actions: one for the files' internal changes and - another for the file movement itself. Instead, we prefer to - perform file movements first and files' internal replacements - later. This way it is possible to commit both changes as if - they were just one. - - - - - There is no support for URLs actions inside - centos-art.sh script. The - centos-art.sh script is designed to work - with local files inside the working copy only. If you need to - perform URL actions directly, use Subversion's commands - instead. - - - - - At this moment there isn't full implementation of path - syncronization inside centos-art.sh script - and that is somthing we need to do oursleves. However, the - texinfo backend inside the - help functionality does provide a restricted - implementation of path syncronization to documentation area - through the , - and options. You can read this - implementation and use it as reference to implement path - syncronization in other areas. - - - - The plan for a full implementation of path syncronization - inside centos-art.sh script would be to - create individual restricted implementations like the one in - texinfo backend for other areas that demand it - and then, create a higher implmentation that combines them all - as needed. This way, if we try to rename a repository - directory, the higher action can know which are all the - restricted actions that should be performed in order - to make the full path syncronization. - - - - For example, if the directory we are renaming is a master - path, it is required to syncronize the related output and - localization auxiliar paths. On the other hand, if the - directory we are renaming through full path syncronization is - an auxiliar path, it is required to determine first what is - the related master path and later, perform the syncronization - from master path to auxiliar paths as if the path provided - would be the master path not the auxiliar path. - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/worklines.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/worklines.docbook deleted file mode 100755 index f31dd87..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Conventions/worklines.docbook +++ /dev/null @@ -1,186 +0,0 @@ -
- - Repository Work Lines - - - The content production inside &TCAR; 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 &TCP;). 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 &TCAR; 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. - - -
- - Artworks - - - Artworks is the first component we work - out in order to produce new corporate visual identities. - Through this work line, graphic designers create - models and motifs for all the - visual manifestation &TCP; is made of. Once design models and - artistic motifs are set in place, graphic designers use the - functionality to - combine them into final images. - - - - The mission of Artworks work line is - define all the visual manifestations the &TCP; is made of and - provide design models and artistic motifs for them in order to - produce the image files required to transmit the visual style - that identifies &TCP; as unique organization. - - - - To know more about &TCPCVI;, read . - - -
- -
- - 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 functionality 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 localization process takes place inside the - Localization/ directory - in the first level of each repository directory structure. - This directory mirrors the renderable directory structures - outside it and stores .po and .pot files mainly. - - - - The mission of Localization work line is - extend 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 &TCP; in their own native languages. - - - - To know more about the specific localization process read - . - - -
- -
- - Documentation - - - The documentation work line is the third component that must - be worked out in the corporate identity production cycle. - Through this work line documentors settle down the conceptual - and practical used to edificate &TCAR;. To write - documentation, documentors use the help - functionality described in which provides a consistent interface for building - documentation through different documentation backends (e.g., - Texinfo, DocBook, LaTeX, etc.). - - - - The main purpose of this work line is describe the standard - procedures &TCAR; realies on, as well as conceive a place to - help you understand what &TCAR; is and what can you do with - it. - - - - The documentation work line takes palce in the Manuals directory. - - -
- -
- 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 art works and - put all together inside RPM packages. For this purpose, - packagers use the pack describe in - which provides a - consistent interface for building packages inside the - repository. - - - - The main purpose of this work line is pack all the information - &TCP; requires to rebrand &TCD; according Red Hat - redistribution guidelines. - - - - The packages work line takes palce in the Packages directory. - - -
- -
- - 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, documentors, - translators and packagers need to make their work consistent - and reusable. For this purpose, programmers develop the - centos-art.sh script described in . - - - - The main purpose of this work line is standardize the - interaction of work lines in a reliable way. - - - - The automation work line takes palce in the Scripts directory. - - -
- -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History.docbook deleted file mode 100644 index ca54c8a..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History.docbook +++ /dev/null @@ -1,17 +0,0 @@ - - - Repository History - - - This chapter summarizes relevant changes committed to &TCAR; - along the years. - - - &repo-history-2008; - &repo-history-2009; - &repo-history-2010; - &repo-history-2011; - &repo-history-2012; - &repo-history-2013; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2008.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2008.docbook deleted file mode 100644 index aff53c8..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2008.docbook +++ /dev/null @@ -1,67 +0,0 @@ -
- - 2008's - - - &TCAR; started at The CentOS Developers - Mailing List around 2008, on a discussion about how to - automate slide images used by Anaconda (&TCD; installer). In - such discussion, Ralph - Angenendt rose up his hand to ask —Do you have - something to show?—. - - - - To answer the question, Alain Reguera - Delgado suggested a bash script which combined SVG and - SED files in order to produce PNG images in different - languages —in conjunction with the proposition of - creating a Subversion repository where translations and image - production could be distributed inside &TCC;—. - - - - Karanbir - Singh considered the idea intresting and provided the - infrastructure necessary to support the effort. This way, - &TCAS; and &TCAR; were officially created and made world wide - available. In this configuration, users were able to register - themselves and administrators were able to assign access - rights to registered users inside &TCAR;, both using a web - interface. - - - - Once &TCAR; was available, Alain Reguera Delgado uploaded the - bash script used to produce the Anaconda - slides;See Ralph Angenendt documented it very - well;See and people started to download working - copies of &TCAR; to produce slide images in their own - languages.See the following Google - search. - - - - From this time on &TCAR; has been evolving into an automated - production environment where &TCC; can conceive &TCP; - corporate visual identity. - - - - The exact changes commited to &TCAR; through history can be - found in the repository - logs so you can know the real history about it. For - those of you who just want to get a glance of changes - committed, see . - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2009.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2009.docbook deleted file mode 100644 index 725ca9c..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2009.docbook +++ /dev/null @@ -1,55 +0,0 @@ -
- - 2009's - - - 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 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 &TCARUG; was - initiated. - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2010.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2010.docbook deleted file mode 100644 index 4faacb0..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2010.docbook +++ /dev/null @@ -1,78 +0,0 @@ -
- - 2010's - - - 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 &TCW;. - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2011.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2011.docbook deleted file mode 100644 index 69f840d..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2011.docbook +++ /dev/null @@ -1,51 +0,0 @@ -
- - 2011's - - - 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 &TCAR; - 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. - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2012.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2012.docbook deleted file mode 100644 index cf81287..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2012.docbook +++ /dev/null @@ -1,431 +0,0 @@ -
- - 2012's - - - &TCAR; 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. - - - - Make Localization Of <command>centos-art.sh</command> - 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. - - - - - 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 and respectively. - - - - - - 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. - - - - Directory structure of a rendering-only context - - 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 - - - - - - - - A practical example of using the solution described above may - be found when you are working on the corporate identity of - &TCP; and then need to start a new corporate identity project - for another organization. You want to keep the directory - structure of &TCAR; 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 - &TCP; (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 &TCAR; has been integrated into the working copy of - your new project. - - - - Mixing automation functionalities. - - Mixing automation functionalities. - - - -/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 &TCAR;. In this environment, all updates - commited to the Render, - Locales and Commons directories at &TCAR; - 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 &TCAR; 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 &TCP;. You probably need to - change this if you are producing images to a different - organization than &TCP;. 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 &TCP;. - - - - 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 - specific functionality uses SVG files as - reference to build images (i.e., one SVG - image produces one PNG image). - - - - - - Modify 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 - - 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. - - - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2013.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2013.docbook deleted file mode 100644 index 290647a..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/History/2013.docbook +++ /dev/null @@ -1,141 +0,0 @@ -
- - 2013's - - - &TCAR; development was eventually stopped at November, 2012, - when I moved myself from Cienfuegos to Havana city for working - The first months were very difficult, specially at the moment - of finding a stable place to set my personal desktop (I was - moving myself from one apartment to another, frequently). - - - - On May 14th, the work in Havana ends for me and I have to - return to Cienfuegos city. I tried to take advantage of the - situation dedicating more work and study hours to &TCAR; and - the related automation scripts once again. At this point I - consider a Git+Gitolite+Gitweb+MantisBT infrastructure for - &TCAR; and start working on it in my workstation. This, in - order to implement a distributed work flow for &TCAR; based on - Git version control system. - - - - Update Version Control Environment - - The function environment related to version control tasks was - renamed from svn to in order to handle both - Subversion and - Git working copies of &TCAR;. This - change prepares the centos-art.sh script to - follow the suggestion of a complete migration from - Subversion to - Git, at some point. - - - - Because the Subversion - infrastructure is the one in place right now and it is the one - with most artwork history, it will be - Subversion the version control - system we are using as default in - centos-art.sh. However this will surely - change as soon as a Git - infrastructure be approved for &TCAR; and everything could be - moved there. - - - - - Start Using The <filename>centos-art.conf</filename> File - - Based on the need of supporting more than one application to - handle version control tasks, it was added the - centos-art.conf file into the Scripts/Bash directory. This file - exists to customize specific behaviours of - centos-art.sh script once it has been - executed (e.g., what kind of application will be used as - default for doing version control, or even if the actions - related to version control will be performed or not). - - - - - - 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 &TCAR; 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. See - . - - - - 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 &TCAR; 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, &TCAR; directory - structure needs to be reorganized to better delineate each - component the repository is made of. - - - - For more information see . - - - - - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation.docbook deleted file mode 100644 index cf55d5e..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation.docbook +++ /dev/null @@ -1,9 +0,0 @@ - - - Preparing Your Workstation - - &repo-ws-intro; - &repo-ws-install; - &repo-ws-config; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation/config.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation/config.docbook deleted file mode 100644 index 8ad40d0..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation/config.docbook +++ /dev/null @@ -1,351 +0,0 @@ -
- - Configuring 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 &TCAR; 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. - - - - - Do not use the root username for regular - tasks inside your working copy of &TCAR;. This is dangerous - and might provoke unreversable 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 &TCAR; inside your home directory. This - desition 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 &TCAR; 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 through dynamic expansion - - Most of the absolute paths we use inside the working copy are - made of two parts, one dynamic and one relative fixed. The - dynamic part is the home directory of the current user and its - value can be retrived from the $HOME - environment variable. The fixed part of the path is the one - we set inside the repositroy structure itself as a matter of - organization. What we need here is to find a way to expand - variables inside files that don't support variable expansion. - This alternative had worked rather fine when we produce - produce PNG files from SVG files and XTHML from DocBook files, - but the same is not true for absolute paths inside files that - are used as in their permanent state inside the repository - (e.g., CSS files and other files similar in purpose). - -
- -
- Different absolute paths, dynamic expansion, symbolic - links, relative links, and environment variables - - - With this solution it is possible to store working copies of - &TCAR; 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 &TCAR; 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. - - - - Bacause 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 &TCAR; 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 &TCAR; 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 https://projects.centos.org/~al/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 - &TCAR;. If you want to have your working copy in a location - different to that one shown above, see . - - - - 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 &TCPCVI;. - - -
- -
- Configure Administrative Tasks - - - Most of the administrative tasks you need to perform in your - working copy of &TCAR; 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 . - - - - The <filename>/etc/sudoers</filename> configuration file - - /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 - - - - - - -
- -
- Run Preparation Tool - - Once you've both downloaded a working copy from &TCAR; - and configured the sudo's 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 - - - To know more about the prepare - functionality of centos-art.sh script, see - . - -
- -
- Changing Your Working Copy Default Path - - By default your working copy should be store in your home - directory, specifically in the location ~/artwork. This location may not - be the final location where you want to have your working copy - in situations where you are working on several projects at the - same time or you already have a define location to organize - your projects inside your home directory. Thus, you may need - to change the default location of your working copy to a more - appropriate location. - - - - The default path to your working copy is controlled by the - TCAR_WORKDIR environment variable. This - variable is firstly defined in your personal profile after - running the prepare functionality of - centos-art.sh script. So, to change the - path of your working copy correctly, do the following: - - - - - - Create the parent directory you will use to store your working - copy. For example: - mkdir -p ~/Projects/CentOS - - - - - Move the currently downloaded working copy from ~/artwork to - your new location. For example: - mv ~/artwork ~/Projects/CentOS/ - - - - - Update the environment variables set in - ~/.bash_profile by running the - centos-art.sh script from the new location. - For example: - ~/Projects/CentOS/artwork/Scripts/Bash/centos-art.sh prepare --set-environment - - - - - Do log out from your active user's seesion and do log in again - so the environment changes take effect. Or just update the - current environment information by running the following - command: - . ~/.bash_profile - - - - - Update internal links by running the - centos-art.sh script. For example: - ${TCAR_WORKDIR}/Scripts/Bash/centos-art.sh prepare --links - - - - -
- -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation/install.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation/install.docbook deleted file mode 100644 index 46d30a9..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation/install.docbook +++ /dev/null @@ -1,41 +0,0 @@ -
- - Installing Your Workstation - - - To install your workstation use &TCD; default configuration as - proposed by &TCD; installer. This includes default - partitioning and packages. &TCAR; is been completly develop - upon &TCD; and realies on such environment to achieve most - automation tasks. In order to get a reproducable environment, - it is convenient that you, too, use the same operating system - that we do. - - -
- Supported Platforms - - - &TCAR; has been tested in the following platforms: - - - - - - The CentOS Distribution major release 5 update 5, for i386 and - i686 architectures. - - - - - - In case you be using a working copy of &TCAR; in a different - platform from those listed here, please send a mail to centos-devel@centos.org - notifying it. It is our intention to make &TCAR; as portable - as possible through different major releases of &TCD;. - - -
- -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation/intro.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation/intro.docbook deleted file mode 100644 index d6677cc..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/Workstation/intro.docbook +++ /dev/null @@ -1,27 +0,0 @@ -
- - Introduction - - - The workstation is the machine you use to store your working - copy of &TCAR;. The working copy is an ordinary directory - tree on your workstation, containing a collection of files - that you can edit however you wish. The working copy is your - own private work area related to &TCAR; where you perform - changes and receive changes from others. - - - - In order to make your workstation completely functional, it is - necessary that you install it and configure it to satisfy the - needs demanded by the working copy of &TCAR; you later - download in it. - - - - This chapter describes the steps you need to follow in order - to install and configure a workstation for using a working - copy of &TCAR; in all its extention. - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/introduction.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/introduction.docbook deleted file mode 100644 index a059dc5..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Repository/introduction.docbook +++ /dev/null @@ -1,120 +0,0 @@ -
- - Overview - - - The corporations always have a corporate identity, even when - they don't take an intentional control over it. It is a choise - from the corporation to define how much control to take over - its identity. This kind of control is expensive and not all - corporations are able to maintain it. However, it is - necessary that, based on pragmatic facts, the corporation - assume an acceptable degree of compromise with its identity in - order to create a consistent idea of itself in a way that can - be progresively improved through time. - - - - During the years (2003-2009), we've seen a growing interest - inside &TCC; for helping on &TCP; development. Some people - seem to be very clear about what the project needs are and how - to maintain it being a very stable project, but others however - don't to get what &TCP; is (even it is explained time after - time) and sometimes decide to put their efforts in the wrong - direction making everything to be a waste of time and source - of distraction from what is really needed. - - - - &TCAR; phases the question What can I do for - &TCP;? by identifying different work lines you can - join in and providing automated production mechanisms that - complement one another according to each work line needs so - consistent results can be achieved inside a distributed - environment under version control. For example, consider an - environment where there are graphic designers to produce - images, documentors to produce documentation manuals (whose - can use images produced by graphic designers), programmers to - produce automation scripts (needed to standardize production - tasks) and translators to localize source files created by - graphic designers, documetors and programmers. Once such - environment has been implemented, it would be possible for - packagers to take localized images and localized documentation - from &TCAR; (through an automation script probably) to - rebrand/update the content of those packages inside &TCD; that - must include information specific to &TCP; itself (e.g., boot - loader, distribution installer, release notes, display - managers, release notes, web browsers default page, etc.). - - - - Most production tasks inside &TCAR; are focused on the files - needed to implement &TCP; corporate visual identity. - - Notice that, here, visual identity means everything - perceived through the human's visual sences (i.e., the - human eyes), but the corporate identity is a wider concept - that extends to all human senses (i.e., visibilty (eyes), - audition (ears), scent (nose), touch (fingers), and savour - (tongue)), not just that one related to visual aspects. - Nevertheless, we need to be consequent with the media - where &TCP; manifests its existence on, as described in - . - This includes everything from file edition - (e.g., text width, text indentation, line numbering, text - tabulation, etc.) up to how the web sites, distribution, and - industrial stuff (e.g., pullovers, caps, installation media, - etc.) look and feel. Notice that, more specific details like - typography, window design, icons, menu items, etc., inside - &TCD; are already covered by &TCP; upstream provider. In our - effort to be 100% binary compatible with the upstream provider - and also keeping maintainance low, we stand over those - specific details as much as possible assuming them as default. - However, if you feel brave enough (and prove your ability to - keep yourself being that way) it would be possible to open a - work line for you to maintain variants of such very specific - details inside &TCAR;. - - - - In addition to visual manifestations, there are also emotional - feelings and ethical behaviours that must be considered as - part of &TCP; corporate identity. A pleasant experience in - this area includes &TCWIKI;, specifically the way it was - conceived and administered. When the &TCWIKI; was published, - &TCP; published a list of needs with it so anyone could - contribute based on them. Not much time after that, the list - of tasks triggered some souls' motivations ruled by the good - will of initiating the translation of that content published - inside the wiki, redesigning its visual style, proposing the - TreeFlower theme for &TCD;, and reducing to zero the - contraditions of precoceived minds with respect, reason and - passion. As result of this experience, we found that &TCC; - posseses an incredible strong creative force, however, a long - path must be traveled before it can be focalized into the - right direction because: it isn't enough just telling what the - right direction is, it is also necessary to provide the - vehicles for &TCC; be able of moving through it. - - - - &TCAR; extends the feelings and ethicals behaviours from - &TCWIKI; to itself by identifying the visual manifestations - &TCP; is made of (i.e., tracing a direction) and allowing - people to develop them through standardized procedures inside - a colaborative environment (i.e., providing the vehicles). - - - - Finally, if you find yourself needing to do something for - &TCP; and &TCAR; isn't the place for it, be sure to define - what that something exactly is and also make it a community - effort so it can be validated as something useful to the - community itself. Otherwise, the effort would loose its - initial sense soon enough so as to be considered seriously. - Notice that the way these needs are described may take - different forms: they can be written and organized inside a - book, an article, or even a well documented program ;-). - - -
diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts.docbook deleted file mode 100644 index 088ba46..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts.docbook +++ /dev/null @@ -1,24 +0,0 @@ - - - Automation - - - - This part of the book describes &TCAR; automation work - line. Through this work line programmers provide the - production standards that graphic designers, - documentalists, translators and packagers need to make - their work consistent and reusable. For this purpose, - programmers develop the centos-art.sh - script and its functionalities. The main purpose of this - work line is standardize the interaction of work lines in - a reliable way. The automation work line takes place in - the Scripts - directory. - - - - &scripts-bash; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts.ent b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts.ent deleted file mode 100644 index 3a8db4c..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts.ent +++ /dev/null @@ -1,16 +0,0 @@ - - - - - - - - - - - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash.docbook deleted file mode 100644 index 33a1e2f..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash.docbook +++ /dev/null @@ -1,23 +0,0 @@ - - - The <command>centos-art.sh</command> Reference - Version 0.4 - - - &scripts-bash-intro; - &scripts-bash-mission; - &scripts-bash-nameconvs; - &scripts-bash-cliref; - &scripts-bash-environment; - - - &scripts-bash-prepare; - &scripts-bash-help; - &scripts-bash-render; - &scripts-bash-locale; - &scripts-bash-pack; - &scripts-bash-tuneup; - &scripts-bash-vcs; - &scripts-bash-cli_checkFiles; - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/cli_checkFiles.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/cli_checkFiles.docbook deleted file mode 100644 index 74f40a4..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/cli_checkFiles.docbook +++ /dev/null @@ -1,245 +0,0 @@ - - - - cli_checkFiles - 1 - - Standardize constructions for file verifications - - - - - cli_checkFiles - Standardize constructions for file verifications. - - - - - cli_checkFiles - - -d - -e - -f - -h - -x - - LOCATION - - - - - Description - - The cli_checkFiles exists to answer basic - questions like Is LOCATION - is a regular file? and Is - LOCATION a directory?. The - answer to such questions affects the script execution flow in - the following way: when the answer positive (e.g., - LOCATION is a regular file), the - script passes the test silently and continues its execution. - When the answer is negative(e.g., - LOCATION is not a regular file), - the script finishes its execution immediately with an error - message. - - - - The cli_checkFiles function is exported - to centos-art.sh script environment in the - very beginning of its execution and will be available all - along its execution lifetime. You can use this function inside - common and specific functions whenever you need to verify - files inside the &TCAR;. - - - - The cli_checkFiles function is available - inside the centos-art.sh script only as - part of its execution environment. This function is exported - to centos-art.sh script just after - executing the script from the command-line and will be - available all along the script lifetime. So, you can use this - function both in common and specific functionalities of - centos-art.sh script. - - - - The cli_checkFiles function doesn't - create subsequent execution environments. - - - - - Usage - - Use the cli_checkFiles function inside - centos-art.sh script whenever you need to - control the script execution flow based on file type (e.g., - regular files, directories, links, etc.) verifications. - - - - - Options - - The cli_checkFiles function accepts the - following options: - - - - - - - Verifies whether LOCATION exists - and is a directory. If it doesn't exists or isn't a directory, - an error message is printed and the script finishes its - execution. Otherwise, if it exists and is a directory, the - script continues its execution normally. - - - - - - - - - Verifies whether LOCATION exists or - not. If it doesn't exist, an error message is printed and the - script finishes its execution. Otherwise, if it does exists, - the script continues its execution normally. - - - - - - - - - Verifies whether LOCATION exists - and is a regular file. If it doesn't exists or isn't a regular - file, an error message is printed and the script finishes its - execution. Otherwise, if it exists and is a regular file, the - script continues its execution normally. - - - - - - - - - Verifies whether LOCATION exists - and is a symbolic link. If it doesn't exists or isn't a - symbolic link, an error message is printed and the script - finishes its execution immediately. Otherwise, if it does - exist and is a symbolic link, the script continue its - execution normally. - - - - - - - - - Verifies whether LOCATION exists - and execution permission is granted. If it doesn't exist or - hasn't execution permission, the script finishes its execution - immediately. Otherwise, if it exists and has execution - permissions, the script continues its execution normally. - - - - - - - The value of the LOCATION argument - must be an absolute path to the file you want to verify. If - such file doesn't exists in any supported form, the script - finishes its execution with an error message. - - - - - Examples - - The following example was taken from - centos-art.sh script initialization phase. - Notice the position of cli_checkFiles - function inside the loop. If some of the function files we - need to export doesn't have execution rights, - cli_checkFiles will - finish the script execution immediately with an error message. - - -# Process the list of files. -for FUNCFILE in $FUNCFILES;do - - # Verify the execution rights for function file. - cli_checkFiles -x ${FUNCFILE} - - # Initialize the function file. - . ${FUNCFILE} - - # Export the function names inside the file to current shell - # script environment. - export -f $(egrep "${PATTERN}" ${FUNCFILE} | gawk '{ print $2 }') - -done - - - - - Bugs - - To report bugs related to this function, please create a new - ticket at refering the - name of this function clearly and the specific problems you - found in it. - - - - - Authors - - - - Alain Reguera Delgado alain.reguera@gmail.com, =COPYRIGHT_YEAR_LIST= - - - - - - - License - - - Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - - - - 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. - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/cliref.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/cliref.docbook deleted file mode 100644 index a8ff53e..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/cliref.docbook +++ /dev/null @@ -1,569 +0,0 @@ - - - Command-line Interface - - - The centos-art.sh script follows a - conventional GNU/Linux command-line interface where there - might be options and non-option arguments in it. As convention - to centos-art.sh, the first non-option - argument passed through the command-line will be the name of - the specific function you want to execute (e.g., , , , etc.). This first argument - will be immediately removed from the list of arguments passed - to centos-art.sh script leaving just the - remaining options and non-option arguments passed to it. From - this point on, the centos-art.sh script - uses the getopt command to retrieve option - arguments and remove them from the list of arguments passed to - centos-art.sh script. - - - - To better understand the centos-art.sh - command-line interface, consider the command shown in . This example - shows the entire command as a list of space-separated - arguments. Each argument passed in the command-line can be - reached using positional variables as described in . - - - - The command-line interface - - The command-line interface - - - -centos-art render Identity/Images/Themes --with-brands - - - - - - - - Option Arguments - - - As convention inside the centos-art.sh, all - specific function environments should provide support for the - following option arguments: - - - - - | - - - This option makes centos-art.sh to shows - information about the specific function environment (e.g., how - to execute it, available options, etc.) set as first - non-option argument. For example, if you provide the - centos-art render --help, the - centos-art.sh script will display to you - the information related to functionality. - - - This information is retrieved from The CentOS Artwork - Repository File System (tcar-fs) documentation manual. - This manual is written in Texinfo format and provides a quick - way for you to read and browse documentation related to each - directory inside &TCAR; as you work with it from a text - terminal. - - - - - - - - - | - - - This option makes the centos-art.sh script - to suppress messages sent to standard output. This option - doesn't suppress error messages, nor questions related to - script execution. - - - - - - - - The specific option arguments used by function environments - are described individually, as part of each function - environment documentation. To know more about the specific - options used by function environments, see and . - - - - Specific functions environment - - - - Name - Description - - - - - - - Standardize configuration tasks inside &TCAR; - - - - Standardize rendition tasks inside &TCAR; - - - - Standardize localization tasks inside &TCAR; - - - - Standardize documentation tasks inside &TCAR; - - - - Standardize packing tasks inside &TCAR; - - - - Standardize maintainance tasks inside &TCAR; - - - - Standardize version control tasks inside &TCAR; - - - - -
- - - Common functions environment - - - - Name - Description - - - - - - - cli_checkFiles - - - Standardize conditional expressions applied to files - (including links and directories) inside the - centos-art.sh script. - - - - cli_checkRepoDirSource - - Standardize directories' path construction inside the - working copy, using absolute paths. - - - - cli_expandTMarkers - - Standardize translation markers construction and their - related expansion. - - - - cli_exportFunctions - - Standardize the way specific functionalities are - exported to centos-art.sh script - environment. - - - - cli_getConfigLines - - Standardize the way configuration lines are retrieved - form configuration files. - - - - cli_getConfigSectionNames - - Standardize the way section names are retrieved from - configuration files. - - - - cli_getConfigValue - - Standardize the way configuration values are retrieved - from configuration files. - - - - cli_getFilesList - - Standardize the way list of files are built inside - centos-art.sh script. - - - - cli_getPathComponent - - Standardize the way directory structures are organized - inside the working copy of &TCAR;. - - - - cli_getRepoName - - Standardize files and directories name convection - inside the working copy of &TCAR;. - - - - cli_getTemporalFile - - Standardize temporal files creation. - - - - cli_parseArgumentsReDef - - Initiate/reset and sanitize positional parameters - passed to this function and creates the list of - arguments that getopt will process. - - - - cli_parseArguments - - Redefine the ARGUMENTS global - variable using getopt output. - - - - cli_printCopyrightInfo - - Standardize the copyright information printed on - content produced by centos-art.sh - script. - - - - cli_printMailingList - - Standardize the way mailing list addresses are printed - on content produced by - centos-art.sh script. - - - - cli_printMessage - - Standardize the way messages are printed by - centos-art.sh script. - - - - cli_printUrl - - Standardize the way URLs are printed by - centos-art.sh script. - - - - cli_runFnEnvironment - - Standardize the way centos-art.sh - script is called to itself. - - - - cli - - Initiates the centos-art.sh script - command-line interface. - - - - cli_synchronizeRepoChanges - - Standardize the way changes are synchronized between - the working copy and the central repository. - - - - cli_terminateScriptExecution - - Standardize the actions that must be realized just - before leaving the script execution (e.g., cleaning - temporal files). - - - - cli_unsetFunctions - - Unset functionalities from - centos-art.sh script execution - environment. - - - - - - -
- - - - - Non-Option Arguments - - - Once option arguments have been removed from the list of - arguments passed to centos-art.sh - command-line, non-option arguments are processed then. - Non-option arguments will always be paths pointing to - directories inside your working copy of &TCAR; or - documentation entries pointing to specific sections in a - documentation manual. Paths provided in the command-line can - be absolute or relative considering the root directory of the - working copy as start point. For example, both the absolute - path ${HOME}/Projects/CentOS/artwork/Identity/Themes/ - and the relative path Identity/Themes point to - the same location. Documentation entries, on the other hand, - exist to specify the files inside the Documentation/Models/ - directory structure you want to work with, based on specific - documentation manual components (e.g., manual name, part, - chapter or section). To know more about documentation entries, - see the functionality - reference. - - - - - - - Implementation - - - The command-line interface of - centos-art.sh script is implemented - individually for each specific function environments it is - made of. Each specific function environment inside the - centos-art.sh has its own command-line - definition and can differ in options when they are - compared one another. The command-line differences between - specific function environments exist as consequence of the - purpose they were designed for (e.g., different purposes, - different options and arguments). Nevertheless, all - specific function environments use the same base - construction to implement their unique command-line - interfaces (see ). - - - - The specific function environments the - centos-art.sh script is made of use the - Scripts/Bash/Functions/Fname/fname_getOptions.sh - file to store the - fname_getOptions - function definition. This function definition is where you - set the relation between actions to be executed and - arguments passed to centos-art.sh - script. - - - - Basically, when you decide to create new function - environments for the centos-art.sh - script, you need to consider whether they will use - arguments from the command-line or not. When the function - environment doesn't need arguments (e.g., it exists to - redefine values related to variables only) there is not - need to consider a parsing feature for it. However, when - you need to interact with a specific function through the - command-line, you should use the - fname_getOptions - function related to your - fname - function environment to define the way such interaction - will take place. This way you can control the possible - arguments your function environment will be able to - interpret from the command-line. - - - - The command-line implementation - - The command-line implementation - - - -function fname_getOptions { - - # Define short options we want to support. - local ARGSS="h,q" - - # Define long options we want to support. - local ARGSL="help,quiet" - - # Redefine ARGUMENTS using getopt(1) command parser. - cli_parseArguments - - # Redefine positional parameters using ARGUMENTS variable. - eval set -- "$ARGUMENTS" - - # Look for options passed through command-line. - while true; do - - case "$1" in - - -h | --help ) - cli_runFnEnvironment help --read --format="texinfo" "tcar-fs::scripts:bash-functions-fname" - shift 1 - exit - ;; - - -q | --quiet ) - FLAG_QUIET="true" - shift 1 - ;; - - -- ) - # Remove the `--' argument from the list of arguments - # in order for processing non-option arguments - # correctly. At this point all option arguments have - # been processed already but the `--' argument still - # remains to mark ending of option arguments and - # beginning of non-option arguments. The `--' argument - # needs to be removed here in order to avoid - # centos-art.sh script to process it as a path inside - # the repository, which obviously is not. - shift 1 - break - ;; - esac - done - - # Redefine ARGUMENTS variable using current positional parameters. - cli_parseArgumentsReDef "$@" - -} - - - - - - - - Using the base structure described in , you can - create new options so your specific function environment - can express its usefulness. For example, if you want your - specific function environment to print a greeting on the - screen when the option is passed - through its command-line, you can modify the base - structure shown above with the following: - - - -... - - # Define long options we want to support. - local ARGSL="help,quiet,hello" - -... - - --hello ) - cli_printMessage "`gettext "Hello World!"`" - shift 1 - ;; -... - - - - In case you want to provide an option value in the form - , you can do it as described - below: - - - -... - - # Define long options we want to support. - local ARGSL="help,quiet,hello:" - -... - - --hello ) - cli_printMessage "`gettext "Hello"` ${2}" - shift 2 - ;; -... - - - - In this last case, the option value is required. So, if you - provide the option but do not provide - a value for it, an error will be triggered and the script will - finish its execution. To make an option value not-required, - you need to use two colons instead of one when you define the - options, see the following lines: - - - -... - - # Define long options we want to support. - local ARGSL="help,quiet,hello::" - -... - - --hello ) - cli_printMessage "`gettext "Hello"` ${2}" - shift 2 - ;; -... - - - - To know more about the features provided by - getopt command, read its man page (e.g., - typing the man getopt command in your - terminal). This information will also help you to understand - how to improve the command-line interfaces you create for - the function environments of centos-art.sh - script. - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/environment.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/environment.docbook deleted file mode 100644 index fbbcfd9..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/environment.docbook +++ /dev/null @@ -1,475 +0,0 @@ - - - The Execution Environment - - - The execution environment of centos-art.sh - script is organized in four levels. The first level is the - shell environment, the second level is the - command environment, the third level is the - common functions environment and, finally, the - fourth level which contains the specific function - environment, as described in . In this - context, child environments inherit definitions (e.g., - variables and functions) from their parent environments making - possible to logically organize the script in a way that needs - can be isolated one another to follow the paradigm proposed by - Unix developers at Bell Labs when felt that programs - should do one thing well. - - - - The execution environment - - The execution environment - - - -+-----------------------------------------------------+ -| Shell environment | -+---|-------------------|-----------------|-----------+ -. |-- TCAR_WORKDIR |-- TCAR_BRAND |-- EDITOR . -. |-- LANG |-- HOME |-- PATH . -. `-- centos-art.sh `-- TMPDIR `-- ... . -. +---|-----------------------------------------+ . -. | Command environment | . -. +---|---------------|----------------|--------+ . -. . |-- CLI_NAME |-- CLI_VERSION `-- ... . . -. . |-- CLI_FUNCDIR `-- CLI_BASEDIR . . -. . `-- cli() . . -. . +---|-----------------------------------+ . . -. . | Common functions environment | . . -. . +---|------------------------|----------+ . . -. . . |-- cli_printMessage() |-- ... . . . -. . . |-- cli_getFilesList() |-- ... . . . -. . . `-- render() `-- ... . . . -. . . +---|---------------------------+ . . . -. . . | Specific function environment | . . . -. . . +-------------------------------+ . . . -. . ......................................... . . -. ............................................... . -....................................................... - - - - - - - - The Shell Environment - - - The centos-art.sh script uses the following - shell environment variables: - - - - - PATH - - - The PATH environment variable is specific to - the operating system and provides search paths for command - execution. By default, the centos-art.sh - script links executable scripts from the ~/bin directory which is one of - the locations used as search path in this variable. This is - how we create the centos-art command from - the centos-art.sh script inside your - working copy. - - - - This variable is not initialized inside the - centos-art.sh script. Instead, the value - set in ~/.bash_profile file is used. - - - - - - - EDITOR - - - The EDITOR environment variable is specific to - the operating system and provides the path to your default - text editor. The centos-art.sh script uses - the default text editor to edit subversion pre-commit - messages, translation files, documentation files, script - files, and similar text-based files. - - - - Possible values for this variable are: - - - - - - /usr/bin/vim - - - - - - /usr/bin/emacs - - - - - - /usr/bin/nano - - - - - - In case none of these values is set for the - EDITOR environment variable inside - ~/.bash_profile, the - centos-art.sh script uses /usr/bin/vim as default text - editor. This is the text editor installed by default in &TCD;. - - - - - - TEXTDOMAIN - - - The TEXTDOMAIN environment variable is specific - to the operating system and provides the domain name of that - application we are producing translation messages for. This - variable, in combination with TEXTDOMAINDIR, is - used by gettext to find out the - location of translation messages. In the very specific case - of centos-art.sh script we use the - centos-art.sh name as domain name. - - - - This variable is initialized inside the - centos-art.sh script, so if you set it - outside it (e.g., in ~/.bash_profile) the - value you set there will be overwritten by that one set inside - centos-art.sh script, once it is executed. - - - - - - TEXTDOMAINDIR - - - The TEXTDOMAINDIR environment variable is - specific to the operating system and provides the absolute - path to the directory containing the translation messages - related to that application specified by - TEXTDOMAIN environment variable. In the very - specific case of centos-art.sh script we - use the Locales/Scripts/Bash - path as default value. - - - This variable is initialized inside the - centos-art.sh script, so if you set it - outside it (e.g., in ~/.bash_profile) the - value you set there will be overwritten by that one set inside - centos-art.sh script, once it is executed. - - - - - - TMPDIR - - - The TMPDIR environment variable is specific to - the operating system and provides the absolute path to the - temporal directory the centos-art.sh script will use along its - execution. This variable is defined inside the - centos-art.sh script itself using the - mktemp command and will be unique on each - script execution. Thus, you should be able to run several - instances of centos-art.sh script - simultaneously without any problem. - - - - When you contribute code to centos-art.sh - script and need to create temporal files, do it inside the - absolute path specified by this variable. - - - - This variable is redefined inside the - centos-art.sh script, so if you set it - outside it (e.g., in ~/.bash_profile) the - value you set there will be overwritten by that one set inside - centos-art.sh script, once it is executed. - - - - - - LANG - - - The LANG environment variable is specific to - the operating system and controls the default locale - information of it. The centos-art.sh - script use the LANG environment variable to - determine what language to use for printing output messages - from the script itself, as well as the portable objects - locations that need to be updated or edited when you localize - directory structures inside the working copy of &TCAR;. - - - - The LANG environment variable is initially set - in the installation process of &TCD;, specifically in the - Language step. Generally, there is no - need to customize this variable in your personal profile. If - you need to change the value of this environment variable do - it through the login screen of GNOME Desktop Environment or - the system-config-language command, or even - resetting the variable before executing the - centos-art.sh script. - - - - - - - - In addition to shell environment variables described above, - the centos-art.sh script adds the following - variables inside the ~/.bash_profile file - to control the script behaviour in a per-user level: - - - - - TCAR_WORKDIR - - - The TCAR_WORKDIR environment variable is - specific to centos-art.sh script and - controls the working copy default location of &TCAR;. This is - the place in your workstation where &TCAR; file system is - stored for you to work with it. - - - - By default, just after installing your workstation, this - variable will not be found in it and the - centos-art.sh script will finish its - execution with an error message if you try to execute it - without any argument. This behaviour is OK because the - centos-art.sh script doesn't know where you - stored the working copy of &TCAR; in your workstation. In - order for this variable to exist in your workstation you need - to configure your workstation first, as described in . - - - - - - TCAR_BRAND - - - The TCAR_BRAND environment variable is specific - to centos-art.sh script and controls the - brand information that identifies the content produced inside - &TCAR;. The brand information is used to give name to some - files inside the repository (e.g., see files under Identity/Models/Brands - directory). - - - By default, this variable takes centos as - value. In case you want to change it to something else, you - should consider the following implications: - - - - - The centos-art.sh script will no longer be - referred as such. Instead, the - ${TCAR_BRAND}-art.sh name will be used. - This implies that you no longer are using the - centos-art.sh file we provide as part of - &TCAR; and won't be able to commit changes to it. However, if - you retain the same logic from - centos-art.sh script in - ${TCAR_WORKDIR}-art.sh, you can use - common and specific functionalities provided by - centos-art.sh script and commit changes to - them. - - - - - The files stored under Identity/Models/Brands - should be named using the value of - ${TCAR_BRAND} as section. If you change - the value of this variable, you need to be sure the new value - set does coincide with the file names you use to store brand - information. - - - - - - - - - - - The Command Environment - - - The first file the centos-art.sh script - calls is the - Scripts/Bash/Functions/Commons/cli.sh - file. This file initializes all variables and functions you - will be able to use along the script execution environment - lifetime. Such environment variables are for internal use - inside the centos-art.sh script only and - users shouldn't modify them to customize the script in a - per-user level. Instead, to customize the script behaviour in - a per-user level, you need to make use of your personal - environment variables set in the - ~/.bash_profile file. - - - - Once environment variables are initialized, the - centos-art.sh script initializes common and - specific environment functions, in that order. - - - - Common Function Environment - - - Common function environments are stored under Scripts/Bash/Functions/Commons - directory and will be available always, both for common - environment functions themselves and specific environment - functions. - - - - - - Specific Function Environments - - - Specific function environments, on the other hand, are stored - in the Scripts/Bash/Functions/${CLI_FUNCDIRNAM}/${CLI_FUNCNAME}.sh - file, where: - - - - - CLI_FUNCDIRNAME - - - Is the first argument passed to - centos-art.sh script with the first letter - in uppercase but the rest in lowercase. For example, - Render, Locale and - Help are all possible values to this - variable. - - - - - - CLI_FUNCNAME - - - Is the first argument passed to - centos-art.sh script with all letters in - lowercase. For example, render, - locale and help are all - possible values to this variable. - - - - - - - Specific functions environment can be written in just one file - or in several files inside the same directory. Using one file - to write specific functions environment is rarely seen inside - the centos-art.sh script but it could - happen in situations where the need you want to solve can be - written in a few lines inside just one file. On the other - hand, if you find yourself writing a too long file, it is - convenient to logically divide it into several files. This - logical division takes place using functions, which indeed - create other environments where you can create and express - your solutions. - - - - The order in which individual files are exported and executed - inside the specific functions environments depends in the way - each developer write the Scripts/Bash/Functions/${CLI_FUNCDIRNAM}/${CLI_FUNCNAME}.sh - file. This is the main file inside the specific function - environment and controls the kind of logical division you - implement to organize the solution you need. As file name - convention, the following structure for new specific functions - environment is proposed: - - - -Scripts/Bash/Functions/${CLI_FUNCDIRNAM}/ -|-- ${CLI_FUNCNAME}.sh -`-- ${CLI_FUNCNAME}_verbSubject.sh - - - - Specific functions environment is exported after common - functions environment does, so it is not possible for specific - functions environment to be available inside the common - functions environment, nor inside other specific functions - environment, different to the one been passed as first - argument to the centos-art.sh script - command-line. - - Although, it is possible for you to call the - centos-art.sh script to itself - through the cli_runFnEnvironment - common function environment. - - In , - render is a specific function environment - while cli_printMessage and - cli_getFilesList are common function - environments. - - - - Both specific and common function environments exist to - standardize frequent tasks inside &TCAR;. The following - sections will describe which these frequent tasks are and the - way they are standardized using specific and common function - environments. - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/funref.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/funref.docbook deleted file mode 100644 index c67c159..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/funref.docbook +++ /dev/null @@ -1,1294 +0,0 @@ - - - Environment Functions Reference - - - In addition to environment variables described above, the - centos-art.sh script makes available the following common - environment functions once it is executed: - - - - - - - - cli_checkRepoDirSource - - cli_checkRepoDirSource - - - - - - - - The cli_checkRepoDirSource function - standardizes the path construction to directories inside it - the working copy, using absolute paths. This function - transforms relative paths passed as non-option arguments to - centos-art.sh script command-line into - absolute paths inside the working copy and verifies whether - they really exist as directories inside the working copy or - not. If the path provided doesn't exist as directory inside - the working copy, the script will finish its execution - immediately with an error message. Otherwise, if the directory - exists, the variable ACTIONVAL is redefined - with the related absolute path for further use. - - - - Use the cli_checkRepoDirSource function - whenever you need to be sure that non-option arguments passed - to centos-art.sh script command-line will - always point to directories inside the working copy. - - - - - - - - - cli_expandTMarkers - - cli_expandTMarkers - - - LOCATION - - - - - The cli_expandTMarkers standardizes - construction of translation markers and their related - expansion. As convention, translation markers are set inside - source files (e.g., DocBook, SVG) and expanded inside temporal - instances used to produce final contents. The - LOCATION argument should point to - the temporal file where translation markers expansion takes - place in. - - - Translation markers written in source files must comply the - =[A-Z_]+= regular expression pattern. For - example, =UNKNOWN_MARKER= is a valid - translation marker without any replacement. To prevent - centos-art.sh script from expanding - translation markers, add a backslash (\) - between the first equal sign and the following letter. For - example, =\...= won't be expanded. - - - The cli_expandTMarkers supports the - following translation markers: - - - - =\COPYRIGHT_YEAR_LAST= - =\COPYRIGHT_YEAR= - - - These translation markers expand to the last year used in - copyright notes. For example, - =COPYRIGHT_YEAR_LAST=. - - - - - - =\COPYRIGHT_YEAR_LIST= - =\COPYRIGHT_YEARS_LIST= - - - This translation markers expand to the list of years used in - copyright notes. For example, - =COPYRIGHT_YEARS_LIST=. The first year - represents the time we began to work on &TCAR;. - - - - - - =\COPYRIGHT_HOLDER= - - - This translation marker expands to the holder used in - copyright notes. For example, - =COPYRIGHT_HOLDER=. - - - - - - =\COPYRIGHT_HOLDER_PREDICATE= - - - This translation marker expands both the holder and the - predicate used in copyright notes. For example, - =COPYRIGHT_HOLDER_PREDICATE=. - - - - - - =\BRAND= - - - This translation marker expands to the brand name used on - files names and URLs inside &TCAR;. For example, - =BRAND=. - - - - - - =\LICENSE= - - - This translation marker expands to the license information - used in files created by centos-art.sh - script. For example, =LICENSE=. - - - - - - =\LICENSE_URL= - - - This translation marker expands to the license URL used in - files created by centos-art.sh script. For - example, =LICENSE_URL=. - - - - - - =\THEME= - - - This translation marker expands to the theme portion of path - you are producing through centos-art.sh script. As - consequence, this translation marker should be used in - situations where you are producing theme components only. - This translation marker expands its value by retrieving the - theme part of the path you provide as non-option argument to - centos-art.sh script. For example, if you - provide the path - Identity/Images/Themes/Modern/2/Distro/5, - this translation will expand to the - Modern/2/ value. - - - In case you need to retrieve the theme name or version - separately one another, then you can use the - =\THEMENAME= and - =\THEMERELEASE= translation markers, - respectively. When you use these translation markers, forward - slashes are removed from result. So, if you provide the path - Identity/Images/Themes/Modern/2/Distro/5, - =\THEMENAME= will expand to - Modern and - =THEMERELEASE= will expand to - 2. - - - - - - =\RELEASE= - - - This translation marker expands to the current release - information of your CentOS distribution. By default this - information is retrieved from - /etc/redhat-release. In case the option - be passed, the value specified with - it will overwrite the default value and will be this the one - used as section for this translation marker to retrieve the - release information. So, for example, if you are running a - CentOS-5.8 distribution and no - option is passed to centos-art.sh script, - this translation marker expands to 5.8. On - the other hand, if you are still running a CentOS-5.8 - distribution but provide the - option to centos-art.sh script, this - translation marker expands to 6.3 instead. - - - In case you need to retrieve minor and major release numbers - separately one another, then you can use the - =\MINOR_RELEASE= and - =\MAJOR_RELEASE= translation makers, - respectively. - - - - - - =\ARCH= - - - This translation marker expands to the current architecture of - your CentOS Distribution. By default this information is - retrieved from uname -i. In case the option - be passed, the value specified with it - will overwrite the default value and will be the one used as - section. For example, if the uname -i - outputs the line i386, this - translation marker will expand to i386. On - the other hand, if you pass the - option to centos-art.sh script, this - translation marker will expand to x86_64 - instead. - - - - - - =\URL= - - - This translation marker expands to the URL which points to - &TCP; home page. For example, =URL=. In - case you are using the centos-art.sh script in a different - locale but English (en_US.UTF-8), this - translation marker expands as usual but with the language - information appended to the end of the string. For example, if - you are executing the centos-art.shscript for Spanish locale - (e.g., es_ES.UTF-8), this translation - marker expands to =URL=es/. - - - - In case you need to expand other URL related to &TCP; domain, - use translation markers described in . Likewise - =\URL=, translation markers described in does - append the current language information to the end of the URL - string based on the locale information you are currently - executing the centos-art.sh script. - - - - URL-related translation markers - - - - Translation Marker - Expands To - - - - - - =\URL_WIKI= - =URL_WIKI= - - - =\URL_LISTS= - =URL_LISTS= - - - =\URL_FORUMS= - =URL_FORUMS= - - - =\URL_MIRRORS= - =URL_MIRRORS= - - - =\URL_DOCS= - =URL_DOCS= - - - =\URL_PROJECTS= - =URL_PROJECTS= - - - =\URL_SVN= - =URL_SVN= - - - =\URL_TRAC= - =URL_TRAC= - - - =\URL_PLANET= - =URL_PLANET= - - - - -
- - - - - - =\MAIL_DOCS= - - - This translation marker expands to CentOS documentation - mailing list address. For example, - =MAIL_DOCS=. - - - - - - =\LOCALE= - - - This translation marker expands to the current locale - information used by centos-art.sh script. - This value is retrieved from the LANG - environment variable and should look like - =LOCALE=. In case you need to retrieve the - language and country part separately one another, you can use - the =\LOCALE_LL= and - =\LOCALE_CC=, respectively. - - - - - - =\REPO_TLDIR= - - - This translation marker expands to the absolute path to - directory inside - your workstation. For example, - /home/al/Projects/CentOS/artwork/trunk. - - - - - - =\REPO_HOME= - =\TCAR_WORKDIR= - - - This translation marker expands to the absolute path of your - working copy. For example, - /home/al/Projects/CentOS/artwork. - - - - - - - See also: - - - - - - - - - cli_exportFunctions - - cli_exportFunctions - - - EXPORTID - - - - - The cli_exportFunctions function - standardizes the way specific functionalities are exported to - centos-art.sh script execution environment. - The EXPORTID argument points the - specific function initialization file relatively from - Scripts/Bash/Functions directory - on. For example, if we want to export the - render specific functionality, we use the - following construction: - - -cli_exportFunctions "Render/render" - - - In this construction, Render with the first - letter in upper case is the name of the directory under - Scripts/Bash/Functions - where the specific functionality is stored in, and - render with all letters in lower case is - the name of the specific functionality we want to export, - without its extension. This name is also used as suffix to - identify all files related to the specific functionality we - are exporting to centos-art.sh script - execution environment. - - - - See also: - - - - - - - - - cli_getConfigLines - - cli_getConfigLines - - - FILE - SECTION - OPTION - - - - - The cli_getConfigLines function - standardizes the way configuration lines are retrieved from - configuration files. - - - - The cli_getConfigLines function accepts - the following arguments: - - - - - FILE - - - This argument specifies the absolute path to the configuration - file you want to retrieve configuration lines from. For - example, - ${TCAR_WORKDIR}/Identity/Models/Themes/Default/Distro/5/Anaconda/branding.conf. - - - - - - SECTION - - - This argument specifies the name of the section you want to - retrieve configuration lines from. For example, - symbols without brackets. - - - - - - OPTION - - - This argument specifies the name of the option related to the - configuration line you want to retrieve. For example, - anaconda_header.svgz. - - - - - - - In order for cli_getConfigLines to work - properly, the configuration files must have a section line - with the form [sectionname] which groups - several option = "value" lines. - Lines beginning with # are ignored and can - be used for comments. - - - - Configuration file used to produce Tcar-fs documentation manual - - Configuration used to produce Tcar-fs documentation manual - - - -[main] - -# Specify documentation backend used by documentation manual. -manual_format = "texinfo" - -# Specify title style used by sections inside the manual. -manual_section_style = "directory" - -# Specify the order used by sections inside the manual. -manual_section_order = "ordered" - -[templates] - -# Specify relation between template files and section definition files -# inside the manual. -Chapters/section-functions.texinfo = "^.+-functions-[[:alnum:]]+\.texinfo$" -Chapters/section.texinfo = "^.+\.texinfo$" - - - - - - - - The section names and option names used inside configuration - files can be anything. It depends on the use and - interpretation programmed inside - centos-art.sh script for specific purposes - which defines what kind of section and options must exist - inside a configuration file. For example, consider the - configuration files used by render - functionality. They follow the same structure used in - documentation configuration files but the meaning of their - sections and options change to fit the specific needs of - render functionality. - - - - Configuration file used to produced Anaconda images - - Configuration used to produced Anaconda images - - - -[types] - -anaconda_header.svgz = "Types/White/48/=\BRAND=-5.png:x48+20+20" -first.svgz = "Types/White/32/=\BRAND=-5.png:x32+30+219" -splash.svgz = "Types/White/48/=\BRAND=-5-msg.png:x48+30+138" - -[symbols] - -anaconda_header.svgz = "Symbols/48/=\BRAND=.png:x48+732+20" -first.svgz = "Symbols/48/=\BRAND=.png:x48+30+20" -splash.svgz = "Symbols/48/=\BRAND=.png:x48+30+20" - - - - - - - - Use the cli_getConfigLines function when - you need to retrieve option = "value" lines - from configuration files in a controlled way. - - - - See also: - - - - - - - - - cli_getConfigValue - - cli_getConfigValue - - - FILE - SECTION - OPTION - - - - - The cli_getConfigValue function - standardizes the way option values are retrieved from - configuration files. As convention, - cli_getConfigValue uses the output - produced by cli_getConfigLines as input - to retrieve the option values. As convention, in - option = "value" lines, the values - retrieved are always on the right side. The values retrieved - are also output without quotation and translation markers - already expanded. - - - - The cli_getConfigValue function accepts - the following arguments: - - - - - FILE - - - This argument specifies the absolute path to the configuration - file you want to retrieve the value from. For example, - ${TCAR_WORKDIR}/Identity/Models/Themes/Default/Distro/5/Anaconda/branding.conf. - - - - - - SECTION - - - This argument specifies the name of the section related to the - configuration line you want to retrieve the value from. For - example, symbols without brackets. - - - - - - OPTION - - - This argument specifies the name of the option you want to - retrieve the value from. For example, in , the - anaconda_header.svgz option will output the - Symbols/48/=\BRAND=.png:x48+732+20 value - without quotation and translation markers expanded. So if the - value of TCAR_BRAND environment variable is - centos, the real value you - get will be - Symbols/48/centos.png:x48+732+20. - - - - - - - Use the cli_getConfigValue function - whenever you want to retrieve values from configuration files - in a controlled way. - - - - See also: - - - - - - - - - cli_getFilesList - - cli_getFilesList - - - --pattern - --mindepth - --maxdepth - --type - --uid - LOCATION - - - - - The cli_getFilesList standardizes the way - list of files are built inside the - centos-art.sh script. This function outputs - a sorted and unique list of files based on the options and - location provided as argument. This function is an interface - to the find command. Don't use - find command directly inside the - centos-art.sh script. Instead, use the - cli_getFilesList function. - - - The cli_getFilesList accepts the - following arguments: - - - - - LOCATION - - - This arguments must be the absolute path to a directory and - specifies where the search of files in any form (e.g., - directories, links, etc.) will take place in. If - LOCATION isn't a directory, the - script finishes its execution with an error message. - - - - - - - The cli_getFilesList accepts the - following options: - - - - - - - - This option specifies a posix-egrep type regular expression as - value. This regular expression is applied to path specified in - LOCATION argument. Only file paths - that match this regular expression inside - LOCATION directory will be included - in the final list of files. By default, if this option is not - provided, the - ^/.*[[:alnum:]_/-]+$ regular - expression is used. - - - When you use the cli_getFilesList you - don't need to specified the absolute path of files you want to - look for. This is something - cli_getFilesList already does for you. - When you use this function, the value you pass as regular - expression isn't the final regular expression used. Instead, - the regular expression you pass is used to build the final - regular expression passed to find command. - The final regular expression passed to find is - ^/.*${PATTERN}$, where - ${PATTERN} is the value you passed to - option as - REGEX. - - - - - - - - This option specifies the minimal - NUMBER of levels deep the search - should go under the directory - LOCATION specified. For example, if - you specify the search will - start two levels deep considering the path provided as - section. - - - - - - - - This option specifies the maximum - NUMBER of levels deep the search - should go under the directory - LOCATION specified. For example, if - you specify the search will - begin in the very same directory path you provided as - LOCATION and stop two levels deep - using it as section. - - - - - - - - This option specifies the type of files being searched. This - option accepts the same values the find - option does. However, the following - STRING values are the most used - inside the script so far: - - - - - - d — directory. - - - - - f — regular file. - - - - - - - - - - - - This option specifies the numeric user id of the files you - want to search. Only files that match this numeric user id - will be added to the final list of files. - - - - - - - Use the cli_getFilesList whenever you - need to build list of files for further processing. - - - - - - - - - cli_getPathComponent - - cli_getPathComponent - - - --release - --release-major - --release-minor - --release-pattern - --architecture - --architecture-pattern - --motif - --motif-name - --motif-release - --motif-pattern - PATH - - - - - ... - - - - - - - - cli_synchronizeRepoChanges - - cli_syncronizeRepoChanges - - - LOCATION - - - - - The cli_synchronizeRepoChanges - standardizes the way changes are synchronized between the - working copy and the central repository using - LOCATION as section. This - function is the interface we use inside the - centos-art.sh script to execute the - Svn functionality described in . - - - Use cli_synchronizeRepoChanges function - inside the centos-art.sh script whenever - you need to synchronize one or more changes at any - LOCATION inside the working copy. - - - - - - - - cli_printMessage - - cli_printMessage - - - MESSAGE - - --as-separator-line - --as-banner-line - --as-cropping-line - --as-tuningup-line - --as-checking-line - --as-combining-line - --as-creating-line - --as-reading-line - --as-savedas-line - --as-linkto-line - --as-movedto-line - --as-validating-line - --as-template-line - --as-configuration-line - --as-palette-line - --as-reponse-line - --as-request-line - --as-selection-line - --as-error-line - --as-toknowmore-line - --as-yesornorequest-line - --as-notrailingnew-line - --as-stdout-line - --as-stderr-line - - - - - - The cli_printMessage function - standardizes the way centos-ar.sh scirpt prints messages. By - default, centos-art.sh script prints all messages to the - standard output with the exception of those messages printed - with the option, which are - printed to standard error output instead. - - - - The cli_printMessage function requires - two arguments. The first argument specifies the - MESSAGE you want to print and the - second argument specifies the FORMAT you'll use to print that - message. Because this function is so used inside the - centos-art.sh script, it is convenient to provide localization - to strings passed as MESSAGE using - gettext contructions when they aren't - paths. - - - - The cli_printMessage function accepts the - following formats as second argument: - - - - - - - - This format takes the first character passed as - MESSAGE and repeats it horizontally - to build a separator line. Use this format whenever you need - to create a logical separation between different actions. - - - - - - - - - This format takes the string passed as - MESSAGE and puts it inside two - horizontal separator lines. Use this format whenever you need - to print header information for following lines. - - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file has been cropped. - - - - - - - - - This format is for two columns messages where - MESSAGE - generally refers to a file inside the repository. Use this - format whenever you need to imply the fact that certain file - has been tuned-up. - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file has been checked or verified - (e.g., through cli_checkFiles - functionality). - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file has been combined. - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file has been created. - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file has been read. - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file has been saved. - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file has been linked. - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file has been moved. - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file has been validated. - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file is a template or design - model. - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file is a configuration file. - - - - - - - - This format is for two columns messages where - MESSAGE generally refers to a file - inside the repository. Use this format whenever you need to - imply the fact that certain file is a palette of colors. - - - - - - - - This format adds --> at the begining of the - string passed as MESSAGE. Use this - format whenever you need to imply the fact that certain file - is considered part of a response. For example, when you need - to express that a group of files will take ceratin action, you - can use this option to doing so. - - - - - - - - This format prints MESSAGE without - trailing new line. Use this format whenever you need to imply - a question or yes or no request. - - - - - - - - This format uses each word in - MESSAGE as item of a selection - list. Use this format whenever you need to select one of the - items provided as MESSAGE. - - - - - - - - This format prints error messages produced by centos-art.sh - script. It uses the caller built-in command - to display the line number and the filename where such error - was triggered. Later, it prints where to find more information - by using the option. - - - - - - - - This format takes a function name as - MESSAGE and prints the command you - can use to find more information about it. When this option is - passed the script finishes its execution immediately. This - option is used in combination with - to finish the script - execution after an error. - - - - - - - - - This format takes a question as - MESSAGE and reads a yes or no - answer. When answer is negative, the script finishes its - execution immediately. When answer is affirmative, the script - continues its execution normally. - - - - - - - - - Print MESSAGE without any trailing - newline. - - - - - - - - - Print MESSAGE to standard output. - - - - - - - - - Print MESSAGE to standard error - output. - - - - - - - Use cli_printMessage function whenever - you need to print information inside the - centos-art.sh script. - - - - - - - - cli_unsetFunctions - - cli_unsetFunctions - - - EXPORTID - - - - - ... - - - See also: - - - - - - - - cli_getTemporalFile - - cli_unsetFunctions - - - FILENAME - - - - - ... - - - - - - ... - - - ... - - - - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/help.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/help.docbook deleted file mode 100644 index 8855021..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/help.docbook +++ /dev/null @@ -1,754 +0,0 @@ - - - - help - - Standardize constructions tasks inside &TCAR; - - - - - help - Standardize documentation tasks inside &TCAR;. - - - - - centos-art help - - -h|--help - -q|--quiet - --answer-yes - --synchronize - --format="KEYWORD" - --search="KEYWORD" - --edit - --read - --update-output - --update-structure - --copy - --delete - --rename - - - MANUAL:PART:CHAPTER:SECTION - LOCATION - - - - - - - Description - - - The help functionality exists to create - and maintain documentation manuals inside &TCAR;. - - - - Documentation Entries - - The documentation entry identifies the specific file you want - to work with inside a documentation manual. The help - functionality recognizes documentation entries in the - following formats: - - - - Path style - - - This format uses paths to represent the documentation entries - you want to work with. This format assumes you are using the - first path component as chapter and the rest of the path as - section identifier both inside tcar-fs - documentation manual as parent documentation structure. The - field related to the part sectioning structure in the - documentation entry (the second field) is assumed empty, as - well. For example, if you want to document the directory - Scripts/Bash/Functions/Help, - then you can do it with the following command: - - - - centos-art help --edit Scripts/Bash/Functions/Help - - - - - - Colon style - - - This format uses colons to represent the documentation entries - you want to work with. In this format, the whole documentation - entry is divided in fields using colon as separator character. - Documentation entries written this way use each field to - specify manual, part, chapter and section identifiers (in this - order). The section identifier can use a path style or hyphen - style to separate - components. For example, if you want to document the directory - Scripts/Bash/Functions/Help, - then you can do it with any of the following commands: - - - - centos-art help --edit tcar-fs::trunk:Scripts/Bash/Functions/Help - centos-art help --edit tcar-fs::trunk:scripts-bash-functions-help - - - - The documentation manual name specified in the first field of - a colon style documentation entry, must match the name the - name of the directory where the documentation manual is stored - in. By default documentation manuals are written in - Documentation/Models/Texinfo or - Documentation/Models/Docbook directories, based on - whether they are written in Texinfo or Docbook documentation - format. - - - The match relation between the manual name you provide in the - documentation entry and the related directory name inside - &TCAR; is case insensitive. The same is true for all other - documentation entry fields. - - - - - - - - From these documentation entry formats, the colon style - provides more flexibility than path style does. You can use - documentation entries written in colon style to create and - maintain different documentation manuals, including the - tcar-fs documentation manual. This is something - you cannot do with documentation entries written in path style - because they confine all documentation actions to - tcar-fs documentation manual. - - - - - - - Options - - The centos-art help command accepts common - options described in and the following - specific options: - - - - - - - - Assume yes to all confirmation requests. - - - - - - - - - Synchronizes available changes between the working copy and - the central repository. - - - - - - - - - Specifies the format of documentation entry source file. This - information is used as reference to build the absolute path of - documentation entry, so you always have to provide it in order - to reach the documentation entry you want to work with. - Possible values for this option are shown in . When none of - these values is passed as format, Texinfo is used as default - format. - - - - Documentation formats - - - - Keyword - Description - Supported - - - - - - texinfo - - Yes - - - docbook - - No - - - latex - - No - - - linuxdoc - ... - No - - - - -
- - - - - - - - Looks for documentation entries that match the - KEYWORD specified as value and - display them one by one in the order they were found. The way - each documentation entry is presented to you depends on the - documentation format the related documentation manual was - written on. - - - - - - - - - Edit the documentation entry provided as argument. The - edition itself takes place through your default text editor - (e.g., the one you specified in the EDITOR - environment variable) one file at a time (i.e., the queue of - files to edit is not loaded in the text editor.). - - - When parent components inside documentation entries doesn't - exist (e.g., you try to create a section for a documentation - manual that doesn't exist), the help - functionality will create all documentation parent structures - considering the documentation format constraints and the - following document structure hierarchy order: documentation - manual first, parts second, - chapters third and sections - lastly. - - - - - - - - - Read the documentation entry provided as argument. This - option is used internally by centos-art.sh - script to refer documentation based on errors, so you can know - more about them and the causes that could have provoked them. - - - - - - - - - Update output files rexporting them from the specified backend - source files. - - - - - - - - - Update document structure (e.g., cross references, menus, - nodes, etc.) and should be passed with a section as - documentation entry. - - - This option should be used whenever a document structure - changes (e.g., documentation entries are added, copied, - renamed, deleted, etc.). This option grantees the document - integrity and should be run before updating documentation - manual final output files. - - - - - - - - - Duplicate documentation entries inside the working copy using - version control. - - - When you duplicate documentation entries through this option, - you should pass only two documentation entries in the command - line. The first one is considered the source location and - should point to a file under version control inside the - working copy. The second one is considered the target location - and should point either to the same structural level the - source points to or a direct parent level based on source - location, as described below. - - - - - - "manual:part:chapter:section1" "manual:part:chapter:section2" - - - Duplicates section1 as - section2 inside the same - chapter, - part and - manual. - - - - - - - "manual:part:chapter1:" "manual:part:chapter2:" - - - Duplicates chapter1 as - chapter2 inside the same - part and - manual. - - - - - - - "manual:part1::" "manual:part2::" - - - Duplicates part1 as - part2 inside the same - manual. - - - - - - - "manual1:::" "manual2:::" - - - Duplicates manual1 as - manual2 inside Documentation/Models/${FLAG_FORMAT}/ - directory, where ${FLAG_FORMAT} is the name of the format - passed as option with the first letter in uppercase and the - rest in lowercase. - - - - - - - When you copy documentation entries through this option, all - structuring sections inside the one copied will be also - copied. For example, if you copy a documentation manual that - is made of parts, chapters and sections, the duplicated manual - will contain all those parts, chapters and sections, as well. - The same is true for lower sectioning structures. Thus, you - can be more specific in the documentation entry by reducing - the amount of content to duplicate. - - - - When you copy documentation entries through this option, you - do it using documentation entries in the same structural level - only. This option doesn't support copying documentation - entries from differnet structural levels. For example, you - cannot copy one section to a chapter different from that the - source section you specified belongs to. The same applies to - chapters, and parts. - - - - When you copy documentation entries through this option, the - source documentation entry you specify must not contain - pending changes. Otherwise, the target section won't be - created and the script will immediatly stop its execution with - a The source location has pending changes. - error message. - - - - - - - - - - Delete documentation entries. It is possible to delete more - than one documentation entry by specifying several - documentation entries in the command line. - - - When you delete documentation entries, you can pass any number - of documentation entries as argument. The documentation - entries you provide will be processed one by one. - - - When you delete a documentation entry from a documentation - manual, all cross references pointing to the deleted - documentation entry will be transformed into something - different to point out the fact that the related documentation - entry has been removed from the documentation manual and - restored back if you create the deleted section again. The - purpose of this is to keep the documentation manual structure - in a consistent state. - - - - - - - - - Rename documentation entries inside the working copy. This - option copies the source documentation entry to its target - location, removes the source documentation entry, and restores - removed cross references renaming them to point the specified - target documentation entry. - - - When you rename documentation entries, it is required to pass - only two non-option parameters to the command-line. The first - non-option parameter is considered the source location and the - second one the target location. Both source location and - target location must point to a directory under version - control inside the working copy. - - - - - - - - - Examples - - - This section describes, using examples, the procedure you - should follow to manage documentation manuals through - help functionality inside &TCAR;. To - better understand the procedure to follow, it describes a - hypothetical documentation scenario and the related commands - and outputs you may go through in order to complete specific - documentation tasks successfully. - - - - Creating Document Structures - - To create new documentation manuals inside &TCAR; you need to - provide both and - options as well as a documentation - entry in the form manual::: - to the help functionality. - - - - For example, consider a scenario where you need to create a - documentation manual in texinfo format to describe different - maintenance tasks you need to realized in order to keep your - pets happy. We'll name such manual My Zoo. It - will use chapters to organize each different kind of pets you - have. Inside chapters, sections will have the pet's name as - their own name to describe each pet's requirements, schedules, - and so on. To create such documentation manual, run the - following command: - - - - centos-art help --edit --format="texinfo" "myzoo:::" - - - - In case such documentation manual doesn't exist in the - Docuementation/Models/Texinfo/ - directory, this command will produce the following output: - - - -The following documentation manual doesn't exist: ---> Documentation/Models/Texinfo/Myzoo/en_US/myzoo.texinfo -Do you want to create it now? [yes/no]: yes -Enter manual's title: My Zoo -Enter manual's subtitle: Reference -Enter manual's abstract: This manual describes my zoo maintenance tasks. -Creating Documentation/Models/Texinfo/Myzoo -Creating Documentation/Models/Texinfo/Myzoo/en_US -Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo.conf -Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-index.texinfo -Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-menu.texinfo -Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-nodes.texinfo -Creating Documentation/Models/Texinfo/Myzoo/en_US/myzoo.texinfo -Creating Documentation/Models/Texinfo/Myzoo/en_US/Licenses/chapter-menu.texinfo -Creating Documentation/Models/Texinfo/Myzoo/en_US/Licenses/chapter-nodes.texinfo -Creating Documentation/Models/Texinfo/Myzoo/en_US/Licenses/chapter.texinfo -Updating Documentation/Models/Texinfo/Myzoo/en_US/myzoo.texinfo -Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2 -Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2 -Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml -Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook -Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf -Creating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2 - - - - Once the documentation structure has been created this way, - the recently created documentation manual is ready to receive - new sectioning levels (e.g., parts, chapters, sections, etc.). - For example, to create a new chapter named - Turtles inside My Zoo - documentation manual, run the following command: - - - - centos-art help --edit --format="texinfo" "myzoo::turtles:" - - - -The following documentation chapter doesn't exist: ---> Documentation/Models/Texinfo/Myzoo/en_US/Turtles -Do you want to create it now? [yes/no]: yes -Enter chapter's title: Turtles -Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles -Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter-menu.texinfo -Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter-nodes.texinfo -Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter.texinfo -Updating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-menu.texinfo -Updating Documentation/Models/Texinfo/Myzoo/en_US/myzoo-nodes.texinfo -Updating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/chapter.texinfo -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2 -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2 -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2 - - - - Once chapters have been created it is possible to create - sections inside them. For example, if you want to create a - section for describing the life of a turtle named Longneck, - run the following command: - - - - centos-art help --edit --format="texinfo" "myzoo::turtles:longneck" - - - -The following documentation section doesn't exist: ---> Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo -Do you want to create it now? [yes/no]: yes -Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2 -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2 -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2 - - - - - - Editing Document Structures - - To edit documentation entries you can follow the same - procedure described above. Just keep in mind the following - rules: - - - - - - When the entry you want to edit already exist it will be - edited. - - - - - - When the entry you want to edit doesn't exist it will be created - first and edited later. - - - - - - - - - Copying Document Structures - - Consider a new turtle named Slowfeet has arrived to your home - and you want to duplicate Longneck's section for it (they both - are turtles and have similar requirements, squedules, etc.). - To copy documentation entries you use the - option with two documentation entries, - where the first one is the source location and the second one - the target location. To do this, run the following command: - - - - centos-art help --copy --format="texinfo" "myzoo::turtles:longneck" "myzoo::turtles:slowfeet" - - - -Creating Documentation/Models/Texinfo/Myzoo/en_US/Turtles/slowfeet.texinfo -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.info.bz2 -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xhtml.tar.bz2 -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.xml -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.docbook -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.pdf -Updating Documentation/Manuals/Texinfo/Myzoo/en_US/myzoo.txt.bz2 - - - - - - Renaming Document Structures - - Consider you've created the section of Longneck turtle using - the following documentation entry format - myzoo::turtles:longnek, but you didn't notice - the typo in it. You've made cross references to the misspelled - section in a few pages inside the My Zoo - documentation manual and some time later you realize the - section name has a spelling problem. To fix such a problem - you can rename the misspelled section with the correct one - running the following command: - - - - centos-art help --rename --format="texinfo" "myzoo::turtles:longnek" "myzoo::turtles:longneck" - - - -Creating Documentation/Models/Texinfo/MyZoo/en_US/Turtles/longneck.texinfo -Deleting Documentation/Models/Texinfo/MyZoo/en_US/Turtles/longnek.texinfo -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.info.bz2 -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xhtml.tar.bz2 -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xml -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.docbook -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.pdf -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.txt.bz2 - - - - ... - - - - - Deleting Document Structures - - Consider you gift the turtle named Longneck to a friend and - you want to delete its section from the My Zoo - documentation manual. To do so, run the following command: - - - centos-art help --delete --format="texinfo" "myzoo::turtles:longneck" - - -Deleting Documentation/Models/Texinfo/Myzoo/en_US/Turtles/longneck.texinfo -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.info.bz2 -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xhtml.tar.bz2 -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.xml -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.docbook -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.pdf -Updating Documentation/Manuals/Texinfo/MyZoo/en_US/myzoo.txt.bz2 - - - - - - - - Bugs - - To report bugs related to this function, please create a new - ticket here - refering the specific problems you found in it. For example, - it would be useful if you copy and paste any error output from - centos-art.sh script. - - - - - Authors - - The following people have worked in this functionality: - - - - - Alain Reguera Delgado <alain.reguera@gmail.com>, =COPYRIGHT_YEAR_LIST= - - - - - - - License - - - Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - - - - 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. - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/intro.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/intro.docbook deleted file mode 100644 index bf64c16..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/intro.docbook +++ /dev/null @@ -1,6 +0,0 @@ - - This reference covers the centos-art.sh script - mission, name convenctions, command-line interface and execution - environments. You can use this reference to understand how the - centos-art.sh script works. - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/locale.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/locale.docbook deleted file mode 100644 index 21a37d9..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/locale.docbook +++ /dev/null @@ -1,292 +0,0 @@ - - - - locale - - Standardize translation tasks inside &TCAR; - - - - - locale - Standardize translation tasks inside &TCAR; - - - - - The DIRECTORY parameter specifies the - directory path, inside the working copy of &TCAR;, where the - files you want to process are stored in. This paramter can be - provided more than once in order to process more than one - directory path in a single command execution. When this - parameter is not provided, the current directory path where - the command was called from is used instead. - - - - - Options - - The locale functionality accepts the - following options: - - - - - - - - Supress all output messages except error messages. When this - option is passed, all confirmation requests are supressed and - a possitive answer is assumed for them, just as if the - option would have been provided. - - - - - - - - - Assume yes to all confirmation requests. - - - - - - - - - Reduce the list of files to process inside - DIRECTORY using REGEX as - pattern. You can use this option to control the amount of - files you want to locale. The deeper you go into the - directory structure the more specific you'll be about the - files you want to locale. When you cannot go deeper into the - directory structure through DIRECTORY - specification, use this option to reduce the list of files - therein. - - - - - - - - - Synchronizes available changes between the working copy and - the central repository. - - - - - - - - - This option updates both POT and PO files related to source - files. Use this option everytime you change translatable - strings inside the source files. - - - - - - - - - This option edits the portable object related to source files. - When you provide this option, your default text editor is used - to open the portable object you, as translator, need to change - in order to keep source file messages consistent with their - localized versions. In the very specific case of shell - scripts localization, this option takes care of updating the - machine object (MO) file the shell script requires to - displayed translation messages correctly when it is executed. - - - - - - - - - This option unlocalizes source files. When you provide this - option, the localization directory related to source files is - removed from the working copy in conjunction with all portable - objects and machine objects inside it. - - - - - - - - - This option suppresses machine objects creation when shell - scripts are localized. - - - - - - - - - Description - - - The localization process is very tied to the source files we - want to provide localized messages for. Inside the working - copy of &TCAR; it is possible to localize XML-based files - (e.g., SVG and Docbook) and programs written in most popular - programming languages (e.g., C, C++, C#, Shell Scripts, - Python, Java, GNU awk, PHP, etc.). - - - - The localization process initiates by retriving translatable - strings from source files. When source files are XML-based - files, the only requisite to retrive translatable strings - correctly is that they be well-formed. Beyond that, the - xml2po command takes care of everything - else. When source files are Shell script files, it is - necessary that you previously define what strings inside the - script are considered as translatable strings in order for - xgettext command to retrive them correctly. - To define translatable strings inside shell scripts, you need - to use either gettext, - ngettext, eval_gettext - or eval_ngettext command as it is following - described: - - - - - - Use the gettext command to display the - native language translation of a textual message. - - MESSAGE="`gettext "There is no entry to create."`" - - - - - Use the ngettext command to display the - native language translation of a textual message whose - grammatical form depends on a number. - - MESSAGE="`ngettext "The following entry will be created" \ - "The following entries will be created" \ - $COUNT`:" - - - - - Use the eval_gettext command to display the - native language translation of a textual message, performing - dollar-substitution on the result. Note that only shell - variables mentioned in the message will be dollar-substituted - in the result. - - MESSAGE="`eval_gettext "The location \\\"\\\$LOCATION\\\" is not valid."`" - - - - - Use the eval_ngettext command to display - the native language translation of a textual message whose - grammatical form depends on a number, performing - dollar-substitution on the result. Note that only shell - variables mentioned in messages will be dollar-substituted in - the result. - - MESSAGE="`eval_ngettext "The following entry will be created in \\\$LOCATION" \ - "The following entries will be created in \\\$LOCATION" \ - $COUNT`:" - - - - - Once translatable strings are retrived, a portable object - template (POT) file is created for storing them. Later, the - POT file is used to create a portable object (PO). The - portable object is the place where localization itself takes - place, it is the file translators edit to localize messages. - When translatable strings change inside source files, it is - necessary that you update these POT and PO files in order to - keep consistency between source file messages and their - localized versions. - - - - Inside source files, translatable strings are always written - in English language. In order to localize translatable strings - from English language to another language, you need to be sure - the LANG environment variable has been already - set to the locale code you want to localize message for or see - them printed out before running the - locale functionality of - centos-art.sh script. Localizing English - language to itself is not supported. - - - - To have a list of all locale codes you can have localized - messages for, run the following command: locale -a | - less. - - - - - Function Specific Environment - - ... - - - - - Authors - - The following people have worked in the - locale functionality: - - - - - Alain Reguera Delgado <alain.reguera@gmail.com>, =COPYRIGHT_YEAR_LIST= - - - - - - - License - - - Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - - - - 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. - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/mission.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/mission.docbook deleted file mode 100644 index 283781e..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/mission.docbook +++ /dev/null @@ -1,9 +0,0 @@ - -Mission - - - The centos-art.sh script exists to automate - frequent tasks inside &TCAR;. - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/nameconvs.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/nameconvs.docbook deleted file mode 100644 index a041b3a..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/nameconvs.docbook +++ /dev/null @@ -1,54 +0,0 @@ - - - Convenctions - - - ... - - - - Variable Names - - ... - - - - - Function Names - - ... - - - - - Exit Status - - The centos-art.sh script has the following - exit status: - - - - - - 0 — The script completed successfully - without error. - - - - - - 1 — The script didn't complete successfully - because something went wrong. This error status is generally - produced by cli_printMessage - functionality, when you use it with the - option as second argument. - - - - - - ... - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/pack.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/pack.docbook deleted file mode 100755 index 01c5937..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/pack.docbook +++ /dev/null @@ -1,82 +0,0 @@ - - - - pack - - Standardize packing tasks inside &TCAR; - - - - - pack - Standardize packing tasks inside &TCAR; - - - - - ... - - - - - Description - - ... - - - - - Usage - - ... - - - - - Function Specific Environment - - ... - - - - - Authors - - - - ... - - - - - - - License - - - Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - - - - 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. - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/prepare.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/prepare.docbook deleted file mode 100644 index 4fb9cf9..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/prepare.docbook +++ /dev/null @@ -1,314 +0,0 @@ - - - - prepare - - Standardize configuration tasks inside &TCAR; - - - - - prepare - Standardize configuration tasks inside &TCAR; - - - - - Assuming this is the very first time you run the - centos-art command, you'll find that there - isn't such a command in your workstation. This is correct - because you haven't created the symbolic link that makes it - available in your execution path, yet. In order to make the - centos-art command available in the - execution path of your workstation, you need to run the - centos-art.sh script using its absolute - path first: - - - - ~/artwork/Scripts/Bash/centos-art.sh - prepare - -h|--help - -q|--quiet - --answer-yes - --set-environment - --see-environment - --packages - --locales - --links - --images - --manuals - --synchronize - - - - Later, once the centos-art command is - available in your execution path, there is no need for you to - use any absolute path again. From this time on, you can use - the centos-art command-line interface - directly, as the following example describes: - - - - centos-art - prepare - -h|--help - -q|--quiet - --answer-yes - --set-environment - --see-environment - --packages - --locales - --links - --images - --manuals - --synchronize - - - - - Description - - The prepare function exists to set - environment variables, install/update required packages, - create symbolic links for content reusing, render images based - on available design models and artistic motifs, render - documentation manuals, build language-specific files required - for content localization and anything else needed in order to - make the working copy of &TCAR; ready to be used. - - - - When no option is provided to prepare - functionality, the centos-art.sh script - uses the , - , - , and - options, in that order, as default - behaviour. Otherwise, if you provide any option, the - centos-art.sh script avoids its default - behaviour and executes the prepare - functionality as specified by the options you provided. - - - - Notice that it is possible for you to execute the - prepare functionality as many times as - you need to. This is specially useful when you need to keep - syncronized the relation between content produced inside your - working copy and the applications you use outside it. For - example, considering you've added new brushes to or removed - old brushes from your working copy of &TCAR;, the link - information related to those files need to be updated in the - ~/.gimp-2.2/brushes - directory too, in a way the addition/deletion change that took - place in your working copy can be reflected there, as well. - The same is true for other similar components like fonts, - patterns and palettes. - - - - - - Usage - - Use the prepare functionality the first - time you download a working copy of &TCAR; or later, to be - sure your workstation has all the components it needs so you - can use the working copy of &TCAR; in all its extension. - - - - - Options - - - The centos-art prepare command accepts - common options described in and the following - specific options: - - - - - - - - Assume yes to all confirmation requests. - - - - - - - - - This option verifies packeges required by automation scripts - and installs or updates them as required. When required - packages aren't installed or need to be updated, the - centos-art uses the sudo - and yum to perform either installations or - actualizations tasks. In both cases, it is required that you - configure the /etc/sudoers configuration - file first, as discribed in . - - - - - - - - - - This option creates or updates the portable objects (PO) and - machine object (MO) used by gettext - to retrive translated strings related to - centos-art.sh script. This option calls - the locale functionality of centos-art.sh - with the option, as described in - . - - - - - - - - - This option maintains the file relation between your working - copy and configuration files inside your workstation through - symbolic links. When you provide this option, the - centos-art.sh script puts itself into your - system's execution path through its command line interface - centos-art and makes common brushes, - patterns, palettes and fonts inside the working copy, - available to applications like GIMP in order for you to make - use of them without loosing version control over them. - - - - This option removes all common fonts, brushes, patterns, and - palettes currently installed in your home directory, in order - to create a fresh installation of them all again, using the - working copy as section. - - - - - - - - - - This option initializes image files inside the working copy. - When you provide this option, the - centos-art.sh calls the - render functionality to create images - related to each design model available in your working copy, - as described in . - - - - - - - - - This option initializes documentation files inside the working - copy. When you provide this option, the - centos-art.sh script calls both the - render and help - functionality to produce DocBook and Texinfo manuals, - respectively. - - - - - - - - - Print the name and value of some of the environment variables - used by centos-art.sh script as described - in . - - - - - - - - - Set default environment values to your personal profile - (~/.bash_profile). - - - - - - - - - Examples - - None. - - - - - Bugs - - To report bugs related to this function, please create a new - ticket here - refering the specific problems you found in it. For example, - it would be useful if you copy and paste any error output from - centos-art.sh script. - - - - - Authors - - The following people have worked in this functionality: - - - - - Alain Reguera Delgado <alain.reguera@gmail.com>, =COPYRIGHT_YEAR_LIST= - - - - - - - License - - - Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - - - - 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. - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/render.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/render.docbook deleted file mode 100644 index 84826ba..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/render.docbook +++ /dev/null @@ -1,435 +0,0 @@ - - - - render - - Standardize rendition tasks inside &TCAR;. - - - - - render - Standardize rendition tasks inside &TCAR;. - - - - - centos-art - render - -h|--help - -q|--quiet - --filter="REGEX" - --answer-yes - --dont-dirspecific - --releasever="RELEASEVER" - --basearch="BASEARCH" - --post-rendition="COMMAND" - --last-rendition="COMMAND" - --theme-model="MODELNAME" - --with-brands - --synchronize - LOCATION - - - - - Description - - - The render functionality exists to - automate content rendition inside &TCAR;. The content - rendition process itself takes place through the following - rendition modes: - - - - - - svg — This modes works with both - gzip-compressed (.svgz) - or uncompressed (.svg) - scalable vector graphics as source files and produces portable - network graphics as main output. - - - - - docbook — This mode works with - DocBook source files and produces XHTML as main output. It is - also possible to produce PDF output from DocBook source files, - however PDF output is commented because its production fails - trying to create indexes. - - - - - conf — This mode works with one or - more configuration files as source and produces portable - network graphics as main output. The format used in these - configuration files is described in . - - - - - - To determine the rendition mode, the - render functionality uses the path - provided as LOCATION argument and - the path name convention described in . - - - - Render-able Directories - - - The render-able directories are conventional locations inside - the working copy where you can find final output files. The - final output files are produced from source files and - auxiliary files. Auxiliary files are frequently used to - create localized instances of source files which are, in turn, - used to create final output files in different forms (e.g., in - a different language). - - - - Inside the working copy of &TCAR;, the following directory - structures are considered render-able directories: - - - - - - Identity/Images/ - — This directory structure organizes final image files - in different formats. It also includes source files for - producing the backgrounds of themes. Related design models for - all these files are under Identity/Models/ directory - structure. - - - - Don't move any source file related to theme backgrounds from - render-able directories to theme design models directory - structure. The source files related to theme backgrounds are - specific to each theme and cannot be shared among different - themes. The directory structure related to theme design models - is reserved for files shared by all themes. - - - - - - Documentation/Manuals/ - — This directory structure organizes final documentation - files. Design models for all these files are organized under - Documentation/Models/ - directory structure. - - - - - - Inside render-able directories the rendition process is - performed through different rendition flows known as - theme-rendition, base-rendition, post-rendition and - last-rendition. - - - - - Theme-Rendition Flow - - The theme-rendition flow exists to produce content inside - Identity/Images/Themes/ directory - structure. This rendition flow identifies which directories - are render-able and uses the base-rendition on them, one by - one. - - - The theme-rendition flow exists to support massive rendition - of themes through the following command: - - - - centos-art render Identity/Images/Themes - - - - In case you need to limit the amount of themes or components - inside themes you want to render, you can be more - specific about the LOCATION you - passed as argument and use the - - to specify the file you want to render. For example, if you - only want to render the 01-welcome.png - Anaconda file for CentOS-5 distribution based on version 2 of - Modern artistic motif, then you can run the following command: - - - - centos-art render Identity/Images/Themes/Modern/2/Distro/5/Anaconda --filter="01-welcome" - - - - Notice that you can reach the same result in different ways - here by creating combinations between the path you provide as - LOCATION and the - option. For example, the following - commands produce the same result: - - - - centos-art render Identity/Images/Themes/Modern/2/Distro/5/Anaconda - - - - centos-art render Identity/Images/Themes/Modern --filter="2/Distro/5/Anaconda" - - - - You can use whatever combination you like whenever it matches - a valid render-able directory inside the working copy. But it - seems to be an acceptable practice to use the - LOCATION argument to specify the - render-able directory path inside the Identity/Images/Themes - directory which images need to be rendered for and the - option only when it is needed to - restrict rendition to a specific file inside the directory - provided as LOCATION. - - - - - - Base-Rendition Flow - - ... - - - - - Post-Rendition Flow - - ... - - - - - Last-Rendition Flow - - ... - - - - - Configuration Files (<filename>render.conf</filename>) - - ... - - - - - - Usage - - ... - - - - - Options - - - The centos-art prepare command accepts - common options described in and the following - specific options: - - - - - - - - - Assume yes to all confirmation requests. - - - - - - - - - This option reduces the list of files to process inside - LOCATION using - REGEX as REGUEX - using REGEX as files you want to render. - The deeper you go into the directory structure the more - specific you'll be about the files you want to render. When - you cannot go deeper into the directory structure through - LOCATION specification, use this - option to reduce the list of files therein. - - - - - - - - - Synchronizes available changes between the working copy and - the central repository. - - - - - - - - - This option expands the =\RELEASE=, - =\MAJOR_RELEASE=, and - =\MINOR_RELEASE= translation makers based on - NUMBER value. Notice that - translation markers here were escaped using a backslash - (\) in order to prevent their expansion. Use this - option when you need to produce release-specific contents, but - no release information can be retrived from the directory path - you are currently rendering. - - - - - - - - - This option expands the =\ARCHITECTURE=, - translation makers based on ARHC value. - Notice that translation markers here were escaped using a - backslash (\) in order to prevent their - expansion. Use this option when you need to produce - architecture-sepecific contents but no architecture - information can be retrived from the directory path you are - currently rendering. - - - - - - - - - This option specifies the name of theme model you want to use - when producing theme artistic motifs. By default, if this - option is not provided, the Default theme - model is used as reference to produce theme artistic motifs. - To know what values can be passed as - MODELNAME, run the following - command: - - - - ls ${TCAR_WORKDIR}/Identity/Models/Themes - - - - - - - - - - This option lets you apply a command as post-rendition action. - In this case, the COMMAND - represents the command-line you want to execute in order to - perform in-place modifications to base-rendition output. - - - - - - - - - This option lets you apply a command as last-rendition action. - In this case, the COMMAND argument - represents the command string you want to execute in order to - perform in-place modifications to base-rendition, - post-rendition and directory-specific rendition outputs. - - - - - - - - Examples - - ... - - - - - Bugs - - To report bugs related to this function, please create a new - ticket here - refering the specific problems you found in it. For example, - it would be useful if you copy and paste any error output from - centos-art.sh script. - - - - - Authors - - The following people have worked in this functionality: - - - - - Alain Reguera Delgado <alain.reguera@gmail.com>, =COPYRIGHT_YEAR_LIST= - - - - - - - License - - - Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - - - - 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. - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/svn.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/svn.docbook deleted file mode 100644 index 179cf3d..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/svn.docbook +++ /dev/null @@ -1,83 +0,0 @@ - - - - svn - - Standardize version control tasks inside &TCAR; - - - - - svn - Standardize version control tasks inside &TCAR; - - - - - ... - - - - - Description - - ... - - - - - Usage - - ... - - - - - Function Specific Environment - - ... - - - - - Authors - - - - ... - - - - - - - License - - - Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - - - - 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. - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/tuneup.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/tuneup.docbook deleted file mode 100644 index c40f697..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/tuneup.docbook +++ /dev/null @@ -1,301 +0,0 @@ - - - - tuneup - - Standardize maintainance tasks inside &TCAR; - - - - - tuneup - Standardize maintainance tasks inside &TCAR; - - - - - The DIRECTORY parameter specifies the - directory path, inside the working copy of &TCAR;, where the - files you want to process are stored in. This paramter can be - provided more than once in order to process more than one - directory path in a single command execution. When this - parameter is not provided, the current directory path where - the command was called from is used instead. - - - - - Description - - - Tasks related to file maintainance are repetitive. You might - find yourself doing them time after time inside the working - copy of &TCAR;. Some of these maintainance tasks do update top - comments on shell scripts, create table of contents for web - pages, update metadata related to design models and remove - unused definitions from design models. - - - - When you execute the tuneup functionality of centos-art.sh - script, it looks for all files that match the supported - extensions (e.g., .sh, - .svg and .xhtml) in the directory - specified, builds a list with them and applies the - maintainance tasks using file extensions as refentry. - - - - When shell scripts are found, the tuneup - functionality of centos-art.sh script reads a comment template - from - Scripts/Functions/Tuneup/Shell/Config/topcomment.sed - and applies it to all shell scripts found, one by one. As - result, all shell scripts will end up having the same - copyright and license information the comment template does. - - - In order for the shell script top comment template to be - applied correctly, the shell scripts you write must have the - structure described in . - - - - Shell script top-comment template. - - Shell script top-comment template. - - - - 1| #!/bin/bash - 2| # - 3| # doSomething.sh -- The function description goes here. - 4| # - 5| # Copyright - 6| # - 7| # ... - 8| # - 9| # ---------------------------------------------------------------------- -10| # $Id$ -11| # ---------------------------------------------------------------------- -12| -13| function doSomething { -14| -15| } - - - - - - - - The tuneup functionality of - centos-art.sh script replaces all lines - between the Copyright line (e.g., line 5) - and the first separator line (e.g., line 9), inclusively. - Everything else will remain immutable in the file. - - - - When scalable vector graphics are found, the tuneup - functionality reads a SVG metadata template from - Scripts/Functions/Tuneup/Svg/Config/metadata.sed - and applies it to all files found, one by one. Immediatly - after the metadata template has been applied and, before - passing to next file, all unused definition are removed from - the file, too. - - - The metadata applied by the SVG metadata template is created - dynamicaly combining the absolute path of the file being - currently modified, the workstation's date information, the - centos-art.sh script copyright holder - (e.g., =COPYRIGHT_HOLDER=) as refentry and the Creative - Common Distribution-ShareAlike 3.0 License as default license - to release SVG files. - - - The elimination of unused definitions inside SVG files takes - place through Inkscape's - option, as described in its man page (e.g., man - inkscape). - - - - When HTML files are found, the tuneup - functionality of centos-art.sh script - transforms web page headings to make them accessible through a - table of contents. The table of contents is expanded in - place, wherever the <div - class="toc"></div> piece of code be in the - file. Once the table of contents has been expanded, there is - no need to put anything else in the page. You can run the - tuneup functionality everytime you update - the heading information so as to update the table of contents, - too. - - - In order for this functionality to build the table of contents - from headings, you need to put headings in just one line. The - headin level can vary from h1 to h6 - with attribute definitions accepted. Closing tag must be - present and also match the openning tag. Inside the heading - definition an anchor definition must be present with attribute - definitions accepted. The value of name - and href attributes from the anchor - element are set dynamically using the md5sum output of - combining the page location, the head- - string and the heading content itself. If any of the - components used to build the heading refentry changes, you - need to run the the tuneup functionality of - centos-art.sh script in order for the - anchor elements to use the correct information. - - - For example, the headings shown in produces the table of - contents shown in . - - - - HTML heading definition. - - HTML heading definition. - - - -<h1 class="title"><a name="head-8a23b56a28dfa7277d176576f217054a">Forms</a></h1> -<h2 class="title"><a name="head-629f38bc607f2a270177106b450aeae3">Elements</a></h2> -<h2 class="title"><a name="head-f49cae1d73592c984bbb0bffb1d5699a">Recommendations</a></h2> - - - - - - - - HTML table of contents definition. - - HTML table of contents definition. - - - -<div class="toc"> <p>Table of contents</p> <dl><dt><a href="#head-8a23b56a28dfa7277d176576f217054a">Forms</a> <dl><dt><a href="#head-629f38bc607f2a270177106b450aeae3">Elements</a> </dt><dt><a href="#head-f49cae1d73592c984bbb0bffb1d5699a">Recommendations</a> </dt></dl> </dt></dl> </div> - - - - - - - - - Options - - The tuneup functionality accepts the - following options: - - - - - - - - Supress all output messages except error messages. When this - option is passed, all confirmation requests are supressed and - a possitive answer is assumed for them, just as if the - option would have been provided. - - - - - - - - - Assume yes to all confirmation requests. - - - - - - - - - Reduce the list of files to process inside - path/to/dir using - REGEX as pattern. You can use this - option to control the amount of files you want to tuneup. The - deeper you go into the directory structure the more specific - you'll be about the files you want to tuneup. When you cannot - go deeper into the directory structure through - path/to/dir specification, use this - option to reduce the list of files therein. - - - - - - - - - Synchronizes available changes between the working copy and - the central repository. - - - - - - - - Function Specific Environment - - ... - - - - - Authors - - The following people have worked in the - tuneup functionality: - - - - - Alain Reguera Delgado <alain.reguera@gmail.com>, =COPYRIGHT_YEAR_LIST= - - - - - - - License - - - Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - - - - 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. - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/vcs.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/vcs.docbook deleted file mode 100644 index fbf8a4c..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/Scripts/Bash/vcs.docbook +++ /dev/null @@ -1,83 +0,0 @@ - - - - vcs - - Standardize version control tasks inside &TCAR; - - - - - vcs - Standardize version control tasks inside &TCAR; - - - - - ... - - - - - Description - - ... - - - - - Usage - - ... - - - - - Function Specific Environment - - ... - - - - - Authors - - - - ... - - - - - - - License - - - Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - - - - 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. - - - - - diff --git a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/tcar-ug.docbook b/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/tcar-ug.docbook deleted file mode 100644 index b0a19c9..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Docbook/Tcar-ug/tcar-ug.docbook +++ /dev/null @@ -1,84 +0,0 @@ - - - - - - - - The CentOS Artwork Repository - User's Guide - - - - Alain - Reguera Delgado - - - - - 2009 - 2010 - 2011 - 2012 - 2013 - &TCP;. All rights reserved. - - - - - 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 - . - - - - - - 1.0 - Today - - Alain - Reguera Delgado - - - - Under development. - - - - - - - - - &preface; - - &repo; - &identity; - &locales; - &manuals; - &scripts; - - - - Index - - diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters-menu.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters-menu.texinfo deleted file mode 100644 index e69de29..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters-menu.texinfo +++ /dev/null diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters-nodes.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters-nodes.texinfo deleted file mode 100644 index 3e2dc0b..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters-nodes.texinfo +++ /dev/null @@ -1 +0,0 @@ -@include =INCL= diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters.texinfo deleted file mode 100644 index 249e5cc..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters.texinfo +++ /dev/null @@ -1,12 +0,0 @@ -@node =CHAPTER_NODE= -@chapter =CHAPTER_TITLE= -@cindex =CHAPTER_CIND= - -@c -- Chapter Introduction -... - -@c -- Chapter Menu -@include =CHAPTER_NAME=-menu.texinfo - -@c -- Chapter Nodes -@include =CHAPTER_NAME=-nodes.texinfo diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters/section-functions.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters/section-functions.texinfo deleted file mode 100644 index 88cd2cc..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters/section-functions.texinfo +++ /dev/null @@ -1,35 +0,0 @@ -@node =SECT= -@section =SECT= -@cindex =CIND= - -@subheading Name - -The =SECT= directory organizes @dots{} - -@subheading Synopsis - -@dots{} - -@subheading Description - -@dots{} - -@subheading Examples - -@dots{} - -@subheading Author - -Written by @dots{} - -@subheading Reporting bugs - -Report bugs to @email{centos-artwork@@centos.org} mailing list. - -@subheading Copyright - -Copyright @copyright{} =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - -This is free software. You may redistribute copies of it under the -terms of the @ref{GNU General Public License}. There is NO WARRANTY, -to the extent permitted by law. diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters/section.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters/section.texinfo deleted file mode 100644 index 9461faa..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Chapters/section.texinfo +++ /dev/null @@ -1,8 +0,0 @@ -@node =NODE= -@section =SECT= -@cindex =CIND= - -... - -@c -- <[centos-art(SeeAlso) -@c -- ]> diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses-menu.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses-menu.texinfo deleted file mode 100755 index b8240ba..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses-menu.texinfo +++ /dev/null @@ -1,4 +0,0 @@ -@menu -* GNU General Public License:: -* GNU Free Documentation License:: -@end menu diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses-nodes.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses-nodes.texinfo deleted file mode 100755 index da69108..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses-nodes.texinfo +++ /dev/null @@ -1,9 +0,0 @@ -@node GNU General Public License -@section GNU General Public License -@cindex GNU General Public License -@include Licenses/GPL.texinfo - -@node GNU Free Documentation License -@section GNU Free Documentation License -@cindex GNU Free Documentation License -@include Licenses/GFDL.texinfo diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses.texinfo deleted file mode 100755 index 8b2fda9..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses.texinfo +++ /dev/null @@ -1,5 +0,0 @@ -@node Licenses -@appendix Licenses -@cindex Licenses -@include Licenses-menu.texinfo -@include Licenses-nodes.texinfo diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses/GFDL.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses/GFDL.texinfo deleted file mode 100755 index c40cf38..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses/GFDL.texinfo +++ /dev/null @@ -1,414 +0,0 @@ -Version 1.2, November 2002 - -@verbatim -Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. - 675 Mass Ave, Cambridge, MA 02139, USA -@end verbatim - -Everyone is permitted to copy and distribute verbatim copies of this -license document, but changing it is not allowed. - -@subheading 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. - -@subheading 1. Applicability and definitions - -This License applies to any manual or other work, in any medium, that -contains a notice placed by the copyright holder saying it can be -distributed under the terms of this License. Such a notice grants a -world-wide, royalty-free license, unlimited in duration, to use that -work under the conditions stated herein. The ``Document'', below, -refers to any such manual or work. Any member of the public is a -licensee, and is addressed as ``you''. You accept the license if you -copy, modify or distribute the work in a way requiring permission -under copyright law. - -A ``Modified Version'' of the Document means any work containing the -Document or a portion of it, either copied verbatim, or with -modifications and/or translated into another language. - -A ``Secondary Section'' is a named appendix or a front-matter section of -the Document that deals exclusively with the relationship of the -publishers or authors of the Document to the Document's overall -subject (or to related matters) and contains nothing that could fall -directly within that overall subject. (Thus, if the Document is in -part a textbook of mathematics, a Secondary Section may not explain -any mathematics.) The relationship could be a matter of historical -connection with the subject or with related matters, or of legal, -commercial, philosophical, ethical or political position regarding -them. - -The ``Invariant Sections'' are certain Secondary Sections 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 -Sections then there are none. - -The ``Cover Texts'' are certain short passages of text that are listed, -as Front-Cover Texts or Back-Cover Texts, in the notice that says that -the Document is released under this License. A Front-Cover Text may -be at most 5 words, and a Back-Cover Text may be at most 25 words. - -A ``Transparent'' copy of the Document means a machine-readable copy, -represented in a format whose specification is available to the -general public, that is suitable for revising the document -straightforwardly with generic text editors or (for images composed of -pixels) generic paint programs or (for drawings) some widely available -drawing editor, and that is suitable for input to text formatters or -for automatic translation to a variety of formats suitable for input -to text formatters. A copy made in an otherwise Transparent file -format whose markup, or absence of markup, has been arranged to thwart -or discourage subsequent modification by readers is not Transparent. -An image format is not Transparent if used for any substantial amount -of text. A copy that is not ``Transparent'' is called ``Opaque''. - -Examples of suitable formats for Transparent copies include plain -ASCII without markup, Texinfo input format, LaTeX input format, SGML -or XML using a publicly available DTD, and standard-conforming simple -HTML, PostScript or PDF designed for human modification. Examples of -transparent image formats include PNG, XCF and JPG. Opaque formats -include proprietary formats that can be read and edited only by -proprietary word processors, SGML or XML for which the DTD and/or -processing tools are not generally available, and the -machine-generated HTML, PostScript or PDF produced by some word -processors for output purposes only. - -The ``Title Page'' means, for a printed book, the title page itself, -plus such following pages as are needed to hold, legibly, the material -this License requires to appear in the title page. For works in -formats which do not have any title page as such, ``Title Page'' means -the text near the most prominent appearance of the work's title, -preceding the beginning of the body of the text. - -A section ``Entitled XYZ'' means a named subunit of the Document whose -title either is precisely XYZ or contains XYZ in parentheses following -text that translates XYZ in another language. (Here XYZ stands for a -specific section name mentioned below, such as ``Acknowledgements'', -``Dedications'', ``Endorsements'', or ``History''.) To ``Preserve the -Title'' of such a section when you modify the Document means that it -remains a section ``Entitled XYZ'' according to this definition. - -The Document may include Warranty Disclaimers next to the notice which -states that this License applies to the Document. These Warranty -Disclaimers are considered to be included by reference in this -License, but only as regards disclaiming warranties: any other -implication that these Warranty Disclaimers may have is void and has -no effect on the meaning of this License. - -@subheading 2. 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 @emph{3. -Copying in quantity}. - -You may also lend copies, under the same conditions stated above, and -you may publicly display copies. - -@subheading 3. 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 Cover -Texts: 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 Transparent -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 Transparent 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 Transparent 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. - -@subheading 4. Modifications - -You may copy and distribute a Modified Version of the Document under -the conditions of sections @emph{2. Verbatim copying} and @emph{3. -Copying in quantity} above, provided that you release the Modified -Version under precisely this License, with the Modified Version -filling the role of the Document, thus licensing distribution and -modification of the Modified Version to whoever possesses a copy of -it. In addition, you must do these things in the Modified Version: - -A. Use in the Title Page (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 Title Page, as authors, one or more persons or entities -responsible for authorship of the modifications in the Modified -Version, 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 Title page the name of the publisher of the Modified -Version, 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 Modified Version under the -terms of this License, in the form shown in the Addendum below. - -G. Preserve in that license notice the full lists of Invariant -Sections and required Cover Texts 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 Modified Version as given on the Title Page. 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 Title Page, then add an item describing the Modified -Version as stated in the previous sentence. - -J. Preserve the network location, if any, given in the Document for -public access to a Transparent 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 Invariant Sections 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 Modified Version. - -N. Do not retitle any existing section to be Entitled ``Endorsements'' -or to conflict in title with any Invariant Section. - -O. Preserve any Warranty Disclaimers. - -If the Modified Version includes new front-matter sections or -appendices that qualify as Secondary Sections 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 Invariant Sections in the Modified Version'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 Modified Version 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 Cover Texts in the Modified Version. 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 Modified Version. - -@subheading 5. Combining documents - -You may combine the Document with other documents released under this -License, under the terms defined in section @emph{4. Modifications} -above for modified versions, provided that you include in the -combination all of the Invariant Sections of all of the original -documents, unmodified, and list them all as Invariant Sections 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 Invariant Sections may be replaced with a single -copy. If there are multiple Invariant Sections 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 -Invariant Sections 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''. - -@subheading 6. Collections 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. - -@subheading 7. 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 @emph{3. Copying in quantity} -is applicable to these copies of the Document, then if the Document is -less than one half of the entire aggregate, the Document's Cover Texts -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. - -@subheading 8. Translations - -Translation is considered a kind of modification, so you may -distribute translations of the Document under the terms of section -@emph{4. Modifications}. Replacing Invariant Sections with -translations requires special permission from their copyright holders, -but you may include translations of some or all Invariant Sections in -addition to the original versions of these Invariant Sections. 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 @emph{4. -Modifications}) to Preserve its Title (section @emph{1. Applicability -and definitions}) will typically require changing the actual title. - -@subheading 9. 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. - -@subheading 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 -@url{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. - -@subheading 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: - -@verbatim - 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''. -@end verbatim - -If you have Invariant Sections, Front-Cover Texts and Back-Cover -Texts, replace the ``with...Texts''. line with this: - -@verbatim - with the Invariant Sections being LIST THEIR TITLES, with the - Front-Cover Texts being LIST, and with the Back-Cover Texts - being LIST. -@end verbatim - -If you have Invariant Sections without Cover Texts, 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/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses/GPL.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses/GPL.texinfo deleted file mode 100755 index 3349125..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/Licenses/GPL.texinfo +++ /dev/null @@ -1,376 +0,0 @@ -Version 2, June 1991 - -@verbatim -Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 675 Mass Ave, Cambridge, MA 02139, USA -@end verbatim - -Everyone is permitted to copy and distribute verbatim copies of this -license document, but changing it is not allowed. - -@subheading 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. - -@subheading TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - -@subsubheading 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. - -@subsubheading 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. - -@subsubheading 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 Section 1 -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. (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. - -@subsubheading Section 3 - -You may copy and distribute the Program (or a work based on it, under -Section 2) in object code or executable form under the terms of -Sections 1 and 2 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 Sections 1 -and 2 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 Sections 1 and 2 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. - -@subsubheading 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. - -@subsubheading 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. - -@subsubheading 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. - -@subsubheading 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. - -@subsubheading 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. - -@subsubheading 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. - -@subsubheading 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. - -@subsubheading NO WARRANTY - -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. - -@subsubheading 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. - -@strong{END OF TERMS AND CONDITIONS} - -@subheading 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. - -@verbatim - - 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. -@end verbatim - -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: - -@verbatim - 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. -@end verbatim - -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: - -@verbatim - 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 -@end verbatim - -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/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-index.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-index.texinfo deleted file mode 100755 index b197b13..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-index.texinfo +++ /dev/null @@ -1,8 +0,0 @@ -@node Index -@unnumbered Index -@syncodeindex fn cp -@syncodeindex vr cp -@syncodeindex ky cp -@syncodeindex pg cp -@syncodeindex tp cp -@printindex cp diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-init.pl b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-init.pl deleted file mode 100755 index c6eff54..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-init.pl +++ /dev/null @@ -1,7 +0,0 @@ -# This file extends the `../manual-init.pl' initialization file to -# provide English specific initializations for `texi2html-1.76-4.fc6'. -# ---------------------------------------------------------------------- -# $Id$ -# ---------------------------------------------------------------------- - -return 1; diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-menu.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-menu.texinfo deleted file mode 100644 index 0afc9ff..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-menu.texinfo +++ /dev/null @@ -1,4 +0,0 @@ -@menu -* Licenses:: -* Index:: -@end menu diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-nodes.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-nodes.texinfo deleted file mode 100644 index e69de29..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual-nodes.texinfo +++ /dev/null diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual.conf b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual.conf deleted file mode 100755 index 72b65de..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual.conf +++ /dev/null @@ -1,36 +0,0 @@ -# This file controls the manual configuration. This file is divided -# in configuration sections (e.g., `main' and `templates') which, in -# turn, are organized in the form `variable = value'. -# ---------------------------------------------------------------------- -# $Id$ -# ---------------------------------------------------------------------- - -[main] - -# Specify documentation backend used by documentation manual. This is -# the format used to write documentation manual source files. -manual_format = "texinfo" - -# Specify title style used by sections inside the manual. Possible -# values to this option are `cap-each-word' to capitalize each word in -# the section title, `cap-first-word' to capitalize the first word in -# the section title only and `directory' to transform each word in the -# section title into a directory path. From all these options, -# `cap-each-word' is the one used as default. -manual_section_style = "cap-each-word" - -# Specify the order used by sections inside the manual. By default new -# sections added to the manual are put on the end to follow the -# section `created' order. Other possible values to this option are -# `ordered' and `reversed' to sort the list of sections alphabetically -# from A-Z and Z-A, respectively. -manual_section_order = "created" - -[templates] - -# Specify relation between template files and section definition files -# inside the manual. Template definition is set on the left side using -# relative path. The section main definition file is described on the -# right using a regular expression. The first match wins. -Chapters/section-functions.texinfo = "^.+-functions-[[:alnum:]]+\.texinfo$" -Chapters/section.texinfo = "^.+\.texinfo$" diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual.sed b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual.sed deleted file mode 100755 index 274b0f5..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual.sed +++ /dev/null @@ -1,40 +0,0 @@ -#!/bin/sed -# -# repository.sed -- This file provide English transformations for -# texi2html outupt, based on The CentOS Project CSS definitions. -# -# Copyright (C) 2009-2012 The CentOS Project -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -# General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 -# USA. -# -# ---------------------------------------------------------------------- -# $Id$ -# ---------------------------------------------------------------------- - -# Quotations. -s!

Note!

Info

Note

!g - -s!

Warning!

Warning

Warning

!g - -s!

Important!

Important

Important

!g - -s!

Tip!

Tip

Tip

!g - -s!

Caution!

Caution

Caution

!g - -s!

Convention!

Convention

Convention

!g - -s!

Redirection!

Redirection

Redirection

!g diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual.texinfo deleted file mode 100644 index 0a7f838..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/en_US/manual.texinfo +++ /dev/null @@ -1,74 +0,0 @@ -\input texinfo @c -*-texinfo-*- -@c -- Header -------------------------------------------------- - -@setfilename =MANUAL_NAME=.info -@settitle =MANUAL_TITLE= -@documentlanguage =LOCALE_LL= -@afourpaper -@finalout - -@c -- Variables ----------------------------------------------- - -@set TCENTOS The Community Enterprise Operating System -@set TCPROJ @url{http://www.centos.org/, The CentOS Project} -@set TCWIKI @url{http://wiki.centos.org/, The CentOS Wiki} -@set TCMLISTS @url{http://lists.centos.org/, The CentOS Mailing Lists} -@set TCBUGS @url{http://bugs.centos.org/, The CentOS Bugs} -@set TCMIRRORS @url{http://mirrors.centos.org/, The CentOS Mirrors} -@set TCPLANET @url{http://planet.centos.org/, The CentOS Planet} -@set TCFORUMS @url{http://forums.centos.org/, The CentOS Forums} -@set TCINFOML @email{centos-info@@centos.org, The CentOS Information Mailing List} -@set TCDEVSML @email{centos-devel@@centos.org, The CentOS Developers Mailing List} -@set TCDOCSML @email{centos-docs@@centos.org, The CentOS Documentation Mailing List} -@set TCARTWML @email{centos-artwork@@centos.org, The CentOS Artwork Mailing List} -@set TCL10NML @email{centos-l10n@@centos.org, The CentOS Localization Mailing List} -@set TCAR @url{https://projects.centos.org/svn/artwork/, The CentOS Artwork Repository} -@set TCAS @url{https://projects.centos.org/trac/artwork/, The CentOS Artwork SIG} - -@c -- Summary description and copyright ----------------------- - -@copying -=MANUAL_ABSTRACT= - -Copyright @copyright{} =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - -Permission is granted to copy, distribute and/or modify this document -under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no -Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A -copy of the license is included in the section entitled @ref{GNU Free -Documentation License}. -@end copying - -@c -- Titlepage, contents, copyright --------------------------- - -@titlepage -@title =MANUAL_TITLE= -@subtitle =MANUAL_SUBTITLE= -@author =COPYRIGHT_HOLDER= -@page -@vskip 0pt plus 1filll -@insertcopying -@end titlepage -@contents - -@c -- `Top' node and master menu ------------------------------- - -@ifnottex -@node Top -@top =MANUAL_TITLE= -@insertcopying -@end ifnottex - -@include =MANUAL_NAME=-menu.texinfo - -@c -- The body of the document -------------------------------- - -@include =MANUAL_NAME=-nodes.texinfo - -@c -- The end of the document --------------------------------- - -@include Licenses.texinfo -@include =MANUAL_NAME=-index.texinfo - -@bye diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses-menu.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses-menu.texinfo deleted file mode 100755 index b8240ba..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses-menu.texinfo +++ /dev/null @@ -1,4 +0,0 @@ -@menu -* GNU General Public License:: -* GNU Free Documentation License:: -@end menu diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses-nodes.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses-nodes.texinfo deleted file mode 100755 index e7eded9..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses-nodes.texinfo +++ /dev/null @@ -1,9 +0,0 @@ -@node GNU General Public License -@section Licencia Pública General de GNU -@cindex Licencia pública general GNU -@include Licenses/GPL.texinfo - -@node GNU Free Documentation License -@section Licencia de Documentación Libre de GNU -@cindex Licencia documentación libre GNU -@include Licenses/GFDL.texinfo diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses.texinfo deleted file mode 100755 index be90966..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses.texinfo +++ /dev/null @@ -1,5 +0,0 @@ -@node Licenses -@appendix Licencias -@cindex Licencias -@include Licenses-menu.texinfo -@include Licenses-nodes.texinfo diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses/GFDL.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses/GFDL.texinfo deleted file mode 100755 index 8f789ec..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses/GFDL.texinfo +++ /dev/null @@ -1,372 +0,0 @@ -@subheading Preámbulo - -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. - -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. - -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. - -@subheading 1. Aplicación y definiciones - -Esta Licencia se aplica a cualquier manual u otro trabajo que contenga -un aviso colocado por el poseedor del copyright diciendo que puede -distribuirse bajo los términos de esta Licencia. El «Documento», -abajo, se refiere a cualquier manual o trabajo. Cualquier miembro del -público es un licenciatario,y será referido como «Usted». - -Una «Versión Modificada» del Documento significa cualquier trabajo que -contenga el Documento o una porción del mismo, ya sea una copia -literal o con modificaciones y/o traducciones a otro idioma. - -Una «Sección Secundaria» es un apéndice con título o una sección -preliminar del Documento que trata exclusivamente de la relación entre -los autores o editores y el tema general delDocumento que trata -exclusivamente con la relación entre los editores o autores del -Documento con el asunto general del Documento (o asuntos relacionados) -y no contiene nada que pueda considerarse dentro del tema principal. -(Por ejemplo, si el Documento es en parte un libro de texto de -matemáticas, una Sección Secundaria no explicará nada de matemáticas.) -La relación puede ser una conexión histórica con el asunto o temas -relacionados, o una opinión legal, comercial, filosófica, ética o -política acerca de ellos. - -Las «Secciones Invariantes» son ciertas Secciones Secundarias cuyos -títulos son designados como Secciones Invariantes en la nota que -indica que el Documento se publica bajo esta Licencia. - -Los «Textos de Cubierta» son ciertos pasajes cortos de texto que se -listan como Textos de Cubierta Delantera o Textos de Cubierta Trasera -en la nota que indica que el Documento se publica bajo esta Licencia. - -Una copia «Transparente» del Documento, significa una copia para -lectura en máquina, representada en un formato cuya especificación -está disponible al público en general, cuyo contenido puede ser visto -y editados directamente con editores de texto genéricos o (para -imágenes compuestas por píxeles) con programas genéricos de -manipulación de imágenes o (para dibujos) con algún editor de dibujos -ampliamente disponible, y que sea adecuado como entrada para -formateadores de texto o para su traducción automática a formatos -adecuados para formateadores de texto. Una copia hecha en un formato -definido como Transparente, pero cuyo marcaje o ausencia de él haya -sido diseñado para impedir o dificultar modificaciones posteriores por -parte de los lectores no es Transparente. Una copia que no es -«Transparente» se denomina «Opaca». - -Como ejemplos de formatos adecuados para copias Transparentes están -ASCII puro sin marcaje, formato de entrada de Texinfo, formato de -entrada de LaTeX, SGML o XML usando una DTD disponible públicamente, y -HTML, PostScript o PDF simples, que sigan los estándares y diseños -para que los modifiquen personas.Los formatos Opacos incluyen formatos -propietarios que pueden ser leídos y editados únicamente en -procesadores de textos propietarios, SGML o XML para los cuáles las -DTD y/o herramientas de procesamiento no estén ampliamente -disponibles, y HTML, PostScript o PDF generados por algunos -procesadores de textos sólo como salida. - -La «Portada» significa, en un libro impreso, la página de título, más -las páginas siguientes que sean necesarias para mantener legiblemente -el material que esta Licencia requiere en la portada. Para trabajos en -formatos que no tienen página de portada como tal, «Portada»significa -el texto cercano a la aparición más prominente del título del -trabajo,precediendo el comienzo del cuerpo del texto. - -@subheading 2. Copia literal - -Usted puede copiar y distribuir el Documento en cualquier medio, sea -en forma comercial o no, siempre y cuando proporcione esta Licencia, -las notas de copyright y la nota que indica que esta Licencia se -aplica al Documento reproduciéndola en todas las copias y que usted no -añada ninguna otra condición a las expuestas en esta Licencia. Usted -no puede usar medidas técnicas para obstruir o controlar la lectura o -copia posterior de las copias que usted haga o distribuya. Sin -embargo, usted puede aceptar compensación a cambio de las copias. Si -distribuye un número suficientemente grande de copias también deberá -seguir las condiciones de la sección 3. - -Usted también puede prestar copias, bajo las mismas condiciones -establecidas anteriormente, y puede exhibir copias públicamente. - -@subheading 3. Copiando en cantidad - -Si publica copias impresas del Documento que sobrepasen las 100, y la -nota de licencia del Documento exige Textos de Cubierta, debe -incluirlas copias con cubiertas que lleven en forma clara y legible -todos esos Textos de Cubierta: Textos de Cubierta Delantera en la -cubierta delantera y Textos de Cubierta Trasera en la cubierta -trasera. Ambas cubiertas deben identificarlo a Usted clara y -legiblemente como editor de tales copias. La cubierta debe mostrar el -título completo con todas las palabras igualmente prominentes y -visibles. Además puede añadir otro material en las cubiertas. Las -copias con cambios limitados a las cubiertas, siempre que conserven el -título del Documento y satisfagan estas condiciones, pueden -considerarse como copias literales en todos los aspectos. - -Si los textos requeridos para la cubierta son muy voluminosos para que -ajusten legiblemente, debe colocar los primeros (tantos como sea -razonable colocar) en la verdadera cubierta y situar el resto en -páginas adyacentes. - -Si Usted publica o distribuye copias Opacas del Documento cuya -cantidad exceda las 100, debe incluir una copia Transparente, que -pueda ser leída por una máquina, con cada copia Opaca, o bien mostrar, -en cada copia Opaca, una dirección de red donde cualquier usuario de -la misma tenga acceso por medio de protocolos públicos y -estandarizados a una copia Transparente del Documento completa, sin -material adicional. Si usted hace uso de la última opción, deberá -tomar las medidas necesarias, cuando comience la distribución de las -copias Opacas en cantidad, para asegurar que esta copia Transparente -permanecerá accesible en el sitio establecido por lo menos un año -después de la última vez que distribuya una copia Opaca de esa edición -al público (directamente o a través de sus agentes o distribuidores). - -Se solicita, aunque no es requisito, que se ponga en contacto con los -autores del Documento antes de redistribuir gran número de copias, -para darles la oportunidad de que le proporcionen una versión -actualizada del Documento. - -@subheading 4. Modificaciones - -Puede copiar y distribuir una Versión Modificada del Documento bajo -las condiciones de las secciones 2 y 3 anteriores, siempre que Usted -libere la Versión Modificada bajo esta misma Licencia, con la Versión -Modificada haciendo el rol del Documento, por lo tanto dando Licencia -de distribución y modificación de la Versión Modificada a quienquiera -posea una copia de la misma. Además, debe hacer lo siguiente en la -Versión Modificada: - -A. Usar en la Portada (y en las cubiertas, si hay alguna) un título -distinto al del Documento y de sus versiones anteriores (que deberían, -si hay alguna, estar listadas en la sección de Historia del -Documento). Puede usar el mismo título de versiones anteriores al -original siempre y cuando quien las publicó originalmente otorgue -permiso. - -B. Listar en la Portada, como autores, una o más personas o entidades -responsables de la autoría de las modificaciones de la Versión -Modificada, junto con por lo menos cinco de los autores principales -del Documento (todos sus autores principales, si hay menos de cinco), -a menos que le eximan de tal requisito. - -C. Mostrar en la Portada como editor el nombre del editor de la -Versión Modificada - -D. Conservar todas las notas de copyright del Documento. - -E. Añadir una nota de copyright apropiada a sus modificaciones, -adyacente a las otras notas de copyright. - -F. Incluir, inmediatamente después de los avisos de copyright, una -nota de licencia dando el permiso público para usar la Versión -Modificada bajo los términos de esta Licencia, de la forma mostrada en -el Adenda de más abajo. - -G. Incluir, inmediatamente después de ese aviso de licencia, la lista -completa de Secciones invariantes y de los Textos de Cubierta que sean -requeridos en el aviso de Licencia del Documento original. - -H. Incluir una copia sin modificación de esta Licencia. - -I. Conservar la sección titulada «Historia», conservar su Título y -añadirle un elemento que declare al menos el título, el año, los -nuevos autores y el editor de la Versión Modificada, tal como figuran -en la Portada. Si no hay una sección titulada «Historia» en el -Documento, crear una estableciendo el título, el año, los autores y el -editor del Documento, tal como figuran en su Portada, añadiendo además -un elemento describiendo la Versión Modificada, como se estableció en -la sentencia anterior. - -J. Conservar la dirección en red, si la hay, dada en el Documento para -el acceso público a una copia Transparente del mismo, así como las -otras direcciones de red dadas en el Documento para versiones -anteriores en las que estuviese basado. Pueden ubicarse en la sección -«Historia». Se puede omitir la ubicación en red de un trabajo que haya -sido publicado por lo menos cuatro años antes que el Documento mismo, -o si el editor original de dicha versión da permiso. - -K. En cualquier sección titulada «Agradecimientos» o «Dedicatorias», -conservar el título de la sección y conservar en ella toda la -sustancia y el tono de los agradecimientos y/o dedicatorias incluidas -por cada contribuyente. - -L. Conservar todas las Secciones Invariantes del Documento, sin -alterar su texto ni sus títulos. Los números de sección o equivalentes -no se consideran parte de los títulos de la sección. - -M. Borrar cualquier sección titulada «Aprobaciones». Tales secciones -no pueden estar incluidas en las Versiones Modificadas. - -N. No cambiar el título de ninguna sección existente a «Aprobaciones» -ni a uno que entre en conflicto con el de alguna Sección Invariante. - -Si la Versión Modificada incluye secciones o apéndices nuevos que -cualifiquen como Secciones Secundarias y no contienen ningún material -copiado del Documento, puede opcionalmente designar algunas o todas -esas secciones como invariantes. Para hacerlo, añada sus títulos a la -lista de Secciones Invariantes en el aviso de licencia de la Versión -Modificada. Tales títulos deben ser distintos de cualquier otro título -de sección. - -Puede añadir una sección titulada «Aprobaciones», siempre que contenga -únicamente aprobaciones de su Versión Modificada por otras fuentes ---por ejemplo, observaciones de compañeros o que el texto ha sido -aprobado por una organización como definición oficial de un estándar. - -Puede añadir un pasaje de hasta cinco palabras como Texto de Cubierta -Delantera y un pasaje de hasta 25 palabras como Texto de Cubierta -Trasera al final de la lista de Texto de Cubierta en la Versión -Modificada. Una entidad sólo puede añadir (o hacer que se añada) un -pasaje al Texto de Cubierta Delantera y uno al de Cubierta Trasera. Si -el Documento ya incluye un textos de cubiertas añadidos previamente -por usted o por acuerdo previo con la entidad que usted representa, -usted no puede añadir otro; pero puede reemplazar el anterior, con -permiso explícito del editor anterior que agregó el texto anterior. - -Con esta Licencia ni los autores ni los editores del Documento dan -permiso para usar sus nombres para publicidad ni para asegurar o -implicar aprobación de cualquier Versión Modificada. - -@subheading 5. Combinación de documentos - -Usted puede combinar el Documento con otros documentos liberados bajo -esta Licencia, bajo los términos definidos en la sección section 4 más -arriba para versiones modificadas, siempre que incluya en la -combinación todas las Secciones Invariantes de todos los documentos -originales, sin modificaciones, y las liste todas como Secciones -Invariantes de su trabajo combinado en su aviso de licencia. - -El trabajo combinado necesita contener solamente una copia de esta -Licencia, y múltiples Secciones Invariantes idénticas pueden -reemplazarse por una sola copia. Si hay múltiples Secciones -Invariantes con el mismo nombre pero con contenidos diferentes, haga -el título de cada una de estas secciones único añadiéndolo al final de -este, entre paréntesis, el nombre del autor o de quien editó -originalmente esa sección, si es conocido, o si no, un número único. -Haga el mismo ajuste a los títulos de sección en la lista de Secciones -Invariantes en la nota de licencia del trabajo combinado. - -En la combinación, debe combinar cualquier sección titulada «Historia» -de los distintos documentos originales, formando una sección titulada -«Historia»; de la misma forma, combine cualquier sección titulada -«Reconocimientos» y cualquier sección titulada «Dedicatorias». Debe -borrar todas las secciones tituladas «Aprobaciones». - -@subheading 6. Colecciones de documentos - -Puede hacer una colección que conste del Documento y de otros -documentos publicados bajo esta Licencia, y reemplazar las copias -individuales de esta Licencia en todos los documentos por una sola -copia que esté incluida en la colección, siempre que siga las reglas -de esta Licencia para cada copia literal de cada uno de los documentos -en cualquiera de los demás aspectos. - -Puede extraer un solo documento de una de tales colecciones y -distribuirlo individualmente bajo esta Licencia, siempre que inserte -una copia de esta Licencia en el documento extraído, y siga esta -Licencia en todos los demás aspectos relativos a la copia literal de -dicho documento. - -@subheading 7. Agregación con trabajos independientes - -Una recopilación que conste del Documento o sus derivados y de otros -documentos o trabajos separados e independientes, en cualquier soporte -de almacenamiento o distribución, no cuenta como un todo como una -Versión Modificada del Documento, siempre que no se reclame ningún -derecho de copyright por la compilación. Dicha compilación se denomina -un «agregado», y esta Licencia no se aplica a otros trabajos -autocontenidos incluidos con el Documento. teniendo en cuenta que son -compilados, si no son los mismos trabajos derivados del Documento. Si -el requisito de Texto de Cubierta de la sección 3 es aplicable a estas -copias del Documento, entonces si el Documento es menor que un cuarto -del agregado completo, los Textos de Cubierta del Documento pueden -colocarse en cubiertas que enmarquen solamente el Documento dentro del -agregado. En caso contrario deben aparecer en cubiertas impresas -enmarcando todo el agregado. - -@subheading 8. Traducción - -La Traducción se considera como un tipo de modificación, por lo que -usted puede distribuir traducciones del Documento bajo los términos de -la sección 4. El reemplazo las Secciones Invariantes por traducciones -requiere permiso especial de los poseedores del copyright, pero usted -puede incluir traducciones de algunas o todas las Secciones -Invariantes junto con las versiones originales de las mismas. Puede -incluir una traducción de esta Licencia, siempre que incluya también -la versión original en inglés de esta Licencia. En caso de desacuerdo -entre la traducción y la versión original en inglés de esta Licencia, -la versión original en Inglés prevalecerá. - -@subheading 9. Terminación - -Usted no puede copiar, modificar, sublicenciar o distribuir el -Documento salvo por lo permitido expresamente por esta Licencia. -Cualquier otro intento de copia, modificación, sublicenciamiento o -distribución del Documento es nulo, y dará por terminados -automáticamente sus derechos bajo esa Licencia. Sin embargo, los -terceros que hayan recibido copias, o derechos, de usted bajo esta -Licencia no verán terminadas sus licencias, siempre que permanezcan en -total conformidad con ella. - -@subheading Revisiones futuras de esta licencia - -La Free Software Foundation puede publicar versiones nuevas y -revisadas de la Licencia de Documentación Libre GNU de vez en cuando. -Dichas versiones nuevas serán similares en espíritu a la presente -versión, pero pueden diferir en detalles para solucionar nuevos -problemas o preocupaciones. Vea @url{http://www.gnu.org/copyleft/}. - -Cada versión de la Licencia tiene un número de versión que la -distingue. Si el Documento especifica que se aplica una versión -numerada en particular de esta licencia o «cualquier versión -posterior», usted tiene la opción de seguir los términos y condiciones -de la versión especificada o cualquiera posterior que haya sido -publicada (no como borrador) por la Free Software Foundation. Si el -Documento no especifica un número de versión de esta Licencia, puede -escoger cualquier versión que haya sido publicada (no como borrador) -por la Free Software Foundation. - -@subheading Adenda - -Para usar esta licencia en un documento que usted haya escrito, -incluya una copia de la Licencia en el documento y ponga el siguiente -copyright y notificación de licencia justo después de la página de -título: - -@example -Copyright © AÑO SU NOMBRE. - -Se otorga permiso para copiar, distribuir y/o modificar este documento -bajo los términos de la Licencia de Documentación Libre de GNU, -Versión 1.1 o cualquier otra versión posterior publicada por la -Free Software Foundation; con las Secciones Invariantes siendo su -LISTE SUS TÍTULOS, con Textos de Cubierta Delantera siendo LISTA, y -con los Textos de Cubierta Trasera siendo LISTA. Una copia de la -licencia está incluida en la sección titulada «GNU Free -Documentation License». -@end example - -Si no tiene Secciones Invariantes, escriba «sin Secciones Invariantes» -en vez de decir cuáles son invariantes. Si no tiene Textos de Cubierta -Frontal, escriba «sin Textos de Cubierta Frontal»; de la misma manera -para Textos de Cubierta Trasera. - -Si su documento contiene ejemplos de código de programa no triviales, -recomendamos liberar estos ejemplos en paralelo bajo la licencia de -software libre que usted elija, como la Licencia Pública General de -GNU (@pxref{GNU General Public License}), para permitir su uso en -software libre. diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses/GPL.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses/GPL.texinfo deleted file mode 100755 index 79680fe..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/Licenses/GPL.texinfo +++ /dev/null @@ -1,329 +0,0 @@ -@subheading Preámbulo - -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. - -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. - -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. - -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. - -Protegemos sus derechos con la combinación de dos medidas: - -@itemize -@item Derechos de copia del software (copyright), y -@item Le ofrecemos esta licencia, que le da permiso legal para copiar, -distribuir y/o modificar el software. -@end itemize - -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. - -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. - -Los términos precisos y las condiciones para la copia, distribución y -modificación se exponen a continuación. - -@subheading TÉRMINOS Y CONDICIONES PARA LA COPIA, DISTRIBUCIÓN Y MODIFICACIÓN - -@subsubheading Sección 0 - -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». - -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. - -@subsubheading Sección 1 - -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. - -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. - -@subsubheading Sección 2 - -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 -Sección 1 anterior, probado que además usted cumpla con todas las -siguientes condiciones: - -@enumerate -@item Debe hacer que los ficheros modificados lleven anuncios -prominentes indicando que los ha cambiado y la fecha de cualquier -cambio. - -@item 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. - -@item 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. - -Excepción: 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. - -@end enumerate - -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ó. - -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. - -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. - -@subsubheading Sección 3 - -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 Secciones 1 y 2 anteriores, -supuesto que además cumpla una de las siguientes condiciones: - -@enumerate - -@item 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 las Secciones 1 y 2 mencionadas antes en un medio -habitualmente utilizado para el intercambio de software, o, - -@item 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 - -@item 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). -@end enumerate - -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. - -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. - -@subsubheading Sección 4 - -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. 5Sección 5 - -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. 6Sección 6 - -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. 7Sección 7 - -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. - -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. - -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. - -Este apartado pretende dejar completamente claro lo que se cree que es -una consecuencia del resto de esta Licencia. - -@subsubheading Sección 8 - -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. 9Sección 9 - -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. - -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. - -@subsubheading Sección 10 - -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. - -@subsubheading AUSENCIA DE GARANTÍA - -Sección 11 - -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. - -@subsubheading Sección 12 - -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. diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-index.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-index.texinfo deleted file mode 100755 index bed8139..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-index.texinfo +++ /dev/null @@ -1,8 +0,0 @@ -@node Index -@unnumbered Índice -@syncodeindex fn cp -@syncodeindex vr cp -@syncodeindex ky cp -@syncodeindex pg cp -@syncodeindex tp cp -@printindex cp diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-init.pl b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-init.pl deleted file mode 100755 index d8e2045..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-init.pl +++ /dev/null @@ -1,119 +0,0 @@ -# This file extends the '../manual-init.pl' initialization file to # provide Spanish translation messages for `texi2html-1.76-4.fc6'. -# ---------------------------------------------------------------------- -# $Id$ -# ---------------------------------------------------------------------- - -$LANGUAGES->{'es'} = { - ' The buttons in the navigation panels have the following meaning:' => 'Los botones en el panel de navegación tienen el significado siguiente:', - ' where the @strong{ Example } assumes that the current position is at @strong{ Subsubsection One-Two-Three } of a document of the following structure:' => 'donde el @strong{Ejemplo} asume que la posición actual es en @strong{Subsubsección Uno-Dos-Tres}', - ' Up ' => 'Arriba', - '%{acronym_like} (%{explanation})' => '', - '%{month}, %{day} %{year}' => '', - '%{name} of %{class}' => '%{name} de %{class}', - '%{name} on %{class}' => '%{name} en %{class}', - '%{node_file_href}' => '', - '%{node_file_href} @cite{%{book}}' => '', - '%{node_file_href} section `%{section}\' in @cite{%{book}}' => 'sección %{node_file_href} `%{section}\' en @cite{%{book}}', - '%{reference_name}' => '', - '%{style} %{number}' => '', - '%{style}: %{caption_first_line}' => '', - '%{style}: %{shortcaption_first_line}' => '', - '@b{%{quotation_arg}:} ' => '', - '@cite{%{book}}' => '', - 'About This Document' => 'Acerca de este documento', - 'April' => 'abril', - 'August' => 'agosto', - 'Button' => 'Botón', - 'Contents' => 'Contenidos', - 'Current Position' => 'Posición actual', - 'December' => 'diciembre', - 'February' => 'febrero', - 'Footnotes' => 'Pie de página', - 'From 1.2.3 go to' => 'Desde 1.2.3 va a', - 'Go to' => 'Ir a', - 'Index' => 'Índice', - 'Index Entry' => 'Entrada índice', - 'January' => 'enero', - 'July' => 'julio', - 'Jump to' => 'Saltar a', - 'June' => 'junio', - 'March' => 'marzo', - 'May' => 'mayo', - 'Menu:' => 'Menú:', - 'Name' => 'Nombre', - 'Next' => 'Siguiente', - 'November' => 'noviembre', - 'October' => 'octubre', - 'Overview' => 'Introducción', - 'Overview:' => 'Introducción:', - 'Prev' => 'Anterior', - 'Section' => 'Sección', - 'Section One' => 'Sección Uno', - 'See %{node_file_href}' => 'Véase %{node_file_href}', - 'See %{node_file_href} @cite{%{book}}' => 'Véase %{node_file_href} @cite{%{book}}', - 'See %{node_file_href} section `%{section}\' in @cite{%{book}}' => 'Véase la sección %{node_file_href} `%{section}\' en @cite{%{book}}', - 'See %{reference_name}' => 'Véase %{reference_name}', - 'See @cite{%{book}}' => 'Véase @cite{%{book}}', - 'See section %{reference_name}' => 'Véase la sección %{reference_name}', - 'See section `%{section}\' in @cite{%{book}}' => 'Véase la sección `%{section}\' en @cite{%{book}}', - 'September' => 'septiembre', - 'Short Table of Contents' => 'Resumen del Contenido', - 'Subsection One-Four' => 'Subsección Uno-Cuatro', - 'Subsection One-One' => 'Subsección Uno-Uno', - 'Subsection One-Three' => 'Subsección Uno-Tres', - 'Subsection One-Two' => 'Subsección Uno-Dos', - 'Subsubsection One-Two-Four' => 'Subsubsección Uno-Dos-Cuatro', - 'Subsubsection One-Two-One' => 'Subsubsección Uno-Dos-Uno', - 'Subsubsection One-Two-Three' => 'Subsubsección Uno-Dos-Tress', - 'Subsubsection One-Two-Two' => 'Subsubsección Uno-Dos-Dos', - 'T2H_today' => '', - 'Table of Contents' => 'Tabla de contenidos', - 'This document was generated by @emph{%{user}} on @emph{%{date}} using @uref{%{program_homepage}, @emph{%{program}}}.' => 'Este documento fue generado pr @emph{%{user}} en @emph{%{date}} usando @uref{%{program_homepage}, @emph{%{program}}}.', - 'This document was generated by @emph{%{user}} using @uref{%{program_homepage}, @emph{%{program}}}.' => 'Este documento fue generado por @emph{%{user}} usando @uref{%{program_homepage}, @emph{%{program}}}.', - 'This document was generated on @i{%{date}} using @uref{%{program_homepage}, @i{%{program}}}.' => 'Este documento fue generado en @i{%{date}} usando @uref{%{program_homepage}, @i{%{program}}}.', - 'This document was generated using @uref{%{program_homepage}, @emph{%{program}}}.' => 'Este documento fue generado usando @uref{%{program_homepage}, @emph{%{program}}}.', - 'Top' => 'Inicio', - 'Untitled Document' => 'Documento sintítulo', - 'about (help)' => 'Acerca de (ayuda)', - 'beginning of this chapter or previous chapter' => 'Inicio del capítulo o capítulo anterior', - 'by @emph{%{user}}' => 'por @emph{%{user}}', - 'by @emph{%{user}} on @emph{%{date}}' => 'por @emph{%{user}} el @emph{%{date}}', - 'cover (top) of document' => 'Cubierta (inicio) del documento', - 'current' => 'actual', - 'current section' => 'Sección actual', - 'first section in reading order' => 'Primera sección en orden de lectura', - 'following node' => 'Nodo siguiente', - 'index' => 'Índice', - 'last section in reading order' => 'Última sección en orden de lectura', - 'next chapter' => 'Capítulo siguiente', - 'next node' => 'Nodo siguiente', - 'next section in reading order' => 'Sección siguiente en order de lectura', - 'next section on same level' => 'Sección siguiente en el mismo nivel', - 'node following in node reading order' => 'siguiente nodo en orden de lectura', - 'node up' => 'nodo arriba', - 'on @emph{%{date}}' => 'el @emph{%{date}}', - 'previous node' => 'nodo anterior', - 'previous section in reading order' => 'Sección anterior en orden de lectura', - 'previous section on same level' => 'Sección anterior en el mismo nivel', - 'section `%{section}\' in @cite{%{book}}' => 'sección `%{section}\' en @cite{%{book}}', - 'see %{node_file_href}' => 'Véase %{node_file_href}', - 'see %{node_file_href} @cite{%{book}}' => 'Véase %{node_file_href} @cite{%{book}}', - 'see %{node_file_href} section `%{section}\' in @cite{%{book}}' => 'Véase %{node_file_href} sección `%{section}\' en @cite{%{book}}', - 'see %{reference_name}' => 'Véase %{reference_name}', - 'see @cite{%{book}}' => 'Véase @cite{%{book}}', - 'see section %{reference_name}' => 'véase sección %{reference_name}', - 'see section `%{section}\' in @cite{%{book}}' => 'véase sección `%{section}\' en @cite{%{book}}', - 'short table of contents' => 'resumen del contenido', - 'table of contents' => 'Tabla de contenidos', - 'unknown' => 'desconocido', - 'up node' => 'nodo superior', - 'up section' => 'Sección superior' - }; - -$T2H_OBSOLETE_STRINGS->{'es'} = { - 'See' => 'Véase', - 'section' => 'sección', - 'see' => 'véase' - }; - -return 1; diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-menu.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-menu.texinfo deleted file mode 100644 index 0afc9ff..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-menu.texinfo +++ /dev/null @@ -1,4 +0,0 @@ -@menu -* Licenses:: -* Index:: -@end menu diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-nodes.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-nodes.texinfo deleted file mode 100644 index e69de29..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual-nodes.texinfo +++ /dev/null diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual.conf b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual.conf deleted file mode 100755 index b4f9ae4..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual.conf +++ /dev/null @@ -1,43 +0,0 @@ -# Este fichero controla la configuración del manual. Este fichero -# está dividido en diferentes secciones de configuración (e.g., `main' -# para organizar la configuración principal y `templates' para -# organizar la relación de asiganación plantillas-sección). Cada -# sección de configuración está organizada en pares de valores -# `variable = valor' usados para describir las preferencias de -# configuración. -# ---------------------------------------------------------------------- -# $Id$ -# ---------------------------------------------------------------------- - -[main] - -# Especifica el trasfondo de documentación usado por el manual. Este -# es el formato utilizado para redactar los ficheros fuentes del -# manual de documentación. -manual_format = "texinfo" - -# Especifica el estilo de títulos utilizados por las secciones del -# manual. Los valores posibles para esta opción son `cap-each-word' -# para escribir la primera letra de cada palabra en el título con -# mayúscula y el resto en minúscula, `cap-first-word' para escribir -# solo la primera letra del título en mayúscula y el resto en -# minúscula; y `directory' para transformar el título en un camino de -# directorio. -manual_section_style = "cap-each-word" - -# Especifica el order con que se muestran las secciones en el manual. -# Los valores posibles para esta opción son `created' para ubicar las -# nuevas secciones creadas en orden de creación, `ordered' para -# ordenar las secciones alfabéticamente sin importar el orden con el -# cual fueron creadas; y `reversed' lo contrario the `ordered'. -manual_section_order = "created" - -[templates] - -# Especifica la relación entre los ficheros de plantilla y los -# ficheros de definición de secciones en el manual. La definición de -# las plantillas se escriben en forma de camino relativo en el -# izquierdo y la definición de secciones en forma de expresión regular -# en el lado derecho. -Chapters/section-functions.texinfo = "^.+-functions-[[:alnum:]]+\.texinfo$" -Chapters/section.texinfo = "^.+\.texinfo$" diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual.sed b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual.sed deleted file mode 100644 index baa4b5b..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual.sed +++ /dev/null @@ -1,40 +0,0 @@ -#!/bin/sed -# -# repository.sed -- This file provide Spanish transformations for -# texi2html outupt, based on The CentOS Project CSS definitions. -# -# Copyright (C) 2009-2012 The CentOS Project -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -# General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 -# USA. -# -# ---------------------------------------------------------------------- -# $Id$ -# ---------------------------------------------------------------------- - -# Quotations. -s!

Nota!

Info

Nota

!g - -s!

Advertencia!

Advertencia

Advertencia

!g - -s!

Importante!

Importante

Importante

!g - -s!

Idea!

Idea

Idea

!g - -s!

Precaución!

Precaución

Precaución

!g - -s!

Convensión!

Convensión

Convensión

!g - -s!

Redirección!

Redirección

Redirección

!g diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual.texinfo b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual.texinfo deleted file mode 100644 index c21f607..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/es_ES/manual.texinfo +++ /dev/null @@ -1,75 +0,0 @@ -\input texinfo @c -*-texinfo-*- -@c -- Header -------------------------------------------------- - -@setfilename =MANUAL_NAME=.info -@settitle =MANUAL_TITLE= -@documentlanguage es -@afourpaper -@finalout - -@c -- Variables ----------------------------------------------- - -@set TCENTOS The Community Enterprise Operating System -@set TCPROJ @url{http://www.centos.org/, The CentOS Project} -@set TCWIKI @url{http://wiki.centos.org/, The CentOS Wiki} -@set TCMLISTS @url{http://lists.centos.org/, The CentOS Mailing Lists} -@set TCBUGS @url{http://bugs.centos.org/, The CentOS Bugs} -@set TCMIRRORS @url{http://mirrors.centos.org/, The CentOS Mirrors} -@set TCPLANET @url{http://planet.centos.org/, The CentOS Planet} -@set TCFORUMS @url{http://forums.centos.org/, The CentOS Forums} -@set TCINFOML @email{centos-info@@centos.org, The CentOS Information Mailing List} -@set TCDEVSML @email{centos-devel@@centos.org, The CentOS Developers Mailing List} -@set TCDOCSML @email{centos-docs@@centos.org, The CentOS Documentation Mailing List} -@set TCARTWML @email{centos-artwork@@centos.org, The CentOS Artwork Mailing List} -@set TCL10NML @email{centos-l10n@@centos.org, The CentOS Localization Mailing List} -@set TCAR @url{https://projects.centos.org/svn/artwork/, The CentOS Artwork Repository} -@set TCAS @url{https://projects.centos.org/trac/artwork/, The CentOS Artwork SIG} - -@c -- Summary description and copyright ----------------------- - -@copying -=MANUAL_ABSTRACT= - -Copyright @copyright{} =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= - -Se otorga permiso para copiar, distribuir y/o modificar este documento -bajo los términos de la Licencia de Documentación Libre de GNU, -Versión 1.1 o cualquier otra versión posterior publicada por la Free -Software Foundation; con las Secciones Invariantes, con Textos de -Cubierta Delantera, y con los Textos de Cubierta Trasera. Una copia de -la licencia está incluida en la sección titulada @ref{GNU Free -Documentation License}. -@end copying - -@c -- Titlepage, contents, copyright --------------------------- - -@titlepage -@title =MANUAL_TITLE= -@subtitle =MANUAL_SUBTITLE= -@author =COPYRIGHT_HOLDER= -@page -@vskip 0pt plus 1filll -@insertcopying -@end titlepage -@contents - -@c -- `Top' node and master menu ------------------------------- - -@ifnottex -@node Top -@top =MANUAL_TITLE= -@insertcopying -@end ifnottex - -@include =MANUAL_NAME=-menu.texinfo - -@c -- The body of the document -------------------------------- - -@include =MANUAL_NAME=-nodes.texinfo - -@c -- The end of the document --------------------------------- - -@include Licenses.texinfo -@include =MANUAL_NAME=-index.texinfo - -@bye diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/manual-init.pl b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/manual-init.pl deleted file mode 100755 index 8f68ea7..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/manual-init.pl +++ /dev/null @@ -1,389 +0,0 @@ -#!/usr/bin/perl -# -# repository.init -- This file initializes Texi2HTML program to -# produce the repository documentation manual using the CentOS Web -# Environment XHTML and CSS standard definition. -# -# Copyright (C) 2009, 2010, 2011 The CentOS Project -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -# General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 -# USA. -# ---------------------------------------------------------------------- -# $Id$ -# ---------------------------------------------------------------------- - -# -iso -# if set, ISO8859 characters are used for special symbols (like -# copyright, etc) -$USE_ISO = 1; - -# -I -# add a directory to the list of directories where @include files are -# searched for (besides the directory of the file). additional '-I' -# args are appended to this list. (APA: Don't implicitely search ., -# to conform with the docs!) my @INCLUDE_DIRS = ("."); -#@INCLUDE_DIRS = ("/home/al/Projects/CentOS/artwork"); - -# Extension used on output files. -$EXTENSION = "xhtml"; - -# Horizontal rules. -$DEFAULT_RULE = '

'; -$SMALL_RULE = $DEFAULT_RULE; -$MIDDLE_RULE = $DEFAULT_RULE; -$BIG_RULE = $DEFAULT_RULE; - -# -split section|chapter|node|none -# if $SPLIT is set to 'section' (resp. 'chapter') one html file per -# section (resp. chapter) is generated. If $SPLIT is set to 'node' one -# html file per node or sectionning element is generated. In all these -# cases separate pages for Top, Table of content (Toc), Overview and -# About are generated. Otherwise a monolithic html file that contains -# the whole document is created. -$SPLIT = 'section'; - -# -sec-nav|-nosec-nav -# if this is set then navigation panels are printed at the beginning -# of each section. If the document is split at nodes then navigation -# panels are printed at the end if there were more than $WORDS_IN_PAGE -# words on page. -# -# If the document is split at sections this is ignored. -# -# This is most useful if you do not want to have section navigation -# with -split chapter. There will be chapter navigation panel at the -# beginning and at the end of chapters anyway. -$SECTION_NAVIGATION = 1; - -# Layout control -$print_page_head = \&T2H_XHTML_print_page_head; -$print_page_foot = \&T2H_XHTML_print_page_foot; -$print_frame = \&T2H_XHTML_print_frame; -$button_icon_img = \&T2H_XHTML_button_icon_img; -$print_navigation = \&T2H_XHTML_print_navigation; - -#FIXME update once it is more stabilized in texi2html.init -sub T2H_XHTML_print_page_head -{ - my $fh = shift; - my $longtitle = "$Texi2HTML::THISDOC{'title_unformatted'}"; - $longtitle .= ": $Texi2HTML::UNFORMATTED{'This'}" if exists $Texi2HTML::UNFORMATTED{'This'}; - print $fh < - - - - - $longtitle - - - - - - - - - - - - - - - - - -
- -
- -
- - -EOT -} - -sub T2H_XHTML_print_page_foot -{ - my $fh = shift; - my @date=localtime(time); - my $year=$date[5] += 1900; - my $program_string = program_string(); - print $fh <$program_string

- -
- -
- - -
- - - - -EOT -} - -# / in -sub T2H_XHTML_button_icon_img -{ - my $button = shift; - my $icon = shift; - my $name = shift; - return '' if (!defined($icon)); - if (defined($name) && $name) - { - $name = ": $name"; - } - else - { - $name = ''; - } - $button = "" if (!defined ($button)); - return qq{$button$name}; -} - -$simple_map{'*'} = '
'; - -# formatting functions - -$def_line = \&t2h_xhtml_def_line; -$index_summary = \&t2h_xhtml_index_summary; -$image = \&t2h_xhtml_image; - -# need / in -sub t2h_xhtml_image($$$) -{ - my $file = shift; - my $base = shift; - my $preformatted = shift; - return "[ $base ]" if ($preformatted); - return "\"$base\""; -} - -# process definition commands line @deffn for example -# replaced by -sub t2h_xhtml_def_line($$$$$) -{ - my $category = shift; - my $name = shift; - my $type = shift; - my $arguments = shift; - my $index_label = shift; - $index_label = '' if (!defined($index_label)); - $name = '' if (!defined($name) or ($name =~ /^\s*$/)); - $type = '' if (!defined($type) or $type =~ /^\s*$/); - if (!defined($arguments) or $arguments =~ /^\s*$/) - { - $arguments = ''; - } - else - { - $arguments = '' . $arguments . ''; - } - my $type_name = ''; - $type_name = " $type" if ($type ne ''); - $type_name .= ' ' . $name . '' if ($name ne ''); - $type_name .= $arguments . "\n"; - if (! $DEF_TABLE) - { - return '
'. '' . $category . ':' . $type_name . $index_label . "
\n"; - } - else - { - - return "\n" . $type_name . - "\n" . $category . $index_label . "\n" . "\n"; - } -} - -# There is a br which needs / -sub t2h_xhtml_index_summary($$) -{ - my $alpha = shift; - my $nonalpha = shift; - my $join = ''; - my $nonalpha_text = ''; - my $alpha_text = ''; - $join = "   \n
\n" if (@$nonalpha and @$alpha); - if (@$nonalpha) - { - $nonalpha_text = join("\n   \n", @$nonalpha) . "\n"; - } - if (@$alpha) - { - $alpha_text = join("\n   \n", @$alpha) . "\n   \n"; - } - #I18n - return "
" . &$I('Jump to') . ":   " . - $nonalpha_text . $join . $alpha_text . '
'; -} - -# Layout of navigation panel -sub T2H_XHTML_print_navigation -{ - my $fh = shift; - my $buttons = shift; - my $vertical = shift; - print $fh '' . "\n"; - - print $fh "" unless $vertical; - for my $button (@$buttons) - { - print $fh qq{\n} if $vertical; - print $fh qq{\n"; - print $fh "\n" if $vertical; - } - print $fh "" unless $vertical; - print $fh "
}; - - if (ref($button) eq 'CODE') - { - &$button($fh, $vertical); - } - elsif (ref($button) eq 'SCALAR') - { - print $fh "$$button" if defined($$button); - } - elsif (ref($button) eq 'ARRAY') - { - my $text = $button->[1]; - my $button_href = $button->[0]; - if (defined($button_href) and !ref($button_href) - and defined($text) and (ref($text) eq 'SCALAR') and defined($$text)) - { # use given text - if ($Texi2HTML::HREF{$button_href}) - { - print $fh "" . - &$anchor('', - $Texi2HTML::HREF{$button_href}, - $$text - ) - ; - } - else - { - print $fh $$text; - } - } - } - elsif ($button eq ' ') - { # handle space button - print $fh - $ICONS && $ACTIVE_ICONS{' '} ? - &$button_icon_img($button, $ACTIVE_ICONS{' '}) : - $NAVIGATION_TEXT{' '}; - #next; - } - elsif ($Texi2HTML::HREF{$button}) - { # button is active - my $btitle = $BUTTONS_GOTO{$button} ? - 'title="' . ucfirst($BUTTONS_GOTO{$button}) . '"' : ''; - if ($ICONS && $ACTIVE_ICONS{$button}) - { # use icon - print $fh '' . - &$anchor('', - $Texi2HTML::HREF{$button}, - &$button_icon_img($button, - $ACTIVE_ICONS{$button}, - #$Texi2HTML::NAME{$button}), - $Texi2HTML::NO_TEXI{$button}), - $btitle - ); - } - else - { # use text - print $fh - '[' . - &$anchor('', - $Texi2HTML::HREF{$button}, - $NAVIGATION_TEXT{$button}, - $btitle - ) . - ']'; - } - } - else - { # button is passive - print $fh - $ICONS && $PASSIVE_ICONS{$button} ? - &$button_icon_img($button, - $PASSIVE_ICONS{$button}, - #$Texi2HTML::NAME{$button}) : - $Texi2HTML::NO_TEXI{$button}) : - - "[" . $NAVIGATION_TEXT{$button} . "]"; - } - print $fh "
\n"; -} - -# Use icons for navigation. -$ICONS = 0; - -# insert here name of icon images for buttons -# Icons are used, if $ICONS and resp. value are set -%ACTIVE_ICONS = - ( - 'Top', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-top.png', - 'Contents', 'file:///usr/share/icons/Bluecurve/24x24/stock/help-contents.png', - 'Overview', '', - 'Index', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-find.png', - 'This', '', - 'Back', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png', - 'FastBack', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png', - 'Prev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png', - 'Up', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png', - 'Next', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png', - 'NodeUp', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png', - 'NodeNext', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png', - 'NodePrev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png', - 'Following', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png', - 'Forward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png', - 'FastForward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png', - 'About' , 'file:///usr/share/icons/Bluecurve/24x24/stock/gtk-about.png', - 'First', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png', - 'Last', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png', - ' ', '' - ); - -# Insert here name of icon images for these, if button is inactive -%PASSIVE_ICONS = - ( - 'Top', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-top.png', - 'Contents', 'file:///usr/share/icons/Bluecurve/24x24/stock/help-contents.png', - 'Overview', '', - 'Index', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-find.png', - 'This', '', - 'Back', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png', - 'FastBack', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png', - 'Prev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png', - 'Up', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png', - 'Next', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png', - 'NodeUp', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-up.png', - 'NodeNext', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png', - 'NodePrev', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-back.png', - 'Following', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png', - 'Forward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-go-forward.png', - 'FastForward', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png', - 'About' , 'file:///usr/share/icons/Bluecurve/24x24/stock/gtk-about.png', - 'First', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-first.png', - 'Last', 'file:///usr/share/icons/Bluecurve/24x24/stock/stock-goto-last.png', - ' ', '' - ); - -return 1; diff --git a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/manual.sed b/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/manual.sed deleted file mode 100644 index 2b89341..0000000 --- a/Artworks/Documentation/Repository/UserGuide/Texinfo/Default/manual.sed +++ /dev/null @@ -1,29 +0,0 @@ -#!/bin/sed -# -# repository.sed -- This file provides common transformations for -# texi2html output, based on The CentOS Project CSS definitions. -# -# Copyright (C) 2009, 2010, 2011 The CentOS Project -# -# This program is free software; you can redistribute it and/or modify -# it under the terms of the GNU General Public License as published by -# the Free Software Foundation; either version 2 of the License, or -# (at your option) any later version. -# -# This program is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY; without even the implied warranty of -# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU -# General Public License for more details. -# -# You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software -# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 -# USA. -# -# ---------------------------------------------------------------------- -# $Id$ -# ---------------------------------------------------------------------- - -# Links -#s! +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: diff --git a/Artworks/Documentation/Showroom/Clothes/cap-back.svgz b/Artworks/Documentation/Showroom/Clothes/cap-back.svgz deleted file mode 100644 index 72e4995..0000000 Binary files a/Artworks/Documentation/Showroom/Clothes/cap-back.svgz and /dev/null differ diff --git a/Artworks/Documentation/Showroom/Clothes/cap-front.svgz b/Artworks/Documentation/Showroom/Clothes/cap-front.svgz deleted file mode 100644 index a3f8291..0000000 Binary files a/Artworks/Documentation/Showroom/Clothes/cap-front.svgz and /dev/null differ diff --git a/Artworks/Documentation/Showroom/Clothes/cap-left.svgz b/Artworks/Documentation/Showroom/Clothes/cap-left.svgz deleted file mode 100644 index d2ef431..0000000 Binary files a/Artworks/Documentation/Showroom/Clothes/cap-left.svgz and /dev/null differ diff --git a/Artworks/Documentation/Showroom/Clothes/cap-right.svgz b/Artworks/Documentation/Showroom/Clothes/cap-right.svgz deleted file mode 100644 index bbd5996..0000000 Binary files a/Artworks/Documentation/Showroom/Clothes/cap-right.svgz and /dev/null differ diff --git a/Artworks/Documentation/Showroom/Clothes/shirt-back.svgz b/Artworks/Documentation/Showroom/Clothes/shirt-back.svgz deleted file mode 100644 index 2f4d897..0000000 Binary files a/Artworks/Documentation/Showroom/Clothes/shirt-back.svgz and /dev/null differ diff --git a/Artworks/Documentation/Showroom/Clothes/shirt-front.svgz b/Artworks/Documentation/Showroom/Clothes/shirt-front.svgz deleted file mode 100644 index a1403ab..0000000 Binary files a/Artworks/Documentation/Showroom/Clothes/shirt-front.svgz and /dev/null differ diff --git a/Artworks/Documentation/Showroom/Clothes/summary.svgz b/Artworks/Documentation/Showroom/Clothes/summary.svgz deleted file mode 100644 index 26f462f..0000000 Binary files a/Artworks/Documentation/Showroom/Clothes/summary.svgz and /dev/null differ diff --git a/Artworks/Documentation/Showroom/Clothes/tshirt-back.svgz b/Artworks/Documentation/Showroom/Clothes/tshirt-back.svgz deleted file mode 100644 index cd0d8c5..0000000 Binary files a/Artworks/Documentation/Showroom/Clothes/tshirt-back.svgz and /dev/null differ diff --git a/Artworks/Documentation/Showroom/Clothes/tshirt-front.svgz b/Artworks/Documentation/Showroom/Clothes/tshirt-front.svgz deleted file mode 100644 index 343ed4f..0000000 Binary files a/Artworks/Documentation/Showroom/Clothes/tshirt-front.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/common-design-model-fig1.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/common-design-model-fig1.svgz deleted file mode 100644 index 91b88e1..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/common-design-model-fig1.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/common-design-model-fig2.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/common-design-model-fig2.svgz deleted file mode 100644 index 38d267f..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/common-design-model-fig2.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/header-fig-1.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/header-fig-1.svgz deleted file mode 100755 index 7a8d5c1..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/header-fig-1.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/header-fig-2.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/header-fig-2.svgz deleted file mode 100755 index b183a40..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/header-fig-2.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/header-fig-summary.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/header-fig-summary.svgz deleted file mode 100755 index 2c6a56c..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/header-fig-summary.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-1.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-1.svgz deleted file mode 100755 index 9ca9a2b..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-1.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-2.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-2.svgz deleted file mode 100755 index ceb0db1..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-2.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-3.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-3.svgz deleted file mode 100755 index 5fdcd8b..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-3.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-4.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-4.svgz deleted file mode 100755 index a14ac0d..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-4.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-5.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-5.svgz deleted file mode 100755 index 27ccbee..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-5.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-summary.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-summary.svgz deleted file mode 100755 index f849e75..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/progress-fig-summary.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/splash-fig-1.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/splash-fig-1.svgz deleted file mode 100755 index 6015230..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/splash-fig-1.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/splash-fig-2.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/splash-fig-2.svgz deleted file mode 100755 index 2322cfc..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/splash-fig-2.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/splash-fig-summary.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/splash-fig-summary.svgz deleted file mode 100644 index 3d76b4a..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/splash-fig-summary.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/summary.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/summary.svgz deleted file mode 100755 index b23b620..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/summary.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-1.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-1.svgz deleted file mode 100755 index 3f6b27c..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-1.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-2.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-2.svgz deleted file mode 100755 index 9b11d80..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-2.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-3.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-3.svgz deleted file mode 100755 index bbed5ba..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-3.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-summary.svgz b/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-summary.svgz deleted file mode 100755 index 5120530..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/Anaconda/syslinux-fig-summary.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/BootUp/firstboot-fig-1.svgz b/Artworks/Documentation/Themes/Models/Distro/BootUp/firstboot-fig-1.svgz deleted file mode 100644 index 4aee16f..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/BootUp/firstboot-fig-1.svgz and /dev/null differ diff --git a/Artworks/Documentation/Themes/Models/Distro/BootUp/firstboot-fig-summary.svgz b/Artworks/Documentation/Themes/Models/Distro/BootUp/firstboot-fig-summary.svgz deleted file mode 100644 index 8b46337..0000000 Binary files a/Artworks/Documentation/Themes/Models/Distro/BootUp/firstboot-fig-summary.svgz and /dev/null differ diff --git a/Artworks/Documentation/Versions/schema-branching.svgz b/Artworks/Documentation/Versions/schema-branching.svgz deleted file mode 100644 index 1e53a09..0000000 Binary files a/Artworks/Documentation/Versions/schema-branching.svgz and /dev/null differ diff --git a/Artworks/Documentation/Webenv/customization-with-ads.svgz b/Artworks/Documentation/Webenv/customization-with-ads.svgz deleted file mode 100644 index 7f0ae99..0000000 Binary files a/Artworks/Documentation/Webenv/customization-with-ads.svgz and /dev/null differ diff --git a/Artworks/Documentation/Webenv/customization.svgz b/Artworks/Documentation/Webenv/customization.svgz deleted file mode 100644 index 482a531..0000000 Binary files a/Artworks/Documentation/Webenv/customization.svgz and /dev/null differ diff --git a/Artworks/Documentation/Webenv/homepage.svgz b/Artworks/Documentation/Webenv/homepage.svgz deleted file mode 100644 index 41b449c..0000000 Binary files a/Artworks/Documentation/Webenv/homepage.svgz and /dev/null differ diff --git a/Artworks/Documentation/Webenv/navigation.svgz b/Artworks/Documentation/Webenv/navigation.svgz deleted file mode 100644 index 69419c5..0000000 Binary files a/Artworks/Documentation/Webenv/navigation.svgz and /dev/null differ diff --git a/Artworks/Documentation/Webenv/webenv-html-defs.svgz b/Artworks/Documentation/Webenv/webenv-html-defs.svgz deleted file mode 100644 index e1483b4..0000000 Binary files a/Artworks/Documentation/Webenv/webenv-html-defs.svgz and /dev/null differ diff --git a/Artworks/Documentation/Webenv/wiki-moin.svgz b/Artworks/Documentation/Webenv/wiki-moin.svgz deleted file mode 100644 index 3a09750..0000000 Binary files a/Artworks/Documentation/Webenv/wiki-moin.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/0.svgz b/Artworks/Icons/Webenv/0.svgz new file mode 100644 index 0000000..f3fad04 Binary files /dev/null and b/Artworks/Icons/Webenv/0.svgz differ diff --git a/Artworks/Icons/Webenv/1.svgz b/Artworks/Icons/Webenv/1.svgz new file mode 100644 index 0000000..573d824 Binary files /dev/null and b/Artworks/Icons/Webenv/1.svgz differ diff --git a/Artworks/Icons/Webenv/10.svgz b/Artworks/Icons/Webenv/10.svgz new file mode 100644 index 0000000..b3fa1f0 Binary files /dev/null and b/Artworks/Icons/Webenv/10.svgz differ diff --git a/Artworks/Icons/Webenv/11.svgz b/Artworks/Icons/Webenv/11.svgz new file mode 100644 index 0000000..f0ff37c Binary files /dev/null and b/Artworks/Icons/Webenv/11.svgz differ diff --git a/Artworks/Icons/Webenv/12.svgz b/Artworks/Icons/Webenv/12.svgz new file mode 100644 index 0000000..50f7b43 Binary files /dev/null and b/Artworks/Icons/Webenv/12.svgz differ diff --git a/Artworks/Icons/Webenv/13.svgz b/Artworks/Icons/Webenv/13.svgz new file mode 100644 index 0000000..3c1c651 Binary files /dev/null and b/Artworks/Icons/Webenv/13.svgz differ diff --git a/Artworks/Icons/Webenv/14.svgz b/Artworks/Icons/Webenv/14.svgz new file mode 100644 index 0000000..88b979a Binary files /dev/null and b/Artworks/Icons/Webenv/14.svgz differ diff --git a/Artworks/Icons/Webenv/15.svgz b/Artworks/Icons/Webenv/15.svgz new file mode 100644 index 0000000..b048d6d Binary files /dev/null and b/Artworks/Icons/Webenv/15.svgz differ diff --git a/Artworks/Icons/Webenv/2.svgz b/Artworks/Icons/Webenv/2.svgz new file mode 100644 index 0000000..19a05aa Binary files /dev/null and b/Artworks/Icons/Webenv/2.svgz differ diff --git a/Artworks/Icons/Webenv/3.svgz b/Artworks/Icons/Webenv/3.svgz new file mode 100644 index 0000000..81cb255 Binary files /dev/null and b/Artworks/Icons/Webenv/3.svgz differ diff --git a/Artworks/Icons/Webenv/4.svgz b/Artworks/Icons/Webenv/4.svgz new file mode 100644 index 0000000..b5c3335 Binary files /dev/null and b/Artworks/Icons/Webenv/4.svgz differ diff --git a/Artworks/Icons/Webenv/5.svgz b/Artworks/Icons/Webenv/5.svgz new file mode 100644 index 0000000..e2c3bb6 Binary files /dev/null and b/Artworks/Icons/Webenv/5.svgz differ diff --git a/Artworks/Icons/Webenv/6.svgz b/Artworks/Icons/Webenv/6.svgz new file mode 100644 index 0000000..e66833b Binary files /dev/null and b/Artworks/Icons/Webenv/6.svgz differ diff --git a/Artworks/Icons/Webenv/7.svgz b/Artworks/Icons/Webenv/7.svgz new file mode 100644 index 0000000..995ba6b Binary files /dev/null and b/Artworks/Icons/Webenv/7.svgz differ diff --git a/Artworks/Icons/Webenv/8.svgz b/Artworks/Icons/Webenv/8.svgz new file mode 100644 index 0000000..92dab30 Binary files /dev/null and b/Artworks/Icons/Webenv/8.svgz differ diff --git a/Artworks/Icons/Webenv/9.svgz b/Artworks/Icons/Webenv/9.svgz new file mode 100644 index 0000000..ccb44a1 Binary files /dev/null and b/Artworks/Icons/Webenv/9.svgz differ diff --git a/Artworks/Icons/Webenv/Callouts/0.svgz b/Artworks/Icons/Webenv/Callouts/0.svgz deleted file mode 100644 index f3fad04..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/0.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/1.svgz b/Artworks/Icons/Webenv/Callouts/1.svgz deleted file mode 100644 index 573d824..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/1.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/10.svgz b/Artworks/Icons/Webenv/Callouts/10.svgz deleted file mode 100644 index b3fa1f0..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/10.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/11.svgz b/Artworks/Icons/Webenv/Callouts/11.svgz deleted file mode 100644 index f0ff37c..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/11.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/12.svgz b/Artworks/Icons/Webenv/Callouts/12.svgz deleted file mode 100644 index 50f7b43..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/12.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/13.svgz b/Artworks/Icons/Webenv/Callouts/13.svgz deleted file mode 100644 index 3c1c651..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/13.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/14.svgz b/Artworks/Icons/Webenv/Callouts/14.svgz deleted file mode 100644 index 88b979a..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/14.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/15.svgz b/Artworks/Icons/Webenv/Callouts/15.svgz deleted file mode 100644 index b048d6d..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/15.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/2.svgz b/Artworks/Icons/Webenv/Callouts/2.svgz deleted file mode 100644 index 19a05aa..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/2.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/3.svgz b/Artworks/Icons/Webenv/Callouts/3.svgz deleted file mode 100644 index 81cb255..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/3.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/4.svgz b/Artworks/Icons/Webenv/Callouts/4.svgz deleted file mode 100644 index b5c3335..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/4.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/5.svgz b/Artworks/Icons/Webenv/Callouts/5.svgz deleted file mode 100644 index e2c3bb6..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/5.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/6.svgz b/Artworks/Icons/Webenv/Callouts/6.svgz deleted file mode 100644 index e66833b..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/6.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/7.svgz b/Artworks/Icons/Webenv/Callouts/7.svgz deleted file mode 100644 index 995ba6b..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/7.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/8.svgz b/Artworks/Icons/Webenv/Callouts/8.svgz deleted file mode 100644 index 92dab30..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/8.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/9.svgz b/Artworks/Icons/Webenv/Callouts/9.svgz deleted file mode 100644 index ccb44a1..0000000 Binary files a/Artworks/Icons/Webenv/Callouts/9.svgz and /dev/null differ diff --git a/Artworks/Icons/Webenv/Callouts/render.conf b/Artworks/Icons/Webenv/Callouts/render.conf deleted file mode 100644 index f25d2a5..0000000 --- a/Artworks/Icons/Webenv/Callouts/render.conf +++ /dev/null @@ -1,63 +0,0 @@ -[0.png] -render-type = "svg" -render-from = "0.svgz" - -[1.png] -render-type = "svg" -render-from = "1.svgz" - -[2.png] -render-type = "svg" -render-from = "2.svgz" - -[3.png] -render-type = "svg" -render-from = "3.svgz" - -[4.png] -render-type = "svg" -render-from = "4.svgz" - -[5.png] -render-type = "svg" -render-from = "5.svgz" - -[6.png] -render-type = "svg" -render-from = "6.svgz" - -[7.png] -render-type = "svg" -render-from = "7.svgz" - -[8.png] -render-type = "svg" -render-from = "8.svgz" - -[9.png] -render-type = "svg" -render-from = "9.svgz" - -[10.png] -render-type = "svg" -render-from = "10.svgz" - -[11.png] -render-type = "svg" -render-from = "11.svgz" - -[12.png] -render-type = "svg" -render-from = "12.svgz" - -[13.png] -render-type = "svg" -render-from = "13.svgz" - -[14.png] -render-type = "svg" -render-from = "14.svgz" - -[15.png] -render-type = "svg" -render-from = "15.svgz" diff --git a/Artworks/Icons/Webenv/powered_by_centos.svgz b/Artworks/Icons/Webenv/powered_by_centos.svgz old mode 100755 new mode 100644 index 2597201..95570b8 Binary files a/Artworks/Icons/Webenv/powered_by_centos.svgz and b/Artworks/Icons/Webenv/powered_by_centos.svgz differ diff --git a/Artworks/Icons/Webenv/render.conf b/Artworks/Icons/Webenv/render.conf index 9934966..671fd17 100644 --- a/Artworks/Icons/Webenv/render.conf +++ b/Artworks/Icons/Webenv/render.conf @@ -89,6 +89,8 @@ render-from = "pagination-bg-2.svgz" [powered_by_centos.png] render-type = "svg" render-from = "powered_by_centos.svgz" +brand = "${TCAR_BASEDIR}/Artworks/Brands/Symbols/Default/Final/ffffff-0/ffffff/26/centos.png:x26+3+3" +brand = "${TCAR_BASEDIR}/Artworks/Brands/Types/Default/Final/ffffff-0/ffffff/11/centos.png:x11+30+15.7" [redirect.png] render-type = "svg" @@ -133,3 +135,67 @@ render-from = "ul.svgz" [warning.png] render-type = "svg" render-from = "warning.svgz" + +[0.png] +render-type = "svg" +render-from = "0.svgz" + +[1.png] +render-type = "svg" +render-from = "1.svgz" + +[2.png] +render-type = "svg" +render-from = "2.svgz" + +[3.png] +render-type = "svg" +render-from = "3.svgz" + +[4.png] +render-type = "svg" +render-from = "4.svgz" + +[5.png] +render-type = "svg" +render-from = "5.svgz" + +[6.png] +render-type = "svg" +render-from = "6.svgz" + +[7.png] +render-type = "svg" +render-from = "7.svgz" + +[8.png] +render-type = "svg" +render-from = "8.svgz" + +[9.png] +render-type = "svg" +render-from = "9.svgz" + +[10.png] +render-type = "svg" +render-from = "10.svgz" + +[11.png] +render-type = "svg" +render-from = "11.svgz" + +[12.png] +render-type = "svg" +render-from = "12.svgz" + +[13.png] +render-type = "svg" +render-from = "13.svgz" + +[14.png] +render-type = "svg" +render-from = "14.svgz" + +[15.png] +render-type = "svg" +render-from = "15.svgz" diff --git a/Artworks/Locales/es_ES/artworks-docs-licenses-gfdl.po b/Artworks/Locales/es_ES/artworks-docs-licenses-gfdl.po deleted file mode 100644 index e9be2e0..0000000 --- a/Artworks/Locales/es_ES/artworks-docs-licenses-gfdl.po +++ /dev/null @@ -1,638 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: centos-art-0.4\n" -"POT-Creation-Date: 2013-06-13 22:17-0400\n" -"PO-Revision-Date: 2013-06-13 22:17-0400\n" -"Last-Translator: Documentation SIG\n" -"Language-Team: Español\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" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:6(title) -msgid "GNU Free Documentation License" -msgstr "Licencia de Documentación Libre de GNU" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:8(para) -msgid "Version 1.2, November 2002" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:10(para) -msgid "" -"Copyright © 2000, 2001, 2002 Free Software Foundation, Inc. 675 Mass " -"Ave, Cambridge, MA 02139, USA" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:13(para) -msgid "" -"Everyone is permitted to copy and distribute verbatim copies of this license " -"document, but changing it is not allowed." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:18(title) -msgid "Preamble" -msgstr "Preámbulo" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:20(para) -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." - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:30(para) -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 , which is a copyleft " -"license designed for free software." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:36(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:50(title) -msgid "Applicability and definitions" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:52(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:63(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:69(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:83(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:93(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:100(para) -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 is called Opaque." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:118(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:130(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:139(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:150(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:162(title) -msgid "Verbatim copying" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:164(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:177(para) -msgid "" -"You may also lend copies, under the same conditions stated above, and you " -"may publicly display copies." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:184(title) -msgid "Copying in quantity" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:186(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:201(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:206(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:221(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:230(title) -msgid "Modifications" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:232(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:250(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:259(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:269(para) -msgid "" -"State on the the name of the publisher of the " -", as the publisher." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:276(para) -msgid "Preserve all the copyright notices of the Document." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:281(para) -msgid "" -"Add an appropriate copyright notice for your modifications adjacent to the " -"other copyright notices." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:287(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:295(para) -msgid "" -"Preserve in that license notice the full lists of and required given in the " -"Document's license notice." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:302(para) -msgid "Include an unaltered copy of this License." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:306(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:321(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:334(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:343(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:351(para) -msgid "" -"Delete any section Entitled Endorsements. Such a section may " -"not be included in the ." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:357(para) -msgid "" -"Do not retitle any existing section to be Entitled Endorsements or to conflict in title with any ." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:363(para) -msgid "Preserve any Warranty Disclaimers." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:367(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:380(para) -msgid "" -"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." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:390(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:406(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:417(title) -msgid "Combining documents" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:419(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:429(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:441(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:453(title) -msgid "Collection of documents" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:455(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:463(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:473(title) -msgid "Aggregation with independent works" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:475(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:485(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:499(title) -msgid "Translations" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:501(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:518(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:529(title) -msgid "Termination" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:531(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:544(title) -msgid "Future Revisions of this License" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:546(para) -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 ." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:553(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:568(title) -msgid "How to use this License for your documents" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:570(para) -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 "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:575(screen) -#, no-wrap -msgid "" -"\n" -"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.\n" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:586(para) -msgid "" -"If you have , Front-Cover Texts and " -"Back-Cover Texts, replace the with...Texts. line with this:" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:590(screen) -#, no-wrap -msgid "" -"\n" -"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.\n" -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:596(para) -msgid "" -"If you have without , or some other combination of the three, merge those two " -"alternatives to suit the situation." -msgstr "" - -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:601(para) -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. -#: Documentation/Models/Docbook/Default/Licenses/Gfdl/gfdl.docbook:0(None) -msgid "translator-credits" -msgstr "" diff --git a/Artworks/Locales/es_ES/artworks-docs-licenses-gpl.po b/Artworks/Locales/es_ES/artworks-docs-licenses-gpl.po deleted file mode 100644 index fe16e03..0000000 --- a/Artworks/Locales/es_ES/artworks-docs-licenses-gpl.po +++ /dev/null @@ -1,489 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: centos-art-0.4\n" -"POT-Creation-Date: 2013-06-12 14:04-0400\n" -"PO-Revision-Date: 2013-06-12 14:04-0400\n" -"Last-Translator: Documentation SIG\n" -"Language-Team: Español\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 "Version 2, June 1991" -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 "" - -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 "" - -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 "" - -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 "" - -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 "" - -msgid "We protect your rights with two steps:" -msgstr "" - -msgid "copyright the software, and" -msgstr "" - -msgid "" -"offer you this license which gives you legal permission to copy, distribute " -"and/or modify the software." -msgstr "" - -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 "" - -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 "" - -msgid "" -"The precise terms and conditions for copying, distribution and modification " -"follow." -msgstr "" - -msgid "Terms and Conditions for Copying, Distribution and Modification" -msgstr "" - -msgid "Section 1" -msgstr "" - -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 "" - -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 "" - -msgid "Section 2" -msgstr "" - -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 "" - -msgid "" -"You must cause the modified files to carry prominent notices stating that " -"you changed the files and the date of any change." -msgstr "" - -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 "" - -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 "" - -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 "" - -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 "" - -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 "" - -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 "" - -msgid "Section 3" -msgstr "" - -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 "" - -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 "" - -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 "" - -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 "" - -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 "" - -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 "" - -msgid "Section 4" -msgstr "" - -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 "" - -msgid "Section 5" -msgstr "" - -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 "" - -msgid "Section 6" -msgstr "" - -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 "" - -msgid "Section 7" -msgstr "" - -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 "" - -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 "" - -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 "" - -msgid "" -"This section is intended to make thoroughly clear what is believed to be a " -"consequence of the rest of this License." -msgstr "" - -msgid "Section 8" -msgstr "" - -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 "" - -msgid "Section 9" -msgstr "" - -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 "" - -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 "" - -msgid "Section 10" -msgstr "" - -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 "" - -msgid "NO WARRANTY" -msgstr "" - -msgid "Section 11" -msgstr "" - -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 "" - -msgid "Section 12" -msgstr "" - -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 "" - -msgid "End of Terms and Conditions." -msgstr "" - -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 " -"copyright line and a pointer to where the full notice is " -"found." -msgstr "" - -#, no-wrap -msgid "" -"\n" -"<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.\n" -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 "" -"\n" -"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.\n" -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 "" -"\n" -"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\n" -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/Artworks/Locales/es_ES/artworks-docs-manual.po b/Artworks/Locales/es_ES/artworks-docs-manual.po deleted file mode 100644 index e69de29..0000000 --- a/Artworks/Locales/es_ES/artworks-docs-manual.po +++ /dev/null diff --git a/Artworks/Locales/es_ES/artworks-models-concepts.po b/Artworks/Locales/es_ES/artworks-models-concepts.po deleted file mode 100644 index e69de29..0000000 --- a/Artworks/Locales/es_ES/artworks-models-concepts.po +++ /dev/null diff --git a/Artworks/Locales/es_ES/artworks-models-distro-5-anaconda.po b/Artworks/Locales/es_ES/artworks-models-distro-5-anaconda.po deleted file mode 100644 index e69de29..0000000 --- a/Artworks/Locales/es_ES/artworks-models-distro-5-anaconda.po +++ /dev/null diff --git a/Artworks/Locales/es_ES/artworks-models-media.po b/Artworks/Locales/es_ES/artworks-models-media.po deleted file mode 100644 index e69de29..0000000 --- a/Artworks/Locales/es_ES/artworks-models-media.po +++ /dev/null diff --git a/Artworks/Locales/es_ES/artworks-models-posters.po b/Artworks/Locales/es_ES/artworks-models-posters.po deleted file mode 100644 index e69de29..0000000 --- a/Artworks/Locales/es_ES/artworks-models-posters.po +++ /dev/null diff --git a/Artworks/Themes/Models/Media/Locales/en_US/label-netinstall.svgz.po b/Artworks/Themes/Models/Media/Locales/en_US/label-netinstall.svgz.po new file mode 100644 index 0000000..d736c6d --- /dev/null +++ b/Artworks/Themes/Models/Media/Locales/en_US/label-netinstall.svgz.po @@ -0,0 +1,59 @@ +msgid "" +msgstr "" +"Project-Id-Version: label-netinstall.svgz 0.6\n" +"POT-Creation-Date: 2013-11-06 13:33-0500\n" +"PO-Revision-Date: 2013-11-06 13:33-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" + +#, no-wrap +msgid "Net install" +msgstr "Net install" + +#, no-wrap +msgid "for =ARCH= architectures" +msgstr "for =ARCH= architectures" + +#, no-wrap +msgid "120mm" +msgstr "120mm" + +#, no-wrap +msgid "Copyright © =COPYRIGHT_YEAR= =COPYRIGHT_HOLDER_PREDICATE=" +msgstr "Copyright © =COPYRIGHT_YEAR= =COPYRIGHT_HOLDER_PREDICATE=" + +#, no-wrap +msgid "This artwork is released under the terms of =LICENSE=." +msgstr "This artwork is released under the terms of =LICENSE=." + +#, no-wrap +msgid "CD Labels" +msgstr "CD Labels" + +#, no-wrap +msgid "For CentOS =RELEASE= net install media on =ARCH= architectures." +msgstr "For CentOS =RELEASE= net install media on =ARCH= architectures." + +#, no-wrap +msgid "=RELEASE=" +msgstr "=RELEASE=" + +#, no-wrap +msgid "=URL=" +msgstr "=URL=" + +#, no-wrap +msgid "Copyright © =COPYRIGHT_YEAR= The CentOS Project" +msgstr "Copyright © =COPYRIGHT_YEAR= The CentOS Project" + +#, no-wrap +msgid "All rights reserved" +msgstr "All rights reserved" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Artworks/Themes/Models/Media/Locales/en_US/sleeve-netinstall.svgz.po b/Artworks/Themes/Models/Media/Locales/en_US/sleeve-netinstall.svgz.po new file mode 100644 index 0000000..86faadf --- /dev/null +++ b/Artworks/Themes/Models/Media/Locales/en_US/sleeve-netinstall.svgz.po @@ -0,0 +1,91 @@ +msgid "" +msgstr "" +"Project-Id-Version: sleeve-netinstall.svgz 0.6\n" +"POT-Creation-Date: 2013-11-06 13:33-0500\n" +"PO-Revision-Date: 2013-11-06 13:33-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" + +#, no-wrap +msgid "125mm" +msgstr "125mm" + +#, no-wrap +msgid "Net install" +msgstr "Net install" + +#, no-wrap +msgid "For =ARCH= architectures" +msgstr "For =ARCH= architectures" + +#, no-wrap +msgid "Copyright © =COPYRIGHT_YEAR= The CentOS Project. All rights reserved." +msgstr "Copyright © =COPYRIGHT_YEAR= The CentOS Project. All rights reserved." + +#, no-wrap +msgid "What is CentOS?" +msgstr "What is CentOS?" + +#, no-wrap +msgid "CentOS is an Enterprise GNU/Linux distribution based on the freely available sources from Red Hat Enterprise Linux. Each CentOS version is supported for 7 years (by means of security updates)." +msgstr "CentOS is an Enterprise GNU/Linux distribution based on the freely available sources from Red Hat Enterprise Linux. Each CentOS version is supported for 7 years (by means of security updates)." + +#, no-wrap +msgid "A new CentOS version is release every 2 years and each CentOS version is regularly updated (every 6 months) to support newer hardware." +msgstr "A new CentOS version is release every 2 years and each CentOS version is regularly updated (every 6 months) to support newer hardware." + +#, no-wrap +msgid "This results in a secure, low-maintenance, reliable, predictable and reproducible environment." +msgstr "This results in a secure, low-maintenance, reliable, predictable and reproducible environment." + +#, no-wrap +msgid "Visit =URL=, for more information." +msgstr "Visit =URL=, for more information." + +#, no-wrap +msgid "FOLD HERE" +msgstr "FOLD HERE" + +#, no-wrap +msgid "CD Sleeve" +msgstr "CD Sleeve" + +#, no-wrap +msgid "For CentOS =RELEASE= net install media on =ARCH= architectures." +msgstr "For CentOS =RELEASE= net install media on =ARCH= architectures." + +#, no-wrap +msgid "=RELEASE=" +msgstr "=RELEASE=" + +#, no-wrap +msgid "Copyright © =COPYRIGHT_YEAR= =COPYRIGHT_HOLDER_PREDICATE=" +msgstr "Copyright © =COPYRIGHT_YEAR= =COPYRIGHT_HOLDER_PREDICATE=" + +#, no-wrap +msgid "This artwork is released under the terms of =LICENSE=." +msgstr "This artwork is released under the terms of =LICENSE=." + +#, no-wrap +msgid "FOLDED SLEEVE" +msgstr "FOLDED SLEEVE" + +#, no-wrap +msgid "EMPTY CASE" +msgstr "EMPTY CASE" + +#, no-wrap +msgid "1" +msgstr "1" + +#, no-wrap +msgid "2" +msgstr "2" + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Artworks/Themes/Models/Release_notes/eula.asciidoc b/Artworks/Themes/Models/Release_notes/eula.asciidoc index d39d427..34f16d7 100644 --- a/Artworks/Themes/Models/Release_notes/eula.asciidoc +++ b/Artworks/Themes/Models/Release_notes/eula.asciidoc @@ -1,5 +1,4 @@ = CentOS-=RELEASE= EULA -The CentOS Project image:=TCAR_BASEDIR=/Artworks/Brands/Symbols/Default/Final/ffffff-0/ffffff/64/centos.png[The CentOS Symbol] diff --git a/Artworks/Themes/Models/Release_notes/index.asciidoc b/Artworks/Themes/Models/Release_notes/index.asciidoc index bfae94e..e97989b 100644 --- a/Artworks/Themes/Models/Release_notes/index.asciidoc +++ b/Artworks/Themes/Models/Release_notes/index.asciidoc @@ -1,10 +1,10 @@ = Welcome to CentOS -The CentOS Project image:=TCAR_BASEDIR=/Artworks/Brands/Symbols/Default/Final/ffffff-0/ffffff/64/centos.png[The CentOS Symbol] -The *Community ENTerprise Operating System* -(http://www.centos.org/[CentOS]) is an Enterprise-class Linux +== The Community ENTerprise Operating System + +http://www.centos.org/[CentOS] is an Enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor. CentOS conforms fully with the upstream vendors redistribution policy and aims to be diff --git a/Artworks/Themes/Models/Release_notes/release_notes.asciidoc b/Artworks/Themes/Models/Release_notes/release_notes.asciidoc index 7ba3f16..e0e89bc 100644 --- a/Artworks/Themes/Models/Release_notes/release_notes.asciidoc +++ b/Artworks/Themes/Models/Release_notes/release_notes.asciidoc @@ -1,5 +1,4 @@ = CentOS-=RELEASE= Release Notes -The CentOS Project image:=TCAR_BASEDIR=/Artworks/Brands/Symbols/Default/Final/ffffff-0/ffffff/64/centos.png[The CentOS Symbol] diff --git a/Artworks/Themes/Models/Release_notes/render.conf.tpl b/Artworks/Themes/Models/Release_notes/render.conf.tpl index 37fb5ff..af40069 100644 --- a/Artworks/Themes/Models/Release_notes/render.conf.tpl +++ b/Artworks/Themes/Models/Release_notes/render.conf.tpl @@ -3,8 +3,6 @@ render-type = "asciidoc" render-flow = "article" render-from = "${TCAR_BASEDIR}/Artworks/Themes/Models/Release_notes/release_notes.asciidoc" locale-from = "${TCAR_BASEDIR}/Artworks/Themes/Models/Release_notes/Locales/${TCAR_SCRIPT_LANG_LC}/release_notes.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-notoc" @@ -13,8 +11,6 @@ render-type = "asciidoc" render-flow = "article" render-from = "${TCAR_BASEDIR}/Artworks/Themes/Models/Release_notes/index.asciidoc" locale-from = "${TCAR_BASEDIR}/Artworks/Themes/Models/Release_notes/Locales/${TCAR_SCRIPT_LANG_LC}/index.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-notoc" @@ -23,8 +19,6 @@ render-type = "asciidoc" render-flow = "article" render-from = "${TCAR_BASEDIR}/Artworks/Themes/Models/Release_notes/firefox_service_agreement.asciidoc" locale-from = "${TCAR_BASEDIR}/Artworks/Themes/Models/Release_notes/Locales/${TCAR_SCRIPT_LANG_LC}/firefox_service_agreement.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-notoc" @@ -33,7 +27,5 @@ render-type = "asciidoc" render-flow = "article" render-from = "${TCAR_BASEDIR}/Artworks/Themes/Models/Release_notes/eula.asciidoc" locale-from = "${TCAR_BASEDIR}/Artworks/Themes/Models/Release_notes/Locales/${TCAR_SCRIPT_LANG_LC}/eula.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-notoc" diff --git a/Artworks/Webenv/Docbook/1.69.1/Css/headings.css b/Artworks/Webenv/Docbook/1.69.1/Css/headings.css index 869150d..370ebfd 100755 --- a/Artworks/Webenv/Docbook/1.69.1/Css/headings.css +++ b/Artworks/Webenv/Docbook/1.69.1/Css/headings.css @@ -85,8 +85,7 @@ div.section > div.titlepage h4.title { div.refnamediv { padding-top: 1.5em; - -} + } div.refentry div.refnamediv h2 span { font-family: "DejaVuLG Mono", monospace @@ -103,3 +102,8 @@ div.reference div.titlepage h1, div.reference div.titlepage h2 { margin: 0.5em 0; } + +div.figure p.title { + margin-top: 1.5em; + margin-bottom: 0.3em; + } diff --git a/Automation/Manuals/Locales/en_US/centos-art.sh.po b/Automation/Manuals/Locales/en_US/centos-art.sh.po index 7875450..4daf2be 100644 --- a/Automation/Manuals/Locales/en_US/centos-art.sh.po +++ b/Automation/Manuals/Locales/en_US/centos-art.sh.po @@ -1,8 +1,8 @@ msgid "" msgstr "" "Project-Id-Version: centos-art.sh.asciidoc 0.6\n" -"POT-Creation-Date: 2013-11-07 00:08-0500\n" -"PO-Revision-Date: 2013-11-07 00:08-0500\n" +"POT-Creation-Date: 2013-11-26 10:20-0500\n" +"PO-Revision-Date: 2013-11-26 10:20-0500\n" "Last-Translator: Localization SIG \n" "Language-Team: English\n" "MIME-Version: 1.0\n" @@ -20,169 +20,157 @@ msgid "The CentOS artwork repository automation tool." msgstr "The CentOS artwork repository automation tool." msgid "" -"centos-art.sh [--help|--version]" +"centos-art.sh [--help|--version]" msgstr "" -"centos-art.sh [--help|--version]" +"centos-art.sh [--help|--version]" msgid "" -"Print information about centos-art.sh script itself." +"Print information about centos-art.sh " +"script itself." msgstr "" -"Print information about centos-art.sh script itself." +"Print information about centos-art.sh " +"script itself." msgid "" -"centos-art.shMODULE [--help|--" -"version]" +"centos-art.shMODULE [--help|--version]" msgstr "" -"centos-art.shMODULE [--help|--" -"version]" +"centos-art.shMODULE [--help|--version]" msgid "" -"Print information about the specified module. See below to see which modules centos-art.sh script supports." +"Print information about the specified module. See below to see which modules centos-art.sh script supports." msgstr "" -"Print information about the specified module. See below to see which modules centos-art.sh script supports." +"Print information about the specified module. See below to see which modules centos-art.sh script supports." msgid "Description" msgstr "Description" msgid "" -"centos-art.sh exists to " -"standardize frequent tasks inside the CentOS artwork repository. " -"Inside centos-art.sh script, " -"frequent tasks are organized inside modules." +"centos-art.sh exists to standardize " +"frequent tasks inside the CentOS artwork repository. Inside centos-art.sh script, frequent tasks are organized " +"inside modules." msgstr "" -"centos-art.sh exists to " -"standardize frequent tasks inside the CentOS artwork repository. " -"Inside centos-art.sh script, " -"frequent tasks are organized inside modules." +"centos-art.sh exists to standardize " +"frequent tasks inside the CentOS artwork repository. Inside centos-art.sh script, frequent tasks are organized " +"inside modules." msgid "" -"When you execute the centos-art.sh script in a terminal, it requests you to enter the " -"absolute path of CentOS artwork repository in your workstation. " -"This information is required in order for centos-art.sh to know where the repository directory " -"structure you want to work with is stored in. Later, once centos-art.sh knows where your copy of " -"CentOS artwork repository is stored in, it initializes " -"configuration variables and global functions. At this point, it " -"continues reading the command-line arguments to retrieve the " -"module's name, process common options next to it, store module-" -"specific options and initiates the module's environment by " -"executing the module's initialization script, based on the module's " -"name retrieved from the command-line." +"When you execute the centos-art.sh " +"script in a terminal, it requests you to enter the absolute path of CentOS " +"artwork repository in your workstation. This information is required in " +"order for centos-art.sh to know where " +"the repository directory structure you want to work with is stored in. " +"Later, once centos-art.sh knows where " +"your copy of CentOS artwork repository is stored in, it initializes " +"configuration variables and global functions. At this point, it continues " +"reading the command-line arguments to retrieve the module's name, process " +"common options next to it, store module-specific options and initiates the " +"module's environment by executing the module's initialization script, based " +"on the module's name retrieved from the command-line." msgstr "" -"When you execute the centos-art.sh script in a terminal, it requests you to enter the " -"absolute path of CentOS artwork repository in your workstation. " -"This information is required in order for centos-art.sh to know where the repository directory " -"structure you want to work with is stored in. Later, once centos-art.sh knows where your copy of " -"CentOS artwork repository is stored in, it initializes " -"configuration variables and global functions. At this point, it " -"continues reading the command-line arguments to retrieve the " -"module's name, process common options next to it, store module-" -"specific options and initiates the module's environment by " -"executing the module's initialization script, based on the module's " -"name retrieved from the command-line." +"When you execute the centos-art.sh " +"script in a terminal, it requests you to enter the absolute path of CentOS " +"artwork repository in your workstation. This information is required in " +"order for centos-art.sh to know where " +"the repository directory structure you want to work with is stored in. " +"Later, once centos-art.sh knows where " +"your copy of CentOS artwork repository is stored in, it initializes " +"configuration variables and global functions. At this point, it continues " +"reading the command-line arguments to retrieve the module's name, process " +"common options next to it, store module-specific options and initiates the " +"module's environment by executing the module's initialization script, based " +"on the module's name retrieved from the command-line." msgid "Modules" msgstr "Modules" msgid "" -"The centos-art.sh script " -"supports the following modules:" +"The centos-art.sh script supports the " +"following modules:" msgstr "" -"The centos-art.sh script " -"supports the following modules:" +"The centos-art.sh script supports the " +"following modules:" msgid "prepare" msgstr "prepare" msgid "" -"Standardize configuration tasks needed by your working copy (e.g., " -"verify whether required packages are installed or not in your " -"workstation, calls render module to produce images and manuals in " -"the correct order). This is the first task you should run in your " -"workstation, just after downloading a fresh working copy of CentOS " -"artwork repository." +"Standardize configuration tasks needed by your working copy (e.g., verify " +"whether required packages are installed or not in your workstation, calls " +"render module to produce images and manuals in the correct order). This is " +"the first task you should run in your workstation, just after downloading a " +"fresh working copy of CentOS artwork repository." msgstr "" -"Standardize configuration tasks needed by your working copy (e.g., " -"verify whether required packages are installed or not in your " -"workstation, calls render module to produce images and manuals in " -"the correct order). This is the first task you should run in your " -"workstation, just after downloading a fresh working copy of CentOS " -"artwork repository." +"Standardize configuration tasks needed by your working copy (e.g., verify " +"whether required packages are installed or not in your workstation, calls " +"render module to produce images and manuals in the correct order). This is " +"the first task you should run in your workstation, just after downloading a " +"fresh working copy of CentOS artwork repository." msgid "render" msgstr "render" msgid "" -"Standardize the way content is produced inside the repository. This " -"function relies on configuration files to do its work. Whenever you " -"need to produce images, documentation or localized content this is " -"the module you'll need to use." +"Standardize the way content is produced inside the repository. This function " +"relies on configuration files to do its work. Whenever you need to produce " +"images, documentation or localized content this is the module you'll need to " +"use." msgstr "" -"Standardize the way content is produced inside the repository. This " -"function relies on configuration files to do its work. Whenever you " -"need to produce images, documentation or localized content this is " -"the module you'll need to use." +"Standardize the way content is produced inside the repository. This function " +"relies on configuration files to do its work. Whenever you need to produce " +"images, documentation or localized content this is the module you'll need to " +"use." msgid "locale" msgstr "locale" msgid "" -"Standardize the way translatable strings are retrieved from source " -"files and put into portable objects for you to edit. Portable " -"objects produced by this module are used by render module to produce localized content. Whenever " -"you need to produce the intermediate files holding the translatable " -"strings required to produce localized content, use this module." +"Standardize the way translatable strings are retrieved from source files and " +"put into portable objects for you to edit. Portable objects produced by this " +"module are used by render module to " +"produce localized content. Whenever you need to produce the intermediate " +"files holding the translatable strings required to produce localized " +"content, use this module." msgstr "" -"Standardize the way translatable strings are retrieved from source " -"files and put into portable objects for you to edit. Portable " -"objects produced by this module are used by render module to produce localized content. Whenever " -"you need to produce the intermediate files holding the translatable " -"strings required to produce localized content, use this module." +"Standardize the way translatable strings are retrieved from source files and " +"put into portable objects for you to edit. Portable objects produced by this " +"module are used by render module to " +"produce localized content. Whenever you need to produce the intermediate " +"files holding the translatable strings required to produce localized " +"content, use this module." msgid "tuneup" msgstr "tuneup" msgid "" -"Standardize maintenance tasks frequently run inside the repository " -"(e.g., reset written by, copyright and license information inside " -"shell script's top-comments; transform probably malformed HTML " -"documents into valid documents, and remove unused tags inside SVG " -"documents.)." +"Standardize maintenance tasks frequently run inside the repository (e.g., " +"reset written by, copyright and license information inside shell script's " +"top-comments; transform probably malformed HTML documents into valid " +"documents, and remove unused tags inside SVG documents.)." msgstr "" -"Standardize maintenance tasks frequently run inside the repository " -"(e.g., reset written by, copyright and license information inside " -"shell script's top-comments; transform probably malformed HTML " -"documents into valid documents, and remove unused tags inside SVG " -"documents.)." +"Standardize maintenance tasks frequently run inside the repository (e.g., " +"reset written by, copyright and license information inside shell script's " +"top-comments; transform probably malformed HTML documents into valid " +"documents, and remove unused tags inside SVG documents.)." msgid "Options" msgstr "Options" msgid "" -"The centos-art.sh script " -"supports the following options:" +"The centos-art.sh script supports the " +"following options:" msgstr "" -"The centos-art.sh script " -"supports the following options:" +"The centos-art.sh script supports the " +"following options:" msgid "--help" msgstr "--help" @@ -200,39 +188,39 @@ msgid "--debug" msgstr "--debug" msgid "" -"Run the script in debugging mode. This option is very useful if you " -"want to get a closer look to the way modules are opened and closed " -"inside centos-art.sh script." +"Run the script in debugging mode. This option is very useful if you want to " +"get a closer look to the way modules are opened and closed inside centos-art.sh script." msgstr "" -"Run the script in debugging mode. This option is very useful if you " -"want to get a closer look to the way modules are opened and closed " -"inside centos-art.sh script." +"Run the script in debugging mode. This option is very useful if you want to " +"get a closer look to the way modules are opened and closed inside centos-art.sh script." msgid "--quiet" msgstr "--quiet" msgid "" -"Run the script quietly. This option reduces the amount of " -"information the centos-art.sh " -"script prints out when processing source files." +"Run the script quietly. This option reduces the amount of information the " +"centos-art.sh script prints out when " +"processing source files." msgstr "" -"Run the script quietly. This option reduces the amount of " -"information the centos-art.sh " -"script prints out when processing source files." +"Run the script quietly. This option reduces the amount of information the " +"centos-art.sh script prints out when " +"processing source files." msgid "--yes" msgstr "--yes" msgid "" -"Run the script in affirmative mode. This is answering “yes” to all " -"“yes or no” questions. This option is useful when you run centos-art.sh with the --quiet option." +"Run the script in affirmative mode. This is answering “yes” to all “yes or " +"no” questions. This option is useful when you run centos-art.sh with the --quiet option." msgstr "" -"Run the script in affirmative mode. This is answering “yes” to all " -"“yes or no” questions. This option is useful when you run centos-art.sh with the --quiet option." +"Run the script in affirmative mode. This is answering “yes” to all “yes or " +"no” questions. This option is useful when you run centos-art.sh with the --quiet option." msgid "Exit Status" msgstr "Exit Status" @@ -253,18 +241,18 @@ msgid "Author" msgstr "Author" msgid "" -"The centos-art.sh script has " -"received contribution from the following people:" +"The centos-art.sh script has received " +"contribution from the following people:" msgstr "" -"The centos-art.sh script has " -"received contribution from the following people:" +"The centos-art.sh script has received " +"contribution from the following people:" msgid "" -"Alain Reguera Delgado <al@centos.org.cu>, 2009-2013" +"Alain Reguera Delgado <al@centos." +"org.cu>, 2009-2013" msgstr "" -"Alain Reguera Delgado <al@centos.org.cu>, 2009-2013" +"Alain Reguera Delgado <al@centos." +"org.cu>, 2009-2013" msgid "Copyright" msgstr "Copyright" @@ -273,35 +261,35 @@ msgid "Copyright © 2009-2013 The CentOS Artwork SIG" msgstr "Copyright © 2009-2013 The CentOS Artwork SIG" msgid "" -"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 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." msgstr "" -"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 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." msgid "" -"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." +"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." msgstr "" -"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." +"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." msgid "" -"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." +"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." msgstr "" -"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." +"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." #. Put one translator per line, in the form of NAME , YEAR1, YEAR2. msgid "translator-credits" diff --git a/Automation/Manuals/Locales/en_US/tcar_checkFiles.sh.po b/Automation/Manuals/Locales/en_US/tcar_checkFiles.sh.po new file mode 100644 index 0000000..585629d --- /dev/null +++ b/Automation/Manuals/Locales/en_US/tcar_checkFiles.sh.po @@ -0,0 +1,296 @@ +msgid "" +msgstr "" +"Project-Id-Version: tcar_checkFiles.sh.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-26 10:20-0500\n" +"PO-Revision-Date: 2013-11-26 10:20-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 "tcar_checkfiles" +msgstr "tcar_checkfiles" + +msgid "1" +msgstr "1" + +msgid "tcar_checkFiles" +msgstr "tcar_checkFiles" + +msgid "Standardize constructions for file verifications." +msgstr "Standardize constructions for file verifications." + +msgid "cli_checkFiles [-d|-e|-f|-h|-x] LOCATION" +msgstr "cli_checkFiles [-d|-e|-f|-h|-x] LOCATION" + +msgid "Description" +msgstr "Description" + +msgid "" +"The cli_checkFiles exists to answer " +"basic questions like “Is LOCATION is a regular file?” and " +"“Is LOCATION a directory?”. The answer to such questions " +"affects the script execution flow in the following way: when the answer " +"positive (e.g., LOCATION is a regular file), the script " +"passes the test silently and continues its execution. When the answer is " +"negative(e.g., LOCATION is not a regular file), the " +"script finishes its execution immediately with an error message." +msgstr "" +"The cli_checkFiles exists to answer " +"basic questions like “Is LOCATION is a regular file?” and " +"“Is LOCATION a directory?”. The answer to such questions " +"affects the script execution flow in the following way: when the answer " +"positive (e.g., LOCATION is a regular file), the script " +"passes the test silently and continues its execution. When the answer is " +"negative(e.g., LOCATION is not a regular file), the " +"script finishes its execution immediately with an error message." + +msgid "" +"The cli_checkFiles function is exported " +"to centos-art.sh script environment in " +"the very beginning of its execution and will be available all along its " +"execution lifetime. You can use this function inside common and specific " +"functions whenever you need to verify files inside the The CentOS Artwork " +"Repository." +msgstr "" +"The cli_checkFiles function is exported " +"to centos-art.sh script environment in " +"the very beginning of its execution and will be available all along its " +"execution lifetime. You can use this function inside common and specific " +"functions whenever you need to verify files inside the The CentOS Artwork " +"Repository." + +msgid "" +"The cli_checkFiles function is " +"available inside the centos-art.sh " +"script only as part of its execution environment. This function is exported " +"to centos-art.sh script just after " +"executing the script from the command-line and will be available all along " +"the script lifetime. So, you can use this function both in common and " +"specific functionalities of centos-art.sh script." +msgstr "" +"The cli_checkFiles function is " +"available inside the centos-art.sh " +"script only as part of its execution environment. This function is exported " +"to centos-art.sh script just after " +"executing the script from the command-line and will be available all along " +"the script lifetime. So, you can use this function both in common and " +"specific functionalities of centos-art.sh script." + +msgid "" +"The cli_checkFiles function doesn't " +"create subsequent execution environments." +msgstr "" +"The cli_checkFiles function doesn't " +"create subsequent execution environments." + +msgid "Usage" +msgstr "Usage" + +msgid "" +"Use the cli_checkFiles function inside " +"centos-art.sh script whenever you need " +"to control the script execution flow based on file type (e.g., regular " +"files, directories, links, etc.) verifications." +msgstr "" +"Use the cli_checkFiles function inside " +"centos-art.sh script whenever you need " +"to control the script execution flow based on file type (e.g., regular " +"files, directories, links, etc.) verifications." + +msgid "Options" +msgstr "Options" + +msgid "" +"The cli_checkFiles function accepts the " +"following options:" +msgstr "" +"The cli_checkFiles function accepts the " +"following options:" + +msgid "-d" +msgstr "-d" + +msgid "" +"Verifies whether LOCATION exists and is a directory. If " +"it doesn't exists or isn't a directory, an error message is printed and the " +"script finishes its execution. Otherwise, if it exists and is a directory, " +"the script continues its execution normally." +msgstr "" +"Verifies whether LOCATION exists and is a directory. If " +"it doesn't exists or isn't a directory, an error message is printed and the " +"script finishes its execution. Otherwise, if it exists and is a directory, " +"the script continues its execution normally." + +msgid "-e" +msgstr "-e" + +msgid "" +"Verifies whether LOCATION exists or not. If it doesn't " +"exist, an error message is printed and the script finishes its execution. " +"Otherwise, if it does exists, the script continues its execution normally." +msgstr "" +"Verifies whether LOCATION exists or not. If it doesn't " +"exist, an error message is printed and the script finishes its execution. " +"Otherwise, if it does exists, the script continues its execution normally." + +msgid "-f" +msgstr "-f" + +msgid "" +"Verifies whether LOCATION exists and is a regular file. " +"If it doesn't exists or isn't a regular file, an error message is printed " +"and the script finishes its execution. Otherwise, if it exists and is a " +"regular file, the script continues its execution normally." +msgstr "" +"Verifies whether LOCATION exists and is a regular file. " +"If it doesn't exists or isn't a regular file, an error message is printed " +"and the script finishes its execution. Otherwise, if it exists and is a " +"regular file, the script continues its execution normally." + +msgid "-h" +msgstr "-h" + +msgid "" +"Verifies whether LOCATION exists and is a symbolic link. " +"If it doesn't exists or isn't a symbolic link, an error message is printed " +"and the script finishes its execution immediately. Otherwise, if it does " +"exist and is a symbolic link, the script continue its execution normally." +msgstr "" +"Verifies whether LOCATION exists and is a symbolic link. " +"If it doesn't exists or isn't a symbolic link, an error message is printed " +"and the script finishes its execution immediately. Otherwise, if it does " +"exist and is a symbolic link, the script continue its execution normally." + +msgid "-x" +msgstr "-x" + +msgid "" +"Verifies whether LOCATION exists and execution permission " +"is granted. If it doesn't exist or hasn't execution permission, the script " +"finishes its execution immediately. Otherwise, if it exists and has " +"execution permissions, the script continues its execution normally." +msgstr "" +"Verifies whether LOCATION exists and execution permission " +"is granted. If it doesn't exist or hasn't execution permission, the script " +"finishes its execution immediately. Otherwise, if it exists and has " +"execution permissions, the script continues its execution normally." + +msgid "" +"The value of the LOCATION argument must be an absolute " +"path to the file you want to verify. If such file doesn't exists in any " +"supported form, the script finishes its execution with an error message." +msgstr "" +"The value of the LOCATION argument must be an absolute " +"path to the file you want to verify. If such file doesn't exists in any " +"supported form, the script finishes its execution with an error message." + +msgid "Examples" +msgstr "Examples" + +msgid "" +"The following example was taken from centos-art." +"sh script initialization phase. Notice the position of cli_checkFiles function inside the loop. If some " +"of the function files we need to export doesn't have execution rights, " +"cli_checkFiles will finish the script " +"execution immediately with an error message." +msgstr "" +"The following example was taken from centos-art." +"sh script initialization phase. Notice the position of cli_checkFiles function inside the loop. If some " +"of the function files we need to export doesn't have execution rights, " +"cli_checkFiles will finish the script " +"execution immediately with an error message." + +#, no-wrap +msgid "" +"for FUNCFILE in ${FUNCFILES};do\n" +"\n" +" # Verify the execution rights for function file.\n" +" cli_checkFiles -x ${FUNCFILE}\n" +"\n" +" # Initialize the function file.\n" +" . ${FUNCFILE}\n" +"\n" +" # Export the function names inside the file to current shell\n" +" # script environment.\n" +" export -f $(egrep \"${PATTERN}\" ${FUNCFILE} | gawk '{ print $2 }')\n" +"\n" +"done" +msgstr "" +"for FUNCFILE in ${FUNCFILES};do\n" +"\n" +" # Verify the execution rights for function file.\n" +" cli_checkFiles -x ${FUNCFILE}\n" +"\n" +" # Initialize the function file.\n" +" . ${FUNCFILE}\n" +"\n" +" # Export the function names inside the file to current shell\n" +" # script environment.\n" +" export -f $(egrep \"${PATTERN}\" ${FUNCFILE} | gawk '{ print $2 }')\n" +"\n" +"done" + +msgid "Bugs" +msgstr "Bugs" + +msgid "See https://centos.org.cu/bugs/" +msgstr "See https://centos.org.cu/bugs/" + +msgid "Authors" +msgstr "Authors" + +msgid "" +"The tcar_checkFiles function has " +"received contributions from the following people:" +msgstr "" +"The tcar_checkFiles function has " +"received contributions from the following people:" + +msgid "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" +msgstr "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" + +msgid "License" +msgstr "License" + +msgid "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" +msgstr "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Manuals/Locales/en_US/tcar_checkRepoDirSource.sh.po b/Automation/Manuals/Locales/en_US/tcar_checkRepoDirSource.sh.po new file mode 100644 index 0000000..3e3f609 --- /dev/null +++ b/Automation/Manuals/Locales/en_US/tcar_checkRepoDirSource.sh.po @@ -0,0 +1,125 @@ +msgid "" +msgstr "" +"Project-Id-Version: tcar_checkRepoDirSource.sh.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-26 10:20-0500\n" +"PO-Revision-Date: 2013-11-26 10:20-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 "tcar_checkrepodirsource.sh" +msgstr "tcar_checkrepodirsource.sh" + +msgid "1" +msgstr "1" + +msgid "tcar_checkRepoDirSource" +msgstr "tcar_checkRepoDirSource" + +msgid "Standardize the working copy's absolute path construction." +msgstr "Standardize the working copy's absolute path construction." + +msgid "tcar_checkRepoDirSource \"LOCATION\"" +msgstr "tcar_checkRepoDirSource \"LOCATION\"" + +msgid "Description" +msgstr "Description" + +msgid "" +"The tcar_checkRepoDirSource function " +"standardizes the path construction to directories inside it the working " +"copy, using absolute paths. This function transforms relative paths passed " +"as non-option arguments to centos-art.sh script command-line into absolute paths inside the working copy " +"and verifies whether they really exist as directories inside the working " +"copy or not. If the path provided doesn't exist as directory inside the " +"working copy, the script will finish its execution immediately with an error " +"message. Otherwise, if the directory exists, the variable " +"TCAR_ARGUMENTS is redefined with the related absolute " +"path for further use." +msgstr "" +"The tcar_checkRepoDirSource function " +"standardizes the path construction to directories inside it the working " +"copy, using absolute paths. This function transforms relative paths passed " +"as non-option arguments to centos-art.sh script command-line into absolute paths inside the working copy " +"and verifies whether they really exist as directories inside the working " +"copy or not. If the path provided doesn't exist as directory inside the " +"working copy, the script will finish its execution immediately with an error " +"message. Otherwise, if the directory exists, the variable " +"TCAR_ARGUMENTS is redefined with the related absolute " +"path for further use." + +msgid "" +"Use the tcar_checkRepoDirSource " +"function whenever you need to be sure that non-option arguments passed to " +"centos-art.sh script command-line will " +"always point to directories inside the working copy." +msgstr "" +"Use the tcar_checkRepoDirSource " +"function whenever you need to be sure that non-option arguments passed to " +"centos-art.sh script command-line will " +"always point to directories inside the working copy." + +msgid "Bugs" +msgstr "Bugs" + +msgid "See https://centos.org.cu/bugs/" +msgstr "See https://centos.org.cu/bugs/" + +msgid "Authors" +msgstr "Authors" + +msgid "" +"The tcar_checkRepoDirSource function " +"has received contributions from the following people:" +msgstr "" +"The tcar_checkRepoDirSource function " +"has received contributions from the following people:" + +msgid "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" +msgstr "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" + +msgid "License" +msgstr "License" + +msgid "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" +msgstr "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Manuals/Locales/en_US/tcar_getConfigValue.sh.po b/Automation/Manuals/Locales/en_US/tcar_getConfigValue.sh.po new file mode 100644 index 0000000..442eca5 --- /dev/null +++ b/Automation/Manuals/Locales/en_US/tcar_getConfigValue.sh.po @@ -0,0 +1,156 @@ +msgid "" +msgstr "" +"Project-Id-Version: tcar_getConfigValue.sh.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-26 10:20-0500\n" +"PO-Revision-Date: 2013-11-26 10:20-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 "tcar_getconfigvalue.sh" +msgstr "tcar_getconfigvalue.sh" + +msgid "1" +msgstr "1" + +msgid "tcar_getConfigValue" +msgstr "tcar_getConfigValue" + +msgid "Standardize options retrieval from configuration files." +msgstr "Standardize options retrieval from configuration files." + +msgid "tcar_getConfigValue FILE SECTION OPTION" +msgstr "tcar_getConfigValue FILE SECTION OPTION" + +msgid "Description" +msgstr "Description" + +msgid "" +"The tcar_getConfigValue function " +"standardizes the way option values are retrieved from configuration files. " +"As convention, tcar_getConfigValue uses " +"the output produced by tcar_getConfigLines as input to retrieve the option values. As convention, in " +"option = \"value\" lines, the values retrieved are always " +"on the right side. The values retrieved are also output without quotation " +"and translation markers already expanded." +msgstr "" +"The tcar_getConfigValue function " +"standardizes the way option values are retrieved from configuration files. " +"As convention, tcar_getConfigValue uses " +"the output produced by tcar_getConfigLines as input to retrieve the option values. As convention, in " +"option = \"value\" lines, the values retrieved are always " +"on the right side. The values retrieved are also output without quotation " +"and translation markers already expanded." + +msgid "" +"The tcar_getConfigValue function " +"accepts the following arguments:" +msgstr "" +"The tcar_getConfigValue function " +"accepts the following arguments:" + +msgid "FILE" +msgstr "FILE" + +msgid "" +"This argument specifies the absolute path to the configuration file you want " +"to retrieve the value from. For example," +msgstr "" +"This argument specifies the absolute path to the configuration file you want " +"to retrieve the value from. For example," + +msgid "SECTION" +msgstr "SECTION" + +msgid "" +"This argument specifies the name of the section related to the configuration " +"line you want to retrieve the value from. For example, “symbols” without " +"brackets." +msgstr "" +"This argument specifies the name of the section related to the configuration " +"line you want to retrieve the value from. For example, “symbols” without " +"brackets." + +msgid "OPTION" +msgstr "OPTION" + +msgid "" +"This argument specifies the name of the option you want to retrieve the " +"value from." +msgstr "" +"This argument specifies the name of the option you want to retrieve the " +"value from." + +msgid "" +"Use the tcar_getConfigValue function " +"whenever you want to retrieve values from configuration files in a " +"controlled way." +msgstr "" +"Use the tcar_getConfigValue function " +"whenever you want to retrieve values from configuration files in a " +"controlled way." + +msgid "Bugs" +msgstr "Bugs" + +msgid "See https://centos.org.cu/bugs/" +msgstr "See https://centos.org.cu/bugs/" + +msgid "Authors" +msgstr "Authors" + +msgid "" +"The tcar_checkFiles function has " +"received contributions from the following people:" +msgstr "" +"The tcar_checkFiles function has " +"received contributions from the following people:" + +msgid "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" +msgstr "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" + +msgid "License" +msgstr "License" + +msgid "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" +msgstr "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Manuals/Locales/en_US/tcar_getFilesList.sh.po b/Automation/Manuals/Locales/en_US/tcar_getFilesList.sh.po new file mode 100644 index 0000000..ba5bdfc --- /dev/null +++ b/Automation/Manuals/Locales/en_US/tcar_getFilesList.sh.po @@ -0,0 +1,236 @@ +msgid "" +msgstr "" +"Project-Id-Version: tcar_getFilesList.sh.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-26 10:20-0500\n" +"PO-Revision-Date: 2013-11-26 10:20-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 "tcar_getfileslist.sh" +msgstr "tcar_getfileslist.sh" + +msgid "1" +msgstr "1" + +msgid "tcar_getFilesList" +msgstr "tcar_getFilesList" + +msgid "Create customized list of files for further processing." +msgstr "Create customized list of files for further processing." + +msgid "" +"tcar_getFilesList [--pattern|--mindepth|--maxdepth|--type|--uid] LOCATION" +msgstr "" +"tcar_getFilesList [--pattern|--mindepth|--maxdepth|--type|--uid] LOCATION" + +msgid "Description" +msgstr "Description" + +msgid "" +"The tcar_getFilesList standardizes the " +"way list of files are built inside the centos-art." +"sh script. This function outputs a sorted and unique list of " +"files based on the options and location provided as argument. This function " +"is an interface to the find command. " +"Don't use find command directly inside " +"the centos-art.sh script. Instead, use the tcar_getFilesList function." +msgstr "" +"The tcar_getFilesList standardizes the " +"way list of files are built inside the centos-art." +"sh script. This function outputs a sorted and unique list of " +"files based on the options and location provided as argument. This function " +"is an interface to the find command. " +"Don't use find command directly inside " +"the centos-art.sh script. Instead, use the tcar_getFilesList function." + +msgid "" +"The LOCATION arguments must be the absolute path to a " +"directory and specifies where the search of files in any form (e.g., " +"directories, links, etc.) will take place in. If LOCATION " +"isn't a directory, the script finishes its execution with an error message." +msgstr "" +"The LOCATION arguments must be the absolute path to a " +"directory and specifies where the search of files in any form (e.g., " +"directories, links, etc.) will take place in. If LOCATION " +"isn't a directory, the script finishes its execution with an error message." + +msgid "" +"The tcar_getFilesList accepts the " +"following options:" +msgstr "" +"The tcar_getFilesList accepts the " +"following options:" + +msgid "--pattern=\"REGEX\"" +msgstr "--pattern=\"REGEX\"" + +msgid "" +"This option specifies a posix-egrep type regular expression as value. This " +"regular expression is applied to path specified in LOCATION argument. Only file paths that match this regular expression inside " +"LOCATION directory will be included in the final list of " +"files. By default, if this option is not provided, the “^/.*[[:" +"alnum:]_/-]$+” regular expression is used." +msgstr "" +"This option specifies a posix-egrep type regular expression as value. This " +"regular expression is applied to path specified in LOCATION argument. Only file paths that match this regular expression inside " +"LOCATION directory will be included in the final list of " +"files. By default, if this option is not provided, the “^/.*[[:" +"alnum:]_/-]$+” regular expression is used." + +msgid "" +"When you use the tcar_getFilesList you " +"don't need to specified the absolute path of files you want to look for. " +"This is something tcar_getFilesList " +"already does for you. When you use this function, the value you pass as " +"regular expression isn't the final regular expression used. Instead, the " +"regular expression you pass is used to build the final regular expression " +"passed to find command. The REGEX." +msgstr "" +"When you use the tcar_getFilesList you " +"don't need to specified the absolute path of files you want to look for. " +"This is something tcar_getFilesList " +"already does for you. When you use this function, the value you pass as " +"regular expression isn't the final regular expression used. Instead, the " +"regular expression you pass is used to build the final regular expression " +"passed to find command. The REGEX." + +msgid "--mindepth=\"NUMBER\"" +msgstr "--mindepth=\"NUMBER\"" + +msgid "" +"This option specifies the minimal NUMBER of levels deep " +"the search should go under the directory LOCATION " +"specified. For example, if you specify --mindepth=" +"\"2\" the search will start two levels deep considering the path " +"provided as section." +msgstr "" +"This option specifies the minimal NUMBER of levels deep " +"the search should go under the directory LOCATION " +"specified. For example, if you specify --mindepth=" +"\"2\" the search will start two levels deep considering the path " +"provided as section." + +msgid "--maxdepth=\"NUMBER\"" +msgstr "--maxdepth=\"NUMBER\"" + +msgid "" +"This option specifies the maximum NUMBER of levels deep " +"the search should go under the directory LOCATION " +"specified. For example, if you specify --maxdepth=" +"\"2\" the search will begin in the very same directory path you " +"provided as LOCATION and stop two levels deep using it as " +"section." +msgstr "" +"This option specifies the maximum NUMBER of levels deep " +"the search should go under the directory LOCATION " +"specified. For example, if you specify --maxdepth=" +"\"2\" the search will begin in the very same directory path you " +"provided as LOCATION and stop two levels deep using it as " +"section." + +msgid "--type=\"STRING\"" +msgstr "--type=\"STRING\"" + +msgid "" +"This option specifies the type of files being searched. This option accepts " +"the same values the find-type option does. However, the following " +"STRING values are the most used inside the script so far:" +msgstr "" +"This option specifies the type of files being searched. This option accepts " +"the same values the find-type option does. However, the following " +"STRING values are the most used inside the script so far:" + +msgid "d &mdash; directory." +msgstr "d &mdash; directory." + +msgid "f &mdash; regular file." +msgstr "f &mdash; regular file." + +msgid "--uid=\"NUMBER\"" +msgstr "--uid=\"NUMBER\"" + +msgid "" +"This option specifies the numeric user id of the files you want to search. " +"Only files that match this numeric user id will be added to the final list " +"of files." +msgstr "" +"This option specifies the numeric user id of the files you want to search. " +"Only files that match this numeric user id will be added to the final list " +"of files." + +msgid "" +"Use the tcar_getFilesList whenever you " +"need to build list of files for further processing." +msgstr "" +"Use the tcar_getFilesList whenever you " +"need to build list of files for further processing." + +msgid "Bugs" +msgstr "Bugs" + +msgid "See https://centos.org.cu/bugs/" +msgstr "See https://centos.org.cu/bugs/" + +msgid "Authors" +msgstr "Authors" + +msgid "" +"The tcar_checkFiles function has " +"received contributions from the following people:" +msgstr "" +"The tcar_checkFiles function has " +"received contributions from the following people:" + +msgid "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" +msgstr "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" + +msgid "License" +msgstr "License" + +msgid "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" +msgstr "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Manuals/Locales/en_US/tcar_printMessage.sh.po b/Automation/Manuals/Locales/en_US/tcar_printMessage.sh.po new file mode 100644 index 0000000..4ee9f19 --- /dev/null +++ b/Automation/Manuals/Locales/en_US/tcar_printMessage.sh.po @@ -0,0 +1,437 @@ +msgid "" +msgstr "" +"Project-Id-Version: tcar_printMessage.sh.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-26 10:20-0500\n" +"PO-Revision-Date: 2013-11-26 10:20-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 "tcar_printmessage.sh" +msgstr "tcar_printmessage.sh" + +msgid "1" +msgstr "1" + +msgid "tcar_printMessage.sh" +msgstr "tcar_printMessage.sh" + +msgid "Print customized messages in standard ways." +msgstr "Print customized messages in standard ways." + +msgid "" +"tcar_printMessage \"MESSAGE\" [--as-separator-line|--as-banner-line|--as-" +"cropping-line|--as-tuningup-line|--as-checking-line|--as-combining-line|--as-" +"creating-line|--as-reading-line|--as-savedas-line|--as-linkto-line|--as-" +"movedto-line|--as-validating-line|--as-template-line|--as-configuration-" +"line|--as-palette-line|--as-reponse-line|--as-request-line|--as-selection-" +"line|--as-error-line|--as-toknowmore-line|--as-yesornorequest-line|--as-" +"notrailingnew-line|--as-stdout-line|--as-stderr-line]" +msgstr "" +"tcar_printMessage \"MESSAGE\" [--as-separator-line|--as-banner-line|--as-" +"cropping-line|--as-tuningup-line|--as-checking-line|--as-combining-line|--as-" +"creating-line|--as-reading-line|--as-savedas-line|--as-linkto-line|--as-" +"movedto-line|--as-validating-line|--as-template-line|--as-configuration-" +"line|--as-palette-line|--as-reponse-line|--as-request-line|--as-selection-" +"line|--as-error-line|--as-toknowmore-line|--as-yesornorequest-line|--as-" +"notrailingnew-line|--as-stdout-line|--as-stderr-line]" + +msgid "Description" +msgstr "Description" + +msgid "" +"The tcar_printMessage function " +"standardizes the way centos-art.sh scirpt prints messages. By default, " +"centos-art.sh script prints all messages to the standard output with the " +"exception of those messages printed with the --as-" +"stderr-line option, which are printed to standard error output " +"instead." +msgstr "" +"The tcar_printMessage function " +"standardizes the way centos-art.sh scirpt prints messages. By default, " +"centos-art.sh script prints all messages to the standard output with the " +"exception of those messages printed with the --as-" +"stderr-line option, which are printed to standard error output " +"instead." + +msgid "" +"The tcar_printMessage function requires " +"two arguments. The first argument specifies the message you want to print " +"and the second argument specifies the format you'll use to print that " +"message. Because this function is so used inside the centos-art.sh script, " +"it is convenient to provide localization to strings passed as " +"MESSAGE using gettext constructions when they aren't paths." +msgstr "" +"The tcar_printMessage function requires " +"two arguments. The first argument specifies the message you want to print " +"and the second argument specifies the format you'll use to print that " +"message. Because this function is so used inside the centos-art.sh script, " +"it is convenient to provide localization to strings passed as " +"MESSAGE using gettext constructions when they aren't paths." + +msgid "Options" +msgstr "Options" + +msgid "" +"The tcar_printMessage function accepts " +"the following format options as second argument:" +msgstr "" +"The tcar_printMessage function accepts " +"the following format options as second argument:" + +msgid "--as-separator-line" +msgstr "--as-separator-line" + +msgid "" +"This format takes the first character passed as MESSAGE " +"and repeats it horizontally to build a separator line. Use this format " +"whenever you need to create a logical separation between different actions." +msgstr "" +"This format takes the first character passed as MESSAGE " +"and repeats it horizontally to build a separator line. Use this format " +"whenever you need to create a logical separation between different actions." + +msgid "--as-banner-line" +msgstr "--as-banner-line" + +msgid "" +"This format takes the string passed as MESSAGE and puts " +"it inside two horizontal separator lines. Use this format whenever you need " +"to print header information for following lines." +msgstr "" +"This format takes the string passed as MESSAGE and puts " +"it inside two horizontal separator lines. Use this format whenever you need " +"to print header information for following lines." + +msgid "--as-cropping-line" +msgstr "--as-cropping-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been cropped." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been cropped." + +msgid "--as-tuningup-line" +msgstr "--as-tuningup-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been tuned-up." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been tuned-up." + +msgid "--as-checking-line" +msgstr "--as-checking-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been checked or verified (e." +"g., through tcar_checkFiles " +"functionality)." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been checked or verified (e." +"g., through tcar_checkFiles " +"functionality)." + +msgid "--as-combining-line" +msgstr "--as-combining-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been combined." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been combined." + +msgid "--as-creating-line" +msgstr "--as-creating-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been created." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been created." + +msgid "--as-reading-line" +msgstr "--as-reading-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been read." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been read." + +msgid "--as-savedas-line" +msgstr "--as-savedas-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been saved." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been saved." + +msgid "--as-linkto-line" +msgstr "--as-linkto-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been linked." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been linked." + +msgid "--as-movedto-line" +msgstr "--as-movedto-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been moved." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been moved." + +msgid "--as-validating-line" +msgstr "--as-validating-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been validated." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file has been validated." + +msgid "--as-template-line" +msgstr "--as-template-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file is a template or design model." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file is a template or design model." + +msgid "--as-configuration-line" +msgstr "--as-configuration-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file is a configuration file." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file is a configuration file." + +msgid "--as-palette-line" +msgstr "--as-palette-line" + +msgid "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file is a palette of colors." +msgstr "" +"This format is for two columns messages where MESSAGE " +"generally refers to a file inside the repository. Use this format whenever " +"you need to imply the fact that certain file is a palette of colors." + +msgid "--as-response-line" +msgstr "--as-response-line" + +msgid "" +"This format adds --> at the beginning of the string " +"passed as MESSAGE. Use this format whenever you need to " +"imply the fact that certain file is considered part of a response. For " +"example, when you need to express that a group of files will take certain " +"action, you can use this option to doing so." +msgstr "" +"This format adds --> at the beginning of the string " +"passed as MESSAGE. Use this format whenever you need to " +"imply the fact that certain file is considered part of a response. For " +"example, when you need to express that a group of files will take certain " +"action, you can use this option to doing so." + +msgid "--as-request-line" +msgstr "--as-request-line" + +msgid "" +"This format prints MESSAGE without trailing new line. Use " +"this format whenever you need to imply a question or yes or no request." +msgstr "" +"This format prints MESSAGE without trailing new line. Use " +"this format whenever you need to imply a question or yes or no request." + +msgid "--as-selection-line" +msgstr "--as-selection-line" + +msgid "" +"This format uses each word in MESSAGE as item of a " +"selection list. Use this format whenever you need to select one of the items " +"provided as MESSAGE." +msgstr "" +"This format uses each word in MESSAGE as item of a " +"selection list. Use this format whenever you need to select one of the items " +"provided as MESSAGE." + +msgid "--as-error-line" +msgstr "--as-error-line" + +msgid "" +"This format prints error messages produced by centos-art.sh script. It uses " +"the caller built-in command to display " +"the line number and the filename where such error was triggered. Later, it " +"prints where to find more information by using the --as-toknowmore-line option." +msgstr "" +"This format prints error messages produced by centos-art.sh script. It uses " +"the caller built-in command to display " +"the line number and the filename where such error was triggered. Later, it " +"prints where to find more information by using the --as-toknowmore-line option." + +msgid "--as-toknowmore-line" +msgstr "--as-toknowmore-line" + +msgid "" +"This format takes a function name as MESSAGE and prints " +"the command you can use to find more information about it. When this option " +"is passed the script finishes its execution immediately. This option is used " +"in combination with --as-error-line to " +"finish the script execution after an error." +msgstr "" +"This format takes a function name as MESSAGE and prints " +"the command you can use to find more information about it. When this option " +"is passed the script finishes its execution immediately. This option is used " +"in combination with --as-error-line to " +"finish the script execution after an error." + +msgid "--as-yesornorequest-line" +msgstr "--as-yesornorequest-line" + +msgid "" +"This format takes a question as MESSAGE and reads a yes " +"or no answer. When answer is negative, the script finishes its execution " +"immediately. When answer is affirmative, the script continues its execution " +"normally." +msgstr "" +"This format takes a question as MESSAGE and reads a yes " +"or no answer. When answer is negative, the script finishes its execution " +"immediately. When answer is affirmative, the script continues its execution " +"normally." + +msgid "--as-notrailingnew-line" +msgstr "--as-notrailingnew-line" + +msgid "Print MESSAGE without any trailing newline." +msgstr "Print MESSAGE without any trailing newline." + +msgid "--as-stdout-line" +msgstr "--as-stdout-line" + +msgid "Print MESSAGE to standard output." +msgstr "Print MESSAGE to standard output." + +msgid "--as-stderr-line" +msgstr "--as-stderr-line" + +msgid "Print MESSAGE to standard error output." +msgstr "Print MESSAGE to standard error output." + +msgid "Examples" +msgstr "Examples" + +msgid "Bugs" +msgstr "Bugs" + +msgid ".." +msgstr ".." + +msgid "See https://centos.org.cu/bugs/" +msgstr "See https://centos.org.cu/bugs/" + +msgid "Authors" +msgstr "Authors" + +msgid "" +"The tcar_printMessage function has " +"received contributions from the following people:" +msgstr "" +"The tcar_printMessage function has " +"received contributions from the following people:" + +msgid "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" +msgstr "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" + +msgid "License" +msgstr "License" + +msgid "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" +msgstr "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Manuals/Locales/en_US/tcar_setModuleEnvironment.sh.po b/Automation/Manuals/Locales/en_US/tcar_setModuleEnvironment.sh.po index aaa9567..286f0dc 100644 --- a/Automation/Manuals/Locales/en_US/tcar_setModuleEnvironment.sh.po +++ b/Automation/Manuals/Locales/en_US/tcar_setModuleEnvironment.sh.po @@ -1,8 +1,8 @@ msgid "" msgstr "" "Project-Id-Version: tcar_setModuleEnvironment.sh.asciidoc 0.6\n" -"POT-Creation-Date: 2013-11-07 00:08-0500\n" -"PO-Revision-Date: 2013-11-07 00:08-0500\n" +"POT-Creation-Date: 2013-11-26 10:20-0500\n" +"PO-Revision-Date: 2013-11-26 10:20-0500\n" "Last-Translator: Localization SIG \n" "Language-Team: English\n" "MIME-Version: 1.0\n" @@ -23,11 +23,11 @@ msgid "Initiate module environments." msgstr "Initiate module environments." msgid "" -"tcar_setModuleEnvironment [-m \"MODULE_NAME\"] [-t \"MODULE_TYPE\"] " -"[-g MODULE_ARGUMENT] …" +"tcar_setModuleEnvironment [-m \"MODULE_NAME\"] [-t \"MODULE_TYPE\"] [-g " +"MODULE_ARGUMENT] …" msgstr "" -"tcar_setModuleEnvironment [-m \"MODULE_NAME\"] [-t \"MODULE_TYPE\"] " -"[-g MODULE_ARGUMENT] …" +"tcar_setModuleEnvironment [-m \"MODULE_NAME\"] [-t \"MODULE_TYPE\"] [-g " +"MODULE_ARGUMENT] …" msgid "Description" msgstr "Description" @@ -36,150 +36,143 @@ msgid "Options" msgstr "Options" msgid "" -"The tcar_setModuleEnvironment " -"function accepts the following options:" +"The tcar_setModuleEnvironment function " +"accepts the following options:" msgstr "" -"The tcar_setModuleEnvironment " -"function accepts the following options:" +"The tcar_setModuleEnvironment function " +"accepts the following options:" msgid "-m" msgstr "-m" msgid "This option specifies the name of the module you want to load." -msgstr "" -"This option specifies the name of the module you want to load." +msgstr "This option specifies the name of the module you want to load." msgid "-t" msgstr "-t" msgid "" -"This option specifies the type of the module you want to load. " -"Modules can be one of the following types:" +"This option specifies the type of the module you want to load. Modules can " +"be one of the following types:" msgstr "" -"This option specifies the type of the module you want to load. " -"Modules can be one of the following types:" +"This option specifies the type of the module you want to load. Modules can " +"be one of the following types:" msgid "top-module" msgstr "top-module" msgid "" -"This modules are stored in the first level of Modules directory. " -"This type of modules initiate module environments for specific " -"tasks so it can be called from anywhere inside centos-art.sh script." +"This modules are stored in the first level of Modules directory. This type " +"of modules initiate module environments for specific tasks so it can be " +"called from anywhere inside centos-art.sh script." msgstr "" -"This modules are stored in the first level of Modules directory. " -"This type of modules initiate module environments for specific " -"tasks so it can be called from anywhere inside centos-art.sh script." +"This modules are stored in the first level of Modules directory. This type " +"of modules initiate module environments for specific tasks so it can be " +"called from anywhere inside centos-art.sh script." msgid "sub-module" msgstr "sub-module" msgid "" -"This modules are stored from the second-level of Modules directory " -"on. This type of modules can be executed from top-modules, sub-" -"modules, or sib-modules but never the centos-art.sh file itself." +"This modules are stored from the second-level of Modules directory on. This " +"type of modules can be executed from top-modules, sub-modules, or sib-" +"modules but never the centos-art.sh " +"file itself." msgstr "" -"This modules are stored from the second-level of Modules directory " -"on. This type of modules can be executed from top-modules, sub-" -"modules, or sib-modules but never the centos-art.sh file itself." +"This modules are stored from the second-level of Modules directory on. This " +"type of modules can be executed from top-modules, sub-modules, or sib-" +"modules but never the centos-art.sh " +"file itself." msgid "sib-module" msgstr "sib-module" msgid "" -"This modules are stored from the second-level of Modules directory " -"on. This type of modules can be executed from sub-modules or sib-" -"modules, but never top-modules or the centos-art.sh file itself." +"This modules are stored from the second-level of Modules directory on. This " +"type of modules can be executed from sub-modules or sib-modules, but never " +"top-modules or the centos-art.sh file " +"itself." msgstr "" -"This modules are stored from the second-level of Modules directory " -"on. This type of modules can be executed from sub-modules or sib-" -"modules, but never top-modules or the centos-art.sh file itself." +"This modules are stored from the second-level of Modules directory on. This " +"type of modules can be executed from sub-modules or sib-modules, but never " +"top-modules or the centos-art.sh file " +"itself." msgid "-g" msgstr "-g" msgid "" -"This option specifies the module-specific option you want to pass " -"for processing in the module environment you are about to execute. " -"Generally, module-specific options are passed through centos-art.sh command-line but you may " -"need to pass them internally in some cases (e.g., you are executing " -"a top-module from a sub-module). If you need to pass more than one " -"option, then you need to put the -g option before each option you " -"want to pass." -msgstr "" -"This option specifies the module-specific option you want to pass " -"for processing in the module environment you are about to execute. " -"Generally, module-specific options are passed through centos-art.sh command-line but you may " -"need to pass them internally in some cases (e.g., you are executing " -"a top-module from a sub-module). If you need to pass more than one " -"option, then you need to put the -g option before each option you " -"want to pass." +"This option specifies the module-specific option you want to pass for " +"processing in the module environment you are about to execute. Generally, " +"module-specific options are passed through centos-" +"art.sh command-line but you may need to pass them internally in " +"some cases (e.g., you are executing a top-module from a sub-module). If you " +"need to pass more than one option, then you need to put the -g option before " +"each option you want to pass." +msgstr "" +"This option specifies the module-specific option you want to pass for " +"processing in the module environment you are about to execute. Generally, " +"module-specific options are passed through centos-" +"art.sh command-line but you may need to pass them internally in " +"some cases (e.g., you are executing a top-module from a sub-module). If you " +"need to pass more than one option, then you need to put the -g option before " +"each option you want to pass." msgid "Bugs" msgstr "Bugs" msgid "" "In the very beginning of tcar_setModuleEnvironment function, it used just non-" -"array variables and it worked fine for top-module and sub-module " -"processing, however when it was needed to do sibling processing, it " -"didn't work as expected. The failure was produced because a wrong " -"variable assignment when tried to set the path of the next module " -"to load. There was not a clean way to “remember” what was the base " -"directory of the parent directory, so it ended up using the last " -"loaded module base directory which made impossible to load a " -"sibling module. The tcar_setModuleEnvironment function as implemented in " -"version 0.5 of The CentOS Artwork Repository, fixes this issue " -"replacing non-array variables by array variables which can remember " -"module information." +"\">tcar_setModuleEnvironment function, it used just non-array " +"variables and it worked fine for top-module and sub-module processing, " +"however when it was needed to do sibling processing, it didn't work as " +"expected. The failure was produced because a wrong variable assignment when " +"tried to set the path of the next module to load. There was not a clean way " +"to “remember” what was the base directory of the parent directory, so it " +"ended up using the last loaded module base directory which made impossible " +"to load a sibling module. The tcar_setModuleEnvironment function as implemented in version " +"0.5 of The CentOS Artwork Repository, fixes this issue replacing non-array " +"variables by array variables which can remember module information." msgstr "" "In the very beginning of tcar_setModuleEnvironment function, it used just non-" -"array variables and it worked fine for top-module and sub-module " -"processing, however when it was needed to do sibling processing, it " -"didn't work as expected. The failure was produced because a wrong " -"variable assignment when tried to set the path of the next module " -"to load. There was not a clean way to “remember” what was the base " -"directory of the parent directory, so it ended up using the last " -"loaded module base directory which made impossible to load a " -"sibling module. The tcar_setModuleEnvironment function as implemented in " -"version 0.5 of The CentOS Artwork Repository, fixes this issue " -"replacing non-array variables by array variables which can remember " -"module information." +"\">tcar_setModuleEnvironment function, it used just non-array " +"variables and it worked fine for top-module and sub-module processing, " +"however when it was needed to do sibling processing, it didn't work as " +"expected. The failure was produced because a wrong variable assignment when " +"tried to set the path of the next module to load. There was not a clean way " +"to “remember” what was the base directory of the parent directory, so it " +"ended up using the last loaded module base directory which made impossible " +"to load a sibling module. The tcar_setModuleEnvironment function as implemented in version " +"0.5 of The CentOS Artwork Repository, fixes this issue replacing non-array " +"variables by array variables which can remember module information." msgid "" -"See also: https://centos." -"org.cu/bugs/" +"See also: https://centos.org.cu/" +"bugs/" msgstr "" -"See also: https://centos." -"org.cu/bugs/" +"See also: https://centos.org.cu/" +"bugs/" msgid "Author" msgstr "Author" msgid "" -"The centos-art.sh script has " -"received contribution from the following people:" +"The centos-art.sh script has received " +"contribution from the following people:" msgstr "" -"The centos-art.sh script has " -"received contribution from the following people:" +"The centos-art.sh script has received " +"contribution from the following people:" msgid "" -"Alain Reguera Delgado <al@centos.org.cu>, 2009-2013" +"Alain Reguera Delgado <al@centos." +"org.cu>, 2009-2013" msgstr "" -"Alain Reguera Delgado <al@centos.org.cu>, 2009-2013" +"Alain Reguera Delgado <al@centos." +"org.cu>, 2009-2013" msgid "Copyright" msgstr "Copyright" @@ -188,35 +181,35 @@ msgid "Copyright © 2009-2013 The CentOS Artwork SIG" msgstr "Copyright © 2009-2013 The CentOS Artwork SIG" msgid "" -"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 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." msgstr "" -"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 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." msgid "" -"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." +"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." msgstr "" -"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." +"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." msgid "" -"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." +"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." msgstr "" -"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." +"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." #. Put one translator per line, in the form of NAME , YEAR1, YEAR2. msgid "translator-credits" diff --git a/Automation/Manuals/Locales/en_US/tcar_setTranslationMarkers.sh.po b/Automation/Manuals/Locales/en_US/tcar_setTranslationMarkers.sh.po new file mode 100644 index 0000000..adddc15 --- /dev/null +++ b/Automation/Manuals/Locales/en_US/tcar_setTranslationMarkers.sh.po @@ -0,0 +1,445 @@ +msgid "" +msgstr "" +"Project-Id-Version: tcar_setTranslationMarkers.sh.asciidoc 0.6\n" +"POT-Creation-Date: 2013-11-26 10:20-0500\n" +"PO-Revision-Date: 2013-11-26 10:20-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 "tcar_settranslationmarkers" +msgstr "tcar_settranslationmarkers" + +msgid "1" +msgstr "1" + +msgid "tcar_setTranslationMarkers" +msgstr "tcar_setTranslationMarkers" + +msgid "Expands translation markers." +msgstr "Expands translation markers." + +msgid "tcar_setTranslationMarkers \"FILE\"" +msgstr "tcar_setTranslationMarkers \"FILE\"" + +msgid "Description" +msgstr "Description" + +msgid "" +"The cli_setTranslationMarkers " +"standardizes construction of translation markers and their related " +"expansion. As convention, translation markers are set inside source files (e." +"g., DocBook, SVG) and expanded inside temporal instances used to produce " +"final contents. The FILE argument should point to the " +"temporal file where translation markers expansion takes place in." +msgstr "" +"The cli_setTranslationMarkers " +"standardizes construction of translation markers and their related " +"expansion. As convention, translation markers are set inside source files (e." +"g., DocBook, SVG) and expanded inside temporal instances used to produce " +"final contents. The FILE argument should point to the " +"temporal file where translation markers expansion takes place in." + +msgid "" +"Translation markers written in source files must comply the " +"== regular expression pattern. For example, =UNKNOWN_MARKER= is a valid translation marker without any " +"replacement. To prevent centos-art.sh " +"script from expanding translation markers, add a backslash (+) " +"between the first equal sign and the following letter. For example, +=...=+ " +"won't be expanded." +msgstr "" +"Translation markers written in source files must comply the " +"== regular expression pattern. For example, =UNKNOWN_MARKER= is a valid translation marker without any " +"replacement. To prevent centos-art.sh " +"script from expanding translation markers, add a backslash (+) " +"between the first equal sign and the following letter. For example, +=...=+ " +"won't be expanded." + +msgid "" +"The cli_setTranslationMarkers supports " +"the following translation markers:" +msgstr "" +"The cli_setTranslationMarkers supports " +"the following translation markers:" + +msgid "" +"=\\COPYRIGHT_YEAR_LAST=, =\\COPYRIGHT_YEAR=" +msgstr "" +"=\\COPYRIGHT_YEAR_LAST=, =\\COPYRIGHT_YEAR=" + +msgid "" +"These translation markers expand to the last year used in copyright notes. " +"For example, =COPYRIGHT_YEAR_LAST=." +msgstr "" +"These translation markers expand to the last year used in copyright notes. " +"For example, =COPYRIGHT_YEAR_LAST=." + +msgid "" +"=\\COPYRIGHT_YEAR_LIST=, =" +"\\COPYRIGHT_YEARS_LIST=" +msgstr "" +"=\\COPYRIGHT_YEAR_LIST=, =" +"\\COPYRIGHT_YEARS_LIST=" + +msgid "" +"This translation markers expand to the list of years used in copyright " +"notes. For example, =COPYRIGHT_YEARS_LIST=. The first " +"year represents the time we began to work on The CentOS Artwork Repository." +msgstr "" +"This translation markers expand to the list of years used in copyright " +"notes. For example, =COPYRIGHT_YEARS_LIST=. The first " +"year represents the time we began to work on The CentOS Artwork Repository." + +msgid "=\\COPYRIGHT_HOLDER=" +msgstr "=\\COPYRIGHT_HOLDER=" + +msgid "" +"This translation marker expands to the holder used in copyright notes. For " +"example, =COPYRIGHT_HOLDER=." +msgstr "" +"This translation marker expands to the holder used in copyright notes. For " +"example, =COPYRIGHT_HOLDER=." + +msgid "=\\COPYRIGHT_HOLDER_PREDICATE=" +msgstr "=\\COPYRIGHT_HOLDER_PREDICATE=" + +msgid "" +"This translation marker expands both the holder and the predicate used in " +"copyright notes. For example, =COPYRIGHT_HOLDER_PREDICATE=." +msgstr "" +"This translation marker expands both the holder and the predicate used in " +"copyright notes. For example, =COPYRIGHT_HOLDER_PREDICATE=." + +msgid "=\\BRAND=" +msgstr "=\\BRAND=" + +msgid "" +"This translation marker expands to the brand name used on files names and " +"URLs inside The CentOS Artwork Repository. For example, =BRAND=." +msgstr "" +"This translation marker expands to the brand name used on files names and " +"URLs inside The CentOS Artwork Repository. For example, =BRAND=." + +msgid "=\\LICENSE=" +msgstr "=\\LICENSE=" + +msgid "" +"This translation marker expands to the license information used in files " +"created by centos-art.sh script. For " +"example, =LICENSE=." +msgstr "" +"This translation marker expands to the license information used in files " +"created by centos-art.sh script. For " +"example, =LICENSE=." + +msgid "=\\LICENSE_URL=" +msgstr "=\\LICENSE_URL=" + +msgid "" +"This translation marker expands to the license URL used in files created by " +"centos-art.sh script. For example, " +"=LICENSE_URL=." +msgstr "" +"This translation marker expands to the license URL used in files created by " +"centos-art.sh script. For example, " +"=LICENSE_URL=." + +msgid "=\\THEME=" +msgstr "=\\THEME=" + +msgid "" +"This translation marker expands to the theme portion of path you are " +"producing through centos-art.sh script. As consequence, this translation " +"marker should be used in situations where you are producing theme components " +"only. This translation marker expands its value by retrieving the theme part " +"of the path you provide as non-option argument to centos-art.sh script. For example, if you provide the path " +"Identity/Images/Themes/Modern/2/Distro/5, this " +"translation will expand to the Modern/2/ value." +msgstr "" +"This translation marker expands to the theme portion of path you are " +"producing through centos-art.sh script. As consequence, this translation " +"marker should be used in situations where you are producing theme components " +"only. This translation marker expands its value by retrieving the theme part " +"of the path you provide as non-option argument to centos-art.sh script. For example, if you provide the path " +"Identity/Images/Themes/Modern/2/Distro/5, this " +"translation will expand to the Modern/2/ value." + +msgid "" +"In case you need to retrieve the theme name or version separately one " +"another, then you can use the =\\THEMENAME= and =" +"\\THEMERELEASE= translation markers, respectively. When you use " +"these translation markers, forward slashes are removed from result. So, if " +"you provide the path Identity/Images/Themes/Modern/2/Distro/5, =\\THEMENAME= will expand to Modern and =THEMERELEASE= will expand to 2." +msgstr "" +"In case you need to retrieve the theme name or version separately one " +"another, then you can use the =\\THEMENAME= and =" +"\\THEMERELEASE= translation markers, respectively. When you use " +"these translation markers, forward slashes are removed from result. So, if " +"you provide the path Identity/Images/Themes/Modern/2/Distro/5, =\\THEMENAME= will expand to Modern and =THEMERELEASE= will expand to 2." + +msgid "=\\RELEASE=" +msgstr "=\\RELEASE=" + +msgid "" +"This translation marker expands to the current release information of your " +"CentOS distribution. By default this information is retrieved from /" +"etc/redhat-release. In case the option --" +"release be passed, the value specified with it will overwrite the " +"default value and will be this the one used as section for this translation " +"marker to retrieve the release information. So, for example, if you are " +"running a CentOS-5.8 distribution and no --" +"release option is passed to centos-art." +"sh script, this translation marker expands to 5.8. On the other hand, if you are still running a CentOS-5.8 " +"distribution but provide the --release=6.3 option to centos-art.sh " +"script, this translation marker expands to 6.3 instead." +msgstr "" +"This translation marker expands to the current release information of your " +"CentOS distribution. By default this information is retrieved from /" +"etc/redhat-release. In case the option --" +"release be passed, the value specified with it will overwrite the " +"default value and will be this the one used as section for this translation " +"marker to retrieve the release information. So, for example, if you are " +"running a CentOS-5.8 distribution and no --" +"release option is passed to centos-art." +"sh script, this translation marker expands to 5.8. On the other hand, if you are still running a CentOS-5.8 " +"distribution but provide the --release=6.3 option to centos-art.sh " +"script, this translation marker expands to 6.3 instead." + +msgid "" +"In case you need to retrieve minor and major release numbers separately one " +"another, then you can use the =\\MINOR_RELEASE= and " +"=\\MAJOR_RELEASE= translation makers, respectively." +msgstr "" +"In case you need to retrieve minor and major release numbers separately one " +"another, then you can use the =\\MINOR_RELEASE= and " +"=\\MAJOR_RELEASE= translation makers, respectively." + +msgid "=\\ARCH=" +msgstr "=\\ARCH=" + +msgid "" +"This translation marker expands to the current architecture of your CentOS " +"Distribution. By default this information is retrieved from uname -i. In case the option --arch be passed, the value specified with it will overwrite " +"the default value and will be the one used as section. For example, if the " +"uname -i outputs the line <" +"computeroutput>i386</computeroutput>, this translation marker will " +"expand to i386. On the other hand, if you pass the " +"--arch=x86_64 option to centos-art.sh script, this translation marker will " +"expand to x86_64 instead." +msgstr "" +"This translation marker expands to the current architecture of your CentOS " +"Distribution. By default this information is retrieved from uname -i. In case the option --arch be passed, the value specified with it will overwrite " +"the default value and will be the one used as section. For example, if the " +"uname -i outputs the line <" +"computeroutput>i386</computeroutput>, this translation marker will " +"expand to i386. On the other hand, if you pass the " +"--arch=x86_64 option to centos-art.sh script, this translation marker will " +"expand to x86_64 instead." + +msgid "=\\URL=" +msgstr "=\\URL=" + +msgid "" +"This translation marker expands to the URL which points to The CentOS " +"Project home page. For example, =URL=. In case you are " +"using the centos-art.sh script in a different locale but English " +"(en_US.UTF-8), this translation marker expands as usual " +"but with the language information appended to the end of the string. For " +"example, if you are executing the centos-art.shscript for Spanish locale (e." +"g., es_ES.UTF-8), this translation marker expands to " +"=URL=es/." +msgstr "" +"This translation marker expands to the URL which points to The CentOS " +"Project home page. For example, =URL=. In case you are " +"using the centos-art.sh script in a different locale but English " +"(en_US.UTF-8), this translation marker expands as usual " +"but with the language information appended to the end of the string. For " +"example, if you are executing the centos-art.shscript for Spanish locale (e." +"g., es_ES.UTF-8), this translation marker expands to " +"=URL=es/." + +msgid "" +"In case you need to expand other URL related to The CentOS Project domain, " +"use translation markers described in . Likewise =\\URL=, translation markers described in does append the current " +"language information to the end of the URL string based on the locale " +"information you are currently executing the centos-" +"art.sh script." +msgstr "" +"In case you need to expand other URL related to The CentOS Project domain, " +"use translation markers described in . Likewise =\\URL=, translation markers described in does append the current " +"language information to the end of the URL string based on the locale " +"information you are currently executing the centos-" +"art.sh script." + +msgid "URL-related translation markers" +msgstr "URL-related translation markers" + +msgid "-------------------`----------------- Translation Marker Expands To" +msgstr "-------------------`----------------- Translation Marker Expands To" + +#, no-wrap +msgid "" +"=\\URL_WIKI= =URL_WIKI=\n" +"=\\URL_LISTS= =URL_LISTS=\n" +"=\\URL_FORUMS= =URL_FORUMS=\n" +"=\\URL_MIRRORS= =URL_MIRRORS=\n" +"=\\URL_DOCS= =URL_DOCS=\n" +"=\\URL_PROJECTS= =URL_PROJECTS=\n" +"=\\URL_SVN= =URL_SVN=\n" +"=\\URL_TRAC= =URL_TRAC=\n" +"=\\URL_PLANET= =URL_PLANET=" +msgstr "" +"=\\URL_WIKI= =URL_WIKI=\n" +"=\\URL_LISTS= =URL_LISTS=\n" +"=\\URL_FORUMS= =URL_FORUMS=\n" +"=\\URL_MIRRORS= =URL_MIRRORS=\n" +"=\\URL_DOCS= =URL_DOCS=\n" +"=\\URL_PROJECTS= =URL_PROJECTS=\n" +"=\\URL_SVN= =URL_SVN=\n" +"=\\URL_TRAC= =URL_TRAC=\n" +"=\\URL_PLANET= =URL_PLANET=" + +msgid "=\\MAIL_DOCS=" +msgstr "=\\MAIL_DOCS=" + +msgid "" +"This translation marker expands to CentOS documentation mailing list " +"address. For example, =MAIL_DOCS=." +msgstr "" +"This translation marker expands to CentOS documentation mailing list " +"address. For example, =MAIL_DOCS=." + +msgid "=\\LOCALE=" +msgstr "=\\LOCALE=" + +msgid "" +"This translation marker expands to the current locale information used by " +"centos-art.sh script. This value is " +"retrieved from the <envar>LANG</envar> environment variable and " +"should look like =LOCALE=. In case you need to retrieve " +"the language and country part separately one another, you can use the " +"=\\LOCALE_LL= and =\\LOCALE_CC=, " +"respectively." +msgstr "" +"This translation marker expands to the current locale information used by " +"centos-art.sh script. This value is " +"retrieved from the <envar>LANG</envar> environment variable and " +"should look like =LOCALE=. In case you need to retrieve " +"the language and country part separately one another, you can use the " +"=\\LOCALE_LL= and =\\LOCALE_CC=, " +"respectively." + +msgid "=\\REPO_TLDIR=" +msgstr "=\\REPO_TLDIR=" + +msgid "" +"This translation marker expands to the absolute path to <filename class=" +"\"directory\"> directory inside your workstation. For example, /home/al/Projects/CentOS/artwork/trunk+." +msgstr "" +"This translation marker expands to the absolute path to <filename class=" +"\"directory\"> directory inside your workstation. For example, /home/al/Projects/CentOS/artwork/trunk+." + +msgid "=\\REPO_HOME=, =\\TCAR_WORKDIR=" +msgstr "=\\REPO_HOME=, =\\TCAR_WORKDIR=" + +msgid "" +"This translation marker expands to the absolute path of your working copy. " +"For example, /home/al/Projects/CentOS/artwork." +msgstr "" +"This translation marker expands to the absolute path of your working copy. " +"For example, /home/al/Projects/CentOS/artwork." + +msgid "Bugs" +msgstr "Bugs" + +msgid "See https://centos.org.cu/bugs/" +msgstr "See https://centos.org.cu/bugs/" + +msgid "Authors" +msgstr "Authors" + +msgid "" +"The tcar_setTranslationMarkers function " +"has received contributions from the following people:" +msgstr "" +"The tcar_setTranslationMarkers function " +"has received contributions from the following people:" + +msgid "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" +msgstr "Alain Reguera Delgado <al@centos.org.cu>, =COPYRIGHT_YEAR_LIST=" + +msgid "License" +msgstr "License" + +msgid "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" +msgstr "Copyright © =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER=" + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +msgid "" +"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." +msgstr "" +"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." + +#. Put one translator per line, in the form of NAME , YEAR1, YEAR2. +msgid "translator-credits" +msgstr "translator-credits" diff --git a/Automation/Manuals/render.conf b/Automation/Manuals/render.conf index 9ba001d..fef2aa6 100644 --- a/Automation/Manuals/render.conf +++ b/Automation/Manuals/render.conf @@ -13,3 +13,51 @@ render-from = "tcar_setModuleEnvironment.sh.asciidoc" locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/tcar_setModuleEnvironment.sh.po" formats = "xhtml manpage" mansect = "1" + +[tcar_checkFiles.sh] +render-type = "asciidoc" +render-flow = "manpage" +render-from = "tcar_checkFiles.sh.asciidoc" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/tcar_checkFiles.sh.po" +formats = "xhtml manpage" +mansect = "1" + +[tcar_checkRepoDirSource.sh] +render-type = "asciidoc" +render-flow = "manpage" +render-from = "tcar_checkRepoDirSource.sh.asciidoc" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/tcar_checkRepoDirSource.sh.po" +formats = "xhtml manpage" +mansect = "1" + +[tcar_getConfigValue.sh] +render-type = "asciidoc" +render-flow = "manpage" +render-from = "tcar_getConfigValue.sh.asciidoc" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/tcar_getConfigValue.sh.po" +formats = "xhtml manpage" +mansect = "1" + +[tcar_getFilesList.sh] +render-type = "asciidoc" +render-flow = "manpage" +render-from = "tcar_getFilesList.sh.asciidoc" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/tcar_getFilesList.sh.po" +formats = "xhtml manpage" +mansect = "1" + +[tcar_printMessage.sh] +render-type = "asciidoc" +render-flow = "manpage" +render-from = "tcar_printMessage.sh.asciidoc" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/tcar_printMessage.sh.po" +formats = "xhtml manpage" +mansect = "1" + +[tcar_setTranslationMarkers.sh] +render-type = "asciidoc" +render-flow = "manpage" +render-from = "tcar_setTranslationMarkers.sh.asciidoc" +locale-from = "Locales/${TCAR_SCRIPT_LANG_LC}/tcar_setTranslationMarkers.sh.po" +formats = "xhtml manpage" +mansect = "1" diff --git a/Automation/Manuals/tcar_checkFiles.sh.asciidoc b/Automation/Manuals/tcar_checkFiles.sh.asciidoc new file mode 100644 index 0000000..7a0de6e --- /dev/null +++ b/Automation/Manuals/tcar_checkFiles.sh.asciidoc @@ -0,0 +1,135 @@ +tcar_checkFiles(1) +================== + +== Name + +tcar_checkFiles - Standardize constructions for file verifications. + +== Synopsis + +*cli_checkFiles [-d|-e|-f|-h|-x] LOCATION* + +== Description + +The *cli_checkFiles* exists to answer basic questions like ``Is ++LOCATION+ is a regular file?'' and ``Is +LOCATION+ a directory?''. +The answer to such questions affects the script execution flow in the +following way: when the answer positive (e.g., +LOCATION+ is a regular +file), the script passes the test silently and continues its +execution. When the answer is negative(e.g., +LOCATION+ is not a +regular file), the script finishes its execution immediately with an +error message. + +The *cli_checkFiles* function is exported to *centos-art.sh* script +environment in the very beginning of its execution and will be +available all along its execution lifetime. You can use this function +inside common and specific functions whenever you need to verify files +inside the The CentOS Artwork Repository. + +The *cli_checkFiles* function is available inside the *centos-art.sh* +script only as part of its execution environment. This function is +exported to *centos-art.sh* script just after executing the script +from the command-line and will be available all along the script +lifetime. So, you can use this function both in common and specific +functionalities of centos-art.sh script. + +The *cli_checkFiles* function doesn't create +subsequent execution environments. + +== Usage + +Use the *cli_checkFiles* function inside *centos-art.sh* script +whenever you need to control the script execution flow based on file +type (e.g., regular files, directories, links, etc.) verifications. + +== Options + +The *cli_checkFiles* function accepts the following options: + +-d:: + Verifies whether +LOCATION+ exists and is a directory. If it + doesn't exists or isn't a directory, an error message is printed + and the script finishes its execution. Otherwise, if it exists + and is a directory, the script continues its execution normally. +-e:: + Verifies whether +LOCATION+ exists or not. If it doesn't exist, an + error message is printed and the script finishes its execution. + Otherwise, if it does exists, the script continues its execution + normally. +-f:: + Verifies whether +LOCATION+ exists and is a regular file. If it + doesn't exists or isn't a regular file, an error message is + printed and the script finishes its execution. Otherwise, if it + exists and is a regular file, the script continues its execution + normally. +-h:: + Verifies whether +LOCATION+ exists and is a symbolic link. If it + doesn't exists or isn't a symbolic link, an error message is + printed and the script finishes its execution immediately. + Otherwise, if it does exist and is a symbolic link, the script + continue its execution normally. +-x:: + Verifies whether +LOCATION+ exists and execution permission is + granted. If it doesn't exist or hasn't execution permission, the + script finishes its execution immediately. Otherwise, if it exists + and has execution permissions, the script continues its execution + normally. + +The value of the +LOCATION+ argument must be an absolute path to the +file you want to verify. If such file doesn't exists in any supported +form, the script finishes its execution with an error message. + +== Examples + +The following example was taken from *centos-art.sh* script +initialization phase. Notice the position of *cli_checkFiles* +function inside the loop. If some of the function files we need to +export doesn't have execution rights, *cli_checkFiles* will finish the +script execution immediately with an error message. + +---------------------------------------------------------------------- +for FUNCFILE in ${FUNCFILES};do + + # Verify the execution rights for function file. + cli_checkFiles -x ${FUNCFILE} + + # Initialize the function file. + . ${FUNCFILE} + + # Export the function names inside the file to current shell + # script environment. + export -f $(egrep "${PATTERN}" ${FUNCFILE} | gawk '{ print $2 }') + +done +---------------------------------------------------------------------- + +== Bugs + +See https://centos.org.cu/bugs/ + +== Authors + +The *tcar_checkFiles* function has received contributions from the +following people: + +- Alain Reguera Delgado , =COPYRIGHT_YEAR_LIST= + +== License + +Copyright (C) =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= + +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. + +// vim: set syntax=asciidoc: diff --git a/Automation/Manuals/tcar_checkRepoDirSource.sh.asciidoc b/Automation/Manuals/tcar_checkRepoDirSource.sh.asciidoc new file mode 100644 index 0000000..412d4e6 --- /dev/null +++ b/Automation/Manuals/tcar_checkRepoDirSource.sh.asciidoc @@ -0,0 +1,59 @@ +tcar_checkRepoDirSource.sh(1) +============================= + +== Name + +tcar_checkRepoDirSource - Standardize the working copy's absolute path +construction. + +== Synopsis + +tcar_checkRepoDirSource "LOCATION" + +== Description + +The *tcar_checkRepoDirSource* function standardizes the path +construction to directories inside it the working copy, using absolute +paths. This function transforms relative paths passed as non-option +arguments to *centos-art.sh* script command-line into absolute paths +inside the working copy and verifies whether they really exist as +directories inside the working copy or not. If the path provided +doesn't exist as directory inside the working copy, the script will +finish its execution immediately with an error message. Otherwise, if +the directory exists, the variable +TCAR_ARGUMENTS+ is redefined with +the related absolute path for further use. + +Use the *tcar_checkRepoDirSource* function whenever you need to be +sure that non-option arguments passed to *centos-art.sh* script +command-line will always point to directories inside the working copy. + +== Bugs + +See https://centos.org.cu/bugs/ + +== Authors + +The *tcar_checkRepoDirSource* function has received contributions from +the following people: + +- Alain Reguera Delgado , =COPYRIGHT_YEAR_LIST= + +== License + +Copyright (C) =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= + +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. + +// vim: set syntax=asciidoc: diff --git a/Automation/Manuals/tcar_getConfigValue.sh.asciidoc b/Automation/Manuals/tcar_getConfigValue.sh.asciidoc new file mode 100644 index 0000000..bd5002e --- /dev/null +++ b/Automation/Manuals/tcar_getConfigValue.sh.asciidoc @@ -0,0 +1,72 @@ +tcar_getConfigValue.sh(1) +========================= + +== Name + +tcar_getConfigValue - Standardize options retrieval from configuration +files. + +== Synopsis + +*tcar_getConfigValue FILE SECTION OPTION* + +== Description + +The *tcar_getConfigValue* function standardizes the way option values +are retrieved from configuration files. As convention, +*tcar_getConfigValue* uses the output produced by +*tcar_getConfigLines* as input to retrieve the option values. As +convention, in +option = "value"+ lines, the values retrieved are +always on the right side. The values retrieved are also output without +quotation and translation markers already expanded. + +The *tcar_getConfigValue* function accepts the +following arguments: + +FILE:: + This argument specifies the absolute path to the configuration + file you want to retrieve the value from. For example, + ``+${TCAR_WORKDIR}/Identity/Models/Themes/Default/Distro/5/Anaconda/branding.conf+''. + +SECTION:: + This argument specifies the name of the section related to the + configuration line you want to retrieve the value from. For + example, ``symbols'' without brackets. + +OPTION:: + This argument specifies the name of the option you want to + retrieve the value from. + +Use the *tcar_getConfigValue* function whenever you want to retrieve +values from configuration files in a controlled way. + +== Bugs + +See https://centos.org.cu/bugs/ + +== Authors + +The *tcar_checkFiles* function has received contributions from the +following people: + +- Alain Reguera Delgado , =COPYRIGHT_YEAR_LIST= + +== License + +Copyright (C) =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= + +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. + +// vim: set syntax=asciidoc: diff --git a/Automation/Manuals/tcar_getFilesList.sh.asciidoc b/Automation/Manuals/tcar_getFilesList.sh.asciidoc new file mode 100644 index 0000000..8ca537d --- /dev/null +++ b/Automation/Manuals/tcar_getFilesList.sh.asciidoc @@ -0,0 +1,107 @@ +tcar_getFilesList.sh(1) +======================= + +== Name + +tcar_getFilesList - Create customized list of files for further +processing. + +== Synopsis + +*tcar_getFilesList [--pattern|--mindepth|--maxdepth|--type|--uid] LOCATION* + +== Description + +The *tcar_getFilesList* standardizes the way list of files are built +inside the *centos-art.sh* script. This function outputs a sorted and +unique list of files based on the options and location provided as +argument. This function is an interface to the *find* command. Don't +use *find* command directly inside the centos-art.sh script. Instead, +use the *tcar_getFilesList* function. + +The +LOCATION+ arguments must be the absolute path to a directory and +specifies where the search of files in any form (e.g., directories, +links, etc.) will take place in. If +LOCATION+ isn't a directory, the +script finishes its execution with an error message. + +The *tcar_getFilesList* accepts the following options: + +--pattern="REGEX":: + This option specifies a posix-egrep type regular expression as + value. This regular expression is applied to path specified in + +LOCATION+ argument. Only file paths that match this regular + expression inside +LOCATION+ directory will be included in the + final list of files. By default, if this option is not provided, + the ``+^/.*[[:alnum:]_/-]+$+'' regular expression + is used. ++ +When you use the *tcar_getFilesList* you don't need to specified the +absolute path of files you want to look for. This is something +*tcar_getFilesList* already does for you. When you use this function, +the value you pass as regular expression isn't the final regular +expression used. Instead, the regular expression you pass is used to +build the final regular expression passed to *find* command. The +final regular expression passed to find is ``+^/.*${PATTERN}$+'', +where +${PATTERN}+ is the value you passed to *--pattern* option as +REGEX. + +--mindepth="NUMBER":: + This option specifies the minimal +NUMBER+ of levels deep the + search should go under the directory +LOCATION+ specified. For + example, if you specify *--mindepth="2"* the search will start two + levels deep considering the path provided as section. + +--maxdepth="NUMBER":: + This option specifies the maximum +NUMBER+ of levels deep the + search should go under the directory +LOCATION+ specified. For + example, if you specify *--maxdepth="2"* the search will begin in + the very same directory path you provided as +LOCATION+ and stop + two levels deep using it as section. + +--type="STRING":: + This option specifies the type of files being searched. This + option accepts the same values the *find* *-type* option does. + However, the following +STRING+ values are the most used inside + the script so far: ++ +- d — directory. +- f — regular file. + +--uid="NUMBER":: + This option specifies the numeric user id of the files you want to + search. Only files that match this numeric user id will be added + to the final list of files. + +Use the *tcar_getFilesList* whenever you need to build list of files +for further processing. + +== Bugs + +See https://centos.org.cu/bugs/ + +== Authors + +The *tcar_checkFiles* function has received contributions from the +following people: + +- Alain Reguera Delgado , =COPYRIGHT_YEAR_LIST= + +== License + +Copyright (C) =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= + +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. + +// vim: set syntax=asciidoc: diff --git a/Automation/Manuals/tcar_printMessage.sh.asciidoc b/Automation/Manuals/tcar_printMessage.sh.asciidoc new file mode 100644 index 0000000..7db2ed8 --- /dev/null +++ b/Automation/Manuals/tcar_printMessage.sh.asciidoc @@ -0,0 +1,192 @@ +tcar_printMessage.sh(1) +======================= + +== Name + +tcar_printMessage.sh - Print customized messages in standard ways. + +== Synopsis + +*tcar_printMessage "MESSAGE" [--as-separator-line|--as-banner-line|--as-cropping-line|--as-tuningup-line|--as-checking-line|--as-combining-line|--as-creating-line|--as-reading-line|--as-savedas-line|--as-linkto-line|--as-movedto-line|--as-validating-line|--as-template-line|--as-configuration-line|--as-palette-line|--as-reponse-line|--as-request-line|--as-selection-line|--as-error-line|--as-toknowmore-line|--as-yesornorequest-line|--as-notrailingnew-line|--as-stdout-line|--as-stderr-line]* + +== Description + +The *tcar_printMessage* function standardizes the way centos-art.sh +scirpt prints messages. By default, centos-art.sh script prints all +messages to the standard output with the exception of those messages +printed with the *--as-stderr-line* option, which are printed to +standard error output instead. + +The *tcar_printMessage* function requires two arguments. The first +argument specifies the message you want to print and the second +argument specifies the format you'll use to print that message. +Because this function is so used inside the centos-art.sh script, it +is convenient to provide localization to strings passed as +MESSAGE+ +using *gettext* constructions when they aren't paths. + +== Options + +The *tcar_printMessage* function accepts the following format options +as second argument: + +--as-separator-line:: + This format takes the first character passed as +MESSAGE+ and + repeats it horizontally to build a separator line. Use this + format whenever you need to create a logical separation between + different actions. + +--as-banner-line:: + This format takes the string passed as +MESSAGE+ and puts it + inside two horizontal separator lines. Use this format whenever + you need to print header information for following lines. + +--as-cropping-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file has been cropped. + +--as-tuningup-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file has been tuned-up. + +--as-checking-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file has been checked or + verified (e.g., through *tcar_checkFiles* functionality). + +--as-combining-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file has been combined. + +--as-creating-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file has been created. + +--as-reading-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file has been read. + +--as-savedas-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file has been saved. + +--as-linkto-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file has been linked. + +--as-movedto-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file has been moved. + +--as-validating-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file has been validated. + +--as-template-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file is a template or + design model. + +--as-configuration-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file is a configuration + file. + +--as-palette-line:: + This format is for two columns messages where +MESSAGE+ generally + refers to a file inside the repository. Use this format whenever + you need to imply the fact that certain file is a palette of + colors. + +--as-response-line:: + This format adds +-->+ at the beginning of the string passed as + +MESSAGE+. Use this format whenever you need to imply the fact + that certain file is considered part of a response. For example, + when you need to express that a group of files will take certain + action, you can use this option to doing so. + +--as-request-line:: + This format prints +MESSAGE+ without trailing new line. Use this + format whenever you need to imply a question or yes or no request. + +--as-selection-line:: + This format uses each word in +MESSAGE+ as item of a selection + list. Use this format whenever you need to select one of the items + provided as +MESSAGE+. + +--as-error-line:: + This format prints error messages produced by centos-art.sh + script. It uses the *caller* built-in command to display the line + number and the filename where such error was triggered. Later, it + prints where to find more information by using the + *--as-toknowmore-line* option. + +--as-toknowmore-line:: + This format takes a function name as +MESSAGE+ and prints the + command you can use to find more information about it. When this + option is passed the script finishes its execution immediately. + This option is used in combination with *--as-error-line* to + finish the script execution after an error. + +--as-yesornorequest-line:: + This format takes a question as +MESSAGE+ and reads a yes or no + answer. When answer is negative, the script finishes its execution + immediately. When answer is affirmative, the script continues its + execution normally. + +--as-notrailingnew-line:: + Print +MESSAGE+ without any trailing + newline. + +--as-stdout-line:: + Print +MESSAGE+ to standard output. + +--as-stderr-line:: + Print +MESSAGE+ to standard error output. + +== Examples + +... + +== Bugs + +See https://centos.org.cu/bugs/ + +== Authors + +The *tcar_printMessage* function has received contributions from the +following people: + +- Alain Reguera Delgado , =COPYRIGHT_YEAR_LIST= + +== License + +Copyright (C) =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= + +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. + +// vim: set syntax=asciidoc: +// vim: set syntax=asciidoc: diff --git a/Automation/Manuals/tcar_setTranslationMarkers.sh.asciidoc b/Automation/Manuals/tcar_setTranslationMarkers.sh.asciidoc new file mode 100644 index 0000000..3474df9 --- /dev/null +++ b/Automation/Manuals/tcar_setTranslationMarkers.sh.asciidoc @@ -0,0 +1,199 @@ +tcar_setTranslationMarkers(1) +============================= + +== Name + +tcar_setTranslationMarkers - Expands translation markers. + +== Synopsis + +*tcar_setTranslationMarkers "FILE"* + +== Description + +The *cli_setTranslationMarkers* standardizes construction of +translation markers and their related expansion. As convention, +translation markers are set inside source files (e.g., DocBook, SVG) +and expanded inside temporal instances used to produce final contents. +The +FILE+ argument should point to the temporal file where +translation markers expansion takes place in. + +Translation markers written in source files must comply the +++=[A-Z_]+=++ regular expression pattern. For example, ++=UNKNOWN_MARKER=+ is a valid translation marker without any +replacement. To prevent *centos-art.sh* script from +expanding translation markers, add a backslash (+\+) between the first +equal sign and the following letter. For example, +=\...=+ won't be +expanded. + +The *cli_setTranslationMarkers* supports the following translation +markers: + ++=\COPYRIGHT_YEAR_LAST=+, +=\COPYRIGHT_YEAR=+:: + These translation markers expand to the last year used in + copyright notes. For example, +=COPYRIGHT_YEAR_LAST=+. + ++=\COPYRIGHT_YEAR_LIST=+, +=\COPYRIGHT_YEARS_LIST=+:: + This translation markers expand to the list of years used in + copyright notes. For example, +=COPYRIGHT_YEARS_LIST=+. The first + year represents the time we began to work on The CentOS Artwork + Repository. + ++=\COPYRIGHT_HOLDER=+:: + This translation marker expands to the holder used in copyright + notes. For example, +=COPYRIGHT_HOLDER=+. + ++=\COPYRIGHT_HOLDER_PREDICATE=+:: + This translation marker expands both the holder and the predicate + used in copyright notes. For example, + +=COPYRIGHT_HOLDER_PREDICATE=+. + ++=\BRAND=+:: + This translation marker expands to the brand name used on files + names and URLs inside The CentOS Artwork Repository. For example, + +=BRAND=+. + ++=\LICENSE=+:: + This translation marker expands to the license information used in + files created by *centos-art.sh* script. For + example, +=LICENSE=+. + ++=\LICENSE_URL=+:: + This translation marker expands to the license URL used in files + created by *centos-art.sh* script. For example, + +=LICENSE_URL=+. + ++=\THEME=+:: + This translation marker expands to the theme portion of path you + are producing through centos-art.sh script. As consequence, this + translation marker should be used in situations where you are + producing theme components only. This translation marker expands + its value by retrieving the theme part of the path you provide as + non-option argument to *centos-art.sh* script. + For example, if you provide the path + +Identity/Images/Themes/Modern/2/Distro/5+, + this translation will expand to the +Modern/2/+ value. ++ +In case you need to retrieve the theme name or version separately one +another, then you can use the +=\THEMENAME=+ and +=\THEMERELEASE=+ +translation markers, respectively. When you use these translation +markers, forward slashes are removed from result. So, if you provide +the path ++Identity/Images/Themes/Modern/2/Distro/5+, ++=\THEMENAME=+ will expand to +Modern+ and +=THEMERELEASE=+ will +expand to +2+. + ++=\RELEASE=+:: + This translation marker expands to the current release information + of your CentOS distribution. By default this information is + retrieved from +/etc/redhat-release+. In case + the option *--release* be passed, the value specified with it will + overwrite the default value and will be this the one used as + section for this translation marker to retrieve the release + information. So, for example, if you are running a CentOS-5.8 + distribution and no *--release* option is passed to + *centos-art.sh* script, this translation marker + expands to +5.8+. On the other hand, if you are still running a + CentOS-5.8 distribution but provide the *--release=6.3* option to + *centos-art.sh* script, this translation marker + expands to +6.3+ instead. ++ +In case you need to retrieve minor and major release numbers +separately one another, then you can use the +=\MINOR_RELEASE=+ and ++=\MAJOR_RELEASE=+ translation makers, respectively. + ++=\ARCH=+:: + This translation marker expands to the current architecture of + your CentOS Distribution. By default this information is retrieved + from *uname -i*. In case the option *--arch* be + passed, the value specified with it will overwrite the default + value and will be the one used as section. For example, if the + *uname -i* outputs the line + i386, this translation marker + will expand to +i386+. On the other hand, if you pass the + *--arch=x86_64* option to *centos-art.sh* script, + this translation marker will expand to +x86_64+ instead. + ++=\URL=+:: This translation marker expands to the URL which points to +The CentOS Project home page. For example, +=URL=+. In case you are +using the centos-art.sh script in a different locale but English +(+en_US.UTF-8+), this translation marker expands as usual but with the +language information appended to the end of the string. For example, +if you are executing the centos-art.shscript for Spanish locale (e.g., ++es_ES.UTF-8+), this translation marker expands to +=URL=es/+. ++ +In case you need to expand other URL related to The CentOS Project +domain, use translation markers described in +<>. Likewise =\URL=, translation +markers described in <> does append +the current language information to the end of the URL string based on +the locale information you are currently executing the *centos-art.sh* +script. + +[[url-related-translation-markers]] +.URL-related translation markers +-------------------`----------------- +Translation Marker Expands To +------------------------------------- +=\URL_WIKI= =URL_WIKI= +=\URL_LISTS= =URL_LISTS= +=\URL_FORUMS= =URL_FORUMS= +=\URL_MIRRORS= =URL_MIRRORS= +=\URL_DOCS= =URL_DOCS= +=\URL_PROJECTS= =URL_PROJECTS= +=\URL_SVN= =URL_SVN= +=\URL_TRAC= =URL_TRAC= +=\URL_PLANET= =URL_PLANET= +------------------------------------- + ++=\MAIL_DOCS=+:: + This translation marker expands to CentOS documentation mailing + list address. For example, +=MAIL_DOCS=+. + ++=\LOCALE=+:: + This translation marker expands to the current locale information + used by *centos-art.sh* script. This value is + retrieved from the LANG environment variable and + should look like +=LOCALE=+. In case you need to retrieve the + language and country part separately one another, you can use the + +=\LOCALE_LL=+ and +=\LOCALE_CC=+, respectively. + ++=\REPO_TLDIR=+:: + This translation marker expands to the absolute path to + directory inside your workstation. For + example, +/home/al/Projects/CentOS/artwork/trunk+. + ++=\REPO_HOME=+, +=\TCAR_WORKDIR=+:: + This translation marker expands to the absolute path of your + working copy. For example, +/home/al/Projects/CentOS/artwork+. + +== Bugs + +See https://centos.org.cu/bugs/ + +== Authors + +The *tcar_setTranslationMarkers* function has received contributions +from the following people: + +- Alain Reguera Delgado , =COPYRIGHT_YEAR_LIST= + +== License + +Copyright (C) =COPYRIGHT_YEAR_LIST= =COPYRIGHT_HOLDER= + +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. + +// vim: set syntax=asciidoc: