firebird-docs Mailing List for Firebird (Page 28)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hey Helen, get well soon. Best wishes.

Send me the files if you still need a volunteer. 

Cheers,
Norm.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Helen Borrie wrote:

> Sorry for the delay replying.  I have had a stroke with various
> negative effects that are not being rehabilitated very quickly.

Oh dear. I hope you're doing alright, Helen! Please take care.

> Working the github stuff is still defeating me.
> Can I send the updated 2.5.9 files to someone who could update
> the repository?

I'm still struggling with git(hub) too, but I suppose Mark or someone
else will volunteer :-)

Get well soon!

Cheers,
Paul

A couple of weeks ago Mark wrote

> I just noticed that the release notes in git are still at 2.5.8. What 
> happened to the 2.5.9 release notes?

Sorry for the delay replying.  I have had a stroke with various
negative effects that are not being rehabilitated very quickly.
Working the github stuff is still defeating me.

Can I send the updated 2.5.9 files to someone who could update the
repository?

Helen

Mark Rotteveel wrote:

> I had some problems with the Japanese rendering. I had to install the 
> Japanese Windows fonts, and I had to rebuild the font metrics files, and 
> rename the fonts from MSMincho to MS-Mincho and MSGothic to MS-Gothic. 
> Now it looks ok for me (I haven't committed those changes yet though).

Funny, just this afternoon I had the same experience trying to build the
Japanese docs. Then I looked at the "Using non-Western fonts" doc and
realized what the problem must be, but ran out of time. Will try again tonight.

Talking about metrics files, have you added gradle tasks for the three metrics
targets (t1metrics, ttfmetrics and ttcmetrics) or did you build them with ant
for now? People are going to need them, so if they're not already present
they'll have to be added sooner or later.

Cheers,
Paul Vinkenoog

On 11-02-2020 23:09, Paul Vinkenoog wrote:
> However... before burning our bridges we should do some more testing,
> especially with non-Western script sets (Japanese, Russian).

I had some problems with the Japanese rendering. I had to install the 
Japanese Windows fonts, and I had to rebuild the font metrics files, and 
rename the fonts from MSMincho to MS-Mincho and MSGothic to MS-Gothic. 
Now it looks ok for me (I haven't committed those changes yet though).

I'll double check the Russian rendering, although at first glance it 
looks OK, but maybe those metrics files need to be rebuilt as well.

Mark
-- 
Mark Rotteveel

Mark Rotteveel wrote:

> * I removed the foxon usage, because it caused errors with newer 
> versions of Apache FOP, and it wasn't immediately clear to me what this 
> was for

Foxon is something I created ages ago to make the .fo file more
human-readable. At that time, we often needed to hand-edit the .fo
in order to circumvent some limitations in Apache FOP that caused
ugly output. With newer versions of Apache FOP, this is no longer
necessary, so we can safely drop Foxon.

Paul Vinkneoog

Hi Mark,

> > I built several HTML and PDF targets successfully. But I noticed some structural
> > differences in the PDF's. The ones built with gradle opened with the navigation
> > bookmarks initially all collapsed, and the 'Table of Contents' bookmark entirely
> > missing.
>
> I found the cause for both: docbook-xsl 1.79.1 uses XSL 1.1 bookmarks by 
> default, instead of FOP specific bookmark handling. Setting 
> xsl1.1.bookmarks to 0 fixed the problem. Fix is now committed.

Thanks for the fixes; I built some PDF's and HTML and it all looks fine to me.

Cheers,
Paul

Mark Rotteveel wrote:

> I had noticed the changes in margin, but I actually thought it looked 
> better ;).

So do I, so let's keep them that way :-)

Paul

On 12-02-2020 11:11, Mark Rotteveel wrote:
> On 11-02-2020 23:00, Paul Vinkenoog wrote:
>> Hi Mark,
> 
>> I built several HTML and PDF targets successfully. But I noticed some 
>> structural
>> differences in the PDF's. The ones built with gradle opened with the 
>> navigation
>> bookmarks initially all collapsed, and the 'Table of Contents' 
>> bookmark entirely
>> missing.
> 
> I found the cause for both: docbook-xsl 1.79.1 uses XSL 1.1 bookmarks by 
> default, instead of FOP specific bookmark handling. Setting 
> xsl1.1.bookmarks to 0 fixed the problem. Fix is now committed.

Digging further, it looks like the title page on same level, and 
inclusion of TOC in the bookmarks is done by our customization in 
src/docs/xsl/fo/fop1.xsl.

Mark
-- 
Mark Rotteveel

On 11-02-2020 23:00, Paul Vinkenoog wrote:
> Hi Mark,

> I built several HTML and PDF targets successfully. But I noticed some structural
> differences in the PDF's. The ones built with gradle opened with the navigation
> bookmarks initially all collapsed, and the 'Table of Contents' bookmark entirely
> missing.

I found the cause for both: docbook-xsl 1.79.1 uses XSL 1.1 bookmarks by 
default, instead of FOP specific bookmark handling. Setting 
xsl1.1.bookmarks to 0 fixed the problem. Fix is now committed.

Mark
-- 
Mark Rotteveel

On 11-02-2020 23:00, Paul Vinkenoog wrote:
> Hi Mark,
> 
>> I'm currently working on a gradle build to replace the current ant-based
>> build for the documentation.
>>
>> It is a work-in-progress, but I'd really like some other eyes on its
>> output. So, could some of you please try it out, look at its output and
>> report any problems you see compared to the existing output of the ant
>> build, or with its usage?
> 
> I built several HTML and PDF targets successfully. But I noticed some structural
> differences in the PDF's. The ones built with gradle opened with the navigation
> bookmarks initially all collapsed, and the 'Table of Contents' bookmark entirely
> missing.

As far as I can tell, the reason for the initial collapse seems to be 
that the book title has a different level, which means all sections are 
collapsed under the title, while in the old version the title was on the 
same level as the sections, and sections were collapsed individually.

As to the missing bookmark of the Table of Contents, I have no idea yet.

> Also, in the gradle builds the vertical margin before the section headers was
> smaller. But maybe that's just because you adjusted some XSL parameters
> in your copy?

I had noticed the changes in margin, but I actually thought it looked 
better ;). In any case, I did not touch any XSL parameters, although 
I'll double check if maybe I skipped one. I'd sooner suspect the reason 
is upgrading to docbook-xsl 1.79.1, or possibly my removal of 
fo/fo-fix.xsl from fo.xsl (as far as I know those fixes are no longer 
necessary with FO 2.4.0). I'll experiment with that.

