Some strings are hard to translate, because there are HTML tags splitting the sentences into multiple parts. Use the HtmlTags filter so the sentences can be translated as a single unit instead.
Created attachment 73082 [details] [review] Bug 20442: intranet patron clubs Some strings are hard to translate, because there are HTML tags splitting the sentences into multiple parts. Use the HtmlTags filter so the sentences can be translated as a single unit instead. This is the intranet Patron clubs part. Test plan: 1) Apply patch 2) Go to Home -> Tools -> Patron clubs 3) Create a new template, edit it, a new club, edit it, etc. 4) Note the strings look correct in the page 5) Update a language po-files 6) Look through the xx-YY-staff-prog.po for the clubs pages strings and that they look correct
Created attachment 73088 [details] [review] Bug 20442: intranet catalogue Some strings are hard to translate, because there are HTML tags splitting the sentences into multiple parts. Use the HtmlTags filter so the sentences can be translated as a single unit instead. This is the intranet catalogue part. Test plan: 1) Apply patch 2) Search for a biblio 3) See the "X result(s) found for ..." that it looks correct 4) Check out the biblio detail page and MARC detail page breadcrumbs 5) Search for nonexistent biblio, check the "No results match for ..." text 6) Update a language po-files 7) Look through the xx-YY-staff-prog.po for the catalogue pages strings and that they look correct
There's more room for improvement than just these, but I don't have time to work on it right now. This is a good start at least.
Created attachment 73842 [details] [review] Bug 20442: Use more HtmlTags filter Some strings are hard to translate, because there are HTML tags splitting the sentences into multiple parts. Use the HtmlTags filter so the sentences can be translated as a single unit instead. This is the intranet catalogue part. Test plan: 1) Apply patch 2) Search for a biblio 3) See the "X result(s) found for ..." that it looks correct 4) Check out the biblio detail page and MARC detail page breadcrumbs 5) Search for nonexistent biblio, check the "No results match for ..." text 6) Update a language po-files 7) Look through the xx-YY-staff-prog.po for the catalogue pages strings and that they look correct Patch applies and functions as expected. Signed-off-by: Pasi Kallinen <pasi.kallinen@joensuu.fi> Signed-off-by: Dilan Johnpullé <dilan@calyx.net.au>
Sorry paxed patches don't apply. Can you please rebase?
Note that we also have KohaSpan using id and class. In my opinion, this should be use to allow tuning via CSS.