http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13600
--- Comment #26 from Heather <[email protected]> --- (In reply to Katrin Fischer from comment #25) > > I also like the ':' (currently it is ':' should it be ';'?) between title > > and volumne, a solution would be to make it conditional, so it only appears > > if a $v is present. > > I like the conditional and would like the ; a bit better (less likely to be > used in the title?) > > > >And, in the future, perhaps such pipes should be used as field separators > >for >other multiple field displays. > > I think the trend goes to | currently - we already have that in several > fields now. :) What I'd like to see is have them wrapped in a span with a > class. So if you don't like the |, you can easily change it. I think we have > done that in one place at least already. > > I am not sure how close we need to stick to the MARC21 standard here as we > are building a 'normal view' targetted at patrons and all library staff. I > know that the ending punctuation '.' has caused some questions here in the > past - same for the / at the end of the title. I feel like most catalogs > here don't have that, but they are mostly not MARC21 internally either. Yes--the semicolon is rarely used in titles. And your idea about the span & class would be great! I think the slash in the 245 ("/") is misapplied. Most catalogs don't have it at the end of 245 subfields because it is not terminal punctuation. It is not supposed to be at the end of a field, but is supposed to *precede* the 245 $c (statement of responsibility) only if the $c is present. So it is like this semicolon for the 4XX & 8XX $v that we are discussing--it is supposed to appear preceding a field only if the field is present. Have a slash appear as terminal punctuation is not proscribed by AACR2, AACR2R, or RDA. (RDA D.1.2.2, "Precede the first statement of responsibility by a diagonal slash. Precede each subsequent statement of responsibility by a semicolon.") --h2 -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