> Anyway, I'm too tired now to hunt down the source of there differences. I'll
> have another look at it tomorrow.

Thanks!

-- 
Mark Rotteveel

Hello Mark,

> Due to incompatible changes with regard to how the stylesheets are
> specified and resolved (specifically the imports), the Ant build doesn't
> work. (...)

> I'm wondering if I should invest time to 'fix' that or not. I think it
> is probably better to switch-over and tackle any issues that occur
> instead of allowing both to exist side-by-side.

Fully agreed. Your gradle setup clearly works, so let's concentrate on
ironing out the wrinkles and not waste time on keeping a soon-to-be-
abandoned system up.

However... before burning our bridges we should do some more testing,
especially with non-Western script sets (Japanese, Russian).

And I want my Table of Contents back, dammit! ;-)

Cheers,
Paul

Hi Mark,

> I'm currently working on a gradle build to replace the current ant-based 
> build for the documentation.
>
> It is a work-in-progress, but I'd really like some other eyes on its 
> output. So, could some of you please try it out, look at its output and 
> report any problems you see compared to the existing output of the ant 
> build, or with its usage?

I built several HTML and PDF targets successfully. But I noticed some structural
differences in the PDF's. The ones built with gradle opened with the navigation
bookmarks initially all collapsed, and the 'Table of Contents' bookmark entirely
missing.

Also, in the gradle builds the vertical margin before the section headers was
smaller. But maybe that's just because you adjusted some XSL parameters
in your copy?

