https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24975
--- Comment #123 from Julian Maurice <[email protected]> --- Re-reading all comments and patches after a year and a half... the end result doesn't look easier to use that what we currently have in master: db_t('itemtype', $itemtype->{translation_key}) I can't precisely tell what is wrong with this, but it's definitely harder to read than: $itemtype->translated_description I think this is because at first, I tried to fit the gettext (POT/PO files) model into database, and then it evolved to use a (primary) key as "source string" instead of the original string, trying to fit this in a system not really designed for it. So I tried another approach. Since it appear we want to use the primary key as the "matching point" between an object and its localizations, I tried storing itemtypes localizations in a dedicated `itemtypes_localizations` table and see how much I could generalize it to make it easy to localize other tables data. I will submit the result soon in a new bug report. It's not finished but I need to get feedback in order to continue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
