#musicbrainz

They don't, which is why I was confused.

ok so do you know how to add 2 discs to the same release?

I don't yet!

Ok no problems, do you know how to enter one disc?

Yeah, that's super simple.

Ok so when you enter one release, and you are on the track section, there is an option to add another album (at the bottom)

Click on that then you can add the details of the other disc

(It might say Add another disc or something can remember)

can´t

"Add medium", yeah.

Oh, and then I get to enter disc titles, cool.

That´s it ... you got it now?

If the 2nd disc exists already you can import the details

from MB

Yeah, I got it!

Thanks for the help!

Awesome, no worries. Ask if you get stuck, usually somebody here.

Yeah, I'll probably be back, I'm pretty new to this whole thing but people have been super helpful.

It takes a while to get your head around it all

Oh yeah, I actually have one more question right away.

Is there a policy on full-width characters?

umm not sure what you mean by that?

Ｌｉｋｅ ｔｈｉｓ.

Usually I'd imagine it's just an oversight by the person entering the tracklist, as I think some Japanese input methods for instance default to fullwidth.

I would say (without being an authority), if that is how it appears on the release (and it seems to be intentional rather than just fancy formatting of the designer) then do it that wya

Japanese releases are a whole other kettle of fish, pretty much as it appears I think is how they do it

hibiscuskazeneko, will be able to help with that

Yeah, they can give me some real headaches sometimes.

I take one look at a Japanese release and run away

Point is, it does not really matter. Enter how you think it should be and if somebody thinks that is not right they can fix it.

And I still feel kinda iffy about changing all their funky remix tags to just (remix).

They tend to like -remix- or ~remix~ or god knows what.

MajorLurker: Sorry, I haven't been paying attention. What is it you all need?

Not sure that we do actually change them for Japanese releases

nvm, I see now

:)

omar_: What kind of fullwidth characters are you talking about?

Can you give an example?

Ｌｉｋｅ ｔｈｉｓ. << is the example they gace

gave

Generally with Japanese, the rule is "follow what's on the cover"

I wouldn't use fullwidth letters, if that's all you're referring to

Punctuation is another story

My specific issue is with this:

Sorry for the long link.

Specifically track 4.

For tracks 4 and 6, I'd use regular ASCII letters in lieu of fullwidth

I would think that was right too, but hibiscuskazeneko is much better with that than me!

The thing is, right now it's A.N.A in MB.

And I wanted to at least get the punctuation right.

The character you need to use for that is ・

But combining that punctuation with regular letters turns out to look like ass.

I know

It's not an exact science

So you think I should stick with regular letters plus Japanese punctuation?

Yes. That's what I normally do.

Alright, thanks!

Sometimes when you enter a tracklist into MB, it won't look as glossy as it does on the cover. There are a number of reasons for this (font variations, use of images as characters, etc.)

Thanks for popping up, hibiscuskazeneko :)

No problem; I'm usually lurking in here

I'll try to remember your name for the next time I run in to some Japanese confusion haha.

I know, and I knew you would know....

One egregious example I can think of was a release (whose name I can no longer remember) with a track whose title contained a treble clef. For those who don't know, the Unicode treble clef character is not centered. The end result ended up looking garbled.

Haha wow, that's annoying.

On a lot of older releases (circa '80s-early '90s) exclamation points will be slanted to the right, so I often am left guessing as to whether to use ASCII or fullwidth exclamation points.

Yeah, don't get me started on my frustration with exclamation points...

CatQuest: I didn't have any problem merging your PR back to my bitbucket repo, so I'll continue with my "primary bitbucket" workflow

and you can continue opening PR on github directly :)

Can somebody explain the tag here: https://beta.musicbrainz.org/release/0c72e8d4-9...

please

eh

?

odd ?