diff --git a/Manuals/en/Texinfo/Repository/trunk/Identity/Fonts.texi b/Manuals/en/Texinfo/Repository/trunk/Identity/Fonts.texi index d4da140..ef6730a 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Identity/Fonts.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Identity/Fonts.texi @@ -37,8 +37,8 @@ clear enough to dismiss any confussion between similar typefaces As CentOS logo typography convenction, the word @samp{CentOS} uses @samp{Denmark} typography as base, both for the word @samp{CentOS} and -the phrase @samp{Community Enterprise Operating System}. The size of -CentOS logo's phrase is half the size in poits the word @samp{CentOS} +the phrase @samp{Community Enterprise Operating System}. The phrase +size of CentOS logo is half the size in poits the word @samp{CentOS} has and it below @samp{CentOS} word and aligned with it on the left. The distance between @samp{CentOS} word and phrase @samp{Community Enterprise Operating System} have the size in points the phrase has. diff --git a/Manuals/en/Texinfo/Repository/trunk/Identity/Models/Tpl/Promo/Web.texi b/Manuals/en/Texinfo/Repository/trunk/Identity/Models/Tpl/Promo/Web.texi index 836340e..f67b346 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Identity/Models/Tpl/Promo/Web.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Identity/Models/Tpl/Promo/Web.texi @@ -41,9 +41,9 @@ their own visual styles. For example: MoinMoin, the web application used to support the CentOS wiki (@url{http://wiki.centos.org/}) is highly customizable but Mailman (in its 2.x.x serie), the web application used to support the CentOS mailing list, doesn't -support@footnote{Mailman's theme support may be introduced in +support@footnote{The theme support of Mailman may be introduced in mailman-3.x.x release.} a customization system that separates -presentation from logic, similar to MoinMoin's one. +presentation from logic, similar to that used by MoinMoin. This visual style diversity complicates our goal of one unique visual style for all web applications. So, if we want one unique visual style @@ -230,9 +230,9 @@ the place where you customize the visual style of @file{webapp1-0.0.1/} web application. @quotation -@strong{Tip} Use Subversion's @command{diff} between CentOS -customization and upstream development lines to know what you are -changing exactly. +@strong{Tip} Use the @command{diff} command of Subversion between +CentOS customization and upstream development lines to know what you +are changing exactly. @end quotation @item Build packages diff --git a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Models/Default.texi b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Models/Default.texi index 24bc2e6..6ce9103 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Models/Default.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Models/Default.texi @@ -1,7 +1,7 @@ @subsection Goals -This location stores CentOS default theme model. The CentOS default -theme model is used in all visual manifestations of CentOS Project's +This location stores CentOS default theme model. The default theme +model of CentOS is used in all visual manifestations of CentOS Project corporate visual identity (e.g., distributions, web sites, promotion, etc.). diff --git a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs.texi b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs.texi index 43dc5f3..7b8c0e0 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs.texi @@ -9,8 +9,8 @@ The @file{trunk/Identity/Themes/Motifs} directory exists to: @subsection Description The artistic motif of theme is a graphic design component that -provides theme's visual style, it is used as pattern to connect all -visual manifestations inside one unique theme. +provides the visual style of themes, it is used as pattern to connect +all visual manifestations inside one unique theme. Artistic motifs are based on conceptual ideas. Conceptual ideas bring the motivation, they are fuel for the engines of human imagination. @@ -30,7 +30,7 @@ If you have new conceptual ideas for CentOS, then you can say that you want to create a new artistic motif for CentOS. To create a new artistic motif you need to create a directory under @file{Identity/Themes/Motifs/} using a name coherent with your -conceptual idea. That name will be your artistic motif's name. If +conceptual idea. That name will be the name of your artistic motif. If possible, when creating new conceptual ideas for CentOS, think about what CentOS means for you, what does it makes you feel, take your time, think deep, and share; you can improve the idea as time goes on. @@ -48,8 +48,8 @@ use the @command{centos-art} command line in the centos-art add --motif=ThemeName @end example -The previous command will create the motif's basic structure for you. -The basic structure produced by @command{centos-art} command is +The previous command will create the basic structure of themes for +you. The basic structure produced by @command{centos-art} command is illustrated in the following figure: @example @@ -79,18 +79,16 @@ inspiration and concepts behind your work. store your work. If it doesn't exist create it. Note that this require you to have previous commit access in CentOS Artwork Repository. -@item The CentOS Project is using the blue color (@b{#204c8d}) -as base for its corporate visual identity. Use the CentOS Project's -base corporate color as much as possible in your artistic motif -designs. +@item The CentOS Project is using the blue color (@b{#204c8d}) as base +color for its corporate visual identity. Use such base corporate color +information as much as possible in your artistic motif designs. @item Try to make your design fit one of the theme models. @item Feel free to make your art enterprise-level and beautiful. -@item Add the following information on your art work (both in a visible -design area, and inside Inkscape's document metadata section wherever -it be possible): +@item Add the following information on your artwork (both in a visible +design area and document metadata): @itemize diff --git a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Flame.texi b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Flame.texi index 6815200..57c0b78 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Flame.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Flame.texi @@ -16,8 +16,8 @@ identity (@pxref{trunk Identity}). The @emph{Flame} artistic motif was built using the flame filter of Gimp 2.2 in CentOS 5.5. -The Gimp's flame filter can produce stunning, randomly generated -fractal patterns. The Gimp's flame filter gives us a great oportunity +The flame filter of Gimp can produce stunning, randomly generated +fractal patterns. The flame filter of Gimp gives us a great oportunity to reduce the time used to produce new artistic motifs, because of its ``randomly generated'' nature. Once the artistic motif be created, it is propagated through all visual manifestations of CentOS Project @@ -32,7 +32,7 @@ visual identity (i.e., distribution stuff, promotion stuff, websites stuff, etc.) with the new major release of CentOS distribution all together at once. -Producing a new visual style is not one day's task. Once we have +Producing a new visual style is not one day's time task. Once we have defined the artistic motif, we need to propagate it through all visual manifestations of The CentOS Project corporate visual identity. When we say that we could produce one new visual style every two years we @@ -139,10 +139,10 @@ Duplicate @samp{Base} layer and name it @samp{Paper}. Place Once you've done with black radial degradation, reduce the @samp{Paper} layer opacity to 20%. -Notice that when we duplicate one layer, the information related to -layer's mask is preserved from one layer to another. This saves some -time when you want to have different layers with the same mask -information on them. +Notice that when we duplicate one layer, the mask information related +to layer is preserved from one layer to another. This saves some time +when you want to have different layers with the same mask information +on them. Duplicate @samp{Paper} layer and rename it @samp{Stripes}. Remove paper pattern from @samp{Stripes} layer. Fill @samp{Stripes} layer @@ -160,10 +160,10 @@ Create a new layer named @samp{Flame}. Set the foreground (@code{003cff}) and background (@code{0084ff}) colors to the gradient you want to build the flame motif. -To build flame motif, use the Gimp's flame filter (@samp{Filters > -Render > Nature > Flame...}) on @samp{Flame} layer. We used a layer -mask, with a radial gradient on it to control the boundaries of flame -motif on @samp{Flame} layer. +To build flame motif, use the flame filter (@samp{Filters > Render > +Nature > Flame...}) on @samp{Flame} layer. We used a layer mask, with +a radial gradient on it to control the boundaries of flame motif on +@samp{Flame} layer. Duplicate @samp{Flame} layer and rename it `Flame Blur'. Place `Flame Blur' below @samp{Flame} layer. Apply Gussian blur filter @@ -198,8 +198,9 @@ and recreate a new one using an inverted alpha channel as reference. Remove @samp{Color#1} layer content and fill it back with plain black (@code{000000}) color. Reduce @samp{Color#1} opacity to 20%. In this step we created a mask to protect the flame artistic motif from black -color, so when we decrement or increment layer's opacity, the flame -artistic motif wouldn't be affected, just the environment suround it. +color, so when we decrement or increment the opacity of layer, the +flame artistic motif wouldn't be affected, just the environment +suround it. @float Figure, fig:Motifs:Flame:Construction:4 @image{trunk/Identity/Themes/Motifs/Flame/Screenshots/Construction/5,400pt,,,jpg} diff --git a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi index 876b7d6..eef32da 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds.texi @@ -6,10 +6,11 @@ @subsection Description -Inside motif's @file{Backgrounds/} directory you can create vectorial -designs using Inkscape and background images using Gimp. Later, you -can export background images as @file{.png} and load them in your -vectorial design project using Inkscape's import feautre. +Inside @file{Motifs} directory, the @file{Backgrounds/} directory is +used to create vectorial designs using Inkscape and background images +using Gimp. Later, you can export background images as @file{.png} and +load them in your vectorial design project using the import feautre of +Inkscape. You may need to repeat this technic for different screen resoluions. In that case you need to create one file for each screen resolution @@ -42,7 +43,7 @@ img/800x600.png The @file{img/800x600.png} background image is produced automatically by means of rendering scripts. -In other cases, like Anaconda's, it is possible that you need to make +In other cases (e.g. Anaconda), it is possible that you need to make some variations to one background image that don't want to appear on regular background images of the same resolution. In this case you need to create a new and specific background image for that art @@ -78,16 +79,16 @@ and 640x480 pixels so you need to create a 640x480 background image for it, and take the color limitation into account when designing it. Background images without artistic motif are generally used as based -to build the Background images that do contain the theme's artistic +to build the Background images that do contain the theme artistic motif. -Background images are linked (using Inkscape's @b{import} feature) -inside almost all theme art works. This structure let you make -centralized changes on the visual identity and propagate them quickly -to other areas. +Background images are linked (using the @b{import} feature of +Inkscape) inside almost all theme art works. This structure let you +make centralized changes on the visual identity and propagate them +quickly to other areas. In this structure you design background images for different screen -resolutions based on theme's artistic motif. +resolutions based on the theme artistic motif. You may create different artistic motifs propositions based on the same conceptual idea. The conceptual idea is what defines a @@ -114,8 +115,8 @@ When you design an artistic motif for CentOS you concentrate on its visual style, and eventualy, use the @command{centos-art} command line interface to render the visual style, you are currently producing, against an already-made theme model in order to produce the final -result. Final images are stored under the motif's name directory -using the model directory structure as reference. +result. Final images are stored under @file{Motifs/} directory using +the model name, and the model directory structure as reference. The artistic motif base structure is used by @command{centos-art} to produce images automatically. This section describes each directory of @@ -123,11 +124,12 @@ CentOS artistic motif base structure. @subsection Usage -The motif's @file{Backgrounds/} directory is probably the motif's core -component. Inside motif's @file{Backgrounds/} directory you produce -background images used by almost all theme models (e.g., Distribution, -Websites, Promotion, etc.). The motif's @file{Backgrounds/} directory -can contain subdirectories to help you organize the design process. +The @file{Backgrounds/} directory is probably the core component, +inside @file{Motifs/} directory structure. Inside @file{Backgrounds/} +directory you produce background images used by almost all theme +models (e.g., Distribution, Websites, Promotion, etc.). The +@file{Backgrounds/} directory can contain subdirectories to help you +organize the design process. @subsection See also diff --git a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi index feb304a..b572a3d 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf.texi @@ -13,13 +13,13 @@ @subsection Usage -In this directory is where you store Gimp's project files (e.g, .xcf). -This directory is not required by @file{centos-art} command line -interface. If you can create a beautiful background images using +In this directory is where you store the project files (e.g, .xcf) of +Gimp. This directory is not required by @file{centos-art} command +line interface. If you can create a beautiful background images using scalable vector graphics only, then there is no need to use the -@file{Xcf/} directory to store Gimp's background projects. Of course, -you can merge Gimp's power with Inkscape's power to produce images -based on them. In this last case you need the @file{Xcf/} directory. +@file{Xcf/} directory to store background projects. Of course, you can +merge both Gimp and Inkscape power to produce images based on them. +In this last case you need the @file{Xcf/} directory. @subsection See also diff --git a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi index 84d7b78..a0f9856 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress.texi @@ -8,10 +8,10 @@ @subsection Usage -To render Anaconda progress slide images using the Modern's artistic -motif design, the Default theme model, and available translation files -(@pxref{trunk Translations Identity Themes Distro Anaconda Progress}); -use the following commands: +To render Anaconda progress slide images using the @emph{Modern} +artistic motif design, the Default theme model, and available +translation files (@pxref{trunk Translations Identity Themes Distro +Anaconda Progress}); use the following commands: @example cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ diff --git a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Palettes.texi b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Palettes.texi index b5bca41..79765d1 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Palettes.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/Modern/Palettes.texi @@ -11,7 +11,8 @@ Here is where graphic designers define theme palettes for color-limited art works. Theme palettes contain the color information that rendering functions need, in order to produce images with color -limitations. Theme palettes contain theme's unique color information. +limitations. Theme palettes contain the unique color information +required by theme. @subsection See also diff --git a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi index 404af31..32e0626 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds.texi @@ -1,6 +1,7 @@ @subsection Goals -This section exists to orgnize TreeFlower's backgrounds. +This section exists to orgnize backgrounds of @emph{TreeFlower} +artistic motif. @subsection Description @@ -13,7 +14,7 @@ vectorial design do the following: Open the png version with GIMP. -Save the png version as gimp's project inside +Save the png version as a project of GIMP inside @file{trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Xcf} directory, using the same name of your vectorial design but with the @samp{.xcf} extension. @@ -22,8 +23,8 @@ Now use GIMP to improve your design. Here you may add one layer for pattern, another for colors, and so on until you find yourself confortable with your artwork. For example, the following layer distribution (from bottom to top) was used to build revision 285 of -file @file{1360x768.xcf} using TreeFlower's artistic motif at revision -241. +file @file{1360x768.xcf} using @emph{TreeFlower} artistic motif at +revision 241. @table @strong @item Layer 1: Background @@ -95,9 +96,9 @@ opacity. visual design is a matter of constant testing and personal taste. @end quotation -Finally, use the GIMP's @samp{Save as copy ...} option to export the -final design. To export the final design use the same name of your -vectorial design plus @samp{-final.png} extension. +Finally, use @samp{Save as copy ...} option to export the final +design. To export the final design use the same name of your vectorial +design plus @samp{-final.png} extension. You can repeat these steps to create images for other screen resolutions. @@ -176,8 +177,8 @@ color information found with this composition produces an acceptable 16 color image. Of course this is something we haven't seen yet. To define the color information of our current coposition, save the -syslinux GIMP's background composition we've done using GIMP's -@samp{File > Save as Copy ...} option in the following location: +syslinux background composition we've done using @samp{File > Save as +Copy ...} option in the following location: @verbatim trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Img/Png/640x300-final.png @@ -198,9 +199,9 @@ the correct color information to use. Open one @file{syslinux-splash.png} file with GIMP and use the @samp{Image > Mode > Indexed} to reduce image colors up to 16 colors, -using GIMP's @samp{Generate optimum palette} feature. If the image -looks aceptable after reducing colors, use GIMP's @samp{Palettes} menu -(Ctrl+P) to import a new palette from file and name it +using the @samp{Generate optimum palette} feature of GIMP. If the +image looks aceptable after reducing colors, use the @samp{Palettes} +menu (Ctrl+P) of GIMP to import a new palette from file and name it @samp{CentOS-TreeFlower-Syslinux}. Once you've saved the palette, the color information is stored at: diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash.texi index f571fad..dffcf07 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash.texi @@ -21,7 +21,7 @@ When you type the @command{centos-art} command in your terminal, the operating system trys to execute that command. In order to execute the command, the operating system needs to know where it is, so the operating system uses the @var{PATH} environment variable to look for -that command's location. If your system was prepared to use CentOS +that command location. If your system was prepared to use CentOS Artwork Repository correctly (@pxref{trunk Scripts Bash Functions Verify}), you should have a symbolic link inside @file{~/bin/} directory that points to the @file{centos-art.sh} script file. As @@ -31,7 +31,7 @@ variable, the execution of @command{centos-art} command runs the When @file{centos-art.sh} script is executed, the first it does is executing the @file{trunk/Scripts/Bash/initEnvironment.sh} script to -initialize global variables (e.g., @command{gettext}'s variables) and +initialize global variables (e.g., @command{gettext} variables) and global function scripts. Global function scripts are located inside @file{trunk/Scripts/Bash/Functions} directory and their file names begin with @samp{cli}. Global function scripts provide common diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi index 03c5913..eea03fd 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi @@ -73,8 +73,8 @@ Inside @file{centos-art.sh} script functions, top commentaries have the following components: the functionality description, one-line for copyright note with your personal information, the license under which the function source code is released ---the @file{centos-art.sh} -script is released as GPL, so do all its functions---, subversion's -@code{$Id$} keyword which is later expanded by @command{svn propset} +script is released as GPL, so do all its functions---, the @code{$Id$} +keyword of Subversion is later expanded by @command{svn propset} command. In our @code{greet} function example, top commentary for @@ -205,7 +205,7 @@ The @code{greet_doBye} function definition is stored in the @file{greet_doBye.sh} function script. Both @file{greet_doHello.sh} and @file{greet_doBye.sh} function -scripts are stored inside @code{greet}'s function directory path (i.e. +scripts are stored inside @code{greet} function directory path (i.e. @file{trunk/Scripts/Bash/Functions/Greet}). The @var{ACTIONVAL} global variable is defined in @file{cli.sh} @@ -216,8 +216,8 @@ argument is @option{--hello='World'}, the value of @var{ACTIONVAL} variable would be @samp{World} without quotes. Let's see how @code{greet} specific functionality files are organzied -under @code{greet}'s function directory. To see file organization we -use the @command{tree} command: +under @code{greet} function directory. To see file organization we use +the @command{tree} command: @verbatim trunk/Scripts/Bash/Functions/Greet @@ -645,7 +645,7 @@ Initialize function name (@var{FUNCNAM}), action name variables, using positional parameters passed in @var{$@@} variable. The @code{cli_getArguments} function is called from @code{cli.sh} -function script, using @code{cli} function's positional parameters +function script, using @code{cli} function positional parameters (i.e., the positional parameters passed as arguments in the command-line) as first function argument. diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Locale.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Locale.texi index 2d791eb..bf264c9 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Locale.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Locale.texi @@ -46,7 +46,7 @@ environment variable to determine your favorite text editor. If no value is defined on @var{EDITOR}, the @file{/usr/bin/vim} text editor is used as default. -When you finish PO file's edition and quit text editor, the +When you finishd PO file edition and quit text editor, the @command{centos-art} command creates the related machine object in the location @file{$CLI_LANG/LC_MESSAGES/$TEXTDOMAIN.mo}. diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Path.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Path.texi index 90e879f..e0e87cc 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Path.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Path.texi @@ -294,10 +294,10 @@ in mind the corporate visual identity structure used inside the CentOS Artwork Repository (@pxref{trunk Identity}) would be probaly the best advice we could offer, the rest is just matter of choosing appropriate names. To illustrate this desition process let's consider the -@file{trunk/Identity/Themes/Motifs/TreeFlower} directory as -example. It is the trunk development line of TreeFlower's artistic -motif. Artistic motifs are considered part of themes, which in turn -are considered part of CentOS corporate visual identity. +@file{trunk/Identity/Themes/Motifs/TreeFlower} directory as example. +It is the trunk development line of @emph{TreeFlower} artistic motif. +Artistic motifs are considered part of themes, which in turn are +considered part of CentOS corporate visual identity. When building parent directory structures, you may find that reaching an acceptable location may take some time, and as it uses to happen diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Render.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Render.texi index c4e1881..7aa7cf6 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Render.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Render.texi @@ -111,9 +111,8 @@ pre-rendition configuration scripts, and related translations files). When we duplicate directories, inside `trunk/Identity' directory structure, we need to be aware of renderable layout described above -and the source location used to perform the duplication action. - -The source location is relevant to centos-art.sh script in order to +and the source location used to perform the duplication action. The +source location is relevant to centos-art.sh script in order to determine the required auxiliar information inside directory structures that need to be copied too (otherwise we may end up with orphan directory structures unable to be rendered, due the absence of diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Svg.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Svg.texi index 280d2e4..37889d4 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Svg.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Svg.texi @@ -142,7 +142,7 @@ maintain it is not a fun task to use the graphical interface to remove unused definitions editing those files one by one. To remove unused definitions from several scalable vector graphics -files, the @file{centos-art.sh} script uses Inkscape's command-line +files, the @file{centos-art.sh} script uses Inkscape command-line interface, specifically with the @option{--vaccum-defs} option. @subsection Usage diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Verify.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Verify.texi index 7f6591f..bbf2a3c 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Verify.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions/Verify.texi @@ -44,7 +44,7 @@ following URL: @end quotation Before installing packages, the @file{centos-art.sh} script uses -@command{sudo} to request root privileges to execute @command{yum}'s +@command{sudo} to request root privileges to execute @command{yum} installation functionality. If your user isn't defined as a privileged user---at least to run @command{yum} commands--- inside @file{/etc/sudoers} configuration file, you will not be able to diff --git a/Manuals/en/Texinfo/Repository/trunk/Translations.texi b/Manuals/en/Texinfo/Repository/trunk/Translations.texi index 2717edd..2c15e69 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Translations.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Translations.texi @@ -26,7 +26,7 @@ CentOS release schema.} @item Each CentOS distribution in parallel development supports more than two hundreds locales.@footnote{This value was taken from the -@command{locale -a} command's output.} +output of @command{locale -a} command.} @end itemize In order to aliviate maintainance of artwork production for such @@ -73,12 +73,12 @@ rendered, the @command{centos-art} script remove the previous instance and takes the next file in the list of translation files to repate the whole process once again, and so on for all files in the list. This configuration is mainly used to produce translatable artworks like -Anaconda's progress slide images. +Anaconda progress slide images. To find out correspondence between translation entries and identity entries, you need to look the path of both translation entries and -identity entries. For example, if you are using the Modern's artisitic -motif, the identity entry for Anaconda progress artwork is: +identity entries. For example, if you are using the @emph{Modern} +artisitic motif, the identity entry for Anaconda progress artwork is: @verbatim trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress @@ -92,10 +92,10 @@ trunk/Translations/Identity/Themes/Distro/Anaconda/Progress Note how the @file{Translations/} directory prefixes @file{Identity/} directory, also how static values (e.g., Identity, Themes, Distro, -etc.) in the identity's entry path remain in translation's entry path, -and how variable values like theme names (e.g., Modern) are stript out -from translation's entry path. The same convenction can be applied to -other identity entries in order to determine their translation +etc.) in the identity entry path remain in translation entry path, and +how variable values like theme names (e.g., @emph{Modern}) are stript +out from translation entry path. The same convenction can be applied +to other identity entries in order to determine their translation entries, or to other translation entries to determine their identity entries. @@ -183,7 +183,7 @@ designers can work together but independently one another. @subsubsection Translation Files @cindex Translation files -Translation files are text files with @command{sed}'s commands inside, +Translation files are text files with @command{sed} commands inside, replacement commands mainly. As convenction, translation file names end in @samp{.sed}. Translation files are used by @command{centos-art} script to produce translated artworks for specific major releases of @@ -260,11 +260,11 @@ for in the @samp{--filter='release-number'} argument. Template translation files are translation files stored inside translation template directory. Template translation files are used by @command{centos-art} script to produce specific translation files -only. Template translation files may be empty or contain -@command{sed}'s replacement commands. If template translation files -are empty files, the final specifc translation file built from it -contains release-specific replacement commands only. For example, -see the following translation entry: +only. Template translation files may be empty or contain @command{sed} +replacement commands. If template translation files are empty files, +the final specifc translation file built from it contains +release-specific replacement commands only. For example, see the +following translation entry: @verbatim trunk/Translations/Identity/Themes/Distro/BootUp/Firstboot/ @@ -423,10 +423,10 @@ we use the FLAG component with the @samp{g} command to apply the replacements globally. @quotation -@strong{Tip} More information about how to use @command{sed}'s -replacement commands and flags is available in @command{sed}'s -documentation manual. To read sed's documentation manual type the -following command: +@strong{Tip} More information about how to use @command{sed} +replacement commands and flags is available in @command{sed} +documentation manual. To read @command{sed} documentation manual type +the following command: @verbatim info sed @end verbatim @@ -513,19 +513,19 @@ When the @command{centos-art} script finds a translation template directory inside translation entry, it looks for translations pre-rendering configuration scripts for that translation entry. Translation pre-rendering configuration scripts let you extend -translation's default functionality (described below). +translation default functionality (described below). Translation pre-rendering configuration scripts are stored under @file{trunk/Scripts} directory, specifically under the appropriate -language implementation. If you are using @command{centos-art} Bash's +language implementation. If you are using @command{centos-art} Bash implementation, the translation pre-rendering scripts are store in the @file{trunk/Scripts/Bash/Config} location; if you are using -@command{centos-art} Python's implementation, then translation +@command{centos-art} Python implementation, then translation pre-rendering scripts are stored in the @file{trunk/Scripts/Python/Config} location, and so on for other implementations. -Bash's translation pre-rendering configuration scripts look like the +Bash translation pre-rendering configuration scripts look like the following: @verbatim @@ -563,7 +563,7 @@ Translation pre-rendering scripts are function scripts loaded and executed when rendering a translation entry. Translation pre-rendering scripts are loaded using the translation entry being rendered as reference. For example, suppose you are using the -@command{centos-art} Bash's implementation, and you are rendering +@command{centos-art} Bash implementation, and you are rendering translations for CentOS brands, in this situation the translation entry would be: @@ -593,8 +593,8 @@ following form: render.conf.extension @end verbatim where @samp{extension} refers the programming language implementation -you are using. For example, @samp{sh} for Bash's, @samp{py} for -Python's, @samp{pl} for Perl's, and so on for other implementations. +you are using. For example, @samp{sh} for Bash, @samp{py} for Python, +@samp{pl} for Perl, and so on for other implementations. @end quotation As we are using Bash implementation to describe the translation diff --git a/Manuals/en/Texinfo/Repository/trunk/Translations/Identity/Brands.texi b/Manuals/en/Texinfo/Repository/trunk/Translations/Identity/Brands.texi index eba660d..c20a12a 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Translations/Identity/Brands.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Translations/Identity/Brands.texi @@ -56,7 +56,7 @@ templates, and translation file names are used as final image name. The final image is saved using an specific @samp{width} defined by the number part of the translation file name. The image @samp{height} is automatically scaled based on the previous @samp{width} definition to -maintain the design's ratio. +maintain the designing ratio. For example, if your design template has 400x200 pixels of dimension, and you apply a translation file named `300.sed' to it, the final diff --git a/Manuals/en/Texinfo/Repository/trunk/Translations/Identity/Fonts.texi b/Manuals/en/Texinfo/Repository/trunk/Translations/Identity/Fonts.texi index ba1e23a..2699334 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Translations/Identity/Fonts.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Translations/Identity/Fonts.texi @@ -17,12 +17,12 @@ for each font preview image you want to produce. This way, we create one translation file for each font-family we use somewhere inside CentOS visual identity. -@quotation -@strong{Important} Do not create translation files for font-families -not used somewhere inside CentOS visual identity. The font's identity -entry (@pxref{trunk Identity Fonts}) is used as reference when someone -needs to know which font-families are allowed to use inside CentOS -visual identity. +@quotation +@strong{Important} Do not create translation files for +font-families not used somewhere inside CentOS visual identity. The +identity of font entry (@pxref{trunk Identity Fonts}) is used as +reference when someone needs to know which font-families are allowed +to use inside CentOS visual identity. @end quotation @subsubsection Translation Markers