Bug 17489 - Allow Koha plugins to have translations
Summary: Allow Koha plugins to have translations
Status: RESOLVED DUPLICATE of bug 37472
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Kyle M Hall (khall)
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-24 14:16 UTC by Kyle M Hall (khall)
Modified: 2024-08-06 20:47 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall (khall) 2016-10-24 14:16:43 UTC
We should come up with a way of allowing plugin templates to be translatable so installations using multiple languages can have the plugin displayed in the selected language.
Comment 1 Katrin Fischer 2018-02-08 07:27:52 UTC
I think this deserves more attention.

Plugins are a great way to add extra functionality to Koha, but by being non-translatable we invite forking instead of sharing and improving one version of the plugin together. I think a translation system is at this point much needed to move them further. 

I think this should be seen as a bug in the current plugin implementation even.
Comment 3 Katrin Fischer 2018-04-01 11:52:11 UTC
Hi Kyle, this looks promising! I am not sure I can figure it out myself, any chance you could spend some time on a prototype?
Comment 4 Magnus Enger 2019-04-15 11:31:36 UTC
Anyone want to work on this at the KohaCon19 hackfest? :-)
Comment 5 Katrin Fischer 2020-01-11 15:53:29 UTC
Tomas, I believe you had found a solution to this?
Comment 6 Katrin Fischer 2023-06-25 14:19:06 UTC
I know translations have been enabled in various plugins. Any chance we could implement one way to do it in the Kitchen Sink plugin?
Comment 7 Michaela Sieber 2024-08-06 20:47:25 UTC

*** This bug has been marked as a duplicate of bug 37472 ***