[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vile] permission to put vile docs online

From: Thomas Dickey
Subject: Re: [vile] permission to put vile docs online
Date: Fri, 10 Feb 2012 07:17:12 -0500
User-agent: Mutt/1.5.18 (2008-05-17)

On Fri, Feb 10, 2012 at 12:41:59PM +0100, ben wrote:
> hi
> I'd like to know if it's ok to put exisisting vile documentation online  
> on my website. The idea is to make all pod documentation (plugins)  

yes (all of the documentation uses the same license as the code -
offhand the code is all GPLv2 except for the regular expressions
which use the ncurses license).

since a couple of years ago when I switched from plain text to html
as the documentation format, I've put a copy of the html files on
my webpage, as-is, and linked from my pre-existing page.

As a rule, the pages that link to my website in their headers are
part of the website, while those that do not are essentially content
that could be "anywhere".  My understanding is that you're asking
about files which are not part of the website.

At the moment, these are the files in that folder.  Except for
two, they are all part of vile's source distribution.

        vile-man.html (generated)
        vile-toc.html (generated)
        vile.faq.html (website)
        vile.html (website)

The generated files are a special case.  The manpage is still in
plain-text format (since there are no usable scripts for going from
html to nroff).

The scripts used for generating them are in vile's doc directory.

(The table of contents uses a Perl module - not part of vile - there's
a Debian package for it).

> available in html and maybe the main vile documentation in another  
> design and/or another form (chunked html).

some of the files are rather large - I haven't spent any time looking
for nice tools to do chunking however...

> Is this OK for you? What do I have to consider? Should I make a special  
> header where I refer to invisible-island?

no - as I understand it, the files that you want to use don't require
remarkup (unless someone wants to be picky about marking license on
each file, etc).

Thomas E. Dickey <address@hidden>

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]