<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">All: </p>
<div><br>
</div>
<div>I should add that, as with the Audacity rewrite, for this new Shotcut manual I will need to ask the community if any Mac and Linux users are willing to give the install a try, to finish out the "Installation" chapter (at <a href="http://write.flossmanuals.net/introduction-to-video-editing-with-shotcut/_edit/" class="OWAAutoLink" id="LPlnk304526" previewremoved="true">http://write.flossmanuals.net/introduction-to-video-editing-with-shotcut/_edit/</a> ).
Shotcut is very lightweight, in good open-source fashion, and the Windows install was smooth and quick. It doesn't appear that there are any major gotchas for MacOS, and while the Linux install seems a bit more elaborate, to my Windows eyes, I'm sure it's
SOP for Linux installs. Moreover, I really do think Shotcut is a fantastic video editor, amazingly light-footprint for what it does; so it might even be worth keeping around unless you're deeply committed to an alternative. After doing some research I picked
it over Kden, among free open-source editors, before knowing that there a Floss Kden manual and far less Shotcut documentation around anywhere (which is why I'm writing this book). </div>
<div><br>
</div>
<div>Indeed,I would absolutely be open to people suggesting their own 'how to' chapters as well, on whatever OS, though that will need to be a separate conversation as I haven't yet figured out which how-to's I intend to do myself <span>😊, or will have time
for. I can say that my video editing literacy is still pretty basic; for example I know nothing at all about topics like color treatment, or really about half of the "Video Effects" features they list here: <a href="https://shotcut.org/features/" class="OWAAutoLink" id="LPlnk642585" previewremoved="true">https://shotcut.org/features/</a>
The shotcut team are a couple of guys who've put their energy into building a really nice open-source editor, and not at all into explaining its features in any depth. To a great extent they are relying on users to have decent prior literacy in the field.
I am hoping that someone out there has more than I do. Certainly the Kden writers, though you'd have to decide if you want to show the love for a competing editor...</span><br>
</div>
<div><span><br>
</span></div>
<div><span>Thanks,</span></div>
<div><span><br>
</span></div>
<div><span>Matt</span></div>
<div><span><br>
</span></div>
<div><span><br>
</span></div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Discuss <discuss-bounces@lists.flossmanuals.net> on behalf of M R <matrobnew@hotmail.com><br>
<b>Sent:</b> Friday, February 9, 2018 1:16 PM<br>
<b>To:</b> discuss@lists.flossmanuals.net<br>
<b>Subject:</b> Re: [FM Discuss] issues with Kdenlive manual images</font>
<div> </div>
</div>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p style="margin-top:0; margin-bottom:0">Hi All:</p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">Thanks so much for the prompt replies to my questions. Although this does leave me a dilemma. If there really is a hard limit of 600 px width for images in Booktype 1.6 (and no prospect of migration soon to 2.3), then
I guess I need to decide how much I care about the print format (or maybe PDF too?) as opposed to the html version. I've always felt that FM was most useful in it's html format, and then perhaps secondarily as an ePUB book export. So one follow-up question
for Mick is whether the width restriction applies to ePUB format as well? I'm guessing it does, based on my ePUB version of the rewritten Audacity manual. Actually, now that I look at it closely, that ePUB suffers from many of the same formatting issues as
the PDF--so I guess I won't go around showing that version to everybody <span>😊.</span></p>
<p style="margin-top:0; margin-bottom:0"><span><br>
</span></p>
<p style="margin-top:0; margin-bottom:0"><span>Meanwhile, though, Maren is correct: the restriction on image width (and resulting distortion) seems to disappear when you look at a published book in html format, or even "View Draft" of a book in progress from
the main book page, e.g. <a href="http://write.flossmanuals.net/introduction-to-video-editing-with-shotcut/_info/" class="x_OWAAutoLink" id="LPlnk660041" previewremoved="true">http://write.flossmanuals.net/introduction-to-video-editing-with-shotcut/_info/</a> in
the case of my new manual. This is interesting because the same 1366-width screenshot (see the Installing chapter) shows up distorted not just in the editor, but also when you hit "View Chapter" from within the editor, and expand that new window as much
as possible. You have to "View Draft" from the main book page to see the image properly proportioned in that chapter. Btw, Maren's Inkscape book is absolutely gorgeous, but as far as I can tell most of the images there seem to actually stay within the 600
or 700 px limit. I did that myself with the Audacity book, in order to avoid what I thought was otherwise inescapable distortion. I have tons of screenshots but I sized my Audacity window itself as small as I felt I could, practically, and then generally
just captured a particular panel or region or control area of it. I'll see to what extent that works for Shotcut too. 600 px is a pretty draconian limit for modern screenshots, though, as no one in their right might would use most of these editing tools
at that width. I get that the print version needs some kind of image width limit. One would think that the "Constrain Proportions" function would at least, you know, constrain proportions if the image exceeded that limit, and simply show a smaller overall
screenshot. But I can't get that to work in the editor: it seems to always take the actual height but constain the width. No doubt why they fixed it in 2.2...</span></p>
<p style="margin-top:0; margin-bottom:0"><span><br>
</span></p>
<p style="margin-top:0; margin-bottom:0"><span>Matt </span><br>
</p>
<br>
<br>
<div style="color:rgb(0,0,0)">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Discuss <discuss-bounces@lists.flossmanuals.net> on behalf of Daniel James <daniel.james@booktype.org><br>
<b>Sent:</b> Friday, February 9, 2018 5:41 AM<br>
<b>To:</b> mick@flossmanuals.net; discuss@lists.flossmanuals.net<br>
<b>Subject:</b> Re: [FM Discuss] issues with Kdenlive manual images</font>
<div> </div>
</div>
<div class="x_BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="x_PlainText">Hi Mick,<br>
<br>
> I know the limit used to be 600px wide and I have always stuck to that.<br>
<br>
Booktype has come a long way since those days :-)<br>
<br>
> I am pretty sure that this is a limit that has<br>
> increased in Booktype 2.x and also he might have more knowledge of what<br>
> happens if we use a wider images size in 1.6 and any potential hacks.<br>
<br>
In Booktype 2.3 you can use any image size you want, as long as the<br>
resolution is high enough for print output (should that be one of your<br>
targets). There are also tools for zooming, cropping etc. built in.<br>
<br>
Cheers!<br>
<br>
Daniel<br>
_______________________________________________<br>
Discuss mailing list<br>
Discuss@lists.flossmanuals.net<br>
<a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" id="LPlnk697332" previewremoved="true">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a> - you can unsubscribe here
<div id="LPBorder_GT_15182044681770.9160345192548438" style="margin-bottom:20px; overflow:auto; width:100%; text-indent:0px">
<table id="LPContainer_15182044681710.25614113968579" cellspacing="0" style="width:90%; background-color:rgb(255,255,255); overflow:auto; padding-top:20px; padding-bottom:20px; margin-top:20px; border-top:1px dotted rgb(200,200,200); border-bottom:1px dotted rgb(200,200,200)">
<tbody>
<tr valign="top" style="border-spacing:0px">
<td id="x_TextCell_15182044681730.1327219267521642" colspan="2" style="vertical-align: top; padding: 0px; display: table-cell; position: relative;">
<div id="LPRemovePreviewContainer_15182044681730.61206820658279"></div>
<div id="LPTitle_15182044681740.2869298689283686" style="top:0px; color:rgb(0,120,215); font-weight:400; font-size:21px; font-family:wf_segoe-ui_light,"Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; line-height:21px">
<a id="LPUrlAnchor_15182044681750.07678085126842138" href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank" style="text-decoration:none">Discuss Info Page - lists.flossmanuals.net</a></div>
<div id="LPMetadata_15182044681760.2598381461766992" style="margin:10px 0px 16px; color:rgb(102,102,102); font-weight:400; font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size:14px; line-height:14px">
lists.flossmanuals.net</div>
<div id="LPDescription_15182044681760.8931225307174406" style="display:block; color:rgb(102,102,102); font-weight:400; font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size:14px; line-height:20px; max-height:100px; overflow:hidden">
Discuss anything about floss manuals - its aims, what it does, how it does it, what it could do, and how it can be better. To see the collection of prior postings to ...</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<br>
</div>
</span></font></div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>