Issue Bug Closed

#14920Irritating field name "l18n_parent"

Thomas Keller 08/11/05, 17:15 updated 08/22/05, 15:20

Description

If a new module including new tables with i18n support is created, these tables
get a new field “l18n_parent” which determines the parental relationship of a translated field to the original field.
However, this field is named wrong, it should either be “l10n_parent“ (“localisation parent”) or “i18n_parent“ (“internationalisation parent”) but not a mixture of both (“l18n_parent”). I first thought the “l” was a big “I” which looks equally with sans-serif fonts and wondered why my SQL didn’t work…

(issue imported from #M1368)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.