Hi Ævar, Ævar Arnfjörð Bjarmason wrote: > +#: wt-status.c:53 > +msgid "# Unmerged paths:" > +msgstr "" On projects that use gettext, merging these line number changes can be a royal pain. In effect, the .po files are mixing semantically meaningful text and automatically generated cruft. So my ignorant questions: . does gettext use the #: comments for anything important? . can they be suppressed when generating the .po file? . can they be easily re-added if some translation front-end needs them? > +#: git-pull.sh:124 > +msgid "Fetching tags only, you probably meant:" > +msgstr "" I noticed there are no printf formats among the shell scripting examples. Would we have to roll our own, like this? gettext 'You asked me to pull without telling me which branch you want to OP_TYPE OP_PREP, and 'branch.CURR_BRANCH.merge' in your configuration file does not tell me, either. Please try again (e.g., 'git pull <repository> <refspec>'). See git-pull(1) for details. ' | sed " s/OP_TYPE/$op_type/g s/OP_PREP/$op_prep/g s/CURR_BRANCH/$curr_branch/g " Jonathan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html