Since the end of 2012, using Unicode for Title, Artist, Source, Tag has been abled.
These days, we can see lots of beatmap getting ranked with the unicode being used at the source. Japanese for J-Anime for a frequent example.

However the problem is that the unicode gets displayed at the osu! official site, and users who can not read those native language will not have a chance to know how those language pronounce at the beatmap listing unless clicking the beatmap and checking the tags.
It will be a great discomfort for the user who I've mentioned above, and deciding to use only romanized letters to the source would make everyone read where the source of the song is.

I've always thought that a criterion should be made for this topic, and will result in less randomness among beatmaps.

Discuss.

Cool suggestion, I second this!

Rather some Feature Request to add Source/Romanised Source, like we already have for Artist and Title.
But probably this won't work smoothly as we have mixed formats there.

Sonnyc wrote:

However the problem is that the unicode gets displayed at the osu! official site, and users who can not read those native language will not have a chance to know how those language pronounce at the beatmap listing unless clicking the beatmap and checking the tags.
It will be a great discomfort for the user who I've mentioned above, and deciding to use only romanized letters to the source would make everyone read where the source of the song is.

I completely agree for this reason! It always annoys me when I can't see the source the song is from by hovering over its beatmap listing.

Since this got denied I guess this will work even better.

want this

I'm still curious what happened to having a Unicode source field alongside a romanized source field. It would make the source appear romanized on the site and allow for players who can read the native language of thir song, still possible.

Was it denied or something? Or never even suggested yet?

Sonnyc wrote:

However the problem is that the unicode gets displayed at the osu! official site, and users who can not read those native language will not have a chance to know how those language pronounce at the beatmap listing unless clicking the beatmap and checking the tags.
It will be a great discomfort for the user who I've mentioned above, and deciding to use only romanized letters to the source would make everyone read where the source of the song is.

totally agree :V hope this will happen

If Romanized sources mean that the sources are spelled out how they are pronounced instead of in their native language, I'm all for it.

I support this but dake's idea would work too c:

DakeDekaane wrote:

Rather some Feature Request to add Source/Romanised Source, like we already have for Artist and Title.
But probably this won't work smoothly as we have mixed formats there.

Lanturn wrote:

Was it denied or something? Or never even suggested yet?

I have ever nominated it p/2556081/

Didn't know there was something similar at the denied list. Seems it's the opposite suggestion with mine?

Anyways I think we need to decide to one side; romanize or unicode if both exists.

I honestly don't see much of a problem because if you choose to source the Hiragana/Kanji part of an Anime in the source field you will more than likely add the other one to tags. Switching that around is not really anything that makes a difference.

I personally am for treating this like Unicode Artist / Romanised Artist because if your source is something Polish or whatever which uses Unicode stuff you can take the official thing as source (e.g. the way it is shown on the anime's website or something) and then put the romanisation in the other field which would then be shown based on user's preference by checking this.

Would make more sense to me this way than enforcing one thing

I'd rather it not be romanized because sometimes things get pushed off the top of the screen like this.

As opposed to this

This doesn't happen too often, but I would like to see a romanized source field in .osu.

IMO this is totally stupid. It's like 'Many people do not understand Russian so sources in that language has to be Romanised. Also Polish letters like 'ó' and 'ś' should be Romanised too. The same goes to German and French signs since they have different ones too.' Please. If someone doesn't speak in the language which is used in a source gap, it is A PERSONAL PROBLEM.. What is the simplest solution? To learn that language for God's sake. The only recommendation from me would be just using romanised version of the source in tags, but it's really stupid to transalte everything to the Rom. version.

I am writing like that because I do not appreciate things like this. Imagine you're the author of the animu/movie/whatever where the music is used and for example it's called 'Opowieści z Mieściny'. So the romanised version should be:
a) The name without Polish 'ś' sign and should be replaced with 's' sign
b) The title should be translated into English, this time it'd be 'Stories from a Little Town' or something what has the same meaning.

And? Both are stupid. Why? Because the original title is in Polish and not in English. The authors would be really annoyed they couldn't use the original name and it's the obligation to use only Roman signs which do not translate it 100% correctly. IDK how it works with Asian languages, but if people write Russian/Ukrainian (generally: Slavic languages) words in English there are usually from 2 to 5 or even more ways to write something and still not sure which way is more correct. Want a simple example? Imagine the name 'Аня' - read 'Anya' - is the source. So simply we should write 1 of the possible ways in the source and the whole rest in the tags. We should add 'Ania' 'Anja' 'Anjia' 'Anna' to the tags then! So please, no.

LVU Krfawy (>o3o)>

Yeah, romanization is hard especially when you get to the debate of whether or not it's correct
It would probably suck as the creator to see your own work translated to something else you don't agree with..

Can't we just put down whatever's official? if it's Japanese, leave it in Japanese; if it's English, leave it in English.

Oh right, I agree too on leaving the Source written in their native language. If Japanese, Japanese, if Polish, Polish, if Klingon, Klingon, etc.
This way would be more correct and we'd avoid problems for having a bad romanisation (we already have them with Artist/Title, why looking for more?)

Krfawy wrote:

IMO this is totally stupid. It's like 'Many people do not understand Russian so sources in that language has to be Romanised. Also Polish letters like 'ó' and 'ś' should be Romanised too. The same goes to German and French signs since they have different ones too.' Please. If someone doesn't speak in the language which is used in a source gap, it is A PERSONAL PROBLEM.. What is the simplest solution? To learn that language for God's sake.

Go and learn every language used as source in osu, it's totally damn stupid point that you have.

