You can subscribe to this list here.
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
|
From: Mark R. <ma...@la...> - 2020-06-01 16:18:35
|
On 01-06-2020 18:09, Paul Vinkenoog wrote: > Mark Rotteveel wrote: >> 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 > > That's two links to the HTML ;-) > > Of course it wasn't rocket science to find the PDF: > > https://firebirdsql.org/file/documentation/pdf/en/refdocs/fblangref25/firebird-25-language-reference.pdf Thanks. I guess I forgot to 'copy' the link from my PDF browser tab before pasting in the email. Mark -- Mark Rotteveel |
From: Paul V. <pa...@vi...> - 2020-06-01 16:10:06
|
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 That's two links to the HTML ;-) Of course it wasn't rocket science to find the PDF: https://firebirdsql.org/file/documentation/pdf/en/refdocs/fblangref25/firebird-25-language-reference.pdf Cheers, Paul Vinkenoog |
From: Mark R. <ma...@la...> - 2020-06-01 15:54:46
|
On 29-05-2020 18:52, Mark Rotteveel wrote: > I hadn't noticed it before, but the names of these files don't match the > standard output of the build. The intent is for it to be possible to > upload the build output without having to manually rename files. So to > produce the right output, the German AsciiDoc file should match the > intended output filename (for the names above, `firebird-fbcache-de.adoc`). > > We may want to consider tweaking the filenames further (eg to > `firebird-cache` for English and `firebird-cache-de` for German), this > avoids the repetition of `firebird` and its abbreviation `fb`. I renamed these according to my suggestion above. The old name currently links to the new file, and I will ask Sergey to put in place a redirect later this week. Mark -- Mark Rotteveel |
From: Mark R. <ma...@la...> - 2020-06-01 15:52:43
|
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 -- Mark Rotteveel |
From: Mark R. <no...@gi...> - 2020-06-01 15:39:39
|
Branch: refs/heads/master Home: https://github.com/FirebirdSQL/firebird-documentation Commit: 644dc548488f8d2847833b79d42465940cfa57a3 https://github.com/FirebirdSQL/firebird-documentation/commit/644dc548488f8d2847833b79d42465940cfa57a3 Author: Mark Rotteveel <ma...@la...> Date: 2020-06-01 (Mon, 01 Jun 2020) Changed paths: A src/docs/asciidoc/de/firebirddocs/fbcache/firebird-cache-de.adoc R src/docs/asciidoc/de/firebirddocs/fbcache/firebird-fbcache.adoc A src/docs/asciidoc/en/firebirddocs/fbcache/firebird-cache.adoc R src/docs/asciidoc/en/firebirddocs/fbcache/firebird-fbcache.adoc Log Message: ----------- Rename firebird-fbcache to conform to naming convention Commit: 636bdd908d64109c8cc06dceba39fc96cde9c871 https://github.com/FirebirdSQL/firebird-documentation/commit/636bdd908d64109c8cc06dceba39fc96cde9c871 Author: Mark Rotteveel <ma...@la...> Date: 2020-06-01 (Mon, 01 Jun 2020) Changed paths: M src/docs/asciidoc/fb-docs-redirects.txt Log Message: ----------- Document redirects necessary for fbcache Compare: https://github.com/FirebirdSQL/firebird-documentation/compare/e3bdf90a344f...636bdd908d64 |
From: Mark R. <no...@gi...> - 2020-06-01 14:58:43
|
Branch: refs/heads/master Home: https://github.com/FirebirdSQL/firebird-documentation Commit: e3bdf90a344f46381b6d489849d2afac500a77c5 https://github.com/FirebirdSQL/firebird-documentation/commit/e3bdf90a344f46381b6d489849d2afac500a77c5 Author: Mark Rotteveel <ma...@la...> Date: 2020-06-01 (Mon, 01 Jun 2020) Changed paths: R src/docs/firebirddocs-de/fbcache-de.xml M src/docs/firebirddocs-de/firebirddocs-de.xml R src/docs/firebirddocs/fbcache.xml M src/docs/firebirddocs/firebirddocs.xml Log Message: ----------- Remove fbcache en fbcache-de that have been converted to DocBook |
From: Mark R. <no...@gi...> - 2020-06-01 14:58:01
|
Branch: refs/heads/master Home: https://github.com/FirebirdSQL/firebird-documentation Commit: 91ce49114dc143dc000683acb693e46ade5802e7 https://github.com/FirebirdSQL/firebird-documentation/commit/91ce49114dc143dc000683acb693e46ade5802e7 Author: Mark Rotteveel <ma...@la...> Date: 2020-06-01 (Mon, 01 Jun 2020) Changed paths: M src/theme/firebird-pdf/firebird-theme.yml Log Message: ----------- Revert table padding, and extend from default-with-fallback-font |
From: Mark R. <no...@gi...> - 2020-06-01 14:37:11
|
Branch: refs/heads/master Home: https://github.com/FirebirdSQL/firebird-documentation Commit: 68e3b847190143c30112a7bd565024e7108dfe3a https://github.com/FirebirdSQL/firebird-documentation/commit/68e3b847190143c30112a7bd565024e7108dfe3a Author: Mark Rotteveel <ma...@la...> Date: 2020-06-01 (Mon, 01 Jun 2020) Changed paths: M src/docs/asciidoc/en/asciidoc-migration/asciidoc-migration.adoc Log Message: ----------- small not on spanned rows in tables Commit: f3f5648b2b404d275b5446b416a8a98c088cdaaf https://github.com/FirebirdSQL/firebird-documentation/commit/f3f5648b2b404d275b5446b416a8a98c088cdaaf Author: Mark Rotteveel <ma...@la...> Date: 2020-06-01 (Mon, 01 Jun 2020) Changed paths: M src/theme/firebird-html/firebird.css M src/theme/firebird-pdf/firebird-theme.yml Log Message: ----------- Theme fixes * show code in definition list as bold * increase horizontal padding on tables in PDF Commit: 46b77b631cf4775324f90765e19460a9a2ffb894 https://github.com/FirebirdSQL/firebird-documentation/commit/46b77b631cf4775324f90765e19460a9a2ffb894 Author: Mark Rotteveel <ma...@la...> Date: 2020-06-01 (Mon, 01 Jun 2020) Changed paths: A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-appx01-supplement.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-appx02-errorcodes.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-appx03-reskeywords.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-appx04-systables.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-appx05-montables.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-appx06-charsets.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-appx07-license.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-commons.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-datatypes.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-ddl.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-dml.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-dochist.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-functions-vars.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-intro.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-psql.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-security.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-structure.adoc A src/docs/asciidoc/en/refdocs/fblangref25/_fblangref25-transacs.adoc A src/docs/asciidoc/en/refdocs/fblangref25/firebird-25-language-reference.adoc R src/docs/refdocs/langref/fblangref25/fblangref25-appx01-supplement.xml R src/docs/refdocs/langref/fblangref25/fblangref25-appx02-errorcodes.xml R src/docs/refdocs/langref/fblangref25/fblangref25-appx03-reskeywords.xml R src/docs/refdocs/langref/fblangref25/fblangref25-appx04-systables.xml R src/docs/refdocs/langref/fblangref25/fblangref25-appx05-montables.xml R src/docs/refdocs/langref/fblangref25/fblangref25-appx06-charsets.xml R src/docs/refdocs/langref/fblangref25/fblangref25-appx07-license.xml R src/docs/refdocs/langref/fblangref25/fblangref25-commons.xml R src/docs/refdocs/langref/fblangref25/fblangref25-datatypes.xml R src/docs/refdocs/langref/fblangref25/fblangref25-ddl.xml R src/docs/refdocs/langref/fblangref25/fblangref25-dml.xml R src/docs/refdocs/langref/fblangref25/fblangref25-dochist.xml R src/docs/refdocs/langref/fblangref25/fblangref25-functions-vars.xml R src/docs/refdocs/langref/fblangref25/fblangref25-intro.xml R src/docs/refdocs/langref/fblangref25/fblangref25-psql.xml R src/docs/refdocs/langref/fblangref25/fblangref25-security.xml R src/docs/refdocs/langref/fblangref25/fblangref25-structure.xml R src/docs/refdocs/langref/fblangref25/fblangref25-transacs.xml R src/docs/refdocs/langref/fblangref25/fblangref25.xml M src/docs/refdocs/refdocs.xml Log Message: ----------- Migrate Firebird 2.5 Language Reference to AsciiDoc Compare: https://github.com/FirebirdSQL/firebird-documentation/compare/01047865753c...46b77b631cf4 |
From: Mark R. <no...@gi...> - 2020-06-01 09:16:04
|
Branch: refs/heads/master Home: https://github.com/FirebirdSQL/firebird-documentation Commit: 01047865753c8de68b39976eb2ffc2e9fab8c500 https://github.com/FirebirdSQL/firebird-documentation/commit/01047865753c8de68b39976eb2ffc2e9fab8c500 Author: Mark Rotteveel <ma...@la...> Date: 2020-06-01 (Mon, 01 Jun 2020) Changed paths: M build.gradle M buildSrc/src/main/groovy/org/firebirdsql/documentation/asciidoc/FbAsciidocHtmlTask.groovy M buildSrc/src/main/groovy/org/firebirdsql/documentation/asciidoc/FbAsciidocPdfTask.groovy Log Message: ----------- Fix propagation of include pattern and dirty detection The fix is a bit hackish, but I can't see a cleaner route while still working along with the task for the asciidoctor-gradle plugin. Also fixed issue where the task ignored the asciidoctorj config, and thus used the wrong version of asciidoctor-pdf |
From: Paul V. <pa...@vi...> - 2020-05-31 18:23:38
|
Hello Mark, >>> Any objections if I just remove this caution in the new version? >> >> No, please correct this. I sometimes use expressions for ordering >> levels, e.g. with IIF or DECODE constructs that return, say, the >> numbers 1, 2 and 3, and they do the expected thing in Fb 2.5 and 3, >> i.e. they sort by the numerical value returned, not by the contents >> of column 1, 2 or 3. > > Did you mean "No, I have no objections", or "No, don't remove it, but > correct it"? I meant: no objections, please remove the incorrect caution! (I.e., correct the section by removing what's incorrect.) > The caution is entirely wrong. I could write another note > to explain the actual behaviour, but that sounds more like an > improvement for later than removing factually incorrect information. I guess that's up to you. The most important thing is to remove incorrect information. Then, while you're at it, *if* you have time and *if* you feel like it, you could write a useful and correct note. But that can also wait till later. > > It would be silly anyway, because the value of X+Y may vary wildly > > across rows, so which one would determine the column number > > to sort by? > > > > Maybe what they're (trying to) say is true for constant expressions > > and/or expressions involving only constants and local variables in > > PSQL. > > Constant expressions other than `number` or `(number)` sort by the value > as well (so `1+1` does not sort by column 2). You're right. > Sorting by a PSQL variable > (is that possible?) will likely also not sort by column position, as the > sort needs to be known at prepare time. > > Interestingly enough, Firebird does perform some sort of sort when using > constant expressions. Without thorough testing it looks like it performs > an equivalent of `ORDER BY <all columns of the select clause>`, but that > might just be the limited set of data I used when testing. I just played around a bit and indeed it seems that adding an ordering item like "3+2" - with or without parentheses - causes some ordering pattens in (parts of) the output, but I'm not able to tell what it does exactly - if anything! Cheers, Paul |
From: Mark R. <ma...@la...> - 2020-05-31 17:59:36
|
On 31-05-2020 18:37, Paul Vinkenoog wrote: > Mark Rotteveel wrote: >> Any objections if I just remove this caution in the new version? > > No, please correct this. I sometimes use expressions for ordering > levels, e.g. with IIF or DECODE constructs that return, say, the > numbers 1, 2 and 3, and they do the expected thing in Fb 2.5 and 3, > i.e. they sort by the numerical value returned, not by the contents > of column 1, 2 or 3. Did you mean "No, I have no objections", or "No, don't remove it, but correct it"? The caution is entirely wrong. I could write another note to explain the actual behaviour, but that sounds more like an improvement for later than removing factually incorrect information. > It would be silly anyway, because the value of X+Y may vary wildly > across rows, so which one would determine the column number > to sort by? > > Maybe what they're (trying to) say is true for constant expressions > and/or expressions involving only constants and local variables in > PSQL. Constant expressions other than `number` or `(number)` sort by the value as well (so `1+1` does not sort by column 2). Sorting by a PSQL variable (is that possible?) will likely also not sort by column position, as the sort needs to be known at prepare time. Interestingly enough, Firebird does perform some sort of sort when using constant expressions. Without thorough testing it looks like it performs an equivalent of `ORDER BY <all columns of the select clause>`, but that might just be the limited set of data I used when testing. Mark -- Mark Rotteveel |
From: Paul V. <pa...@vi...> - 2020-05-31 16:37:39
|
Mark Rotteveel wrote: > While going over the language reference to do some manual fixes, I came > across the following caution (see > https://firebirdsql.org/file/documentation/reference_manuals/fblangref25-en/html/fblangref25-dml-select.html#fblangref25-dml-select-orderby-unions > > """ > Expressions whose calculation results are non-negative integers will be > interpreted as column position numbers and will cause an exception if > they fall outside the range from 1 to the number of columns. > > Example: > > SELECT > X, Y, NOTE > FROM PAIRS > ORDER BY X+Y DESC > > > * The number returned by a function or a procedure is unpredictable, > regardless of whether the sort order is defined by the expression itself > or by the column number > * Only non-negative integers are interpreted as column numbers > * An integer obtained by one-time evaluation of an expression or by > parameter substitution is saved as a constant, because this value > applies to all rows. > """ > > I just tested this in Firebird 2.5 and 1.5, and this is not actually the > case (and I would be surprised if it ever has been the case). The value > of an expression itself is used to sort. As far as I'm aware only > literal or parenthesized literal values can be used to identify column > positions. > > Any objections if I just remove this caution in the new version? No, please correct this. I sometimes use expressions for ordering levels, e.g. with IIF or DECODE constructs that return, say, the numbers 1, 2 and 3, and they do the expected thing in Fb 2.5 and 3, i.e. they sort by the numerical value returned, not by the contents of column 1, 2 or 3. It would be silly anyway, because the value of X+Y may vary wildly across rows, so which one would determine the column number to sort by? Maybe what they're (trying to) say is true for constant expressions and/or expressions involving only constants and local variables in PSQL. Paul Vinkenoog |
From: Mark R. <ma...@la...> - 2020-05-31 16:05:53
|
While going over the language reference to do some manual fixes, I came across the following caution (see https://firebirdsql.org/file/documentation/reference_manuals/fblangref25-en/html/fblangref25-dml-select.html#fblangref25-dml-select-orderby-unions """ Expressions whose calculation results are non-negative integers will be interpreted as column position numbers and will cause an exception if they fall outside the range from 1 to the number of columns. Example: SELECT X, Y, NOTE FROM PAIRS ORDER BY X+Y DESC * The number returned by a function or a procedure is unpredictable, regardless of whether the sort order is defined by the expression itself or by the column number * Only non-negative integers are interpreted as column numbers * An integer obtained by one-time evaluation of an expression or by parameter substitution is saved as a constant, because this value applies to all rows. """ I just tested this in Firebird 2.5 and 1.5, and this is not actually the case (and I would be surprised if it ever has been the case). The value of an expression itself is used to sort. As far as I'm aware only literal or parenthesized literal values can be used to identify column positions. Any objections if I just remove this caution in the new version? Mark -- Mark Rotteveel |
From: Paul V. <pa...@vi...> - 2020-05-30 22:51:47
|
Mark Rotteveel wrote: >> I like that better and I think that, between the tables, I'd still prefer the >> autowidth, but with 2-3 times more right-padding than left-padding. > > Given the text is left-aligned, why would more right-padding than > left-padding be important? It's easier to the human eye. It feels a bit cramped if the cell is closed immediately after the text ('immediately' meaning with the same space as on the left side). Of course this only matters for the cell(s) with the longest lines in auto-width tables. But please forget it, I don't want to waste too much of your time on such details. I really appreciate what you are doing, and all three alternatives are more than adequate (except for the autowidth bug in the PDF). > Apparently, this is a bug in the prawn-table library asciidoctor-pdf > uses to render the table (it didn't take the actual font-size into > account or something). It is supposedly fixed upstream, but that fix > hasn't been released. It should be possible to monkey-patch it, but it > isn't exactly clear how to do that for the Gradle plugin, if it is > possible at all, and I think my time is better spent on converting the > documentation. Agreed. > In any case, I have updated the example: > > 1. More padding > 2. Fourth example, with autowidth in HTML output and fullwidth in PDF Thanks, they look fine. I'm still pro-table, but I seem to be the only one ;-) So maybe we should just pick the majority choice. Cheers, Paul |
From: Mark R. <ma...@la...> - 2020-05-30 16:39:37
|
On 30-05-2020 16:25, Paul Vinkenoog wrote: >> I have updated the examples (same links): >> >> - little bit more padding in PDF > > I don't see that (but can't compare with the previous rendering, obviously) > and the 'r' is still on the next line. Maybe my increase was too conservative (I increased from 2px to 4px). I have no increased it to 8px >> - Column heading left-aligned >> - No striping > > I like that better and I think that, between the tables, I'd still prefer the > autowidth, but with 2-3 times more right-padding than left-padding. Given the text is left-aligned, why would more right-padding than left-padding be important? > But like I said earlier: all 3 are OK, and if somehow the rendering of > autowidth columns in the PDF's is problematic, we'd better forget about > that alternative unless it's really easy to fix in a short time. Apparently, this is a bug in the prawn-table library asciidoctor-pdf uses to render the table (it didn't take the actual font-size into account or something). It is supposedly fixed upstream, but that fix hasn't been released. It should be possible to monkey-patch it, but it isn't exactly clear how to do that for the Gradle plugin, if it is possible at all, and I think my time is better spent on converting the documentation. In any case, I have updated the example: 1. More padding 2. Fourth example, with autowidth in HTML output and fullwidth in PDF Mark -- Mark Rotteveel |
From: Paul V. <pa...@vi...> - 2020-05-30 14:26:23
|
Hi MArk, > I have updated the examples (same links): > > - little bit more padding in PDF I don't see that (but can't compare with the previous rendering, obviously) and the 'r' is still on the next line. > - Column heading left-aligned > - No striping I like that better and I think that, between the tables, I'd still prefer the autowidth, but with 2-3 times more right-padding than left-padding. But like I said earlier: all 3 are OK, and if somehow the rendering of autowidth columns in the PDF's is problematic, we'd better forget about that alternative unless it's really easy to fix in a short time. Cheers, Paul |
From: Mark R. <ma...@la...> - 2020-05-30 13:36:36
|
On 30-05-2020 14:57, Mark Rotteveel wrote: > It should be bold as well in the HTML, but there is a conflict in style > rules, which means text in code tags is rendered in font-weight normal. > I'll fix that later. Style is now also updated in the HTML (may need a hard refresh to see it). Mark -- Mark Rotteveel |
From: Mark R. <ma...@la...> - 2020-05-30 12:57:14
|
On 30-05-2020 13:06, Paul Vinkenoog wrote: > Mark Rotteveel wrote: > >> I'm currently converting the Firebird Language Reference, and I was >> wondering if there is a preference in the rendering of parameter lists >> as used for function arguments and for syntax elements (in the current >> language reference, a table is used). >> >> I would like to have input on what style to apply >> >> I have prepared three example: >> 1. full width table >> 2. autowidth table (which seems to have width issues in PDF) >> 3. definition list > > The tables look clearer to me. You 'get' them in one glance. In general > I'd prefer autowidth, but it doesn't work well in the PDF (quite apart > from the in-word break in 'Parameter', there's too little horizontal > padding) and full width is fine too. I can increase the padding for tables in the PDF through the stylesheet. > However, above left-aligned > columns I'd also left-align the headers. And we could do without the > useless striping in the HTML tables. I have updated the examples (same links): - little bit more padding in PDF - Column heading left-aligned - No striping > All that said, I think the definition list is fine as well. A little > better in the PDF, probably because of the boldfacing of the terms (if > they are - at least they look a tad darker to me). It should be bold as well in the HTML, but there is a conflict in style rules, which means text in code tags is rendered in font-weight normal. I'll fix that later. Mark -- Mark Rotteveel |
From: Paul V. <pa...@vi...> - 2020-05-30 11:07:18
|
Mark Rotteveel wrote: > I'm currently converting the Firebird Language Reference, and I was > wondering if there is a preference in the rendering of parameter lists > as used for function arguments and for syntax elements (in the current > language reference, a table is used). > > I would like to have input on what style to apply > > I have prepared three example: > 1. full width table > 2. autowidth table (which seems to have width issues in PDF) > 3. definition list The tables look clearer to me. You 'get' them in one glance. In general I'd prefer autowidth, but it doesn't work well in the PDF (quite apart from the in-word break in 'Parameter', there's too little horizontal padding) and full width is fine too. However, above left-aligned columns I'd also left-align the headers. And we could do without the useless striping in the HTML tables. All that said, I think the definition list is fine as well. A little better in the PDF, probably because of the boldfacing of the terms (if they are - at least they look a tad darker to me). Cheers, Paul Vinkenoog |
From: Norman D. <No...@du...> - 2020-05-30 08:56:01
|
I prefer the definition list. Cheers, Norm. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. |
From: Mark R. <ma...@la...> - 2020-05-29 17:10:44
|
I'm currently converting the Firebird Language Reference, and I was wondering if there is a preference in the rendering of parameter lists as used for function arguments and for syntax elements (in the current language reference, a table is used). I would like to have input on what style to apply I have prepared three example: 1. full width table 2. autowidth table (which seems to have width issues in PDF) 3. definition list Example 3 has my preference. See HTML: https://www.lawinegevaar.nl/fbdocs/html/en/asciidoc-migration/example.html PDF: https://www.lawinegevaar.nl/fbdocs/pdf/en/asciidoc-migration/example.pdf Equivalent in current language reference HTML: https://firebirdsql.org/file/documentation/reference_manuals/fblangref25-en/html/fblangref25-functions-scalarfuncs.html#fblangref25-functions-scalarfuncs-position PDF: https://firebirdsql.org/file/documentation/reference_manuals/fblangref25-en/Firebird_Language_Reference_25EN.pdf#%5B%7B%22num%22%3A2268%2C%22gen%22%3A0%7D%2C%7B%22name%22%3A%22XYZ%22%7D%2C54%2C371.209%2Cnull%5D For comparison, similar usage in the PostgreSQL documentation: https://www.postgresql.org/docs/12/sql-insert.html#id-1.9.3.152.6 Mark -- Mark Rotteveel |
From: Mark R. <ma...@la...> - 2020-05-29 16:52:31
|
On 27-05-2020 10:57, Köditz, Martin wrote: > I converted my first doc to asciiDoc: fbcache-de. I think everything is > fine. I already uploaded the PDF and the HTML output. > > Please feel free to give me some feedback. > > https://firebirdsql.org/file/documentation/html/de/firebirddocs/fbcache/firebird-fbcache-de.html > > https://firebirdsql.org/file/documentation/pdf/de/firebirddocs/fbcache/firebird-fbcache-de.pdf I hadn't noticed it before, but the names of these files don't match the standard output of the build. The intent is for it to be possible to upload the build output without having to manually rename files. So to produce the right output, the German AsciiDoc file should match the intended output filename (for the names above, `firebird-fbcache-de.adoc`). We may want to consider tweaking the filenames further (eg to `firebird-cache` for English and `firebird-cache-de` for German), this avoids the repetition of `firebird` and its abbreviation `fb`. See also the suggested naming conventions at https://firebirdsql.org/file/documentation/html/en/firebirddocs/docwritehowto/firebird-docwriting-guide.html#docwritehowto-asciidoc-file-naming-convention Mark -- Mark Rotteveel |
From: Mark R. <ma...@la...> - 2020-05-28 15:25:00
|
On 28-05-2020 12:01, Köditz, Martin wrote: > You're right. The CMS is back again. So I updated the German and English fbcache docs. Please have a look. Looks good to me. Mark -- Mark Rotteveel |
From: Mark R. <ma...@la...> - 2020-05-28 11:27:22
|
On 2020-05-28 12:01, Köditz wrote: >> On 2020-05-28 10:35, Köditz wrote: >>>>> Hi Mark, >>>>> >>>>> thank you for the feedback. I did the conversion with help of >>>>> Pandoc. >>>> >>>> Pandoc is not my tool of choice for the conversion. I have selected >>>> Docbookrx and implemented a number of customizations for it. For the >>>> sake of consistency of output, I think it is better >that a single >>>> method of conversion is used. >>>> >>>>> I will correct it. Now I know what to look for. >>>> >>>> Thanks. >>>> >>>> Mark >>> >>> Well, I tried to use Docbookrx, but got some errors. I will try it >>> again later. >> >> Did you use the one from the firebird-modifications branch of >> https://github.com/mrotteveel/docbookrx ? > > Yes, I used the modified one. I have to find out what the problem is. I know it doesn't run directly on Windows (or at least, I believe I had some issue with Ruby, and I switched to my Ubuntu WSL shell immediately). Mark |
From: Mark R. <ma...@la...> - 2020-05-28 11:25:39
|
On 2020-05-28 12:37, marius adrian popa wrote: > Nice VSCode extension > https://marketplace.visualstudio.com/items?itemName=joaompinto.asciidoctor-vscode Thanks. That plugin is already listed in https://firebirdsql.org/file/documentation/html/en/firebirddocs/docwritehowto/firebird-docwriting-guide.html#docwritehowto-asciidoc-tools Mark |