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 1hViqF-00025G-EJ for pgsql-translators@arkaria.postgresql.org; Tue, 28 May 2019 20:37:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hViqE-0006O0-1P for pgsql-translators@arkaria.postgresql.org; Tue, 28 May 2019 20:37:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hViqD-0006MI-J7 for pgsql-translators@lists.postgresql.org; Tue, 28 May 2019 20:37:01 +0000 Received: from mail-io1-xd44.google.com ([2607:f8b0:4864:20::d44]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hViq9-0004VC-UT for pgsql-translators@lists.postgresql.org; Tue, 28 May 2019 20:36:59 +0000 Received: by mail-io1-xd44.google.com with SMTP id n5so10775673ioc.7 for ; Tue, 28 May 2019 13:36:57 -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=FU7yr6YWR2sGGtd+3n8MEpZ3Y3Gng3CDSOEkZ6XwyFg=; b=AiWNDrhsxOooox0UKUGDfPwK83fYQyNbwcnsL5HZ61tqSN5zaZotVIkfafwWxrVZNF 1eVDFkKjnwA0UuPnd6+wdi+yns8fL718eZ3b37EE6Q65uzODI0TrFkDMuH0UTsnhc90U bTAFGoThDB952fpq5l7vvqzFuEqmHRm5PJOKAKGqMCwqs+RekSFUHHcQRqxj8dRQAV6S zWI5P9o6LpZvth956VvVag6YQeLuq3OLpoARZl0tFepbuoQdY6SAiEqBi6KL/om9Jvna woSQYYRE6w+NVqk3Z5GQPM5bUkRKP3PCUD9iSSIJeH5dh/930Zj24RpR4tDbfICTChzx U57A== 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=FU7yr6YWR2sGGtd+3n8MEpZ3Y3Gng3CDSOEkZ6XwyFg=; b=Pahz+saaaOzMeGO3CxLY1vCCIoiBL3KCsCtpTnLmaoiKO7sDyB2uOEsyyX0gBSD5iB YUZCqRP683xJ0A34pB2VqhsHvOzHP0GC9NAIUKntqXd7p8GwlISbMXQSU5JUYPlRFQjS TILqosKFiLDVTJiPS4WqRYwNg7LhPxi1y/IVKma9xUvl5gfqLBjq7pw+qFUM2v9+rX9g OEd97Vzu0bNDHQ8qIMPeJhO3jdVVYfvC7L0NlQTzm7nFjOJlNuzjMjqz//9jWchqsulV 5EaBNZrwCSVLiziWfq8oXAyHC1rXxarRdcvJLi2MCww096+8ZpBJTFm3hHvvkNm+gImP 89+Q== X-Gm-Message-State: APjAAAVC64CV8Epy3339r0mOf3kMErkkmbAQTkNwp/i/a49OKVXDFV9o h7AwW4DsdYafO5yvedawTosbqa/64U3jEhVlW+OTyk2qQEHqxJEzDCzb/ThIItjLFZ0I81vmnzZ iDNO4iYKIWu1BUXgs7K4Ofn7EYw0zTSBXurYMNmokdxWj8dj/LLPmO/iNsWv87wPgzE5Q16wKv2 e+b/VXw6UfwtT/HJ6ueWpgtQ== X-Google-Smtp-Source: APXvYqyErwTkFnLvpZey5LW+aEesqDIgECyqUXRKfY7ROjrbd0d7FYQzdBSQ+jKMle1ZRYX8Oib4QQ== X-Received: by 2002:a5d:9758:: with SMTP id c24mr15026002ioo.114.1559075816643; Tue, 28 May 2019 13:36:56 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([72.139.62.74]) by smtp.gmail.com with ESMTPSA id j185sm77491itj.3.2019.05.28.13.36.55 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 28 May 2019 13:36:56 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 2BF19120B2A; Tue, 28 May 2019 16:36:55 -0400 (-04) Date: Tue, 28 May 2019 16:36:55 -0400 From: Alvaro Herrera To: Daniel Gustafsson Cc: pgsql-translators@lists.postgresql.org Subject: Re: PostgreSQL misspellings in translations Message-ID: <20190528203655.GA25214@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <532270F8-FFC3-4831-AFB3-57110DF74E25@yesql.se> 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-28, Daniel Gustafsson wrote: > Spotted two misspellings of PostgreSQL in the translations as per the attached > patch. FTR, any translation entry prefixed with #~ corresponds to an obsolete one, that is, a string that once was a valid message in the catalog and was translated in that catalog, but isn't a valid message anymore. It would be picked up by the fuzzy matcher if the string is revived in the code, but I wouldn't normally bother trying to get a fix for it committed. If anything, I would remove all #~ entries from the catalog files once in a while ... -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services