> 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 if the technique can be applied to any
>> languag
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 if the technique can be applied to any
language including Japanes
Hi.
I greet this discussion. Korean PgDoc encoding is UTF-8 too.
korean SGML encoding is utf8 since 10 years.
currently, PgDoc is very inefficient for L10N work.
but, we have no clean idea for this workaround.
I think, English main document's encoding be continued currently.
Encoding of
> Hello,
> If I understand you right, your goal to change the docs encoding is to
> allow for the docs translation.
> But I don't think that the translation should be done that way (with
> replacing sgml/xml/whatever).
> Just as we don't translate server messages by copying all the source
> files a
> 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 any program like Inkscape it tends to get
> unreadable. But
On Thu, Aug 18, 2016 at 11:38:15AM +0300, Alexander Law wrote:
> Hello,
>
> While translating docs I encountered an inconsistency with the
> literal/replaceable Docbook tags.
>
> I believe that the 'replaceable' tag should be used for keywords that
> intended to be replaced with some values, but
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 any program like Inkscape it tends to get unreadable.
But if we
Hello,
If I understand you right, your goal to change the docs encoding is to
allow for the docs translation.
But I don't think that the translation should be done that way (with
replacing sgml/xml/whatever).
Just as we don't translate server messages by copying all the source
files and replaci
>> Really, what change we need, it is conversion from SGML to XML format.
>> It would solve some real problems, such as ability to include diagrams
>> in the docs,
This argument sounds weak to me. Last time when I proposed to include
diagrams in the docs in the pgsql-hackers list, some developers
Hello,
The next items in our plan were:
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.
Please consider c
In the previous mails we have seen some statements concerning the source
format of postgres' documentation and other statements to formats which
are derived from it. In the following I'm only speaking about the
original format. Premised this, I want to second Victor Wagner, who
wrote on pgsql-h
11 matches
Mail list logo
