Hi, I have installed TexStudio + TexLive. It had 12 groups to install, I put everything except "games" and "music". Do I have to put these on too? Then I added the package for the extra language, not putting Chinese, Korean, greeks, etc.. I downloaded your main report with git clone, opened it with TexStudio and compiled the pdf; but it doesn't work and I have the following errors: line 104: Package fontenc Error: Encoding file `t2aenc.def' not found. \ProcessOptions* line 105: Encoding scheme `T2A' unknown. \fontencoding\encodingdefault line 104: Package fontenc Error: Encoding file `t2aenc.def' not found. \ProcessOptions* line 20: File `mathtext.sty' not found. \usepackage If necessary, I can provide the entire log. [Note: (I don't know if you need it) Automatically TexStudio was in Italian; I put it in English. When I opened CinelerraGG_Manual.tex, I saw that it was set in German. I put it in English]

Yes, it plays. Thank you. No problem with "mathtext.sty" now.

Hi Andrea,

Now how to submit it to your review?

The simple way it's just to mail me tex and images files. But it's not convenient in long term usage. The better way is use git. It designed to exchange only a changes between files, so it's suite perfectly for your internet speed. To use git you should: 1. Create private and public ssh keys (if didn't do that). Run ssh-keygen in terminal. It will create files is_rsa and id_rsa.pub in ~/.ssh/ folder. It's up to you add password protection to key or not. Passwordless key is less secure, but more convenient. 2. Register at github.com and add your public key (id_rsa.pub) in that page https://github.com/settings/keys 3. Fork my repo (https://github.com/einhander/cin-manual-latex) by clicking "Fork" button. 4. Clone your own fork of repo to a local folder ( git clone [email protected]:YOUR_NAME/cin-manual-latex.git) 5. Add your changes in your local repo. 6. Add new files to git repo ( git add FILENAME), repeat this step for all new files. 7. Commit your modifications to a local repo ( git commit -a -m "Brief info about changes") 8. Push local changes into your github repo ( git push) 9. Repeat step 6 and 7 then needed. And step 8 to share your changes to your github repo. It's a brief instruction how to use git. In github you can propose pull request to my repo by clicking new pull request in my repo. Or just write me then you are done and I create pull request. I'm not so experienced git user, but I'll try to answer your questions about git.

- How do you make the width of the caption coincide with the width of the figure? (see figure 3.1).

Use \captionsetup{width=YOUR_WIDTH} inside figure enviroment before caption to adjust caption width.

- Page 67. The second paragraph, "color model", is preceded by an empty line and I do not understand why. This does not happen with the other paragraphs.

I need a chapter file to investigate this.

Note: in the attributes.odt file, fig 3.2 had text on its left. I tried to do it with \begin{wrapfigure}, but I didn't like the result. So I went back to the usual way.

It's up to you, to choose the best look)) Wed, May 08, 2019 at 03:51:25PM +0200, Andrea paz написал:

Hi, @Phyllis. I think it is best not to waste time converting all images into high quality png. It's a job you can do as you convert chapters to Latex. @einhander. I have finished chapter 4 of the manual (3, in the conversion to Latex). Now how to submit it to your review? I'm not familiar with git or other systems, I'd need detailed explanations. A big problem is my internet connection which uploads no more than ~50KB/s. For a few tens of MB it takes me a whole day. Now for a few questions: - How do you make the width of the caption coincide with the width of the figure? (see figure 3.1). - Page 67. The second paragraph, "color model", is preceded by an empty line and I do not understand why. This does not happen with the other paragraphs.

Note: in the attributes.odt file, fig 3.2 had text on its left. I tried to do it with \begin{wrapfigure}, but I didn't like the result. So I went back to the usual way. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin

Hi, Great job! I changed plain text formatting to described list for Audio attributes and Video attributes section. I used nested described list for the color model. I hope you like it. Also I used small space between digits and units.

1. Do I occasionally have to update my fork of your repository or does it happen automatically? How do I do it? 2. I don't understand what "pull requests" are and how to do them. (I guess that's the answer to question 1).

