Fix the doc build process for the 1.x line about mybatisnet HOT 7 CLOSED

I just tried generating the tutorial's doc using a docbook 5 DTD. The only 
required change was to adjust the header of docs/tutorial/src/en/index.xml (the 
DTD version is part of the XML namespace) and also the DTD changed name 
(docbook.dtd instead of docbookx.dtd).

This did not fix the PDF formating problems.

However, if we only need to change the header of the three index.xml files, I 
would be tempted to suggest we consider moving to docbook 5, which by the way 
still seems to be in beta phase.

Docbook 5 DTD also works well for DataAccessGuide and DataMapperGuide.

I'm testing all this on a local copy, I do not intend to commit these changes 
until I get feedback from others, and until we fix all the urgent issues with 
the doc build process.

In trying to fix the FOP related problems (PDF version of the doc), I looked at 
the Hibernate docbook source files (our fopdf.xsl files were oringinnally 
imported from the hibernate project, so the headers say).

They seem to still be using docbook 4.5. I suppose there might be good reasons 
for that. Food for thought in our decision making regarding upgrading our 
source to a more recent version of docbook than our current 4.1.2.

Here is my current list of issues with the production of the PDF format of the 
doc:

- Cover page missing most of its information (authors, date, version number, 
...).
- Leaders in TOC not adequate,
- Some images are way too wide, I don't yet know how to control this from the 
stylesheets, or even if it's possible.
- When code samples are too long, the line doesn't wrap automatically and the 
rightmost portion is lost.

If someone else manages to build the PDF doc and notices other issues, please 
add them here.

As far as I know, the CHM output is as good as it can get, I haven't noticed 
any issues, but I did not read the CHM docs thoroughly, just skimmed them.

Revision 28 fixes the overblown images in PDF output problem. This required 
changing both the docbook XML source files AND the stylesheets for HTML.

I also proposed a temporary path to the cover page and TOC problems, by 
removing the custom first page and custom TOC in the PDF stylesheet 
(tutorial/styles/fopdf.xsl). If this is acceptable, I will mimic this solution 
in DataAccessGuide and DataMapperGuide PDF stylesheets until I can figure out 
what the problem is with FOP and custom first pages.

The only remaining issue would be the long lines in code samples which are 
clipped.

Revision 29 fixes the overrunning lines in code samples.

Closing this issue, will create a new one with the remaining PDF problem 
(custom first page).