Re: [mb-style] RFC-STYLE-296. remove bogus attribute work-work version TRANSLATED
On 3/1/2014 4:10 AM, Nicolás Tamargo de Eguren wrote: I think part of the problem here is that translation is currently used pretty much as some lyrics in a different language whether it's a translation or not (which IMO is a mistake) rendering it meaningless. If we did indicate actual translations with this attribute, and unrelated lyrics were just version or based on or whatever, I'd certainly be quite happier myself. Chris says we wouldn't always be able to tell - well if in doubt, don't claim it's a translation sounds reasonable and workable to me, dunno about others. +1 ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Re: [mb-style] RFC-STYLE-296. remove bogus attribute work-work version TRANSLATED
So if that means an additional line in the guidelines, saying Do only use if it really is a pretty close translation, otherwise use simply ''version of'' I could probably +1 this, too - even if I don't believe it will change much. What would the term be to use in relationships for the person that wrote the translated/adapted/different-language lyrics? On Mon, Mar 3, 2014 at 8:28 PM, Alex Mauer ha...@hawkesnest.net wrote: On 3/1/2014 4:10 AM, Nicolás Tamargo de Eguren wrote: I think part of the problem here is that translation is currently used pretty much as some lyrics in a different language whether it's a translation or not (which IMO is a mistake) rendering it meaningless. If we did indicate actual translations with this attribute, and unrelated lyrics were just version or based on or whatever, I'd certainly be quite happier myself. Chris says we wouldn't always be able to tell - well if in doubt, don't claim it's a translation sounds reasonable and workable to me, dunno about others. +1 ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Re: [mb-style] RFC-STYLE-296. remove bogus attribute work-work version TRANSLATED
On Mon, Mar 3, 2014 at 9:51 PM, SwissChris swissch...@gmail.com wrote: So if that means an additional line in the guidelines, saying Do only use if it really is a pretty close translation, otherwise use simply ''version of'' I could probably +1 this, too - even if I don't believe it will change much. What would the term be to use in relationships for the person that wrote the translated/adapted/different-language lyrics? I assume we'd use translator if it's a translation (plus the original lyricist as lyricist) and lyricist if it's not (without the original lyricist credited). ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Re: [mb-style] RFC-STYLE-296. remove bogus attribute work-work version TRANSLATED
On Mon, Mar 3, 2014 at 8:57 PM, Nicolás Tamargo de Eguren reosare...@gmail.com wrote: On Mon, Mar 3, 2014 at 9:51 PM, SwissChris swissch...@gmail.com wrote: So if that means an additional line in the guidelines, saying Do only use if it really is a pretty close translation, otherwise use simply ''version of'' I could probably +1 this, too - even if I don't believe it will change much. What would the term be to use in relationships for the person that wrote the translated/adapted/different-language lyrics? I assume we'd use translator if it's a translation (plus the original lyricist as lyricist) and lyricist if it's not (without the original lyricist credited). What do we do with all the 60s and 70s pop songs that not only (systematically) credit the original lyricist, but also give the original title in the track list, even when - according to our eventually new guidelines - the text is not a translation? http://www.encyclopedisque.fr/images/imgdb/main/92007.jpg. How should editors decide, whom should they (omit to) credit if they don't know the original (or don't speak/read the language of the original) ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Re: [mb-style] RFC-STYLE-296. remove bogus attribute work-work version TRANSLATED
On Mar 3, 2014, at 1:57 PM, Nicolás Tamargo de Eguren reosare...@gmail.com wrote: On Mon, Mar 3, 2014 at 9:51 PM, SwissChris swissch...@gmail.com wrote: So if that means an additional line in the guidelines, saying Do only use if it really is a pretty close translation, otherwise use simply ''version of'' I could probably +1 this, too – even if I don't believe it will change much. What would the term be to use in relationships for the person that wrote the translated/adapted/different-language lyrics? I assume we'd use translator if it's a translation (plus the original lyricist as lyricist) and lyricist if it's not (without the original lyricist credited). This is what irks me. Releases give credit to original lyricists because if they didn’t, said lyricist could turn around and sue for lack of credit (and accompanying royalties). It’s not fair that we act any differently; one of these days some songwriter could come and sue us for not crediting him/her properly. ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Re: [mb-style] RFC-STYLE-296. remove bogus attribute work-work version TRANSLATED
It sounds like the old mb-classic releases vs. facts. We can't (IMO) put incorrect information @ mb-work level. Right now I don't have any ideas except use the release annotation? or add extra release credits AND use the release annotation? 2014-03-03 21:44 GMT+01:00 Rachel Dwight hibiscuskazen...@gmail.com: On Mar 3, 2014, at 1:57 PM, Nicolás Tamargo de Eguren reosare...@gmail.com wrote: On Mon, Mar 3, 2014 at 9:51 PM, SwissChris swissch...@gmail.com wrote: So if that means an additional line in the guidelines, saying Do only use if it really is a pretty close translation, otherwise use simply ''version of'' I could probably +1 this, too – even if I don't believe it will change much. What would the term be to use in relationships for the person that wrote the translated/adapted/different-language lyrics? I assume we'd use translator if it's a translation (plus the original lyricist as lyricist) and lyricist if it's not (without the original lyricist credited). This is what irks me. Releases give credit to original lyricists because if they didn’t, said lyricist could turn around and sue for lack of credit (and accompanying royalties). It’s not fair that we act any differently; one of these days some songwriter could come and sue us for not crediting him/her properly. ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style -- /symphonick ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Re: [mb-style] RFC-STYLE-296. remove bogus attribute work-work version TRANSLATED
2014-03-03 21:44 GMT+01:00 Rachel Dwight hibiscuskazen...@gmail.com: On Mar 3, 2014, at 1:57 PM, Nicolás Tamargo de Eguren reosare...@gmail.com wrote: On Mon, Mar 3, 2014 at 9:51 PM, SwissChris swissch...@gmail.com wrote: So if that means an additional line in the guidelines, saying Do only use if it really is a pretty close translation, otherwise use simply ''version of'' I could probably +1 this, too - even if I don't believe it will change much. What would the term be to use in relationships for the person that wrote the translated/adapted/different-language lyrics? I assume we'd use translator if it's a translation (plus the original lyricist as lyricist) and lyricist if it's not (without the original lyricist credited). This is what irks me. Releases give credit to original lyricists because if they didn't, said lyricist could turn around and sue for lack of credit (and accompanying royalties). It's not fair that we act any differently; one of these days some songwriter could come and sue us for not crediting him/her properly. Then IMO this means we need a new AR for this. After all, those credits usually don't say that those are translations, they only tell who wrote the original lyrics. So if they don't use the word translation, why should we? -- Frederic Da Vitoria (davitof) Membre de l'April - promouvoir et défendre le logiciel libre - http://www.april.org ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Re: [mb-style] RFC-STYLE-296. remove bogus attribute work-work version TRANSLATED
2014-03-03 22:23 GMT+01:00 symphonick symphon...@gmail.com: It sounds like the old mb-classic releases vs. facts. Right :-) We can't (IMO) put incorrect information @ mb-work level. Right now I don't have any ideas except use the release annotation? or add extra release credits AND use the release annotation? I once suggested that we need to qualify the information: is it factual, it it legal, is it just plausible but unproven information? -- Frederic Da Vitoria (davitof) Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
[mb-style] RFC STYLE-298: New packaging type: Brilliant Box
RFC expected expiration date: 2014-03-11. I would love to see Brilliant Box as a new packaging type. It’s like a Jewel Case from the outside, but inside it fits 2 discs, as it has extra plastic piece inside, that can hold 1 disc on each side. It can be seen here: http://www.carthuplas.be/site/brbox.htm http://tickets.musicbrainz.org/browse/STYLE-298 Marko Sultsing markosults...@gmail.com ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
Re: [mb-style] RFC STYLE-298: New packaging type: Brilliant Box
+1 On Mar 3, 2014, at 5:31 PM, Marko markosults...@gmail.com wrote: RFC expected expiration date: 2014-03-11. I would love to see Brilliant Box as a new packaging type. It’s like a Jewel Case from the outside, but inside it fits 2 discs, as it has extra plastic piece inside, that can hold 1 disc on each side. It can be seen here: http://www.carthuplas.be/site/brbox.htm http://tickets.musicbrainz.org/browse/STYLE-298 Marko Sultsing markosults...@gmail.com ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style ___ MusicBrainz-style mailing list MusicBrainz-style@lists.musicbrainz.org http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
