From: Good Guy Date: Thu, 16 Jan 2020 17:51:02 +0000 (-0700) Subject: some settings changes recommended by MatN X-Git-Tag: 2021-05~146 X-Git-Url: https://git.cinelerra-gg.org/git/?p=goodguy%2Fcin-manual-latex.git;a=commitdiff_plain;h=4f88cfa7939dc9b8c1a1971099c9f5a05a55853e some settings changes recommended by MatN --- diff --git a/CinelerraGG_Manual.tex b/CinelerraGG_Manual.tex index 4734406..0480dba 100644 --- a/CinelerraGG_Manual.tex +++ b/CinelerraGG_Manual.tex @@ -2,7 +2,7 @@ \documentclass[ letter, 14pt, -twoside, +oneside, openright, svgnames ]{memoir} % paper size, font size and other options for document diff --git a/common/settings.tex b/common/settings.tex index eda1094..019ea85 100644 --- a/common/settings.tex +++ b/common/settings.tex @@ -2,10 +2,10 @@ %====================== Page geometry \usepackage{geometry} % page geometry \geometry{left=2.0cm} -\geometry{right=3.0cm} +\geometry{right=2.0cm} \geometry{top=2.0cm} -\geometry{bottom=1.5cm} -\parindent=1.0cm % first indent in section +\geometry{bottom=2.0cm} +\parindent=0.0cm % first indent in section \righthyphenmin=2 % hyphen last charecter \setsecnumdepth{subsubsection} % section numration depth diff --git a/parts/Tips.tex b/parts/Tips.tex index a80ad59..64a76fd 100644 --- a/parts/Tips.tex +++ b/parts/Tips.tex @@ -169,7 +169,7 @@ Again, to measure the performance run \texttt{top} from another window to check Some mixed preliminary results that have been reported are provided below. -\subsubsection*{Case \#1:}% +\subsubsection*{Case 1:}% \label{ssub:case_1} \noindent X11 Video Driver set in \texttt{Settings $\rightarrow$ Preferences, Playback A tab}: @@ -194,7 +194,7 @@ Some mixed preliminary results that have been reported are provided below. \noindent Best is the least amount of CPU usage. Note that in this case, using X11-OpenGL is better -\subsubsection*{Case \#2:}% +\subsubsection*{Case 2:}% \label{ssub:case_2} \noindent X11 Video Driver set in \texttt{Settings $\rightarrow$ Preferences, Playback A tab}: diff --git a/parts/Translations.tex b/parts/Translations.tex index 6b063a9..352ec51 100644 --- 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