Field UI: no way to set the translatable property

Looks fine to me. And we need a UI for the feature to be user-tested.

That description looks a bit overly technical to me. Please work with the UX team to come up with something that conveys the same thing but uses a bit more plain language.

Also, both solely English and multilingual sites see this checkbox. Is that intended?

Cool. I know the UX team is going to smack me for asking for such a long description, but honestly there's a fair amount of stuff here to convey.

One thing that would make this slightly better in both the breaking-up-the-descripton standpoint as well as clarity-of-what-you're-choosing-here standpoint is making this choice two radio buttons rather than a checkbox. It's not obvious that "Language neutral" is the opposite of "Translatable" and I think explicitly making them two choices will help usability quite a bit.

I switched around the apostrophe style on that description and don't trust myself to commit it blindly, so just uploading it for testing bot.

Oh, I'm good. ;P

Committed to HEAD. :)

I am totally not following the reasoning behind, making this a two radios as opposed to one checkbox. Couldn't we find a more fitting label for the checbox? Sure there is a fair bit to explain, so why not explain one thing? I am really worried that choosing radio's here, is going to motivate the behavior that its good to explain underlaying defaults - when the user really doesn't need to know.

I don't see any reason, why a user would need to understand that a certain value is "neutral" ? Obviously when I don't want to translate it- I know it won't be translated in other languages then?

Actually, I think the User Interface can be a lot easier by defaulting to Translatable, and only providing a checkbox with the Language Neutral option.

text mockup:
---

[ ] Language neutral
Fields can have different values for each available language. If this field will contain data that is language-neutral, such as an users first name check this field. If this contains data that is not language languge neutral, such as a news body, don't check this field. If this field is checked, All availble languages will have the same value for this field.

---

naturally, this text can be improved upon.

The bottom line is this UI needs more thought, especially given that we immediately smash people directly in the face with it when creating any type of field.

Tagging as something to focus on prior to UX freeze.

I like alexanderpas idea of making the field translatable by default. Although the majority of people probably aren't going to be messing about with translations, the fact that it can't be changed means they should only have to take action/give it thought if they _don't_ want it translated, ever.

Alternative copy "Fields, such as an article's body, can be translated into one or more languages with configuration. Some fields should not be translated, e.g. a user's first name."

Change 'Multilingual settings' to 'This field can be translated into other languages'

Change 'Language neutral field' to have a checkbox and text 'Never translate this field'

A small attempt to change smashing into stroking. Before and after pics: