Re: [Koha-devel] Spine Label Wrapping in 2.2.x

It was only officially committed to the dev_week branch: http://cvs.savannah.gnu.org/viewvc/koha/C4/Labels.pm?view=log&root=koha&pathrev=dev_week sub split_lccn {} and perhaps related use in the script(s). But yes, it was working there, and was ported to a couple of 2.2 installations. Ping me fo

[Koha-devel] Spine Label Wrapping in 2.2.x

Hi all, Can anyone confirm or deny that the labels code in Koha 2.2.x had a decent, working algorithm for wrapping the text on spine labels? A quick look at the code seems to indicate that the text was just wrapped at 14 columns without consideration of where that might fall in the text. Kind Re

Re: [Koha-devel] patches & bugs.koha.org

Hi Paul - On Wed, Jul 30, 2008 at 8:54 AM, Paul POULAIN <[EMAIL PROTECTED]> wrote: >> It does sometimes seem like a long process, especially compared to a >> small patch. Could we make it easier by making bugzilla accept entries >> via email? > > mmm... maybe a good way to do so. I'll follow up o

Re: [Koha-devel] patches & bugs.koha.org

Andrew Moore a écrit : >> For at least 2 reasons : >> - it is an obviously "long" process to add a bug. If we have found a >> small & quickly fixed bug, then there is no need to add a bug imo. >> Having a complete patch comment is necessary for the ppl >> reviewing/validating the patch. But the nee

Re: [Koha-devel] patches & bugs.koha.org

Andrew Moore a écrit : > On Wed, Jul 30, 2008 at 8:32 AM, Paul POULAIN <[EMAIL PROTECTED]> wrote: >> Everybody is against me it seems, so I think i'll accept & change my mind... > > I apologize, Paul. I was specifically trying to avoid having you feel that > way. You will see that our mails have

Re: [Koha-devel] patches & bugs.koha.org

On Wed, Jul 30, 2008 at 8:32 AM, Paul POULAIN <[EMAIL PROTECTED]> wrote: > Everybody is against me it seems, so I think i'll accept & change my mind... I apologize, Paul. I was specifically trying to avoid having you feel that way. -Andy ___ Koha-devel

Re: [Koha-devel] patches & bugs.koha.org

Galen Charlton a écrit : > But we don't get the benefit of your wisdom if the bug description and > history is locked away in your internal bugs database. :) LibLime > also has an internal bugs database, but that's mostly for truly > internal stuff; We too. But you must know that sometimes a cust

Re: [Koha-devel] patches & bugs.koha.org

On Wed, Jul 30, 2008 at 7:03 AM, Paul POULAIN <[EMAIL PROTECTED]> wrote: > I fully agree with the idea of pointing the bug if there is one. But I > strongly disagree about adding a bug if there is none. Hi Paul - Thanks for the feedback. I'm glad you're on board with putting bug numbers in the gi

Re: [Koha-devel] Good Bye

Hi Dorian, On Wed, Jul 30, 2008 at 5:28 AM, Dorian Meid <[EMAIL PROTECTED]> wrote: > After long time silence from me I finally have to cease my comittment > for Koha. > Our small library has been taken over and also did I quit my honorary > position as a librarian and sysadmin there. > The new lea

Re: [Koha-devel] patches & bugs.koha.org

Hi On Wed, Jul 30, 2008 at 7:03 AM, Paul POULAIN <[EMAIL PROTECTED]> wrote: > For at least 2 reasons : > - it is an obviously "long" process to add a bug. If we have found a > small & quickly fixed bug, then there is no need to add a bug imo. Small bug = quick description, therefore less time to

Re: [Koha-devel] patches & bugs.koha.org

> Comments welcomed It's a good rule because it helps RM to validate, test and apply patches. But not only. There is another advantage: it helps identifying already submitted bugs and comments/solution. It avoid investigating bugs already solved. I have an example... Yesterday, someone on ko

[Koha-devel] patches & bugs.koha.org

Hello world, I see a change in the wiki : " Contributors to Koha are encouraged to reference a bug number with every commit. This helps us determine the purpose of the commit and establishes a more searchable and understandable history. If there is no bug open at [[http://bugs.koha.org|bugs.koh

[Koha-devel] Good Bye

After long time silence from me I finally have to cease my comittment for Koha. Our small library has been taken over and also did I quit my honorary position as a librarian and sysadmin there. The new leadership has declared that they are not willing to continue using Koha which makes me sad

Re: [Koha-devel] [Koha-patches] [PATCH] BUG-2393: ENHANCEMENT: SearchMember() uses "cardnumber%" wildcard - if other search-types fail

Joe Atzberger a écrit : > > On Fri, Jul 25, 2008 at 1:57 AM, paul POULAIN > <[EMAIL PROTECTED] > wrote: > > Please note that the SQL "LIMIT" pragma is mySQL specific. So it > must be avoided. > > > Paul, I'm not sure what gave you that impression. Mayb

Re: [Koha-devel] About macles.pl

Henri-Damien LAURENT a écrit : > Zeno Tajoli a écrit : >> Hi to all, >> >> checking the staff translation I have found a connection to the >> script ../cataloguing/value_builder/macles.pl. >> >> For me is not clea the use of the plugin for cataloguing. >> Is 'MACLES' a name for a specif type of ke

Re: [Koha-devel] Is aqorderdelivery table of any use?

Ryan Higgins a écrit : > > The table is not used anywhere in any code that we've been running. > No objections here. same opinion for me, except we may reintroduce is later, to handle partial recieves. atm, when you have ordered 5 similar items, if you recieve 3, you note 3. Then you recieve 2,

Re: [Koha-devel] RFC 3.2 : Item status bulk change

Jesse Weaver a écrit : > I think the reason for this is because virtualshelves were never > intended to refer to specific items, merely bibs, since they were used > as simple collections for the public and staff's use. If we make > something like what you want, it should probably be entirely sep

[Koha-devel] Image-Magick replaced with GD

Hi all, Just a quick heads up to developers that in line with the proposed solution to bug 2404, Image-Magick has been removed as a dependency and replaced by GD. Please bear this in mind if you're running off of a 3.0 Git repo as you may need to install these dependencies prior to upgrading to av