Quick tangent to double down on this. The album F♯ A♯ ∞ is read as F-sharp A-sharp Infinite but it's to be written with its proper symbols because they're, well, symbols, not words. So in this case it's rather useless to name it as ...Sharp FE when it's clearly meant to be a play on the sharp symbol as ♯FE and while it ruins the play, it also makes it confusing as "Sharp" can refer to any meaning but the actual musical definition.
Besides, by the time anyone writes the tag up to that point, autocomplete/tag suggestions will show it on top of others.
You're comparing an emoticon tag to a copyright tag with a symbol that has a very specific meaning. Or does "consistency" only matter when you feel like it?
As 朝子 said, the meaning is lost when transliterating it to "sharp", and Danbooru tags have to be easily typed with a standard US keyboard. I'd be in favor of omitting it entirely like Wikipedia does in the Google results.
You're comparing an emoticon tag to a copyright tag with a symbol that has a very specific meaning. Or does "consistency" only matter when you feel like it?
I'm sorry, but i don't see the problem? I dwell with music from time to time, and i didn't even know ♯ was a different ASCII character from #. I'm pretty sure most people don't know that either, or care. The exact character doesn't matter as long as the meaning behind it is conveyed (that it's supposed to be read as "sharp" and not "hash"). Regarding the consistency part, i was trying to be consistent with how we use other "rare" ASCII characters in tagging rather, i don't see what consistency i'm going against. There's also to be seen the argument in how Danbooru should pop up on google search, and how people will inevitable search #FE way more than ♯FE.
If we really want to use it, tokyo_mirage_sessions_#fe could be aliased to tokyo_mirage_sessions_♯fe. I think removing the character is a bad idea.
Regarding the consistency part, i was trying to be consistent with how we use other "rare" ASCII characters in tagging rather, i don't see what consistency i'm going against.
We've been over this when deciding between v-13 or nu-13. Since then we've gone with transliteration over transletteration.
If we really want to use it, tokyo_mirage_sessions_#fe could be aliased to tokyo_mirage_sessions_♯fe. I think removing the character is a bad idea.
We don't use non-standard characters in tags. That includes aliases.
Most wikis, whether it's Wikipedia or Fandom, opt to omit it and add a proper ♯ in the actual article. I really don't want the transletteration can of worms to open back up where people substitute Latin characters in names and titles because it "looks close enough". See the thread I linked in my previous post.
It's supposed to be pronounced "sharp FE", not "hash FE" or "pound FE", so calling it "#FE" is misleading about the pronunciation.
Past precedent is against translettering, aka changing a non-English character to an English character just because they look "close enough". Changing ♯ to # is wrong in the same way that changing something like "µ's" (an idol group in Love Live!, pronounced "Muse") to "u's" is wrong.
Some sources call it this.
Tokyo Mirage Session Sharp FE is the least preferable option for me because I don't really see any other sites calling it that, except when they're explaining that it's pronounced "sharp FE".
We've been over this when deciding between v-13 or nu-13. Since then we've gone with transliteration over transletteration.
evazion said:
Changing ♯ to # is wrong in the same way that changing something like "µ's" (an idol group in Love Live!, pronounced "Muse") to "u's" is wrong.
I want to say that changing greek letters with latin letters is fundamentally different than changing a symbol with another symbol. I don't have a strong preference, but on a paper you'd write sharp and pound the same way. The strokes are the same, the shape is the same. Their only difference is in ASCII. Compared to µ and u, they have a definite difference, and the strokes are different as a result.
I'm pretty sure we've already done that anyways - a lot of japanese titles use the wave dash (〜), but we use the tilde (~). If we went with that reasoning, we'd have to remove all tildes from titles that contain a wave dash instead.
EDIT: In topic #17126, poppi a was aliased instead of poppi alpha even after i pointed out the problem. I'd say that was more people not particularly caring about the BUR, but it does raise a precedent (of something i'm against of) i guess.
It does not matter if it's #FE or ♯FE because a lot of people can't write the symbol and it isn't recognised by a considerable amount of places like one of my media players, besides if it's Sharp or left bare as FE it creates more confusion, whereas if it's #FE it's either sharp or hashtag and given the clear idol theming and content it's "sharp". A lot of people write F♯ A♯ as F# A# as some of you have probably seen if you're familiar with it and it's still easily and perfectly understandable as F-sharp A-sharp given the context.
I want to say that changing greek letters with latin letters is fundamentally different than changing a symbol with another symbol. I don't have a strong preference, but on a paper you'd write sharp and pound the same way. The strokes are the same, the shape is the same. Their only difference is in ASCII. Compared to µ and u, they have a definite difference, and the strokes are different as a result.
I see your point and don't necessarily disagree, but I don't think whether we call it FE or #FE is that big of a deal, so I'm just going with FE. All this stuff about how it should actually be called ♯FE can be explained in the wiki.
