[mb-style] MultipleTitleStyle with similar classical pieces

[MLL]

Michelle . a écrit :
> From:  /Leiv Helleb?p;lt;leivhe at broadpark.no>/
>  >mll wrote:
>  >>
>  >>Looks fine to me, too. I'd prefer avoiding ampersands, i.e. always
>  >>commas.
>  >
>  >Any good reasons to stray further from original release title other
>  >than your personal preference?

None. But
1. I remember MB decided that we definitely make up our own classical 
release titles when the original is inaccurate / uncomplete
2. we should have a common guideline, be it with or without ampersands
3. my preference is without ampersand, so that the rule is simpler to 
remember (always commas be there 2, 3 or more symphonies) and apply 
(correcting titles where 1 or more numbers lack).

>  >
>  >>Except that for the sake of happy searching, as someone said, I'd
>  >>prefer the
>  >>singular, so:
>  >>
>  >>'Symphony No. 4, No. 7 / "King Stephen" Overture'
>  >>and in the other example
>  >>'Symphony No. 91, No. 92 "Oxford" / Scena di Berenice'
>  >>
>  >
>  >1) Using the singular is illogical when there are two.
> 
> I was also going to criticise this, but I found that a few releases (I 
> googled "Symphony No. 1 and no.") on Amazon use this. I think it'd be 
> fine if it's common practice on releases (does anyone know? I only found 
> a few examples, and grammatically the plural would be correct), but 
> having a completely different notation for track names for the sake of a 
> search function is illogical. The search function would need 
> modification, not the track names.

I'd say it's not illogical, but gramatically incorrect. Logic is why I 
support not according to the plural.

Even on the field of grammar, you could escape gracefully by saying the 
comma symbolises a repetition of the previous term, ie:
'Symphony No. 91, No. 92' = 'Symphony No. 91, Symphony No. 92' :)

> 
> 
>  >2) As for searching, I guess what you really need is software which
>  >provides regular expression searches. Searching for "Symph.* 4"
>  >would return both English and German releases.
> 
> Agreed.

I was speaking of MB's website search. No regexp searchs as of today 
AFAIK. Moreover, regexp search is not non-geek friendly.

The reason was this point: searching for 'Symphony No. 91' would return 
both 'Symphony No. 91' and 'Symphony No. 91, No. 92 "Oxford"'.
Now, on second thought, I realize that this dream breaks apart because a 
search for 'Symphony No. 92' would not return 'Symphony No. 91, No. 92 
"Oxford"'.
So yes, I think regexp is the unavoidable evil. :) But is it planned on 
this infamous yet clunky lucene engine ?

MLL

> 
> Michelle (dirtyboots)