shipdate.warning=Your thing will ship on {0,choice,1#Sunday|2#Monday|3#Tuesday|4#Wednesday|5#Thursday|6#Friday|7#Saturday}
and then you'd pass an Integer (valued 1 through 7) in in the first token replacement position.
Joe
> >If you're talking about building a message using other keys, no. I>generally find that I am better off using a seperate key for such
>situations. The problem I run usually into is one of
syntax, especially
>with other languages. Breaking things up like that can make
it harder to
>structure a well formed sentence. Since one of my pet
peeves is messages
>that are not grammatically correct, I avoid this at all costs.
>
>Consider an English message translated into say German. IIRC there is a
>joke about a German teacher who ends every class with 5 minutes of
>verbs. Apparently German verb structure is different then
English, so how
>would fit that structure into your messages? Or Navajo, which is
>completely different from any other language?
>
>Such flexibitlity in your messages might be nice from a programming
>standpoint, but could be a major pain when translating into
foreign languages.
>
>So, my answer to your question is that I don't use message
resource keys
>as arguments to my messages. In such cases I just use a
different message
>key for each possibilty.
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
