What should we do about the i18n repo?

FUJIWARA Katsunori foozy at lares.dti.ne.jp
Mon Sep 7 05:07:53 EDT 2020

On Fri, 24 Apr 2020 09:36:14 +0900,
Augie Fackler wrote:
> [1  <multipart/alternative (7bit)>]
> [1.1  <text/plain; utf-8 (quoted-printable)>]
> We can do that, but I don’t think we even know who has access to i18n right now?

As far as I confirmed, almost all *.po files has not been changed for
translation since 2015 or so. pt_BR.po and ja.po have not been changed
for translation since 2018-05, too.

Therefore, it seems reasonable to reset access permission for NEW
i18n-repo under www.mercurial-scm.org/repo/, IMHO. And how about the
process below ?

  0. admin creates NEW i18n-repo under www.mercurial-scm.org/repo/
     without any access permission for translation coordinators

  1. translators should post the request of permission for i18n-repo
     (with SSH public key?) to devel-ML, if they were previously
     translation coordinator

     (previous) translation coordinators for each languages are listed in

     It is reasonable to assume that they can work well for
     translation, even without trial.

     Then, they will work for translation with i18n-repo instead of
     https://bitbucket.org/mg/hg-i18n/, after permitted by admin.

  2. otherwise:

     2-1. translators should contact to the coordinator for
          corresponded language, if there is already permitted
          coordinator for that language

          Translations for each languages may be managed in
          per-language repositories other than i18n-repo.

     2-2. otherwise, translators should post translation changes
          directly to devel-ML (or Phabricator)

          After some (or the first?) importing, they will become the
          NEW coordinator for that language.

          If the OLD coordinator requests permission after election of
          the NEW one, make them coordinate themselves :-)

FYI, date and summary line of the last 5 commits for each *.po files,
which have "i18n-LANG:" summary line (to omit non translation
changes), are shown below.

    ==== da
    2015-09-17: i18n-da: include translation of DEPRECATED
    2013-06-25: i18n-da: add missing format character and fix translation
    2013-06-25: i18n-da: remove extra trailing newline and fix translation
    2013-06-25: i18n-da: add missing newline
    2013-06-25: i18n-da: remove extra trailing newline
    ==== de
    2014-05-07: i18n-de: translation improvement for gpg extension
    2014-01-30: i18n-de: update many fuzzy entries and translate some simple ones
    2014-01-29: i18n-de: update po file for showing the effect of changed posplit
    2014-01-22: i18n-de: updated po file with 427d672c0e4e
    2014-01-22: i18n-de: remove locations
    ==== el
    2013-06-29: i18n-el: add missing indention for literal block
    2013-06-24: i18n-el: remove extra newline
    2013-06-23: i18n-el: remove duplicate paragraphs
    2010-06-19: i18n-el: split messages into paragraphs
    2009-12-05: i18n-el: translate Mercurial's copyright info message
    ==== fr
    2015-09-17: i18n-fr: reject translation which is missing DEPRECATED
    2013-06-25: i18n-fr: remove extra trailing newline
    2013-06-25: i18n-fr: fix malformed literal blocks
    2013-06-25: i18n-fr: remove extra empty line at end of msgtr
    2013-06-25: i18n-fr: remove duplicate paragraphs
    ==== it
    2015-09-17: i18n-it: include translation of DEPRECATED
    2013-07-25: i18n-it: do not translate rst syntax
    2013-06-25: i18n-it: remove extra trailing newlines
    2013-04-05: hg-i18n-it: minor fixes
    2011-10-26: i18n-it: fixed wrong message
    ==== ja
    2018-05-04: i18n-ja: fix block indentation
    2018-05-01: i18n-ja: synchronized with 32a75a8a5b0f
    2017-05-01: i18n-ja: synchronized with 6e0368b6e0bb
    2017-03-01: i18n-ja: synchronized with 7074589cf22a
    2016-12-31: i18n-ja: synchronized with 5f33116cd787
    ==== pt_BR
    2018-05-04: i18n-pt_BR: synchronized with 32a75a8a5b0f
    2018-01-31: i18n-pt_BR: synchronized with 373fb3f5922c
    2017-11-21: i18n-pt_BR: synchronized with cabc840ffdee
    2017-11-01: i18n-pt_BR: synchronized with cab34bda259e
    2017-07-31: i18n-pt_BR: synchronized with 850d2ec2cf6a
    ==== ro
    2015-09-17: i18n-ro: use ()s instead of [] for DEPRECATED
    2015-09-17: i18n-ro: include translation of DEPRECATED
    2011-06-08: i18n-ro: synchronized with 3c7907dc95ca
    2011-06-08: i18n-ro: outstanding changes
    2010-08-26: i18n-ro: ongoing translation
    ==== ru
    2014-10-13: i18n-ru: synchronized with 6b4dc7968bf0
    2014-08-09: i18n-ru: fix RST breakage spotted by test-gendoc
    2014-08-09: i18n-ru: undo fix buildbot breakage
    2014-08-04: i18n-ru: syncronized with 45a01832cad1
    2014-08-04: i18n-ru: sync with ad56fc55cbc3 (fuzzies)
    ==== sv
    2015-09-17: i18n-sv: select a single definition of DEPRECATED
    2013-06-25: i18n-sv: fix malformed literal block
    2012-07-28: i18n-sv: continue translating mq extension
    2012-07-28: i18n-sv: translated record extension
    2012-07-28: i18n-sv: synchronized with a09cc6aeed4a
    ==== zh_CN
    2015-09-25: i18n-zh_CN: annotate broken HG: translations
    2015-09-17: i18n-zh_CN: include translation of DEPRECATED
    2013-06-24: i18n-zh_CN: remove duplicate paragraphs
    2013-06-23: i18n-zh_CN: add missing literal blocks
    2013-06-23: i18n-zh_CN: remove duplicate paragraphs
    ==== zh_TW
    2014-05-07: i18n-zh_TW: set Language header
    2010-10-31: i18n-zh_TW: synchronize with 15ca4bfecfe3
    2010-06-19: i18n-zh_TW: split messages into paragraphs
    2009-10-25: i18n-zh_TW: synchronized with e06c940d554d
    2009-06-18: i18n-zh_TW: Traditional Chinese translation

> > On Apr 23, 2020, at 8:35 PM, Gregory Szorc <gregory.szorc at gmail.com> wrote:
> > 
> > Make www.mercurial-scm.org/repo/ <http://www.mercurial-scm.org/repo/> the canonical home?
> > 
> > On Thu, Apr 23, 2020 at 12:51 PM Augie Fackler <raf at durin42.com <mailto:raf at durin42.com>> wrote:
> > As I idly pulled the i18n repo today, I realized it's still on bitbucket. I think it's been over a year since I saw i18n traffic, so do we still need it? If so, what should we do about it?
> > 
> > Thanks,
> > Augie
> > 
> > (CC mg because it's in his account!)
> > _______________________________________________
> > Mercurial-devel mailing list
> > Mercurial-devel at mercurial-scm.org <mailto:Mercurial-devel at mercurial-scm.org>
> > https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel <https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel>
> [1.2  <text/html; utf-8 (quoted-printable)>]
> [2  <text/plain; utf-8 (base64)>]
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

[FUJIWARA Katsunori]                             foozy at lares.dti.ne.jp

More information about the Mercurial-devel mailing list