discuss: Some ideas for TLDP


Previous by date: 3 Feb 2016 05:44:44 +0000 Re: History of LDP, David Lawyer
Next by date: 3 Feb 2016 05:44:44 +0000 My rejected "replacement" for the Author Guide, David Lawyer
Previous in thread: 3 Feb 2016 05:44:44 +0000 Re: Some ideas for TLDP, J. S. Evans
Next in thread:

Subject: Re: Some ideas for TLDP
From: David Lawyer ####@####.####
Date: 3 Feb 2016 05:44:44 +0000
Message-Id: <20160203054539.GY2571@daveslinux>

On Sat, Jan 16, 2016 at 01:45:42PM +0100, J. S. Evans wrote:
> > Markdown is very simple to use for beginners and can be converted into
> > various formats using pandoc:
I took a quick look at it and think it's inferior to linuxdoc.  It doesn't
seem to be able by itself to automaticall create a table of contents.  The
line break tag is just 2 (or more) spaces at the end of a line; invisible.
For each html reference you have to invent a reference name.
> > 
> > http://pandoc.org/
> > 
> > I would be far more likely to contribute to TLDP documentation if I
> > could get stuck in writing things instead of having to work out how
> > DocBook and a complex build system go together.
Why don't you try linuxdoc?  I have a howto on it.
> > 
But linuxdoc needs to be updated to make it easier to add images and
doesn't seem to work with unicode.
> 
> ______________________ http://lists.tldp.org/
> 
> 
			David Lawyer

Previous by date: 3 Feb 2016 05:44:44 +0000 Re: History of LDP, David Lawyer
Next by date: 3 Feb 2016 05:44:44 +0000 My rejected "replacement" for the Author Guide, David Lawyer
Previous in thread: 3 Feb 2016 05:44:44 +0000 Re: Some ideas for TLDP, J. S. Evans
Next in thread:


  ©The Linux Documentation Project, 2014. Listserver maintained by dr Serge Victor on ibiblio.org servers. See current spam statz.