y tags).
>
> I used the tools provided in the "Docbook 5.x" thread, in particular the
> sgml2xml.pl script. I think you should be able to use that for your
> documentation as well.
Thank you for the info!
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp
; unfortunately.)
Just out of curiosity, did you do the work (expanding the empty tags)
manually or using some tools? We are using SGML DocBook in the
Pgpool-II project and a little bit annoyed by the empty tags (for
example emacs auto indentation does not work with empty tags).
Best regards,
--
T
ing on the logical replication here would give
users cleaner image of PostgreSQL replication solutions.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To ma
> On 1/4/17 19:25, Tatsuo Ishii wrote:
>> In:
>> https://www.postgresql.org/docs/devel/static/runtime-config-file-locations.html
>>
>> ---
>> ident_file (string)
>>
>> Specifies the configuration
GML coding:
Specifies the configuration file for
user name mapping
(customarily called pg_ident.conf).
This parameter can only be set at server start.
Shouldn't we use a link tag instead of the xref tag here? Attached is
a patch to fix this.
Best reg
GML coding:
Specifies the configuration file for
user name mapping
(customarily called pg_ident.conf).
This parameter can only be set at server start.
Shouldn't we use a link tag instead of the xref tag here? Attached is
a patch to fix this.
Best reg
have been
"the portion of the plan below"?
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http:
> Hello,
> 24.08.2016 02:19, Tatsuo Ishii пишет:
>>> We at Postgres Pro using the gettext technologies for this. And we
>>> have complete working toolchain (including modified Makefile) for
>>> translation the docs.
>> Sounds great but I am not sure
FreeBSD Documentation Project is most remarkable example) or similar
> approaches.
As far as I know, FreeBSD's Japanese document project does not use
the gettext technologies.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http:/
know that. Thank you for pointing it out. I hope this work
will be included in 10.0.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to
lve all the
problems we have.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
tion with Peter at pgsql-hackers.
> On 8/22/16 9:32 AM, Tatsuo Ishii wrote:
>> I don't know what kind of problem you are seeing with encoding
>> handling, but at least UTF-8 is working for Japanese, French and
>> Russian.
>
> Those translations are using DocBook XM
12 matches
Mail list logo