Anyway, I'm too tired now to hunt down the source of there differences. I'll
have another look at it tomorrow.

Cheers,
Paul

Hi Mark,

thanks for the clarification.

Regards,
Martin

-----Ursprüngliche Nachricht-----
Von: Mark Rotteveel [mailto:ma...@la...] 
Gesendet: Montag, 10. Februar 2020 11:33
An: fir...@li...
Betreff: Re: [Firebird-docs] Wrong example in FB 4.0 Beta release notes

On 09-02-2020 22:38, Köditz, Martin wrote:
> I think we have a simple error in the release docs for FB 4.0 Beta 1:
> 
> Section
> 
> *More Window Functions* (Pages: 76-77) Ranking Functions:
> 
[..]
> 
> Simple Example
> The following example illustrates the behaviour of ranking functions. 
> SUM is included for comparison.
> 
> SQL> select
> CON> *id*,
> CON> salary,
[..]
> CON> order by salary;
> Statement failed, SQLSTATE = 42S22
> Dynamic SQL Error
> -SQL error code = -206
> -Column unknown
> -ID
> -At line 2, column
> 
> „id“ has to be „emp_no“. The same for the table.
> 
> Please verify. I don’t have an installation of FB 4.0.

That is only true if you assume the examples are against the example employee database, and that is not actually the case.

Both the [Firebird 3][1] and the Firebird 4 beta 1 release notes have used an `employee` table with columns `id`, `salary`, `department` for its window functions examples.

