I agree that the further the limit is moved out toward the end of the rendering pipeline, the better the design. However, I think there's a deeper issue.
It seems to me that truncation is just about the worst way to deal with long titles, since titles appearing together are likely to begin similarly and differ mainly toward the end. A human would notice the pattern and perhaps abbreviate the leading words preferentially. How to apply this heuristic mechanically is an interesting problem. And we'd probably wind up needing a whole basketful of heuristics and a strategy routine to select one (or more!) based on another layer of pattern matching. Daunting. Any thoughts on how to shrink this sort of idea to the proper size? (This pie-in-the-sky-A.I. could run in batch at the system's leisure, munching on titles, noticing patterns, and adding hints to the indicated objects. Then the rendering machinery can do the Right Thing with those hints when it finds them. A well-thought-out implementation wouldn't be restricted to DSpace, either.) -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgph6zgml3Hoy.pgp
Description: PGP signature
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
