I think I will stick to html... But I will check Abiword...

Thank you for your reply...

On Fri, 2009-04-03 at 17:48 -0500, Tim Chase wrote:
> > The thing is I hate document processors. I really do. I love
> > vim. I really really do.
> 
> Ditto :)
> 
> > But "they" want a .doc file. With italics, bold, red for the
> > code and green for page count.
> 
> To get this from plain-text, you need _some_ sort of text markup
> (he types, using underscores to mark up the sentence).  There are
> literally hundreds if not thousands of markup languages, and you
> can even produce your own fairly easy (one of the main
> contributing factors to the large numbers).  Choices include RTF,
> HTML, Markdown, DocBook, LaTeX...the list goes on and on.
> 
> > I tried editing with vim and then opening with open office
> > writer coloring, italizing, bolding and saving to .doc. But it
> > is painful! To much mouse work... select the text go press the
> > stupid B or I button or go press font color and then red or
> > green. Painful. I want to use my keybord and only my keyboard.
> > 
> As an aside, in most word-processors, you should be able to
> select by holding down <shift> while using motion keys (arrows,
> control+arrows, home, end, pgup/pgdn, etc).  You can then use
> control+B to get bold, control+I to get italics.  Colors, not
> usually as readily available.  But that's 2/3 of a solution. :)
> 
> > So here is what I thought. I will edit an html document, open
> > it with oowriter and save to .doc.
> > 
> > And here is the question:
> > 
> > Is there an even easier way to do this using my vim?
> 
> Choose some markup that's easy for you, and then post-process it
> to tweak it to be valid HTML.  I happen to think fairly natively
> in basic HTML (wrote most of my college papers in HTML using a
> text-editor and then printed from the library for free instead of
> the $0.07/pg in the labs; darn javascript end-note library I
> wrote from scratch :), so I just started there.  HTML has good
> control for styling and doing things like code-blocks, or
> defining <div>/<span> elements for page-counts.
> 
> However, your markup can be as simple as
> 
>    <code>
>    here's some code
>    </code>
>    @42@
> 
> which you can then post-process to HTML (bound in a
> script/keystroke to save your sanity)
> 
>    :%s/@\(\d\+\)@/<span class='page'>\1<\/span>/g
> 
> Vim has fairly strong support for HTML so I know that's pretty
> easy.  You don't mention what's getting italicized, bolded, or
> made red, so I'm not sure if there's a better/worse way to mark
> those up.
> 
> If you're willing to put up with RTF markup, you can do this 
> natively in Vim and just open the resulting file directly in Word 
> or WordPad (most users see the idiot-icon for Word and don't care 
> that it's an RTF file instead of .DOC as long as it opens in 
> Word).  I think OO.o does .rtf as well (when forced to use a 
> document processor, I tend to use AbiWord because it's a bit more 
> light-weight on my old machine here).
> 
> Hope this gives you some ideas,
> 
> -tim
> 
> 
> 
> 
> > 
> 


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to