http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10734 --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> ---
Good point. I wonder how we should handle dates like uuuu or 190u or 19uu. Maybe it makes sense just to include definite completely numeric dates? Or maybe do a label for uuuu like "Unknown" and change the u to a question mark for other cases like 190? or 19??, perhaps?
I think the second would make a bit more sense to me.
I wrote a little TT plugin a while ago to change codes into nice labels for the facets, which I think I mentioned to you, but the problem was that it had hardcoded strings :/.
Hm, not sure I remember. If the strings can be in an include or similar, we can translate them.
Is there a way of maybe using the "language_descriptions" table to use translated strings?
I think that would probably be the best option for a language facet.
We would run into the same problem with a record type facet.
I think it is solvable especially when the options and descriptions you want to have are somehow limited by the standard.
Actually...with record type...we could probably use authorized values like we have for item type and shelving location. I suppose that's not hardcoded but I suppose that probably still presents translation issues.
I always prefer template translation over using authorised values because the latter are one language only currently. -- You are receiving this mail because: You are watching all bug changes.