Re: Questions how to contribute to fvwmorg.github.io

2016-06-02 Thread Thomas Adam
On 2 Jun 2016 5:27 p.m., "Thomas Funk"  wrote:
>
> On 06/02/2016 06:09 PM, Thomas Adam wrote:
>>
>> You should read my previous emails on documentation to this list.
>
>
> you refer to
https://www.mail-archive.com/fvwm-workers@lists.math.uh.edu/msg15756.html ?

Yes.

>
>> You should look at:
>>
>> manpages/fvwm.rst
>
>
> So the preferred format is rst, right?

Yes.

Thomas Adam


Re: Questions how to contribute to fvwmorg.github.io

2016-06-02 Thread Thomas Funk

On 06/02/2016 06:09 PM, Thomas Adam wrote:

You should read my previous emails on documentation to this list.


you refer to 
https://www.mail-archive.com/fvwm-workers@lists.math.uh.edu/msg15756.html ?


You should look at:

manpages/fvwm.rst


So the preferred format is rst, right?




Re: Questions how to contribute to fvwmorg.github.io

2016-06-02 Thread Thomas Adam
On 2 June 2016 at 17:06, Thomas Funk  wrote:
> No prob. Which documents you've meant? the manpages in bin ? Or others?
> If so, how should I added the files? For example fvwm.bug.1.in ... create
> a new one named fvwm.bug.md.in?

You should read my previous emails on documentation to this list.

You should look at:

manpages/fvwm.rst

Everything remains as-is for now, including module man pages,

> Another question is if there're some manpages which aren't important enough
> to convert (e.g. fvwm.bug.1.in ;-) )?

See above.

-- Thomas Adam



Re: Questions how to contribute to fvwmorg.github.io

2016-06-02 Thread Thomas Funk

On 06/02/2016 05:49 PM, Thomas Adam wrote:

On 2 June 2016 at 16:38, Thomas Funk  wrote:

Hi Jaimos,

I want to implement the missing 'allCommands' and the linkings in
fvwm.man to the website. I've cloned master and created a new branch
tf/allCommands-linked-fvwm.man


I'd rather you didn't do this just yet.  If anything, I'd much rather
you contributed to ta/docs-to-md in the fvwm repo, because once that's
done, the means by which we generate HTML documentation will be
different, and simpler.


No prob. Which documents you've meant? the manpages in bin ? Or others?
If so, how should I added the files? For example fvwm.bug.1.in ... create
a new one named fvwm.bug.md.in?

Another question is if there're some manpages which aren't important enough
to convert (e.g. fvwm.bug.1.in ;-) )?

-- Thomas --

--
--
"Two things are infinite: the universe and human stupidity; and I'm not sure about 
the the universe."   --   Albert Einstein