Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hR2MA-0006ul-SL for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2019 22:26:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hR2LB-0000uN-Mm for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2019 22:25:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hR2LB-0000qG-5I for pgsql-hackers@lists.postgresql.org; Wed, 15 May 2019 22:25:37 +0000 Received: from mail-qt1-x844.google.com ([2607:f8b0:4864:20::844]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hR2L8-0004RQ-55 for pgsql-hackers@lists.postgresql.org; Wed, 15 May 2019 22:25:36 +0000 Received: by mail-qt1-x844.google.com with SMTP id a39so1697871qtk.2 for ; Wed, 15 May 2019 15:25:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=LfrB1Gwy2RKPjC+ZThhxphTWkRS+dMsPb7V2A2nrgIQ=; b=IYAQ1IV1EzYhQw7ffGYLtWL/1312fFkmzmI4xaMnB4J53PiWb8DE2n1jsHrpcsB9wx rSYxzrI8xhC5oicZPuhoerrfS5VUXwZ/d5TSQK7eJMqBc/kayxW0HNDFwVse0/Vxs942 SKoZgsLf312iejggAYizOdvAOP+HPyO67QkUBW6x1GcG/gAqQG4oj18glyP2ZARA9d62 R2B5j7k5LpmEDoPnKMU9qCK7xlgsxGysDXI4PzodKsltajvIiTuAcYDwcRHS5Id6rlRf E3CpG0jXlasWt8vqekXRuWiS1uOeSd4DmZ9C8dRlHWnH3e/YtXKjSy6nX563OHOYwlgJ njAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=LfrB1Gwy2RKPjC+ZThhxphTWkRS+dMsPb7V2A2nrgIQ=; b=RXCby/OUWSLtyhIp93M7T6t1aGTBn7zTT/QTl4pEch2ncael7wrNsFUnmWhKknmeHW EqrxH5vYtnQY9wC4jWFqdBh92GwHFSkJ5uZTxl+XA5IWnoXVXZriRzmDw6xGbv7vLQjG J3FAR957ErHmb+vObvmHlEuZYw6flrTvxsutRtbpCGbVdqYjbaX+B1kJjaKqDKAIPMGP M5tFcCeXGK8hUb9UvvzPg4w9FtigTBNgNbFBYIsOYWZKxa8AodUmuq/i7atcvRz+yZDI +Kv/e6nbIhWvI9c+fgvfKnpMrjvUzSh9zqEG7+UoD8nsbOhHRzxwJYANs0xpECVL0AKV 1FwQ== X-Gm-Message-State: APjAAAWxaUumyW7saT63Uw8yDaFgJsZkNHFWqevt0Mp3vKyf9Q8Fw3R4 qlk2AZNjhEM9EmjHuv6UPy8RXtjqsGDnt57Ca6jLJ0D8QhPW7sKxtiEV2mGGkmvVkwq7fDb8eVi vQSrY+iK4NvjnnIMbMHjKPJvCA8UZKdK/MsgOZWdEqjxMrFHmT1pZqpfzTkNnNSBRCyZ396hTbT fQpdGto2wslY8odQ== X-Google-Smtp-Source: APXvYqzRu+A4VkFdQ8QnfUDyKsu+QTKKdZ+ogLDRVAHR0yQcfKrGRLFb4pTaKN0TTKGoJkdnYUYOrg== X-Received: by 2002:a0c:b04f:: with SMTP id l15mr23810712qvc.191.1557959132176; Wed, 15 May 2019 15:25:32 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id x126sm1762770qkd.34.2019.05.15.15.25.30 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 15 May 2019 15:25:31 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 038C9120C15; Wed, 15 May 2019 18:25:28 -0400 (-04) Date: Wed, 15 May 2019 18:25:28 -0400 From: Alvaro Herrera To: Tom Lane Cc: pgsql-hackers@lists.postgresql.org, pgsql-translators@lists.postgresql.org Subject: Re: more message fixes Message-ID: <20190515222528.GA23894@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <17813.1557956881@sss.pgh.pa.us> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-May-15, Tom Lane wrote: > Alvaro Herrera writes: > > Here's a bunch of message fixes in the postgres.po module. Please > > comment if anything seems amiss. > > These sorts of changes trouble me a bit from a translatability standpoint: > > - errmsg("connect = false and enabled = true are mutually exclusive options"))); > + errmsg("%s and %s are mutually exclusive options", > + "connect = false", "enabled = true"))); > > - (errmsg("CREATE_REPLICATION_SLOT ... USE_SNAPSHOT " > - "must not be called in a subtransaction"))); > + (errmsg("%s must not be called in a subtransaction", > + "CREATE_REPLICATION_SLOT ... USE_SNAPSHOT"))); > > A translator might expect the %s's to represent single words. > I think at least you'd want a translator: comment to warn about > what the insertion will be. Fair point, I can add that. (As a translator, I know I have to reference the source files more often than I would like.) :-( > + /* XXX is it okay to use %d for BlockNumber everywhere? */ > > BlockNumber should be %u, no? Yeah. It's %d in basebackup.c, hence the comment. I think technically it's okay most of the time, because it's only used to reference to block numbers in a *file*, not a relation; however, I fear it might still break in cases of a very large --with-segsize option. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services