Re: Make prep_status() message translatable - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Make prep_status() message translatable
Date
Msg-id 5ac927ee-2327-484c-bca3-9a78eee20459@oss.nttdata.com
Whole thread Raw
In response to Re: Make prep_status() message translatable  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: Make prep_status() message translatable
List pgsql-hackers

On 2025/04/07 16:26, Fujii Masao wrote:
> 
> 
> On 2025/04/07 15:55, Kyotaro Horiguchi wrote:
>> Hello,
>>
>> The recent commit 173c97812ff made the following change:
>>
>> -    prep_status("Adding \".old\" suffix to old global/pg_control");
>> +    prep_status("Adding \".old\" suffix to old " XLOG_CONTROL_FILE);
>>
>> This change results in a message that is untranslatable, at least into
>> Japanese.  In addition, the file name should be quoted.
>>
>> The attached patch modifies the message to use %s for XLOG_CONTROL_FILE,
>> making it properly translatable.
> 
> Thanks for the report and patch!
> 
> The fix looks good to me.
> 
>          pg_log(PG_REPORT, "\n"
>                 "If you want to start the old cluster, you will need to remove\n"
>                 "the \".old\" suffix from %s/%s.old.\n"
>                 "Because \"link\" mode was used, the old cluster cannot be safely\n"
>                 "started once the new cluster has been started.",
>                 old_cluster.pgdata, XLOG_CONTROL_FILE);
> 
> Commit 173c97812ff also updated the above part of disable_old_cluster()
> and replaced the hardcoded "global/pg_control" with %s using XLOG_CONTROL_FILE.
> Maybe we should also add a translator: comment and wrap %s/%s.old in
> double quotes there?

I've updated the patch to reflect this comment.
Barring any objections, I'm thinking to commit this patch.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Attachment

pgsql-hackers by date:

Previous
From: Ajin Cherian
Date:
Subject: Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding
Next
From: shveta malik
Date:
Subject: Re: Conflict detection for update_deleted in logical replication