Russian language has a very weird thing that allows letter "ё" to be written as "е" for simplification and stylization while still being the same letter, however it is not considered in metadata standardizations at all. This brings us to a problem where words that are originally using "ё" but are spelled with "е" cannot be romanised properly due to the way we currently handle such cases.
An example of such case would be this song that is generally interpreted as "всё для тебя", however due to stylization reasons it is spelled as "все для тебя" which would be romanised as "vse dlya tebya" instead of "vsyo dlya tebya" which is an actual correct form of this word that is originally intended.
Taking this into consideration I have the following proposal:
Will be glad to hear more feedback on this matter.
An example of such case would be this song that is generally interpreted as "всё для тебя", however due to stylization reasons it is spelled as "все для тебя" which would be romanised as "vse dlya tebya" instead of "vsyo dlya tebya" which is an actual correct form of this word that is originally intended.
Taking this into consideration I have the following proposal:
- Songs with Russian/Cyrillic metadata are to be romanised using the BGN/PCGN system method in romanised fields. The same applies to the Source field if a romanised Source is preferred by the mapper.
Еandеshould be romanised asyeif it stands alone or aftera,e,ё,и,о,у,ы,э,ю,я,й,ъ,ь. In other cases, it should be romanised ase.ёshould be romanised toyo, however, useoif the character comes afterж,ч,ш, orщ.еcan be romanised asyoin cases where it is used instead ofёfor stylization reasons. Wheneverёexists in any metadata field the alternative spelling should be added to tags to allow both ways of searching.- Ignore any other rules in the file provided, as these are either irrelevant or would not help in the game. For most of the other characters, refer to the first page of this document.
Will be glad to hear more feedback on this matter.