Commitee37fb5

committed

Add guidelines for formatting errcontext strings

1 parent7bfc0e5 commitee37fb5Copy full SHA for ee37fb5

File tree

-1

lines changed

-1

lines changed

Lines changed: 7 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<!-- $PostgreSQL: pgsql/doc/src/sgml/sources.sgml,v 2.35 2009/10/08 02:39:16 tgl Exp $ -->`
	`1`	`+<!-- $PostgreSQL: pgsql/doc/src/sgml/sources.sgml,v 2.36 2010/06/28 17:48:26 petere Exp $ -->`
`2`	`2`
`3`	`3`	`<chapter id="source">`
`4`	`4`	`<title>PostgreSQL Coding Conventions</title>`
`@@ -444,6 +444,12 @@ Hint: the addendum`
`444`	`444`	`inappropriate in other languages).`
`445`	`445`	`</para>`
`446`	`446`
	`447`	`+ <para>`
	`448`	`+ Error context strings: Do not capitalize the first letter and do`
	`449`	`+ not end the string with a period. Context strings should normally`
	`450`	`+ not be complete sentences.`
	`451`	`+ </para>`
	`452`	`+`
`447`	`453`	`<para>`
`448`	`454`	`Rationale: Avoiding punctuation makes it easier for client applications to`
`449`	`455`	`embed the message into a variety of grammatical contexts. Often, primary`

Comments

(0)