Core translation should be documented on po/README

Core translation should be documented on po/README

[Bagas Sanjaya]

Hello,

I had learned the following when I submitted Indonesian translation [1].

The documentation at po/README missed mentioning about "core translation",
which IMO is minimum translated messages needed to complete the translation.
So the l10n coordinator had to instructed me to complete it.

To translate core messages, I ran `po-helper.sh check id.po` first and
do the translation work on the generated po/core-id.po. Next, I merged
po/core-id.po to id.po by `msgcat`, however he didn't tell me the order of
PO files to be passed to `msgcat`, so AFAIK I `ran msgcat core-id.po id.po`
and fixed "fuzzy" errors (such as misplaced translated messages).

I think these above should be mentioned in po/README.

NOTE: po-helper.sh can be found on po-helper branch of l10n coordinator
repo. [2]

[1]: https://github.com/git-l10n/git-po/pull/500
[2]: https://github.com/git-l10n/git-po/blob/po-helper/utils/po-helper.sh

-- 
An old man doll... just what I always wanted! - Clara

Re: Core translation should be documented on po/README

[Jiang Xin]

Bagas Sanjaya <bagasdotme@gmail.com> 于2021年3月9日周二 下午7:40写道：
>
> Hello,
>
> I had learned the following when I submitted Indonesian translation [1].
>
> The documentation at po/README missed mentioning about "core translation",
> which IMO is minimum translated messages needed to complete the translation.
> So the l10n coordinator had to instructed me to complete it.

When we started l10n for git, there were only about 700 entries in
"po/git.pot", but there are over 5000 entries now for git 2.31.0.
Providing a complete translation is not a piece of cake for a new l10n
team. So, I defined a minimal l10n template based on source code for
some daily used commands, such as wt-status.c, builtin/clone.c, etc.
The first contribution of a new l10n team should cover this minimal
l10n template, which I called as "core.pot" (I'm not good at naming).

It's a good suggestion to add notes in "po/README". But without a
helper, it is hard to describe how to generate the minimal l10n
template. The personal used helper "po-helper.sh" may have bugs, and I
want to rewrite it to check author date and committer date in order to
prevent unecessarly calibrated the corrected committer date in
commit-graph.

>
> To translate core messages, I ran `po-helper.sh check id.po` first and
> do the translation work on the generated po/core-id.po. Next, I merged
> po/core-id.po to id.po by `msgcat`, however he didn't tell me the order of
> PO files to be passed to `msgcat`, so AFAIK I `ran msgcat core-id.po id.po`
> and fixed "fuzzy" errors (such as misplaced translated messages).
> I think these above should be mentioned in po/README.
>

I think the order of PO files to `msgcat` is not important, commands
are as follows:

        msgcat <input1.po> <input2.po> -s -o <output.po>
        mv <output.po>  XX.po
        msgmerge --add-location --backup=off -U XX.po  git.pot


> NOTE: po-helper.sh can be found on po-helper branch of l10n coordinator
> repo. [2]
>
> [1]: https://github.com/git-l10n/git-po/pull/500
> [2]: https://github.com/git-l10n/git-po/blob/po-helper/utils/po-helper.sh
>
> --
> An old man doll... just what I always wanted! - Clara