firebird-docs — chat stuff about documentation

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Mark R. <ma...@la...>]

On 16-10-2017 22:58, Helen Borrie wrote:
> I guess I have to say (to quote my ex-Navy husband) "that's life in a
> blue suit."  My preference would have been to convert to SVN and leave
> the repository on Sourceforge - don't fix what aint broke.  But Github
> seems to dominate our (project) lives these days.
> 
> Currently, with the CVS and SVN clients I use - necessarily on
> Windows, since our doc app is Windows-based - I can commit, check out,
> etc. from a right click on the /manual/ subdir, or any subdir beneath
> it.  Given that I'm committing to multiple projects, this is a
> blessing that I will miss badly.

You can use a subversion client if you want: GitHub provides a 
compatibility layer that will make a git repository accessible as if it 
is a subversion repository.

> After all these months with the core project on GitHub, I have yet to
> succeed in downloading the repository AT ALL to access the readme
> files in the core tree for use in the release notes.  I have to rely
> on Dmitry sending me a link, from which I can view a file and
> copy/paste it into my local resource directory for that version.

That sounds problematic. Could you send me a private email with the 
problems you run into?

> As for code control, I currently keep two copies of the /manual/
> branch:  one for working on and the other which I sync with the
> working one before committing.  I have no idea how I will manage with
> the Github thing.  Any docs I have read so far (and I have not tried
> in recent months) assumes that one is working on the entire source
> code tree.  I do NOT want to keep a current copy of the entire tree.
> To consult core source code, it is simple for me to find what I want
> in the repository and copy/paste it, since I never commit changes to
> that code.

You will not need to checkout the Firebird sources to work with the 
documentation: they will be separate, individual, repositories, instead 
of one big repository with 'modules'.

And as to working like you currently do: you could still do it that way, 
but using git to its fullest might make things easier after the initial 
learning curve.

In git you can make local branches, commit changes to that local branch, 
and you can easily switch between the master branch and that local 
branch. Once you are happy with that, you can merge that local branch 
back to master with the commits you made on the local branch and 'push' 
that to the repository on GitHub. You could 'squash' the changes in the 
local branch to a single commit on master (but that is a bit more 
'advanced' git).

On the other hand, for Jaybird I use separate local copies for Jaybird 4 
(master branch), Jaybird 3 (Branch_3_0) and Jaybird 2.2 (Branch_2_2), 
because that is simpler with uncommitted changes in progress.

> I guess I just have to work something out.  This is about the worst
> week Mark could have picked, from my POV, as I'm already burning the
> midnight oil on other project infrastructure problems and TRYING (in
> conjunction with Denis Simonov) to sort out the Ringlish translation
> of the FB Developer's Guide.

The fact that I did the test conversion this weekend does not put a rush 
on you. We have until the 30th of November before we lose write access 
to the CVS repository, moving before that time would probably be better, 
but we can still move after that time if that is better for your schedule.

However it would be great if there are more eyes on the conversion than 
just me. For example with the test conversion of OdbcJdbc, Alexander 
already found a conversion issue that I hadn't detected because he used 
the GitHub subversion support, and the git client automatically 'fixed' 
the issue.

If necessary I can also grant write access to the test repository.

> Note that Denis will have to be "in" on any changes as, this time
> around, he is planning to convert the Word text to DocBook himself and
> (presumably) commit the DocBook source once he has built it
> successfully.  Amongst other things, he has quite a number of
> screenshots there which, of course, are binary files.  I have no idea
> how GH deals with image files but I guess we are going to find out
> soon enough.  I can't walk him through it myself, since I am clueless
> about how it's going to work.

Git by default uses a few heuristics to determine if a file is binary or 
not, and you can override that by explicitly setting the behavior for a 
file pattern in the .gitattributes file, like I did for the test 
conversion (see 
https://github.com/mrotteveel/test-firebird-documentation-3/blob/master/.gitattributes 
). I already added the most likely image types to that file. Adding new 
types is just a matter of editing that file.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] Test repository CVS to git migration

[Köditz, M. <Mar...@it...>]

Hi,

seems I got unsubscribed from the list. So I had some trouble to be part of the discussion. I will try it again.

Do we have any problems with special characters? Please have a look at https://github.com/mrotteveel/test-firebird-documentation-3/tree/master/src/docs/refdocs-de/langref/fblangref25. Here you can see some hieroglyphs in the commit messages.

