|Kdenlive/Manual/Effects/Alpha manipulation/Blue Screen||Kdenlive/Manual/Effects/Alpha manipulation/Color Selection||Kdenlive/Manual/Effects/Blur and hide/Auto Mask|
|Kdenlive/Manual/Effects/Crop and transform/Rotate and Shear||Kdenlive/Manual/Effects And Transitions||Kdenlive/Manual/Full Luma|
|Kdenlive/Manual/Introduction||Kdenlive/Manual/Project Menu/Render||Kdenlive/Manual/Projects and Files/Clips|
|Kdenlive/Manual/Projects and Files/Project Settings||Kdenlive/Manual/Timeline/Right Click Menu||Kdenlive/Manual/Titles|
|Kdenlive/Manual/ToDo||Kdenlive/Manual/View Menu/Project Notes|
|Thread title||Replies||Last modified|
|embed youtube||7||11:07, 1 July 2012|
|links to effects categories||7||08:36, 22 June 2012|
|Organizing manual redaction||2||15:43, 20 September 2011|
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
There is no special markup for youtube videos, but just adding a link should work: try
The description part is optional but a good idea.
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.
The userbase.kde.org wiki should install https://github.com/Whiteknight/mediawiki-embedvideo/wiki/
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.
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 http://www.mltframework.org/bin/view/MLT/PluginsFilters 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.
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 )
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.
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.
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?
Sorry, I think I am adding to confusion. Claus, take over and explain more clearly what works and what doesn't :-)
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
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 http://userbase.kde.org/Kdenlive/Manual/Credits_and_License (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...
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 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.