firebird-docs — chat stuff about documentation

Re: [Firebird-docs] Widowed section headers in PDF

[Lester C. <le...@ls...>]

Paul Vinkenoog wrote:

> The better solution is therefore to insert the pagebreaks directly
> into the .fo file. Open it in a text or XML editor, use the search
> function to find the right spot, and change e.g.:
> 
>   <fo:block font-size="12pt" ...>Using a GUI client</fo:block>
> 
> to
> 
>   <fo:block break-before="page" font-size="12pt" ...>Using a GUI client</fo:block>
> 
> Of course it's still a hack, but now it takes less time and we keep
> the sources clean.

That will do me for the time being ;)
As for this not being part of DocBook DTD, on one hand I can understand 
the reasoning, BUT a header should never be the last thing on a page. If 
that rule was added, things would probably come out much better?

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

Re: [Firebird-docs] Widowed section headers in PDF

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

Hi Lester,

>> So the only option (at least as long as we use Apache FOP) seems to
>> be: wrap every header in a single-cell table together with the text
>> that follows it. This requires editing our transformation
>> stylesheets; don't know how complicated it will be, but I'll have a
>> look at it (somewhere in the next weeks).

Hm, this approach has its drawbacks: it could lead to lots uf
*unwanted* pagebreaks, namely if header + all of the following text
don't fit on the remainder of the page. But I've thought of something
else (see next post).

> Seems to be a bit of a major bobo ;)
> It is the only thing that two of my customers both picked up and
> commented on. Just a simple 'page break' would solve the problem,
> and hopefully something that will come. Just need to find just where
> to post a bug report :)

It's not a bug - it's an unimplemented feature ;-)
The people at Apache FOP are aware of this and full keep-with-next
support will be implemented... one day.

See the Standard Compliance page at
  http://xml.apache.org/fop/compliance.html
more specifically:
  http://xml.apache.org/fop/compliance.html#fo-property-keepsbreaks

> I'll pull the file set together to a single 'book' with 'chapters'
> for each OS and probably a separate book for all the Eclipse
> stuff. That does not need to be part of the basic stuff, but it will
> be nice to have it all documented for my own reference.

Yes, the Eclipse stuff - but also the logo stuff - shouldn't be in
there. But the Eclipse info is very useful; could you make it an
<article> so we can add it to the "Documentation for Firebird
docwriters" book? That would be its rightful place.

As for the logo stuff - is it ready to be published yet? I thought
there needed to be some official OK first (from admin group and/or
FFmembers).


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] Widowed section headers in PDF

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

Hi Philippe,

> on my linux machine, I use db2pdf for my technical doc, and I have
> page-break so it might be possible with FOP too ??

Yes, using page-break as such is no problem. The problem is: where to
insert it? Because you don't know where it's needed until the PDF is
produced and you find widowed headers. And you *only* want to place it
where it's needed or you'll get unwanted pagebreaks.

So (until FOP implements keep-with-next, or until we find a better
alternative) I guess the best solution is:

  repeat
    build the PDF;
    find first occurrence of a widowed header;
    if found, insert a pagebreak before that header;
  until no widowed headers remain.

This is not exactly elegant, but given the rate at which we publish
PDFs it's certainly feasible. After all, we only have to run this
cycle on the docs we publish; not on all the versions we build
in-between for ourselves or for comments by others.

Next question: how to insert the pagebreak? We don't have support for
a <?dbfo break...> instruction so we'd have to implement that first;
only then could we include such a PI in our docs.

This has two drawbacks:
- spending time to implement something that is essentially a hack;
- the pagebreaks will be in our XML sources; if the document is
  edited, chances are that some of them will have to be removed, but
  this could easily be forgotten. Even if not, I think it pollutes
  the source.

The better solution is therefore to insert the pagebreaks directly
into the .fo file. Open it in a text or XML editor, use the search
function to find the right spot, and change e.g.:

  <fo:block font-size="12pt" ...>Using a GUI client</fo:block>

