Re: DISCUSSION: Drop PDF support in documentation

2018-10-14 Thread Edward Ribeiro
+1 about dropping the PDF support. Edward On Fri, Oct 5, 2018 at 5:30 AM Norbert Kalmar wrote: > > Sounds logical to me, dropping pdf support / generation. > +1 > > On Thu, Oct 4, 2018 at 10:47 PM Michael Han wrote: > > > +1 on dropping support for PDF documents. Most if not all of the other >

Re: DISCUSSION: Drop PDF support in documentation

2018-10-05 Thread Norbert Kalmar
Sounds logical to me, dropping pdf support / generation. +1 On Thu, Oct 4, 2018 at 10:47 PM Michael Han wrote: > +1 on dropping support for PDF documents. Most if not all of the other > apache projects only provide html documents. > > On Wed, Oct 3, 2018 at 1:18 AM Enrico Olivelli > wrote: > >

Re: DISCUSSION: Drop PDF support in documentation

2018-10-04 Thread Michael Han
+1 on dropping support for PDF documents. Most if not all of the other apache projects only provide html documents. On Wed, Oct 3, 2018 at 1:18 AM Enrico Olivelli wrote: > Il giorno mer 3 ott 2018 alle ore 09:34 Tamas Penzes > ha scritto: > > > > Hi All, > > > > As part of "ZOOKEEPER-925

Re: DISCUSSION: Drop PDF support in documentation

2018-10-03 Thread Enrico Olivelli
Il giorno mer 3 ott 2018 alle ore 09:34 Tamas Penzes ha scritto: > > Hi All, > > As part of "ZOOKEEPER-925 Consider maven site generation to replace our > forrest site and documentation generation" I have implemented > "ZOOKEEPER-3153 Create MarkDown files and build process for them". > > The

DISCUSSION: Drop PDF support in documentation

2018-10-03 Thread Tamas Penzes
Hi All, As part of "ZOOKEEPER-925 Consider maven site generation to replace our forrest site and documentation generation" I have implemented "ZOOKEEPER-3153 Create MarkDown files and build process for them". The solution would replace the old Forrest based document creation with MarkDown based