Re: [Firebird-docs] Adding new doc "Firebird UDRs in Pascal"
Hello, Lets put there IDPL. Regards, Alexey Kovyazin Денис Симонов via Firebird-docs : > I don't mind. This article was originally created for general access, > although I did not think about the license, but if necessary, I can add so > that there is no contradiction > > -- > Regards, > Simonov Denis. > вторник, 19 сентября 2023г., 19:02 +03:00 от Mark Rotteveel via > Firebird-docs firebird-docs@lists.sourceforge.net: > > On 19-09-2023 13:12, Köditz, Martin wrote: > > I have recently translated the document "Writing Firebird UDRs in > > Pascal" by Denis Simenov into English. If you and Denis agree, I would > > include both the Russian and English versions in the general > documentation. > > > > What is your opinion about this? > > I don't see a problem with it *if* Denis agrees, and if there is a clear > license for the documentation. > > Apart from that, in the future please use firebird-devel > (https://groups.google.com/g/firebird-devel) also for documentation > related discussions. > > 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 mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Outdated documents
Hello Mark, May be we can map page of multi page document to the link of single page document with anchor? Regards, Alexey Kovyazin пн, 5 июл. 2021 г., 22:09 Mark Rotteveel : > On 05-07-2021 20:04, Alexey Kovyazin wrote: > > I just found that we have a hidden nest of old versions of many documents > > > > https://www.firebirdsql.org/pdfmanual/html/ > > > > and many of them seems to be well-ranked by Google :( > > > > I think the best solution will be to create mapping through nginx or > > similar to the actual versions, so it will be seamlessly unified, > > without many 404 on site. > > Is it Ok? or could be another solution? > > I'll look it over and coordinate with Sergey to add the necessary > redirects. I'm already maintaining a list of such redirects for > documentation. > > One of the problems is that multi-html documents are probably better for > search-engine ranking. I'm currently investigating options to > reintroduce multi-html documents again (at least for the language > references). > > 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] Outdated documents
Hello, I just found that we have a hidden nest of old versions of many documents https://www.firebirdsql.org/pdfmanual/html/ and many of them seems to be well-ranked by Google :( I think the best solution will be to create mapping through nginx or similar to the actual versions, so it will be seamlessly unified, without many 404 on site. Is it Ok? or could be another solution? Regards, Alexey Kovyazin ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Review Firebird 4.0 Language Reference
Hello, I think, the good idea will be to include link to it to the launch message for release of 4.0. Regards, Alexey On 24.05.2021 19:18, Mark Rotteveel wrote: I 'soft-launched' the language reference and put it online on https://firebirdsql.org/en/firebird-rdbms/ and https://firebirdsql.org/en/reference-manuals/ Mark On 22-05-2021 19:24, Mark Rotteveel wrote: I have a 'feature-complete' Firebird 4.0 Language Reference ready to go live, but it would be helpful if others take a second look. Maybe sample a few sections, check for weird stuff in rendering, or simply take a look at the content. I'll publish the links on the site on Monday; maybe the current version, maybe after some further revision. I still have some TODOs in the source that I need to follow or just remove, but I think it is ready enough in its current state. HTML: https://www.firebirdsql.org/file/documentation/html/en/refdocs/fblangref40/firebird-40-language-reference.html PDF: https://www.firebirdsql.org/file/documentation/pdf/en/refdocs/fblangref40/firebird-40-language-reference.pdf ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Firebird 3.0 Language Reference
Hello, I took a quick look and did not see any noticeable problem. Regards, Alexey вт, 23 февр. 2021 г., 19:27 Mark Rotteveel : > I'm going to publish the links tomorrow. > > Mark > > On 20-02-2021 17:02, Mark Rotteveel wrote: > > I have finished up the first version of the Firebird 3.0 Language > > Reference, I used the 2.5 version as starting point, and added new > > things based on the release notes and the Russian Firebird 3.0 Language > > Reference, and made corrections based on inspecting the actual syntax > > and close reading of the existing text. > > > > Before I put the links up on the website, I'd like another set of eyes > > on it. Not so much content-wise, as more layout-wise (e.g. weird > > rendering problems), as by now I'm seeing a bit cross-eyed ;) > > > > Links: > > > > HTML: > > > https://firebirdsql.org/file/documentation/html/en/refdocs/fblangref30/firebird-30-language-reference.html > > > > > > PDF: > > > https://firebirdsql.org/file/documentation/pdf/en/refdocs/fblangref30/firebird-30-language-reference.pdf > > > > > > I committed the document as one large commit. Originally, I had it > > separated out into individual commits, but somewhere along the way I got > > sidetracked by making consistency changes all over the document, or a > > change in one part triggered a revision elsewhere, and in the end I gave > > up on making incremental commits and decided to just use one commit. My > > apologies to translators for this, but it was the only way to retain my > > sanity. > > > > If you need to diff sources to find out what changed, I recommend taking > > the Firebird 2.5 Language Reference sources, rename them to match the > > 3.0 version, and split the DDL and Security chapter in similar fashion > > as done for the 3.0 version (per keyword or subject). > > > > 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
Re: [Firebird-docs] Firebird 3.0 Language Reference
Hello Mark, Great work! Thank you vey much! I will read it, of course. Regards, Alexey On 20.02.2021 19:02, Mark Rotteveel wrote: I have finished up the first version of the Firebird 3.0 Language Reference, I used the 2.5 version as starting point, and added new things based on the release notes and the Russian Firebird 3.0 Language Reference, and made corrections based on inspecting the actual syntax and close reading of the existing text. Before I put the links up on the website, I'd like another set of eyes on it. Not so much content-wise, as more layout-wise (e.g. weird rendering problems), as by now I'm seeing a bit cross-eyed ;) Links: HTML: https://firebirdsql.org/file/documentation/html/en/refdocs/fblangref30/firebird-30-language-reference.html PDF: https://firebirdsql.org/file/documentation/pdf/en/refdocs/fblangref30/firebird-30-language-reference.pdf I committed the document as one large commit. Originally, I had it separated out into individual commits, but somewhere along the way I got sidetracked by making consistency changes all over the document, or a change in one part triggered a revision elsewhere, and in the end I gave up on making incremental commits and decided to just use one commit. My apologies to translators for this, but it was the only way to retain my sanity. If you need to diff sources to find out what changed, I recommend taking the Firebird 2.5 Language Reference sources, rename them to match the 3.0 version, and split the DDL and Security chapter in similar fashion as done for the 3.0 version (per keyword or subject). Mark ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] gstat OST - OIT and Sweep
Hello Martin, I spoke with Vlad about section devoted to garbage, and we agreed it is difficult. I plan to rewrite it with pictures explaining records versions, garbage and sweep, but it really needs courage :) I suggest to let ost-oit phrases as is. Regards, Alexey Kovyazin IBSurgeon пт, 31 июл. 2020 г., 12:56 Köditz, Martin : > Hi, > > > > I’m currently working on gstat-de. I struggled with following part: > > > > Many web sites, books, manuals (previously including this one) explain > that the automatic sweep is activated when OAT - OIT is greater than the > sweep interval. > > This is _not_ the case as explained by Vlad Khorsun, one of the Firebird > developers, who explained that it is when OST -- OIT is greater than the > threshold that the sweep is activated. > > > > What does the last sentence exactly mean? Can someone „tidy“ it? > > > > Regards > > Martin > ___ > 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
Re: [Firebird-docs] Translation of Russian Firebird 3.0 Language Reference
Mark, And if the Firebird 2.5 translation is any indication, translating it will require a ton of effort afterwards to make it presentable. I'd rather spent time and effort to write it myself (maybe with some inspiration and copy/google-translate/paste/edit from the Russian version). I think the translator's adoption for the Firebird peculiarities greatly increased since LR 2.5 - after that he did translation of Developer Guide, which is much better. Do you think we should ask agency to translate some difficult part of LR3.0 or 4.0 and estimate the results? Regards, Alexey ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Translation of Russian Firebird 3.0 Language Reference
Mark, On 30.07.2020 16:37, Mark Rotteveel wrote: On 2020-07-30 13:20, Alexey Kovyazin (ak) wrote: Hello, We did survey in Telegram channel, and idea was to skip 3.0 and do the translation of LR4.0... What Telegram channel? https://t.me/firebirdsql Not very representative, of course, but at least 200+ people using Firebird, mostly from the visitors of Firebird Conference. While I understand that the Russian version is what we have, I don't think this 'Russian version first' approach is healthy from a perspective of ownership (as in, the project being responsible for the documentation). Not sure what do you mean. All documentation is released under IDPL license. Russian version of LR (versions 2.5, 3.0 and 4.0) is actively used, it is constantly updated by Denis Simonov (editor and maintainer), and got good feedback from Russian-speaking community (which is #2 in size, after Brazil). Regards, Alexey Kovyazin IBSurgeon Mark ___ 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
Re: [Firebird-docs] Translation of Russian Firebird 3.0 Language Reference
Hello, We did survey in Telegram channel, and idea was to skip 3.0 and do the translation of LR4.0... Regards, Alexey Kovyazin IBSurgeon чт, 30 июл. 2020 г., 12:55 Mark Rotteveel : > On 2020-07-30 09:44, Köditz wrote: > > Hello everybody, > > > > I was asked whether it would make sense to start a crowdfunding > > campaign for the translation of the Russian Firebird 3.0 Language > > Reference into English. > > > > Or are there already other efforts to implement it? > > I'm not sure if that is a viable course of action. IIRC, the translation > effort for 2.5 cost quite a lot (the initial idea was that the money > collected would also go toward translating the 3.0 version, but not > enough was left) and also required a lot of post-translation editing by > Helen to fix glaring translation errors. I'm considering to spend some > time to use the current 2.5 version as a basis to go to 3.0 (and then to > 4.0), where I may use Google translate on the Russian 3.0 version, but > might also just write things from scratch. However, I haven't made solid > plans for that yet as I first want to finish up the migration to > AsciiDoc. > > Mark > > > ___ > 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] [FirebirdSQL/firebird-documentation] 521ee7: Update of nbackup documentation (#12)
Branch: refs/heads/master Home: https://github.com/FirebirdSQL/firebird-documentation Commit: 521ee76d782ca3ee9581691e2e217c13bd302cc0 https://github.com/FirebirdSQL/firebird-documentation/commit/521ee76d782ca3ee9581691e2e217c13bd302cc0 Author: Alexey Kovyazin Date: 2020-07-25 (Sat, 25 Jul 2020) Changed paths: M src/docs/asciidoc/en/firebirddocs/gfix/firebird-gfix.adoc M src/docs/asciidoc/en/firebirddocs/nbackup/firebird-nbackup.adoc Log Message: --- Update of nbackup documentation (#12) Update firebird-nbackup.adoc and firebird-gfix * Update firebird-nbackup.adoc Added paragraph about nbackup and virtual machines added example of Firebird nbackup with non-standard port, added paragraph about VM backups and Firebird, and several small changes/clarification. * firebird-gfix changes in gfix -buffers description Update of values and limitations, clarification of behavior Fixes in Database Page Space Utilisation description ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] What is the process of enhancing documentation?
Mark, Martin, thanks, will try. Regards, Alexey On 08.07.2020 16:15, Mark Rotteveel wrote: On 08-07-2020 14:33, Alexey Kovyazin wrote: I would like to amend documentation of gfix and nbackup to add some recovery commands, 1-2 examples, extend description of process, etc. What is the general process - download sources in asciidoc from git, change it, apply changes in git, then generate html, upload to the site? Yes, or if you want a second pair of eyes to review your work, (optionally) fork the firebird-docs project to your account, checkout a branch from master, make your change in that branch. Commit and push to GitHub, create a pull request and ask someone to review it. If you don't have sufficient rights to upload, you can ask here for someone else to do it for you. Mark ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Firebird File and Metadata Security migrated
Hello, I support the idea of the single Page list/index for all docs. I suggest that we should create such page, and then ask people about their opinion (it will also increase awareness of documentation). Regards, Alexey Kovyazin ср, 1 июл. 2020 г., 16:31 Paul Vinkenoog : > Mark Rotteveel wrote: > > > I migrated the Firebird File and Metadata Security document. > (...) > > I do wonder if this document really belongs under 'Reference Manuals', I > > think it would be more suitable under White Papers & Presentations.. > > I think the whole categorization is seriously flawed. > > First we have the top-level categories: > > - Release Notes > - Reference Manuals > - White Papers & Presentations > - FAQ > - Firebird Books > - Drivers Documentation > - Third-Party Docs and Articles > > each corresponding to a separate webpage. > > Then within those categories (i.e. on most of those webpages) we have > further subdivisions. For the page "Reference Manuals", they are: > > - Current Versions > - Firebird Command Line Tools > - Various User Manuals > - Reference Material (h? I thought the whole page was Reference > Manuals) > - Firebird Licenses > > and a couple more. > > Given the fact that the bulk of our docs is on the "Reference Manuals" > page, even if they aren't reference manuals, I think that the Firebird > File and Metadata Security document is reasonably well placed under > "Various User Manuals". > > Now, this isn't a pressing matter, but I do think that we should have > the Doc index back on a single page again (except maybe for a few docs/ > categories that are heavily "niche" and/or outdated and/or third-party), > with categories that make sense, and without separate lines for each > language version, because that's eating up huge amounts of vertical > space. > > Paul Vinkenoog > > > ___ > 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
Re: [Firebird-docs] Firebird 3.0 Developer's Guide migrated
Hello Mark, Thank you very much, excellent work! Regards, Alexey On 27.06.2020 11:14, Mark Rotteveel wrote: New links: https://www.firebirdsql.org/file/documentation/html/en/refdocs/fbdevgd30/firebird-30-developers-guide.html https://www.firebirdsql.org/file/documentation/pdf/en/refdocs/fbdevgd30/firebird-30-developers-guide.pdf Links on the site are updated, redirects from the old to the new will follow later. Mark ___ 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
Re: [Firebird-docs] Firebird 2.5 Language Reference migration preview
Hello, Looks good! Thank you for your efforts, Mark! What is the next - Firebird Developers Guide? Or Quick Start Guide? Or something else? Regards, Alexey On 06.06.2020 11:37, Mark Rotteveel wrote: I have updated the documentation section on the site to point to the new version. Mark ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Firebird 2.5 Language Reference migration preview
Hello Mark, PDF link is the same as HTML. Regards, Alexey On 01.06.2020 18:52, Mark Rotteveel wrote: I have migrated the Firebird 2.5 Language Reference, and it is available for preview on: HTML: https://firebirdsql.org/file/documentation/html/en/refdocs/fblangref25/firebird-25-language-reference.html PDF: https://firebirdsql.org/file/documentation/html/en/refdocs/fblangref25/firebird-25-language-reference.html I haven't linked it yet from the documentation page, and I still need to do some changes like removing that incorrect caution we discussed earlier. This isn't a direct migration: after the migration I touched a lot of things (like syntax blocks) for consistency, and here and there I clarified or corrected some texts. I had to revert my changes to the padding of the tables in PDF, because it caused rather tight columns in Appendix B. Mark ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] The single Page for the documentation outline
Hello Mark, Like that Page but with high level table of contents for each document. Regards, Alexey Kovyazin ср, 27 мая 2020 г., 14:25 Mark Rotteveel : > On 2020-05-27 09:43, Alexey Kovyazin (ak) wrote: > > Hello All, > > > > As you know, Firebird documentation contains a set of documents, and > > they are grouped in several pages, by the topic or type of documents, > > like Release Notes, etc. > > > > Should we consider build the overall list of the docs and put to the > > Documentation starting Page? > > > > It would be like a big outline. Not like a 100% organized > > documentation set, of co3, but better than current distributed > > structure. > > > > What do you think? > > I'm not sure what you mean. This sounds like what we already have at > https://firebirdsql.org/en/firebird-rdbms/, that page and its subpages > is that list as I see it. > > Mark > > > ___ > 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] The single Page for the documentation outline
Hello All, As you know, Firebird documentation contains a set of documents, and they are grouped in several pages, by the topic or type of documents, like Release Notes, etc. Should we consider build the overall list of the docs and put to the Documentation starting Page? It would be like a big outline. Not like a 100% organized documentation set, of co3, but better than current distributed structure. What do you think? Regards, Alexey Kovyazin ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Do we need/want chunked HTML?
Hello, I think we don't need chuncked html. Regards, Alexey On 08.03.2020 16:13, Mark Rotteveel wrote: As I'm looking at the asciidoc conversion, our current choice of having a (single) PDF and a chunked HTML output on the website is a bit of a pain point. Asciidoctor does not support chunked HTML output (there is an experimental, third-party plugin, but that plugin is tied to a specific, out-of-date asciidoctor version). The current options to produce chunked HTML output are: 1. Use separate asciidoc files per section 2. Generate docbook from asciidoc and then use xsl to generate chunked HTML Option 1 has the downsides that to generate a PDF, an additional 'include' file needs to be maintained to be able to generate a single document in addition to the 'chunked' files. This has maintenance overhead and could be something that can easily be overlooked when adding sections. I also haven't yet figured out how to have navigation between sections in the (faked) chunked output this way. This last concern might be addressable by using Antora[https://antora.org/] to generate the HTML documentation (eg see https://docs.antora.org/antora/2.2/ for an example), but that feels like a huge increase in scope. Option 2 might run into some problems as asciidoctor generates docbook 5, not docbook 4.5, so I'm not sure if this would cause problems with our current stylesheets. Option 2 seems to be the least intrusive way to retain chunked HTML output. However, before I spend a lot of time going that route, I'm wondering: - Do we need to retain the ability to generate chunked HTML output? - And, what is the reason that we currently use chunked HTML output? Personally, I'm not really a fan of chunked HTML (searching through a single page HTML document is much simpler), but maybe I'm overlooking something. Mark ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
On 09.10.2017 8:27, Jiří Činčura wrote: Convert to Git and put it under FirebirdSQL organization on GitHub for extra visibility. It might even help with contributions. +1 Regards, Alexey -- 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] Doc funding - samples
Hi Jiří, Here they are in Russian http://www.ibase.ru/files/articles/firebird_examples/how_to_create_aplication_firebird_delphi_example_rus.pdf http://www.ibase.ru/files/articles/firebird_examples/how_to_create_application_firebird_sql_entity_framework_net_example_rus.pdf http://www.ibase.ru/files/articles/firebird_examples/how_to_create_application_firebird_sql_entity_framework_mvc_example_rus.pdf http://www.ibase.ru/files/articles/firebird_examples/how_to_add_Firebird_support_to_the_Laravel_framework.pdf http://www.ibase.ru/files/articles/firebird_examples/how_to_create_application_firebird_php.pdf and draft for Java https://github.com/sim1984/fbjavaex/releases/tag/1.0 Regards, Alexey > Hello, > > customer of mine wants to spend 1000-2000€ on doc funding > (https://www.firebirdsql.org/en/doc-funding-2017/), but he'd like to see > some samples of the content. Is it available somewhere? > -- 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
[Firebird-docs] Broken link
Hi, There is broken link (http://developer.postgresql.org/cvsweb.cgi/#dirlist) at the page http://firebirdsql.com/manual/docwritehowto-copyrights.html, using this text "http://developer.postgresql.org/cvsweb.cgi/pgsql-server/doc/src/sgml/; I assume that associated document should be regenerated and republished to remove this link? Regards, Alexey -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Let's move Firebird Langref to public beta
Hi, >We need reviewers who are fluent in English AND SQL. I am more than happy to coordinate so we can avoid covering territory that has already been covered. Please write news item to distribute at firebirdsql.org and through other channels - kind of Call for reviewers. I am sure there will be several volunteers which will satisfy your strict requirements. And, if it will be short and closed list, should we just give your contact email to them? Or suggest to subscribe to firebird-docs? Regards, Alexey -- ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
[Firebird-docs] Fwd: Another translation
It's a copy. Please confirm - do you see it? Regards, Alexey : Another translation : Mon, 09 Mar 2015 15:34:06 +0300 : Alexey Kovyazin a...@ib-aid.com : firebird-docs@lists.sourceforge.net Hi All, I've got another translation sample from another translator (there were some delays): https://yadi.sk/i/7oMVYZ-Tf8GbB Need your feedback. Regards, Alexey Kovyazin IBSurgeon -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Choosing the translation service
Hi All, I have submitted your feedback to translators, and they provided new version https://yadi.sk/i/vavPQbm7cqjK6 Please review it and let's decide - should we give these guys a chance or need to turn to another? I'm in negotiations with another company for test translation too, it should be ready next week. Regards, Alexey Kovyazin -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Choosing the translation service
Hi Martin, I think so. However, translation requires docx or odp formats. Regards, Alexey Kovyazin IBSurgeon Hi Alexey, will we get the final documentation in DocBook format? Kind regards, Martin it synergy GmbH -Ursprüngliche Nachricht- Von: Alexey Kovyazin [mailto:a...@ib-aid.com] Gesendet: Montag, 10. November 2014 09:38 An: firebird-docs@lists.sourceforge.net Betreff: [Firebird-docs] Choosing the translation service Hi All, As you know, we are going to translate recently completed Firebird Language Reference in Russian into English. For this purpose we are working with translation services. I need input from English speakers (native and not native :) about quality of the following test translation from one of the services: https://yadi.sk/i/uh1WeVY9ccChv Obviously, this translation needs some additional work, and also we can supply translator with some kind of guideline how to translate certain things in better way, but the question is: should we choose them or need to try another one? Regards, Alexey Kovyazin IBSurgeon -- ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
[Firebird-docs] Choosing the translation service
Hi All, As you know, we are going to translate recently completed Firebird Language Reference in Russian into English. For this purpose we are working with translation services. I need input from English speakers (native and not native :) about quality of the following test translation from one of the services: https://yadi.sk/i/uh1WeVY9ccChv Obviously, this translation needs some additional work, and also we can supply translator with some kind of guideline how to translate certain things in better way, but the question is: should we choose them or need to try another one? Regards, Alexey Kovyazin IBSurgeon -- ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Choosing the translation service
Hi Helen, thank you for feedback. I'll submit more texts for translations and present them here. Certainly we will need to provide some vocabulary for any translator - SQL is pretty narrow topic... Regards, Alexey At 09:37 p.m. 10/11/2014, Alexey Kovyazin wrote: Hi All, As you know, we are going to translate recently completed Firebird Language Reference in Russian into English. For this purpose we are working with translation services. I need input from English speakers (native and not native :) about quality of the following test translation from one of the services: https://yadi.sk/i/uh1WeVY9ccChv Obviously, this translation needs some additional work, and also we can supply translator with some kind of guideline how to translate certain things in better way, but the question is: should we choose them or need to try another one? On a quick read, 1. I sense that this translator does not have a good command of the use of articles in English (the, a/an, some. and constructs with no article). At best, it makes the text awkward to read for an English native speaker; at worst, the misuse of articles can make a difference to meaning, which could be a problem when translating the English version to other languages. It is a tedious editing task to go through text and correct these errors. (Believe me, I'm doing that all the time!!) If the person is being paid to translate, we should not be put in the position of needing to do such basic corrections. 2. Vocabulary choice in some cases needs to be reviewed. Referring to statements as operators is a bad choice in a language reference. The term operator has a distinct meaning in SQL and it is not that one! Similarly, use of the word events when talking about operations will cause confusion, even to native English speakers, given that the word event has a specific meaning in Firebird's procedural language. I found some other examples where vocab choice was inappropriate. Possibly the translator(s) should be given a set vocab of the terms most used in English for the various concepts. 3. Is the merging of keywords into one invalid word intentional? e.g. DROPPROCEDURE and other examples. If so, why? As far as I can tell, this occurs only in the explanatory text, not in the syntax patterns or the examples. I downloaded the sample, in the hope that I will have more time to study it when I get clear of release notes for a while. Helen -- ___ 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