You are right pull requests it's a way to sync ours repos. Then you create pull requests in my repository it's like to say to me that you did some additions to my version of manual and ask me to review these changes. Pull requests based on "merge" of "branches" mechanism in git. Code versions stored in so called "branches". Branches used then you want to create new feature in product and want to keep old stable version. Good how-to about branches in git located at: https://nvie.com/posts/a-successful-git-branching-model/ So in short to transfer my changes into your repository, you have to crate pull requests in your repository, a select base repository Andrea-Paz/cin-manual-latex and head repository einhander/cin-manual-latex and click Create Pull request. Pay attention to green label "Able to merge. These branches can be automatically merged." After you write title of Pull requests and comment Pull Request will be completed. Click accept to actually transfer changes into your github repo. Execute "git pull" in local repository to download all changes from github into your local repository. Alternatively you can create local branch that tracks changes in my repository. To add remote branch called einhander: git remote add einhander [email protected]:einhander/cin-manual-latex.git to switch into remote branch: git checkout remotes/einhander/master To create local branch from current remote: git checkout -b einhander To set bind local and remote branch to use git pull git branch --set-upstream-to=einhander/master einhander Now you have a local branch that tracks my repo. To update it switch to that branch: git checkout einhander git pull To merge all changes into your repository Switch into main master: git checkout master git merge einhander I hope that I write it correctly. The second way is the only way to work with other git hostings without web GUI.

Hi,

Great! I'll use it too. small space = \, is it right? Yes, you are right. There is more rules to follow, --- it's long dash (em dash) used between words -- it's medium dash used in digit range

There is more rules, but I don't remember them.

Adding a branch of your git from terminal does not work. Some commands give error

If pull request works correctly, we can do it later.

Hi, Great job!

This part is a little more complicated, so I've made less-than-optimal decisions. For example: - I used "source code listing", I think improperly. But I don't know how to do it better.

No, you are absolutely right that used source code listing. I added the descriptions to it.

- Between page 94 and 95, figure 4.6 slipped forward after the beginning of the next section. I don't like it very much, but I don't know what to do. I'm filing that I can't get you right. Are figure 4.6 placed after the start of new section? In my pdf it's placed before the new section.

I put all file path and names in \texttt{} to visually separate them. And added two subsections for file list and image2ffmpeg. Also I increased width of some figures because text was to small on them. Also I modified Introduction.tex to add references to new chapters.

I have error to upload new files in git (git push). See append file. Now, upload is OK. I apologize for the delay and the problems.

Hi, I'm sorry for my disappearance, a lot of work lately. About your questions.

- "Wrapfigures" have too much white space on the sides, but I don't know how to fix it. (instead of vertical spaces I know how to change them). I see that you are using wrapfloat environment, but it's leave much space behind it. So I suggest using wrapfigure environment with optional parameters like this:

