Martin Cooper wrote:
> I like the idea. I do see a couple of problems, however.
>
> * You are presumably defining the juxtaposition of the label, the colon, the
> asterisk, and the input field, in the tag itself. This, I think, would be
> rather specific to the layout you have in mind.
Yes. We have this layout:
Some Field: ________
My label tag only creates the "Some Field:", not the input box, so it
does presume it comes to the left or above. Our app. has no I18N
requirements at this point.
> * The use of a trailing colon is very much locale-dependent. In some
> languages (e.g. Finnish), the use of a trailing colon actually changes the
> meaning of the text before it. In such cases, a somewhat different layout
> may be desired.
Interesting. What does it change about the meaning of the text, just
out of curiosity?
> Certainly, neither of these is insurmountable. In fact, if they could be
> resolved in such a way that the tag supports full i18n and is still easy to
> use, this would be a very handy tag.
I'll paste the relevant code snippet in reply to the next message, and
you folks can do what you want with it. I certainly won't have the time
or knowledge to make it more generic than it already is, except to
perhaps have some indirection on what to wrap around the message (its a
<span> now, with * and style class to affect the display).
Erik
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
