Hi Helen,
> >But in case you didn't receive it: user name dommasw, user id 3560308
>
> Done.
Thanks,
> (I take it you are not planning to go to bed today... ;-) )
*Just* logging off - really! :-)
Paul
--
All the data
At 02:21 PM 27/09/2011, Paul wrote:
>But in case you didn't receive it: user name dommasw, user id 3560308
Done.
(I take it you are not planning to go to bed today... ;-) )
Cheers,
Helen
--
All the data continuously g
Helen wrote:
> >OK, it's done, so please do a cvs update in manual/src/docs/refdocs
>
> Are we still using cvs?
For the manual module, yes.
> >Dmitry, could you add Thomas to the project so he can commit his changes to
> >CVS? Or should I ask this in fb-admins?
>
> I can do it if I know Thomas'
At 11:46 AM 27/09/2011, Paul Vinkenoog wrote:
>Hi all,
>
If you guys (that's Dmitry and Thomas, but of course others are also
welcome to comment) agree with splitting the source, I suggest we put it
in a separate subdir (e.g. refdocs/langref/langref25), given the number
of sourc
> Dmitry, could you add Thomas to the project so he can commit his changes to
> CVS? Or should I ask this in fb-admins?
Oh, forgot to mention: his user name is dommasw, user id 3560308.
Paul
--
All the data continuousl
Hi all,
>>> If you guys (that's Dmitry and Thomas, but of course others are also
>>> welcome to comment) agree with splitting the source, I suggest we put it
>>> in a separate subdir (e.g. refdocs/langref/langref25), given the number
>>> of source files that will result from the split.
>
> D> I do
Hi all,
>> If you guys (that's Dmitry and Thomas, but of course others are also
>> welcome to comment) agree with splitting the source, I suggest we put it
>> in a separate subdir (e.g. refdocs/langref/langref25), given the number
>> of source files that will result from the split.
D> I don't min
Hi Norman,
> > XMLMind wasn't the problem (anymore), but it broke our build tools. More
> > precisely: Saxon.
> > Do you manage to build the docs with our current build tools if xincludes
> > are present?
> To be honest, since the problems were detected (September 2008), I've
> never tried to bu
All,
Our build system has been updated to enable the use of xincludes. To get up to
date, you need to take these two steps:
1) Download http://www.firebirdsql.org/doclibs/xercesImpl.jar to your local
manual/lib folder.
2) Do a cvs update, either global or in both manual/lib and manual/src/buil
Morning Paul,
> XMLMind wasn't the problem (anymore), but it broke our build tools. More
> precisely: Saxon.
> Do you manage to build the docs with our current build tools if xincludes are
> present?
To be honest, since the problems were detected (September 2008), I've
never tried to build with
26.09.2011 14:28, Paul Vinkenoog wrote:
>
>> It's also worth to look at the v2.5.1 Release Notes, as it mentions the
>> new SQLSTATE context variable which is not documented in the v2.5 LRU yet.
>
> Not in the published version, but the latest committed sources are fully up
> to date with SQLSTATE
Norman wrote:
> Actually, since I originally posted that, I've been using XML Mind
> version 4.3.0_01 which is happy to handle xincludes without - as far as
> I know - requiring xerces.
XMLMind wasn't the problem (anymore), but it broke our build tools. More
precisely: Saxon.
Do you manage to b
Dmitry wrote:
> > You only need the chapter from the 2.5 LRU. The best approach is probably
> > to copy that chapter, edit the existing sections as necessary and add the
> > missing bits.
>
> It's also worth to look at the v2.5.1 Release Notes, as it mentions the
> new SQLSTATE context variable wh
On 26/09/11 03:40, Paul Vinkenoog wrote:
> ...
> Talking about chapters: I propose that we create a separate file for each
> chapter, e.g. langref25-intro.xml, langref25-contextvars.xml etc.
>
> The LRU 25 has already become awkwardly large (over 20,000 lines), and
> the full LangRef will be a lo
On 26/09/11 03:16, Paul Vinkenoog wrote:
> On Fri, 26 Sep 2008 17:10:26 +0200, Norman Dunbar wrote:
Eh? ;-)
> ...
> Solved! Now is that quick or what? :-)
Extremely - thanks!
Actually, since I originally posted that, I've been using XML Mind
version 4.3.0_01 which is happy to handle xincludes w
On Mon, Sep 26, 2011 at 10:36 AM, Dmitry Yemanov wrote:
> Only SQLCODE is deprecated (in favor of SQLSTATE),
> GDSCODE is still the only choice to uniquely identify the error.
Clearly, this qualifies GDSCODE als not deprecated.
-
26.09.2011 12:32, Thomas Woinke wrote:
>> It's also worth to look at the v2.5.1 Release Notes, as it mentions the
>> new SQLSTATE context variable which is not documented in the v2.5 LRU yet.
>
> Good point, I'll mark GDSCODE and SQLCODE as deprecated, too.
Only SQLCODE is deprecated (in favor o
On Mon, Sep 26, 2011 at 6:48 AM, Dmitry Yemanov wrote:
> It's also worth to look at the v2.5.1 Release Notes, as it mentions the
> new SQLSTATE context variable which is not documented in the v2.5 LRU yet.
Good point, I'll mark GDSCODE and SQLCODE as deprecated, too.
On Mon, Sep 26, 2011 at 4:40 AM, Paul Vinkenoog wrote:
> You only need the chapter from the 2.5 LRU. The best approach is probably
> to copy that chapter, edit the existing sections as necessary and add the
> missing bits.
Okay.
> Talking about chapters: I propose that we create a separate file f
19 matches
Mail list logo
