http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8633
--- Comment #4 from Jared Camins-Esakov <[email protected]> --- (In reply to comment #3) > > misc/translator/translate is hardcoded to translate only prog, when in > > fact it should be translating any themes included in Koha. > > For each template, we would have to create 2 .po files, one per > interface, OPAC or professional. Does it make sense to generate .po > files for intranet template other than 'prog'? Why would we want to > include a second template for intranet interface? I can't really think of any reason we would want to, to be honest. The change I made to translate the ccsr theme was to add: + ccsr => { + dir => $context->config('opachtdocs') . '/ccsr', + suffix => '-i-opac-t-ccsr-v-3006000.po', + }, in the $self->{interface} definition in new. I am not sure if that is the best way, which is why I defer to you. -- 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] http://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/
