Re: [Firebird-docs] Conversion of fbutil-*
On 15-06-2020 20:24, Alexey Kovyazin (ak) wrote: ... Another question - do you plan to convert also Developers Guide? Yes, that is the plan. Mark -- Mark Rotteveel ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Conversion of fbutil-*
Mark Rotteveel wrote: > I was planning on converting the fbutil-* documentation next, however I > was wondering how to approach this. Historically, we have released those > as individual documentation, while at the same time they were also > intended to be a single volume (the "Firebird Command Line Utilities" book). > > Should I convert them individually (and 'throw away' the fbutil-intro, > fbutil-outro and fbutil-appendix that are only referred from the > "Firebird Command Line Utilities" book), or should I try to preserve > this by allowing them to be built as individual books and as a combined > volume? I think it's far more practical to have them as separate docs. I also don't see the extra value in a combined volume if separate docs exist - but would have nothing against it either. Cheers, Paul Vinkenoog ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Conversion of fbutil-*
Hello Mark, I think it is necesary to keep the current structure, and unite them only virtually, since "command line tools" is a weak basis for grouping such different tools. Theoretically, they should be parts of Firebird Admin Guide, but now they are just pieces. Another question - do you plan to convert also Developers Guide? Regards, Alexey Kovyazin пн, 15 июн. 2020 г., 21:13 Mark Rotteveel : > I was planning on converting the fbutil-* documentation next, however I > was wondering how to approach this. Historically, we have released those > as individual documentation, while at the same time they were also > intended to be a single volume (the "Firebird Command Line Utilities" > book). > > Should I convert them individually (and 'throw away' the fbutil-intro, > fbutil-outro and fbutil-appendix that are only referred from the > "Firebird Command Line Utilities" book), or should I try to preserve > this by allowing them to be built as individual books and as a combined > volume? > > I should note that the text in the intro and outro is outdated because > it wasn't updated for several utilitities that are actually documented > (like gfix, gstat and isql). > > Mark > -- > Mark Rotteveel > > > ___ > Firebird-docs mailing list > Firebird-docs@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/firebird-docs > ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
[Firebird-docs] Conversion of fbutil-*
I was planning on converting the fbutil-* documentation next, however I was wondering how to approach this. Historically, we have released those as individual documentation, while at the same time they were also intended to be a single volume (the "Firebird Command Line Utilities" book). Should I convert them individually (and 'throw away' the fbutil-intro, fbutil-outro and fbutil-appendix that are only referred from the "Firebird Command Line Utilities" book), or should I try to preserve this by allowing them to be built as individual books and as a combined volume? I should note that the text in the intro and outro is outdated because it wasn't updated for several utilitities that are actually documented (like gfix, gstat and isql). Mark -- Mark Rotteveel ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
