Final Draft software activation: Difference between revisions
GoldenCMOS (talk | contribs) m Reworded intro paragraph to be clearer. Tags: Mobile edit Mobile web edit Visual edit |
Added mention of the open Fountain file format as an alternative |
||
Line 27: | Line 27: | ||
===Broader Implications=== | ===Broader Implications=== | ||
This represents a growing trend in software licensing where companies can unilaterally alter the terms of the sale, taking away perpetual licenses through technical mechanisms rather than legal means. While the company cites security concerns and operating system compatibility, the core word processing functions of the software work fine, raising questions about the necessity of disabling activation. | This represents a growing trend in software licensing where companies can unilaterally alter the terms of the sale, taking away perpetual licenses through technical mechanisms rather than legal means. While the company cites security concerns and operating system compatibility, the core word processing functions of the software work fine, raising questions about the necessity of disabling activation. | ||
=== Alternatives === | |||
A recent alternative for screenplays is the Markdown-like [https://fountain.io/ Fountain], an open standard supported by most screenwriting and production tools. However, it cannot fully replace Final Draft files for exchange with production software because in Fountain, text wrap is app-dependent and thus page breaks are not guaranteed to be consistent. | |||
<references /> | <references /> |