Loading ...
Sorry, an error occurred while loading the content.

130321Re: Vim manual

Expand Messages
  • Phil Dobbin
    Apr 11 11:33 AM
      Hash: SHA1

      On 10/04/2012 22:01, Andre Majorel wrote:

      > On 2012-04-10 18:37 +0100, Phil Dobbin wrote:
      >> Putting the documents (manual & reference) into tex I think is
      >> the best way to go & will result in a much better looking final
      >> PDF from which to print.
      > What do you have in mind ?
      > If you just put all the text in a giant monospace verbatim, it
      > won't be much better (or worse) that the output of vimpspp. Page
      > breaks and page numbering may be easier, though.
      > If you intend to reflow the text, there is much to gain. But then
      > you need to know what is, in HTML parlance, <pre>, what is <code>
      > and what is neither. Dunno how easy/hard that is.
      > In any case, it's essential that the process be as automated as
      > possible. EG, program reads /usr/share/vim/vim*/doc/ and spits out
      > {man,ref}.ps. Otherwise, the files will always lag behind.

      Well, I have this crazy idea of taking the plain text files, flowing
      them into markdown, then converting them into tex to be typeset & then
      generating a PDF ready for print.

      All perfectly possible using Pandoc, Vim & Lulu, just a question of
      how viable it is.

      Any thoughts appreciated.



      - --
      But masters, remember that I am an ass.
      Though it be not written down,
      yet forget not that I am an ass.

      Wm. Shakespeare - Much Ado About Nothing

      -----BEGIN PGP SIGNATURE-----
      Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
      Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
      Comment: GPGTools - http://gpgtools.org
      Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

      -----END PGP SIGNATURE-----
    • Show all 19 messages in this topic