[Firebird-docs] Publishing process of the FB LangRef translations
Hi all. How do we want to go on with the translated texts of the langref? Should I translate the complete langref first or do we want to publish finished sections? Just for interest: Is there a script or something else refreshing the docs automatically at night? Will they be updated after someone pushes changed contents to the SVN repository? Regards Martin -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Publishing process of the FB LangRef translations
Hello Martin, Wednesday, March 16, 2016, 3:21:15 AM, you wrote: > How do we want to go on with the translated texts of the langref? > Should I translate the complete langref first or do we want to publish > finished sections? I think it is safe to proceed with translating the chapters and sections that have already been reviewed by Paul and Mark. That said, a few "tweaks" affecting those parts have been appearing. For example, I have a small list from Aage that will appear in the next update. > > Just for interest: > > Is there a script or something else refreshing the docs > automatically at night? Will they be updated after someone pushes > changed contents to the SVN repository? The Docs sources are in the CVS repository, not SVN. So far, the changes since the first Beta have been minimal and I have been re-posting the change report here. That tells you which file has changed and shows the old and new text. I am the only one pushing changes in the English sources. I am not tracking anyone else's changes and I hope I don't need to, whilst the langref is still in Beta. If a translator finds something missing or wrong in the checked sections, it is very important that you report it here so that the English source can be amended and all the other translators know about it. Note, also, that the publication date and the document version change whenever I push an updated version. That shows up in one or more of the CVS reports and also in the PDF, of course. The file that contains that information is fblangref25.xml. That is how is goes, for now. I am open to any better ideas Helen -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Publishing process of the FB LangRef translations
Hello Helen, thank you very much. I think the first German chapters will be available next week. > The Docs sources are in the CVS repository, not SVN. Sure. Read too much in the devel-list. > That is how is goes, for now. I am open to any better ideas Well, just a thought: We're (4 developers) working on several manuals (set with books) using DocBook. Instead of CVS we're using Git, but that's just an aside. So when the work on a manual is done, the developer commits his changes to the repository. In background runs a script (periodically) that fetches the current repository, clones it and builds the HTML and PDF outputs which are automatically released on the product's web site. The actual writing is done on a develop branch. It is merged into the master branch after review. The script publishes the official release (master branch) at night at the web site while the "devel"-docs are built at an unofficial (or hidden) server. This can be done hourly or manually. It depends on runtime. With this prerelease everybody can review the doc before the merge. The main benefit of this process is that nobody has to publish the release by hand and everybody knows what they have to do to get their work on the product's page. And of course there is still an instance doing the review work. Hope I expressed it well. Don't know if this is something that can help. I think currently there are just a few commits. But maybe there could be much more if we're able to push smaller parts as mentioned above (sections / chapters). And maybe we can acquire more doc writers on that way. Regards Martin -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs