From owner-freebsd-translators@freebsd.org Wed Feb 24 19:41:01 2016 Return-Path: Delivered-To: freebsd-translators@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71A72AB2E2D for ; Wed, 24 Feb 2016 19:41:01 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 439EB1A84 for ; Wed, 24 Feb 2016 19:41:01 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u1OJf0Kt036810 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 24 Feb 2016 12:41:00 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u1OJf0SQ036807 for ; Wed, 24 Feb 2016 12:41:00 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 24 Feb 2016 12:41:00 -0700 (MST) From: Warren Block To: freebsd-translators@FreeBSD.org Subject: Re: How to handle fuzzy translations In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Wed, 24 Feb 2016 12:41:00 -0700 (MST) X-BeenThere: freebsd-translators@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Translators List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Feb 2016 19:41:01 -0000 On Tue, 23 Feb 2016, Warren Block wrote: > A couple of recent PO files have had a few "fuzzy" translations. These can > be suggestions of close strings that the PO editor thinks might work as > translations of the English original string. In practice, I think they are > usually not very good matches. > > Currently, fuzzy translations are ignored and the English string is used > instead in the translated document. The concern is that, at present, the only way these English strings will be noticed is by looking at the generated translated document. There are no warnings or notices shown during the translation process.