Re: [greenstone-devel] miscellaneous proposals

From Michael Dewsnip
DateTue, 22 May 2007 12:01:02 +1200
Subject Re: [greenstone-devel] miscellaneous proposals
In-Reply-To (464D4581-90807-gmx-org)
Hi Jens,
Almost all of your changes are in code that I wrote, so I guess
I'm the best person to take care of them :-)
    
well, this is because i use GenericList almost exclusively now ;-)
you did a great job with it!
  
Thanks! I think it should be used more than it is, because it replaces all the AZ* classifiers and does a much better job on Unicode data. Trouble is, it's not mentioned in the documentation.
Thanks for pointing this out; I'll try to find an alternative way
of doing this that doesn't mess up Unicode strings.
    
given the difficulty of solving this, do you think it's needed at
all? we're living quite well without.
  
Actually, I've tried to reproduce your problem (with à) and can't. Are you absolutely sure you've got the latest version? (Try cvs update -A). I improved the Unicode support (as part of adding the -sort_using_unicode_collation option) in January, and I think this might have fixed the problem.

I have committed your "partition_name_length" change into GenericList.pm, thank you.
I can see your point about the incorrect search matches, but I
don't think this is the right way to solve the problem because
you sometimes see this string when viewing the document.
    
ah, ok, forgot that. in our collections we have taken measures
against displaying "empty" texts.
  
It would be better if the plugin didn't add any text to the
document, and the C++ code displayed the "dummy text" string if
necessary when outputting the document.
    
wasn't the dummy text needed due to restrictions in mg(pp)? i mean,
wasn't this the reason to *add* that dummy text to the documents?
  
Yes, you're right, but this was a cheap fix (that has other consequences, as you've found out). Hopefully MG/MGPP will be fixed properly in the future and then the dummy text can go away, but until then I think it's best to keep the current "solution".
Good idea, I'll add this in.
    
thanks :-)
  
Again, are you sure you've got the latest version? Your suggestion doesn't match up to any existing code (now that the "ifln" stuff has been added).

All the best,

Michael
-- 
DL Consulting
Greenstone Digital Library and Digitisation Specialists
contact@dlconsulting.com
www.dlconsulting.com