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

Re: Update *.po with git.pot?

From
Peter Krefting <peter@softwolves.pp.se>
Date
Mar 19, 2016, 06:53 UTC
Message-ID
<alpine.DEB.2.11.1603190750550.16189@perkele.intern.softwolves.pp.se>
In-Reply-To
<CAN0XMO+8PQNXPRgROd9oVqHzTsgLo_k1yP-MLpqK5N44+1ShDQ@mail.gmail.com>
Ralf Thielow:
> Since translations are made in one commit, this commit is messed up 
> with the msgmerge update so when you look at the commit later, 
> you'll have a hard time to find out what the actual changes in 
> translations were.

You can always use something like podiff <http://man.gnu.org.ua/manpage/?1+podiff> to find the actual changes in each update.

> It will make the history of *.po-files much more readable.

Unfortunately, it also makes merging changes more difficult. I sometimes queue up bugfixes between translation runs, and having the po file be reformatted in commits I do not control means I would have to manually re-add those as there is no good merge driver than can handle that reformatting.

-- 
\\// Peter - http://www.softwolves.pp.se/
Previous: Ralf ThielowNext: Jiang Xin
Message 2 of 3 in “Update *.po with git.pot?”
  1. Ralf ThielowMar 18, 2016
  2. Peter KreftingMar 19, 2016
  3. Jiang XinMar 20, 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.