Talk:Style/Titles/Part numbers

From MusicBrainz Wiki
< Talk:Style
Revision as of 23:30, 15 March 2009 by Gecks (talk | contribs) (response)
Jump to navigationJump to search

I have releases where the first part of the track series has no part number, despite a second part existing. In this case I think we should leave that numberless, as it could be considered the 'original' or 'main' version of the song. --Gecks

Q: What if a track "Some Trackname (Pt. 1)" is featured with the said title on a compilation? Should it stick to the formatting as it were in sequence with the other parts of the series, e.g. "Some Trackname, Part 1"? I'm in favor of applying PartNumberStyle to all track names which have some notation of Pt, Pts and other variants. --Keschte

A: I believe that's the thing to do - I think tracks that intentionally have these abbreviations (for whatever reason) are a rare occurrence. --Gecks

Q: Should stuff not be added to TrackTitles in parentheses, like in TrackAttributesStyle and RemixStyle?

A: As long as it is consistent, use the format the artist uses. Parts are almost always shown with a preceding comma on tracklistings, rather than track attributes (e.g. mix names). Also, we consider PartNumbers to be more a part of the title than ExtraTitleInformation, they are special.

Yet another question :) What about tracks which combine different parts where every part has a name? See for example Angra's Rebirth and its entry in Discogs (they do this in comments). Often we seem to leave those parts out as they make the title to long and the part names are often not mentioned on the cover but only in the lyrics. But on this cover for example there are part names (not with the word "Part"). Discogs does this as before, in our release entry it is not mentioned at the moment. I really think we need to adopt more style guidelines from the classical guide. --Shepard

  • I don't think this guideline should cover this really. This is just for dealing with part numbers of separate tracks. For that example I would like to see it as something like "Unholy Wars: Imperial Crown / Forgiven Return". I seem to remember that being suggested back in the StyleDude days but there doesn't seem to be anything concrete in place. Anyway it's for another page :) --Gecks

Sentence "Applies to songs that have been split across multiple tracks." should go, because it contradicts the rest of the document. Opinions? --Zout

  • For it. Or at least reformulate it. --Shepard
    • Agreed, and done. --Gecks
      • But I still disagree :( Again: the last track on only has those 3 parts so there are no other tracks that belong to this series. Also it does not say that this track can contain several parts of the series. I'd say: "If a track covers one (or several) part(s) of a work which is splitted to several parts ..." or something like that. --Shepard
        • I think with that, the title *implies* there's more parts to the series, regardless of whether they have ever been recorded or not. If not, then it's just a stylistic title and as such doesn't really come under this rule I think. Regardless, I think this is an exceptional case and I'd rather we didn't compromise the integrity of the rule that applies to 99% of cases. We can't cover every eventuality really. --Gecks
          • A stylistic title would not come under the rule? So I should write it like it's on the cover? That would be very inconsistent. Another example: - see: it's not an exceptional case. And not an eventuality. --Shepard
            • If you can think of a way to incorporate this into the guideline without confusing things then be my guest. Personally, I can't, and I'd like to go with a simple (hah!) set of rules to cover most things, and let common sense prevail over the rest. --Gecks

What about when separate parts are labelled not as numbers, but as letters on the sleeve? Do we use "Part X", "X)", or "part x", or some variant? "Daydream Nation" --ArtySmokes

  • As per SeriesNumberStyle, any alternative numbering scheme is fine. Please DeleteWhenCooked --Gecks
    • Any recommendation on the case of the lettering? I believe it to be lower-case on the Sonic Youth sleeve. --ArtySmokes
      • it's uppercase on mine so i guess it should stay like that unless there's an inconsistancy, in which case i'd probably favour lowercase as it's more 'standard'. --Gecks

Spacing ranges

I've spaced out "1-3" into "1 - 3" in the single example using a range. This works, sortof, for parts using arabic numbering. However, it breaks on just about anything else:

However, this breaks on anything but that one numbering scheme, or at least, makes the result more comfusing to read / invalid grammar syntax:

Train to Lamy Suite, Parts One-Two
Train to Lamy Suite, Parts I-II
Train to Lamy Suite, Parts A1-A2
Train to Lamy Suite, Parts I-1-I-2
Train to Lamy Suite, Parts A1a-A1b, A1c
Train to Lamy Suite, Parts I,II-III
Train to Lamy Suite, Parts Twenty-One-Twenty-Two

Contrast that with:

Train to Lamy Suite, Parts One - Two
Train to Lamy Suite, Parts I - II
Train to Lamy Suite, Parts A1 - A2
Train to Lamy Suite, Parts I-1 - I-2
Train to Lamy Suite, Parts A1a - A1b, A1c
Train to Lamy Suite, Parts I , II - III
Train to Lamy Suite, Parts Twenty-One - Twenty-Two

Especially in cases 4, 6, and 7 above, it makes the output more comprehensible. In cases 1 and 7, it makes the grammar valid. In case 2, it makes the Roman numeral range valid. Additionally, we already space & - we use "1 & 2", not "1&2". Why should ranges be any different? - @SIG

-It is the only correct way to do normal numbering - I can see an argument that it breaks "I-1 - I-2", but not for non-arabic numbers in genera? And in any case, why make it wrong/unintuitive for arabic numbers (used in 99% of cases) just to protect these edge-cases?

-I also don't think the new examples table is necessary as examples are given in the section above. I don't think anyone really has any trouble with how to use this style! --Gecks 23:30, 15 March 2009 (UTC)

-(and how the hell do you indent in this new wiki? of course, the help page doesn't work any more :P)