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

Re: Fixing translation errors in gits error messages

From
Junio C Hamano <gitster@pobox.com>
Date
May 3, 2015, 17:58 UTC
Message-ID
<xmqqh9rtv8yz.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAKB+oNsa5c3zwx03pm7P_FDO3Xdxgr+rBOncAAmAjQL4LLJOdg@mail.gmail.com>
Alangi Derick <alangiderick@gmail.com> writes:
> I ran the command:
>  git grep --cached -F -e 'error("' > fix_translation.txt
> so that i can track all the files with the errors and fix them file
> after file manually.

That is a good first step to find candidates, but you have to be careful to sift that output into ones that needs marking and others. Some strings are for plumbing output that must never be translated.

Previous: Alangi DerickNext: Alangi Derick
Message 2 of 3 in “Fixing translation errors in gits error messages”
  1. Alangi DerickMay 3, 2015
  2. Junio C HamanoMay 3, 2015
  3. Alangi DerickMay 3, 2015

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.