to

  <fo:block break-before="page" font-size="12pt" ...>Using a GUI client</fo:block>

Of course it's still a hack, but now it takes less time and we keep
the sources clean.

So you run the cycle like this:

  "build pdf";
  repeat
    find first widowed header in PDF file;
    find that spot in the .fo and add break-before attribute;
    "build fo2pdf";
  until no more widows found.

BTW, the .fo is in manual/build/docs. As soon as you issue a "build
fo" or "build pdf", your manually inserted pagebreaks will be lost!

If someone has a PDF ready to publish but finds this too complicated,
I don't mind doing it myself.


> As far as the rationale for the DTD not providing an element to
> force pagebreaks in rendered output, it's just consistent with the
> fact that the DTD by design provides markup only for modeling
> structure and content, not presentation.

That's entirely correct; pagebreaks don't belong in the DocBook DTD.


Greetings,
Paul Vinkenoog

[Firebird-docs] Widowed section headers in PDF

[Philippe M. <mak...@a6...>]

>> So the only option (at least as long as we use Apache FOP) seems to
>> be: wrap every header in a single-cell table together with the text
>> that follows it. This requires editing our transformation stylesheets;
>> don't know how complicated it will be, but I'll have a look at it
>> (somewhere in the next weeks).
>>

It's seem that it is possible,
on my linux machine, I use db2pdf for my technical doc, and I have page-break
so it might be possible with FOP too ??

Perhaps some help with :

<http://cscisl.dce.harvard.edu/lecture_notes/20040722/links.html>
And this :

How to insert a pagebreak into docbook output

The answer's been that you need to use a processing instruction instead of an
element (so also need to write support in your XSLT customization layer for
generating a pagebreak in the FO output for each instance of that PI).

The suggestion from Paul Reavis on the debian-sgml list was to use <?dbfo
break-before="page"?>. Something like that would work -- there's existing
(undocumented) support in the stylesheets (dbfo-attribute template in fo/pi.xsl
and dbhtml-attribute template in html/pi.xsl) for processing PIs that start with
"dbfo" and "dbhtml" and extracting the pseudo- attributes/values from them.

As far as the rationale for the DTD not providing an element to force pagebreaks
in rendered output, it's just consistent with the fact that the DTD by design
provides markup only for modeling structure and content, not presentation. If a
pagebreak is strictly a processing thing and has no significance to structure or
content -- just something that's specific to print delivery, not to HTML or
online help, etc. -- then not really appropriate to have an element for it.

-- Philippe Makowski

Re: [Firebird-docs] Widowed section headers in PDF

[Lester C. <le...@ls...>]

Paul Vinkenoog wrote:

> So the only option (at least as long as we use Apache FOP) seems to
> be: wrap every header in a single-cell table together with the text
> that follows it. This requires editing our transformation stylesheets;
> don't know how complicated it will be, but I'll have a look at it
> (somewhere in the next weeks).

Seems to be a bit of a major bobo ;)
It is the only thing that two of my customers both picked up and 
commented on. Just a simple 'page break' would solve the problem, and 
hopefully something that will come. Just need to find just where to post 
a bug report :)

I'll pull the file set together to a single 'book' with 'chapters' for 
each OS and probably a separate book for all the Eclipse stuff. That 
does not need to be part of the basic stuff, but it will be nice to have 
it all documented for my own reference.

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

[Firebird-docs] Widowed section headers in PDF

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

[ took conversation here because subject concerns all docwriters ]

Hi Lester,

>> Is there any way to get DocBook to start a new page in the printed
>> versions. The heading on the bottom of a page, and text on the next
>> page looks very mickey mouse.

