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

Re: [PATCH] rebase: make warning less passive aggressive

From
Jean-Noël AVILA <jn.avila@free.fr>
Date
Feb 22, 2024, 10:01 UTC
Message-ID
<7633780.EvYhyI6sBW@cayenne>
In-Reply-To
<xmqq4je1mo5p.fsf@gitster.g>
On Wednesday, 21 February 2024 23:46:10 CET Junio C Hamano wrote:
> Jean-Noël AVILA <jn.avila@free.fr> writes:
> 
> > As a translator, I'm less bothered by editing a sentence to remove a 
question 
> > mark (maybe enforcing a language style and reformulating the sentence by 
the 
Show 12 quoted lines
> > way), than by translating again and again similar sentences.
> 
> Sure, but if the original in C locale used to be "FOO BAR?" and you
> translated it to "foo bar?" in your language, and then a patch
> updates the string in the source to "FOO BAR", doesn't msgmerge
> notice that the original as a "fuzzy" matching and offer you
> something like
> 
>     # fuzzy
>     msgid "FOO BAR"
>     msgstr "foo bar?"
> 
> so that all you have to do is to remove '?' anyway?
Yes, it works as expected.
> So I do not
> think you'd need to translate the "FOO BAR" part again and again.

Sorry for not being clear: I don't consider changing a question to an assertion is translating "again and again". This change is completely entitled to end up on translators desk, because it involves possibly changing the whole structure of the sentence.

About "again and again", I was more refering to strings such as "could not stat '%s'" and then "could not stat file '%s'".

Show 9 quoted lines
> 
> But the above assumes that for your language, the ONLY thing to turn
> such a rhetorical "passive aggressive" question into grammatically
> correct statement of a fact is to remove the question mark.  It may
> not be universally true for all languages, and for some language,
> even after msgmerge did its job correctly, you may need to do more
> than just removing the question mark to adjust the remaining "foo
> bar" part.
> 
I perfectly agree with you.
Thanks
Previous: Junio C HamanoNext: Michal Suchánek
Message 10 of 18 in “rebase: make warning less passive aggressive”
  1. rebase: make warning less passive aggressiveHarmen Stoppels via GitGitGadget, Feb 20, 2024
  2. Junio C HamanoFeb 20, 2024
  3. Michal SuchánekFeb 21, 2024
  4. Junio C HamanoFeb 21, 2024
  5. Junio C HamanoFeb 21, 2024
  6. Michal SuchánekFeb 21, 2024
  7. Jean-Noël AVILAFeb 21, 2024
  8. Junio C HamanoFeb 21, 2024
  9. Junio C HamanoFeb 22, 2024
  10. Jean-Noël AVILAFeb 22, 2024
  11. Michal SuchánekFeb 22, 2024
  12. Junio C HamanoFeb 22, 2024
  13. Patrick SteinhardtFeb 21, 2024
  14. Junio C HamanoFeb 21, 2024
  15. rebase: make warning less passive aggressiveHarmen Stoppels via GitGitGadget, Feb 21, 2024
  16. Patrick SteinhardtFeb 22, 2024
  17. Kristoffer HaugsbakkFeb 22, 2024
  18. Junio C HamanoFeb 22, 2024

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.