<10volumetrique> I mean, the guidelines are pretty clear that Instrumental should stay capitalized because of how it is on the cover... But isn't that completely irrational for stuff like ETI
<13BusterEverett> Japanese releases follow their own special rules
<10volumetrique> Which make sense except for eti
<10volumetrique> Why should they be exempt of lowercase on stuff like Instrumental or remix
<10volumetrique> It just doesn't make sense to me
<10volumetrique> So I'm just raising my concern 😅
<12Aerozol> Going to stream some editing if anyone wants to hang. Just for a little bit, been a while, need to brush the dust off! https://www.twitch.tv/aerozol2
<13BusterEverett> ETI is a subset of Style and Japanese is fully exempt from all Style for the culturally relevant aesthetic reasons the guidelines state. That particular release has the info printed in that uppercase styling as well. If it was lowercased, then I'm sure it would apply,
<10volumetrique> No, what I meant is that I disagree with these guidelines. Not that I will vote against the edi
<10volumetrique> I think Japanese style should have ETI guidelines is what I'm raising
<10volumetrique> Is there really a reason for it not to have it?
chamlis has quit
chamlis joined the channel
<13BusterEverett> Read the guideline
<13BusterEverett> "Japanese artists have a tendency to choose capitalization and punctuation for aesthetic reasons, and to be very consistent regarding case over all releases. For this reason, words in the Latin script on a Japanese release should be in the same case as on the album art if other available sources"
<13BusterEverett> Japanese artists have a tendency to choose capitalization and punctuation for aesthetic reasons, and to be very consistent regarding case over all releases. For this reason, words in the Latin script on a Japanese release should be in the same case as on the album art if other available sources, such as official discography or record label pages, are consistent, not normalized according to English or other
capitalization standards.
<13BusterEverett> Disagree with it if you wish, but I would be exceptionally surprised if there would be any alteration to that rule.
Island_ has quit
kepstin has quit
kepstin joined the channel
kepstin has quit
kepstin joined the channel
Maxr1998 has quit
Maxr1998 joined the channel
atticf has quit
atticf joined the channel
<04zoe.division> I used not to have any qualms with that guideline, till very recently I realized I was exhausted by the majority of english-titled japanese albums just screaming at me in my library in all-caps 🥲
<04elomatreb> Ideallyâ„¢ we will Eventuallyâ„¢ get the "alternate tracklists" feature in the MB server that would allow storing two variants of such tracklists, one "original" and one that's standardized
<10volumetrique> I did read it. Still doesn't make a lot of sense for extra information in this day and age where remix and other info is written the English way. I'd appreciate it if I was not talked about in that tone, please 🙂
<10volumetrique> Just raising my opinion. Consensus will do what should be done.
<04elomatreb> note that disclaimer though, it's not an unconditional blanket exception because it's from a Japanese artist
<04elomatreb> it should be consistent across available sources for that exception to apply
Is there any way to use Harmony data to improve existing release
other than copying & pasting of course
kellnerd[m]
Not yet, you can hack Harmony's HTML form with your browser's developer tools to POST to an existing release, but there are two issues which have to resolved before this can be officially supported.
Namely MBS-13579 and a more general scenario as described by MBS-13493
reosarevok: I am not aware of any way to seed the release relationship editor, but I haven't checked again recently.
reosarevok[m]
Hmm. There are scripts that clone release rels and stuff like that but maybe they don't actively seed but do it differently
bitmap would surely know
bitmap[m]
I don't think there's a way to seed the release one at the moment
reosarevok[m]
Hmm, ok. I guess it shouldn't be super difficult in theory since we know how to seed relationship editors?
bitmap[m]
In theory 😉
but the release one doesn't use Controller::Role::EditRelationships, which is where seeding is handled for the other forms, so it might be more difficult than we expect
<13BusterEverett> MB attempts to make considerations for other cultural customs rather than flatten idiosyncrasies to the Western/English paradigm. Approaching interpretation of the rules through that lens is why it’s not making sense.
<13BusterEverett> It already has and that’s why it is the way that it is
MeatPupp3t has quit
MeatPupp3t joined the channel
rgggn has quit
rgggn joined the channel
gchound joined the channel
gchound has quit
broodroost3r has quit
broodroost3r joined the channel
atj[m] has quit
Island_ joined the channel
Island_ has quit
Island_ joined the channel
minimal has quit
anonn has quit
Toasty has quit
<04zoe.division> the joy of finding a new release to add to the database...... 😸