diff --git a/Manuals/en/Html/Repository/repository_40.html b/Manuals/en/Html/Repository/repository_40.html index d694946..a70b7e7 100644 --- a/Manuals/en/Html/Repository/repository_40.html +++ b/Manuals/en/Html/Repository/repository_40.html @@ -322,9 +322,9 @@ function really works, and how it should be used. When no valid action is passed to a function, the `centos-art.sh' script uses the function documentation entry as vehicle to communicate which the valid functions are. When no documentation entry exists for a -funtcion, that user has provided an invalid action for, the -`centos-art.sh' script informs that no documentation entry exists -for such function and requests user to create it right at that time. +function, the `centos-art.sh' script informs that no +documentation entry exists for such function and requests user to +create it right at that time.

Now that we have documented our function, it is time to translate its output messages to different languages. To translate specific diff --git a/Manuals/en/Info/Repository/repository.info.bz2 b/Manuals/en/Info/Repository/repository.info.bz2 index 30e60f0..6c661bf 100644 Binary files a/Manuals/en/Info/Repository/repository.info.bz2 and b/Manuals/en/Info/Repository/repository.info.bz2 differ diff --git a/Manuals/en/Plaintext/Repository/repository.txt b/Manuals/en/Plaintext/Repository/repository.txt index d128959..39f4e2c 100644 --- a/Manuals/en/Plaintext/Repository/repository.txt +++ b/Manuals/en/Plaintext/Repository/repository.txt @@ -3046,10 +3046,9 @@ centos-art manual --edit=trunk/Scripts/Bash/Functions/Greet function really works, and how it should be used. When no valid action is passed to a function, the `centos-art.sh' script uses the function documentation entry as vehicle to communicate which the valid functions -are. When no documentation entry exists for a funtcion, that user has -provided an invalid action for, the `centos-art.sh' script informs that -no documentation entry exists for such function and requests user to -create it right at that time. +are. When no documentation entry exists for a function, the +`centos-art.sh' script informs that no documentation entry exists for +such function and requests user to create it right at that time. Now that we have documented our function, it is time to translate its output messages to different languages. To translate specific @@ -6280,24 +6279,24 @@ Index ***** branches: See 1. (line 390) -Common translation files: See 3.50.2.5. (line 5709) -How to render brands' translation files: See 3.52.3. (line 6013) -How to render fonts' translation files: See 3.54.3. (line 6086) -How to render translation files: See 3.50.3. (line 5879) -Metadata maintainance: See 3.45.2. (line 4853) -Specific translation files: See 3.50.2.6. (line 5734) +Common translation files: See 3.50.2.5. (line 5708) +How to render brands' translation files: See 3.52.3. (line 6012) +How to render fonts' translation files: See 3.54.3. (line 6085) +How to render translation files: See 3.50.3. (line 5878) +Metadata maintainance: See 3.45.2. (line 4852) +Specific translation files: See 3.50.2.6. (line 5733) tags: See 2. (line 393) -Template translation files: See 3.50.2.4. (line 5539) -Translation brands file names: See 3.52.2.1. (line 5970) -Translation configuration scripts: See 3.50.2.8. (line 5768) -Translation entries: See 3.50.2.1. (line 5355) -Translation files: See 3.50.2.3. (line 5471) -Translation markers: See 3.50.2.2. (line 5436) -Translation paths: See 3.50.2.1. (line 5355) +Template translation files: See 3.50.2.4. (line 5538) +Translation brands file names: See 3.52.2.1. (line 5969) +Translation configuration scripts: See 3.50.2.8. (line 5767) +Translation entries: See 3.50.2.1. (line 5354) +Translation files: See 3.50.2.3. (line 5470) +Translation markers: See 3.50.2.2. (line 5435) +Translation paths: See 3.50.2.1. (line 5354) Translation pre-rendering configuration scripts:See 3.50.2.8. - (line 5768) -Translation rendering: See 3.50.2.7. (line 5757) -Translation rendering default functionality: See 3.50.2.9. (line 5854) + (line 5767) +Translation rendering: See 3.50.2.7. (line 5756) +Translation rendering default functionality: See 3.50.2.9. (line 5853) trunk: See 3. (line 396) trunk Identity: See 3.1. (line 399) trunk Identity Brands: See 3.2. (line 819) @@ -6342,31 +6341,31 @@ trunk Manuals: See 3.34. (line 2579) trunk Scripts: See 3.35. (line 2633) trunk Scripts Bash: See 3.36. (line 2657) trunk Scripts Bash Functions: See 3.37. (line 2806) -trunk Scripts Bash Functions Html: See 3.38. (line 3944) -trunk Scripts Bash Functions Locale: See 3.39. (line 3965) -trunk Scripts Bash Functions Manual: See 3.40. (line 4045) -trunk Scripts Bash Functions Path: See 3.41. (line 4066) -trunk Scripts Bash Functions Render: See 3.42. (line 4468) -trunk Scripts Bash Functions Render Config: See 3.43. (line 4489) -trunk Scripts Bash Functions Shell: See 3.44. (line 4667) -trunk Scripts Bash Functions Svg: See 3.45. (line 4835) -trunk Scripts Bash Functions Verify: See 3.46. (line 5023) -trunk Scripts Bash Locale: See 3.47. (line 5239) -trunk Scripts Perl: See 3.48. (line 5268) -trunk Scripts Python: See 3.49. (line 5285) -trunk Translations: See 3.50. (line 5306) -trunk Translations Identity: See 3.51. (line 5908) -trunk Translations Identity Brands: See 3.52. (line 5929) -trunk Translations Identity Brands Tpl: See 3.53. (line 6024) -trunk Translations Identity Fonts: See 3.54. (line 6039) -trunk Translations Identity Models: See 3.55. (line 6102) -trunk Translations Identity Release: See 3.56. (line 6117) -trunk Translations Identity Themes: See 3.57. (line 6132) -trunk Translations Identity Themes Backgrounds:See 3.58. (line 6147) +trunk Scripts Bash Functions Html: See 3.38. (line 3943) +trunk Scripts Bash Functions Locale: See 3.39. (line 3964) +trunk Scripts Bash Functions Manual: See 3.40. (line 4044) +trunk Scripts Bash Functions Path: See 3.41. (line 4065) +trunk Scripts Bash Functions Render: See 3.42. (line 4467) +trunk Scripts Bash Functions Render Config: See 3.43. (line 4488) +trunk Scripts Bash Functions Shell: See 3.44. (line 4666) +trunk Scripts Bash Functions Svg: See 3.45. (line 4834) +trunk Scripts Bash Functions Verify: See 3.46. (line 5022) +trunk Scripts Bash Locale: See 3.47. (line 5238) +trunk Scripts Perl: See 3.48. (line 5267) +trunk Scripts Python: See 3.49. (line 5284) +trunk Translations: See 3.50. (line 5305) +trunk Translations Identity: See 3.51. (line 5907) +trunk Translations Identity Brands: See 3.52. (line 5928) +trunk Translations Identity Brands Tpl: See 3.53. (line 6023) +trunk Translations Identity Fonts: See 3.54. (line 6038) +trunk Translations Identity Models: See 3.55. (line 6101) +trunk Translations Identity Release: See 3.56. (line 6116) +trunk Translations Identity Themes: See 3.57. (line 6131) +trunk Translations Identity Themes Backgrounds:See 3.58. (line 6146) trunk Translations Identity Themes Distro Anaconda Progress:See 3.59. - (line 6168) -trunk Translations Identity Widgets: See 3.60. (line 6261) -Unused definitions: See 3.45.2.1. (line 4960) + (line 6167) +trunk Translations Identity Widgets: See 3.60. (line 6260) +Unused definitions: See 3.45.2.1. (line 4959) List of Figures *************** diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi index 8c4be91..7cb08db 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi @@ -258,9 +258,9 @@ function really works, and how it should be used. When no valid action is passed to a function, the @file{centos-art.sh} script uses the function documentation entry as vehicle to communicate which the valid functions are. When no documentation entry exists for a -funtcion, that user has provided an invalid action for, the -@file{centos-art.sh} script informs that no documentation entry exists -for such function and requests user to create it right at that time. +function, the @file{centos-art.sh} script informs that no +documentation entry exists for such function and requests user to +create it right at that time. Now that we have documented our function, it is time to translate its output messages to different languages. To translate specific