Re: [Cin] Latex and Manual

[Phyllis Smith]

Andrea, well "no" I will have to make changes!

On Sun, Jan 12, 2020 at 12:45 PM Andrea paz 
wrote:

> I've added the new section 5.6 and I enclose you editing.tex
> But are you sure GG will accept the title I put up? I can't believe it!
>  :-)
> --
> Cin mailing list
> Cin@lists.cinelerra-gg.org
> https://lists.cinelerra-gg.org/mailman/listinfo/cin
>
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

I've added the new section 5.6 and I enclose you editing.tex
But are you sure GG will accept the title I put up? I can't believe it!   :-)
\chapter{Editing}%
\label{cha:editing}

Editing comprises both time and track space.  The timeline consists of the time certain media appear on the track going left to right and a set of tracks from the top to the bottom.  There are 2 methods of timeline editing --- drag and drop editing, also called \textit{arrow mode}, and cut and paste editing or \textit{I-beam mode}.  Cut and Paste is the default editing mode.  An additional, but not often considered editing method is called \textit{two-screen editing} where the Viewer is used to view media and then the desired clip from the media is transferred to the timeline.

The timeline is where all editing decisions are made (figure~\ref{fig:timeline}).  This is a stack of tracks in the center of the main window.  It can be scrolled up, down, left and right with the scrollbars on the right and bottom.  It can also be scrolled up and down with a mouse wheel, or left and right while holding down the Ctrl key and using the mouse wheel.

\begin{figure}[htpb]
\centering
\includegraphics[width=0.8\linewidth]{images/timeline.png}
\caption{Timeline editing session using the upcoming Cinfinity theme.}
\label{fig:timeline}
\end{figure}

The active region is the range of time which is affected by editing commands on the timeline.  The active region is determined first by the presence of in/out points on the timeline.  If those do not exist the highlighted region is used.  If no highlighted region exists, the insertion point is used as the start of the active region.  Some commands treat all the space to the right of the insertion point as active while others treat the active length as 0 if no end point for the active region is defined.

Most importantly, editing decisions never affect source material meaning that it is non-destructive editing.  So not only does your original media stay completely untouched, it is much faster than if you had to copy all the media affected by an edit.  Editing only affects pointers to source material, so if you want to have a new modified media file at the end of your editing session which represents the editing decisions, you need to render it.  Saving and loading your edit decisions is explained in the Load, Save and the EDL section and rendering is explained in the section on Rendering.

In the following editing sections, references to common operations are scattered within any of the modes where they seem pertinent.  However, many of the editing operations work in different modes.

\section{The Patchbay}%
\label{sec:patchbay}

On the left of the timeline is a region known as the patchbay.  The patchbay enables features specific to each track as described next.


\begin{description}
\item[Textbox] for naming the track.  The default names will usually be Video \#, Audio \#, or Mixer \# if using the multi-camera/mixer operations.  A \# will be designated for subsequent tracks as in 1, 2, 3 and so on.
\item[Expander] which is a down arrow on the right side, is for viewing more options on the patchbay and for viewing the effects represented on the track.   You can just click on the expander to expand or collapse the patchbay and the track.  If it is pointing sideways, the track is collapsed.  If it is pointing down, the track is expanded.  Existing effects appear below the media for the track.
\end{description}

\noindent Below the textbox name are several toggles referred to as \textit{attributes} for different features (currently there are 5 as shown in figure~\ref{fig:patchbay01}).  If the toggle button is shadowed by a color, the feature is enabled . If the toggle is the background color of most of the window, it is disabled. Click 
on the toggle to enable/disable the feature.

\begin{wrapfigure}[15]{O}{0.3\linewidth}
\vspace{-2ex}
\centering
\includegraphics[width=0.79\linewidth]{images/patchbay01.png}
\caption{Patchbay}
\label{fig:patchbay01}
\end{wrapfigure}


Several mouse operations speed up the configuration of several tracks at a time. Click on an attribute and drag the cursor across adjacent tracks to copy the same attribute to those tracks.  Hold down Shift while clicking a track's attribute to enable the attribute in the current track and toggle the attribute in all the other tracks. Or you can:

\begin{enumerate}
\item hold down Shift while clicking an attribute,
\item click until all the tracks except the selected one are disabled,
\item then drag the cursor over the adjacent track to enable the attribute in the adjacent track.
\end{enumerate}

The \textit{attributes} are described here next.

\begin{description}
\item[Play Track] determines whether the track is rendered or not. If it is off, the track is not rendered.  For example if you turn it off in all the video tracks, the rendered media file will have only audio tracks.  If 

Re: [Cin] Latex and Manual

[Andrea paz]

GG's response to Glenn in the forum seems
(https://www.cinelerra-gg.org/forum/help-video/hotkey-to-deselect-all-groups/#post-698)
so clear and interesting to me that I propose to include it in the
latex manual:

GG on selection's method: [at the end of paragraph 5.5; as a final
summary. then becomes a new paragraph 5.6 and the following are moved
to 5.7, ... etc. I'd like to name the section: "Good Guy speaks:"]
There are several "selections" method.  First, in the olden days,
there was the column oriented timeline drag selection.  That manifests
in 1 of 3 ways.  a highlighed vertical column, a single flashing line,
or the blue line region between the [in and ]out marker labels.  When
the drag column is in use, it has the highest precedence and is used
for selection.  When the column is a single line, then the fall back
selection is the [in/out] marker region, if they are set.  When they
are not set, and the cursor is flashing, then the selection start=end
and the selection is empty, but it does have a position on the
timeline which can be used for editing.  This is input for the
vertical style cut/paste drag/drop editing.

Now, in the new "group" world, there are "edit" selections.  These are
created by using the drag/drop cursor and clicking edits to toggle
select/deselection.  These are input to a different (more modern) set
of cut/paste/overwrite drag/drop editing.  These are the set of
operations you see when you click an edit with the middle mouse
button, and are available using the hot keys which are more like text
editor, ^x=cut, ^c=copy, ^v=paste, and so on...   The delete key is
not hooked to these operations.  It is hooked to the cursor selection
region.
If there are In/Out points, they enter the selection priority queue
between the column selection and the cursor only. You can see the
region selection blue line across the timebar.  This means that when
the cursor selection is empty, the in/out selection will be used.
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

Add chapter 17.
In \todo I put two figures in which I copied your TikZ code to show
writings and arrows, but the arrows are not displayed. I added the
\caption package at Olaf's suggestion. Let me know if it's okay.
I've also put in the latest changes made by Phyllis.
https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

Add chapter 16.
Pdf at:
https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Спицын Андрей]

Thank you Andrea!

Mon, Nov 18, 2019 at 02:36:35PM +0100, Andrea paz написал:

I'm sorry: the link:
https://www.cinelerra-gg.org/bugtracker/view.php?id=77#c2466

Il giorno lun 18 nov 2019 alle ore 09:32 Andrea paz
 ha scritto:


Hi, Andrey.
Olaf has proposed changes to the structure of the Latex manual. Since
he is not a member of the mailing list, I enclose his attachments here
too.

--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin


--
Best regards, 
Andrey

--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Sergio Daniel Gomez]

Thanks!

Sergio

El 18/11/2019 a las 10:36, Andrea paz escribió:

I'm sorry: the link:
https://www.cinelerra-gg.org/bugtracker/view.php?id=77#c2466

Il giorno lun 18 nov 2019 alle ore 09:32 Andrea paz
 ha scritto:

Hi, Andrey.
Olaf has proposed changes to the structure of the Latex manual. Since
he is not a member of the mailing list, I enclose his attachments here
too.

--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

I'm sorry: the link:
https://www.cinelerra-gg.org/bugtracker/view.php?id=77#c2466

Il giorno lun 18 nov 2019 alle ore 09:32 Andrea paz
 ha scritto:
>
> Hi, Andrey.
> Olaf has proposed changes to the structure of the Latex manual. Since
> he is not a member of the mailing list, I enclose his attachments here
> too.
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

Hi, Andrey.
Olaf has proposed changes to the structure of the Latex manual. Since
he is not a member of the mailing list, I enclose his attachments here
too.
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Спицын Андрей]

@Andrey:
If I put caption and labels to the tables I get an error that I do not
understand and I do not compile the pdf.


Indeed, it's very strange error, because syntax is correct.
I'm think that the source of error is an old information in auxiliary files.
Try to delete all auxiliary and temporary files.
In Texstudio menu Tools> Clean Auxiliary files


Tue, Oct 29, 2019 at 03:55:03PM +0100, Andrea paz написал:

Added chapter 15 with large shortcut tables.
@Andrey:
If I put caption and labels to the tables I get an error that I do not
understand and I do not compile the pdf.
@All
If you have any suggestions for improving the tables please let me know.
For a preview of the pdf:
https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Phyllis Smith]

Andrea,
The table looks really good!  Later today, gg will replace the current
CinelerraGG_manual_WIP.pdf on the website with your latest.  You are
getting really close to full LaTex conversion -- I can hardly wait to get
my hands on it.  Thanks, gg/Phyllis

On Tue, Oct 29, 2019 at 8:54 AM Andrea paz 
wrote:

> Added chapter 15 with large shortcut tables.
> @Andrey:
> If I put caption and labels to the tables I get an error that I do not
> understand and I do not compile the pdf.
> @All
> If you have any suggestions for improving the tables please let me know.
> For a preview of the pdf:
> https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0
> --
> Cin mailing list
> Cin@lists.cinelerra-gg.org
> https://lists.cinelerra-gg.org/mailman/listinfo/cin
>
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

Hi, Andrey.
I continued to study the tables and in the end I came to a simplified
version but that satisfies me. I would like your opinion and
suggestions. I have privileged the practical side of reading over the
aesthetics. When I have finished entering the data I will provide the
sample pdf, so that everyone can give suggestions to improve the
aesthetics. For now I leave this scheme if it suits you.


\begin{center}
\small
\begin{longtable}{ >{\bfseries}c l l p{6cm}}
%\caption{Main menu pulldowns}
%\label{tabular:main_menu} \\
\toprule
\multirow{2}*{MAIN} & 01/19/2019 & update & \\
\noalign{\smallskip}
\cline{2-4}
\noalign{\smallskip}
(Pulldowns) & ITEMS & SHORTCUTS & DESCRIPTION\\
\hline
\hline
\endhead  % here the common page header

File & x1 & yy1 & z1 \\
 \midrule
 & x2 & yy2 & z2 \\
 \midrule
 & x3 & yy3 & z3 \\

\bottomrule

\end{longtable}
\end{center}
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Phyllis Smith]

Marco:

> I am a lurker in this ml, I am sorry, I also am not really a cinelerra
> user but I do like _very much_ the project, the spirit, the people.
>
Lurkers are welcome! and it is nice to get more opinions from outside who
have experience in different areas.

I am sorry but I do not think that Latex is really a good language to write
> docs apart from math books. ...

I mean that now there are better laguages that permits to write docs in
> ...
> One of my favourite is asciidoc.
>
I see that asciidoc is text format.  That for me, personally, is the number
1 reason for using any document writing tool.  It has to be in text format
so that only the actual changes can be checked into GIT (like github does)
without checking in a whole bunch of stuff -- that was the major problem
with using the original .odt format. So Latex fits and exists just about
everywhere.  You may be right that other tools would fit even better. As
there is a lot of work to get a good document completed and to keep it
updated, the current set of people doing the work have to be happy with
which tool is being used and I have to be able to change it continuously as
the developer changes stuff so frequently.  I think I can learn to use
Latex most easily because of my background.