Regards,
Martin

Re: [Firebird-docs] Test repository CVS to git migration

[Helen B. <he...@ii...>]

Hello Mark,

Monday, October 16, 2017, 3:41:43 AM, you wrote:

> I have made a few more test runs, the end result is in 
> https://github.com/mrotteveel/test-firebird-documentation-3

> I think this would be the final run.

> Difference against yesterday:

> - Removed the d_jencks branch
> - Added a .gitignore to ignore build files
> - Added a .gitattributes with sane defaults for the project

> As to the problem with line-endings, yesterday I looked cross-eyed, and
> the problem with the four files were actual in reverse, they had LF in
> CVS and CRLF in git. I have managed to normalize these files so future
> updates to these files should not cause a large-scale whitespace update.

I downloaded the zip from your repository and looked at a few of the
.docbook files from the v.3.0.2 release notes with the editor I use
for creating and updating them.  They look OK to me.
The ReadMe file in the base directory has messed-up line-endings,
though.  I guess we'll need to test what happens when one of the
(currently good) source files gets updated.  We definitely cannot do
with extraneous white space in those files.

Using the Github Desktop, I couldn't access the local copy of the
unpacked zipfile but I cloned a new repository off it, which created
the three git config files.  It didn't copy anything else, so I
file-copied all of the unpacked filesystem (except the git
configuration files) into it.  That sort of worked and it was able to
link back to your github repository and log me in from the local
config.
I'm sure that's not how it's done but at least I am comfortable with
the migrated file formats and filesystem structure, so far.  It looks
possible that I will be able to sync the working source files with the
git ones, much as I was doing with CVS and SVN.

Helen




-- 
Kind regards,
 Helen Borrie

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Helen B. <he...@ii...>]

Thursday, October 12, 2017, 12:59:11 AM, Paul V. wrote:

> Hi all,

> Three people - one of them a committer - have expressed their preference
> for moving to GitHub.

> I have no problem with that, but I would also like to hear Helen's opinion,
> as she is the heaviest user of the manual module.

I guess I have to say (to quote my ex-Navy husband) "that's life in a
blue suit."  My preference would have been to convert to SVN and leave
the repository on Sourceforge - don't fix what aint broke.  But Github
seems to dominate our (project) lives these days.

Currently, with the CVS and SVN clients I use - necessarily on
Windows, since our doc app is Windows-based - I can commit, check out,
etc. from a right click on the /manual/ subdir, or any subdir beneath
it.  Given that I'm committing to multiple projects, this is a
blessing that I will miss badly.

After all these months with the core project on GitHub, I have yet to
succeed in downloading the repository AT ALL to access the readme
files in the core tree for use in the release notes.  I have to rely
on Dmitry sending me a link, from which I can view a file and
copy/paste it into my local resource directory for that version.

As for code control, I currently keep two copies of the /manual/
branch:  one for working on and the other which I sync with the
working one before committing.  I have no idea how I will manage with
the Github thing.  Any docs I have read so far (and I have not tried
in recent months) assumes that one is working on the entire source
code tree.  I do NOT want to keep a current copy of the entire tree.
To consult core source code, it is simple for me to find what I want
in the repository and copy/paste it, since I never commit changes to
that code.

I guess I just have to work something out.  This is about the worst
week Mark could have picked, from my POV, as I'm already burning the
midnight oil on other project infrastructure problems and TRYING (in
conjunction with Denis Simonov) to sort out the Ringlish translation
of the FB Developer's Guide.

Note that Denis will have to be "in" on any changes as, this time
around, he is planning to convert the Word text to DocBook himself and
(presumably) commit the DocBook source once he has built it
successfully.  Amongst other things, he has quite a number of
screenshots there which, of course, are binary files.  I have no idea
how GH deals with image files but I guess we are going to find out
soon enough.  I can't walk him through it myself, since I am clueless
about how it's going to work.

Helen

Re: [Firebird-docs] Test repository CVS to git migration

[Paul V. <pa...@vi...>]

Hi Mark,

