<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">Hi Maren:</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Sorry, I did completely miss that earlier message of yours. The documenting process you've adopted looks really great, judging by your posted examples. Animated GIFs can definitely take us part of the way, at least.
And you're absolutely right that video-tutorial production often takes more specialized (and different) skills to achieve the same quality standard as traditional text-and-screenshot -- although in my experience that's becoming less and less the case, as animation
software (including screen-capture-animation software) becomes increasingly accessible. But still definitely a consideration, along with the one raised earlier about the difficulty of open-source-editing video documentation. </p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">And then, as you say, there is the question of what animation files could work with or be embedded within largely textual (but still digital) documents. I was surprised to learn, when I started working with eLearning
authoring tools, that Flash files of any complexity (even interactive) can be embedded in PDFs, as generated by Adobe Captivate (and I assume Articulate Storyline too). People actually send complete eLearning courses and modules around to each other as PDFs
all the time. And certainly it is generally possible to embed Flash files in html--that was the whole idea of Flash--although I don't know the details of Booktype hmtl either. The challenge there is that Flash itself is becoming deprecated, since it doesn't
work on most mobile devices. But short animated screen captures could (and are) also done as mp4 and .mov files, and those both can be embedded in PDF and html too. Btw, and back to my earlier point about increased accessibility, it would take an absolute
novice about 15 minutes to learn how to use the screen-capture-video feature of Adobe Captivate; the only real barrier there is the price of the software itself. But there is lots of freeware for the same purpose---I've used Screenpresso myself to do screen
capture vids for user testing, as well as static screen shots. What Captivate adds is the ability to easily edit and annotate your screen vids, but I'm sure there's free software for that too. </p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Obviously none of this helps for documents that you intend to print out, but that pretty much goes without saying, and it seems that less and less tech writing practice in general is based around the assumption of printed
material as opposed to digital. So the questions are probably more about the best ways to integrate textual/static and animated presentation modes in the same document--or maybe not the *same* document, but within a single presentation flow or structure which
we could still call a 'manual'. </p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">best,</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Matt</p>
<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 Maren Hachmann <maren@goos-habermann.de><br>
<b>Sent:</b> Thursday, January 4, 2018 3:13 PM<br>
<b>To:</b> discuss@lists.flossmanuals.net<br>
<b>Subject:</b> Re: [FM Discuss] Hi folks</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hey there,<br>
<br>
the Inkscape Beginners' Guide *is* official, as stated in my previous<br>
message :)<br>
Gifs (as described in that same message - maybe you didn't get it?) are<br>
a possible solution for having at least basic usage descriptions. They<br>
can't be very complex, but even the short animations are already very<br>
useful. But they don't work in print (and also not (yet?) in pdf), of<br>
course. I'm not sure if they'd play if included in a booktype html<br>
manual (in theory, they should, but who knows if it does any image<br>
postprocessing).<br>
<br>
Kind Regards,<br>
Maren<br>
<br>
Am 04.01.2018 um 22:04 schrieb M R:<br>
> Mick (and all):<br>
> <br>
> <br>
> That certainly makes sense. One thing that strikes me when I consider<br>
> the concrete examples offered so far is that so many of them are<br>
> centered on/driven by the needs of the FM contributors themselves (like<br>
> you guys, but also going back to the founding), rather than hypothetical<br>
> end-users outside of a specific context like the contributors'<br>
> own teaching/workshops or other needs. Which is completely fine AFAIAK,<br>
> since my own interest would be largely selfish -- I want manual-writing<br>
> practice and portfolio samples 😊; and if anyone else can get some use<br>
> out of my contribution, that's great too. It does appear that the<br>
> situation is a bit different for software like Inkscape (vs Audacity or<br>
> Blender, or Unity, or Firefox) because Inkscape's own site appears to<br>
> endorse the Floss manual as semi-official. So Inkscape might be the<br>
> perfect example of a Floss manual where end-user utility is maximized.<br>
> <br>
> <br>
> At the same time, it's also interesting that Inkscape's own site, in<br>
> their 'Learning' tab, leans heavily as well on tutorials contributed by<br>
> individuals in the user community, many of which are in video format. <br>
> Actually, I'm not aware of any software site (certainly in the graphics<br>
> world), whether open-source or proprietary, that doesn't make heavy use<br>
> of video tutorials, however rich the text documentation is. I think<br>
> this just speaks to a current diversity (maybe a transition -- we'll<br>
> see) in end-user preferred learning modes. Now, for an open-source,<br>
> collaborative framework like Floss, I would say your other point (Mick)<br>
> is probably decisive: the text-and-screenshot type of manual is easily<br>
> remixed/edited/updated, which is essentially impossible in video<br>
> tutorials (except for wholesale replacement/update by the original<br>
> maker, which is what ends up happening in practice). This isn't just<br>
> about a difference in presentation technology, but about a fundamental<br>
> difference in genre: traditional manuals, like all traditional tech<br>
> writing, are intended to be anonymous, or neutrally voiced, such that<br>
> any individual's contribution (given reasonable quality standards)<br>
> should be transparent and interchangeable. Whereas the (literal)<br>
> narrative 'voice' of a video tutorial is not only irreducibly singular,<br>
> personal, non-anonymous; that's also precisely what makes them<br>
> *engaging* for people who prefer to learn that way. <br>
> <br>
> <br>
> I do wonder about a future (or on-going) convergence of the two modes:<br>
> for instance many video tutorials are quite short now, focusing on very<br>
> specific operations in a tool (even if they're then linked into longer<br>
> series), which makes them more useful to a broader user base. I think<br>
> if I were designing a text-based static manual from scratch, now--at<br>
> least for software that featured complex GUI operations---I'd<br>
> probably want every section to at least include curated links to such<br>
> short vid tutorials or demonstrations (even if I had to generate some of<br>
> these myself). But this already violates the anonymity principle...and<br>
> at the same time it doesn't, IMO, go nearly far enough for some of the<br>
> software uses I imagine documenting. Blender, for instance, is a 3D<br>
> modeling tool that relies on such complex and finicky GUI operations<br>
> that a series of text instructions and screenshots would, I think, be<br>
> hopelessly inadequate to convey how to actually use it. There's still<br>
> absolutely a place for textual Blender documentation, but I think it's<br>
> more in the way of a reference dictionary than a manual as such. I even<br>
> feel this way about Audacity. It's orders of magnitude less<br>
> complex-finicky in its GUI than Blender, but if I wanted to convey how<br>
> to do any kind of multi-track sound mixing and editing in order to build<br>
> up an interesting sound-scape (and this is another document example I'm<br>
> actively considering), I can't imagine doing this in any way but video. <br>
> Again, though, this may simply speak to the way I personally have been<br>
> learning software (and on a largely hobbyist basis, at that) for the<br>
> past decade. <br>
> <br>
> <br>
> I would be very interested, anyway, to see if anyone had come up with a<br>
> framework for anonymized, open-source video tech documentation. <br>
> Actually you could sort of do it with a tool like Adobe Captivate, using<br>
> their 'software demonstration' mode and maybe a text-to-voice feature. <br>
> Ok, nevermind...<br>
> <br>
> <br>
> Matt<br>
> <br>
> <br>
> <br>
> ------------------------------------------------------------------------<br>
> *From:* Discuss <discuss-bounces@lists.flossmanuals.net> on behalf of<br>
> Mick Chesterman <M.Chesterman@mmu.ac.uk><br>
> *Sent:* Thursday, January 4, 2018 2:04 AM<br>
> *To:* discuss@lists.flossmanuals.net<br>
> *Subject:* Re: [FM Discuss] Hi folks<br>
> <br>
> Hi there,<br>
> <br>
> I've got different hats on here.<br>
> But one of my aims is to involve some of my University students in<br>
> making manuals as a really productive learning activity.<br>
> <br>
> So that's another reason to lower the barriers to contributions via text<br>
> and screenshot being the basis rather than video. And the ease of<br>
> remixing / updating.<br>
> <br>
> Thanks<br>
> Mick<br>
> <br>
>> -----Original Message-----<br>
>> From: Discuss [<a href="mailto:discuss-bounces@lists.flossmanuals.net">mailto:discuss-bounces@lists.flossmanuals.net</a>] On Behalf Of<br>
>> Maren Hachmann<br>
>><br>
> <br>
> "Before acting on this email or opening any attachments you should read<br>
> the Manchester Metropolitan University email disclaimer available on its<br>
> website <a href="http://www.mmu.ac.uk/emaildisclaimer">http://www.mmu.ac.uk/emaildisclaimer</a> "<br>
> _______________________________________________<br>
> Discuss mailing list<br>
> Discuss@lists.flossmanuals.net<br>
> <a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a> -<br>
> you can unsubscribe here<br>
> <br>
> <br>
> _______________________________________________<br>
> Discuss mailing list<br>
> Discuss@lists.flossmanuals.net<br>
> <a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a> - you can unsubscribe here<br>
> <br>
<br>
_______________________________________________<br>
Discuss mailing list<br>
Discuss@lists.flossmanuals.net<br>
<a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a> - you can unsubscribe here<br>
</div>
</span></font></div>
</div>
</div>
</body>
</html>