Menu
▾
▴
firebird-docs
|
From: Paul V. <pa...@vi...> - 2004-01-31 02:17:05
|
Hello Lester,
[ reserved words glossary ]
> Is there an existing one ? I have not looked properly yet ;)
None that I know of, but then: I haven't looked *at all* ;-)
> If there isn't perhaps that is something I can start pulling
> together?
That would be great (unless we find an existing one we can use).
> As I think I said before, I an using Eclipse to manage the PHP,JS
> and CSS stuff and it handles XML as well, but needs some help there
> still - such as a decent viewer :)
I didn't know anything about Eclipse. I've looked up their website
just now, did some reading, and downloaded it. Looks very promising!
> Only problem I can see is that a couple of words wrap to the next
> column (GROUP_COMMIT_WAIT_TIME) but I can have a look at how that is
> managed.
I was going to ask you about that, but forgot. I thought either you or
the original author had done that on purpose to keep the column width
within limits (it happens three times, each time when the word is
really long), so I mimicked it in the XML. But I think it's ugly and
confusing (people may think that these words belong to two columns) so
we'd better change that.
In the original HTML they've just created spans like this:
<td valign="top" colspan="2">
<p align="left"> GROUP_COMMIT_WAIT</p>
</td>
In DocBook XML this is done like:
<entry namest="col-fb-only" nameend="col-sql92">
<para>GROUP_COMMIT_WAIT</para>
</entry>
The values for namest (span's start col) and nameend (end col) must
have been previously defined in the tgroup in order for this to work:
<tgroup cols="4">
<colspec colname="col-fb-and-sql99"/>
<colspec colname="col-fb-only"/>
<colspec colname="col-sql92"/>
<colspec colname="col-sql99-only"/>
I've removed these spans from my XML version now; will attach it.
BTW: Let's take this conversation back to firebird-docs; maybe we can
get some useful input from others, but even if not, then at least they
can see what's going on.
Greetings,
Paul Vinkenoog
[ Cc: to firebird-docs ]
|
|
From: Helen B. <he...@tp...> - 2004-01-31 02:42:36
|
At 01:23 PM 30/01/2004 +0100, Paul Vinkenoog wrote: >Hello Lester, > >[ reserved words glossary ] > > > Is there an existing one ? I have not looked properly yet ;) > >None that I know of, but then: I haven't looked *at all* ;-) Get the list this way: List from the LangRef of the IB6 Beta docs (look up "Keywords") + List from the release notes of the IB6 Beta docs + List from the Firebird 1.5 release notes. Then you will have them all. Helen > > If there isn't perhaps that is something I can start pulling > > together? > >That would be great (unless we find an existing one we can use). > > > As I think I said before, I an using Eclipse to manage the PHP,JS > > and CSS stuff and it handles XML as well, but needs some help there > > still - such as a decent viewer :) > >I didn't know anything about Eclipse. I've looked up their website >just now, did some reading, and downloaded it. Looks very promising! > > > Only problem I can see is that a couple of words wrap to the next > > column (GROUP_COMMIT_WAIT_TIME) but I can have a look at how that is > > managed. > >I was going to ask you about that, but forgot. I thought either you or >the original author had done that on purpose to keep the column width >within limits (it happens three times, each time when the word is >really long), so I mimicked it in the XML. But I think it's ugly and >confusing (people may think that these words belong to two columns) so >we'd better change that. > >In the original HTML they've just created spans like this: > > <td valign="top" colspan="2"> > <p align="left"> GROUP_COMMIT_WAIT</p> > </td> > >In DocBook XML this is done like: > > <entry namest="col-fb-only" nameend="col-sql92"> > <para>GROUP_COMMIT_WAIT</para> > </entry> > >The values for namest (span's start col) and nameend (end col) must >have been previously defined in the tgroup in order for this to work: > > <tgroup cols="4"> > <colspec colname="col-fb-and-sql99"/> > <colspec colname="col-fb-only"/> > <colspec colname="col-sql92"/> > <colspec colname="col-sql99-only"/> > >I've removed these spans from my XML version now; will attach it. > >BTW: Let's take this conversation back to firebird-docs; maybe we can >get some useful input from others, but even if not, then at least they >can see what's going on. > > >Greetings, >Paul Vinkenoog > > >[ Cc: to firebird-docs ] > > > > > >------------------------------------------------------- >The SF.Net email is sponsored by EclipseCon 2004 >Premiere Conference on Open Tools Development and Integration >See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. >http://www.eclipsecon.org/osdn >_______________________________________________ >Firebird-docs mailing list >Fir...@li... >https://lists.sourceforge.net/lists/listinfo/firebird-docs |
|
From: Lester C. <le...@ls...> - 2004-01-31 07:34:31
|
Helen Borrie wrote: >> [ reserved words glossary ] >> >> > Is there an existing one ? I have not looked properly yet ;) >> >> None that I know of, but then: I haven't looked *at all* ;-) > > Get the list this way: > > List from the LangRef of the IB6 Beta docs (look up "Keywords") > + > List from the release notes of the IB6 Beta docs > + > List from the Firebird 1.5 release notes. > > Then you will have them all. We have the LIST now, the next step is a GLOSSARY to go with it. If there is nothing already existing, then I will start filling one. Paul has converted the list to XML and created a sample for the glossary elements. >> > If there isn't perhaps that is something I can start pulling >> > together? >> >> That would be great (unless we find an existing one we can use). Given the original language reference you gave doesn't have much detail, I presume I will have to do some digging :) >> > As I think I said before, I an using Eclipse to manage the PHP,JS >> > and CSS stuff and it handles XML as well, but needs some help there >> > still - such as a decent viewer :) >> >> I didn't know anything about Eclipse. I've looked up their website >> just now, did some reading, and downloaded it. Looks very promising! The more I start to get into Eclipse, the more I like it. Sun are suggesting that it's only the same as NetBeans, BUT NetBeans can't handle ( as far as I can find out ) PHP development and debugging, javascript, and I'm now looking at C++ Since BuilderX is going to be another expensive bug fix ( when them finish it ;) ). I haven't thought about using Eclipse for Java at all. The CVS client is great, a lot more user friendly than the options I had played with so far. It might even convince me to drop FreeVCS (using Firebird) and switch to CVS my self! >> > column (GROUP_COMMIT_WAIT_TIME) but I can have a look at how that is >> > managed. >> >> I was going to ask you about that, but forgot. I thought either you or >> the original author had done that on purpose to keep the column width >> within limits I think that is the answer - it was designed to print filling the page. >> BTW: Let's take this conversation back to firebird-docs; maybe we can >> get some useful input from others, but even if not, then at least they >> can see what's going on. The list does seem a bit slow in responding? Paul's message came through lunchtime yesterday, by midnight the list copy still had not appeared. The CVS server seems to be down at the moment so I can't look, should the Glossary be a separate file to the base list? Is it worth my taking the PHP starter guide and converting it? I also have the basis for a Linux version which the guys(and galls) on the php list are helping to fill out. -- Lester Caine ----------------------------- L.S.Caine Electronic Services |
|
From: Helen B. <he...@tp...> - 2004-01-31 07:53:00
|
At 07:34 AM 31/01/2004 +0000, Lester Caine wrote: >Helen Borrie wrote: > >>>[ reserved words glossary ] >>> >>> > Is there an existing one ? I have not looked properly yet ;) >>> >>>None that I know of, but then: I haven't looked *at all* ;-) >>Get the list this way: >>List from the LangRef of the IB6 Beta docs (look up "Keywords") >>+ >>List from the release notes of the IB6 Beta docs >>+ >>List from the Firebird 1.5 release notes. >>Then you will have them all. > >We have the LIST now, the next step is a GLOSSARY to go with it. If there >is nothing already existing, then I will start filling one. Paul has >converted the list to XML and created a sample for the glossary elements. Sorry, I missed that you were building a glossary of reserved words. And you're right, in the IB docs they are not indexed reliably. Have you looked at this: http://www.ocelot.ca/glossary.htm Helen |
|
From: Paul V. <pa...@vi...> - 2004-02-01 01:14:52
|
Hi Lester, > The list does seem a bit slow in responding? Paul's message came > through lunchtime yesterday, by midnight the list copy still had > not appeared. Yes, but that's very very rare. I usually see my own messages back in minutes. Maybe it had something to do with the current virus storm. > The CVS server seems to be down at the moment so I can't look, > should the Glossary be a separate file to the base list? If it's a glossary of reserved words only, I think it should be in one document with the table. A DocBook XML document can be spread over several files if you want to, but this sometimes results in practical inconveniences if you edit them with XMLMind. Better leave them in one file; you can always collapse the first section if you want to concentrate on the glossary, and vice versa. BTW, after rendering the glossary is automatically placed in a separate HTML document, just like major <section>s wind up in a file of their own (at least in the defaulthtml build target). > Is it worth my taking the PHP starter guide and converting it? I > also have the basis for a Linux version which the guys(and galls) > on the php list are helping to fill out. Sounds like a good idea to me! Greetings, Paul Vinkenoog |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X