> I have made a few more test runs, the end result is in 
> https://github.com/mrotteveel/test-firebird-documentation-3
> 
> I think this would be the final run.
> 
> Difference against yesterday:
> 
> - Removed the d_jencks branch
> - Added a .gitignore to ignore build files
> - Added a .gitattributes with sane defaults for the project
> 
> As to the problem with line-endings, yesterday I looked cross-eyed, and 
> the problem with the four files were actual in reverse, they had LF in 
> CVS and CRLF in git. I have managed to normalize these files so future 
> updates to these files should not cause a large-scale whitespace update.

Thanks for all your efforts! I'll have a look at it today (Monday) or
at the latest tomorrow.


Cheers,
Paul

[Firebird-docs] Test repository CVS to git migration

[Mark R. <ma...@la...>]

I have made a few more test runs, the end result is in 
https://github.com/mrotteveel/test-firebird-documentation-3

I think this would be the final run.

Difference against yesterday:

- Removed the d_jencks branch
- Added a .gitignore to ignore build files
- Added a .gitattributes with sane defaults for the project

As to the problem with line-endings, yesterday I looked cross-eyed, and 
the problem with the four files were actual in reverse, they had LF in 
CVS and CRLF in git. I have managed to normalize these files so future 
updates to these files should not cause a large-scale whitespace update.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Mark R. <ma...@la...>]

I have made an initial conversion to git, the results are on 
https://github.com/mrotteveel/test-firebird-documentation (hosted on my 
account while doing testing)

There are some differences when comparing against a CVS checkout (with 
TortoiseCVS):

- A branch 'd_jencks' from near the start of the project has surfaced, 
I'll see if I can filter that one out or otherwise I'll delete it 
manually (IIRC this was a cross-module branch, I recall seeing it in 
Jaybird as well when I migrated from CVS to Subversion a few years ago)

- Tags previously not visible in CVS have shown up (not really important)

- Git has no keyword expansion, and in the current config of the 
conversion, things like $Id$ are collapsed (instead of - as an example - 
"$Id: formal.xsl,v 1.1 2007/04/15 16:33:16 paulvink Exp $"); I think 
I'll leave that as is, on master there is only a single occurrence (in 
src\docs\xsl\fo\formal.xsl)

- Four files have a difference in line-endings (LF in git vs CRLF in 
CVS) while other files do have the same line-endings. It is normal that 
git stores line-endings in text files as LF, but my git config on 
Windows should normally change these back to CRLF on checkout. I'll see 
if I can tweak that, but attempts to fix similar problems in the 
OdbcJdbc module conversion where unsuccessful.

Note that this difference in line-endings shouldn't be a real problem, 
but might cause a lot of irrelevant whitespace changes when committing 
changes to these files.

I'll be performing more test conversion tomorrow (in numbered variants 
of this repository).

If you have time to test and compare, I'd be happy to get your feedback.

Mark

-- 
Mark Rotteveel

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Paul V. <pa...@vi...>]

Mark Rotteveel wrote:

>> Three people - one of them a committer - have expressed their preference
>> for moving to GitHub.
>
> Two committers, although it has been a while (3 years AFAICT), I have 
> committed to the manual module.

I know, I counted back to January 2016. Earlier committers are has-beens ;-)


Cheers,
Paul

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Mark R. <ma...@la...>]

On 11-10-2017 14:02, Paul Vinkenoog wrote:
> Mark Rotteveel wrote:
> 
>>> I am willing to spend some time to test and perform the conversion of
>>> the manual module to Git (and GitHub), so the commit history is
>>> preserved. If the consensus is for subversion, I can do that as well.
>>
>> I'll be doing a test conversion of the ODBC repository this weekend. If
>> it is quick to do, I'll also do a test conversion of the docs repository.
> 
> Thanks, that would be most interesting. I'm especially curious about
> the preservation of the history, including branches (not that we have
> many of those).

That should work fine. I previously did a conversion of the client-java 
module from CVS to Subversion (and then later to git), with preservation 
of all history.

If direct conversion runs into problem, I'll first convert to 
subversion, and then use the GitHub import tool like I did for Jaybird ;)

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Mark R. <ma...@la...>]

On 11-10-2017 13:59, Paul Vinkenoog wrote:
> Hi all,
> 
> Three people - one of them a committer - have expressed their preference
> for moving to GitHub.

Two committers, although it has been a while (3 years AFAICT), I have 
committed to the manual module.

> I have no problem with that, but I would also like to hear Helen's opinion,
> as she is the heaviest user of the manual module.

