Re: [PATCH] Cinelerra paste and load with "align cursor to frame" will do paste so..

> the only time "autotrimming" should come into play is when dragging
> _media_files_ from asset window (or in asset window rightclick+paste) or
> when loading _media_files_ directly into timeline. this way you have no
> problems with loading XMLs whatsoever.
>   
done and now in SVN..
Please test, and make packages after possibl bugs have settled..

Re: [CINELERRA-CV MANUAL] Licensing issues solved

nicholas,

this is fantastic. thank you very very much. i am mostly a dumb user,
so this piece of information is really very highly appreciated already now.
i am working on a school kids violin performance documentation in cinelerra.

when trying to duplex-print your pdf, i stumbled over one minor issue
concerning the order of pages: left pages should be even-numbered.
(i am also a very pedantic user as you see, german as you might guess  )

thanks anyhow. accessible documentation is as important as working code.
so if you'd like, i could at least report suggestions while reading.
cheers, georg

p.s. as european citizen, i prefer british english before american.
however as HV is probably us-based... should we vote?

--

-- 
dr.k.g.hooss
schoepfung & wandel wissenschaftliche medienberatung
breite strasse 6-8, d-23617 luebeck
www.schoepfung-und-wandel.de

Re: [CINELERRA-CV MANUAL] Licensing issues solved

Georg,

I appreciate your comments.

Your remark about duplex printing is important. I did not think about
that, and I made another version that should satisfy
you:
http://www.europephoto.com/info/cinelerra/200610/20061031_CinelerraCV_Manual/cinelerra_duplex.pdf 

That version is for printing only. The other pdf is better for viewing
on a computer.

A few lines need to be added in the texinfo file to get that result. I
will leave them -commented out- in the file. That way, people will be
able to generate a manual for duplex printing by uncommenting those
lines.

As regards to the American vs. Britain English, the original manual is
in American English, since Heroine Virtual Ltd is located in the US.
What's the opinion of English speaking people? Which English should we
use? Any other opinion?

Nicolas.

On Wed, Nov 01, 2006 at 11:39:57AM +0100, Kurt Georg Hooss wrote:
> 
> nicholas,
> 
> this is fantastic. thank you very very much. i am mostly a dumb user,
> so this piece of information is really very highly appreciated already now.

Re: [CINELERRA-CV MANUAL] Licensing issues solved

On Tue, 2006-10-31 at 22:06 +0100, Nicolas Maufrais wrote:

> We could now start collaborating on the manual. To do so we have to be
> able to share our work, that is why we need SVN accounts for people
> working on the documentation. At the beginning, there will be a lot of
> revisions on the manual, and we don't want to commit our changes
> everyday into the "main" SVN branch. Isn't it possible to set up a
> documentation-specific SVN branch? 

Why not using some of distributed version control systems (i use darcs,
but git, bzr, mercury are also, afaik, in the same category) where
patches can be easily distributed amongs doc-contributors before
applying them to (most probably) central svn server?

