Re: [Firebird-docs] Writing Guide

[Darcy O'N. <ds...@sk...>]

>
>
>I see that some elements are not rendered the right way. But it's late
>now, I'll have a good look at it over the weekend and then followup
>here. I hope others will respond too because I think this is very
>promising. It makes all the difference if we can present decent PDF
>docs.
>  
>
Ya, I'm still working on the XML mappings but this is what was rendered 
after only an hour or two. Given a little more time I should be able to 
perfect it!

My basic goal was to produce some documents that 'professional' 
corporate types would get the confidence to use the product. MySQL is 
heading in that direction and frankly Firebird is much better than MySQL 
but this project doesn't have the momentum right now. Marketing can fix 
that, and good quality docs can give a powerful first impression to new 
users.

>One drawback is that we can't do this *within* the project at
>SourceForge, because we are certainly not going to buy Ventura and
>it wouldn't run on SF anyway. So we depend on you (or others) to
>produce them. That's not ideal, but still a heck of a lot better
>than ugly and/or broken PDF docs.
>
Ya, it's not perfect in the 'open' sense but I'm willing to contribute 
to this project for a good long time and based on the work I've done so 
far it's pretty much automated for me right now. It depends on the 
goals, I've always been of the mind set that we should use the 'right 
tool for the right job' and Ventura fits the bill.

That's an added benefit of Ventura, once we have a good level of 
documentation in place we can actually publish it to paper, and possible 
sell it via the Firebird site to help support the project. Obviously not 
yet, but this brings us closer.

Better marketing and image will hopefully increase support for this 
project and that can only be a good thing.

Darcy O'Neil