I got a little carried away but the changes to the examples are whitespace only, so, should not be in this commit.
Overall the commit has enormous whitespace problems so that was my main point. Regards, Philip > I see no whitespace changes at all? > > Perhaps my commit message was inaccurate, it should have been: > > "Add parameter, returns and example blocks as per new coding style, all > other conversion had already been done. Previously these did not exist, > so they were written. All outdated, old, wrong documentation in these > functions has been updated or removed." > > Chris > > Philip Olson wrote: > > This commit has a lot of whitespace and content changes. > > Moving to the new doc style should contain neither. Well, > > sometimes it can't be avoided like adding what it returns to > > the new return refsect, etc. Examples should not be > > modified. Also, be sure to appropriately use the > > &example.outputs; and &example.outputs.similar; and new > > entities work well for items written a lot, such as > > descriptions for the result and connection parameters. > > > > For translators, a diff should be as small as possible. Be > > sure to check the unified diff many times before commit as > > 'make test' is not enough. In the very least it means losing > > all whitespace changes. > > > > Regards, > > Philip > > > > On Tue, 5 Apr 2005, Christopher Kings-Lynne wrote: > > > > > >>chriskl Tue Apr 5 01:55:14 2005 EDT > >> > >> Modified files: > >> /phpdoc/en/reference/pgsql constants.xml reference.xml > >> /phpdoc/en/reference/pgsql/functions pg-affected-rows.xml > >> pg-client-encoding.xml > >> pg-close.xml pg-connect.xml > >> pg-num-fields.xml > >> pg-num-rows.xml > >> Log: > >> - Convert more pgsql docs to new docs style. Add undocumented constant. > >> Update reference. > >> >
