Translating options in a custom post type dropdown field

If users are modifying the options, it’s really not going to be convenient (or easy) for them to use a simple custom defined list as they’ll have to go into Pods Admin for the field and edit the field to make changes to the options. Do you really want them doing that?

You’re better off creating either a Custom Taxonomy or another Pod just for the options in that case and creating a standard relationship to the Custom Taxonomy or Pod for that field. Then your translations should work properly. I will alert this one to our Polylang folks to see if this can be addressed as well, though.

Hi, thanks for your answer! By users I meant administrators, sorry for the confusion. They need to have the possibility to add options and translate them from the backend. I would rather use custom fields for other reasons, and I was using this plugin, which is awesome and very lightweight. But now I need Polylang compatibility, so that’s why I’m trying Pods (also awesome, but much more than I actually need). I will explore the alternatives you suggested and see if they work for me.
Thank you!