Re: [Firebird-docs] SourceForge CVS to GitHub migration done
Tuesday, November 28, 2017, 1:21:39 PM, PaulV wrote: > And this CHM file describes the ODBC driver? Yes, it's the same content as the PDF and the HTML with some edits to stop it exploding when you try to hit an external link. Oh, and about a zillion fewer Firebird logos. ;-) > So it naturally belongs to > the Fb-ODBC 2.0.5 documentation? Then I'd put the source files > - unzipped, for easier version control - in a subdir of refdocs/fbodbc205, > e.g. refdocs/fbodbc205/chm or whichever name you think is best. refdocs/fbodbc205/chm-source Helen -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] SourceForge CVS to GitHub migration done
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 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. And this CHM file describes the ODBC driver? So it naturally belongs to the Fb-ODBC 2.0.5 documentation? Then I'd put the source files - unzipped, for easier version control - in a subdir of refdocs/fbodbc205, e.g. refdocs/fbodbc205/chm or whichever name you think is best. Cheers, Paul -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] SourceForge CVS to GitHub migration done
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 the repository, or create a > separate repository for this. Ahm actually, I was asking PaulV that question...you may not be aware that we don't do CHM, but the ODBC fans seem to like them. Our DocBook system doesn't produce it but it turned out to be relatively simple to produce from the html that it does generate. I could probably produce VS help from them as well, some other time when I'm in an experimental frame of mind. Of course, both the CHM and VS help compilers are proprietary Microsoft products, so some might say it would be evil to encourage these people. ;-) So I was really just sounding out Paul as to where he thought might be a good place to put the source files for the CHM file - obviously (I thought) *where?* relative to the parent docbook source from which they evolved. A different repository does not make any sense. Tainted or not, it is still Firebird documentation. Helen -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] SourceForge CVS to GitHub migration done
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 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 the repository, or create a separate repository for this. The other thing is - we don't seem to have a notification channel for checkins to this repository. Can something similar be done for this one as was done for the main Firebird repo? (After a lot of messing about, we finally got main repo notifications coming into firebird-checkins a few weeks ago. I'm not sure they are perfect yet, though) I'll search (or ask) on firebird-devel what they did for this. Mark -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] SourceForge CVS to GitHub migration done
Monday, November 13, 2017, 12:03:31 AM, Mark wrote: > The migration from SourceForge CVS to GitHub has been completed. The > repository is at > https://github.com/FirebirdSQL/firebird-documentation > (with clone URL > g...@github.com:FirebirdSQL/firebird-documentation.git or > https://github.com/FirebirdSQL/firebird-documentation.git ) > If there are any problems or questions, let me know. Over the weekend I did some commits. a few things: Paul, when you have a moment, could you look at what I did: 1. Created a new../refdocs/images subdir, currently containing the images for the ODBC manual. 2. Created a new ../refdocs/fbodbc205 directory containing the source for the ODBC manual. 3. Added fbodbc205 to refdocs.xml. I did all this with pushing from my local repo. 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 should I put them? I'll write a little readme. The other thing is - we don't seem to have a notification channel for checkins to this repository. Can something similar be done for this one as was done for the main Firebird repo? (After a lot of messing about, we finally got main repo notifications coming into firebird-checkins a few weeks ago. I'm not sure they are perfect yet, though) I'll need to do another lot, for the Developer's Guide, when I get the go-ahead from Denis. It's good to go Beta for reviewing, as far as I'm concerned, but I understand Denis still has a meaty job to do translating his source code downloads. That doesn't affect the production of the book at all, except that every chapter ends with a link to the respective source code pack and they are all at some stage of being re-done. I haven't heard from Denis for a couple of weeks, so I don't know exactly where we're at. If anyone is interested in taking a browse through the PDF or the HTML, the latest builds are in my repository at https://github.com/helebor/fbmanuals in the /dist subdirectory. Note that gitHub's PDF browser is not crash-hot; it's better to download it when the Download button appears. Helen -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] SourceForge CVS to GitHub migration done
Thanks for all the hard work on the migration Mark - it is appreciated. Would having issues enabled be better for people to log bugs in the docs perhaps? Cheers, Norm. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
