From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs539839agc; Fri, 23 Oct 2009 00:00:28 -0700 (PDT) Received: by 10.224.81.81 with SMTP id w17mr5173707qak.382.1256281227539; Fri, 23 Oct 2009 00:00:27 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 36si11411162qyk.126.2009.10.23.00.00.27; Fri, 23 Oct 2009 00:00:27 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 4B9E71858291; Fri, 23 Oct 2009 03:00:27 -0400 (EDT) Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id 1741618580F5 for ; Fri, 23 Oct 2009 03:00:21 -0400 (EDT) Received: by kuovi.tilus.net (Postfix, from userid 1000) id 934536011; Fri, 23 Oct 2009 08:00:21 +0100 (BST) From: Tero Tilus To: sup-talk@rubyforge.org In-reply-to: <1254487575-sup-5468@thinkpad-ubuntu> References: <1254353101-sup-1021@thinkpad-ubuntu> <1254415145-sup-635@masanjin.net> <1254420802-sup-3742@thinkpad-ubuntu> <1254421405-sup-8083@masanjin.net> <1254442420-sup-3771@thinkpad-ubuntu> <1254487575-sup-5468@thinkpad-ubuntu> Date: Fri, 23 Oct 2009 10:00:21 +0300 Message-Id: <1256280223-sup-736@tilus.net> User-Agent: Sup/git Subject: Re: [sup-talk] i18n? X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from 's message of pe loka 02 15:52:47 +0300 2009: > Please tell me what you think. Why not default to the english strings as translation keys and fallback to key itself in case of missing translation? This has imo several advantages. You can go grep the source using what you see in sup UI (instead of first greping language yaml). Adding new strings is cumbersome with (mostly unnecessary) key indirection. Code is more readable when messages are inlined. If you change a string a check of translations is forced (there is no translation for the changed version). Most translation workflow tools expect this kind of behavior. -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk