Re: [PATCH] Proposal: Improvements to PDF stylesheet and table column widths

2025-06-11 Thread Noboru Saito
Dear Kuroda-san, 2025年6月11日(水) 13:48 Hayato Kuroda (Fujitsu) : > > I have also attached a part of the PDF generated with both 0001 and > > 0002 applied for your reference. > > The patch is cleanly created, and +1 for all contents. Thank you very much for your review and for confirming the patch c

Re: [PATCH] Proposal: Improvements to PDF stylesheet and table column widths

2025-05-29 Thread Noboru Saito
Thank you Kuroda-san. > To confirm, generated pdf with current setting is left slide, and it would > become like right side, is it correct? I prefer right one. Sorry for the lack of explanation. That's right, the version on the left is the previous version, and the version on the right has the pa

Re: [PATCH] Fix tags in func.sgml

2025-05-08 Thread Noboru Saito
Thanks to all the hackers for your quick response. 2025年5月8日(木) 15:44 Daniel Gustafsson : > > > On 8 May 2025, at 08:36, Noboru Saito wrote: > > > > Hi, > > > > Previously, both "AT TIME ZONE" and "AT LOCAL" were wrapped in a > > sing

[PATCH] Fix tags in func.sgml

2025-05-07 Thread Noboru Saito
Hi, Previously, both "AT TIME ZONE" and "AT LOCAL" were wrapped in a single tag, which was incorrect. This patch separates them into two distinct tags for better semantic correctness. Please review and apply if appropriate. Noboru Saito diff --git a/doc/src/sgml/func

Re: [PATCH] Documentation: Fix minor grammatical and formatting issues

2025-04-21 Thread Noboru Saito
Rowley : > > On Mon, 21 Apr 2025 at 15:06, Noboru Saito wrote: > > 1. Remove unnecessary blank lines (blankline.diff) > > Looks good. > > > 2. Fix repeated "to to" in several command reference files (toto.diff) > > -Specifies the name of the database

[PATCH] Documentation: Fix minor grammatical and formatting issues

2025-04-20 Thread Noboru Saito
Hi PostgreSQL Hackers, I'm a member of the PostgreSQL Japanese documentation translation team. While working on translations, I've identified several minor grammatical and formatting issues in the English documentation. Please review them. 1. Remove unnecessary blank lines (blankline.diff) 2. Fix

Re: Separate the result of \watch for each query execution (psql)

2022-03-01 Thread Noboru Saito
Tom Lane : > Noboru Saito writes: > > I have created a patch that allows you to turn it on and off in \pset. > > The attached patch adds the following features. > > Formfeed can be turned on with the command line option or \pset. > > Formfeed (\f\n) is output after th

Re: Separate the result of \watch for each query execution (psql)

2022-02-27 Thread Noboru Saito
Hi, 2022年2月25日(金) 13:42 Pavel Stehule : > > > > pá 25. 2. 2022 v 5:23 odesílatel Noboru Saito napsal: >> >> Hi, >> >> Pavel Stehule : >> > > I strongly agree. It was a lot of work to find a workable solution for >> > > pspg. Spe

Re: Separate the result of \watch for each query execution (psql)

2022-02-24 Thread Noboru Saito
Hi, Pavel Stehule : > > I strongly agree. It was a lot of work to find a workable solution for > > pspg. Special chars that starting result and maybe other, that ending > > result can significantly increase robustness and can reduce code. I think > > it can be better to use form feed at the end

Re: Separate the result of \watch for each query execution (psql)

2022-02-21 Thread Noboru Saito
Thank you for your reply. 2022年2月21日(月) 14:52 Pavel Stehule : > > Hi > > po 21. 2. 2022 v 6:19 odesílatel Noboru Saito napsal: >> >> I need a way to separate the results of \watch for each query execution. >> >> There is only a blank line between the results

Separate the result of \watch for each query execution (psql)

2022-02-20 Thread Noboru Saito
I need a way to separate the results of \watch for each query execution. There is only a blank line between the results of \watch. However, there is also a blank line after the title, which complicates the rules. My suggestion is to insert a "form feed(\f)" (preferably a newline) before the resul