some settings changes recommended by MatN

[goodguy/cin-manual-latex.git] / parts / Translations.tex

diff --git a/parts/Translations.tex b/parts/Translations.tex
index 6b063a9882c42689e073c1318109390a1c9912cd..352ec51f322ef2cb578380ece58e9596245b1abc 100644 (file)
--- a/parts/Translations.tex
+++ b/parts/Translations.tex
@@ -5,7 +5,7 @@ There are several \textit{po} files for various languages to make Cinelerra more
 
 Because Cinelerra frequently is changin, it is a good idea to start by building a new \texttt{cin.po} file which contains the latest messages/words in English to be translated, along with a comment line of the routine name and line number.  To create this, run the following line from a window:
 
-\begin{lstlisting}[language=bash]
+\begin{lstlisting}[language=bash,numbers=none]
 /{your cinelerra directory}/po/xlat.sh > /tmp/cin.po
 \end{lstlisting}
 
@@ -16,7 +16,7 @@ Because Cinelerra frequently is changin, it is a good idea to start by building
 
 To use the msgmerge command after creating a new cin.po as suggested previously:
 
-\begin{lstlisting}[language=bash]
+\begin{lstlisting}[language=bash,numbers=none]
 /{your cinelerra directory}/po/xlat.sh > /tmp/cin.po # use /tmp as a temporary place
 cp /{your cinelerra directory}/po/x.po /tmp/x.po     # substitute your language for x
 msgmerge -U /tmp/x.po /tmp/cin.po                    # x.po will be overwritten to include updates
@@ -30,7 +30,7 @@ Then use any editor or poedit to provide messages/words translations in the new
 
 To use the xlat.C program, first compile it with “c++ xlat.C”.  You can see the usage help here:
 
-\begin{lstlisting}[language=bash]
+\begin{lstlisting}[language=bash,numbers=none]
        ./a.out 
 list csv    ./a.out csv < data.csv > data.po
 list po     ./a.out po < data.po > data.csv
@@ -57,7 +57,7 @@ This program has 6 commands where the desired command is the first parameter to
 
 The xlat command line parameters specify a new cin.po template, usually created with xlat.sh, and a list of key/value files which are used to build a mapping for the desired translation.  The mapping files are added to the mapping in the order they appear on the command line, and any existing key is replaced with the newest definition; so typically the newest key/value data is last in the command parameters.  Once the mapping is built the first parameter, the new po template, is scanned and the keys it contains are used to find the latest mapping in the key/value files.  The new value replaces the existing value in the template.  For example, to overlay a new map onto an existing po:
 
-\begin{lstlisting}[language=bash]
+\begin{lstlisting}[language=bash,numbers=none]
 c++ xlat.C
 ./a.out po < xx.po > /tmp/xx.csv
 ./a.out po < new.po > /tnp/new.csv