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

Re: [PATCH] Revert diffstat back to English

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Sep 14, 2012, 11:56 UTC
Message-ID
<CACsJy8DnrrB8Fp6xhL8reUgB8-KaQ4Hb9OrEKMupaH70mUqzOw@mail.gmail.com>
In-Reply-To
<20120914001117.GA31647@sigill.intra.peff.net>
On Fri, Sep 14, 2012 at 7:11 AM, Jeff King <peff@peff.net> wrote:
Show 29 quoted lines
> On Thu, Sep 13, 2012 at 02:47:09PM -0700, Junio C Hamano wrote:
>
>> > I agree that the line is not bright. I do not know if it is worthwhile
>> > or not. I think it will solve some practical problems, but it may also
>> > introduce others.  But basically having a per-repo LANG setting (which
>> > is what the projectlang you are talking about would do) also does not
>> > seem like a solution that people will use, because they will not get any
>> > localization benefit at all.
>> >
>> > So again, I'd rather err on the side of pushing those things that are
>> > near the line into the "do not translate" side, letting people use LANG
>> > to localize the rest, and accepting that occasionally people are going
>> > to accidentally show you output in a language you don't understand. But
>> > hopefully that keeps it to "occasionally" and not "every time you send
>> > out a patch".
>>
>> I am confused asto what you really want.  In a Klingon-only project,
>> I think it is perfectly fine to localize the diffstat summary line
>> to Klingon.  It is not machine readble, and it is not personal, but
>> it is to be shared with project members, who all speak Klingon.
>>
>> Pushing more things to "do not translate" side of the line means
>> robbing the benefit of i18n from people, no?
>
> Yes. But you cannot please both sides without creating a third category,
> as you noted. If you do not translate diffstat, then Klingon-only projects are
> unhappy. If you do translate, then projects run in LANG=C will either
> get public Klingon, or the project members will turn off all translation
> and lose all benefit of i18n.

I agree with Jeff on this. And "everything in $projectlang" is just like "everything in C", the problem remains. Suppose Chinese becomes a very popular language (if it has not been so), projects with dominant Chinese people would prefer Chinese. But large enough projects will involve non-Chinese people who prefer their native non-Chinese language as UI.

I'm not pushing "do not translate" side. I just postpone it until a proper approach is found (preferably by Klingon teams who are upset about this "do not translate" patch). Supporting two non-C languages at the same time could be done (not very elegantly) by forking a process with the second language, which serves as gettext source for first process via pipes.

The problem is drawing a line between team strings and local strings without butchering git source code. We're going through sort of the same process already, separating machine-readable strings and translatable strings. Maybe we can learn something before deciding whether to add the team string class.

Show 6 quoted lines
> So for the time being, I would rather choose LANG=C as a lingua franca
> and err on the side of interoperability with other people and not
> translating. And then if and when somebody feels like putting the effort
> into doing i18n.projectlang by splitting out a third category, they are
> welcome to. I just do not see much point in doing i18n.projectlang any
> other way.
-- 
Duy
Previous: Jeff KingNext: Junio C Hamano
Message 18 of 28 in “Mixing English and a local language”
  1. 0/2 Mixing English and a local languageNguyễn Thái Ngọc Duy, Aug 25, 2012
  2. 1/2 Allow to print diffstat in English regardless current localeNguyễn Thái Ngọc Duy, Aug 25, 2012
  3. 2/2 format-patch: always print diffstat in EnglishNguyễn Thái Ngọc Duy, Aug 25, 2012
  4. Nguyen Thai Ngoc DuySep 12, 2012
  5. Junio C HamanoSep 12, 2012
  6. Jeff KingSep 13, 2012
  7. Revert diffstat back to EnglishNguyễn Thái Ngọc Duy, Sep 13, 2012
  8. Jeff KingSep 13, 2012
  9. Junio C HamanoSep 13, 2012
  10. Junio C HamanoSep 13, 2012
  11. Jeff KingSep 13, 2012
  12. Junio C HamanoSep 13, 2012
  13. Jeff KingSep 13, 2012
  14. Junio C HamanoSep 13, 2012
  15. Jeff KingSep 13, 2012
  16. Junio C HamanoSep 13, 2012
  17. Jeff KingSep 14, 2012
  18. Nguyen Thai Ngoc DuySep 14, 2012
  19. Junio C HamanoSep 14, 2012
  20. Nguyen Thai Ngoc DuySep 15, 2012
  21. Junio C HamanoSep 13, 2012
  22. Junio C HamanoSep 13, 2012
  23. Jeff KingSep 13, 2012
  24. Jeff KingSep 13, 2012
  25. Michael J GruberSep 14, 2012
  26. Nguyen Thai Ngoc DuySep 14, 2012
  27. Makefile: respect $LINGUAS variable on selecting .mo files to installNguyễn Thái Ngọc Duy, Sep 14, 2012
  28. Michael J GruberSep 14, 2012

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.