Hi Susie, It seems like this is an issue only if they don't enter their contact information in a Latin language, yes? So an English or French speaker wouldn't need to enter their contact information twice? Only CJK?
My take would be to initially present only one block of fields for contact information. If this is a web app, then Google's language API allows for AJAX detection of language on the fly. So as they type, you could determine in what language they're typing and only show the "Latin" contact block if necessary, either expanded inline or on the next page. If you need to persistently show both blocks of contact input at once for some reason, then consider labeling the section headers for each block, not the fields themselves as local or latin. Again, if you can tell which language they're using, you could lable accordingly. If they enter their first block of contact information in CJK, is there a question about which Latin language they'd use for the 2nd block? Wouldn't the language used for the rest of the site influence their decision? // jeff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=29055 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
