|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/sources.sgml,v 2.25 2007/02/0120:28:08 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/sources.sgml,v 2.26 2007/02/0121:28:34 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="source"> |
4 | 4 | <title>PostgreSQL Coding Conventions</title> |
@@ -605,6 +605,30 @@ BETTER: unrecognized node type: 42 |
605 | 605 | </para> |
606 | 606 | </formalpara> |
607 | 607 |
|
| 608 | + <formalpara> |
| 609 | + <title>May/Can/Might</title> |
| 610 | + <para> |
| 611 | + <quote>May</quote> suggests permission (e.g. "You may borrow my rake.") |
| 612 | + and has little use in documentation or error messages. |
| 613 | + <quote>Can</quote> suggests ability (e.g. "I can lift that log."), |
| 614 | + and <quote>might</quote> suggests possibility (e.g. "It might rain |
| 615 | + today."). |
| 616 | + </para> |
| 617 | + |
| 618 | + <para> |
| 619 | + Rationale: Using the proper word clarifies meaning and assists |
| 620 | + translation. |
| 621 | + </para> |
| 622 | + </formalpara> |
| 623 | + |
| 624 | + <formalpara> |
| 625 | + <title>Contractions</title> |
| 626 | + <para> |
| 627 | + Avoid contractions, like <quote>can't</quote>; use |
| 628 | + <quote>cannot</quote> instead. |
| 629 | + </para> |
| 630 | + </formalpara> |
| 631 | + |
608 | 632 | </simplesect> |
609 | 633 |
|
610 | 634 | <simplesect> |
|