Summary: | Allow Koha plugins to have translations | ||
---|---|---|---|
Product: | Koha | Reporter: | Kyle M Hall (khall) <kyle> |
Component: | Architecture, internals, and plumbing | Assignee: | Kyle M Hall (khall) <kyle> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | magnus, martin.renvoize, michaela.sieber, tomascohen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20340 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Kyle M Hall (khall)
2016-10-24 14:16:43 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. I think this might help us: https://github.com/gflohr/Template-Plugin-Gettext http://search.cpan.org/dist/Template-Plugin-Gettext/lib/Template/Plugin/Gettext.pod 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? Anyone want to work on this at the KohaCon19 hackfest? :-) Tomas, I believe you had found a solution to this? I know translations have been enabled in various plugins. Any chance we could implement one way to do it in the Kitchen Sink plugin? |