Josiah, The following is possible more for my own understanding, but may help describe the situation.
When it comes to IMPLICIT rather than explicit there are hidden characters in any text be it new lines, a pair of new lines and more. It seems to me that along with some smart CSS determining if you can easily process an alternate markup can only be determined in its details, ie stepping through each of the detailed markup features and finding a way to display according the required standard. The idea would be to always retain the text in its custom markup and only display it according to standards just in time. This allows it to be imported/exported/viewed and edited in its native form. Since the act of displaying it, is one of the standards, HTML the fact is we can copy or save it in this display format as well for transfer to other documents or environments. The other approach would be to use tiddlywiki markup and macros as needed to display (not in finished presentation format) but in fountain markup which can be copied and pasted into a converter or tool for the final display. I suppose it all depends on which part(s) of the workflow you want tiddlywiki to be responsible. Regards Tony On Tuesday, November 21, 2017 at 12:01:03 AM UTC+11, @TiddlyTweeter wrote: > > Ciao TonyM > > TonyM wrote: >> >> Is it a third approach, or one of your two to use tiddler type to keep >> and edit in any desired markup standard and only render it as needed to >> html as currently happens with wikitext? >> > > For some types of specialised Markup, closely linked to application types, > it makes most sense to create a new Content Type and go much of the way to > creating final HTML for the rendered version. > > FOUNTAIN markup is an example that is widely used in writing screenplays. *It > makes much sense to author using Fountain when writing screenplays* inTW. > But its markup conflicts with TW standard markup. > https://fountain.io/syntax > > There are TWO ways forward (which you can mix) ... you convert for TW > compliant markup where you can (in other words change F. markup to > compliant TW markup in a pre-parser before the TW parser runs--after that > you get what you'd expect) AND/OR directly convert F. Markup to HTML. > > Fountain markup is interesting because its largely IMPLICIT (how you space > paragraphs & how you start them) whilst most normal wiki markup is > initiated by explicit characters (*/-/! etc). F. is great for screenplay > authors because *you rarely ever have to enter any explicit markup* if > you have your line layout right. > > But to use the F. approach in TW you need more than straight conversion of > markup systems because the "implicit" markup of F. TW has no equivalents > for. Its still pretty easy once you can access a pre-parser just using > regular expressions to do it though. > > All of this works under point (1) of my last post. > > Point (2) about CONVERSION is more a one-way-ticket. Its for cases where > you don't need to retain original markup, just permanently convert for > native TW normal. > > Best wishes > Josiah > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/649b92f5-274a-431d-91ee-526295276c1c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