Also this is pretty nice idea to always setting romanized source. It isn't hard to do, I saw many maps and most of non-romanized sources are from animu/visual novel etc. so it isn't hard to find romanisation lol.

Playing osu! and can't read Japanese? Come on.... Kappa

Yeah this should've already been a thing.Good idea.

OzzyOzrock wrote:

Playing osu! and can't read Japanese? Come on.... Kappa

Yeah this should've already been a thing.Good idea.

So is this statement for or against this proposed rule...? You didn't make that clear. I always thought the reason for the inclusion of unicode source was because it is encouraged.

I thought the reason we implemented the unicode title/artist was to credit the artist better, shouldn't the source be the same? We should keep it at its original language to be more consistent with the way the rules are going to be as close as possible to the actual metadata (tv size, feat. Vocaloid, etc). I think the best solution for this problem is, like DakeDekaane and Lantern mentioned, adding romanize and unicode source in the game though.

Wouldn't be a great idea if there was a romanized source like there is with Titles and Artist already. Then both sides would be happy.

Still I personally prefer something to be romanized if it's more commonly known by that name. (Let's face it. If I map the Mario theme putting スーパーマリオブラザーズ in source will confuse a lot of people)

I agree with Dake.
Sum up, for me, source should be written by official language. For some cases, here I will say for Japanese. Some vn games doesn't give us an exact romanized name/source that you must forcely use Japanese/Unicode for source in Osu!. Yeah, it's sure that you can't find an exact romanized one. What will you do now? Translate by Google-sama and use romanized from it. I'm sure that Developers won't feel good when seeing a thing which is wrong with him. Also, the translated one also isn't perfect. You know, Japanese is a difficult language with many different pronouciations, space and no space in romanized source will creat different pronouciations. It is really dangerous. So, source should always be romanized isn't great at all.
It isn't also a problem that be called as "should" or "shouldn't". If you can find an exact romanized source or you believe that it is exact one and it is official, then add to source, for repeat cases. You can't do it and realize that the unicode is official instead, then keep unicode to source.

I agree to keep romanized source and let the mapper decides what they want to put in the source,
It can be a guideline instead of a new rule that can not be broken.
There will be more issues of which romanized source is correct if everyone is forced to romanzied the source

[ S a k u r a ] wrote:

I agree to keep romanized source and let the mapper decides what they want to put in the source,
It can be a guideline instead of a new rule that can not be broken.
There will be more issues of which romanized source is correct if everyone is forced to romanzied the source

e.g.
とある魔術の禁書目録
Toaru Majutsu no Index
To Aru Majutsu no Index


I think metadata should have a new form to type the romanized source, like Artist and Title.
If what the mapper types there is displayed at the osu! official site, it would be great.

Xgor wrote:

Wouldn't be a great idea if there was a romanized source like there is with Titles and Artist already. Then both sides would be happy.

Still I personally prefer something to be romanized if it's more commonly known by that name. (Let's face it. If I map the Mario theme putting スーパーマリオブラザーズ in source will confuse a lot of people)

I agree with Xgor. Why don't just romanise those that have english versions and leave those that do not as it is in the original language it was made in?

This should be in the guideline (if this really needs to be put in RC), set something like this as a rule might be too strict :\

If this idea becomes a rule, perhaps we can put the romanize of the source in somewhere like in tags or in mapper's words or so. That would probably, probably let more people know what the source is.

Anyways it seems the happiest solution that most people will agree is to seperate the source section in the editor.

Sonnyc wrote:

Anyways it seems the happiest solution that most people will agree is to seperate the source section in the editor.

I really realize that it isn't necessary since noplace for it to show unicode or romanized. They're not the same as artist and tittle yet: Shows unicode in gameplay and shows romanized on forum and menu screenshot. Unless if it was allowed to appear as text in-gameplay like artist and tittle text.

Xgor wrote:

Still I personally prefer something to be romanized if it's more commonly known by that name. (Let's face it. If I map the Mario theme putting スーパーマリオブラザーズ in source will confuse a lot of people)

I'm all for a romanized source. Primary reason: everybody deserves to know what anime/eroge this song is from without having to click to enter the beatmap listing and looking through tags—

KSHR wrote:

I think metadata should have a new form to type the romanized source, like Artist and Title.

Also:

peppy wrote:

I believe source should be in the language it is supposed to be.

So maybe use the original language unless there is an official translation or romanization? for example cases like FAIRY TAIL / フェアリーテイル and to avoid stuff like this: p/3523681

Alright, for all japanese anime (video games too~), plz use original title~

But, about PSYCHO-PASS, what is original japanese tittle? T_T
サイコパス <<<----- that correct?

Up until then whenever someone suggested me to change the source to kanji/hira/kata I rejected it. Why? Because its obvious that learn to read japanese is not an easy task. Its not that hard either but I still can't ask it from 100.000 active players. Therefore in my maps case, I only used romanized source up until now.

Romanizing them is the best choice we can do as we have some nice source to do it (anidb, myanimelist). And we can still ask for confirmation as we already do it in the case of title/artist if we are unsure about it. The double source field can work as well but I'm not sure if that will be added ever. o.o

Its hard to decide what to do with polish, russian, etc names though. I'm not even sure if the source field needs to be filled in those cases but it would be better to change the thread title to "Japanese source should be romanized" since we are mainly speaking about those here.

tr;dr If this needs to be a rule then it can sounds like

Although I think, forcing mappers is not a good solution. Maybe as a guideline this would be better. o.o

No consensus has been made. Flaming.