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

Re: [PATCH 4/7] Remove obsolete LONG_USAGE which breaks xgettext

From
Stefano Lattarini <stefano.lattarini@gmail.com>
Date
Jul 21, 2012, 16:26 UTC
Message-ID
<500AD82B.9010604@gmail.com>
In-Reply-To
<941f7bd695e8a14c940a5b8e4214d2773ae82557.1342884459.git.worldhello.net@gmail.com>
On 07/21/2012 05:50 PM, Jiang Xin wrote:
Show 6 quoted lines
> The obsolete LONG_USAGE variable has the following message in it:
> 
>     A'\''--B'\''--C'\''
> 
> And such complex LONG_USAGE message will breaks xgettext when extract
>
s/extract/extracting/ I think.
> l10n messages. But if remove single quotes from the message,
>

s/remove/we remove/; or, if the passive voice is not a problem, you might reformulate the sentence as follows:

   But if single quotes are removed from the message, ...
> xgettext works fine on 'git-rebase.sh'.
> 
> Since there is a mordern
>
s/mordern/modern/
> OPTIONS_SPEC variable in use in this script,
> it's safe to remove the obsolte
>
s/obsolte/obsolete/
> USAGE and LONG_USAGE variables.
> 
Regards,
  Stefano
Previous: Stefano LattariniNext: Stefano Lattarini
Message 12 of 14 in “i18n for git-am, git-rebase and git-merge”
  1. 0/7 i18n for git-am, git-rebase and git-mergeJiang Xin, Jul 21, 2012
  2. 1/7 i18n: New keywords for xgettext extraction from shJiang Xin, Jul 21, 2012
  3. 2/7 i18n: rebase: mark strings for translationJiang Xin, Jul 21, 2012
  4. 3/7 i18n: Rewrite gettext messages start with dashJiang Xin, Jul 21, 2012
  5. 4/7 Remove obsolete LONG_USAGE which breaks xgettextJiang Xin, Jul 21, 2012
  6. 5/7 i18n: am: mark more strings for translationJiang Xin, Jul 21, 2012
  7. 6/7 Remove unused and bad gettext block from git-amJiang Xin, Jul 21, 2012
  8. 7/7 i18n: merge-recursive: mark strings for translationJiang Xin, Jul 21, 2012
  9. Stefano LattariniJul 21, 2012
  10. Jiang XinJul 22, 2012
  11. Stefano LattariniJul 21, 2012
  12. Stefano LattariniJul 21, 2012
  13. Stefano LattariniJul 21, 2012
  14. Stefano LattariniJul 21, 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.