The MAJOR GOAL right now is to get the document in a correct and current
state, and as .odt, it was not easily fixed.  Once in Latex there is still
a lot of work to get it updated to actually match the software.  If in the
future, other considerations come into play, it sounds like it could be
switched over if needed.

>
> I know a joke about UDP, but you might not get it.

 To steal someone's quote from the internet, "The problem with UDP jokes is
that I don't get half of them!"
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

> It's OK if I'll paste it in mail message, not in repo?

Yeah, all right. All the examples and writings that you put in the old
emails I kept them for study.
I'll try the latex script first, and only for the data.
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Спицын Андрей]

Hi Marco,

We have a discussion about markdown, and other markup languages in
bugtracker https://www.cinelerra-gg.org/bugtracker/view.php?id=77
Asciidoc, markdown and other Lightweight markup language(LML) has advantages
and disadvantages. The advantages you already mentioned is
convertibility into html and into other formats.
Syntax IMHO is a mater of taste. 
The disadvantages of LML is a continuation of it advantages, 
LML has a lack of control of output format.

To produce a good pdf from Asciidoc, you have to fine tune the standard latex 
template and entire document,
because Asciidoc and other LMLs use latex to convert into pdf.  No Tikz drawing 
support.
Sometime a conversion goes wrong, see attached file.
And so on. LMLs produce a much simpler documents even with a latex
support. 


LaTeX has much more power to do with pdf format, and because of that
produce nice looking pdfs, that looks like a real book.
And it's goes closer to some kind of art, see 
https://github.com/jemmybutton/byrne-euclid



Anyway when I have some spare time I can try to convert all 600 pages of
docs in asciidoc to see how it comes out...


I don't know can I speak for a whole community, but we are welcome any help.
It would be nice to have ability to convert latex manual into asciidoc.

Best regards,
Andrey
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

More notes:
I deleted the first image from the original chapter 13 because it
didn't seem necessary to me. Instead, the image of the Recording tab
with the "realtime TOC" button active (paragraph 13.2.6 original), is
of insufficient resolution, but I can not replicate it because I do
not appear the check button. Maybe because I don't own a DVB card? Can
you provide me with a higher resolution version?
The temporary pdf can be found at the usual link:
https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

I'm sorry, my fault. It' ok now.
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Спицын Андрей]

Hi Andrea,

