From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-2.1 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,PDS_OTHER_BAD_TLD, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 4D7D81F4D7 for ; Fri, 6 May 2022 00:50:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1381211AbiEFAyK (ORCPT ); Thu, 5 May 2022 20:54:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54090 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233468AbiEFAyJ (ORCPT ); Thu, 5 May 2022 20:54:09 -0400 Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A23DC165BF for ; Thu, 5 May 2022 17:50:27 -0700 (PDT) Received: by mail-lf1-x12a.google.com with SMTP id x17so10117360lfa.10 for ; Thu, 05 May 2022 17:50:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0w+kbq012XrYmYU90GuN1laAHApHGoNqH/XFXoyniIM=; b=Rqh/ggsLEgL8N6LUtvKt+zpymKlBQhyuQmQ76JWCY+K0IE/NPS/pzMmnGYA6kZB8yo XgQBhl6muziPilF9G4iifpBJ3pNTHW6fkfoQsWDL3vjs1iRMDI0ZvktdSEXpKWmnZYDo 74oDhcffiI+tkeYT9HM+UiKOzaImw3J4Tm7lo2++hz6Rd9fZbyOyX2mLIpfmiiXCXjy9 8Uek1+4SRCE83TI3bNBwDqTQ5AFW63yTd1qSTq3lS2+Up+IgHXjpy7944725SGu+hjVs oLYvFuHDFyi7/H/+QsFQcYgpSgwYsAlV+pSsaDMsKsCRp3o2aSTZCFABWV8HdJeeKLpU KPlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0w+kbq012XrYmYU90GuN1laAHApHGoNqH/XFXoyniIM=; b=leJssw/zUyJWIkpKkHjj9S4Dl2BV5D/EwYdu1W0bWxVHqsRZDrXJmUmWo43RXLshEr /2IkiS9K44E3YHDmPX+A2IFfSo0EW5bKtvuGPLd1cWvou7/7wUSn9nRuOoBW2ZoZtYVu tT/srNelEhJSa8QCJQO8/S6JmpQGzn6nBKFCyx/l3BOr+HrspM5BhFkcgTemhzjB8n1F OJLrK39r4BZgJzHACXKDhgJCarqIPSjkFig3WXg6wSuHU1FnCgb0421wjPZoMytPGJYJ S9fguZqOU1hdus+QgUFvAfUwMtwvkzLbnLG+Gubx89+hEOJz6VNSEfbRR/4jK/vN/o85 TMSw== X-Gm-Message-State: AOAM5336+vN9mEKVq6gtvrDOGs+6Fnnj4a1O7MnDQ+jxoaoL/BUP3taI Ecq+YfnfOME8qukI0rnsByKjCFLP0LaVnOBDfYU= X-Google-Smtp-Source: ABdhPJzc6OrwHRxQcRvjI6tuGVWcfmuRZumJNCqn7R1klzZETiviMyX+L5SfQPTcRiUqy7t8lsoADb3lAhsTn8t78nM= X-Received: by 2002:a19:4f53:0:b0:472:1714:61f1 with SMTP id a19-20020a194f53000000b00472171461f1mr686232lfk.473.1651798225909; Thu, 05 May 2022 17:50:25 -0700 (PDT) MIME-Version: 1.0 References: <20220503132354.9567-1-worldhello.net@gmail.com> In-Reply-To: From: Jiang Xin Date: Fri, 6 May 2022 08:50:13 +0800 Message-ID: Subject: Re: [PATCH 0/9] Incremental po/git.pot update and new l10n workflow To: Daniel Santos Cc: Junio C Hamano , =?UTF-8?B?w4Z2YXIgQXJuZmrDtnLDsCBCamFybWFzb24=?= , Git List , Jiang Xin , Alexander Shopov , Jordi Mas , =?UTF-8?Q?Matthias_R=C3=BCster?= , Jimmy Angelakos , =?UTF-8?Q?Christopher_D=C3=ADaz?= , =?UTF-8?Q?Jean=2DNo=C3=ABl_Avila?= , Bagas Sanjaya , Alessandro Menti , Gwan-gyeong Mun , Arusekk , Dimitriy Ryazantcev , Peter Krefting , Emir SARI , =?UTF-8?B?VHLhuqduIE5n4buNYyBRdcOibg==?= , Fangyi Zhou , Yi-Jyun Pan Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Fri, May 6, 2022 at 6:01 AM Daniel Santos wrote: > > On Thu, May 05, 2022 at 08:20:13AM +0800, Jiang Xin wrote: > > > > A new git clone of git.git is about 150MB in size, while the "po/" > > history occupies 28MB. By removing the location line numbers, > > the size can be reduced from 28MB to 6MB. > > > > See: https://lore.kernel.org/git/20220504124121.12683-1-worldhello.net@gmail.com/ > > That is an improvement of size only for few people. On GNU/Linux > install of git by most users is done through packages, and most git > users of other OS, also will not receive this improvement. We, l10n contributors, only need to make a small setup to our local repository, and we can avoid uncontrolled growth of files under "po/", resulting in more than 50% of the Git repository capacity coming from l10n a day. See patch 9/9 or this link: * https://github.com/jiangxin/git/blob/avar/new-l10n-workflow/po/README.md?plain=1#L160-L171 > Have you considered how the removal of these lines from the po files > will affect the quality of the translation work? > For new translator, not having these lines might make them less prone > to understand po files usage in C? > And probably make them contribute less to i18n C code? The location numbers will always be there in your po/pt_PT.po. Please read: * https://github.com/jiangxin/git/blob/review/avar/po/README.md?plain=1#L133-L158 > Has these implementation upgrade better benefits than counter effects? > > It is worth discussing this. The new l10n workflow is open for discussion, see patch 9/9 or this link: * https://github.com/jiangxin/git/blob/avar/new-l10n-workflow/po/README.md?plain=1#L60-L95 -- Jiang Xin