Anomalie #1926
fermé
Dynamic translations should not be automatically deleted when transalatable entities are updated or removed
0%
Description
When different translatable entities use common labels, when one is updated or removed, translation are removed on all others entities.
Mis à jour par Guillaume AGNIERAY il y a 6 jours
If automatic deletion is removed, then translations should not be automatically added when transalatable entities are updated or created neither.
Mis à jour par Johan Cwiklinski il y a 6 jours
- Version cible
1.2.0supprimé
I'm not sure I entirely understand what you mean (what's an "entity"?)
But I know there are several issues on dynamic translations; the main one being it's not related at all to the initial place that requires it. Currently, we can have a same string that would require several translations depending on context (check in english is a good candidate for example).
My conclusion until now is that dynamic translations are not widely used right now; so that's not a priority :)
Just not removing/updating translations will end in a very huge table; with no way to know what is used and what is not... While I'm not against a change on that part, it won't be for next major, it would require too much work.
Mis à jour par Guillaume AGNIERAY il y a 6 jours
- Assigné à
Guillaume AGNIERAYsupprimé
Johan Cwiklinski a écrit (#note-2):
I'm not sure I entirely understand what you mean (what's an "entity"?)
To name them : Dynamic fields, Payments types, Contributions types and User statuses.
But I know there are several issues on dynamic translations; the main one being it's not related at all to the initial place that requires it. Currently, we can have a same string that would require several translations depending on context (
checkin english is a good candidate for example).
As for this particular example, in the context of payments types, bank check should be used instead of just check I think.
My conclusion until now is that dynamic translations are not widely used right now; so that's not a priority :)
Just not removing/updating translations will end in a very huge table; with no way to know what is used and what is not... While I'm not against a change on that part, it won't be for next major, it would require too much work.
:+1: I totally understand ;)
Mis à jour par Guillaume AGNIERAY il y a 5 jours
Since this is not an "anomaly" per se, but rather the way it is supposed to work at the moment, I think this issue can be rejected (I cannot set this status myself) ;)
If necessary, an "evolution" request will be opened later to improve the current implementation of dynamic translations.
Mis à jour par Johan Cwiklinski il y a 4 jours
- Copié vers Evolution #1928: Rework dynamic translations ajouté
Mis à jour par Johan Cwiklinski il y a 4 jours
- Statut changé de Nouveau à Rejeté
See #1928
Mis à jour par Johan Cwiklinski il y a 4 jours
I've opened the evolution ticket so the idea will not be lost ;)