Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #391164 > unrolled thread
| Started by | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| First post | 2017-01-23 04:02 +0000 |
| Last post | 2017-01-23 18:22 -0500 |
| Articles | 20 on this page of 65 — 10 participants |
Back to article view | Back to comp.os.linux.advocacy
Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-23 04:02 +0000
Re: Screenplays on Linux -- another try Snit <usenet@gallopinginsanity.com> - 2017-01-22 21:27 -0700
Re: Screenplays on Linux -- another try vallor <vallor@cultnix.org> - 2017-01-23 04:47 +0000
Re: Screenplays on Linux -- another try Snit <usenet@gallopinginsanity.com> - 2017-01-22 21:59 -0700
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-23 15:15 +0000
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-23 17:46 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-23 18:22 +0000
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-23 18:34 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-23 19:42 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-23 20:09 +0000
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-23 20:42 +0000
Re: Screenplays on Linux -- another try Snit <usenet@gallopinginsanity.com> - 2017-01-23 13:45 -0700
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-23 20:17 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-23 20:40 +0000
Re: Screenplays on Linux -- another try Steve Carroll <fretwizzer@gmail.com> - 2017-01-23 12:46 -0800
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-23 22:45 +0000
Re: Screenplays on Linux -- another try Snit <usenet@gallopinginsanity.com> - 2017-01-23 15:52 -0700
Re: Screenplays on Linux -- another try Snit <usenet@gallopinginsanity.com> - 2017-01-23 16:00 -0700
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 03:10 +0000
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-24 04:17 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 05:04 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 05:47 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 05:51 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 08:13 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 16:55 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 20:53 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 21:20 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 21:36 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 23:27 +0000
Re: Screenplays on Linux -- another try chrisv <chrisv@nospam.invalid> - 2017-01-25 07:09 -0600
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-24 19:25 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 21:16 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 21:31 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 21:17 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 21:43 +0000
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-24 22:30 +0000
Re: Screenplays on Linux -- another try Marek Novotny <marek.novotny@marspolar.com> - 2017-01-24 16:33 -0600
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-24 22:33 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-25 00:11 +0000
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-25 00:28 +0000
Re: Screenplays on Linux -- another try ronb <ronb02NOSPAM@gmail.com> - 2017-01-25 00:18 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-25 01:06 +0000
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-25 01:55 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-25 15:48 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 23:20 +0000
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 23:30 +0000
Re: Screenplays on Linux -- another try Snit <usenet@gallopinginsanity.com> - 2017-01-31 09:50 -0700
Re: Screenplays on Linux -- another try Snit <usenet@gallopinginsanity.com> - 2017-01-23 13:12 -0700
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-23 20:41 +0000
Re: Screenplays on Linux -- another try Snit <usenet@gallopinginsanity.com> - 2017-01-23 13:43 -0700
Re: Screenplays on Linux -- another try deplorable owl <owl@rooftop.invalid> - 2017-01-24 01:13 +0000
Re: Screenplays on Linux -- another try GreyCloud <mist@cumulus.com> - 2017-01-23 19:37 -0700
Re: Screenplays on Linux -- another try RonB <ronb02NOSPAM@gmail.com> - 2017-01-24 04:19 +0000
Re: Screenplays on Linux -- another try GreyCloud <mist@cumulus.com> - 2017-01-24 11:24 -0700
Re: Screenplays on Linux -- another try Marek Novotny <marek.novotny@marspolar.com> - 2017-01-23 22:42 -0600
Re: Screenplays on Linux -- another try Marek Novotny <marek.novotny@marspolar.com> - 2017-01-24 00:01 -0600
Re: Screenplays on Linux -- another try chrisv <chrisv@nospam.invalid> - 2017-01-24 06:57 -0600
Re: Screenplays on Linux -- another try chrisv <chrisv@nospam.invalid> - 2017-01-24 06:55 -0600
Re: Screenplays on Linux -- another try GreyCloud <mist@cumulus.com> - 2017-01-24 11:22 -0700
Re: Screenplays on Linux -- another try Marek Novotny <marek.novotny@marspolar.com> - 2017-01-24 12:28 -0600
Re: Screenplays on Linux -- another try Steve Carroll <fretwizzer@gmail.com> - 2017-01-24 12:31 -0800
Re: Screenplays on Linux -- another try GreyCloud <mist@cumulus.com> - 2017-01-24 17:09 -0700
Re: Screenplays on Linux -- another try GreyCloud <mist@cumulus.com> - 2017-01-24 17:10 -0700
Re: Screenplays on Linux -- another try GreyCloud <mist@cumulus.com> - 2017-01-24 11:23 -0700
Re: Screenplays on Linux -- another try Chris Ahlstrom <OFeem1987@teleworm.us> - 2017-01-23 18:22 -0500
Page 1 of 4 [1] 2 3 4 Next page →
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2017-01-23 04:02 +0000 |
| Subject | Screenplays on Linux -- another try |
| Message-ID | <o63v8q$vhq$1@dont-email.me> |
Screenplay Writing solutions for Linux users ... (I write this on the off-chance that someone who uses Linux and writes screenplays may do a Google search and find these options. I started a new thread because "Snit" hijacked the last one.) It wasn't that long ago that, if you wanted to write screenplays in Linux, you were limited to just a few choices. Macros for OpenOffice (and then) LibreOffice. Just as they weren't a good idea in Microsoft Office for Windows, screenplay macros are not the way to go. You might be able to make them work, but they're about useless for porting out to another program, should the need arise. At any rate, at one point this was one of the choices (and probably still is), it's just not a good one. Another choice was using Celtx online. For a short while there was downloadable Ubuntu version of Celtx available, but Celtx went a different direction and, for the most part, they're almost completely an online resource now. They have a free version of the software and two "charge per month versions," but there's limitations (online to print) or save to PDF. I haven't tested them lately. Never thought they had the best setup. The third Linux choice was running Final Draft or Movie Magic Screenwriter under Wine. I tried this for a while (and actually got it to work) but I prefer a native Linux solution (I don't even install Wine anymore). Now there are several Linux solutions. Four full, native Linux screenplay applications, at least five more online formatters and -- maybe the best solution of all -- the fountain format language (and afterwriting.com -- online and offline -- to convert the fountain format into something formatted and portable -- like Final Draft .fdx or PDF formats). I'll start with the full applications -- and since I've already mentioned these, I'll keep it brief. Full Offline Applications ... Trelby (www.trelby.org) -- long in the tooth but still my favorite. Simple and clean and it works well for basic screenplay formatting -- which is what I want. Active development has slowed to a crawl, but it's still available for Windows and Linux -- the Mac OSX beta never really got off the ground. Screenshot: http://tinyurl.com/gtszkhn Scrivener for Linux (https://www.literatureandlatte.com/forum/viewforum.php?f=33) -- Only in available in two (non-expiring) betas versions (both in 32 and 64 versions), but a modern writing and research compiling application. Scrivener is too complex in my estimation, I just like as simple formatter -- and I can do my research in Simplenote or Evernote. This Linux user and reviewer liked it, thought it was "Linux-like" in its methods. Review available here ... http://scienceblogs.com/gregladen/2014/08/29/scrivener-on-linux-try-it-youll-like-it/ (To download Scrivener for Linux, just got to the beta thread in the Scrivener for Linux forum.) Screenshot: http://tinyurl.com/j7zz4mv Kit Scenarist (from Russia, https://kitscenarist.ru/en/index.html) -- I've just gotten started with this one, but it appears to have potential. I think it runs under java however, so I'm not too fond of that idea. At any rate you download it and test it for yourself. (Comes in Windows XP SP 3 and up, Linux 32 and 64 bit, and OSX 10.08 and up.) Screenshot: http://tinyurl.com/hgz79d7 Fade In Pro (http://www.fadeinpro.com/) -- The only current commercial Linux screenplay application. Excellent support, comes in .deb, .rpm and tar.gz formats (in both 32 and 64 bit). A trial version is free, but it will nag for the registration and print watermarks on each page. Full cost is $50 -- and that includes a personal license for all your computers (Windows, OSX and Linux). There are also Android and iPhone/iPad applications and all future updates are free. Screenshot: http://tinyurl.com/jmngzwl Amazon Storywriter -- This is a Chrome App and still seems to be available, although I thought Google was getting rid of apps? It works offline. But I wouldn't use Amazon Storywriter. The license is weird and you can't even delete your own scripts -- you have to get support to do it for you. So Amazon definitely feels they have some kind of rights to your work. Screenshot: http://tinyurl.com/jhneccm Online Screenplay software. Celtx -- Mentioned above and still available. The Basic version is still free, but you'll have to pay either $10 or $20 a month for the standard and pro versions (a bit cheaper if you buy by the year.) Screenshot: http://tinyurl.com/hnuc9az Writer Duet (https://writerduet.com) -- A little "crowded" for my taste, but it's a full featured screenplay formatter. For Windows and Mac users there is now an offline application, and Linux users can use Chrome app for writing offline (basically the Web Page saved locally) if they buy the Pro version ($139 lifetime or $8 a month). Screenshot: http://tinyurl.com/jeu8z5p YouMeScript (https://youmescript.com) -- Very simple and usable screenplay formatter. This is one of my favorite online screenplay formatters, and they are now offering a Pro version for $1.80 a month (bought by the year). As is, with standard version, you can export to Final Draft (.fdx), fountain (.fountain), PDF and Formatted Text. So quite useful. Screenshot: http://tinyurl.com/gqqyjuy RawScripts (https://www.rawscripts.com/) -- This one has been around for a while (and I really haven't kept up with them, but it's another very usable screenplay formatter. Exports only to PDF or text. RawScripts is now free and open sourced -- even provides the source code -- the blog is at https://www.rawscripts.org Screenshot: http://tinyurl.com/zpvmy8e Adobe Story (https://story.adobe.com/en-us/) -- I never really got into this one, but it seems able enough. There's a pro version that costs $10, not sure what features it adds. (Sorry, lousy review -- too many choices now, I don't need this one.) Screenshot: http://tinyurl.com/jo2hrm8 There's probably a few others (one called Script Buddy, I think, but I never liked it). Any of these would probably work for basic screenplay writing, although I would stay away from Amazon Storywriter, unless you wanted to get involved in their whole "social screenwriting" "infrastructure." (I don't.) Then we get to the last category -- Fountain (https://fountain.io/) Fountain is a mark-up language. So you can write in just about any text editor and then import that text into a Fountain aware application. Most of the applications (online or offline) that I've listed above will import Fountain files and export to Fountain format. But the one I like best (since there's currently no offline applications for Linux) is afterwriting (afterwriting.com/). This web-site has a built-in text editor for writing in Fountain format and will import Final Draft and Fountain files. It will save in Fountain format or print to PDF. You can automate file saving and reading to/from Dropbox or Google Drive. You can also download afterwriting and use it offline in a browser. It's not quite all you need, but it's close to it. How Fountain works ... You put spaces between screenplay elements ... like this ... INT. "SNIT'S" CLOSET - NIGHT "SNIT" sits in front of his computer, arguing with one of his SOCKS. "SNIT" (drooling profusely) No, we can't write that. They might figure out you're me and I'm you. And we've so cleverly hidden that fact. SOCK (wheedling) I want. I want. I want! afterwriting takes this text file and converts it to ... http://tinyurl.com/zyq9q9u But using the sample script we've been using ... afterwriting Editor and Preview (formatted) ... http://tinyurl.com/zefh2d8 Editor http://tinyurl.com/zfjlzbh Format With the Fountain solution you can write with any editor. I even use a small Neo keyboard/word processor and move the result into afterwriting (via USB cable). I've also used voice type dictation on my Blackberry -- into Simplenote and copied that to afterwriting from my computer. Pure text is an incredibly flexible choice. And that's about it. I think there's also screenplay macros for vim, but I haven't tried them yet. I'll see if I can dig it up and try it out. -- Using slrn with Linux Mint Mate 17.1
[toc] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2017-01-22 21:27 -0700 |
| Message-ID | <D4AAD44A.8B603%usenet@gallopinginsanity.com> |
| In reply to | #391164 |
On 1/22/17, 9:02 PM, in article o63v8q$vhq$1@dont-email.me, "RonB" <ronb02NOSPAM@gmail.com> wrote: > Screenplay Writing solutions for Linux users ... (I write this on the > off-chance that someone who uses Linux and writes screenplays may do a > Google search and find these options. I started a new thread because "Snit" > hijacked the last one.) Seriously, please stop trolling me. > It wasn't that long ago that, if you wanted to write screenplays in Linux, > you were limited to just a few choices. The fact Linux has limited choices is to be expected -- but what matters more is if they are decent choices. If the software works well. > Macros for OpenOffice (and then) LibreOffice. Just as they weren't a good > idea in Microsoft Office for Windows, screenplay macros are not the way to > go. You might be able to make them work, but they're about useless for > porting out to another program, should the need arise. At any rate, at one > point this was one of the choices (and probably still is), it's just not a > good one. Fair enough. You want a choice that is not the minimum. > Another choice was using Celtx online. For a short while there was > downloadable Ubuntu version of Celtx available, but Celtx went a different > direction and, for the most part, they're almost completely an online > resource now. They have a free version of the software and two "charge per > month versions," but there's limitations (online to print) or save to PDF. I > haven't tested them lately. Never thought they had the best setup. Curious: do you write screenplays? > The third Linux choice was running Final Draft or Movie Magic Screenwriter > under Wine. I tried this for a while (and actually got it to work) but I > prefer a native Linux solution (I don't even install Wine anymore). Yes, usually better to use native software... something that uses the benefits of the system you are on. > Now there are several Linux solutions. Four full, native Linux screenplay > applications, at least five more online formatters and -- maybe the best > solution of all -- the fountain format language (and afterwriting.com -- > online and offline -- to convert the fountain format into something > formatted and portable -- like Final Draft .fdx or PDF formats). > > I'll start with the full applications -- and since I've already mentioned > these, I'll keep it brief. No, you did not. :) > Full Offline Applications ... ... > Scrivener for Linux > (https://www.literatureandlatte.com/forum/viewforum.php?f=33) -- Only in > available in two (non-expiring) betas versions (both in 32 and 64 versions), > but a modern writing and research compiling application. Scrivener is too > complex in my estimation, I just like as simple formatter -- and I can do my > research in Simplenote or Evernote. This Linux user and reviewer liked it, > thought it was "Linux-like" in its methods. Review available here ... > http://scienceblogs.com/gregladen/2014/08/29/scrivener-on-linux-try-it-youll-l > ike-it/ > (To download Scrivener for Linux, just got to the beta thread in the > Scrivener for Linux forum.) > Screenshot: http://tinyurl.com/j7zz4mv Tried the link for the review. Seems down right now. Curious about what they might mean by "Linux-like" methods. It was first a Mac program what was ported to Windows and then later Linux (and then only in beta format). Even then they took out features and benefits to make it work on the lowest common denominator. > Kit Scenarist (from Russia, https://kitscenarist.ru/en/index.html) -- I've > just gotten started with this one, but it appears to have potential. I think > it runs under java however, so I'm not too fond of that idea. At any rate > you download it and test it for yourself. (Comes in Windows XP SP 3 and up, > Linux 32 and 64 bit, and OSX 10.08 and up.) > Screenshot: http://tinyurl.com/hgz79d7 I played with it for just a bit... the UI is *bad* in terms of working with the system. But if it is a key part of your workflow I am sure you can get used to it. ... > You put spaces between screenplay elements ... like this ... > > INT. "SNIT'S" CLOSET - NIGHT > > "SNIT" sits in front of his computer, arguing with one of his SOCKS. > > "SNIT" > (drooling profusely) > No, we can't write that. They might figure out you're me and I'm you. And > we've so cleverly hidden that fact. > > SOCK > (wheedling) > I want. I want. I want! > > afterwriting takes this text file and converts it to ... Gee, you use it to further your trolling. Go figure. Let us see: * personal insults, check! * false accusations, check! * holding me accountable for the actions of others, check! Yup... you are a part of the herd. > http://tinyurl.com/zyq9q9u Wow... and taking your trolling out of COLA. It is not like you are even responding to something I did. > But using the sample script we've been using ... afterwriting Editor and > Preview (formatted) ... > > http://tinyurl.com/zefh2d8 Editor > http://tinyurl.com/zfjlzbh Format > > With the Fountain solution you can write with any editor. I even use a small > Neo keyboard/word processor and move the result into afterwriting (via USB > cable). I've also used voice type dictation on my Blackberry -- into > Simplenote and copied that to afterwriting from my computer. Pure text is an > incredibly flexible choice. > > And that's about it. I think there's also screenplay macros for vim, but I > haven't tried them yet. I'll see if I can dig it up and try it out. What type screenplays do you write, other than to troll? -- "All of these acts [prostitution, adultery, necrophilia, bestiality, possession of child pornography, and even incest and pedophilia] should be legal as long as no one is coerced. They are illegal only because of prejudice and narrowmindedness." -- Richard Stallman
[toc] | [prev] | [next] | [standalone]
| From | vallor <vallor@cultnix.org> |
|---|---|
| Date | 2017-01-23 04:47 +0000 |
| Message-ID | <eelg79FmfpkU5@mid.individual.net> |
| In reply to | #391164 |
On Mon, 23 Jan 2017 04:02:34 +0000, RonB wrote: > Screenplay Writing solutions for Linux users ... Thank you for writing this up, read it with interest. :) -- -v
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2017-01-22 21:59 -0700 |
| Message-ID | <D4AADBC9.8B60B%usenet@gallopinginsanity.com> |
| In reply to | #391170 |
On 1/22/17, 9:47 PM, in article eelg79FmfpkU5@mid.individual.net, "vallor" <vallor@cultnix.org> wrote: > On Mon, 23 Jan 2017 04:02:34 +0000, RonB wrote: > >> Screenplay Writing solutions for Linux users ... > > Thank you for writing this up, read it with interest. :) If I had written it, including the trolling and the accusations, you would have called me out. Why not call him out for his trolling? Why the bias? -- 🙈🙉🙊
[toc] | [prev] | [next] | [standalone]
| From | deplorable owl <owl@rooftop.invalid> |
|---|---|
| Date | 2017-01-23 15:15 +0000 |
| Message-ID | <gahcio.ag93@rooftop.invalid> |
| In reply to | #391164 |
RonB <ronb02NOSPAM@gmail.com> wrote:
> Screenplay Writing solutions for Linux users ... (I write this on the
> off-chance that someone who uses Linux and writes screenplays may do a
> Google search and find these options. I started a new thread because "Snit"
> hijacked the last one.)
>
> It wasn't that long ago that, if you wanted to write screenplays in Linux,
> you were limited to just a few choices.
>
...
>
> And that's about it. I think there's also screenplay macros for vim, but I
> haven't tried them yet. I'll see if I can dig it up and try it out.
>
http://i.imgur.com/jMNojwe.png
anon@lowtide:~/movie_scripts/snit$ cat snit.tex
\documentclass{screenplay}
\begin{document}
\fadein
\intslug[day]{snit's house}
An amorphous blob in the corner is backlit by the glow of a computer screen.
\begin{dialogue}{snit}
Toasty, take a look at this color picker. It's got crayons.
\end{dialogue}
\begin{dialogue}{toasty}
If I were nine years old I might like that.
\end{dialogue}
\begin{dialogue}{snit}
I'm going to ignore your gaslighting.
\end{dialogue}
\extslug[evening]{snit's house}
Two men in white lab coats have just emerged from a van, and Toasty
is leading them to the front door.
\fadeout
\end{document}
anon@lowtide:~/movie_scripts/snit$
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2017-01-23 17:46 +0000 |
| Message-ID | <o65fh6$f86$1@dont-email.me> |
| In reply to | #391241 |
On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
> RonB <ronb02NOSPAM@gmail.com> wrote:
>> Screenplay Writing solutions for Linux users ... (I write this on the
>> off-chance that someone who uses Linux and writes screenplays may do a
>> Google search and find these options. I started a new thread because "Snit"
>> hijacked the last one.)
>>
>> It wasn't that long ago that, if you wanted to write screenplays in Linux,
>> you were limited to just a few choices.
>>
> ...
>>
>> And that's about it. I think there's also screenplay macros for vim, but I
>> haven't tried them yet. I'll see if I can dig it up and try it out.
>>
>
> http://i.imgur.com/jMNojwe.png
>
> anon@lowtide:~/movie_scripts/snit$ cat snit.tex
> \documentclass{screenplay}
> \begin{document}
> \fadein
>
> \intslug[day]{snit's house}
> An amorphous blob in the corner is backlit by the glow of a computer screen.
>
> \begin{dialogue}{snit}
> Toasty, take a look at this color picker. It's got crayons.
> \end{dialogue}
>
>
> \begin{dialogue}{toasty}
> If I were nine years old I might like that.
> \end{dialogue}
>
>
> \begin{dialogue}{snit}
> I'm going to ignore your gaslighting.
> \end{dialogue}
>
>
> \extslug[evening]{snit's house}
> Two men in white lab coats have just emerged from a van, and Toasty
> is leading them to the front door.
>
> \fadeout
> \end{document}
> anon@lowtide:~/movie_scripts/snit$
:) Just curious, what is this, vim?
--
Using slrn with Linux Mint Mate 17.1
[toc] | [prev] | [next] | [standalone]
| From | deplorable owl <owl@rooftop.invalid> |
|---|---|
| Date | 2017-01-23 18:22 +0000 |
| Message-ID | <ab803.auv32x41@rooftop.invalid> |
| In reply to | #391283 |
RonB <ronb02NOSPAM@gmail.com> wrote:
> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>> Screenplay Writing solutions for Linux users ... (I write this on the
>>> off-chance that someone who uses Linux and writes screenplays may do a
>>> Google search and find these options. I started a new thread because "Snit"
>>> hijacked the last one.)
>>>
>>> It wasn't that long ago that, if you wanted to write screenplays in Linux,
>>> you were limited to just a few choices.
>>>
>> ...
>>>
>>> And that's about it. I think there's also screenplay macros for vim, but I
>>> haven't tried them yet. I'll see if I can dig it up and try it out.
>>>
>>
>> http://i.imgur.com/jMNojwe.png
>>
>> anon@lowtide:~/movie_scripts/snit$ cat snit.tex
>> \documentclass{screenplay}
>> \begin{document}
>> \fadein
>>
>> \intslug[day]{snit's house}
>> An amorphous blob in the corner is backlit by the glow of a computer screen.
>>
>> \begin{dialogue}{snit}
>> Toasty, take a look at this color picker. It's got crayons.
>> \end{dialogue}
>>
>>
>> \begin{dialogue}{toasty}
>> If I were nine years old I might like that.
>> \end{dialogue}
>>
>>
>> \begin{dialogue}{snit}
>> I'm going to ignore your gaslighting.
>> \end{dialogue}
>>
>>
>> \extslug[evening]{snit's house}
>> Two men in white lab coats have just emerged from a van, and Toasty
>> is leading them to the front door.
>>
>> \fadeout
>> \end{document}
>> anon@lowtide:~/movie_scripts/snit$
>
> :) Just curious, what is this, vim?
>
latex.
So, assuming the latex screenplay class is installed:
`pdflatex snit.tex`
will generate a pdf.
On debian, `apt-get install texlive-full` pulled in the screenplay class
along with everything else.
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2017-01-23 18:34 +0000 |
| Message-ID | <o65ibb$pst$2@dont-email.me> |
| In reply to | #391289 |
On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
> RonB <ronb02NOSPAM@gmail.com> wrote:
>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>> Screenplay Writing solutions for Linux users ... (I write this on the
>>>> off-chance that someone who uses Linux and writes screenplays may do a
>>>> Google search and find these options. I started a new thread because "Snit"
>>>> hijacked the last one.)
>>>>
>>>> It wasn't that long ago that, if you wanted to write screenplays in Linux,
>>>> you were limited to just a few choices.
>>>>
>>> ...
>>>>
>>>> And that's about it. I think there's also screenplay macros for vim, but I
>>>> haven't tried them yet. I'll see if I can dig it up and try it out.
>>>>
>>>
>>> http://i.imgur.com/jMNojwe.png
>>>
>>> anon@lowtide:~/movie_scripts/snit$ cat snit.tex
>>> \documentclass{screenplay}
>>> \begin{document}
>>> \fadein
>>>
>>> \intslug[day]{snit's house}
>>> An amorphous blob in the corner is backlit by the glow of a computer screen.
>>>
>>> \begin{dialogue}{snit}
>>> Toasty, take a look at this color picker. It's got crayons.
>>> \end{dialogue}
>>>
>>>
>>> \begin{dialogue}{toasty}
>>> If I were nine years old I might like that.
>>> \end{dialogue}
>>>
>>>
>>> \begin{dialogue}{snit}
>>> I'm going to ignore your gaslighting.
>>> \end{dialogue}
>>>
>>>
>>> \extslug[evening]{snit's house}
>>> Two men in white lab coats have just emerged from a van, and Toasty
>>> is leading them to the front door.
>>>
>>> \fadeout
>>> \end{document}
>>> anon@lowtide:~/movie_scripts/snit$
>>
>> :) Just curious, what is this, vim?
>>
>
> latex.
>
> So, assuming the latex screenplay class is installed:
>
> `pdflatex snit.tex`
>
> will generate a pdf.
>
> On debian, `apt-get install texlive-full` pulled in the screenplay class
> along with everything else.
Okay, thanks. I considered guessing Latex, but I went with the wrong choice.
Is any of this automated, or do you have to type in all the backslashes and
"curly cue" brackets by hand?
--
Using slrn with Linux Mint Mate 17.1
[toc] | [prev] | [next] | [standalone]
| From | deplorable owl <owl@rooftop.invalid> |
|---|---|
| Date | 2017-01-23 19:42 +0000 |
| Message-ID | <ahbo03ga.bho94@rooftop.invalid> |
| In reply to | #391292 |
RonB <ronb02NOSPAM@gmail.com> wrote:
> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>> Screenplay Writing solutions for Linux users ... (I write this on the
>>>>> off-chance that someone who uses Linux and writes screenplays may do a
>>>>> Google search and find these options. I started a new thread because "Snit"
>>>>> hijacked the last one.)
>>>>>
>>>>> It wasn't that long ago that, if you wanted to write screenplays in Linux,
>>>>> you were limited to just a few choices.
>>>>>
>>>> ...
>>>>>
>>>>> And that's about it. I think there's also screenplay macros for vim, but I
>>>>> haven't tried them yet. I'll see if I can dig it up and try it out.
>>>>>
>>>>
>>>> http://i.imgur.com/jMNojwe.png
>>>>
>>>> anon@lowtide:~/movie_scripts/snit$ cat snit.tex
>>>> \documentclass{screenplay}
>>>> \begin{document}
>>>> \fadein
>>>>
>>>> \intslug[day]{snit's house}
>>>> An amorphous blob in the corner is backlit by the glow of a computer screen.
>>>>
>>>> \begin{dialogue}{snit}
>>>> Toasty, take a look at this color picker. It's got crayons.
>>>> \end{dialogue}
>>>>
>>>>
>>>> \begin{dialogue}{toasty}
>>>> If I were nine years old I might like that.
>>>> \end{dialogue}
>>>>
>>>>
>>>> \begin{dialogue}{snit}
>>>> I'm going to ignore your gaslighting.
>>>> \end{dialogue}
>>>>
>>>>
>>>> \extslug[evening]{snit's house}
>>>> Two men in white lab coats have just emerged from a van, and Toasty
>>>> is leading them to the front door.
>>>>
>>>> \fadeout
>>>> \end{document}
>>>> anon@lowtide:~/movie_scripts/snit$
>>>
>>> :) Just curious, what is this, vim?
>>>
>>
>> latex.
>>
>> So, assuming the latex screenplay class is installed:
>>
>> `pdflatex snit.tex`
>>
>> will generate a pdf.
>>
>> On debian, `apt-get install texlive-full` pulled in the screenplay class
>> along with everything else.
>
> Okay, thanks. I considered guessing Latex, but I went with the wrong choice.
> Is any of this automated, or do you have to type in all the backslashes and
> "curly cue" brackets by hand?
>
It's manual, but you could automate it. You could have launcher buttons
for each string, where the launcher commands are similar to:
#!/bin/bash
echo '\begin{dialogue}{}'|xsel -ib
echo '\begin{dialogue}{}'|xsel -ip
anon@lowtide:~$
Then you just click that launcher button and follow it with a
paste, either Edit->paste, or middle-click, and it would insert
'\begin{dialogue}{}' into your text. Then you just add the character's
name between the empty brackets. You could also add a launcher to build
and open the pdf, so you could get a quick look at your changes.
I'll set something up in Mate later and vid it and you'll see better
how it can work.
[toc] | [prev] | [next] | [standalone]
| From | deplorable owl <owl@rooftop.invalid> |
|---|---|
| Date | 2017-01-23 20:09 +0000 |
| Message-ID | <ahjb0ga.iu@rooftop.invalid> |
| In reply to | #391319 |
deplorable owl <owl@rooftop.invalid> wrote:
> RonB <ronb02NOSPAM@gmail.com> wrote:
>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>>> Screenplay Writing solutions for Linux users ... (I write this on the
>>>>>> off-chance that someone who uses Linux and writes screenplays may do a
>>>>>> Google search and find these options. I started a new thread because "Snit"
>>>>>> hijacked the last one.)
>>>>>>
>>>>>> It wasn't that long ago that, if you wanted to write screenplays in Linux,
>>>>>> you were limited to just a few choices.
>>>>>>
>>>>> ...
>>>>>>
>>>>>> And that's about it. I think there's also screenplay macros for vim, but I
>>>>>> haven't tried them yet. I'll see if I can dig it up and try it out.
>>>>>>
>>>>>
>>>>> http://i.imgur.com/jMNojwe.png
>>>>>
>>>>> anon@lowtide:~/movie_scripts/snit$ cat snit.tex
>>>>> \documentclass{screenplay}
>>>>> \begin{document}
>>>>> \fadein
>>>>>
>>>>> \intslug[day]{snit's house}
>>>>> An amorphous blob in the corner is backlit by the glow of a computer screen.
>>>>>
>>>>> \begin{dialogue}{snit}
>>>>> Toasty, take a look at this color picker. It's got crayons.
>>>>> \end{dialogue}
>>>>>
>>>>>
>>>>> \begin{dialogue}{toasty}
>>>>> If I were nine years old I might like that.
>>>>> \end{dialogue}
>>>>>
>>>>>
>>>>> \begin{dialogue}{snit}
>>>>> I'm going to ignore your gaslighting.
>>>>> \end{dialogue}
>>>>>
>>>>>
>>>>> \extslug[evening]{snit's house}
>>>>> Two men in white lab coats have just emerged from a van, and Toasty
>>>>> is leading them to the front door.
>>>>>
>>>>> \fadeout
>>>>> \end{document}
>>>>> anon@lowtide:~/movie_scripts/snit$
>>>>
>>>> :) Just curious, what is this, vim?
>>>>
>>>
>>> latex.
>>>
>>> So, assuming the latex screenplay class is installed:
>>>
>>> `pdflatex snit.tex`
>>>
>>> will generate a pdf.
>>>
>>> On debian, `apt-get install texlive-full` pulled in the screenplay class
>>> along with everything else.
>>
>> Okay, thanks. I considered guessing Latex, but I went with the wrong choice.
>> Is any of this automated, or do you have to type in all the backslashes and
>> "curly cue" brackets by hand?
>>
>
> It's manual, but you could automate it. You could have launcher buttons
> for each string, where the launcher commands are similar to:
>
> #!/bin/bash
> echo '\begin{dialogue}{}'|xsel -ib
> echo '\begin{dialogue}{}'|xsel -ip
> anon@lowtide:~$
>
> Then you just click that launcher button and follow it with a
> paste, either Edit->paste, or middle-click, and it would insert
> '\begin{dialogue}{}' into your text. Then you just add the character's
> name between the empty brackets. You could also add a launcher to build
> and open the pdf, so you could get a quick look at your changes.
>
> I'll set something up in Mate later and vid it and you'll see better
> how it can work.
>
Also, something like this can do the actual insert for you, without
requiring a paste:
anon@lowtide:~/code/xdotool$ cat begin_dialogue
#!/bin/bash
scriptname="snit.tex"
string="\begin{dialogue}{}"
scriptid=$(xwininfo -tree -root |grep ${scriptname} |awk '{print $1}')
xdotool type --window ${scriptid} ${string}
anon@lowtide:~/code/xdotool$
And you can use that as a skeleton for any other string. Just change
the scriptname and string to suit.
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2017-01-23 20:42 +0000 |
| Message-ID | <o65prm$qhc$1@dont-email.me> |
| In reply to | #391325 |
On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
> deplorable owl <owl@rooftop.invalid> wrote:
>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>>>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>>>> Screenplay Writing solutions for Linux users ... (I write this on the
>>>>>>> off-chance that someone who uses Linux and writes screenplays may do a
>>>>>>> Google search and find these options. I started a new thread because "Snit"
>>>>>>> hijacked the last one.)
>>>>>>>
>>>>>>> It wasn't that long ago that, if you wanted to write screenplays in Linux,
>>>>>>> you were limited to just a few choices.
>>>>>>>
>>>>>> ...
>>>>>>>
>>>>>>> And that's about it. I think there's also screenplay macros for vim, but I
>>>>>>> haven't tried them yet. I'll see if I can dig it up and try it out.
>>>>>>>
>>>>>>
>>>>>> http://i.imgur.com/jMNojwe.png
>>>>>>
>>>>>> anon@lowtide:~/movie_scripts/snit$ cat snit.tex
>>>>>> \documentclass{screenplay}
>>>>>> \begin{document}
>>>>>> \fadein
>>>>>>
>>>>>> \intslug[day]{snit's house}
>>>>>> An amorphous blob in the corner is backlit by the glow of a computer screen.
>>>>>>
>>>>>> \begin{dialogue}{snit}
>>>>>> Toasty, take a look at this color picker. It's got crayons.
>>>>>> \end{dialogue}
>>>>>>
>>>>>>
>>>>>> \begin{dialogue}{toasty}
>>>>>> If I were nine years old I might like that.
>>>>>> \end{dialogue}
>>>>>>
>>>>>>
>>>>>> \begin{dialogue}{snit}
>>>>>> I'm going to ignore your gaslighting.
>>>>>> \end{dialogue}
>>>>>>
>>>>>>
>>>>>> \extslug[evening]{snit's house}
>>>>>> Two men in white lab coats have just emerged from a van, and Toasty
>>>>>> is leading them to the front door.
>>>>>>
>>>>>> \fadeout
>>>>>> \end{document}
>>>>>> anon@lowtide:~/movie_scripts/snit$
>>>>>
>>>>> :) Just curious, what is this, vim?
>>>>>
>>>>
>>>> latex.
>>>>
>>>> So, assuming the latex screenplay class is installed:
>>>>
>>>> `pdflatex snit.tex`
>>>>
>>>> will generate a pdf.
>>>>
>>>> On debian, `apt-get install texlive-full` pulled in the screenplay class
>>>> along with everything else.
>>>
>>> Okay, thanks. I considered guessing Latex, but I went with the wrong choice.
>>> Is any of this automated, or do you have to type in all the backslashes and
>>> "curly cue" brackets by hand?
>>>
>>
>> It's manual, but you could automate it. You could have launcher buttons
>> for each string, where the launcher commands are similar to:
>>
>> #!/bin/bash
>> echo '\begin{dialogue}{}'|xsel -ib
>> echo '\begin{dialogue}{}'|xsel -ip
>> anon@lowtide:~$
>>
>> Then you just click that launcher button and follow it with a
>> paste, either Edit->paste, or middle-click, and it would insert
>> '\begin{dialogue}{}' into your text. Then you just add the character's
>> name between the empty brackets. You could also add a launcher to build
>> and open the pdf, so you could get a quick look at your changes.
>>
>> I'll set something up in Mate later and vid it and you'll see better
>> how it can work.
>>
>
> Also, something like this can do the actual insert for you, without
> requiring a paste:
>
> anon@lowtide:~/code/xdotool$ cat begin_dialogue
> #!/bin/bash
> scriptname="snit.tex"
> string="\begin{dialogue}{}"
> scriptid=$(xwininfo -tree -root |grep ${scriptname} |awk '{print $1}')
> xdotool type --window ${scriptid} ${string}
> anon@lowtide:~/code/xdotool$
>
> And you can use that as a skeleton for any other string. Just change
> the scriptname and string to suit.
Okay. Learning a little about the capabilities of LaTeX (I've heard good
things about it), but (in this case) it would still read like code instead
of English.
A comparison ...
~~
\documentclass{screenplay}
\begin{document}
\fadein
\intslug[day]{snit's house}
An amorphous blob in the corner is backlit by the glow of a computer
screen.
\begin{dialogue}{snit}
Toasty, take a look at this color picker. It's got crayons.
\end{dialogue}
vs.
FADE IN:
int. snit's house - day
An amorphous blob in the corner is backlit by the glow of a computer
screen.
SNIT
Toasty, take a look at this color picker. It's got crayons.
~~
(Scene headings (slugs) automatically capitalize when parsed.)
At any rate, for what it's worth.
--
Using slrn with Linux Mint Mate 17.1
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2017-01-23 13:45 -0700 |
| Message-ID | <D4ABB973.8B73F%usenet@gallopinginsanity.com> |
| In reply to | #391347 |
On 1/23/17, 1:42 PM, in article o65prm$qhc$1@dont-email.me, "RonB"
<ronb02NOSPAM@gmail.com> wrote:
> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>> deplorable owl <owl@rooftop.invalid> wrote:
>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>>>>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>>>>> Screenplay Writing solutions for Linux users ... (I write this on the
>>>>>>>> off-chance that someone who uses Linux and writes screenplays may do a
>>>>>>>> Google search and find these options. I started a new thread because
>>>>>>>> "Snit"
>>>>>>>> hijacked the last one.)
>>>>>>>>
>>>>>>>> It wasn't that long ago that, if you wanted to write screenplays in
>>>>>>>> Linux,
>>>>>>>> you were limited to just a few choices.
>>>>>>>>
>>>>>>> ...
>>>>>>>>
>>>>>>>> And that's about it. I think there's also screenplay macros for vim,
>>>>>>>> but I
>>>>>>>> haven't tried them yet. I'll see if I can dig it up and try it out.
>>>>>>>>
>>>>>>>
>>>>>>> http://i.imgur.com/jMNojwe.png
>>>>>>>
>>>>>>> anon@lowtide:~/movie_scripts/snit$ cat snit.tex
>>>>>>> \documentclass{screenplay}
>>>>>>> \begin{document}
>>>>>>> \fadein
>>>>>>>
>>>>>>> \intslug[day]{snit's house}
>>>>>>> An amorphous blob in the corner is backlit by the glow of a computer
>>>>>>> screen.
>>>>>>>
>>>>>>> \begin{dialogue}{snit}
>>>>>>> Toasty, take a look at this color picker. It's got crayons.
>>>>>>> \end{dialogue}
>>>>>>>
>>>>>>>
>>>>>>> \begin{dialogue}{toasty}
>>>>>>> If I were nine years old I might like that.
>>>>>>> \end{dialogue}
>>>>>>>
>>>>>>>
>>>>>>> \begin{dialogue}{snit}
>>>>>>> I'm going to ignore your gaslighting.
>>>>>>> \end{dialogue}
>>>>>>>
>>>>>>>
>>>>>>> \extslug[evening]{snit's house}
>>>>>>> Two men in white lab coats have just emerged from a van, and Toasty
>>>>>>> is leading them to the front door.
>>>>>>>
>>>>>>> \fadeout
>>>>>>> \end{document}
>>>>>>> anon@lowtide:~/movie_scripts/snit$
>>>>>>
>>>>>> :) Just curious, what is this, vim?
>>>>>>
>>>>>
>>>>> latex.
>>>>>
>>>>> So, assuming the latex screenplay class is installed:
>>>>>
>>>>> `pdflatex snit.tex`
>>>>>
>>>>> will generate a pdf.
>>>>>
>>>>> On debian, `apt-get install texlive-full` pulled in the screenplay class
>>>>> along with everything else.
>>>>
>>>> Okay, thanks. I considered guessing Latex, but I went with the wrong
>>>> choice.
>>>> Is any of this automated, or do you have to type in all the backslashes and
>>>> "curly cue" brackets by hand?
>>>>
>>>
>>> It's manual, but you could automate it. You could have launcher buttons
>>> for each string, where the launcher commands are similar to:
>>>
>>> #!/bin/bash
>>> echo '\begin{dialogue}{}'|xsel -ib
>>> echo '\begin{dialogue}{}'|xsel -ip
>>> anon@lowtide:~$
>>>
>>> Then you just click that launcher button and follow it with a
>>> paste, either Edit->paste, or middle-click, and it would insert
>>> '\begin{dialogue}{}' into your text. Then you just add the character's
>>> name between the empty brackets. You could also add a launcher to build
>>> and open the pdf, so you could get a quick look at your changes.
>>>
>>> I'll set something up in Mate later and vid it and you'll see better
>>> how it can work.
>>>
>>
>> Also, something like this can do the actual insert for you, without
>> requiring a paste:
>>
>> anon@lowtide:~/code/xdotool$ cat begin_dialogue
>> #!/bin/bash
>> scriptname="snit.tex"
>> string="\begin{dialogue}{}"
>> scriptid=$(xwininfo -tree -root |grep ${scriptname} |awk '{print $1}')
>> xdotool type --window ${scriptid} ${string}
>> anon@lowtide:~/code/xdotool$
>>
>> And you can use that as a skeleton for any other string. Just change
>> the scriptname and string to suit.
>
> Okay. Learning a little about the capabilities of LaTeX (I've heard good
> things about it), but (in this case) it would still read like code instead
> of English.
>
> A comparison ...
>
> ~~
> \documentclass{screenplay}
> \begin{document}
> \fadein
>
> \intslug[day]{snit's house}
> An amorphous blob in the corner is backlit by the glow of a computer
> screen.
>
> \begin{dialogue}{snit}
> Toasty, take a look at this color picker. It's got crayons.
> \end{dialogue}
>
> vs.
>
> FADE IN:
>
> int. snit's house - day
>
> An amorphous blob in the corner is backlit by the glow of a computer
> screen.
>
> SNIT
> Toasty, take a look at this color picker. It's got crayons.
> ~~
>
> (Scene headings (slugs) automatically capitalize when parsed.)
>
> At any rate, for what it's worth.
You started this thread with a claimed desire to not have it be about me...
but you failed and are still obsessed.
--
"It is absurd to punish anyone for having sex with someone of age 15 ‹ it is
normal for Americans of age 15 to have sex." -- Richard Stallman
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2017-01-23 20:17 +0000 |
| Message-ID | <o65ocv$koj$1@dont-email.me> |
| In reply to | #391319 |
On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
> RonB <ronb02NOSPAM@gmail.com> wrote:
>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>>> Screenplay Writing solutions for Linux users ... (I write this on the
>>>>>> off-chance that someone who uses Linux and writes screenplays may do a
>>>>>> Google search and find these options. I started a new thread because "Snit"
>>>>>> hijacked the last one.)
>>>>>>
>>>>>> It wasn't that long ago that, if you wanted to write screenplays in Linux,
>>>>>> you were limited to just a few choices.
>>>>>>
>>>>> ...
>>>>>>
>>>>>> And that's about it. I think there's also screenplay macros for vim, but I
>>>>>> haven't tried them yet. I'll see if I can dig it up and try it out.
>>>>>>
>>>>>
>>>>> http://i.imgur.com/jMNojwe.png
>>>>>
>>>>> anon@lowtide:~/movie_scripts/snit$ cat snit.tex
>>>>> \documentclass{screenplay}
>>>>> \begin{document}
>>>>> \fadein
>>>>>
>>>>> \intslug[day]{snit's house}
>>>>> An amorphous blob in the corner is backlit by the glow of a computer screen.
>>>>>
>>>>> \begin{dialogue}{snit}
>>>>> Toasty, take a look at this color picker. It's got crayons.
>>>>> \end{dialogue}
>>>>>
>>>>>
>>>>> \begin{dialogue}{toasty}
>>>>> If I were nine years old I might like that.
>>>>> \end{dialogue}
>>>>>
>>>>>
>>>>> \begin{dialogue}{snit}
>>>>> I'm going to ignore your gaslighting.
>>>>> \end{dialogue}
>>>>>
>>>>>
>>>>> \extslug[evening]{snit's house}
>>>>> Two men in white lab coats have just emerged from a van, and Toasty
>>>>> is leading them to the front door.
>>>>>
>>>>> \fadeout
>>>>> \end{document}
>>>>> anon@lowtide:~/movie_scripts/snit$
>>>>
>>>> :) Just curious, what is this, vim?
>>>>
>>>
>>> latex.
>>>
>>> So, assuming the latex screenplay class is installed:
>>>
>>> `pdflatex snit.tex`
>>>
>>> will generate a pdf.
>>>
>>> On debian, `apt-get install texlive-full` pulled in the screenplay class
>>> along with everything else.
>>
>> Okay, thanks. I considered guessing Latex, but I went with the wrong choice.
>> Is any of this automated, or do you have to type in all the backslashes and
>> "curly cue" brackets by hand?
>>
>
> It's manual, but you could automate it. You could have launcher buttons
> for each string, where the launcher commands are similar to:
>
> #!/bin/bash
> echo '\begin{dialogue}{}'|xsel -ib
> echo '\begin{dialogue}{}'|xsel -ip
> anon@lowtide:~$
>
> Then you just click that launcher button and follow it with a
> paste, either Edit->paste, or middle-click, and it would insert
> '\begin{dialogue}{}' into your text. Then you just add the character's
> name between the empty brackets. You could also add a launcher to build
> and open the pdf, so you could get a quick look at your changes.
>
> I'll set something up in Mate later and vid it and you'll see better
> how it can work.
Honestly this is a lot of extra work when compared to Fountain. The beauty
of the Fountain mark up language is that you just type in text (with a few
exceptions) and the parser takes care of the rest. You retain the natural
flow of writing and, when reading the text file, it looks almost like a
screenplay, instead of like code. You can also do other things with the file
besides print to PDF -- again, using the parser (like importing to most of
the screenplay formatters I listed). I've got a feeling LaTeX is designed
for bigger blocks of uninterrupted text, screenplays (by their nature) are
broken up into small elements -- not ideal for for LaTeX.
--
Using slrn with Linux Mint Mate 17.1
[toc] | [prev] | [next] | [standalone]
| From | deplorable owl <owl@rooftop.invalid> |
|---|---|
| Date | 2017-01-23 20:40 +0000 |
| Message-ID | <aiadb03.ho@rooftop.invalid> |
| In reply to | #391333 |
RonB <ronb02NOSPAM@gmail.com> wrote:
> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>>>>>> RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>>>> Screenplay Writing solutions for Linux users ... (I write this on the
>>>>>>> off-chance that someone who uses Linux and writes screenplays may do a
>>>>>>> Google search and find these options. I started a new thread because "Snit"
>>>>>>> hijacked the last one.)
>>>>>>>
>>>>>>> It wasn't that long ago that, if you wanted to write screenplays in Linux,
>>>>>>> you were limited to just a few choices.
>>>>>>>
>>>>>> ...
>>>>>>>
>>>>>>> And that's about it. I think there's also screenplay macros for vim, but I
>>>>>>> haven't tried them yet. I'll see if I can dig it up and try it out.
>>>>>>>
>>>>>>
>>>>>> http://i.imgur.com/jMNojwe.png
>>>>>>
>>>>>> anon@lowtide:~/movie_scripts/snit$ cat snit.tex
>>>>>> \documentclass{screenplay}
>>>>>> \begin{document}
>>>>>> \fadein
>>>>>>
>>>>>> \intslug[day]{snit's house}
>>>>>> An amorphous blob in the corner is backlit by the glow of a computer screen.
>>>>>>
>>>>>> \begin{dialogue}{snit}
>>>>>> Toasty, take a look at this color picker. It's got crayons.
>>>>>> \end{dialogue}
>>>>>>
>>>>>>
>>>>>> \begin{dialogue}{toasty}
>>>>>> If I were nine years old I might like that.
>>>>>> \end{dialogue}
>>>>>>
>>>>>>
>>>>>> \begin{dialogue}{snit}
>>>>>> I'm going to ignore your gaslighting.
>>>>>> \end{dialogue}
>>>>>>
>>>>>>
>>>>>> \extslug[evening]{snit's house}
>>>>>> Two men in white lab coats have just emerged from a van, and Toasty
>>>>>> is leading them to the front door.
>>>>>>
>>>>>> \fadeout
>>>>>> \end{document}
>>>>>> anon@lowtide:~/movie_scripts/snit$
>>>>>
>>>>> :) Just curious, what is this, vim?
>>>>>
>>>>
>>>> latex.
>>>>
>>>> So, assuming the latex screenplay class is installed:
>>>>
>>>> `pdflatex snit.tex`
>>>>
>>>> will generate a pdf.
>>>>
>>>> On debian, `apt-get install texlive-full` pulled in the screenplay class
>>>> along with everything else.
>>>
>>> Okay, thanks. I considered guessing Latex, but I went with the wrong choice.
>>> Is any of this automated, or do you have to type in all the backslashes and
>>> "curly cue" brackets by hand?
>>>
>>
>> It's manual, but you could automate it. You could have launcher buttons
>> for each string, where the launcher commands are similar to:
>>
>> #!/bin/bash
>> echo '\begin{dialogue}{}'|xsel -ib
>> echo '\begin{dialogue}{}'|xsel -ip
>> anon@lowtide:~$
>>
>> Then you just click that launcher button and follow it with a
>> paste, either Edit->paste, or middle-click, and it would insert
>> '\begin{dialogue}{}' into your text. Then you just add the character's
>> name between the empty brackets. You could also add a launcher to build
>> and open the pdf, so you could get a quick look at your changes.
>>
>> I'll set something up in Mate later and vid it and you'll see better
>> how it can work.
>
> Honestly this is a lot of extra work when compared to Fountain. The beauty
> of the Fountain mark up language is that you just type in text (with a few
> exceptions) and the parser takes care of the rest. You retain the natural
> flow of writing and, when reading the text file, it looks almost like a
> screenplay, instead of like code.
You can add the latex markup later with button clicks.
> You can also do other things with the file
> besides print to PDF -- again, using the parser (like importing to most of
> the screenplay formatters I listed). I've got a feeling LaTeX is designed
> for bigger blocks of uninterrupted text, screenplays (by their nature) are
> broken up into small elements -- not ideal for for LaTeX.
>
Well, you can choose latex instead of pdflatex, and generate a dvi,
then use dvi2tty to get formatted ascii output that you can send to
a text file:
anon@lowtide:~/movie_scripts/snit$ dvi2tty snit.dvi
1
FADE IN:
INT. SNIT'S HOUSE DAY
An amorphous blob in the corner is backlit by the glow of a
computer screen.
SNIT
Toasty, take a look at this
color picker. It's got crayons.
TOASTY
If I were nine years old I might
like that.
SNIT
I'm going to ignore your
gaslighting.
EXT. SNIT'S HOUSE EVENING
Two men in white lab coats have just emerged from a van, and
Toasty is leading them to the front door.
FADE OUT:
anon@lowtide:~/movie_scripts/snit$
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2017-01-23 12:46 -0800 |
| Message-ID | <e25525ab-0ef2-43f9-8415-c7af843f5d83@googlegroups.com> |
| In reply to | #391343 |
On Monday, January 23, 2017 at 1:41:00 PM UTC-7, deplorable owl wrote:
> RonB <ronb02NOSPAM@gmail.com> wrote:
> > On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
> >> RonB <ronb02NOSPAM@gmail.com> wrote:
> >>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
> >>>> RonB <ronb02NOSPAM@gmail.com> wrote:
> >>>>> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
> >>>>>> RonB <ronb02NOSPAM@gmail.com> wrote:
> >>>>>>> Screenplay Writing solutions for Linux users ... (I write this on the
> >>>>>>> off-chance that someone who uses Linux and writes screenplays may do a
> >>>>>>> Google search and find these options. I started a new thread because "Snit"
> >>>>>>> hijacked the last one.)
> >>>>>>>
> >>>>>>> It wasn't that long ago that, if you wanted to write screenplays in Linux,
> >>>>>>> you were limited to just a few choices.
> >>>>>>>
> >>>>>> ...
> >>>>>>>
> >>>>>>> And that's about it. I think there's also screenplay macros for vim, but I
> >>>>>>> haven't tried them yet. I'll see if I can dig it up and try it out.
> >>>>>>>
> >>>>>>
> >>>>>> http://i.imgur.com/jMNojwe.png
> >>>>>>
> >>>>>> anon@lowtide:~/movie_scripts/snit$ cat snit.tex
> >>>>>> \documentclass{screenplay}
> >>>>>> \begin{document}
> >>>>>> \fadein
> >>>>>>
> >>>>>> \intslug[day]{snit's house}
> >>>>>> An amorphous blob in the corner is backlit by the glow of a computer screen.
> >>>>>>
> >>>>>> \begin{dialogue}{snit}
> >>>>>> Toasty, take a look at this color picker. It's got crayons.
> >>>>>> \end{dialogue}
> >>>>>>
> >>>>>>
> >>>>>> \begin{dialogue}{toasty}
> >>>>>> If I were nine years old I might like that.
> >>>>>> \end{dialogue}
> >>>>>>
> >>>>>>
> >>>>>> \begin{dialogue}{snit}
> >>>>>> I'm going to ignore your gaslighting.
> >>>>>> \end{dialogue}
> >>>>>>
> >>>>>>
> >>>>>> \extslug[evening]{snit's house}
> >>>>>> Two men in white lab coats have just emerged from a van, and Toasty
> >>>>>> is leading them to the front door.
> >>>>>>
> >>>>>> \fadeout
> >>>>>> \end{document}
> >>>>>> anon@lowtide:~/movie_scripts/snit$
> >>>>>
> >>>>> :) Just curious, what is this, vim?
> >>>>>
> >>>>
> >>>> latex.
> >>>>
> >>>> So, assuming the latex screenplay class is installed:
> >>>>
> >>>> `pdflatex snit.tex`
> >>>>
> >>>> will generate a pdf.
> >>>>
> >>>> On debian, `apt-get install texlive-full` pulled in the screenplay class
> >>>> along with everything else.
> >>>
> >>> Okay, thanks. I considered guessing Latex, but I went with the wrong choice.
> >>> Is any of this automated, or do you have to type in all the backslashes and
> >>> "curly cue" brackets by hand?
> >>>
> >>
> >> It's manual, but you could automate it. You could have launcher buttons
> >> for each string, where the launcher commands are similar to:
> >>
> >> #!/bin/bash
> >> echo '\begin{dialogue}{}'|xsel -ib
> >> echo '\begin{dialogue}{}'|xsel -ip
> >> anon@lowtide:~$
> >>
> >> Then you just click that launcher button and follow it with a
> >> paste, either Edit->paste, or middle-click, and it would insert
> >> '\begin{dialogue}{}' into your text. Then you just add the character's
> >> name between the empty brackets. You could also add a launcher to build
> >> and open the pdf, so you could get a quick look at your changes.
> >>
> >> I'll set something up in Mate later and vid it and you'll see better
> >> how it can work.
> >
> > Honestly this is a lot of extra work when compared to Fountain. The beauty
> > of the Fountain mark up language is that you just type in text (with a few
> > exceptions) and the parser takes care of the rest. You retain the natural
> > flow of writing and, when reading the text file, it looks almost like a
> > screenplay, instead of like code.
>
>
> You can add the latex markup later with button clicks.
>
>
> > You can also do other things with the file
> > besides print to PDF -- again, using the parser (like importing to most of
> > the screenplay formatters I listed). I've got a feeling LaTeX is designed
> > for bigger blocks of uninterrupted text, screenplays (by their nature) are
> > broken up into small elements -- not ideal for for LaTeX.
> >
>
> Well, you can choose latex instead of pdflatex, and generate a dvi,
> then use dvi2tty to get formatted ascii output that you can send to
> a text file:
>
> anon@lowtide:~/movie_scripts/snit$ dvi2tty snit.dvi
> 1
>
>
>
> FADE IN:
>
>
> INT. SNIT'S HOUSE DAY
>
>
> An amorphous blob in the corner is backlit by the glow of a
> computer screen.
>
>
> SNIT
> Toasty, take a look at this
> color picker. It's got crayons.
>
>
> TOASTY
> If I were nine years old I might
> like that.
>
>
> SNIT
> I'm going to ignore your
> gaslighting.
EDIT: Are we still on for tonight?
>
>
> EXT. SNIT'S HOUSE EVENING
>
>
> Two men in white lab coats have just emerged from a van, and
> Toasty is leading them to the front door
EDIT: ... as he takes his pay and heads to the phone to call ChildBear Protection Services.
>
>
> FADE OUT:
> anon@lowtide:~/movie_scripts/snit$
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2017-01-23 22:45 +0000 |
| Message-ID | <o6611f$mb9$1@dont-email.me> |
| In reply to | #391343 |
On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
> RonB <ronb02NOSPAM@gmail.com> wrote:
>> Honestly this is a lot of extra work when compared to Fountain. The beauty
>> of the Fountain mark up language is that you just type in text (with a few
>> exceptions) and the parser takes care of the rest. You retain the natural
>> flow of writing and, when reading the text file, it looks almost like a
>> screenplay, instead of like code.
>
> You can add the latex markup later with button clicks.
That adds a whole level of unnecessary work when you can use Fountain.
>> You can also do other things with the file
>> besides print to PDF -- again, using the parser (like importing to most of
>> the screenplay formatters I listed). I've got a feeling LaTeX is designed
>> for bigger blocks of uninterrupted text, screenplays (by their nature) are
>> broken up into small elements -- not ideal for for LaTeX.
>
> Well, you can choose latex instead of pdflatex, and generate a dvi,
> then use dvi2tty to get formatted ascii output that you can send to
> a text file:
>
> anon@lowtide:~/movie_scripts/snit$ dvi2tty snit.dvi
> 1
>
>
>
> FADE IN:
>
>
> INT. SNIT'S HOUSE DAY
>
>
> An amorphous blob in the corner is backlit by the glow of a
> computer screen.
>
>
> SNIT
> Toasty, take a look at this
> color picker. It's got crayons.
>
>
> TOASTY
> If I were nine years old I might
> like that.
>
>
> SNIT
> I'm going to ignore your
> gaslighting.
>
>
> EXT. SNIT'S HOUSE EVENING
>
>
> Two men in white lab coats have just emerged from a van, and
> Toasty is leading them to the front door.
>
>
> FADE OUT:
> anon@lowtide:~/movie_scripts/snit$
That's good to know. I'm guessing the extra spaces between elements can be
removed. But using Fountain and a parser application is "cleaner." I took
your text, removed the extra spaces and inserted the hyphens (in the
sluglines) then saved it as a text file with a .fountain extension. I read
that file into Trelby and saved it as formatted text file, then read it into
jstar (my slrn editor) ...
~~
FADE IN:
INT. SNIT'S HOUSE - DAY
An amorphous blob in the corner is backlit by the glow of a
computer screen.
SNIT
Toasty, take a look at this color
picker. It's got crayons.
TOASTY
If I were nine years old I might
like that.
SNIT
I'm going to ignore your
gaslighting.
EXT. SNIT'S HOUSE - EVENING
Two men in white lab coats have just emerged from a van, and
Toasty is leading them to the front door.
FADE OUT:
~~
In my opinion, sometimes a specialized tool (Fountain, in this case) is
better than adapting another tool (LaTeX in this case), especially when that
specialized tool is accepted as a "standard" -- and Fountain is well on the
way to being accepted as a standard.
And a note to "Snit." Quit being an asshole and we'll quit treating you like
one.
--
Using slrn with Linux Mint Mate 17.1
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2017-01-23 15:52 -0700 |
| Message-ID | <D4ABD755.8B778%usenet@gallopinginsanity.com> |
| In reply to | #391368 |
On 1/23/17, 3:45 PM, in article o6611f$mb9$1@dont-email.me, "RonB" <ronb02NOSPAM@gmail.com> wrote: ... >> anon@lowtide:~/movie_scripts/snit$ dvi2tty snit.dvi ... >> INT. SNIT'S HOUSE DAY ... >> SNIT ... >> SNIT ... >> EXT. SNIT'S HOUSE EVENING ... >> anon@lowtide:~/movie_scripts/snit$ ... > INT. SNIT'S HOUSE - DAY ... > SNIT ... > SNIT ... ... > And a note to "Snit." Quit being an asshole and we'll quit treating you like > one. You obsess over me because you know I will *NEVER* sink to your level. You do so out of your own insecurity, not out of me doing anything wrong. Face it: those of you who troll COLA nit-pick my every word and seek to find me being as inappropriate as you are. And you fail. Clearly drives you crazy. -- "There are 'extremists' in the free software world, but that's one major reason why I don't call what I do 'free software' any more. I don't want to be associated with the people for whom it's about exclusion and hatred." -- Linus Torvalds
[toc] | [prev] | [next] | [standalone]
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| Date | 2017-01-23 16:00 -0700 |
| Message-ID | <D4ABD92A.8B786%usenet@gallopinginsanity.com> |
| In reply to | #391368 |
On 1/23/17, 3:45 PM, in article o6611f$mb9$1@dont-email.me, "RonB" <ronb02NOSPAM@gmail.com> wrote: > And a note to "Snit." Quit being an asshole and we'll quit treating you like > one. Hey, let me give you another chance: give specific examples of what you want me to change -- with specific quotes from me where you think I do as you accuse -- and I will consider it. Sincerely. *IF* you are not just trolling then certainly you can find some recent examples (if you cannot then I have done as you asked and already stopped). I suspect you will go back to holding me accountable for the actions of others, asking me to lie about Linux, etc. But, hey, as I said I am happy to give you a chance, even if I suspect you will fall on your face. Would welcome you proving me wrong. As I generally am, I will be open and note that if you show me doing X and it is easy to find "advocates" doing X I will not shy away from showing your hypocrisy. Best of luck to you. -- "It is absurd to punish anyone for having sex with someone of age 15 ‹ it is normal for Americans of age 15 to have sex." -- Richard Stallman
[toc] | [prev] | [next] | [standalone]
| From | deplorable owl <owl@rooftop.invalid> |
|---|---|
| Date | 2017-01-24 03:10 +0000 |
| Message-ID | <ab803g.hi3o@rooftop.invalid> |
| In reply to | #391368 |
RonB <ronb02NOSPAM@gmail.com> wrote:
> On 2017-01-23, deplorable owl <owl@rooftop.invalid> wrote:
>> RonB <ronb02NOSPAM@gmail.com> wrote:
>
>>> Honestly this is a lot of extra work when compared to Fountain. The beauty
>>> of the Fountain mark up language is that you just type in text (with a few
>>> exceptions) and the parser takes care of the rest. You retain the natural
>>> flow of writing and, when reading the text file, it looks almost like a
>>> screenplay, instead of like code.
>>
>> You can add the latex markup later with button clicks.
>
> That adds a whole level of unnecessary work when you can use Fountain.
>
>>> You can also do other things with the file
>>> besides print to PDF -- again, using the parser (like importing to most of
>>> the screenplay formatters I listed). I've got a feeling LaTeX is designed
>>> for bigger blocks of uninterrupted text, screenplays (by their nature) are
>>> broken up into small elements -- not ideal for for LaTeX.
>>
>> Well, you can choose latex instead of pdflatex, and generate a dvi,
>> then use dvi2tty to get formatted ascii output that you can send to
>> a text file:
>>
>> anon@lowtide:~/movie_scripts/snit$ dvi2tty snit.dvi
>> 1
>>
>>
>>
>> FADE IN:
>>
>>
>> INT. SNIT'S HOUSE DAY
>>
>>
>> An amorphous blob in the corner is backlit by the glow of a
>> computer screen.
>>
>>
>> SNIT
>> Toasty, take a look at this
>> color picker. It's got crayons.
>>
>>
>> TOASTY
>> If I were nine years old I might
>> like that.
>>
>>
>> SNIT
>> I'm going to ignore your
>> gaslighting.
>>
>>
>> EXT. SNIT'S HOUSE EVENING
>>
>>
>> Two men in white lab coats have just emerged from a van, and
>> Toasty is leading them to the front door.
>>
>>
>> FADE OUT:
>> anon@lowtide:~/movie_scripts/snit$
>
> That's good to know. I'm guessing the extra spaces between elements can be
> removed. But using Fountain and a parser application is "cleaner." I took
> your text, removed the extra spaces and inserted the hyphens (in the
> sluglines) then saved it as a text file with a .fountain extension. I read
> that file into Trelby and saved it as formatted text file, then read it into
> jstar (my slrn editor) ...
>
> ~~
> FADE IN:
>
> INT. SNIT'S HOUSE - DAY
>
> An amorphous blob in the corner is backlit by the glow of a
> computer screen.
>
> SNIT
> Toasty, take a look at this color
> picker. It's got crayons.
>
> TOASTY
> If I were nine years old I might
> like that.
>
> SNIT
> I'm going to ignore your
> gaslighting.
>
> EXT. SNIT'S HOUSE - EVENING
>
> Two men in white lab coats have just emerged from a van, and
> Toasty is leading them to the front door.
>
> FADE OUT:
> ~~
>
> In my opinion, sometimes a specialized tool (Fountain, in this case) is
> better than adapting another tool (LaTeX in this case), especially when that
> specialized tool is accepted as a "standard" -- and Fountain is well on the
> way to being accepted as a standard.
>
> And a note to "Snit." Quit being an asshole and we'll quit treating you like
> one.
>
Whatever serves your needs best, but taking a look at Fountain, it seems
you need to massage the input at least as much as for latex. For instance,
capitalization rules, etc.
The "-" in the intslug can be done with:
\renewcommand*{\slugspace}{ - }
at the beginning of the document.
The dvi2tty output line spacing can be controlled with "-v" option.
(-v700000 seems to make it about right).
Now bash/sed can help with some of the latex markup. Notice the
dialog sections below ('%' is a latex comment):
anon@lowtide:~/movie_scripts/snit$ cat test.tex
\documentclass{screenplay}
\begin{document}
\fadein
\renewcommand*{\slugspace}{ - }
\intslug[day]{snit's house}
An amorphous blob in the corner is backlit by the glow of a computer screen.
%snit
Toasty, take a look at this color picker. It's got crayons.
%-
%toasty
If I were nine years old I might like that.
%-
%snit
I'm going to ignore your gaslighting.
%-
\extslug[evening]{snit's house}
Two men in white lab coats have just emerged from a van, and Toasty
is leading them to the front door.
\fadeout
\end{document}
anon@lowtide:~/movie_scripts/snit$
anon@lowtide:~/movie_scripts/snit$ cat dia
#!/bin/bash
sed -e 's/\(^%\([a-zA-Z]*\)$\)/\1\n\\begin{dialogue}{\2}/g' -\
| sed 's/\(^%-$\)/\\end{dialogue}\n\1/g' >out.tex
latex out.tex >/dev/null; dvi2tty -v700000 out.dvi
anon@lowtide:~/movie_scripts/snit$
anon@lowtide:~/movie_scripts/snit$ ./dia <test.tex
1
FADE IN:
INT. SNIT'S HOUSE - DAY
An amorphous blob in the corner is backlit by the glow of a
computer screen.
SNIT
Toasty, take a look at this
color picker. It's got crayons.
TOASTY
If I were nine years old I might
like that.
SNIT
I'm going to ignore your
gaslighting.
EXT. SNIT'S HOUSE - EVENING
Two men in white lab coats have just emerged from a van, and
Toasty is leading them to the front door.
FADE OUT:
anon@lowtide:~/movie_scripts/snit$
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2017-01-24 04:17 +0000 |
| Message-ID | <o66kh1$6ck$1@dont-email.me> |
| In reply to | #391454 |
On 2017-01-24, deplorable owl <owl@rooftop.invalid> wrote:
>
> Whatever serves your needs best, but taking a look at Fountain, it seems
> you need to massage the input at least as much as for latex. For instance,
> capitalization rules, etc.
I guess if you're used to looking "around" the code in LaTeX it would be
automatic and unnoticeable. But for someone who hasn't used LaTeX it looks
like a royal mess.
As for "massaging" Fountain, it's not that big of a deal because character
names are capitalized in screenplays (above the dialog) anyhow. That's
really about the only thing you need to worry about -- otherwise it's just
mostly flowing text and line breaks. (I should mention, you fully capitalize
a name when it first appears because that's a screenplay norm.)
> The "-" in the intslug can be done with:
> \renewcommand*{\slugspace}{ - }
> at the beginning of the document.
>
> The dvi2tty output line spacing can be controlled with "-v" option.
> (-v700000 seems to make it about right).
I'm guessing you could also find a way to include "wrylies" (the little
comment in parenthesis under the name and before dialog) but it becomes
complicated.
> Now bash/sed can help with some of the latex markup. Notice the
> dialog sections below ('%' is a latex comment):
>
> anon@lowtide:~/movie_scripts/snit$ cat test.tex
> \documentclass{screenplay}
> \begin{document}
> \fadein
>
> \renewcommand*{\slugspace}{ - }
>
> \intslug[day]{snit's house}
> An amorphous blob in the corner is backlit by the glow of a computer screen.
>
> %snit
> Toasty, take a look at this color picker. It's got crayons.
> %-
>
> %toasty
> If I were nine years old I might like that.
> %-
>
> %snit
> I'm going to ignore your gaslighting.
> %-
>
> \extslug[evening]{snit's house}
> Two men in white lab coats have just emerged from a van, and Toasty
> is leading them to the front door.
>
> \fadeout
> \end{document}
> anon@lowtide:~/movie_scripts/snit$
>
> anon@lowtide:~/movie_scripts/snit$ cat dia
> #!/bin/bash
> sed -e 's/\(^%\([a-zA-Z]*\)$\)/\1\n\\begin{dialogue}{\2}/g' -\
>| sed 's/\(^%-$\)/\\end{dialogue}\n\1/g' >out.tex
> latex out.tex >/dev/null; dvi2tty -v700000 out.dvi
> anon@lowtide:~/movie_scripts/snit$
>
> anon@lowtide:~/movie_scripts/snit$ ./dia <test.tex
1
I'm getting glossy-eyed. Sorry. But I have Fountain. I don't need to do all
this. For me, it's like reinventing the wheel.
> FADE IN:
>
> INT. SNIT'S HOUSE - DAY
>
> An amorphous blob in the corner is backlit by the glow of a
> computer screen.
>
> SNIT
> Toasty, take a look at this
> color picker. It's got crayons.
>
> TOASTY
> If I were nine years old I might
> like that.
>
> SNIT
> I'm going to ignore your
> gaslighting.
>
> EXT. SNIT'S HOUSE - EVENING
>
> Two men in white lab coats have just emerged from a van, and
> Toasty is leading them to the front door.
>
> FADE OUT:
> anon@lowtide:~/movie_scripts/snit$
I figured you could tweak the output but you're not going to get many
writers to go through this much trouble when they've already got something
that works perfectly with a whole let less work.
Another advantage of using Fountain is that you can set up the the format on
your parser application (for example A4 vs Letter paper, size of top/bottom
margins, etc.) and the position of the elements -- sluglines, action,
character names, wrylies, dialog, transitions, two or one line between
scenes, etc. -- import correctly. The Fountain markup language is totally
independent of any particular format -- the element placement is defined by
the parser. Fountain text files flow in correctly however you've set up your
page.
There has been a lot of thought put into the Fountain format by two
professional screenwriters (Fountain was originally two, separate projects
that were merged). This wasn't something just slapped together on the spur
of the moment -- and it has matured over several years now.
Not that I don't understand wanting to use one tool for everything. If I
could, I would use jstar for just about everything. But, ironically (and
sadly), since it won't give me "virtual" carriage returns (carrige returns
on the screen but not in the file) I can't use it for writing in Fountain
format.
--
Using slrn with Linux Mint Mate 17.1
[toc] | [prev] | [next] | [standalone]
Page 1 of 4 [1] 2 3 4 Next page →
Back to top | Article view | comp.os.linux.advocacy
csiph-web