From owner-freebsd-translators@freebsd.org Wed Feb 24 04:07:30 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 B5EA0AB0C9C for ; Wed, 24 Feb 2016 04:07:30 +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 8800519AD for ; Wed, 24 Feb 2016 04:07:27 +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 u1O47JI1098150 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 23 Feb 2016 21:07:19 -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 u1O47J09098119 for ; Tue, 23 Feb 2016 21:07:19 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Tue, 23 Feb 2016 21:07:19 -0700 (MST) From: Warren Block To: freebsd-translators@FreeBSD.org Subject: How to handle fuzzy translations Message-ID: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 23 Feb 2016 21:07:19 -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 04:07:30 -0000 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. We have options in how these fuzzy translations are handled. Fuzzy translations could be always used when present. The build system could show a warning when "make tran" is run, or even refuse to build if fuzzy translations are present. Any preferences or suggestions?