Le 12/04/2016 11:52, Duy Nguyen a écrit :
>
> Ex-translator speaking. Context is important. If it's me, I would even
> go as far as marking the whole line translatable just to give more
> context (it's mostly just copy and translate a few words then). But
> then again, I was half developer half tra
On Mon, Apr 11, 2016 at 5:43 PM, Vasco Almeida wrote:
>>> @@ -458,13 +458,13 @@ static void NORETURN die_no_merge_candidates(const
>>> char *repo, const char **refs
>>> fprintf_ln(stderr, _("Please specify which branch you
>>> want to merge with."));
>>> fprintf
Às 18:01 de 10-04-2016, Junio C Hamano escreveu:
> Vasco Almeida writes:
>
>> Some translations might also translate "" and "".
>
> This offers an interesting observation that I didn't think of while
> reviewing the first round of this series.
>
> Do translations want to translate "remote" and
Vasco Almeida writes:
> Some translations might also translate "" and "".
This offers an interesting observation that I didn't think of while
reviewing the first round of this series.
Do translations want to translate "remote" and "branch" without the
""? Or is it better to allow translations
Some translations might also translate "" and "".
Signed-off-by: Vasco Almeida
---
builtin/pull.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/builtin/pull.c b/builtin/pull.c
index 10eff03..9e8883c 100644
--- a/builtin/pull.c
+++ b/builtin/pull.c
@@ -458,13 +458,13 @
5 matches
Mail list logo
