git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 03/21] i18n: advice: internationalize message for conflicts

From
Vasco Almeida <vascomalmeida@sapo.pt>
Date
May 18, 2016, 21:00 UTC
Message-ID
<573CD7EC.9060606@sapo.pt>
In-Reply-To
<CAPig+cTgQmJG5a8dNjkYcNPG_vEHycyi19sHkO_yO-EfFQzy5A@mail.gmail.com>
Às 19:24 de 18-05-2016, Eric Sunshine escreveu:
Show 33 quoted lines
> On Wed, May 18, 2016 at 11:27 AM, Vasco Almeida <vascomalmeida@sapo.pt> wrote:
>> Mark message for translation telling the user she has conflicts to
>> resolve. Expose each particular use case, in order to enable translating
>> entire sentences which would facilitate translating into other
>> languages.
>>
>> Change "Pull" to lowercase to match other messages.
>>
>> Signed-off-by: Vasco Almeida <vascomalmeida@sapo.pt>
>> ---
>> diff --git a/advice.c b/advice.c
>> @@ -79,7 +79,20 @@ int git_default_advice_config(const char *var, const char *value)
>>  int error_resolve_conflict(const char *me)
>>  {
>> -       error("%s is not possible because you have unmerged files.", me);
>> +       if (!strcmp(me, "cherry-pick"))
>> +               error(_("cherry-pick is not possible because you have unmerged files."));
>> +       else if (!strcmp(me, "commit"))
>> +               error(_("commit is not possible because you have unmerged files."));
>> +       else if (!strcmp(me, "merge"))
>> +               error(_("merge is not possible because you have unmerged files."));
>> +       else if (!strcmp(me, "pull"))
>> +               error(_("pull is not possible because you have unmerged files."));
>> +       else if (!strcmp(me, "revert"))
>> +               error(_("revert is not possible because you have unmerged files."));
>> +       else
>> +               error(_("%s is not possible because you have unmerged files."),
>> +                       me);
> 
> Despite the commit message, I still don't understand this change. 'me'
> is a literal git command which shouldn't be translated, so how is this
> helping?
> 

I saw it as an operation that could be translated, not necessary a git command - just happens to be so. Now that you mention, I can see this patch doesn't had much value from that point of view.

On the other hand, I can translate the sentence, including the command name. Something I couldn't before and I would likely do it to be consistent with other translations I've done and also because, as a user, I would like to read the entire sentence in my language.

I have few experience in i18n and l10n, but often I realize I'm making assumptions about other languages that are not true. Some translations, say Chinese or Bulgarian that have their own writing systems, might translate that command word to something to their writing. Others might agglutinate the command word with some suffix. I can't say for sure because I don't know those languages, but it's possible.

Maybe the first paragraph can give you a better understanding of the issue: http://www.gnu.org/software/gettext/manual/html_node/Names.html

Previous: Eric SunshineNext: Junio C Hamano
Message 6 of 42 in “i18n and tests updates”
  1. 00/21 i18n and tests updatesVasco Almeida, May 18, 2016
  2. 01/21 i18n: builtin/remote.c: fix mark for translationVasco Almeida, May 18, 2016
  3. 02/21 i18n: advice: mark string about detached head for translationVasco Almeida, May 18, 2016
  4. 03/21 i18n: advice: internationalize message for conflictsVasco Almeida, May 18, 2016
  5. Eric SunshineMay 18, 2016
  6. Vasco AlmeidaMay 18, 2016
  7. Junio C HamanoMay 18, 2016
  8. 04/21 i18n: transport: mark strings for translationVasco Almeida, May 18, 2016
  9. 05/21 i18n: sequencer: mark entire sentences for translationVasco Almeida, May 18, 2016
  10. Eric SunshineMay 18, 2016
  11. Vasco AlmeidaMay 18, 2016
  12. Ævar Arnfjörð BjarmasonMay 21, 2016
  13. Junio C HamanoMay 23, 2016
  14. Eric SunshineMay 23, 2016
  15. 06/21 i18n: sequencer: mark string for translationVasco Almeida, May 18, 2016
  16. 07/21 i18n: merge-octopus: mark messages for translationVasco Almeida, May 18, 2016
  17. 08/21 merge-octupus: use die shell function from git-sh-setup.shVasco Almeida, May 18, 2016
  18. 09/21 i18n: rebase: fix marked string to use eval_gettext variantVasco Almeida, May 18, 2016
  19. 10/21 i18n: rebase: mark placeholder for translationVasco Almeida, May 18, 2016
  20. 11/21 i18n: bisect: simplify error message for i18nVasco Almeida, May 18, 2016
  21. 12/21 t6030: update to use test_i18ncmpVasco Almeida, May 18, 2016
  22. 13/21 i18n: git-sh-setup.sh: mark strings for translationVasco Almeida, May 18, 2016
  23. 14/21 i18n: rebase-interactive: mark strings for translationVasco Almeida, May 18, 2016
  24. Eric SunshineMay 19, 2016
  25. Ævar Arnfjörð BjarmasonMay 21, 2016
  26. Vasco AlmeidaMay 21, 2016
  27. 15/21 i18n: rebase-interactive: mark here-doc strings for translationVasco Almeida, May 18, 2016
  28. 16/21 i18n: rebase-interactive: mark comments of squash for translationVasco Almeida, May 18, 2016
  29. 17/21 tests: use test_i18n* functions to suppress false positivesVasco Almeida, May 18, 2016
  30. 18/21 tests: unpack-trees: update to use test_i18n* functionsVasco Almeida, May 18, 2016
  31. 19/21 t9003: become resilient to GETTEXT_POISONVasco Almeida, May 18, 2016
  32. Eric SunshineMay 19, 2016
  33. Vasco AlmeidaMay 19, 2016
  34. Eric SunshineMay 20, 2016
  35. Junio C HamanoMay 20, 2016
  36. Eric SunshineMay 20, 2016
  37. Vasco AlmeidaMay 20, 2016
  38. Junio C HamanoMay 20, 2016
  39. Junio C HamanoMay 20, 2016
  40. Vasco AlmeidaMay 20, 2016
  41. 20/21 t4153: fix negated test_i18ngrep callVasco Almeida, May 18, 2016
  42. 21/21 t5523: use test_i18ngrep for negationVasco Almeida, May 18, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.