From: Jo Simoens Date: Thu, 19 May 2005 19:54:46 +0000 (+0000) Subject: thanks.tex doesn't include the French translator yet, if I'm not mistaken X-Git-Tag: Release-1.38.0~430 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=a09718c8e2099e5fbe18552964ffa4a4ff973ab5;p=bacula%2Fdocs thanks.tex doesn't include the French translator yet, if I'm not mistaken --- diff --git a/docs/manual-fr/state.tex b/docs/manual-fr/state.tex index 7e144a8b..d6dfd235 100644 --- a/docs/manual-fr/state.tex +++ b/docs/manual-fr/state.tex @@ -47,7 +47,7 @@ dernier recours. permettant un contr\^ole total. Trois versions (shell, GNOME et wxWidgets) sont disponibles. Notez que la version GNOME n'offre actuellement que peu des fonctions de la version shell. -\item Verification des fichiers pr\'ec\'edemment catalogu\'es offrant un +\item V\'erification des fichiers pr\'ec\'edemment catalogu\'es offrant un syst\`eme de d\'etection \`a la fa{\c c}on de Tripwire \item Authentification par mot de passe CRAM-MD5 entre chaque composant ({\it daemon}). @@ -58,7 +58,7 @@ fonctions de la version shell. concernant les volumes, pools, jobs et fichiers sauvegard\'es. \item Support pour des catalogues de type SQLite, PostgreSQL, et MySQL. \item Requ\`etes utilisateur arbitraires sur les bases de donn\'ees SQLite, - PostgreSQL and MySQL. + PostgreSQL et MySQL. \item Marquage (label) des Volumes pour pr\'evenir tout \'ecrasement accidentel (au moins par Bacula). \item Un nombre quelconque de Jobs et Clients peuvent \^etre sauvegard\'es sur @@ -91,7 +91,7 @@ automatique par e-mail. capable de s'interfacer avec pratiquement n'importe quel programme autochargeur. \item Support pour les librairies \'equip\'ees de lecteurs de codes barres -- - marquage (labelling) automatique selon les codes barres. + marquage (labeling) automatique selon les codes barres. \item Support pour les librairies \`a magasins multiples, soit par l'utilisation des codes barres, soit par lecture des cartouches. \item Sauvegardes/restaurations ``Raw device''. Les restaurations doivent diff --git a/docs/manual/bugs.tex b/docs/manual/bugs.tex index 1eb2b658..2235674b 100644 --- a/docs/manual/bugs.tex +++ b/docs/manual/bugs.tex @@ -10,7 +10,7 @@ Well fortunately there are not too many bugs, but thanks to Dan Langille, we have a \elink{bugs database}{http://bugs.bacula.org} where bugs are reported. -Generally, when a bug is fixed, a patch for the currently release version will +Generally, when a bug is fixed, a patch for the currently released version will be attached to the bug report. The directory {\bf patches} in the current CVS always contains a list of diff --git a/docs/manual/license.tex b/docs/manual/license.tex index 14892aa6..8c435d80 100644 --- a/docs/manual/license.tex +++ b/docs/manual/license.tex @@ -18,7 +18,7 @@ The vast bulk of the code is released under a modified version of the modifications (actually additions) are described in the source file LICENSE, and their purpose is not to alter the essential qualities of the GPL but to permit more freedom in linking certain third party software supposedly non-GPL -compatable, provide termination for Patent (and IP) actions, clarify +compatible, provide termination for Patent (and IP) actions, clarify contributors IP and Copyright claims and non-infringment intentions. The details and governing text are in the file LICENSE in the main source directory. diff --git a/docs/manual/mysql.tex b/docs/manual/mysql.tex index 7f02b2b2..8a672bd7 100644 --- a/docs/manual/mysql.tex +++ b/docs/manual/mysql.tex @@ -125,7 +125,7 @@ Now you will create the Bacula MySQL database and the tables that Bacula uses. This script creates unrestricted access rights for {\bf kern}, {\bf kelvin}, and {\bf bacula}. You may want to modify it to suit your situation. Please -note that none of these userids including root are password protected. +note that none of these userids, including root, are password protected. \item ./create\_mysql\_database @@ -175,7 +175,7 @@ that you ran. To do so, you can do the following: \normalsize Please note that all information in the database will be lost and you will be -starting from scratch. If you have written on any Volumes, you must write and +starting from scratch. If you have written on any Volumes, you must write an end of file mark on the volume so that Bacula can reuse it. Do so with: \footnotesize @@ -212,7 +212,7 @@ with the name of the mysql-directory. In my case, it is: /home/kern/mysql/lib/mysql then rebuild the loader's cache with: /sbin/ldconfig If you upgrade to a new version of {\bf MySQL}, the shared -library names will probably changes, and you must re-run the {\bf +library names will probably change, and you must re-run the {\bf /sbin/ldconfig} command so that the runtime loader can find them. Alternatively, your system my have a loader environment variable that can be diff --git a/docs/manual/postgresql.tex b/docs/manual/postgresql.tex index 48e67e6d..d5bc0847 100644 --- a/docs/manual/postgresql.tex +++ b/docs/manual/postgresql.tex @@ -130,7 +130,7 @@ that you ran. To do so, you can do the following: \normalsize Please note that all information in the database will be lost and you will be -starting from scratch. If you have written on any Volumes, you must write and +starting from scratch. If you have written on any Volumes, you must write an end of file mark on the volume so that Bacula can reuse it. Do so with: \footnotesize @@ -184,7 +184,7 @@ before proceeding with this process! perform a make install. \item Shutdown Mysql. \item Start PostgreSQL on your system. -\item Create a bacula user in Postgres with createuser command. Depending on +\item Create a bacula user in Postgres with the createuser command. Depending on your Postgres install, you may have to SU to the user who has privileges to create a user. \item Verify your pg\_hba.conf file contains sufficient permissions to allow @@ -274,5 +274,5 @@ SELECT SETVAL('pool_poolid_seq', (SELECT MAX(poolid) FROM pool)); \index[general]{Credits } \addcontentsline{toc}{subsection}{Credits} -Many thanks to Dan Languille for writing the PostgreSQL driver. This will +Many thanks to Dan Langille for writing the PostgreSQL driver. This will surely become the most popular database that Bacula supports. diff --git a/docs/manual/sqlite.tex b/docs/manual/sqlite.tex index 6ee94869..ed6d5d0c 100644 --- a/docs/manual/sqlite.tex +++ b/docs/manual/sqlite.tex @@ -115,7 +115,7 @@ that you ran. To do so, you can do the following: \normalsize Please note that all information in the database will be lost and you will be -starting from scratch. If you have written on any Volumes, you must write and +starting from scratch. If you have written on any Volumes, you must write an end of file mark on the volume so that Bacula can reuse it. Do so with: \footnotesize diff --git a/docs/manual/thanks.tex b/docs/manual/thanks.tex index bc5d94d6..c1ed19c9 100644 --- a/docs/manual/thanks.tex +++ b/docs/manual/thanks.tex @@ -9,7 +9,7 @@ Thanks to Richard Stallman for starting the Free Software movement and for bringing us gcc and all the other GNU tools as well as the GPL license. -Thanks to Linus Torvalds for bring us Linux. +Thanks to Linus Torvalds for bringing us Linux. Thanks to all the Free Software programmers. Without being able to peek at your code, and in some cases, take parts of it, this project would have been diff --git a/docs/manual/vars.tex b/docs/manual/vars.tex index eb977fe9..69fd1e45 100644 --- a/docs/manual/vars.tex +++ b/docs/manual/vars.tex @@ -27,7 +27,7 @@ character class replacement, padding strings, repeated expansion in a user controlled loop, support of arithmetic expressions in the loop start, step and end conditions, and recursive expansion. -When using varaiable expansion characters in a Volume Label Format record, the +When using variable expansion characters in a Volume Label Format record, the format should always be enclosed in double quotes ({\bf ``}). For example, {\bf \$\{HOME\}} will be replaced by your home directory as @@ -58,7 +58,7 @@ the variable name). \item [Internal Variables] \index[dir]{Internal Variables } Internal variables are read-only, and may be related to the current job (i.e. -Job name), or may be special variables such as the date and time. The +Job name), or maybe special variables such as the date and time. The following variables are available: \begin{itemize}