I have added chapters 12 and 13. I have taken the initiative of
splitting the original chapter 13 into two new chapters (12 and 13,

I have an error:
File `images/preset01.png' not found
Is it preset.png file?


--
Best regards,
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

Hi,
I have added chapters 12 and 13. I have taken the initiative of
splitting the original chapter 13 into two new chapters (12 and 13,
precisely), because I consider them huge and autonomous.
Phyllis, if you prefer a single chapter, with Latex it is very simple
and fast to reunite them.
In the DVD/BD chapter there are three references to 8.3.4 and 8.3.5,
but I don't understand what they mean.
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Спицын Андрей]

Hi Andrea,
I put references to corresponding chapters and done a quick fix for the
lines that goes beyond right page border.
All changes already in my repo.

--
Best regards

Fri, Sep 27, 2019 at 04:26:33PM +0200, Andrea paz написал:

About compositing_pipeline_masks you're completely right. I put it in
its place (mask section) and apologize (same dropbox link).
As for the section on the mask tool, I think it needs to be rewritten
to incorporate the latest news. Phyllis, could you get me the odt?
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin


--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

About compositing_pipeline_masks you're completely right. I put it in
its place (mask section) and apologize (same dropbox link).
As for the section on the mask tool, I think it needs to be rewritten
to incorporate the latest news. Phyllis, could you get me the odt?
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Спицын Андрей]

- I had to force the pdf because they are present in ".gitignore". Did

You have done absolutely right to force pdf images.
Add following line to .gitignore to allow pdf in images folder.

!/images/*.pdf


I take this opportunity to clarify how I insert the images: I use 144
Dpi PNG because, in my opinion, they are the minimum acceptable
quality. By minimum quality I mean: being able to easily read the
smallest text on the screen. If we make a version for printing we will
have to replace all the images. I propose to postpone this work until
I'm think its fine for now.  
You can add a high dpi version of images in separate folder, for ex.
./imagesHQ/ 
In settings file we can switch folders used for a manual compilation.

There is a many methods in latex to do it almost automatically.



Thu, Sep 26, 2019 at 08:10:22PM +0200, Andrea paz написал:

- Changed \geometry(right=3.0cm). Thanks, Andrey.
- I have inserted Igor's beautiful pdf in manual_latex. (Usual
address: https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0)
- I had to force the pdf because they are present in ".gitignore". Did
I do wrong?

I take this opportunity to clarify how I insert the images: I use 144
Dpi PNG because, in my opinion, they are the minimum acceptable
quality. By minimum quality I mean: being able to easily read the
smallest text on the screen. If we make a version for printing we will
have to replace all the images. I propose to postpone this work until
after the completion of the manual.
What do you think? I'm fine with any solution. And, as always, the
last word is up to Phyllis.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin


--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

- Changed \geometry(right=3.0cm). Thanks, Andrey.
- I have inserted Igor's beautiful pdf in manual_latex. (Usual
address: https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0)
- I had to force the pdf because they are present in ".gitignore". Did
I do wrong?

I take this opportunity to clarify how I insert the images: I use 144
Dpi PNG because, in my opinion, they are the minimum acceptable
quality. By minimum quality I mean: being able to easily read the
smallest text on the screen. If we make a version for printing we will
have to replace all the images. I propose to postpone this work until
after the completion of the manual.
What do you think? I'm fine with any solution. And, as always, the
last word is up to Phyllis.
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Igor BEGHETTO]

Hi Andrey!
Okay. I thought You wanted the PNGs file for the illustrations.
Here the PDFs.

@Phyllis
Thanks!


compositing_pipeline-masks.pdf
Description: Adobe PDF document


compositing_pipeline-01.pdf
Description: Adobe PDF document
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Андрей Спицын]

Hi Igor,
Please export them as a vector PDF images.
Latex can handle pdf with ease.
It's also decrease whole file size.


ср, 25 сент. 2019 г., 15:56 Igor BEGHETTO :

> Hi!
> @Phyllis and @Andea_paz
> About Pipeline images for the manual I have done that, if you want.
> Two PNGs added. They are made with Inkscape and esported to PNG @300dpi
> (dot per inch) for printing.
> If someone has already drawn them, feel free to put my PNGs in the trash.
> =)
> Thanks
>
> IgorBeg
> --
> Cin mailing list
> Cin@lists.cinelerra-gg.org
> https://lists.cinelerra-gg.org/mailman/listinfo/cin
>
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Андрей Спицын]

Hi Andrea,

About chapter ten and eleven numbering.
To fix the issue we need to change right border of page or choose a
different chapter style.
In any case we should to double-check all pages because printable area
decreases.
I prefer to change right border from 2cm to 3 cm.
It can be done in file common/settings.tex line 5
from \geometry{right=2.0cm} to \geometry{right=3.0cm}

If you want to change chapter style go to line 31 and change
\chapterstyle{madsen} to something else.

Some chapter styles are shown in
http://mirrors.ctan.org/info/latex-samples/MemoirChapStyles/MemoirChapStyles.pdf


Best regards,
Andrey



пн, 19 авг. 2019 г. в 14:33, Andrea paz :

> It works perfectly; thank you very much.
> --
> Cin mailing list
> Cin@lists.cinelerra-gg.org
> https://lists.cinelerra-gg.org/mailman/listinfo/cin
>
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

It works perfectly; thank you very much.
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Спицын Андрей]

Hi Andrea,

It's a default behavior of TeXstudio. Glossary creation is separate
process. It can be included in main compilation routine, or may not.
In my TeXstudio setup I use separate command for glossary creation.
To do so, go to Options-> Configure TeXstudio -> Commands.
Change Makeindex command to:
makeindex %.nlo  -s nomencl.ist -o %.nls 
Click Ok and go to Tools -> Commands -> Makeindex.

Hit F5 to recompile. The Glossary should be updated.

Mon, Aug 19, 2019 at 09:48:32AM +0200, Andrea paz написал:

Hi Andrey,
I wanted to add some entries in the glossary but it's not possible. I
write the new entry but then when I create the updated pdf (F5) it
does not appear. No errors are reported, simply the new entry is
ignored. With the other chapters of the manual, everything is OK. Is
that just my problem?
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin


--
С уважением,
к.т.н., доц. каф. ТЛХП, ХД и ФХ СПбГЛТУ 
Спицын Андрей Александрович

+79500166982
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Спицын Андрей]

Hi,
Here some samples for several figures, choose that you want.

% two figures and one caption
\begin{figure}[h]
\begin{minipage}[h]{0.49\linewidth}
\center{\includegraphics[width=0.5\linewidth]{image} \\ а)}
\end{minipage}
\hfill
\begin{minipage}[h]{0.49\linewidth}
\center{\includegraphics[width=0.5\linewidth]{image} \\ б)}
\end{minipage}
\caption{Corellation.}
\label{ris:image1}
\end{figure} 


%four

\begin{figure}[H]
\begin{minipage}[h]{0.47\linewidth}
\center{\includegraphics[width=1\linewidth]{image}} a) \\
\end{minipage}
\hfill
\begin{minipage}[h]{0.47\linewidth}
\center{\includegraphics[width=1\linewidth]{image}} \\b)
\end{minipage}
\vfill
\begin{minipage}[h]{0.47\linewidth}
\center{\includegraphics[width=1\linewidth]{image}} c) \\
\end{minipage}
\hfill
\begin{minipage}[h]{0.47\linewidth}
\center{\includegraphics[width=1\linewidth]{image}} d) \\
\end{minipage}
\caption{Correlation signal peaks: a) numerical experiment, b)
registered correlation signals, c) intensity distribution of 
correlation
signals in numerical experiment, d) correlation signals 
intensity
distribution for DCRAW processed data.}
\label{ris:experimentalcorrelationsignals}
\end{figure}

% Two figures with separate caption
\begin{figure}[h]
\begin{center}
\begin{minipage}[t]{0.4\linewidth}
\includegraphics[width=1\linewidth]{image}
\caption{Исходное изображение.} %% подпись к рисунку
\label{ris:experimoriginal} %% метка рисунка для ссылки 
на него
\end{minipage}
		\hfill 
		\begin{minipage}[t]{0.4\linewidth}

\includegraphics[width=1\linewidth]{image}
\caption{Закодированное изображение.}
\label{ris:experimcoded}
\end{minipage}
\end{center}
\end{figure}

% three with subfigure
% add below into preamble
\usepackage{subfigure}


\begin{figure}[ht!]  
	\vspace{-4ex} \centering \subfigure[]{
		\includegraphics[width=0.25\linewidth]{actuatorscouplingSheme_decoupledcase.eps} \label{fig:actuatorscouplingSheme_decoupledcase} }  
	\hspace{4ex}

\subfigure[]{

\includegraphics[width=0.25\linewidth]{actuatorscouplingSheme_nearestcoupledcase.eps}
 \label{fig:actuatorscouplingSheme_nearestcoupledcase} }
\hspace{4ex}
	\subfigure[]{ \includegraphics[width=0.24\linewidth]{actuatorscouplingSheme_nearestcoupled_and_diag_case.eps} \label{fig:actuatorscouplingSheme_nearestcoupled_and_diag_case} }  
	\caption{Coupling cases for the DM models: \subref{fig:actuatorscouplingSheme_decoupledcase} decoupled case; \subref{fig:actuatorscouplingSheme_nearestcoupledcase} coupling between the closest neighbours; \subref{fig:actuatorscouplingSheme_nearestcoupled_and_diag_case} coupling between the closest neighbour and diagonally adjacent actuators.} \label{fig:threeDMcases}

\end{figure}

Thu, Jul 18, 2019 at 10:39:26AM +0200, Andrea paz написал:

Added chapter 10 (only 4 pages).
I was thinking of using "subcaption" to create grids of images each
with its own caption. What do you think? Actually, I tried to put it
on, but it doesn't work for me.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin


--
С уважением,
к.т.н., доц. каф. ТЛХП, ХД и ФХ СПбГЛТУ 
Спицын Андрей Александрович

+79500166982
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Andrea paz]

Added chapter 10 (only 4 pages).
I was thinking of using "subcaption" to create grids of images each
with its own caption. What do you think? Actually, I tried to put it
on, but it doesn't work for me.
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

Re: [Cin] Latex and Manual

[Андрей Спицын]

Hi Andrea, 
Sorry for long lasting silence from me, the work and other things needs
to be done.  I finally finished with Plugins chapter. 
You done a very good job with it.
My repo is updated.
Line wrapping is a truncating text  line by some amount of characters, 
historically its 80 characters long.
I prefer a semantic line wrap by sentences.
But it's up to user to do a line brake or not.
Novice LaTeX users prefer not to use linewrap.
For a Git usage I prefer use Diff by words.

пн, 1 июл. 2019 г., 19:08 Andrea paz :

> @Olaf.
> Every month I write an email containing LaTeX and Manual in the title
> to continue the discussion and translation work with einhander. I
> installed the whole package, plus the Greek and Russian languages. Of
> course I also installed an editor, that is TexStudio.
> It would be nice if you could also contribute (in any way).
>
> "I also noticed that the lines in the TeX documents are all written
> without wrapping. When using Git and Diff, however, hard line breaks
> could be useful, short lines limited to less than 80 characters
> simplify the clarity."
>
> My knowledge of \LaTeX is very superficial and therefore I have not
> understood what you mean by wrapping the text.
> It would be nice if you could also contribute (in any way).
> -- 
> Cin mailing list
> Cin@lists.cinelerra-gg.org
> https://lists.cinelerra-gg.org/mailman/listinfo/cin
>
Hi Andrea and Olaf.@AndreaLine wrapping is a truncating text  line by some amount of characters, historically its 80 characters long.I prefer a semantic line wrap by sentences.But it's up to user to do a line brake or not.Novice LaTeX users prefer not to linewrap.For a git I prefer diff by words.пн, 1 июл. 2019 г., 19:08 Andrea paz :@Olaf.
Every month I write an email containing LaTeX and Manual in the title
to continue the discussion and translation work with einhander. I
installed the whole package, plus the Greek and Russian languages. Of
course I also installed an editor, that is TexStudio.
It would be nice if you could also contribute (in any way).

"I also noticed that the lines in the TeX documents are all written
without wrapping. When using Git and Diff, however, hard line breaks
could be useful, short lines limited to less than 80 characters
simplify the clarity."

My knowledge of \LaTeX is very superficial and therefore I have not
understood what you mean by wrapping the text.
It would be nice if you could also contribute (in any way).
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin

[Cin] Latex and Manual

[Andrea paz]

@Olaf.
Every month I write an email containing LaTeX and Manual in the title
to continue the discussion and translation work with einhander. I
installed the whole package, plus the Greek and Russian languages. Of
course I also installed an editor, that is TexStudio.
It would be nice if you could also contribute (in any way).

"I also noticed that the lines in the TeX documents are all written
without wrapping. When using Git and Diff, however, hard line breaks
could be useful, short lines limited to less than 80 characters
simplify the clarity."

My knowledge of \LaTeX is very superficial and therefore I have not
understood what you mean by wrapping the text.
It would be nice if you could also contribute (in any way).
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin