On Tuesday, January 31, 2012 6:59:59 AM UTC+7, PMario wrote: > > I did test pandoc some time ago. FND posted some usefull links [1]. I > didn't want to use it with markdown, but with TW syntax. So I needed to > render HTML output (using TiddlySpace twikifyer) and feed it to pandoc. The > problem is that there are no paragraph <p> tags in TW HTML output, which > makes stuff complicated for propper PDF generation. > > So I stopped testing. >
I thought I remember coming across a TW plugin that handled hard return issues, doesn't that make use of <p> tags? The absolute ideal IMO would be a core TW architecture that allowed for user choice of internally-stored syntax, with or without appropriate rendering and input assistance. Zim's author is intending to head down that road in future. Second best is export capability to one or more "standard" syntaxes to support Txt2tags and/or Pandoc - I'm now leaning toward the latter, so leading candidates are extended markdown or reST/Sphinx. Worst case is adding a "reader" for TW-specific syntax to Pandoc, which will then be able to output to any of its dozen+ target output formats. In which case a Pandoc "writer" for txt2tags and/or Asciidoc (which I believe is in the dev version) would make things pretty complete. My understanding is that these wouldn't be too hard for an experienced programmer. If I need to learn to program, I'm not sure if Haskell's the language to start with but they say most important is a relevant real-world project to motivate you. 8-) -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/XXVlyMY7oAIJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
