On Friday, February 13, 2015 at 6:39:06 PM UTC-8, Jun Omae wrote:
>
> On Mon, Feb 9, 2015 at 3:14 PM, RjOllos <[email protected] <javascript:>> 
> wrote: 
> > INSTALL (5) and UPGRADE (6) duplicate what is provided in TracInstall 
> (7) 
> > and TracUpgrade (8). Would it be sufficient to just put a link to the 
> wiki 
> > docs in the files? The link could direct to either the documentation in 
> the 
> > distribution or to the t.e.o wiki. 
>
> Linking to the documentation in the distribution sounds good. INSTALL 
> and UPGRADE files already navigate the files in the default-pages 
> directory. 
>
>   9 **You should also read the trac/wiki/default-pages/TracInstall 
>  10 documentation file present in the source distribution.** 
>  11 
>  12 If you're upgrading an already installed Trac environment, please also 
>  13 read trac/wiki/default-pages/TracUpgrade. 
>
> However, I assume that users read INSTALL and UPGRADE files on the 
> user's terminal. TracInstall and TracUpgrade file have too long lines 
> (over 80 columns). 
>
>
> > If there's a good reason to not take that approach, maybe there's 
> another 
> > way to eliminate the duplication, such as exporting from the wiki to 
> ReST or 
> > MarkDown? Unfortunately we don't have those features yet. 
>
> I tried to convert TracInstall using pypi:trac2rst but an IndexError is 
> raised. 
> Another idea is using pypi:html2rest library after converting Trac 
> wiki to html. See attached wiki2rst.py. 
>
> $ pip install html2rest 
> $ PYTHONPATH=. python contrib/wiki2rst.py TracInstall 
>

The module works well. I made some comments in:
http://trac.edgewall.org/ticket/11914#comment:17
 

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.

Reply via email to