Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id A53CC632E98; Thu, 17 Jun 2010 06:07:19 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 51351-08; Thu, 17 Jun 2010 09:07:12 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pv0-f174.google.com (mail-pv0-f174.google.com [74.125.83.174]) by mail.postgresql.org (Postfix) with ESMTP id EABF2632A1D; Thu, 17 Jun 2010 06:07:11 -0300 (ADT) Received: by pvg6 with SMTP id 6so91476pvg.19 for ; Thu, 17 Jun 2010 02:07:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:content-type :content-transfer-encoding; bh=VBcl1EuuTD1NXaQY0vG3K8+ttwqJMG92mlAf6+3SAWk=; b=UdhT5uY5DDqrpAcUOfuoP/al9QTsvQx4t1D+Gnzx+AwJg3ftHMqIX+YCcDGLfwWkeT UrWb9eOIQ6MhDOBxkwVOXbG58jzCEmSWTTXjmsY4U13McJimExQzisn0pNtRVYHQe3/Y eVR5qKw/E3t9MDT8iaA+P0/0AWcRAd7j71bJU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type:content-transfer-encoding; b=xnwPG6lfeAd6WZ89K5ujAU5E5tVzoMS4+zYtCOjjZhr+w/2AWBmNZy0w8IffWImLyX KwwYmUQ/GaYfgUAsoylFSG47k3Lw6z71g5P3ML5LEZYRCCc7dMj36xoaEf5fRn/7ZVUh IwnjkEPuCQGrIQHtcIVhX8AqsQdH70euvmx2s= Received: by 10.141.14.8 with SMTP id r8mr8061790rvi.271.1276765630072; Thu, 17 Jun 2010 02:07:10 -0700 (PDT) Received: from [10.0.2.101] (p0245ed.tokyff01.ap.so-net.ne.jp [121.2.69.237]) by mx.google.com with ESMTPS id d14sm7878154rva.6.2010.06.17.02.07.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 17 Jun 2010 02:07:09 -0700 (PDT) Message-ID: <4C19E5B9.3040002@gmail.com> Date: Thu, 17 Jun 2010 18:07:05 +0900 From: Satoshi Nagayasu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org, pgsql-docs@postgresql.org CC: Bruce Momjian , Michael Meskes Subject: ECPG Documentation Improvement Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201006/39 X-Sequence-Number: 5607 Hi all, I'm trying to improve the ECPG documents for the ECPG application developrs, because some of my clients want more detailed information when they develop (or migrate) an embeded SQL applications. Of course, I want to contribute this work to the official manual. So I have one thing to introduce to you, and thing to ask you. At first, I've done writing ECPG directives. I think it could be useful for the ECPG application developers, similar to the SQL reference section in the official manual. ecpgdocs @ GoogleCode (I'm working here.) http://code.google.com/p/ecpgdocs/ ecpgdocs downloads (You can find the current document.) http://code.google.com/p/ecpgdocs/downloads/list?deleted=1&ts=1276763948 However, I'm not familiar with ECPG details or internals, so here is one asking, I hope someone to review my documents and give some feedback to me. Feedbacks which I'm expecting are: - Is this document useful? - Missing directives. - Missing or wrong synopsis. - More appropriate descriptions on parameters or examples. - How to contribute this to the official manual. - Correcting English. (sorry for my poor English.) - etc... Honestly, I'm not familiar with the documentation acceptance/review process, so any advice and/or comments are welcome. Regards, -- NAGAYASU Satoshi