Minor fixes in text about ejabberd localization

SVN Revision: 1528

2 files changed, 17 insertions, 13 deletions

diff --git a/doc/guide.html b/doc/guide.html
index 423259337..b944bdff0 100644
--- a/doc/guide.html
+++ b/doc/guide.html
@@ -1128,7 +1128,7 @@ To define a shaper named &#X2018;<TT>normal</TT>&#X2019; with traffic speed limi
 </PRE></LI></UL><P> <A NAME="language"></A> </P><!--TOC subsection Default Language-->
 <H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc27">3.1.7</A>&#XA0;&#XA0;<A HREF="#language">Default Language</A></H3><!--SEC END --><P> <A NAME="language"></A> 
 </P><P>The option <TT>language</TT> defines the default language of server strings that
-can be seen by Jabber clients. If a Jabber client do not support
+can be seen by Jabber clients. If a Jabber client does not support
 <TT>xml:lang</TT>, the specified language is used. The default value is
 <TT>en</TT>. In order to take effect there must be a translation file
 <TT>&lt;language&gt;.msg</TT> in <TT>ejabberd</TT>&#X2019;s <TT>msgs</TT> directory.</P><P>Examples:
@@ -1137,7 +1137,7 @@ To set Russian as default language:
 <PRE CLASS="verbatim">{language, "ru"}.
 </PRE></LI><LI CLASS="li-itemize">To set Spanish as default language:
 <PRE CLASS="verbatim">{language, "es"}.
-</PRE></LI></UL><P>Translators and developers can check details in Appendix <A HREF="#i18ni10n">A</A>.</P><P> <A NAME="includeconfigfile"></A> </P><!--TOC subsection Include Additional Configuration Files-->
+</PRE></LI></UL><P>Appendix <A HREF="#i18ni10n">A</A> provides more details about internationalization and localization.</P><P> <A NAME="includeconfigfile"></A> </P><!--TOC subsection Include Additional Configuration Files-->
 <H3 CLASS="subsection"><!--SEC ANCHOR --><A NAME="htoc28">3.1.8</A>&#XA0;&#XA0;<A HREF="#includeconfigfile">Include Additional Configuration Files</A></H3><!--SEC END --><P> <A NAME="includeconfigfile"></A> 
 </P><P>The option <TT>include_config_file</TT> in a configuration file instructs <TT>ejabberd</TT> to include other configuration files immediately.</P><P>The basic usage is:
 </P><PRE CLASS="verbatim">{include_config_file, &lt;filename&gt;}.
@@ -3247,12 +3247,14 @@ There are some simple and safe examples in the article
 <A HREF="http://www.ejabberd.im/interconnect-erl-nodes">Interconnecting Erlang Nodes</A></P><P>To exit the shell, close the window or press the keys: control+c control+c.</P><P> <A NAME="i18ni10n"></A> </P><!--TOC chapter Internationalization and Localization-->
 <H1 CLASS="chapter"><!--SEC ANCHOR --><A NAME="htoc88">Appendix&#XA0;A</A>&#XA0;&#XA0;<A HREF="#i18ni10n">Internationalization and Localization</A></H1><!--SEC END --><P> <A NAME="i18ni10n"></A> 
 </P><P>The source code of <TT>ejabberd</TT> supports localization.
-The translators can edit the Gettext PO files using any capable program (KBabel, Lokalizer, Poedit...) or a simple text editor.</P><P>Then <A HREF="http://www.gnu.org/software/gettext/">Gettext</A>
-is used to extract, update and export the language files to the MSG format read by <TT>ejabberd</TT>.
+The translators can edit the 
+<A HREF="http://www.gnu.org/software/gettext/">gettext</A> .po files 
+using any capable program (KBabel, Lokalize, Poedit...) or a simple text editor.</P><P>Then gettext
+is used to extract, update and export those .po files to the .msg format read by <TT>ejabberd</TT>.
 To perform those management tasks, in the <TT>src/</TT> directory execute <TT>make translations</TT>.
 The translatable strings are extracted from source code to generate the file <TT>ejabberd.pot</TT>.
-This file is merged with each <TT>*.po</TT> language file to produce updated language files.
-Finally those <TT>*.po</TT> files are exported to <TT>*.msg</TT> files, that have a format easily readable by <TT>ejabberd</TT>.</P><P>All built-in modules support the <TT>xml:lang</TT> attribute inside IQ queries.
+This file is merged with each .po file to produce updated .po files.
+Finally those .po files are exported to .msg files, that have a format easily readable by <TT>ejabberd</TT>.</P><P>All built-in modules support the <TT>xml:lang</TT> attribute inside IQ queries.
 Figure&#XA0;<A HREF="#fig:discorus">A.1</A>, for example, shows the reply to the following query:
 </P><PRE CLASS="verbatim">&lt;iq id='5'
     to='example.org'
diff --git a/doc/guide.tex b/doc/guide.tex
index 3c0f85912..d2bb0603a 100644
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -1392,7 +1392,7 @@ Examples:
 \ind{options!language}\ind{language}
 
 The option \option{language} defines the default language of server strings that
-can be seen by \Jabber{} clients. If a \Jabber{} client do not support
+can be seen by \Jabber{} clients. If a \Jabber{} client does not support
 \option{xml:lang}, the specified language is used. The default value is
 \term{en}. In order to take effect there must be a translation file
 \term{<language>.msg} in \ejabberd{}'s \term{msgs} directory.
@@ -1409,7 +1409,7 @@ Examples:
 \end{verbatim}
 \end{itemize}
 
-Translators and developers can check details in Appendix \ref{i18ni10n}.
+Appendix \ref{i18ni10n} provides more details about internationalization and localization.
 
 
 \makesubsection{includeconfigfile}{Include Additional Configuration Files}
@@ -4267,14 +4267,16 @@ To exit the shell, close the window or press the keys: control+c control+c.
 \ind{xml:lang}\ind{internationalization}\ind{localization}\ind{i18n}\ind{l10n}
 
 The source code of \ejabberd{} supports localization.
-The translators can edit the Gettext PO files using any capable program (KBabel, Lokalizer, Poedit...) or a simple text editor.
+The translators can edit the 
+\footahref{http://www.gnu.org/software/gettext/}{gettext} .po files 
+using any capable program (KBabel, Lokalize, Poedit...) or a simple text editor.
 
-Then \footahref{http://www.gnu.org/software/gettext/}{Gettext}
-is used to extract, update and export the language files to the MSG format read by \ejabberd{}.
+Then gettext
+is used to extract, update and export those .po files to the .msg format read by \ejabberd{}.
 To perform those management tasks, in the \term{src/} directory execute \term{make translations}.
 The translatable strings are extracted from source code to generate the file \term{ejabberd.pot}.
-This file is merged with each \term{*.po} language file to produce updated language files.
-Finally those \term{*.po} files are exported to \term{*.msg} files, that have a format easily readable by \ejabberd{}.
+This file is merged with each .po file to produce updated .po files.
+Finally those .po files are exported to .msg files, that have a format easily readable by \ejabberd{}.
 
 All built-in modules support the \texttt{xml:lang} attribute inside IQ queries.
 Figure~\ref{fig:discorus}, for example, shows the reply to the following query: