<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [postgis-devel] SQL comment generation</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>That's what I was thinking the packaging would pre-build and it would be another<BR>
sql file similar to spatial_ref_sys.sql. Alternatively for release I guess we could manually build and put in the right location in svn. Would be redundant but oh well.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: postgis-devel-bounces@postgis.refractions.net on behalf of Chris Hodgson<BR>
Sent: Mon 9/22/2008 12:31 PM<BR>
To: PostGIS Development Discussion<BR>
Subject: Re: [postgis-devel] SQL comment generation<BR>
<BR>
Or can we have the package-building process pre-build the documentation<BR>
and include it and the comments in the source tarball? I guess that<BR>
doesn't work for SVN checkouts... but for releases it seems like it<BR>
could be nice.<BR>
<BR>
Chris<BR>
<BR>
Kevin Neufeld wrote:<BR>
> Great work on this Regina. It looks good.<BR>
><BR>
> Were you thinking this sql would be another file a user would load<BR>
> into a postgis database in addition to lwpostgis.sql and<BR>
> spatial_ref_sys.sql, or that we would concatenate it to<BR>
> lwpostgis.sql. I would love to see it in lwpostgis.sql, but that<BR>
> would mean folks would now have to build the documentation to get a<BR>
> spatially enabled database, whereas before they needn't bother. Hmmmmm.<BR>
><BR>
> I wonder if we can do both. Have the makefile build the docs and<BR>
> concatenate the comments during the main build process if xsltproc is<BR>
> installed, otherwise, the docs don't build and lwpostgis.sql remains<BR>
> as is. No harm done.<BR>
><BR>
> -- Kevin<BR>
><BR>
> Obe, Regina wrote:<BR>
>> Mark,<BR>
>><BR>
>> I created a new xsl folder and committed the postgis_comments.sql.xsl I<BR>
>> created to that.<BR>
>><BR>
>> I also made some enhancements to it to include the arg names in the<BR>
>> comments. Sample generated sql file is attached and seems to work just<BR>
>> fine with xsltproc.<BR>
>><BR>
>> To test I ran the command<BR>
>><BR>
>> xsltproc -o postgis_comments.sql xsl/postgis_comments.sql.xsl<BR>
>> reference_new.xml<BR>
>><BR>
>> Though I guess that is not exactly the best place to put it.<BR>
>><BR>
>> In the process I discovered there is really no<BR>
>> ST_BdPolyFromText(text), ST_BdMPolyFromText(text)<BR>
>><BR>
>> or<BR>
>><BR>
>> ST_WktToSQL(text,srid)<BR>
>> even in the 1.4<BR>
>><BR>
>> These seem counter-intuitive to me since we have such constructs for<BR>
>> ST_GeomFromText, ST_GeometryFromText.<BR>
>><BR>
>> Anyrate if this all looks okay to you, can you integrate in the build<BR>
>> and figure out where the postgis_comments.sql should go.<BR>
>><BR>
>> As I mentioned I was eventually planning to create similar xsl files<BR>
>> that will comb out aggregate, mm and 3d compatible functions and<BR>
>> generate an additional toc doc .xml file from those that will then be<BR>
>> processed by our docbook generation step and simply provide an index<BR>
>> listing of said functions.<BR>
>><BR>
>> Can I chain these together like that? - xsl to generate docbox xml, then<BR>
>> docbook to build document?<BR>
>><BR>
>> Thanks,<BR>
>> Regina<BR>
>><BR>
>><BR>
>><BR>
>><BR>
>><BR>
>> -----------------------------------------<BR>
>> The substance of this message, including any attachments, may be<BR>
>> confidential, legally privileged and/or exempt from disclosure<BR>
>> pursuant to Massachusetts law. It is intended<BR>
>> solely for the addressee. If you received this in error, please<BR>
>> contact the sender and delete the material from any computer.<BR>
>><BR>
>><BR>
>> ------------------------------------------------------------------------<BR>
>><BR>
>> This body part will be downloaded on demand.<BR>
> _______________________________________________<BR>
> postgis-devel mailing list<BR>
> postgis-devel@postgis.refractions.net<BR>
> <A HREF="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>
<BR>
_______________________________________________<BR>
postgis-devel mailing list<BR>
postgis-devel@postgis.refractions.net<BR>
<A HREF="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>