Hi Josiah, It's done by pummelling a spreadsheet ~ it's supposed to be automated but in practise, it takes a lot of trial and error to get the macros right. If you had a hundred of them to do, it'd be fairly automated but you'd still be cleaning up the input by hand.
This is the spreadsheet I have left over, but it seems to be missing all the macros, so I must have only kept a copy of the output, but you get the idea. https://docs.google.com/spreadsheets/d/1Pyg99FHK8GhuPWHSLHNoLGmvypTW2Gr_wVL15Jrmeps/edit?usp=sharing I agree that a screenplay tool would be interesting. One thing I have wondered about before is whether it makes sense sometimes to have a different, kind-of "intermediate", editing mode where an end user can edit content, but without dropping into the full wiki-text editor. Sort of like a very limited wysywig editor. We would need to create a pleasant writing environment for the creative mind. Regards, Richard On Tuesday, June 21, 2016 at 6:24:13 PM UTC+10, Josiah wrote: > > Ciao Mark & RichardWS > > Good stuff! showing what can be done. > > Mark, just looking at it made me realise how relatively easy it would be > to tweak further in many ways... for instance to place all STAGE: > instructions into italic or a different colour. > > Richard, the depth of decomposition you go to, and adumbrating various > indices, is fascinating. I'd be interested to know how much this is > automated, or could be. It certainly gives potential fine grained ways of > studying & using long texts. > > The more I look at all this the more I think than just be an approach to > presenting text, but actually to AUTHOR text. Specifically I can see how it > might be developed into a SCREENPLAY writing tool. > > Best wishes > Josiah > > On Tuesday, 21 June 2016 06:16:23 UTC+2, RichardWilliamSmith wrote: >> >> Hi Mark, >> >> It looks great. When I did similar with Macbeth, I was able to use the >> spreadsheet (and a lot of futzing) to add several fields to each line of >> the play - which might seem like overkill but it means that you can, for >> example, extract all the lines spoken by a particular character etc. >> >> >> <https://lh3.googleusercontent.com/-0DtqN8d_zPY/V2i99P4A_oI/AAAAAAAABo0/ojWKFQg2XG0FXJAYM55-VNd3Uo5AVy8ZACLcB/s1600/Screen%2BShot%2B2016-06-21%2Bat%2B2.04.08%2BPM.png> >> >> The primary key here is as simple as possible - every piece of dialog and >> direction gets a sequential integer. >> >> As for the total size of the finished document, my advice would be "don't >> panic!" - most of the web pages we load every day are much bigger than even >> a fully-stuffed tiddlywiki. I was reading this slide-deck just the other >> day which you might be interested in; >> http://idlewords.com/talks/website_obesity.htm >> >> "Let's take a look at the Apple page that explains iOS on the iPad Pro >>> <http://www.apple.com/ipad-pro/ios9/>. How big do you think this page >>> is? >>> Would you believe that it's bigger than the entire memory capacity of >>> the iconic iMac? (32 MB) >>> In fact, you could also fit the contents of the Space Shuttle Main >>> Computer. Not just for one Shuttle, but the entire fleet (5 MB). >>> And you would still have room for a tricked out Macintosh SE... (5MB). >>> ...and the collected works of Shakespeare... (5 MB) >>> With lots of room to spare. The page is 51 megabytes big." >> >> >> So, you see, if our file is only 10 or 20 times the size of our actual >> content, we are really doing quite well ;) >> >> Regards, >> Richard >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/276cc45d-3d8f-4357-acf3-ee8023cb76dc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