Sure, I will just do a test conversion for now to work out the kinks (if 
any), and document the necessary steps.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Paul V. <pa...@vi...>]

Mark Rotteveel wrote:

>> I am willing to spend some time to test and perform the conversion of
>> the manual module to Git (and GitHub), so the commit history is
>> preserved. If the consensus is for subversion, I can do that as well.
>
> I'll be doing a test conversion of the ODBC repository this weekend. If
> it is quick to do, I'll also do a test conversion of the docs repository.

Thanks, that would be most interesting. I'm especially curious about
the preservation of the history, including branches (not that we have
many of those).


Cheers,
Paul Vinkenoog

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Paul V. <pa...@vi...>]

Hi all,

Three people - one of them a committer - have expressed their preference
for moving to GitHub.

I have no problem with that, but I would also like to hear Helen's opinion,
as she is the heaviest user of the manual module.

Cheers,
Paul Vinkenoog

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Mark R. <ma...@la...>]

On 9-10-2017 09:13, Mark Rotteveel wrote:
> I think it would be preferable if the documentation project would move 
> to GitHub (https://github.com/FirebirdSQL), where the main project resides.
> 
> If complexity of git is a problem: GitHub also allows subversion access 
> to a git repository: 
> https://help.github.com/articles/support-for-subversion-clients/
> 
> I am willing to spend some time to test and perform the conversion of 
> the manual module to Git (and GitHub), so the commit history is 
> preserved. If the consensus is for subversion, I can do that as well.

I'll be doing a test conversion of the ODBC repository this weekend. If 
it is quick to do, I'll also do a test conversion of the docs repository.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Norman D. <No...@du...>]

I agree with the git option too.

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

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Mark R. <ma...@la...>]

On 8-10-2017 21:03, Paul Vinkenoog wrote:
> To all committers:
> 
> SourceForge have announced that they plan to terminate CVS read-write
> support on November 30.
> 
> The CVS manual module will still be available after that for checkouts
> and updates, but not for commits.
> 
> That means that we have around 7 weeks to implement another solution.
> 
> Options are:
> 
> - convert the module to SVN on SourceForge;
> - convert the module to Git on SourceForge;
> - convert the module to <whatever> and host it somewhere else.
> 
> Given the nature, and low traffic, of our module, I'm inclined to
> go for in-place conversion to SVN. But the other options are also
> feasible.
> 
> Any opinions?

I think it would be preferable if the documentation project would move 
to GitHub (https://github.com/FirebirdSQL), where the main project resides.

If complexity of git is a problem: GitHub also allows subversion access 
to a git repository: 
https://help.github.com/articles/support-for-subversion-clients/

I am willing to spend some time to test and perform the conversion of 
the manual module to Git (and GitHub), so the commit history is 
preserved. If the consensus is for subversion, I can do that as well.

Just a heads up: This is also being discussed in firebird-admin.

Mark

-- 
Mark Rotteveel

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Alexey K. <ak...@ib...>]

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

Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Jiří Č. <ji...@ci...>]

Convert to Git and put it under FirebirdSQL organization on GitHub for
extra visibility. It might even help with contributions.

-- 
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/

[Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th

[Paul V. <pa...@vi...>]

To all committers:

SourceForge have announced that they plan to terminate CVS read-write
support on November 30.

The CVS manual module will still be available after that for checkouts
and updates, but not for commits.

That means that we have around 7 weeks to implement another solution.

Options are:

- convert the module to SVN on SourceForge;
- convert the module to Git on SourceForge;
- convert the module to <whatever> and host it somewhere else.

Given the nature, and low traffic, of our module, I'm inclined to
go for in-place conversion to SVN. But the other options are also
feasible.

Any opinions?


Cheers,
Paul Vinkenoog

Re: [Firebird-docs] What chapter to translate next?

[Helen B. <he...@ii...>]

Hello Martin,

Saturday, May 13, 2017, 12:37:02 AM, you wrote:

> Hi,

>  

> I’ve committed the fblangref25-commons-de chapter to the manual
> module. Which of the following is ready for translation?

>  

> -          DDL

> -          DML

> -          PSQL

> -          Security

> -          Transacs

>

Consider all of them ready.  There has been no further reviewing since
Aage Johansen died last year so let's assume that what we have is
perfect. ;-)

When I get time, I'll do the final editing on the source to remove the
comments about review status.  For now, assume they are already gone.

