http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7695 Priority: P5 - low Change sponsored?: --- Bug ID: 7695 Assignee: frederic@tamil.fr Summary: Boolean operator AND in XSLT gets translated QA Contact: koha.sekjal@gmail.com Severity: normal Classification: Unclassified OS: All Reporter: magnus@enger.priv.no Hardware: All Status: NEW Version: master Component: I18N/L10N Product: Koha * Problem In koha-tmpl/opac-tmpl/prog/en/xslt/MARC21slim2OPACDetail.xsl (and the corresponding XSLT for the intranet) this: 476 <xsl:with-param name="delimeter"> and </xsl:with-param> gets translated into this, for nb-NO: 476 <xsl:with-param name="delimeter"> og </xsl:with-param> ("og" being Norwegian for "and"), resulting in searches like this, when TraceSubjectSubdivisions is set to "include": (su,complete-subfield:"USA ") og (su,complete-subfield:"Borgerkrigen, 1861-1865") Zebra does not know how to handle "og" as a boolean operator, of course, resulting in zero hits. In the OPAC this can currently be avoided by not translating the string "and ", since this is the only occurrence of that string (but there is one occurrence of "and"), but in the intranet there are three occurrences of "and ", and only one of them is a boolean operator, so you can't just not translate the one place where it is. * One possible solution Since the translation process is case sensitive, but Zebra is not, it might be a way out to change "and" into "AND" in the line above, to make it stand out from the cases where "and" occurs as a regular word. Then we would "just" have to remember not to translate "AND", but just copy it over. Does anyone have a better idea? -- You are receiving this mail because: You are watching all bug changes.