October 2018 - Koha-bugs - lists.koha-community.org

[Bug 13098] Item lost multiple times by the same patron will create only be charged once
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '18

27 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13098 --- Comment #14 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- Created attachment 81354 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=81354&action=ed… Bug 13098: Fix POD for Koha::Account::Offsets::total Signed-off-by: Tomas Cohen Arazi <tomascohen(a)theke.io> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15650] Credit Card Payment development other than Paypal
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '18

27 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15650 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen(a)gmail.com Resolution|--- |WONTFIX Component|Circulation |Fines and fees See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=19173 Status|NEW |RESOLVED --- Comment #2 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- Bug 19173 introduced a way to have plugins implement specific payment methods. I suggest you get a plugin written for whatever payments broker you can use in your area! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 19617] New: Development - Allow partial writeoff
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '18

27 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19617 Bug ID: 19617 Summary: Development - Allow partial writeoff Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jesse(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Add “Write off selected” button -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 14208] Allow for Write of Selected
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '18

27 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14208 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tomascohen(a)gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- *** This bug has been marked as a duplicate of bug 19617 *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15395] Internationalization: plural forms, context, and more
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '18

27 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15395 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oleonard(a)myacpl.org --- Comment #123 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hm, looking at the example, it seems quite complicated and not sure I understand it. Do we really want to do that to all our strings? I feel like we should discuss this change at a general meeting if the long term goal is to change the way we write templates fundamentally outside of some cases where the extra features are useful. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15395] Internationalization: plural forms, context, and more
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '18

27 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15395 --- Comment #122 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi Julian, it's Saturday! ;) I think some best practice examples like this one from the comments would be good: [% IF count %] [% tnx('{count} item', '{count} items', count, { count = count }) %] [% ELSE %] [% t('Not a single item!') %] [% END %] Also still not sure about the "context and more" - seeing examples for that if possible would be great too. An example in German for where context would be useful is "subject". It can be an email subject, a topic subject on a bibliographic record or just the subject (topic) something talks about... and it would all be different words in German. And maybe some explanation about how this changes the translation process technically? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15395] Internationalization: plural forms, context, and more
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '18

27 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15395 --- Comment #121 from Julian Maurice <julian.maurice(a)biblibre.com> --- (In reply to Katrin Fischer from comment #120) > Hi all, > > really happy to see this one moving! Really happy too! > > Maybe time to think about a few things: > > - When is the best moment to push this to master? Should we aim to before > string freeze? In this case it would be nice to get an OK from Bernardo > before we do that. The scheduled time for translating is not very long this > time, so we should avoid issues. I think plural forms might not be set in > all our files. Some languages like Japanese don't even have proper plural. Apart from the "Example usage of I18N Template::Toolkit plugin" patch, this whole patchset won't affect existing translations at all. I'm thinking that maybe I can provide an other example in a more hidden place, so if there is problem with it at release it won't be noticed (or maybe just don't push the example, to be totally safe) > > - Does it affect performance? I see you discussed times for generating the > .po/.mo files already. What about page loads? I am not sure if I understood > the method correctly here, are we still creating translated templates or is > this more 'on the fly'? We'll have to continue to create translated templates until all translatable messages are "wrapped" (see bug 20988 which aims to do that) and translated. But once it is done we should stop, as all translations would be retrieved on the fly. So it will affect performance, but it should be negligible. I did some performance tests some time ago and noticed an increase in page load time of ~3ms for 100 strings translated in a template file. I'm currently trying to write another performance test script. I'll publish it as soon as it is finished so other people can test. > > - Can we have some dev documentation for the wiki with explanations and > examples? I can certainly do that. What kind of explanations would you expect from such documentation ? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21632] New: How to insert line break in a translation ?
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '18

27 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21632 Bug ID: 21632 Summary: How to insert line break in a translation ? Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: e.betemps(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, I would like to insert a break line in a translation because I think the sentences should be split in two paragraphs. http://translate.koha-community.org/fr/man18.05/translate/tools.po#unit=689… I tried <br/> and 'carriage return' but that gives me 'XML tag' or 'line break' critical errors. -> Am I allowed to insert line breaks in translation ? (the Quality-checks page on Pootle lets me think I can't but I'd like to be sure) -> If I am allowed, how can I do ? Emmanuel Bétemps -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 15395] Internationalization: plural forms, context, and more
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '18

27 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15395 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer(a)bsz-bw.de --- Comment #120 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi all, really happy to see this one moving! Maybe time to think about a few things: - When is the best moment to push this to master? Should we aim to before string freeze? In this case it would be nice to get an OK from Bernardo before we do that. The scheduled time for translating is not very long this time, so we should avoid issues. I think plural forms might not be set in all our files. Some languages like Japanese don't even have proper plural. - Does it affect performance? I see you discussed times for generating the .po/.mo files already. What about page loads? I am not sure if I understood the method correctly here, are we still creating translated templates or is this more 'on the fly'? - Can we have some dev documentation for the wiki with explanations and examples? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 18405] New: Self checkout: Fix broken silent printing
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '18

27 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18405 Bug ID: 18405 Summary: Self checkout: Fix broken silent printing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org Fix broken 'silent printing' (without printer dialog) in self checkout. To reproduce: Set up silent printing to slip printers as described in: https://wiki.koha-community.org/wiki/Setting_up_slip_printer_to_print_silen… Verify that it works for check-outs in staff client. Verify that it does not work in Self checkout. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11