On 10/28/2016 06:20 PM, Kevin Bullock wrote:
On Oct 28, 2016, at 03:58, Pierre-Yves David <pierre-yves.da...@ens-lyon.org>
wrote:
On 10/26/2016 10:10 PM, Kevin Bullock wrote:
On Oct 26, 2016, at 15:05, Augie Fackler <r...@durin42.com> wrote:
On Oct 26, 2016, at 15:03, timeless <timel...@gmail.com> wrote:
Augie Fackler wrote:
+ hint = _('(hg rename %s to replace the file by '
+ 'recording a rename)\n') % flags
+ hint = _('(hg copy %s to replace the file by '
+ 'recording a copy)\n') % flags
+ hint = _('(hg rename --after to record the rename)\n')
+ hint = _('(hg copy --after to record the copy)\n')
I know it's too late, but do we want to include backticks around the
part that's a command?
Otherwise it's hard for people (and translators, and people reading
translations) to figure out what to do...
If that's something we normally do, can you prep a patch to mail early in the
4.1 cycle? (This is just a hint, so we can change the hint text safely.)
Changes to hint text should be fine during a freeze. No need to wait until
November.
I can't remember what the exact policy have been in the past, but doesn't this
change the translated string impacting the translator work during the freeze
window ?
I'm not totally clear on what our approach to translations during a freeze is
either. I'm going by the freeze rules on the wiki, and the fact that
translation always happens on stable anyway, both of which lead me to believe
it should be okay?
Last time this was discussed seems to be:
<http://markmail.org/message/uka2mhpamqyvfsub>
Okay, I don't have a too strong opinion on this and I trust you will
take the right decision. Worse case will have user or translator
(hopefully) complaining and we'll adjust.
Cheers,
--
Pierre-Yves David
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