> That's not DocBook, but a limitation of Apache FOP, which doesn't
> honour keep-with-next directives (except in tables). Yes, it's
> annoying. Maybe we can work around it by including a PDF
> postprocessor in the build process, but this will take a lot of time
> to investigate and test - which I don't have at the moment. But I'll
> see if I can hand-edit the PDF to get them right. Will get back to
> you on this.

Hmmm, no luck :-(

It turns out that once a PDF file is produced, the text-structural
information is lost. (Every bit of text only has an absolute position
on the page.) So you can do all kinds of things: deleting entire
pages, moving them around, changing the margins, adding text and
images, deleting text, etc. etc... but you can NOT repaginate in the
sense that you insert a hard page break before a widowed header to
reunite the header with the section text.

This goes for Adobe, but also for any postprocessors out there.

So the only option (at least as long as we use Apache FOP) seems to
be: wrap every header in a single-cell table together with the text
that follows it. This requires editing our transformation stylesheets;
don't know how complicated it will be, but I'll have a look at it
(somewhere in the next weeks).


Greetings,
Paul Vinkenoog

[Firebird-docs] Direbird DocBooks on Eclipse

[Lester C. <le...@ls...>]

Magic

Management of the CVS link via Eclipse is a doddle, but I was having 
problems with the build process - simply because I don't do java ;)

Couple of tweaks in build.xml and I have a working build process.

If anybody is interested the rough 'HowTo' guide is here
http://home.lsces.co.uk/Firebird/Eclipse_Firebird_Docs.html

Next problem is just which XML editor to load, but XMLBuddy is looking 
fine at the moment - Oxygen seems to add too much complication ;)
( Could not get XMen to work )

So NOW I can look at moving all these little 'HowTo' bits over :)

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

Re: [Firebird-docs] Re: Docs on the go

[A6-CMO P. M. <mak...@a6...>]

Le 13/08/2004 00:45, Nigel Weeks a écrit :
> What if, and this is just an idea, FireFly was modified so that it coul=
d
> produce the DocBook-based documentation, AND be multi-user, web-based..=
.
>=20
Yes, the FireFly have to produce docbook, it's the better way

--=20
Philippe Makowski

Firebird serveur SQL open-source en fran=E7ais
http://firebird-fr.eu.org

Ma cl=E9 PGP : http://makowski.net/pgpkey.html

RE: [Firebird-docs] Re: Docs on the go

[Nigel W. <nw...@ex...>]

> Back in January I liked the look of your Firefly pages! Too bad they
> couldn't stay online. But let's suppose you can host them somewhere
> else, then we're working on at least three parallel Firebird doc
> systems:
>
> - The DocBook-based documentation within the Firebird project;
> - Lester's Wiki;
> - Your Firefly pages.

What if, and this is just an idea, FireFly was modified so that it could
produce the DocBook-based documentation, AND be multi-user, web-based...

It would take work, but I think it might go really well.

>
> I'm not saying this is bad, but will we have enough input for all
> three to be viable? Anyway, let's all keep in touch via this list and
> avoid too much overlap, especially when it comes to big docs that take
> a lot of time to write and maintain.

Too right!, but if we can combine two of these, we're really cooking!
You'd like it if people would produce DocBook code, and people don't want to
learn DocBook.
So, a web-based system in the middle kind of makes sense...

Opinions? Ideas?

Nige.

Re: [Firebird-docs] Quick Start Guide: 1.0 and 1.5

[Lester C. <le...@ls...>]

Paul Vinkenoog wrote:

> As said in another email, I'm roughly 75% through updating the Quick
> Start Guide to include the Firebird 1.5 info. However, this leads to
> all kinds of nested forks of the type:
> 
>   If you use Firebird 1.0.x, then
>     - If you're on Win9x/Me, do this;
>     - On Win NT/2000/XP, do the other thing;
>   If you use Firebird 1.5.x, then
>     - On Win9x/Me, do the mambo;
>     - On Win NT/2000/XP, do the samba;
> 
> I think this makes the document way too complicated, *especially* for
> the new users who are its main target audience. So unless there are
> serious objections I'll make two QSGs: one for 1.0.x, the other for
> 1.5.x, and create separate branches for them in the CVS tree. For me
> this is hardly more work than what I'm doing now, and for both readers
> and future doc maintainers it's a lot more convenient.