\begin{wrapfigure}[16]{O}{0.3\linewidth} % | | |____ width of block for figure % | |_________ placement (can be r,l - right or left; O,I - outside or inside in booklike document % |_____________ vertical length of block for figures (in lines) \vspace{-1ex} % change here for vertical alignment of figure, % values can be negative, to reduce space above % figure. \centering \includegraphics[width=0.9\linewidth]{images/cut.png} % |___ width of figure relative to block % width. You can use an absolute values % cm,mm but it's unflexible then you change page size of format. ... \end{wrapfigure}

- I can't create trim and shuttle tables. (sec. 5.7.5 and 5.8.3). I get bad results.

I tried to create the table for section 5.7.5 but I don't like the result very much. Do you have any advice?

There is already colorful figure for this. I'm think it's better than a table It's better to ask Phyllis or GG that should be used here.

- Put a subtitle to a section (5.8). I used "footnotesize" because I don't know the right way. I used \footnote here (see my code).

- When using "\begin{lstlisting}" can you make the lines end with the code instead of continuing to the edge? I'm think it's impossible or I don't know how to do it.

I also tried with tables for section 5.8.3 but you need the package "sidewaystable" to rotate the table and I do not know if you should add it and how to do it. I left the code that uses sidewaystable to show you, but so produces error, of course. It also gives me error for the caption of the table and I do not understand why.

You can use any packages from TexLive distribution. Simply add a line contains \usepackage{NAME} in common/packages.tex file. The package name for sidewaystable is rotating. But instead of use sidewaystable I prefer to use landscape environment. It creates landscape page just like sidewaystable doi, but text placed horizontally to reader (page is rotated initially). The captions can be used on defined types of environments, figures, tables, longtables and so on. Sidewaystable isn't a table so caption does not work. Sidewaystable is like rotated box for table. I've made some edits to your previous version, please mail me then you are done with this chapter so I can merge the two versions.

I will look at that again and see if I can find something better. Or maybe I should make a png instead? What do you think? Phyllis

No, I think to leave the table because it contains more information than the colored image (as the trim was encoded in CinGG). The rendering is not beautiful but not even unsightly. See image of the page with the table, so you can get an idea. We could talk about it later. https://i.postimg.cc/nryVVmxn/trim.jpg The Shuttle tables are not finished yet, but they are coming well, so they are not a problem.

glossary would be nice.

LaTeX has special package for glossary creation. Texstudio should be reconfigured to use that package. I will add an example, and instruction for texstudio.

Hi,

uploaded to github my latest revision of chapter 5 (now it is complete). I'm starting to merge my changes into your version.

- Same Caption error Place caption inside longtable environment or table environment (in case of float table). Note table environment creates only a box for table, table itself creates tabular environment like figure is a box for \includeimage command.

- How to colorize (red) some words inside the tables of the Shuttle? To colorize some text you should use a \color command like this: {\color{red} SOME TEXT }

Hi,

Added chapter 6. Great!

I uploaded my version of Chapter 5 into GH repo. If you finished with Chapter 6, then I will start editing it. I noticed that you are using \noindent. That the purpose of use it? If you want to not break a paragraph, then just remove empty line before \end{figure} and following text. If you want to remove indent after chapter heading then it must done a globally for a whole document. It can be done by a package. I can do it if needed.

Hi, I'm finished with review of your chapters and added them into my repo. I also add a todo package to write nice looking todo. Now we have lists of tables, figures and todos. About glossary. I added a glossary package and test item. To use the glossary, you have to create custom command in texstudio. In brief, go to the preferences and add custom command or edit the existing for glossary. The command: makeindex %.nlo -s nomencl.ist -o %.nls It detailed here: https://tex.stackexchange.com/questions/161304/makeindex-no-nls-file/161381#... Remember to use the newly created glossary command after you add a new word in your glossary, and recompile. Feel free to ask me about a commands or preferences in texstudio.

Hi Andrea,

Your last commit has conflicting merge. See <<<<<<<< lines in .tex files. We have to deal with it manually. I've made my changes based on your version. I can sync our versions again based on your version.

No, don't merge my branch into yours. I could no longer sync your repository with a pull request on the web. I think I managed to do it with the terminal following your instructions (there was no "git fetch" to be able to continue). Now I'm in sync with you, but by opening "CinelerraGG_Manual.tex" I get a lot of errors and I don't compile the pdf. I've definitely made a mistake, but I don't know where. In any case your repository should be correct, the problem is mine (I think), so don't merge. I try to make corrections manually, and then I'll let you know.

I've synchronized my repo with yours, both locally and on the web. Now I start working on chapter 8. I apologize for the problems I have created (and still don't understand). I hope they don't happen again. Il giorno lun 27 mag 2019 alle ore 15:54 Andrea paz <[email protected]> ha scritto:

It seems to me to have mixed "push" with "pull" of the various branches, with the result of having double code in the various "*.tex" (For example, there are both the "verbatim" and the "longtable" of the trim.). Perhaps the best thing is to delete the last commits and start again from what you did yesterday, when you inserted and revised chapters 6 and 7. Can you do it? And what am I supposed to do? Unfortunately, I can't figure out where I'm going wrong. Can you check my branch to find out what's wrong? Do you need information?

Hi Andrea,

On page 91 (105) of the pdf, the wrapfigure narrows the text for 3-4 consecutive pages, instead of returning to normal width after the figure. Is there anything I can do? I can't.

The fix is in my repo. It's wrapfigure feature, it create box in lists environments and not always correctly. The best that I can do is manually close environment and start it again with proper numeration. In case of description environment it's really easy. I don't know any other ways to correct that behavior.

Hi einhander. Add chapter 8. The glossary odt has many entries and long descriptions (good work Phyllis!). Can you make a separate file to include as you do with chapters, instead of searching for words in the text and entering the relevant entry just below? And if you can do so, you can enter multiple entries and only last give the command MakeIndex and then compile the pdf? or you have to do away with for single entry added?

Add glossary.

Good job! I've made small changes in chapter 8 (approx. 1 line) and pushed into my repo.