Hi, On Thu, Dec 27, 2012 at 11:48 AM, Frédéric Demians <frederic@tamil.fr>wrote:
As for why we use biblio-koha-indexdefs.xml to generate biblio-zebra-indexdefs.xsl, I admit I don't actually know. Galen?
So what? Galen? For my libraries, I'm inclined to tweak locally the .xsl file rather than the .xml file. Any reason no to do so?
Admittedly, it's a near thing, but biblio-koha-indexdefs.xml is more concise and expresses the *intention* of the indexes -- the XSL we're just stuck with since that's what Zebra needs. Of course, since it's XML, it's not all that more concise, but at least it admits of the possibility of creating a base index definition language in JSON or YAML that would actually be concise. My practice has always been to update the XML, then generate the XSL. YMMV, but arguably {authority,biblio}-zebra-indexdefs.xsl should be kept out of the source tree and just generated when needed. Regards, Galen -- Galen Charlton Director of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org