Re: nested tags in glossary entries in html docs

2024-04-25 Thread Alexander Lakhin
Hello, 25.04.2024 12:24, Alvaro Herrera wrote: On 2024-Apr-12, Erik Wienhold wrote: There's this bug[1] in the DocBook XSLT stylesheets. Looks like the fix[2] landed in 1.79.2 (latest version on Arch, Maybe one of these days we should get going with the migration to Docbook 5.x that Jürgen

Re: Typo in "43.9.1. Reporting Errors and Messages"?

2023-10-31 Thread Alexander Lakhin
Hi Bruce, 31.10.2023 17:52, Bruce Momjian wrote: It is referring to the internal constant (see src/backend/utils/errcodes.h). It was like you are proposing and it was changed in 66bde49d96a9ddacc49dcbdf1b47b5bd6e31ead5. Reading the original thread, there is no explanation why it was changed.

Re: The huge_pages parameter doesn't work when shared_memory_type is sysv

2021-10-22 Thread Alexander Lakhin
Hello Thomas, 22.10.2021 06:59, Thomas Munro wrote: > That > second patch included exactly such a documentation adjustment, and an > error message too (the idea was to reject that combination on Linux > but allow it on AIX). Here are those bits, extracted. > >

Re: Some inconsistencies in release-14

2021-09-19 Thread Alexander Lakhin
Hello Tom, 19.09.2021 22:43, Tom Lane wrote: > Alexander Lakhin writes: >> While translating names in the acknowledgment section, I've found >> inconsistent spelling of several names. > I believe we've standardized on given-name-first in these lists. > (There was some discus

Some inconsistencies in release-14

2021-09-19 Thread Alexander Lakhin
Hello hackers, While translating names in the acknowledgment section, I've found inconsistent spelling of several names. 1) Dong Wook vs Lee Dong Wook Dong Wook mentioned in 64fe120b (with e-mail sh95...@gmail.com) Dong Wook Lee mentioned in 64725728

Minor fixes for PostgreSQL 13 documentation

2020-08-22 Thread Alexander Lakhin
Hello, Please consider applying fixes for bugs (incorrect tags, redundant spaces, etc.) I noticed while translating the documentation. Best regards, Alexander diff --git a/doc/src/sgml/btree.sgml b/doc/src/sgml/btree.sgml index d03ee4d6fa..435b7cb24d 100644 --- a/doc/src/sgml/btree.sgml +++

Re: Rendering pi more nicely in PDF

2020-04-29 Thread Alexander Lakhin
Hello hackers, 30.04.2020 00:23, Alvaro Herrera wrote: > But apparently it's not sufficient -- the new font is not used > everywhere. For example footnotes seem to use a different font than the > main body of text. (I altered the fontname to Gentium, which I like > better, and uses a different

Re: Rendering pi more nicely in PDF

2020-04-27 Thread Alexander Lakhin
27.04.2020 18:04, Tom Lane wrote: > Alexander Lakhin writes: >> 26.04.2020 22:13, Tom Lane wrote: >> BTW, I tried to also use this markup inside the template for >> , so we'd only need one font-switching special case not two. >> Didn't work though --- apparently

Re: Rendering pi more nicely in PDF

2020-04-26 Thread Alexander Lakhin
>From the symbolic unit of the department... Hello Tom, 26.04.2020 22:13, Tom Lane wrote: > In the department of nitpickery ... > > "" renders poorly in our PDF docs: as shown in the attached > screenshot, it doesn't line up on the baseline. I realized that > this is the same problem I'd run

Re: Getting our tables to render better in PDF output

2020-04-12 Thread Alexander Lakhin
Hello Tom, 12.04.2020 20:33, Tom Lane wrote: > I wrote: >> So if we can get to both insert a right arrow and switch the >> font to match 's choice, this would work more or less decently, and >> it's probably cleaner than the bare-entity-reference approach I posted >> before. I don't have the XSL

Re: Getting our tables to render better in PDF output

2020-02-16 Thread Alexander Lakhin
Hello Tom, > 16.02.2020 23:07, Tom Lane wrote: > > > I poked at this a little bit, and found that I could get a pretty > decent-looking result if I hacked the .fo file to contain > "→" rather than a bare > right arrow. (See attached screenshot, wherein the last rightarrow > was fixed this way but

Re: PDF doc build is broken on recent Fedora

2020-02-15 Thread Alexander Lakhin
15.02.2020 12:09, Alexander Lakhin wrote: > I've just reproduced this on Fedora 29, 30, 31. > On Fedora 29 I see almost the same package versions: > docbook-style-xsl-1.79.2-8.fc29.noarch > libxslt-1.1.33-1.fc29.x86_64 > > But it's not reproduced on Fedora 28, where I have: &

Re: PDF doc build is broken on recent Fedora

2020-02-15 Thread Alexander Lakhin
Hello Tom, 13.02.2020 23:37, Tom Lane wrote: > By chance I tried to build our PDF docs on a Fedora 30 > installation, and it doesn't work. xsltproc seems to > get hung up in a tight loop before it starts to produce > any output. The HTML build works fine, though. > > Relevant package versions: >

Re: Getting our tables to render better in PDF output

2020-02-12 Thread Alexander Lakhin
12.02.2020 23:58, Tom Lane wrote: > Alexander Lakhin writes: >> Please look at a less invasive approach that we use at Postgres Pro for >> some time (mainly for improving the translated documentation, but it >> works for the original one too). The idea is to add zero-width s

Re: Getting our tables to render better in PDF output

2020-02-11 Thread Alexander Lakhin
Hello Tom, 12.02.2020 00:51, Tom Lane wrote: > The crummy formatting of our tables of functions and operators has > been an issue for a long time. To my mind, there are several things > that need to be addressed: > > * The layout is completely unfriendly to function descriptions that > run to

Miscellaneous minor fixes

2019-10-14 Thread Alexander Lakhin
Hello, Please consider fixing minor inconsistencies and typos in doc/. (fix-contributor-name.patch is for REL_12_STABLE only) Best regards, Alexander diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml index 5e2992ddac..3e6f9cd532 100644 --- a/doc/src/sgml/ref/copy.sgml +++

Fix contributor name-related inconsistencies in release-12.sgml

2019-09-23 Thread Alexander Lakhin
Hello, While translating Release Notes for version 12 I found some inconsistencies with contributor names. 1. Constantine Kuznetsov and Konstantin Kuznetsov are the same person. 2. Sho Kato and Kato Sho too. 3. Takayuki Tsunakawa is present in the Acknowledgments, but Tsunakawa Takayuki is

Some typos in documentation

2019-01-12 Thread Alexander Lakhin
Hello, While cross-checking the unique words in doc/ I found a few typos. REL9_6_STABLE transcations (Also there are two 'transcation's in src/bin/psql/po/tr.po, probably these are typos too.) REL_10_STABLE+ PQencryptPasswodConn pg_current_logfiles -- there is only the "pg_current_logfile"

A typo in release notes

2018-11-12 Thread Alexander Lakhin
Hello, I believe, that the name "Masahiko Sawada" was misspelled in the latest release notes. See: https://www.postgresql.org/message-id/CAD21AoB5K1qJm%2Bwj%2BTTCP-sFPiSdnd0LGd_pNAfi3VXrGKfdjw%40mail.gmail.com The patch is attached. Best regards, Alexander diff --git

Re: PDF build warnings

2018-06-27 Thread Alexander Lakhin
r such id don't get into internal FOP id table and then when rechecking id's it can't be resolved. Still think that it should be fixed just to bring attention to another (may be more important) warnings. I can prepare a patch if you find it useful. Best regards, -- Alexander Lakhin Postgres

Re: [DOCS] list of credits for release notes

2018-02-02 Thread Alexander Lakhin
Hello, 03.02.2018 00:56, Peter Eisentraut wrote: On 10/3/17 03:16, Alexander Lakhin wrote: While working on translation I've found a wrong name in credits: Fakhroutdinov Evgenievich That's how the name was entered in bug #14682. I understand it, and I found his real name by the email