Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1olCil-0007D5-6U for pgsql-translators@arkaria.postgresql.org; Wed, 19 Oct 2022 17:19:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1olCij-0006v5-Vk for pgsql-translators@arkaria.postgresql.org; Wed, 19 Oct 2022 17:19:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1olCij-0006ux-Py for pgsql-translators@lists.postgresql.org; Wed, 19 Oct 2022 17:19:09 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1olCig-0008FU-S0 for pgsql-translators@postgresql.org; Wed, 19 Oct 2022 17:19:08 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 456165C00E8; Wed, 19 Oct 2022 13:19:06 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 19 Oct 2022 13:19:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1666199946; x=1666286346; bh=h 1OJhDadEkOEy/4pJ29ntnoFPO8FMfelQSveDFtZJU8=; b=HinpxMBmR5VvkwtMX WeUlXkhVUFYvfFvNe/WCdfmyOoObvyLZQCsQE4L4mzu8moZzd6vCF8EIdTFpjNGx 6SYG1mVrJbTKwSV3nIzJg8TcHbcFE18meg9DRk9o9W/ZxuG8p1M4qYAZEATet2YL 9XnYdyqAipqCWaFnmbs63ABOs8A98Bw4CD3+uY+YD5q/8+tGC03/TXFxRl7ob3gM OF2/UjfnT1IRkpdtdGosx5z+y8+Q8zMCC9p2nkJrUWjTGDS+h3t8qCVLXFkcM82H jw4fizvs7n2keAOwg9csaw1oN97wMbdwtmS5oZOZlyVpSIRJNmD1W0OPM/5VWhdU rQ52Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeelgedgudduudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhv rghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorh hgqeenucggtffrrghtthgvrhhnpedvkedtffduffdtffffheffhfejjefhgfeiueeukeej keffgfdufffhudffffeuveenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtoh hmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghl vhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 19 Oct 2022 13:19:05 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 95BCA70; Wed, 19 Oct 2022 19:19:03 +0200 (CEST) Date: Wed, 19 Oct 2022 19:19:03 +0200 From: Alvaro Herrera To: Justin Pryzby Cc: pgsql-translators@postgresql.org Subject: Re: translation typos spanish Message-ID: <20221019171903.kdoqioh6ewnhj2ou@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20221017202809.GX7745@telsasoft.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2022-Oct-17, Justin Pryzby wrote: > Como proyecto mientras aprendido español, he buscado para errores... > > tieneline => timeline > pg_read_all settings => pg_read_all_settings > remanentde => remanente > particionaiento => particionamiento > nomre => nombre > identificadoes => identificadores > estæ => esta > izquiero => izquierdo > coincidenete => coincidente > dedujeron => deducieron ?? > > Hay palabras que están faltando de acentos: > replicacion > restriccion > combinacion > > Hay pocos palabras inglés que no estan traducido: > > object => objeto > schema => esquema > arguments => argumentos > and => y ¡Gracias! He corregido todos estos errores (y unos pocos más que he visto mientras los buscaba), aunque sólo en la rama master, que aún necesita bastante trabajo más de traducción. Me pregunto si habrá alguna herramienta estilo 'ispell' para archivos .po ... > distinguished name => nombre distinguido I'm unsure about translating this term, as the message would become more obscure, whereas keeping it like this helps somebody who knows the LDAP terminology. I see some other catalogs use the term without translation probably for that reason: msgid "invalid LDAP URL \"%s\": missing distinguished name\n" msgstr "ungültige LDAP-URL »%s«: Distinguished Name fehlt\n" msgid "invalid LDAP URL \"%s\": missing distinguished name\n" msgstr "URL LDAP « %s » invalide : le « distinguished name » manque\n" msgid "invalid LDAP URL \"%s\": missing distinguished name\n" msgstr "URL LDAP \"%s\" non corretta: distinguished name non trovato\n" (Funny all those different quoting styles. I do wish French used non-breaking spaces between the quote sign and the quoted contend ...) > También, tal vez "tokens" debe ser "testigo" (tambien en otras fichas .po): > > src/backend/po/es.po-msgid "cannot create restricted tokens on this platform: error code %lu" > src/backend/po/es.po:msgstr "no se pueden crear tokens restrigidos en esta plataforma: código de error %lu" Unsure about this one also. Some languages keep "restricted" without translation, others keep "token", and Turkish does this msgid "could not create restricted token: error code %lu" msgstr "kısıtlı andaç (restricted token) oluşturulamadı: hata kodu %lu" I think for such a fringe message, it's not worth trying to explain the term too much ... but we have the word "token" in a bunch other messages, so perhaps it's worth uniforming and clarifying. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "Escucha y olvidarás; ve y recordarás; haz y entenderás" (Confucio)