Sean is right that reading and writing rights in a language are tools that you need to use but prohibit the role. Access to the language recording is not needed and a problematic approach to solving the problem.
As soon as you specify the read / write language settings for a role, this role ceases to have read and write permissions in languages ββfor all other languages. This is in accordance with Sitecore's standard security security practice of removing inheritance of rights, rather than a direct waiver of rights.
So, for each role of the editor you provide language access to the corresponding language, and the role will be prohibited for editing in other languages.
It also allows a user with two separate roles, each with its own language record setting for a particular language, to have access to both languages. If you explicitly prohibited language rights to write to one of the languages, then this denial will be canceled by any explicit language that the user will correctly write.
EDIT: see Mark Ursino's comment below - this is not like Sitecore 6.5
source share