Should have read further :)
That is the sort of thing I was trying to explain in the other post ;)
Add the Linux stuff to it, and versions of Linux
Bring in JDBC and PHP.
The CONTENT needs to be more directed, rather than trying to produce a 
one size fits all book. Which is what I was trying to get at with the 
demo 'Using Guide' :)

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

Re: [Firebird-docs] Quick Start Guide: 1.0 and 1.5

[Lester C. <le...@ls...>]

Paul Vinkenoog wrote:

> As said in another email, I'm roughly 75% through updating the Quick
> Start Guide to include the Firebird 1.5 info. However, this leads to
> all kinds of nested forks of the type:
> 
>   If you use Firebird 1.0.x, then
>     - If you're on Win9x/Me, do this;
>     - On Win NT/2000/XP, do the other thing;
>   If you use Firebird 1.5.x, then
>     - On Win9x/Me, do the mambo;
>     - On Win NT/2000/XP, do the samba;
> 
> I think this makes the document way too complicated, *especially* for
> the new users who are its main target audience. So unless there are
> serious objections I'll make two QSGs: one for 1.0.x, the other for
> 1.5.x, and create separate branches for them in the CVS tree. For me
> this is hardly more work than what I'm doing now, and for both readers
> and future doc maintainers it's a lot more convenient.

Should have read further :)
That is the sort of thing I was trying to explain in the other post ;)
Add the Linux stuff to it, and versions of Linux
Bring in JDBC and PHP.
The CONTENT needs to be more directed, rather than trying to produce a
one size fits all book. Which is what I was trying to get at with the
demo 'Using Guide' :)

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

Re: [Firebird-docs] Quick Start Guide: 1.0 and 1.5

[Phil S. <li...@sh...>]

Paul Vinkenoog wrote:

Hi,

> > Would new users be using 1.0.x?  The only reason I can think of
> > using 1.0.x over 1.5 is if you already have it in production, and
> > can't upgrade.
> 
> I guess new users would (and should) go for 1.5. But if I don't split
> the QSG, they will find it pretty complicated at places, and they
> already have a lot to learn. 

I am not saying you should not split them, just with limited time and
resources it may be better to concentrate on 1.5 first as that is what
most, if not all, new users will need.

> It's fairly
> easy to duplicate the doc and weed out the 1.0 stuff from one copy and
> the 1.5 stuff from the other.

In that case, go for it <g>

Phil

-- 
Firdbird has my support, has it yours? www.firebirdsql.org/ff/foundation
      Find a better way of life, play Marbles - www.marillion.com
 ICQ:760757 | AIM:pjshrimpton | Y!:pjshrimpton | pjs...@ja...

Re: [Firebird-docs] Re: Docs on the go

[Lester C. <le...@ls...>]

Paul Vinkenoog wrote:

> I know very little about Wikis and their strong points.

The key thing I need for production systems is the 'diff' module. 
TikiPro ( like all wiki's ) logs every change to a wiki page, and can 
display the history. SO you can wind back 'attacks' or im my customer 
systems, notes relating to a clients activities are logged and changes 
timestamped.
Modules are being produced for html documents and no doubt XML will 
follow - we have the power :)

>>I produce all of my on-line documentation as linked html, rather
>>than linear documents, and I think that is what breaks DocBook?
> 
> "breaks" under what circumstances? Did you feed the HTML to a DocBook
> authoring tool, or did you try to produce the HTML from DocBook
> sources? Producing linked HTML from DocBook XML is a sinch (given
> the right tools, like the ones we have in the manual module).

All my editing is now via Eclipse which handles XML quite happily but I 
think I probably just need to spend time with what I have already, and 
then produce the Eclipse/Firebird Docs user guide ;)

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

Re: [Firebird-docs] Re: Docs on the go

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

Hi Lester,

[ DocBook ]

> I've had a couple of goes at trying to use it, but I simply can't
> get on with it.
> I need to be able to manage pages and small documents in isolation,
> and DocBooks is just too cumbersome for that.

It is possible: I manage documents both in isolation and as a linked
set, but this also involves the transformation stylesheets and their
parameters, so that's an additional learning curve...

Anyway I didn't mean to say that the Wiki or the Firefly approach is
not good. Low-treshold online systems where everyone can contribute
have their own dynamics and can be very useful. I just wonder if there
should be a Wiki *and* the Firefly system - if there will be enough
contributors for both, and if both systems have enough unique features
to warrant their simultaneous existence. I must say that I was
impressed with the PDFs that Nigel's engine produced. I know very
little about Wikis and their strong points.

> I produce all of my on-line documentation as linked html, rather
> than linear documents, and I think that is what breaks DocBook?

"breaks" under what circumstances? Did you feed the HTML to a DocBook
authoring tool, or did you try to produce the HTML from DocBook
sources? Producing linked HTML from DocBook XML is a sinch (given
the right tools, like the ones we have in the manual module).

> That said it is probably me that is broken ;)

Play some John Lee Hooker: Blues is the Healer :-)


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] Quick Start Guide: 1.0 and 1.5

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

Hi Phil,

>> I think this makes the document way too complicated, especially for
>> the new users who are its main target audience. So unless there are
>> serious objections I'll make two QSGs: one for 1.0.x, the other for
>> 1.5.x

> Would new users be using 1.0.x?  The only reason I can think of
> using 1.0.x over 1.5 is if you already have it in production, and
> can't upgrade.

I guess new users would (and should) go for 1.5. But if I don't split
the QSG, they will find it pretty complicated at places, and they
already have a lot to learn. Of course I could also just drop all the
1.0.x info and don't bother, but that would be throwing away the
effort and information that has gone into that version. It's fairly
easy to duplicate the doc and weed out the 1.0 stuff from one copy and
the 1.5 stuff from the other.


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] Re: Docs on the go

[Lester C. <le...@ls...>]

Paul Vinkenoog wrote:

>>From the DocBook XML sources we already produce HTML for the web and
> PDFs to package (and download). Of course this isn't an online editing
> system - but it's both versatile and *very* powerful. I do hope that
> more people will take a sniff at DocBook (see
> http://www.firebirdsql.org/manual/docwritehowto.html or
> http://www.firebirdsql.org/pdfmanual/Firebird-Docwriters-Info.pdf) and
> start contributing...

I've had a couple of goes at trying to use it, but I simply can't get on 
with it.
I need to be able to manage pages and small documents in isolation, and 
DocBooks is just too cumbersome for that.
The wiki approach allows updates to be dropped in from anywhere, but is 
not the answer either - but I can modify the internal tags to produce 
XML ones when I do an extract from the database.
I produce all of my on-line documentation as linked html, rather than 
linear documents, and I think that is what breaks DocBook?
That said it is probably me that is broken ;)

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

Re: [Firebird-docs] Quick Start Guide: 1.0 and 1.5

[Phil S. <ph...@sh...>]

Paul Vinkenoog wrote:

Hi,

> I think this makes the document way too complicated, especially for
> the new users who are its main target audience. So unless there are
> serious objections I'll make two QSGs: one for 1.0.x, the other for
> 1.5.x

Would new users be using 1.0.x?  The only reason I can think of using
1.0.x over 1.5 is if you already have it in production, and can't
upgrade.

Phil


-- 
Firdbird has my support, has it yours? www.firebirdsql.org/ff/foundation
      Find a better way of life, play Marbles - www.marillion.com
 ICQ:760757 | AIM:pjshrimpton | Y!:pjshrimpton | pjs...@ja...

Re: [Firebird-docs] Quick Start Guide: 1.0 and 1.5

[Phil S. <li...@sh...>]

Paul Vinkenoog wrote:

Hi,

> I think this makes the document way too complicated, especially for
> the new users who are its main target audience. So unless there are
> serious objections I'll make two QSGs: one for 1.0.x, the other for
> 1.5.x

Would new users be using 1.0.x?  The only reason I can think of using
1.0.x over 1.5 is if you already have it in production, and can't
upgrade.

Phil

-- 
Firdbird has my support, has it yours? www.firebirdsql.org/ff/foundation
      Find a better way of life, play Marbles - www.marillion.com
 ICQ:760757 | AIM:pjshrimpton | Y!:pjshrimpton | pjs...@ja...

[Firebird-docs] Quick Start Guide: 1.0 and 1.5

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

Hi all,

As said in another email, I'm roughly 75% through updating the Quick
Start Guide to include the Firebird 1.5 info. However, this leads to
all kinds of nested forks of the type:

  If you use Firebird 1.0.x, then
    - If you're on Win9x/Me, do this;
    - On Win NT/2000/XP, do the other thing;
  If you use Firebird 1.5.x, then
    - On Win9x/Me, do the mambo;
    - On Win NT/2000/XP, do the samba;

I think this makes the document way too complicated, *especially* for
the new users who are its main target audience. So unless there are
serious objections I'll make two QSGs: one for 1.0.x, the other for
1.5.x, and create separate branches for them in the CVS tree. For me
this is hardly more work than what I'm doing now, and for both readers
and future doc maintainers it's a lot more convenient.


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] Re: Docs on the go

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

Hi Nigel,

> If I do start filling up your TikiPro, will Paul V be able to use
> that info, or will we have to write things twice?

The info, yes, but only by cutting-and pasting into a DocBook
document, and applying the necessary tags.

> If we had an online system that produced XML for Paul, HTML for
> people searching the web, and PDF's to package up with
> releases...we'd be cooking...

From the DocBook XML sources we already produce HTML for the web and
PDFs to package (and download). Of course this isn't an online editing
system - but it's both versatile and *very* powerful. I do hope that
more people will take a sniff at DocBook (see
http://www.firebirdsql.org/manual/docwritehowto.html or
http://www.firebirdsql.org/pdfmanual/Firebird-Docwriters-Info.pdf) and
start contributing...


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] Re: Docs on the go

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

Hi Nigel,

> If you received by attachments, please suggest subject areas to
> concentrate on, and I'll get working.

How about the new security features in 1.5 ? (just an idea)

The Firebird Quick Start Guide has already been donated to the project
and will be bundled with all future releases. It's also available for
online browsing. This is intended to be *the* starting point for new
users; I don't think it makes much sense to have other general
"getting started" type docs floating around.

After the QSG is fully converted to 1.5 (about 75% done now) the
contents of IBPhoenix' "Using Firebird" will also be phased into
the project.

Back in January I liked the look of your Firefly pages! Too bad they
couldn't stay online. But let's suppose you can host them somewhere
else, then we're working on at least three parallel Firebird doc
systems:

- The DocBook-based documentation within the Firebird project;
- Lester's Wiki;
- Your Firefly pages.

I'm not saying this is bad, but will we have enough input for all
three to be viable? Anyway, let's all keep in touch via this list and
avoid too much overlap, especially when it comes to big docs that take
a lot of time to write and maintain.

BTW, since June we can produce not only HTML, but also decent-looking
PDF from our DocBook sources. See
  http://www.firebirdsql.org/index.php?op=devel&sub=doc
for an overview of what we've got, including the QSG.


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] Re: Docs on the go

[Lester C. <le...@ls...>]

(Forgot to check eMail address ;) )
Chris Knight wrote:

>>Like Firebird on FreeBSD :)
>>
>>Building from Source
> 
> If you're talking about FreeBSD, then all you do is:

Nigel has already written a page
http://home.lsces.co.uk/TikiPro/wiki/index.php?page=Firebird+on+FreeBSD+-+Quick+Guide
He was asking about what else to write.

Nigel
While I agree that straight into XML would be nice, the wiki approach
where material can evolve is a lot easier to manage.

Personally I still haven't got a tidy XML editing system, and I don't
have time to play with it. I actually need the wiki approach for the
next generation of management systems, so any spin off uses are nice.

Now if you want a job, a wiki using XML .....

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

Re: [Firebird-docs] Re: Docs on the go

[A6-CMO P. M. <mak...@a6...>]

Le 12/08/2004 09:09, Nigel Weeks a écrit :

> PHP, Firebird, and a webserver that'll use a SAPI module of PHP(faster)
>=20
> Runs on Windows, Faster on BSD/Linux.
>=20
> Nige.
>=20
>=20
So have a look at :
I think that Basic Hosting is ok

<quote>
I would like to make an offer for all FB Members here who are after fb
hosting, I will offer:

Basic Hosting - Free of charge (+ 1 FB Database)
Developer Hosting - 50% discount
Developer Plus Hosting - 25% discount

Rules:

1.  Must be a FB Member.
2.  FB Fees must be paid up to date.

How to claim:

Sign up at http://www.tectsoft.net/ send me an email with your fb members=
hip
name/email and we will apply the discount.

Rgds

Si Carter
TECT Software Ltd
http://www.tectsoft.net/

</quote>

PS I'm curious about your FireFly
it can be a good solution for my own project

--=20
Philippe Makowski

Firebird serveur SQL open-source en fran=E7ais
http://firebird-fr.eu.org

Ma cl=E9 PGP : http://makowski.net/pgpkey.html

RE: [Firebird-docs] Re: Docs on the go

[Nigel W. <nw...@ex...>]

PHP, Firebird, and a webserver that'll use a SAPI module of PHP(faster)

Runs on Windows, Faster on BSD/Linux.

Nige.

> -----Original Message-----
> From: fir...@li...
> [mailto:fir...@li...]On Behalf Of A6-CMO
> Philippe Makowski
> Sent: Thursday, 12 August 2004 5:06 PM
> To: fir...@li...
> Subject: Re: [Firebird-docs] Re: Docs on the go
>
>
> Le 12/08/2004 06:50, Nigel Weeks a écrit :
> > If I do start filling up your TikiPro, will Paul V be able
> to use that info,
> > or will we have to write things twice?
> >
> > If we had an online system that produced XML for Paul, HTML
> for people
> > searching the web, and PDF's to package up with releases...we'd be
> > cooking...
> >
> > If someone's got an ssh account, I can put FireFly back
> into action - it'll
> > do this fairly well.
> >
> What do you need for Firefly ?
>
>
> --
> Philippe Makowski
> Firebird serveur SQL open-source en français
> http://firebird-fr.eu.org
>
> Ma clé PGP : http://makowski.net/pgpkey.html
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Firebird-docs mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-docs
>

Re: [Firebird-docs] Re: Docs on the go

[A6-CMO P. M. <mak...@a6...>]

Le 12/08/2004 06:50, Nigel Weeks a écrit :
> If I do start filling up your TikiPro, will Paul V be able to use that =
info,
> or will we have to write things twice?
>=20
> If we had an online system that produced XML for Paul, HTML for people
> searching the web, and PDF's to package up with releases...we'd be
> cooking...
>=20
> If someone's got an ssh account, I can put FireFly back into action - i=
t'll
> do this fairly well.
>=20
What do you need for Firefly ?


--=20
Philippe Makowski
Firebird serveur SQL open-source en fran=E7ais
http://firebird-fr.eu.org

Ma cl=E9 PGP : http://makowski.net/pgpkey.html