Can anyone explain {1}

[chrisrixon]

Can anyone explain the {1} that appears in strings, for example:

unread_x_nav "Unread {1}"

I looked at the code and gets fed into a sprintf so I would have thought %s or %d etc would make more sense? :ermm:

[Xenon]

well, but it'S possible that phrases have more than one variable, so {1} stands for the first parameter, {2} for the second...

[chrisrixon]

Yes I agree with that, but I don't see how sprintf knows {1} means 1st variable. I thought it expected things like %s, %d etc :nervous:

[Xenon]

ah, now i see what you mean, hmm, don't see it right now as well

oops ^^

[tehste]

ah, now i see what you mean, hmm, don't see it right now as well

oops ^^

its probably because vb developers thought {1} and {2} would make more sense to end users...

[akanevsky]

As far as I can judge, {1}, {2} etc. is just a nice and friendly user end thingy. In the $vbphrase array, these get replaced with % equivalents.

[Andreas]

build_language() converts the bracevars into the necessary %x$s stuff

[chrisrixon]

Ahhh, thanks for that. Somehow that spurred me on to complete my hack.

My hack is to make the Unread after Private messages red but only if there are unread messages:
http://www.xatquiz.com/img/unread.gif

Being a bit of a newbie is this 1 line hack worth posting and if so where is the best place?