Doc #51978 [Fbk->Opn]: grammar error

Edit report at http://bugs.php.net/bug.php?id=51978&edit=1 ID: 51978 Updated by: rasmus@php.net Reported by: johncburr at hotmail dot com Summary: grammar error -Status: Feedback +Status: Open Type: Documentation Problem Package: Documentation problem Operating System: NA PHP Version: Irrelevant New Comment: He is talking about "an sql" vs. "a sql". And I agree with him, we should be using "an sql" everywhere. Previous Comments: ------------------------------------------------------------------------ [2010-06-02 20:34:27] degeberg@php.net Ah, I see what you mean now. Where do you see the phrase "A SQL statement" though? daniel@daniel-laptop:~/projects/phpdoc/en$ ack 'An?\s+SQL' reference/mssql/functions/mssql-query.xml 32: A SQL query. reference/mysql/functions/mysql-query.xml 32: A SQL query reference/ibm_db2/functions/db2-exec.xml 56: An SQL statement. The statement cannot contain any parameter markers. reference/ibm_db2/functions/db2-prepare.xml 81: An SQL statement, optionally containing one or more parameter markers.. ------------------------------------------------------------------------ [2010-06-02 20:28:53] degeberg@php.net What are you talking about? ------------------------------------------------------------------------ [2010-06-02 20:19:48] johncburr at hotmail dot com Description: ------------ I understand that, despite the OFFICIAL ISO standard in this regard, there is a great debate regarding the correct pronunciation of the acronym, "SQL". While some vendors prefer to pronounce it, "see kwel", MySQL OFFICIALLY pronounces it "ess cue el" and all documentation for MySQL should reflect that. Therefore, the phrase, "A SQL statement..." is poor grammar. It should read, "An SQL statement..." and so forth. Frankly, the ISO officially pronounces it the same way that MySQL does and so the mispronunciation, "see kwel", is an indication of an individual who is uninformed regardless of their position in the industry. We programmers do, after all, live or die by our ability to adapt to the current standards. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/bug.php?id=51978&edit=1