On Tue, 6 Aug 2013 19:29:58 -0400 Steve Litt <[email protected]> wrote:
> On Mon, 5 Aug 2013 16:07:14 +0200 > dufriz <[email protected]> wrote: > > > Thanks for the clarification. > > From what you wrote, I take it that no form of rich text support > > (whether Microsoft's RTF or otherwise) is going to be added > > *natively* to Leo (i.e. excluding plugins). > > Of course, this is your choice as developers, but allow me to point > > out that this limits considerably the chances of Leo to compete with > > other applications such as Notecase and the like. > > > > What I would love to see is a *native* implementation of some form of > > rich text (at the very least: font colors, sizes, italic, etc - that > > is, the basics) within Leo. Only then would I be willing to adopt Leo > > as my main production tool. > > I don't get it. Everything I've ever seen tells me that RTF is an > almost-opaque text format whose only real asset is it's the one way > incompatible MSOffice versions can work on each others' content. I think the term "rich text" is being used informally to mean "text with bold / italic / color / bullet lists / etc." edited in a wysiwyg way. The only file format being considered is HTML. > that computer screens are a lot wider than they are tall. For instance, > I write the Bluefish HTML tag editor (definitely not WYSIWYG) on the > right, and Firefox with the addon on the left, and every time I save in > Bluefish, Firefox updates. It's very much like WYSIWYG authoring. Writing rst with the view rendered plugin works the same way. > I couldn't find out whether Leo exports XHTML, but if it does, that's > perfect. Every time you export you can see it in Firefox. Better yet, I > believe that if you do styles-based authoring, and only styles-based > authoring, it would be pretty easy to write a Python program to convert > XHTML to LaTeX, from which you can get very well formatted PDFs. > > Like I said, I don't know what you're producing, but I don't know of > anything that's optimally produced by RTF. > > On a slightly different subject, several people have mentioned Leo > working with reStructured Text and Markdown as a substitute for it rst does support what you're calling style based authoring, you can define roles: .. role:: litt_style And then the :litt_style:`wheel` fell off! yields <p>And then the <span class="litt-style">wheel</span> fell off!</p> when converted to HTML, or And then the \DUrole{litt-style}{wheel} fell off! when converted to LaTeX. In both cases you'd need to define what the role means, in CSS and LaTeX. I'd use something like rst or LaTeX rather than "rich text" myself, I'm fine with *important* things like /italicized text/ being indicated with asterisks and slashes. But rich text could be quite useful, if it can be done using other tools. And yes, if I was writing a book, I'd definitely use Leo, but I'm not :-) Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
