Re: [DOCS] UTF-8 docs

2016-08-24 Thread Alexander Law
24.08.2016 09:58, Tatsuo Ishii пишет: Please look at the attached .pot for one of the doc files. You can use any translation software (which supports .po (e.g. poedit, Lokalize, ...)) to translate it to any language. And you can look at all the docs converted to .po for translation: http://oc.po

Re: [DOCS] UTF-8 docs

2016-08-24 Thread Oleg Bartunov
On Wed, Aug 24, 2016 at 2:04 AM, Tatsuo Ishii wrote: >> Arguments pro and contra diagrams are not the central focus of SGML to >> XML conversion, nevertheless: "Diagrams" didn't mean any binary format >> - only SVN or any other text-format is acceptable. And: if the SVN >> source is generated by a

Re: [DOCS] Incorrect 'literal' tags

2016-08-24 Thread Alexander Law
Hello, I believe that the 'replaceable' tag should be used for keywords that intended to be replaced with some values, but 'literal' is for literal usage. But there are some places in the docs where 'literal' is used for replaceable values. Patch attached. Patch applied and backpatched to 9.6.

Re: [DOCS] Docbook 5.x

2016-08-24 Thread Peter Eisentraut
On 8/23/16 10:23 AM, Alexander Law wrote: >> An immediate problem is that the patched stuff no longer works with >> > older stylesheets (1.76.1?). I'm glad to leave older stuff behind for a >> > 400% speedup, but we need to analyze the exact effect and possibly >> > document it or work around it.

[DOCS] update to alter user mapping example

2016-08-24 Thread gabrielle
Hello! The example for ALTER USER MAPPING is missing the action keyword (ADD|SET|DROP). Since ADD is the default option, the given command attempts to add a user 'bob' to the already-existing user mapping 'bob', which throws an 'ERROR: option "user" provided more than once' Here's a working exa

Re: [DOCS] Incorrect 'literal' tags

2016-08-24 Thread Bruce Momjian
On Wed, Aug 24, 2016 at 01:17:25PM +0300, Alexander Law wrote: > Hello, > > >>I believe that the 'replaceable' tag should be used for keywords that > >>intended to be replaced with some values, but 'literal' is for literal > >>usage. But there are some places in the docs where 'literal' is used fo