https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37472
--- Comment #6 from Katrin Fischer <[email protected]> --- Hi Matt, first of all: thanks for taking this on! I have tried to understand how this will work from the test plan, but I am not sure I got it completely right yet. I assume that the idea is to not copy the template files to a de-DE directory, but handle all the translations on the fly. Is this correct? In that case I am not sure why an install translation step for plugins would be needed, as I assume they would come with all available languages po files as part of their source. What is achieved by installing a language for a plugin? Ideally I think if a language has been installed for staff or OPAC these translations should be made automatically available when the plugin is installed without requiring additional steps from server side. I am also not sure what is meant here: 13. We’ve proven the concept when installing a language with a plugin already installed, we now need to prove the reverse i.e. that installing a plugin on a system with languages already installed will update any existing language translations I suspect I am missing something big here, please bear with me :) -- You are receiving this mail because: 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/