That table is explicitly introduced in the Firebird 3 release notes (see under "Aggregate Functions Used as Window Functions"_) with _"Imagine a table EMPLOYEE with columns ID, NAME and SALARY, [..]."_ (note that it doesn't define `department`, though that does get used and `name` does not).

Maybe that (corrected) definition needs to be repeated in the Firebird 4 release notes.

  [1]: 
https://www.firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-dml-windowfuncs.html

--
Mark Rotteveel

_______________________________________________
Firebird-docs mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-docs

On 09-02-2020 22:38, Köditz, Martin wrote:
> I think we have a simple error in the release docs for FB 4.0 Beta 1:
> 
> Section
> 
> *More Window Functions* (Pages: 76-77)
> Ranking Functions:
> 
[..]
> 
> Simple Example
> The following example illustrates the behaviour of ranking functions. 
> SUM is included for comparison.
> 
> SQL> select
> CON> *id*,
> CON> salary,
[..]
> CON> order by salary;
> Statement failed, SQLSTATE = 42S22
> Dynamic SQL Error
> -SQL error code = -206
> -Column unknown
> -ID
> -At line 2, column
> 
> „id“ has to be „emp_no“. The same for the table.
> 
> Please verify. I don’t have an installation of FB 4.0.

That is only true if you assume the examples are against the example 
employee database, and that is not actually the case.

Both the [Firebird 3][1] and the Firebird 4 beta 1 release notes have 
used an `employee` table with columns `id`, `salary`, `department` for 
its window functions examples.

That table is explicitly introduced in the Firebird 3 release notes (see 
under "Aggregate Functions Used as Window Functions"_) with _"Imagine a 
table EMPLOYEE with columns ID, NAME and SALARY, [..]."_ (note that it 
doesn't define `department`, though that does get used and `name` does not).

Maybe that (corrected) definition needs to be repeated in the Firebird 4 
release notes.

  [1]: 
https://www.firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-dml-windowfuncs.html

-- 
Mark Rotteveel

Hi Mark,

> I'm currently working on a gradle build to replace the current ant-based 
> build for the documentation.
>
> It is a work-in-progress, but I'd really like some other eyes on its 
> output. So, could some of you please try it out, look at its output and 
> report any problems you see compared to the existing output of the ant 
> build, or with its usage?

I'll try to make some time free for this tomorrow (i.e. Monday) or the day after.

Cheers,
Paul

Hi,

I think we have a simple error in the release docs for FB 4.0 Beta 1:

Section
More Window Functions (Pages: 76-77)
Ranking Functions:

DENSE_RANK() |
RANK() |
PERCENT_RANK() |
CUME_DIST() |
NTILE(<expr>) |
ROW_NUMBER()

Simple Example
The following example illustrates the behaviour of ranking functions. SUM is included for comparison.

SQL> select
CON> id,
CON> salary,
CON> dense_rank() over (order by salary),
CON> rank() over (order by salary),
CON> percent_rank() over (order by salary),
CON> cume_dist() over (order by salary),
CON> ntile(3) over (order by salary),
CON> row_number() over (order by salary),
CON> sum(1) over (order by salary)
CON> from employee
CON> order by salary;
Statement failed, SQLSTATE = 42S22
Dynamic SQL Error
-SQL error code = -206
-Column unknown
-ID
-At line 2, column

"id" has to be "emp_no". The same for the table.

Please verify. I don't have an installation of FB 4.0.

Regards,
Martin

I made some changes, the tasks are now generic and the base set name is 
specified with a commandline option:

gradlew docbookHtml

will build the entire firebirddocs set (firebirddocs is the default 
baseName)

gradlew docbookHtml --baseName=refdocs --docId=fblangref25

will build the Firebird 2.5 language reference

Same for docbookPdf and docbookMonohtml

I decided to include docbook in the task name in preparation of 
supporting asciidoc in the future.

Due to incompatible changes with regard to how the stylesheets are 
specified and resolved (specifically the imports), the Ant build doesn't 
work. Using ant requires using relative paths, while the gradle-based 
builds uses a catalog manager to resolve stylesheets by their URI.

For example to make ant work again, it is necessary to replace

<xsl:import 
href="http://docbook.sourceforge.net/release/xsl/current/fo/docbook.xsl"/>

with

<xsl:import href="../../../tools/docbook-stylesheets/fo/docbook.xsl"/>

I'm wondering if I should invest time to 'fix' that or not. I think it 
is probably better to switch-over and tackle any issues that occur 
instead of allowing both to exist side-by-side.

Mark

On 07-02-2020 18:26, Mark Rotteveel wrote:
> I'm currently working on a gradle build to replace the current ant-based 
> build for the documentation.
> 
> It is a work-in-progress, but I'd really like some other eyes on its 
> output. So, could some of you please try it out, look at its output and 
> report any problems you see compared to the existing output of the ant 
> build, or with its usage?
> 
> The gradle version used requires Java 8 or higher.
> 
> You can find this work-in-progress in the branch gradle-conv-attempt-3 
> in my fork of the repository 
> https://github.com/mrotteveel/firebird-documentation
> 
> Some examples:
> 
> Building docs can be done with
> gradlew firebirddocsHtml
> 
> building German docs can be done with
> gradlew firebirddocsHtml --language=de
> 
> building the nullguide as PDF can be done with
> gradlew firebirddocsPdf --docId=nullguide
> 
> (on Linux or MacOS you may have to use ./gradlew, in PowerShell, you may 
> have to use .\gradlew)
> 
> There are separate tasks for release notes, papers and reference docs. 
> Beware, the commandline parameters are per task, so if for example you 
> want html and pdf in German in one execute, you must use:
> 
> gradlew firebirddocsPdf --language=de firebirddocsHtml --language=de
> 
> To see all tasks:
> gradlew tasks --group=documentation
> 
> Help for a specific task (is pretty sparse though):
> gradlew help --task=rlsnotesHtml
> 
> Some important changes:
> 
> * The gradle build does not use the lib/ and tools/ folders (though the 
> XML currently still contains relative references to the tools folder, 
> which I want to fix once I'm done)
> * The ant-build used some conditional behaviour that drove me a bit 
> crazy to replicate when implementing this, so I changed the following to 
> ensure consistency
> ** No more special handling for firebirddocs English set (so output is 
> in - for example - build/html-firebirddocs, and not in build/html, and 
> the root firebirddocs.xml has been moved into the firebirddocs/ folder)
> ** Every base-set now has an XSLT file (eg html-firebirddocs.xsl) 
> without falling back to html.xsl if such a file does not exist
> * I removed the foxon usage, because it caused errors with newer 
> versions of Apache FOP, and it wasn't immediately clear to me what this 
> was for
> * Build uses docbook XSL 1.79.1 (ant build uses 1.72.0)
> * Apache FOP 2.4 (ant build uses 0.95-1 I think)
> 
> Some things that I haven't worked on yet:
> 
> * Language specific FOP configuration
> * Rewriting the readme
> * ... not verified everything
> 
> Important caveat: this is a work in progress. Naming of tasks and 
> options isn't final yet. For example, I am still considering changing 
> this to use a single task per output type instead of a task per (output 
> type) x (base name), and configure the base name through a commandline 
> option (eg gradlew html --baseName=rlsnotes instead of gradlew 
> rlsnotesHtml)
> 
> I made some changes to the ant build to make it consistent with the 
> changes I made for the firebirddocs base name, but I haven't actually 
> tested that yet.
> 
> Mark

-- 
Mark Rotteveel

I just noticed that the release notes in git are still at 2.5.8. What 
happened to the 2.5.9 release notes?

Mark
-- 
Mark Rotteveel

I'm currently working on a gradle build to replace the current ant-based 
build for the documentation.

It is a work-in-progress, but I'd really like some other eyes on its 
output. So, could some of you please try it out, look at its output and 
report any problems you see compared to the existing output of the ant 
build, or with its usage?

The gradle version used requires Java 8 or higher.

You can find this work-in-progress in the branch gradle-conv-attempt-3 
in my fork of the repository 
https://github.com/mrotteveel/firebird-documentation

Some examples:

Building docs can be done with
gradlew firebirddocsHtml

building German docs can be done with
gradlew firebirddocsHtml --language=de

building the nullguide as PDF can be done with
gradlew firebirddocsPdf --docId=nullguide

(on Linux or MacOS you may have to use ./gradlew, in PowerShell, you may 
have to use .\gradlew)

There are separate tasks for release notes, papers and reference docs. 
Beware, the commandline parameters are per task, so if for example you 
want html and pdf in German in one execute, you must use:

gradlew firebirddocsPdf --language=de firebirddocsHtml --language=de

To see all tasks:
gradlew tasks --group=documentation

Help for a specific task (is pretty sparse though):
gradlew help --task=rlsnotesHtml

Some important changes:

* The gradle build does not use the lib/ and tools/ folders (though the 
XML currently still contains relative references to the tools folder, 
which I want to fix once I'm done)
* The ant-build used some conditional behaviour that drove me a bit 
crazy to replicate when implementing this, so I changed the following to 
ensure consistency
** No more special handling for firebirddocs English set (so output is 
in - for example - build/html-firebirddocs, and not in build/html, and 
the root firebirddocs.xml has been moved into the firebirddocs/ folder)
** Every base-set now has an XSLT file (eg html-firebirddocs.xsl) 
without falling back to html.xsl if such a file does not exist
* I removed the foxon usage, because it caused errors with newer 
versions of Apache FOP, and it wasn't immediately clear to me what this 
was for
* Build uses docbook XSL 1.79.1 (ant build uses 1.72.0)
* Apache FOP 2.4 (ant build uses 0.95-1 I think)

Some things that I haven't worked on yet:

* Language specific FOP configuration
* Rewriting the readme
* ... not verified everything

Important caveat: this is a work in progress. Naming of tasks and 
options isn't final yet. For example, I am still considering changing 
this to use a single task per output type instead of a task per (output 
type) x (base name), and configure the base name through a commandline 
option (eg gradlew html --baseName=rlsnotes instead of gradlew rlsnotesHtml)

I made some changes to the ant build to make it consistent with the 
changes I made for the firebirddocs base name, but I haven't actually 
tested that yet.

Mark
-- 
Mark Rotteveel

On 20-01-2020 19:25, Paul Vinkenoog wrote:
> Mark wrote:
> 
>>> Also, at lines 320-324 (that's the bit about how we used to keep tools and
>>> lib binaries in the CVS repository): you've changed that to 'git repository',
>>> but of course they were never in there.
>>
>> Technically they are in the git repository as well, as I preserved the
>> history during migration, but I get your point ;)
> 
> Ah, OK -- it's always good to be precise! :-)
> 
>> I'll do a revision to remove that and then merge.
> 
> Good, thanks again!

I have released the modified docs to the website.

Mark
-- 
Mark Rotteveel

  Branch: refs/heads/master
  Home:   https://github.com/FirebirdSQL/firebird-documentation
  Commit: 85b786a5c21f9d955ee161b5d926df3698a4c346
      https://github.com/FirebirdSQL/firebird-documentation/commit/85b786a5c21f9d955ee161b5d926df3698a4c346
  Author: Mark Rotteveel <mro...@us...>
  Date:   2020-01-25 (Sat, 25 Jan 2020)

  Changed paths:
    M .gitignore
    M src/docs/firebirddocs/docbuilding-howto.xml
    M src/docs/firebirddocs/docwriting-howto.xml

  Log Message:
  -----------
  Update doc howtos for git usage (#10)

* Update docbuilding-howto with git information

* Replace CVS instructions with basic git instructions

* Remove history lesson about binaries in repository

Mark wrote:

> > Also, at lines 320-324 (that's the bit about how we used to keep tools and
> > lib binaries in the CVS repository): you've changed that to 'git repository',
> > but of course they were never in there.
> 
> Technically they are in the git repository as well, as I preserved the 
> history during migration, but I get your point ;)

Ah, OK -- it's always good to be precise! :-)

> I'll do a revision to remove that and then merge.

Good, thanks again!

Cheers,
Paul

On 20-01-2020 15:45, Paul Vinkenoog wrote:
> Hi Mark,
> 
>>> I have created a pull request with some changes:
>>> https://github.com/FirebirdSQL/firebird-documentation/pull/10
>>
>> I would really like a second pair of eyes on this, otherwise I will
>> merge and release this next weekend.
>   
> Looks very good to me, but I'm still a git newbie so any git-technical errors
> may have eluded me.

> Also, at lines 320-324 (that's the bit about how we used to keep tools and
> lib binaries in the CVS repository): you've changed that to 'git repository',
> but of course they were never in there.

Technically they are in the git repository as well, as I preserved the 
history during migration, but I get your point ;)

> More importantly, this has become
> useless information. Nobody cares - or should care - where we kept those
> binaries in a distant past. So I would cut away most of this section and just
> make sure that they can find them now. That is, keep the lines pointing the
> reader to the readmes.

I'll do a revision to remove that and then merge.

Mark
-- 
Mark Rotteveel

Hi Mark,

> > I have created a pull request with some changes:
> > https://github.com/FirebirdSQL/firebird-documentation/pull/10
>
> I would really like a second pair of eyes on this, otherwise I will 
> merge and release this next weekend.

Looks very good to me, but I'm still a git newbie so any git-technical errors
may have eluded me.

Also, at lines 320-324 (that's the bit about how we used to keep tools and
lib binaries in the CVS repository): you've changed that to 'git repository',
but of course they were never in there. More importantly, this has become
useless information. Nobody cares - or should care - where we kept those
binaries in a distant past. So I would cut away most of this section and just
make sure that they can find them now. That is, keep the lines pointing the
reader to the readmes.

Thanks for the work you're doing on the documentation!

Cheers,
Paul

2001	Jan	Feb (1)	Mar	Apr (36)	May (56)	Jun (1)	Jul (5)	Aug (3)	Sep (1)	Oct	Nov	Dec (1)
2002	Jan	Feb	Mar (15)	Apr (5)	May (7)	Jun (5)	Jul (3)	Aug (6)	Sep (3)	Oct (8)	Nov (23)	Dec (21)
2003	Jan (25)	Feb (37)	Mar (59)	Apr (11)	May (8)	Jun (24)	Jul (18)	Aug (29)	Sep (30)	Oct (11)	Nov (20)	Dec (5)
2004	Jan (43)	Feb (24)	Mar (61)	Apr (14)	May (23)	Jun (50)	Jul (13)	Aug (56)	Sep (55)	Oct (64)	Nov (94)	Dec (27)
2005	Jan (40)	Feb (10)	Mar (55)	Apr (20)	May (16)	Jun (6)	Jul (58)	Aug (38)	Sep (5)	Oct (6)	Nov (71)	Dec (99)
2006	Jan (6)	Feb (15)	Mar (22)	Apr (9)	May (31)	Jun (35)	Jul (47)	Aug (18)	Sep (21)	Oct (24)	Nov (63)	Dec (79)
2007	Jan (22)	Feb (40)	Mar (47)	Apr (69)	May (22)	Jun (20)	Jul (25)	Aug (13)	Sep (7)	Oct (44)	Nov (76)	Dec (1)
2008	Jan (26)	Feb (30)	Mar (120)	Apr (14)	May (22)	Jun (40)	Jul (48)	Aug (7)	Sep (34)	Oct (31)	Nov	Dec (30)
2009	Jan (9)	Feb (6)	Mar (9)	Apr (2)	May (9)	Jun	Jul (31)	Aug (32)	Sep (15)	Oct (23)	Nov	Dec (9)
2010	Jan (19)	Feb (9)	Mar	Apr	May (9)	Jun (6)	Jul (8)	Aug (21)	Sep (10)	Oct (1)	Nov (3)	Dec (33)
2011	Jan	Feb (1)	Mar (4)	Apr (10)	May	Jun (9)	Jul (23)	Aug (2)	Sep (35)	Oct (36)	Nov	Dec (4)
2012	Jan (3)	Feb (8)	Mar (3)	Apr	May	Jun (5)	Jul	Aug	Sep	Oct (12)	Nov (12)	Dec
2013	Jan (18)	Feb (5)	Mar (1)	Apr	May	Jun (5)	Jul	Aug (21)	Sep	Oct (5)	Nov (1)	Dec (11)
2014	Jan	Feb	Mar (4)	Apr (2)	May	Jun	Jul (2)	Aug (5)	Sep (6)	Oct	Nov (29)	Dec
2015	Jan	Feb	Mar (14)	Apr	May	Jun	Jul (7)	Aug (7)	Sep (5)	Oct	Nov (6)	Dec (3)
2016	Jan (14)	Feb (9)	Mar (33)	Apr (12)	May (18)	Jun (3)	Jul	Aug (15)	Sep	Oct	Nov	Dec (22)
2017	Jan	Feb	Mar	Apr	May (10)	Jun	Jul	Aug	Sep	Oct (44)	Nov (32)	Dec (8)
2018	Jan (2)	Feb (25)	Mar (16)	Apr (11)	May (1)	Jun (19)	Jul (3)	Aug	Sep	Oct (25)	Nov	Dec
2019	Jan	Feb (2)	Mar	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov (2)	Dec (3)
2020	Jan (29)	Feb (28)	Mar (13)	Apr (13)	May (107)	Jun (75)	Jul (57)	Aug (36)	Sep (3)	Oct (4)	Nov (4)	Dec (1)
2021	Jan (2)	Feb (13)	Mar (5)	Apr (6)	May (44)	Jun (9)	Jul (9)	Aug (3)	Sep (11)	Oct (5)	Nov (14)	Dec (19)
2022	Jan (1)	Feb	Mar	Apr (4)	May (1)	Jun (1)	Jul (13)	Aug (6)	Sep (2)	Oct (7)	Nov (2)	Dec
2023	Jan (2)	Feb	Mar (13)	Apr (2)	May (31)	Jun (12)	Jul (5)	Aug (5)	Sep (27)	Oct (7)	Nov (25)	Dec (7)
2024	Jan (11)	Feb (27)	Mar (3)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

firebird-docs Mailing List for Firebird (Page 28)

A powerful, cross platform, SQL database system

firebird-docs — chat stuff about documentation