We are evaluating two options:
1) If we change the rsc116 component to be transliteralble, the current name will be marked as "lg-nolan" as main language, but is possible to translate the name to other languages... with "lg-spa" or "lg-eng", etc... the current data will be ok, and will be not necessary export and re-import current data to get the new "state"
2) I we change the rsc116 component to be translatable, the name of the entity will need specify the lang as: "lg-eng" or "lg-spa" (the main language of the installation and will be possible to translate to other langs) instead "lg-nolan" and will be necessary to export and re-import the current data to get the new state. The "lg-nolan" option it's not usable with translatable components.
I think that the solution is change the state of the component to be transliterable. Now, the component has marked as "lg-nolan", and it's more easy to do the change.
BUT, in the case of common names as "private collection" or "colección privada", it will be necessary to change the data from lg-nolan to "lg-eng" or "lg-spa" or the project lang, because in those cases is not an entity name, and it always need to has a language.
If we don't have other opinions about that, we will change it to be transliterable.