Hi, after a very short trial-testing period (one day max ) I followed my impulse to buy the windows version. Having read and seen quite a lot of tutorials and videos I didn’t quite realize that the LaTex export was not yet part of the 1.03 version.
Not a problem -for now- but I wish to create the final documentary for my final evening school project. It will probably be 30-45 DinA4 pages long/short.
Print and PDF should be done in june. Are there any chances a LaTex-Export will have made its way into the windows version by then? Or is there another way to do it? Does a RTF to LaTex converter exist?
While the integration isn’t there, you can still get a LaTeX document out of Scrivener much in the same way you would if had access to the integration. As with the Mac, we’ll be using the MultiMarkdown text processing engine to produce the LaTeX code. So your document will need to be formatting in the MMD syntax. The main things you’ll miss out on without the integration are:
Automatically generated depth-aware headers
Scrivener footnotes converted to MMD footnotes
Embedded images converted to MMD images
Scrivener annotations converted to HTML encapsulated blocks
All of this can be done by hand, and of course in the case of headings you can even get the formatter set up to do what you need to get depth-aware headers. Just use the Formatting pane to set up a prefix and suffix for each header, adding one hash “#” on each side for each level of depth. So a Level 1 title would have “# " and " #” (note the spaces, to push it apart from the binder title that will get inserted in the middle) and a Level 3 title would have “### " and " ###”. You might also need to insert a carriage return into each box to keep it on a clear line.
Everything else you’ll need to type in by hand, which isn’t too bad given the simplicity of the syntax. Compile as plain-text, download the MMD distribution for Windows, convert the compiled file to LaTeX, and you should be roughly where you would be with integration at that point.
I don’t think so. RTF is largely devoid of semantics, so if such a beast exists it would probably result in a massive mess of a source file.
On your timeline: I can’t make any promises. I know that Lee is anxious to get this particular aspect of Scrivener working, so I would be inclined to guess that there will be something by June, but I really can’t say “expect it”. That wouldn’t be fair to you. One nice thing about all that I am describing here is that MMD is more a process than single-ended format option. You need to start working in it now to take advantage of it. If we don’t have anything in June, then you can use the manual techniques I described to get header titles. If we do have something, then you’ll be all set. Either way I would recommend forming your images and footnotes in MMD syntax as that doesn’t hurt anything one way or another. If we have integration in June it will work fine with your manual syntax (as it’s just text anyway).
Hi AmberV, wow, I’m impressed how fast I got such a profound answer! Thanks for that!
A great idea you have about formatting beforehand. Of course using this option I won’t be able to create an epub or another proposed format directly from scrivener as the MMD syntax would be visible in the end-result (not the headers of course). Or am I mistaking?
But it doesn’t mater since I will only be using the LaTeX generated pdf-format.
I will do what you propose and hope that mmd support will find its way before june
Table of Contents would have been another question, but I guess I will have to do this completely in LaTeX?
That is correct, as of today working in MMD largely precludes using the other compile options because the formatting syntax will be visible. In general this isn’t a huge burden as MMD itself has a plentiful battery of useful formats that can all spring off of one source document. You can make a LaTeX file and a second later an .fodt file (LibreOffice format) which gives you a stylesheet-ready word processor workflow, or an XHTML file suitable for web publishing. Going further with the engine, you can use the XHTML file as a valid XML source for XSLT scripting which frankly has no limits to what you can do. I’ve even created converts for BBCode and wiki syntax, making publishing to these venues easier from a single source. Others have successfully coupled an MMD workflow with Pandoc that supports an even larger collection of output formats, like DocBook which is important to technical writing. I’m not sure what the state of Pandoc is on Windows though, it’s a UNIX tool so it might not be available. The big limitation right now is, as you pointed out, e-books. To my knowledge there isn’t yet an e-book workflow for MMD. Like I say it would be possible but as yet there isn’t a stable workflow already extant. It wouldn’t surprise me if this is a very temporary condition. If the community or Fletcher Penney (designer of MMD) doesn’t come up with one, we have it on our list to get Scrivener capable of doing this. E-books are increasingly important and so this gap is bothersome to us as well.
ToC is very easily done in LaTeX. Most of the pre-fab classes that come with MMD do it automatically. Unless you wish to tweak the depth of the ToC you’ll probably be good to go with the vanilla result based on the structure of your outline. Configuration options aside, plugging a ToC into a LaTeX file is just a single line of code, so its easy to do.
thanks for your googling I must admit I didn’t do a search myself as I didn’t want to check all found tools but rely on a tool which is being used here effectively.
I tested http://sourceforge.net/projects/rtf2latex2e/files/rtf2latex2e-win/ which works relatively nice. I exported the Interactive Tutorial and rtf2latex had some problems with utf, especially with the list bullets. Once deleted in the tex I could compile it to pdf, but there would be quit some work until it would be called finished.
I’ll keep an eye on this tool, but I think for now I would still stick to formatting it later on in Lyx.
Best case would be MMD integrated in the window version though
I’ll see by end of may how far scrivener has caught up on the mac version.
(Maybe some nice Mac-Owner will be so helpful to convert my document to tex :mrgreen: )
) I followed my impulse to buy the windows version. Having read and seen quite a lot of tutorials and videos I didn’t quite realize that the LaTex export was not yet part of the 1.03 version.