Helen

[Firebird-docs] What chapter to translate next?

[Köditz, M. <Mar...@it...>]

Hi,

I've committed the fblangref25-commons-de chapter to the manual module. Which of the following is ready for translation?


-          DDL

-          DML

-          PSQL

-          Security

-          Transacs

Regards,
Martin

Re: [Firebird-docs] Error while building PDF

[Köditz, M. <Mar...@it...>]

OK, I will check this later.

Regards,
Martin

Re: [Firebird-docs] Error while building PDF

[Norman D. <No...@du...>]

Sorry, auto correct trashed my reply!

OpenJDK was no use either.

Cheers,
Norm.

On 12 May 2017 09:40:09 BST, Norman Dunbar <No...@du...> wrote:
>Morning Martin,
>
>I think that the IcedTea java environment is not suitable for fop to
>create pdfs. I've got a recollection that this has bugged me in the
>past. I'm pretty sure you need Sun/Oracle jave.
>
>Opened was no use either, at least according to a post of mine from
>2011 (Update of Build System thread.)
>
>HTH
>
>Cheers,
>Norm.
>
>
>-- 
>Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [Firebird-docs] Error while building PDF

[Norman D. <No...@du...>]

Morning Martin,

I think that the IcedTea java environment is not suitable for fop to create pdfs. I've got a recollection that this has bugged me in the past. I'm pretty sure you need Sun/Oracle jave.

Opened was no use either, at least according to a post of mine from 2011 (Update of Build System thread.)

HTH

Cheers,
Norm.


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[Firebird-docs] Error while building PDF

[Köditz, M. <Mar...@it...>]

Hi,

I've just finished the refdocs commons section and wanted to cross check it via PDF, but I got following error. Can I see what is the responsible element?
HTML output is no problem.

Kind regards
Martin


sh build.sh pdf -Dsfx=de
openjdk version "1.8.0_91"
OpenJDK Runtime Environment (IcedTea 3.0.1) (suse-12.1-x86_64)
OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)

Unable to locate tools.jar. Expected to find it in /usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/lib/tools.jar
Buildfile: build.xml

init:
     [echo] Apache Ant version 1.6.5 compiled on June 2 2005

prepare:

getrootarg:

getfontargs:

