Re: [PATCH on ab/i18n] branch: remove lego in i18n tracking info strings

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: May 6, 2012, 13:06 UTC
Message-ID: <CACsJy8Axy3Vaqqd3D4Az-wUO6dS+jGgVLARz0TnURQ2KNYnmog@mail.gmail.com>
In-Reply-To: <7vr4v0apwe.fsf@alter.siamese.dyndns.org>

On Fri, May 4, 2012 at 11:10 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

> Nguyễn Thái Ngọc Duy <pclouds@gmail.com> writes:
>
>> Pseudo html tags to to mark color, like
>>  "On branch <color1>%s</color1>" is probably not a bad idea.
>
> The output machinery needs to understand _some_ color mark-up if the
> destination does not support ANSI colors natively, and there already is
> such a code in compat/ for windows IIRC.  Adding yet another color mark-up
> wouldn't help anybody.  I would suggest to just declare that internally we
> use ANSI colors as the standard color mark-up and be done with it.

Ævar started a new thread about this and I elaborated a little bit there [1]. We cannot just put straight ANSI colors in the string because they are customizable. We don't know what color to put in the string at compile time. So we need an intermediate color representation for translators anyway to avoid fragmented strings. The problem is which way is better, "On branch %s%s%s", "On branch <color>%s</color>" or some other ways

[1] http://thread.gmane.org/gmane.comp.version-control.git/196869/focus=196908

-- 
Duy