Re: [Firebird-docs] SourceForge CVS to GitHub migration done

2017-11-27 Thread Paul Vinkenoog
Helen wrote: > 1. Created a new../refdocs/images subdir, currently containing the > images for the ODBC manual. Perfect. > 2. Created a new ../refdocs/fbodbc205 directory containing the source > for the ODBC manual. > 3. Added fbodbc205 to refdocs.xml. Ditto. > Next thing, I have source file

Re: [Firebird-docs] SourceForge CVS to GitHub migration done

2017-11-27 Thread Helen Borrie
Hello Mark, >> Next thing, I have source files for the build of the CHM file, for use >> with the M$ help compiler, all zipped up. Where should I put them? >> I'll write a little readme. > What are these CHM files for? You could consider just adding them > (unzipped) in a specific subfolder of

Re: [Firebird-docs] SourceForge CVS to GitHub migration done

2017-11-27 Thread Mark Rotteveel
On 2017-11-27 01:02, Helen Borrie wrote: Actually I had to do a minor update today as I'd left something out, so the commit messages don't all reflect what I did yesterday. ;-) Next thing, I have source files for the build of the CHM file, for use with the M$ help compiler, all zipped up. Where

Re: [Firebird-docs] SourceForge CVS to GitHub migration done

2017-11-27 Thread Norman Dunbar
I wrote: > This sounds like a new book, I don't recall reading about it though - or > maybe I've > forgotten - is there a thread or link I can follow to read about it please? > Thanks. Cancel that request, I found it. Thanks. Cheers, Norm. -- Sent from my Android device with K-9 Mail. Please

Re: [Firebird-docs] SourceForge CVS to GitHub migration done

2017-11-27 Thread Norman Dunbar
Morning Helen, well it is here! > The other thing is - we don't seem to have a notification channel for > checkins to this repository. As a temporary measure until a correct solution is implemented, login to github as yourself and navigate to the docs repository. Near the top of the page is a