Thread titleRepliesLast modified
embed youtube711:07, 1 July 2012
links to effects categories708:36, 22 June 2012
Organizing manual redaction215:43, 20 September 2011

embed youtube

Is there any markup for embedding youtube videos. The best way to demo what a video effect from kdenlive does is to have a youtube video showing the effect embeded in the page

13:58, 27 June 2012

There is no special markup for youtube videos, but just adding a link should work: try

[youtube-link description]

The description part is optional but a good idea.

21:04, 27 June 2012

But the link just displays the decription with a little globe icon right. It would be nice to actually have the video imbedded in the page like images are.

But this is usually a restriction on the Wiki software that you have in place. So I understand if this is not technically possible.

09:46, 28 June 2012

The wiki should install


09:51, 28 June 2012

Skadoosh, installed :)

12:59, 28 June 2012

Are you saying you installed the EmbdeVideo extension? Because that should mean the syntax described [here] should get me an embeded video.

But no video. How about you. Does it work for you. Needs testing/troubleshooting.

12:23, 29 June 2012

It works for me. If you still don't see the video it could be a caching issue. Try clearing your browser cache and reload.

14:35, 30 June 2012

links to effects categories

I added a link for each effect category. The pages they link to do not yet exist. I plan on creating them and using the doco at to generate doco for Kdenlive.

This addition stuffed the number of the subsequent sections up. If someone knows how to fix that - that would be good.


11:37, 20 June 2012

Done. If you actually intended blank lines separating some entries on the list, use <br /><br /> to simulate them. After a blank line enumeration restarts.

You are making a lot of work for yourself. It's not necessary to have <translate></translate> tag pairs on each entry. Unless there is something where you need to make a point that something should be excluded from translation, it is enough to enclose large chunks, and sometimes even the whole page, in a pair of tags. Do make sure that the category markup is included though. (It's sometimes overlooked too, that screenshots may need to be localised, so shouldn't be excluded Face-smile.png )

14:29, 20 June 2012

Thanks for fixing the numbering.

The translate markup looks like it might have be auto added when you "marked the page for translation". But I will keep in mind that I can put translate around alot of markup.

09:38, 21 June 2012

The tag numbering is done automatically, yes. Basically a new numbered tag is added whenever an empty line is found. You should never add tags. If you remove <translate></translate> tag pairs, leaving only one at the top and one oat the bottom it should not affect the section numbering. What it does do is show whole messages to the translators, whereas being precise in putting pairs in often ends up with translators seeing only a phrase without context. In some languages that makes a great deal of difficulty. To some extent this is an art rather than a science - thinking of how translators will see it.

10:45, 21 June 2012

In a page like this, we usually add <translate></translate> around individual items in lists. The reason is, that we want each bullet to appear in a separate translation unit, but adding blank lines between them would restart the list, which gives ugly results.

Did you intend the new subitems to not be translated?

15:38, 21 June 2012

Sorry, I think I am adding to confusion. Claus, take over and explain more clearly what works and what doesn't :-)

16:39, 21 June 2012

No. I did not intend the bits to not be translated. I was just kinda following your advice. But I think I get it now. Individual tags are probably good on this sort of thing. But on a big page on one topic - a single pair of tags is good

21:37, 21 June 2012

Organizing manual redaction

I would be ready to go on with other manual sections, but then the original version need to be also rewritten (merging info from kdenlive site, wikibook, and new updates). Who else is invloved in new manual writing ?

So far jb and me, as here (Missing people please add yourself.) I'd be very glad to have more people working on the manual. Especially the web page version is very outdated, and I fear that big parts could not even be re-used. Which section(s) would you start with?

I think I will just go on from start linearly ? Or if you prefer me to focus on something else...

09:31, 19 September 2011

The Kdenlive/Manual/xxxx is your section, you make the decisions, and we help as we can :-) From my PoV, it would be helpful if you looked at the index page, Kdenlive/Manual, and fix the redlinks - even if it means simply creating a page with ToDo on it. You will then need a DPL query on your user page to list those pages, making it easier to find them Face-smile.png I'll try to sort out the correct query today, and add it here, for you to experiment.

Once we have sorted that, tell me whether you want me to start marking up for translation.

09:44, 20 September 2011

I've pasted the query at the top of this page. It is showing the test page I made, so I think you will find it works OK. It's dynamic, so apart from refreshing the page from time to time you don't need to do anything with it. HTH.

15:43, 20 September 2011

This page was last edited on 20 June 2012, at 14:19. Content is available under Creative Commons License SA 4.0 unless otherwise noted.