I recommend usage of Tailor (http://progetti.arstecnica.it/tailor) which
enables everyone to use his/her preferred vcs and exchange with others'
systems.

> That way, we would commit our work into that branch, and commit major
>  changes less often into the official SVN branch. When there will be
>  less changes made to the manual, we could decide to merge the
>  development branch into the main SVN branch.

I also agree that separate repository for documentation would be nice,
so that all work is done there and only 'final' patch is pushed to the
main Cinelerra.

> I could create one shell script to do all of these tasks. But I don't
> think that's the way to go. I assume make should handle the process. Can
> someone help me with that issue? That would avoid me to RTFM about

Re: [CINELERRA-CV MANUAL] Licensing issues solved

Gour,

On Wed, Nov 01, 2006 at 10:56:00PM +0100, Gour wrote:
> On Tue, 2006-10-31 at 22:06 +0100, Nicolas Maufrais wrote:
> > We could now start collaborating on the manual. To do so we have to be
> > able to share our work, that is why we need SVN accounts for people
> > working on the documentation. At the beginning, there will be a lot of
> > revisions on the manual, and we don't want to commit our changes
> > everyday into the "main" SVN branch. Isn't it possible to set up a
> > documentation-specific SVN branch? 
> 
> Why not using some of distributed version control systems (i use darcs,
> but git, bzr, mercury are also, afaik, in the same category) where
> patches can be easily distributed amongs doc-contributors before
> applying them to (most probably) central svn server?

Pmdumuid suggested using git too. If people using git think that RCS
fills our need, I'm ok to use it. For the moment, I don't know a lot
about git. Cehteh could probably help us on that subject. I'll RTFM
about git.

> I recommend usage of Tailor (http://progetti.arstecnica.it/tailor) which
> enables everyone to use his/her preferred vcs and exchange with others'
> systems.
> 
> > That way, we would commit our work into that branch, and commit major
> >  changes less often into the official SVN branch. When there will be
> >  less changes made to the manual, we could decide to merge the
> >  development branch into the main SVN branch.
> 

Re: [CINELERRA-CV MANUAL] Licensing issues solved

> Could any English speaking people tell us what's the best choice?
I am an english speaking person from Australia and despite the strong 
political ties with America, Australia uses British English, and Metric 
measurements...  So I prefer British English, but ... given that HW 
works in the San Francisco Bay Area (see 
http://www.heroinewarrior.com/donate.php3) and our desire is that they 
take as much of our version into their version as possible, (so that 
merging is easier), I suggest that we go with American English.

Surely there's a regexp script that converts American to British 
anyhow.. isn't it just the word replacements (such as organise -> organize)?
**
 (Actually I just took a read of 
http://en.wikipedia.org/wiki/American_and_British_English_differences 
and realise there's more to it!!)

Or we could use: http://www.translatebritish.com/

Re: [CINELERRA-CV MANUAL] Licensing issues solved

On Thu, 2 Nov 2006, Nicolas wrote:

> Could any English speaking people tell us what's the best choice?

Everyone knows that colour is better than color. It is done for one
pathetic dyslexic president. So I suggest through in stead of thru.

British has my preference.

Stefan

Re: [CINELERRA-CV MANUAL] Licensing issues solved

Re: [CINELERRA-CV MANUAL] Licensing issues solved

On Tue, 2006-10-31 at 22:06 +0100, Nicolas Maufrais wrote:

> Some changes must be done in the shell scripts used to compile
> Cinelerra-CV, in order to generate the .pdf and .html manuals
> automatically. There are few dependencies to add (imagemagick to convert
> the images, texinfo to generate the manuals), and only a few commands
> have to be ran to generate the manuals:

Do we want to add more deps to Cinelerra build process or we can just
ship produced pdf manual along with the html one from the doc branch?

I am thinking that we won't immediately update manual with the every
revision number, but, let's say, periodically when tagging some bigger
release like e.g. 2.1-merge, quarterly...and therefore it is, imho,
better to just have ready manual in doc/ which clearly states for which
revision it is up to date.

In such situation, there would not be need for adding additional
dependencies.

What do you think?

> 1 - Ensure texinfo and imagemagick are installed on the system
> 2 - Convert the .png images in hvirtual/doc to .pdf files in the same
>     directory
>     for a in *.png; do convert $a `echo $a | sed "+s+.png+.pdf+g"`; done
> 3 - Generate the HTML manual in hvirtual/doc
>     texi2html --nosec-nav cinelerra.texi
> 4 - Create the /usr/share/doc/cinelerra directory if it doesn't exist
> 5 - Delete everything in /usr/share/doc/cinelerra
> 6 - Copy hvirtual/doc/cinelerra.html and hvirtual/doc/*.png to
>     /usr/share/doc/cinelerra
> 7 - Generate the PDF manual in hvirtual/doc
>     texi2pdf -q --pdf cinelerra.texi
> 8 - Copy hvirtual/doc/cinelerra.pdf to /usr/share/doc/cinelerra
> 
> I could create one shell script to do all of these tasks. But I don't
> think that's the way to go. I assume make should handle the process. Can
> someone help me with that issue? That would avoid me to RTFM about
> makefiles, and I could concentrate my efforts on working on the manual's
> contents.

This can be done with autoconf tools. Can you give me url where I can
get manual's tarball?

> BTW, should we use American English, or Great-Britain English in the
> manual? What's your opinion?

As I already said - no preference here and probably non-native
contributors (at least myself) will probably mix 'em somewhat, so this
is, anyway, job for native editor 

Sincerely,
Gour

Re: [CINELERRA-CV MANUAL] Licensing issues solved

> Do we want to add more deps to Cinelerra build process or we can just
> ship produced pdf manual along with the html one from the doc branch?
>
> I am thinking that we won't immediately update manual with the every
> revision number, but, let's say, periodically when tagging some bigger
> release like e.g. 2.1-merge, quarterly...and therefore it is, imho,
> better to just have ready manual in doc/ which clearly states for which
> revision it is up to date.
>
> In such situation, there would not be need for adding additional
> dependencies.
>
> What do you think?
>   
I'd prefer to have a configure option
configure --makedocumentation

so dependencies depend on your configure arguments.