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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, May 4, 2012 at 11:10 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> Nguyễn Thái Ngọc Duy <pclouds@xxxxxxxxx> 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
--
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


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]