fo:
     [echo] Building Formatting Objects file. Please wait...
   [delete] Deleting: /srv/www/htdocs/firebird/manual/inter/fo/de/firebirddocs-de.fo
     [java] Making portrait pages on A4 paper (210mmx297mm)
     [java] Error: no ID for constraint linkend: fblangref25-license.
     [java] Error: no ID for constraint linkend: fblangref25-dml-execblock-de.
     [java] Error: no ID for constraint linkend: fblangref25-structure-dialects.
     [java] Error: no ID for constraint linkend: fblangref25-commons-predcontaining.
     [java] Error: no ID for constraint linkend: fblangref25-ddl-domn-alter-de.
     [java] Error: no ID for constraint linkend: fblangref25-commons-introducer-syntax.
     [java] Error: no ID for constraint linkend: fblangref25-ddl-sequence-de.
     [java] Error: no ID for constraint linkend: fblangref25-functions-scalarfuncs-gen_id-de.
     [java] Error: no ID for constraint linkend: fblangref25-functions-conditional-de.
     [java] Error: no ID for constraint linkend: fblangref25-functions-scalarfuncs-decode-de.
     [java] Error: no ID for constraint linkend: fblangref25-datatypes-custom.
     [java] Error: no ID for constraint linkend: fblangref25-appx01-supp-rdb_validblr.
     [java] Error: no ID for constraint linkend: fblangref25-appx01-supp-rdb_validblr.
     [java] Error: no ID for constraint linkend: fblangref25-appx01-supp-rdb_validblr.
     [java] Error: no ID for constraint linkend: fblangref25-commons-conditional-nxtvlufor.
     [java] Error: no ID for constraint linkend: fblangref25-commons-conditional-nxtvlufor.
     [java] Error: no ID for constraint linkend: fblangref25-commons-conditional-nxtvlufor.
     [java] Error: no ID for constraint linkend: fblangref25-structure-identifiers.
     [java] Error: no ID for constraint linkend: fblangref-appx04-exceptions.
     [java] Error: no ID for constraint linkend: fblangref25-commons-subqueries.
     [java] Error: no ID for constraint linkend: fblangref25-commons-isnotdistinct.
     [java] Error: no ID for constraint linkend: fblangref25-datatypes.
     [java] Error: no ID for constraint linkend: fblangref25-datatypes-custom.
     [java] Error: no ID for constraint linkend: fblangref25-appx02-errorcodes.
     [java] Error: no ID for constraint linkend: fblangref25-appx02-sqlstates.
     [java] Error: no ID for constraint linkend: fblangref25-appx02-sqlcodes.
     [java] Error: no ID for constraint linkend: fblangref-appx04-exceptions.
     [java] Error: no ID for constraint linkend: fblangref25-appx02-tbl-sqlstates.
     [java] Error: no ID for constraint linkend: fblangref25-datatypes-convert-shortcasts.
     [java] Error: no ID for constraint linkend: fblangref25-appx02-tbl-sqlstates.
     [java] Error: no ID for constraint linkend: fblangref25-datatypes-convert-shortcasts.
     [java] Error: no ID for constraint linkend: fblangref25-datatypes-convert-shortcasts.
     [java] Error: no ID for constraint linkend: fblangref25-datatypes-convert-shortcasts.
     [java] Error: no ID for constraint linkend: fblangref25-datatypes-datetimeops.
     [java] Error: no ID for constraint linkend: fblangref25-datatypes-datetimeops.
     [java] Error: no ID for constraint linkend: fblangref25-datatypes-datetime.
     [java] Error: no ID for constraint linkend: fblangref25-appx01-supp-rdb_validblr.
     [java] Error: no ID for constraint linkend: fblangref25-appx01-supp-rdb_validblr.
     [java] Error: no ID for constraint linkend: fblangref25-commons-conditional-nxtvlufor.
     [java] Error: no ID for constraint linkend: fblangref25-commons-conditional-case-simple.
     [java] Error: no ID for constraint linkend: fblangref25-commons-conditional-case-simple.
     [java] Error: no ID for constraint linkend: fblangref25-structure-identifiers.
     [java] Error: no ID for constraint linkend: fblangref25-appx02-tbl-errcodes01-de.
     [java] Error: no ID for constraint linkend: fblangref25-appx02-tbl-errcodes04-de.

copy-images:

copy-img-files:
     [copy] Copying 1 file to /srv/www/htdocs/firebird/manual/inter/fo/de/images

copy-img-files:
     [copy] Copying 9 files to /srv/www/htdocs/firebird/manual/inter/fo/de/images

copy-img-files:

fo2pdf:
     [echo] Building PDF from Formatting Objects. Please wait...
      [fop] Mai 12, 2017 9:14:06 AM org.apache.fop.apps.FopFactory configure
      [fop] INFORMATION: Initializing FopFactory Configuration
      [fop] /srv/www/htdocs/firebird/manual/inter/fo/de/firebirddocs-de.fo -> /srv/www/htdocs/firebird/manual/dist/pdf/de/firebirddocs-de.pdf
      [fop] Mai 12, 2017 9:14:07 AM org.apache.fop.apps.FOUserAgent setTargetResolution
      [fop] INFORMATION: target-resolution set to: 72.0dpi (px2mm=0.35277778)
      [fop] Mai 12, 2017 9:14:09 AM org.apache.fop.fo.flow.TableColumn bind
      [fop] WARNUNG: table-layout="fixed" and column-width unspecified => falling back to proportional-column-width(1)
      [fop] Mai 12, 2017 9:14:09 AM org.apache.fop.fo.flow.TableColumn bind
      [fop] WARNUNG: table-layout="fixed" and column-width unspecified => falling back to proportional-column-width(1)
      [fop] Mai 12, 2017 9:14:09 AM org.apache.fop.fo.flow.TableColumn bind
      [fop] WARNUNG: table-layout="fixed" and column-width unspecified => falling back to proportional-column-width(1)

BUILD FAILED
/srv/www/htdocs/firebird/manual/src/build/build.xml:738: org.apache.fop.apps.FOPException: java.lang.NullPointerException
javax.xml.transform.TransformerException: java.lang.NullPointerException

Total time: 2 minutes 45 seconds

Re: [Firebird-docs] Doc funding - samples

[Jiří Č. <ji...@ci...>]

Information passed.

-- 
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/