-------- Original Message -------- From: Bharat Chaudhari <openbharat@gmail.com> Sent: 29 March 2017 6:21:38 PM NZDT To: Chris Cormack <chrisc@catalyst.net.nz> Subject: Fwd: Error in Koha Dear Sir, This error occurs when trying to search any books in koha *Software error:* Can't call method "data" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 1915. For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error. Please do helpful. -- *Thanks & Best Regards,* Think Green... Keep it on the Screen... Save a Tree... Bharat M. Chaudhari, The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person. -- *Thanks & Best Regards,* Think Green... Keep it on the Screen... Save a Tree... Bharat M. Chaudhari, DSpace Enthusiasts & ALA-ALCTS Fellow, Faculty of Engineering and Technology, PDPU, Gandhinagar URL: http://library.pdpu.ac.in Office: 07923275091, Mob. 9428415401. The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hi Bharat Could you please let us know what version of Koha you are running? Chris
-------- Original Message -------- From: Bharat Chaudhari <openbharat@gmail.com> Sent: 29 March 2017 6:21:38 PM NZDT To: Chris Cormack <chrisc@catalyst.net.nz> Subject: Fwd: Error in Koha
Dear Sir,
This error occurs when trying to search any books in koha
*Software error:*
Can't call method "data" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 1915.
For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error.
Please do helpful.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari,
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari, DSpace Enthusiasts & ALA-ALCTS Fellow, Faculty of Engineering and Technology, PDPU, Gandhinagar URL: http://library.pdpu.ac.in Office: 07923275091, Mob. 9428415401.
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
now my koha version is 16.11.05.000 On Thu, Mar 30, 2017 at 12:53 AM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
Hi Bharat
Could you please let us know what version of Koha you are running?
Chris
-------- Original Message --------
From: Bharat Chaudhari <openbharat@gmail.com> Sent: 29 March 2017 6:21:38 PM NZDT To: Chris Cormack <chrisc@catalyst.net.nz> Subject: Fwd: Error in Koha
Dear Sir,
This error occurs when trying to search any books in koha
*Software error:*
Can't call method "data" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 1915.
For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error.
Please do helpful.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari,
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari, DSpace Enthusiasts & ALA-ALCTS Fellow, Faculty of Engineering and Technology, PDPU, Gandhinagar URL: http://library.pdpu.ac.in Office: 07923275091, Mob. 9428415401.
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
-- *Thanks & Best Regards,* Think Green... Keep it on the Screen... Save a Tree... Bharat M. Chaudhari, DSpace Enthusiasts & ALA-ALCTS Fellow, Faculty of Engineering and Technology, PDPU, Gandhinagar URL: http://library.pdpu.ac.in Office: 07923275091, Mob. 9428415401. The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
Hi, Monday we posted about a similar error in our koha: "Can't call method "branchname" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 1708." (we are also on 16.11.05.000, but we also saw it already on 16.11.03.000) Yours and ours could be something completely different of course... (and unfortunately we received no reaction of the list) MJ On 03/30/2017 06:58 AM, Bharat Chaudhari wrote:
now my koha version is 16.11.05.000
On Thu, Mar 30, 2017 at 12:53 AM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
Hi Bharat
Could you please let us know what version of Koha you are running?
Chris
-------- Original Message --------
From: Bharat Chaudhari <openbharat@gmail.com> Sent: 29 March 2017 6:21:38 PM NZDT To: Chris Cormack <chrisc@catalyst.net.nz> Subject: Fwd: Error in Koha
Dear Sir,
This error occurs when trying to search any books in koha
*Software error:*
Can't call method "data" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 1915.
For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error.
Please do helpful.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari,
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari, DSpace Enthusiasts & ALA-ALCTS Fellow, Faculty of Engineering and Technology, PDPU, Gandhinagar URL: http://library.pdpu.ac.in Office: 07923275091, Mob. 9428415401.
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
I haven't been able to recreate either error. I would try a full zebra rebuild Chris On 30 March 2017 7:49:56 PM NZDT, mj <lists@merit.unu.edu> wrote:
Hi,
Monday we posted about a similar error in our koha: "Can't call method "branchname" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 1708." (we are also on 16.11.05.000, but we also saw it already on 16.11.03.000)
Yours and ours could be something completely different of course... (and unfortunately we received no reaction of the list)
MJ
On 03/30/2017 06:58 AM, Bharat Chaudhari wrote:
now my koha version is 16.11.05.000
On Thu, Mar 30, 2017 at 12:53 AM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
Hi Bharat
Could you please let us know what version of Koha you are running?
Chris
-------- Original Message --------
From: Bharat Chaudhari <openbharat@gmail.com> Sent: 29 March 2017 6:21:38 PM NZDT To: Chris Cormack <chrisc@catalyst.net.nz> Subject: Fwd: Error in Koha
Dear Sir,
This error occurs when trying to search any books in koha
*Software error:*
Can't call method "data" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 1915.
For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error.
Please do helpful.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari,
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari, DSpace Enthusiasts & ALA-ALCTS Fellow, Faculty of Engineering and Technology, PDPU, Gandhinagar URL: http://library.pdpu.ac.in Office: 07923275091, Mob. 9428415401.
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hi, I do not find your message in my mailbox... This error is caused because you have one of your subfields (in one of your biblio frameworks) which is linked with the authorised value 'branches'. However one of your records has a value in this subfield that is not a branchcode defined in your system. I cannot give you more information on the record that has wrong data, but with the following SQL command you will know the subfields: select frameworkcode, tagfield, tagsubfield from marc_subfield_structure where authorised_value="branches" ; Any ideas how that could have happened? There is a problem in you data, but the application should not explode in that case, could you open a new bug report? Regards, Jonathan On Thu, 30 Mar 2017 at 03:49 mj <lists@merit.unu.edu> wrote:
Hi,
Monday we posted about a similar error in our koha: "Can't call method "branchname" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 1708." (we are also on 16.11.05.000, but we also saw it already on 16.11.03.000)
Yours and ours could be something completely different of course... (and unfortunately we received no reaction of the list)
MJ
On 03/30/2017 06:58 AM, Bharat Chaudhari wrote:
now my koha version is 16.11.05.000
On Thu, Mar 30, 2017 at 12:53 AM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
Hi Bharat
Could you please let us know what version of Koha you are running?
Chris
-------- Original Message --------
From: Bharat Chaudhari <openbharat@gmail.com> Sent: 29 March 2017 6:21:38 PM NZDT To: Chris Cormack <chrisc@catalyst.net.nz> Subject: Fwd: Error in Koha
Dear Sir,
This error occurs when trying to search any books in koha
*Software error:*
Can't call method "data" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 1915.
For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error.
Please do helpful.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari,
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari, DSpace Enthusiasts & ALA-ALCTS Fellow, Faculty of Engineering and Technology, PDPU, Gandhinagar URL: http://library.pdpu.ac.in Office: 07923275091, Mob. 9428415401.
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 <+64%204-803%202238> PO Box 11-053, Manners St, Wellington 6142, New Zealand
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Looks like it means you have one record without the biblionumber field. How did you import you records into Koha? Did you try a full reindex? On Thu, 30 Mar 2017 at 01:58 Bharat Chaudhari <openbharat@gmail.com> wrote:
now my koha version is 16.11.05.000
On Thu, Mar 30, 2017 at 12:53 AM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
Hi Bharat
Could you please let us know what version of Koha you are running?
Chris
-------- Original Message --------
From: Bharat Chaudhari <openbharat@gmail.com> Sent: 29 March 2017 6:21:38 PM NZDT To: Chris Cormack <chrisc@catalyst.net.nz> Subject: Fwd: Error in Koha
Dear Sir,
This error occurs when trying to search any books in koha
*Software error:*
Can't call method "data" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 1915.
For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error.
Please do helpful.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari,
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari, DSpace Enthusiasts & ALA-ALCTS Fellow, Faculty of Engineering and Technology, PDPU, Gandhinagar URL: http://library.pdpu.ac.in Office: 07923275091, Mob. 9428415401.
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 <+64%204-803%202238> PO Box 11-053, Manners St, Wellington 6142, New Zealand
-- *Thanks & Best Regards,*
Think Green... Keep it on the Screen... Save a Tree...
Bharat M. Chaudhari, DSpace Enthusiasts & ALA-ALCTS Fellow, Faculty of Engineering and Technology, PDPU, Gandhinagar URL: http://library.pdpu.ac.in Office: 07923275091, Mob. 9428415401.
The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hi 1. Over the last years I have collected quite a lot of misspellings in (the German translation of) Koha. What will I have to do to correct these misspellings so that they are gone in the next version? 2. Also I have found some places where maybe some text could be added, for example system preference "EnhancedMessagingPreferences" could need an indication to the very useful script "borrowers-force-messaging-defaults". Is it possible to add this myself (where?) or will I have to talk to someone? 3. In the German translation i found that sometimes certain terms are exchanged for each other. For example in English there is * the Koha menu "Administration > Patron categories" * there you can add patron categories * these are part of a certain patron type But in German * the menu is called "Administration > Benutzertypen" (patron categories in English) * there you can add "Kategorien" (patron category in English * these are part of a certain "Typ" (patron type in English) So the terms are exchanged here which is confusing. Especially because in the form where you can add a new patron category, the type is called "Kategorie" and the category is ALSO called "category". So here it is not just a misspelling but a mess. But probably a change has to be discussed because these variations may not only (falsely) be used in the Koha client but also in the manual. To whom will I have to talk about such a problem? Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch
Hi Michel and all, Il 31/03/2017 11:04, Michael Kuhn ha scritto:
1. Over the last years I have collected quite a lot of misspellings in (the German translation of) Koha. What will I have to do to correct these misspellings so that they are gone in the next version?
you can start here: http://translate.koha-community.org/de/ and coordinate the changes with kfischer (Katrin Fisher). Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.tajoli@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)
Hi Michael Misspellings and other issues in translations can have several reasons. - Real misspellings in Pootle. They can be fixed directly on translate.koha-community.org , e.g. for de-DE or de-CH - Inconsistencies in vocabulary (like the one you mention with the German translation of categories). - Wrong syntax because of sentence splitting by html tags in the template files. I tried to fix a couple of them to make translation smoother (Do a search after 'translatability' in Bug tracker) . I'm quite sure there are more such sentence splittings and other template issues to fix. They will have to go through the bug cycle (file a bug, fix it, get a sign-off, QA...) - Ambiguous words (same word in English - several meanings in translations). A related bug is: Bug 11285 - Vocabulary disambiguation You write that you have collected quite a lot of misspellings. It would be interesting to have a list of your findings. Can you file a bug with your list? We can then figure out how to fix (Pootle, changes to templates...), and use this bug as umbrella. PS: As you probably know I'm helping with the German translation, and back in 2012 I initiated the German translation with Swiss orthography (mainly for school libraries). The work flow for the Swiss version depends on the German version. If you have questions, feel free to get in touch directly. Kind regards Marc Véron Koha Support Schweiz www.koha-support.ch marc veron ag informatik information internet Baslerstrasse 50, 4123 Allschwil, Switzerland Am 31.03.2017 um 11:04 schrieb Michael Kuhn:
Hi
1. Over the last years I have collected quite a lot of misspellings in (the German translation of) Koha. What will I have to do to correct these misspellings so that they are gone in the next version?
2. Also I have found some places where maybe some text could be added, for example system preference "EnhancedMessagingPreferences" could need an indication to the very useful script "borrowers-force-messaging-defaults". Is it possible to add this myself (where?) or will I have to talk to someone?
3. In the German translation i found that sometimes certain terms are exchanged for each other. For example in English there is
* the Koha menu "Administration > Patron categories" * there you can add patron categories * these are part of a certain patron type
But in German
* the menu is called "Administration > Benutzertypen" (patron categories in English) * there you can add "Kategorien" (patron category in English * these are part of a certain "Typ" (patron type in English)
So the terms are exchanged here which is confusing. Especially because in the form where you can add a new patron category, the type is called "Kategorie" and the category is ALSO called "category". So here it is not just a misspelling but a mess. But probably a change has to be discussed because these variations may not only (falsely) be used in the Koha client but also in the manual. To whom will I have to talk about such a problem?
Best wishes: Michael
Hi Marc
Misspellings and other issues in translations can have several reasons.
- Real misspellings in Pootle. They can be fixed directly on translate.koha-community.org , e.g. for de-DE or de-CH
Today I have made corrections for the tests of about 20 Koha system preferences in the german translation. Since this is a quite tiresome process I decided to continue later.
- Inconsistencies in vocabulary (like the one you mention with the German translation of categories).
- Wrong syntax because of sentence splitting by html tags in the template files. I tried to fix a couple of them to make translation smoother (Do a search after 'translatability' in Bug tracker) . I'm quite sure there are more such sentence splittings and other template issues to fix. They will have to go through the bug cycle (file a bug, fix it, get a sign-off, QA...)
- Ambiguous words (same word in English - several meanings in translations). A related bug is: Bug 11285 - Vocabulary disambiguation
I had already contact with Katrin Fischer about these subjects. It doesn't seem like there could be a true solution to such inbred translation problems - so I will just live with them and be happy to at least correct some misspellings. To me it seems the problem is not the translation but the techniques that are used to inject the various languages. Since these cannot be changed in the near future it makes no sense to me to invest too much time.
You write that you have collected quite a lot of misspellings. It would be interesting to have a list of your findings. Can you file a bug with your list? We can then figure out how to fix (Pootle, changes to templates...), and use this bug as umbrella.
I have just corrected them in the German translation (de-DE).
PS: As you probably know I'm helping with the German translation, and back in 2012 I initiated the German translation with Swiss orthography (mainly for school libraries). The work flow for the Swiss version depends on the German version. If you have questions, feel free to get in touch directly.
So I hope the my corrections will kind of "automatically" find their way into the Swiss German (de-CH) translation. Though, so far I'm not using or promoting this translation. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch
Hi Michael Since there is no list available of misspellings you found in German (de-DE), I will take time to 'automatically' create a new version for de-CH after your changes to the de-DE translation. Please let me know when you have finished your corrections. If you see some odds due to sentence splitting or ambiguous words, please let the Koha community know by filing a Bug. That would be helpful not only for the German translations, but for all translations rsp. translators who spend a lot of their often voluntary time to adapt Koha to their languages. Kind regards Marc Am 04.04.2017 um 19:31 schrieb Michael Kuhn:
Hi Marc
Misspellings and other issues in translations can have several reasons.
- Real misspellings in Pootle. They can be fixed directly on translate.koha-community.org , e.g. for de-DE or de-CH
Today I have made corrections for the tests of about 20 Koha system preferences in the german translation. Since this is a quite tiresome process I decided to continue later.
- Inconsistencies in vocabulary (like the one you mention with the German translation of categories).
- Wrong syntax because of sentence splitting by html tags in the template files. I tried to fix a couple of them to make translation smoother (Do a search after 'translatability' in Bug tracker) . I'm quite sure there are more such sentence splittings and other template issues to fix. They will have to go through the bug cycle (file a bug, fix it, get a sign-off, QA...)
- Ambiguous words (same word in English - several meanings in translations). A related bug is: Bug 11285 - Vocabulary disambiguation
I had already contact with Katrin Fischer about these subjects. It doesn't seem like there could be a true solution to such inbred translation problems - so I will just live with them and be happy to at least correct some misspellings.
To me it seems the problem is not the translation but the techniques that are used to inject the various languages. Since these cannot be changed in the near future it makes no sense to me to invest too much time.
You write that you have collected quite a lot of misspellings. It would be interesting to have a list of your findings. Can you file a bug with your list? We can then figure out how to fix (Pootle, changes to templates...), and use this bug as umbrella.
I have just corrected them in the German translation (de-DE).
PS: As you probably know I'm helping with the German translation, and back in 2012 I initiated the German translation with Swiss orthography (mainly for school libraries). The work flow for the Swiss version depends on the German version. If you have questions, feel free to get in touch directly.
So I hope the my corrections will kind of "automatically" find their way into the Swiss German (de-CH) translation. Though, so far I'm not using or promoting this translation.
Best wishes: Michael
Hi Marc
Since there is no list available of misspellings you found in German (de-DE), I will take time to 'automatically' create a new version for de-CH after your changes to the de-DE translation. Please let me know when you have finished your corrections.
Well I made some kind of list for myself in my private wiki, so maybe this will help you. But the list was made with noone else in mind to use it (it also seems quite time consuming to first make a list, then correct all these mistakes one by one). However, yes, I will correct more misspellings when I find the time, and I'll let you know when I'm finished.
If you see some odds due to sentence splitting or ambiguous words, please let the Koha community know by filing a Bug. That would be helpful not only for the German translations, but for all translations rsp. translators who spend a lot of their often voluntary time to adapt Koha to their languages.
I wouldn't know where to begin... time is sparse. Also it is quite tiresome to describe problems I found in the German translation that are there because of some inert problems in the text display. Maybe when I'm finished correcting the misspellings I will file such a bug, but I won't promise anything. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch Menü "Administration > Globale Systemparameter > Administration" * <b>ERLEDIGT: Eigenschaft "delimiter":</b> In der Auswahl "umgekehrten Schrägstichen (Backslashes)" anstatt "umgekehrten Schrägstrichen (Backslashes)" * admin.pref#delimiter# backslashes Menü "Administration > Globale Systemparameter > Katalogisierung" * <b>ERLEDIGT: Parameter "AcquisitionDetails":</b> Schreibfehler: "Diensoberfläche" statt "Dienstoberfläche" * cataloguing.pref#AcquisitionDetails# Don't display * <b>ERLEDIGT: Parameter "SubfieldsToAllowForRestrictedEditing":</b> "Unerfelder" statt "Unterfelder" * cataloguing.pref#SubfieldsToAllowForRestrictedEditing# If the pref is empty, no fields are restricted. Menü "Administration > Globale Systemparameter > Ausleihe" == * <b>VORSCHLAG: Parameter "ManInvInNoissuesCharge":</b> statt "noissuescharge-Parameter"; besser fände ich: für den Parameter "noissuescharge") * <b>ERLEDIGT: Parameter "UseBranchTransferLimits":</b> Schreibfehler: "Tansport- und Rückgaberegeln" (statt "Transport- und Rückgaberegeln") * <b>ERLEDIGT: Parameter "CircAutoPrintQuickSlip":</b> Schreibfehler: "der Kurzquittungsdruck anstoßen" (statt "der Kurzquittungsdruck angestoßen") * <b>ERLEDIGT: Parameter "CircAutoPrintQuickSlip":</b> Schreibfehler: "der Quittungsdruck anstoßen" (statt "der Quittungsdruck angestoßen") * <b>ERLEDIGT: Parameter "ExportRemoveFields":</b> Schreibfehler "Die Folgenden Felder" (statt: "Die folgenden Felder") * <b>ERLEDIGT: Parameter "UpdateTotalIssuesOnCirc":</b> Gemeint ist wohl, dass die Aktivierung zu einer signifikanten Erhöhung der Serverlast führt... * <b>ERLEDIGT: Parameter "RefundLostOnReturnControl":</b> Schreibfehler: "Exemplare" (statt "Exemplar") * <b>ERLEDIGT: Parameter "AllowHoldsOnDamagedItems":</b> Schreibfehler: "vornehmen oder ausführen." (statt: "vorzunehmen oder auszuführen.") Menü "Administration > Globale Systemparameter > Benutzer" == * <b>ERLEDIGT: Eigenschaft "AutoEmailPrimaryAddress":</b> Verwende <<die erste gültige E-Mail-Adresse>> E-Mail-Adresse eines Benutzers für den Versand von Benachrichtigungen. // Es müsste heissen: Verwende <<die erste gültige E-Mail-Adresse>> eines Benutzers für den Versand von Benachrichtigungen. * <b>ERLEDIGT: Parameter "autoMemberNum":</b> Wieso Generierung - besser: Erzeugung / Wieso so eine idiotisch lange Nummer als Beispiel? Schreibfehler: vewendete Menü "Administration > Globale Systemparameter > OPAC" * <b>ERLEDIGT: Parameter "AnonSuggestions":</b> Schreibfehler: Erlaube nicht, das (statt "dass") * <b>ERLEDIGT: Parameter "DisplayOPACiconsXSLT":</b> Schreibfehler: Datailansicht * <b>ERLEDIGT: Parameter "hidelostitems":</b> Schreibfehler: verlorenen (statt "verlorene") * <b>ERLEDIGT: Parameter "GoogleIndicTransliteration":</b> Parametername bleibt wohl, aber das Ding heisst inzwischen "Google transliteration" (siehe https://en.wikipedia.org/wiki/Google_transliteration) * <b>ERLEDIGT: Parameter "OpacHiddenItems":</b> Schreibfehler: definiet (statt "definiert") Menü "Administration > Globale Systemparameter > Zeitschriften" * <b>ERLEDIGT: Parameter "SubscriptionDuplicateDroppedInput":</b> Schreibfehler: "dublizieren eines Abonnments" (statt "Duplizieren eines Abonnements")
Looks like it means you have one record without the biblionumber field. Browsing my database using phpmyadmin, looking at items.biblionumber
How did you import you records into Koha? This is a long running koha install, the data was imported many years ago by biblibre, and these issues have started only recently. (biggest recent change was update from 3.16 to 16.11.03.000 in sept 2016, and
Hi Jonathan, hi list, Answers inline: On 03/30/2017 05:59 PM, Jonathan Druart wrote: they all appear to have one. (should I be looking at items.biblionumber??) then on to 16.11.05.000 recently)
Did you try a full reindex? Yep, results in some errors as well:
retrieving biblio 7711 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. .error retrieving biblio 7712 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. 7701............................................................................7801.....................error retrieving biblio 7849 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. 7901............................................................................error retrieving biblio 8004 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. .error retrieving biblio 8005 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. .error retrieving biblio 8006 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. .error retrieving biblio 8007 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. ..................error retrieving biblio 8025 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. .error retrieving biblio 8026 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. 8001............................................................................8101......error retrieving biblio 8134 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. ................................................................................8201................................................................................ Records exported: 8271 and:
So, i tried searching our database for items.biblionumber = 7711 or 7712 or 8006... all results: EMPTY. I am searching in the wrong place (items.biblionumber) or is the zebra-reindex choking on non-exsisting records? You asked for:
mysql> SELECT DISTINCT(branchcode) FROM branches -> ; +------------+ | branchcode | +------------+ | OURBR | +------------+ 1 row in set (0.00 sec)
And this is right: we have only one branch, called OURBR. Then looking at items.homebranch and items.holdingbranch: every one of our 8472 items seems to have this defined correctly: "OURBR" (are there other fields to check, besides items.homebranch and items.holdingbranch?) So this seems to becoming more and more of a mystery? Really hoping for some more suggestions... Best regards, MJ
Anyone with an idea..? On 1-4-2017 11:58, mj wrote:
Hi Jonathan, hi list,
Answers inline:
Looks like it means you have one record without the biblionumber field. Browsing my database using phpmyadmin, looking at items.biblionumber
On 03/30/2017 05:59 PM, Jonathan Druart wrote: they all appear to have one. (should I be looking at items.biblionumber??)
How did you import you records into Koha? This is a long running koha install, the data was imported many years ago by biblibre, and these issues have started only recently. (biggest recent change was update from 3.16 to 16.11.03.000 in sept 2016, and then on to 16.11.05.000 recently)
Did you try a full reindex? Yep, results in some errors as well:
retrieving biblio 7711 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. .error retrieving biblio 7712 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. 7701............................................................................7801.....................error retrieving biblio 7849 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. 7901............................................................................error retrieving biblio 8004 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. .error retrieving biblio 8005 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. .error retrieving biblio 8006 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. .error retrieving biblio 8007 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. ..................error retrieving biblio 8025 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. .error retrieving biblio 8026 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. 8001............................................................................8101......error retrieving biblio 8134 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. ................................................................................8201................................................................................
Records exported: 8271 and:
So, i tried searching our database for items.biblionumber = 7711 or 7712 or 8006... all results: EMPTY.
I am searching in the wrong place (items.biblionumber) or is the zebra-reindex choking on non-exsisting records?
You asked for:
mysql> SELECT DISTINCT(branchcode) FROM branches -> ; +------------+ | branchcode | +------------+ | OURBR | +------------+ 1 row in set (0.00 sec)
And this is right: we have only one branch, called OURBR.
Then looking at items.homebranch and items.holdingbranch: every one of our 8472 items seems to have this defined correctly: "OURBR" (are there other fields to check, besides items.homebranch and items.holdingbranch?)
So this seems to becoming more and more of a mystery?
Really hoping for some more suggestions...
Best regards, MJ _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hello, You should contact directly your support provider if you have one, or used to have one. I was talking about MARC field, not DB Field. Re-read my answer with thinking MARC field instead of DB field. Regards, Jonathan On Sat, 1 Apr 2017 at 06:58 mj <lists@merit.unu.edu> wrote:
Hi Jonathan, hi list,
Answers inline:
Looks like it means you have one record without the biblionumber field. Browsing my database using phpmyadmin, looking at items.biblionumber
On 03/30/2017 05:59 PM, Jonathan Druart wrote: they all appear to have one. (should I be looking at items.biblionumber??)
How did you import you records into Koha? This is a long running koha install, the data was imported many years ago by biblibre, and these issues have started only recently. (biggest recent change was update from 3.16 to 16.11.03.000 in sept 2016, and then on to 16.11.05.000 recently)
Did you try a full reindex? Yep, results in some errors as well:
retrieving biblio 7711 at /usr/share/koha/bin/migration_tools/ rebuild_zebra.pl line 668. .error retrieving biblio 7712 at /usr/share/koha/bin/migration_tools/ rebuild_zebra.pl line 668.
7701............................................................................7801.....................error retrieving biblio 7849 at /usr/share/koha/bin/migration_tools/ rebuild_zebra.pl line 668.
7901............................................................................error retrieving biblio 8004 at /usr/share/koha/bin/migration_tools/ rebuild_zebra.pl line 668.
.error retrieving biblio 8005 at /usr/share/koha/bin/migration_tools/ rebuild_zebra.pl line 668. .error retrieving biblio 8006 at /usr/share/koha/bin/migration_tools/ rebuild_zebra.pl line 668. .error retrieving biblio 8007 at /usr/share/koha/bin/migration_tools/ rebuild_zebra.pl line 668. ..................error retrieving biblio 8025 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 668. .error retrieving biblio 8026 at /usr/share/koha/bin/migration_tools/ rebuild_zebra.pl line 668.
8001............................................................................8101......error retrieving biblio 8134 at /usr/share/koha/bin/migration_tools/ rebuild_zebra.pl line 668.
................................................................................8201................................................................................
Records exported: 8271 and:
So, i tried searching our database for items.biblionumber = 7711 or 7712 or 8006... all results: EMPTY.
I am searching in the wrong place (items.biblionumber) or is the zebra-reindex choking on non-exsisting records?
You asked for:
mysql> SELECT DISTINCT(branchcode) FROM branches -> ; +------------+ | branchcode | +------------+ | OURBR | +------------+ 1 row in set (0.00 sec)
And this is right: we have only one branch, called OURBR.
Then looking at items.homebranch and items.holdingbranch: every one of our 8472 items seems to have this defined correctly: "OURBR" (are there other fields to check, besides items.homebranch and items.holdingbranch?)
So this seems to becoming more and more of a mystery?
Really hoping for some more suggestions...
Best regards, MJ _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hi all, For the archives: our problem was solved with the help of biblibre: we disabled XSLT for the opac. Hopefully this solution will help someone in a similar situation. MJ On 04/03/2017 02:24 PM, Jonathan Druart wrote:
Hello,
You should contact directly your support provider if you have one, or used to have one. I was talking about MARC field, not DB Field. Re-read my answer with thinking MARC field instead of DB field.
Regards, Jonathan
AFAIK The non-XSLT view has been deprecated. -----Oorspronkelijk bericht----- Van: Koha [mailto:koha-bounces@lists.katipo.co.nz] Namens mj Verzonden: woensdag 5 april 2017 18:56 Aan: koha@lists.katipo.co.nz Onderwerp: Re: [Koha] Fwd: Error in Koha Hi all, For the archives: our problem was solved with the help of biblibre: we disabled XSLT for the opac. Hopefully this solution will help someone in a similar situation. MJ On 04/03/2017 02:24 PM, Jonathan Druart wrote:
Hello,
You should contact directly your support provider if you have one, or used to have one. I was talking about MARC field, not DB Field. Re-read my answer with thinking MARC field instead of DB field.
Regards, Jonathan
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hoi Marcel, Yes, we were told that as well, by biblibre. This is something we need to look into. However: it also seems to XSLT bits are not going to be actually removed, in the short term future. But the heads-up is appreciated. :-) MJ On 6-4-2017 8:30, Marcel de Rooy wrote:
AFAIK The non-XSLT view has been deprecated.
-----Oorspronkelijk bericht----- Van: Koha [mailto:koha-bounces@lists.katipo.co.nz] Namens mj Verzonden: woensdag 5 april 2017 18:56 Aan: koha@lists.katipo.co.nz Onderwerp: Re: [Koha] Fwd: Error in Koha
Hi all,
For the archives: our problem was solved with the help of biblibre: we disabled XSLT for the opac.
Hopefully this solution will help someone in a similar situation.
MJ
On 04/03/2017 02:24 PM, Jonathan Druart wrote:
Hello,
You should contact directly your support provider if you have one, or used to have one. I was talking about MARC field, not DB Field. Re-read my answer with thinking MARC field instead of DB field.
Regards, Jonathan
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
participants (9)
-
Bharat Chaudhari -
Chris Cormack -
Jonathan Druart -
lists -
Marc Véron -
Marcel de Rooy -
Michael Kuhn -
mj
-
Tajoli Zeno