We should unify pseudo-releases and originals like vgmdb does. There's a (really long) description (written for Mason) in http://bugs.musicbrainz.org/ticket/4153

Description

The current situation regarding translations and transliterations is very awkward. Among its issues, in no particular order:

Release spam

A new release is created for every translation. This makes the release list unnecessarily long and difficult to search. Even if pseudo-releases are hidden by default, they will still clog search results with duplicate entries.

Duplicate data

Either the translated release is heavily stripped down, with no track lengths / releases / annotations / etc, or the information has to be duplicated in both releases. Either choice is annoying. Lack of track times is especially annoying because lacking times complicates release lookups in Picard.

When I started editing I added PUIDs to both original and translated releases. Now, I add them only to the originals. Either way causes difficulty locating a track based on PUID. If the PUID is added only to the original, it's difficult to know whether a release was correctly looked up by picard. If the PUID is added to both, it is duplicate data and causes potentially duplicate release entries to appear in Picard's release pane.

Relationships

Relationships are not added to translation releases. To find a release's relationships requires an extra click. To find a track's relationship requires three extra clicks, plus searching through the original track list for the correct track index.

Partial release translation

Sometimes if I'm translating a release, I don't know what the correct translation for a track is. The current system is all-or-nothing; there is no good way to translate only a few tracks out of an entire release.

Track ID comparison

Services such as Last.FM can use the MusicBrainz ID of a track as a unique identifier. Translation releases ruin this, because it introduces "phantom" tracks that will not sync up with the existing tracks in the service.

If a release is played with the original set of metadata, and then updated to use a translation, there's no way for the computer to know that they are in fact the same track. Metadata-independent track identification is a major benefit of using MusicBrainz IDs, and the current translation system throws that away.

Localization

If I'm browsing the site in English (or whatever), if a release had an available translation into my language, it would be nice for it to be displayed rather than whatever the native language is.

Pseudo-translations

Some releases are titled in a language other than the artist's native tongue, and end up with titles that are gibberish. It would be nice if there was a way to provide a pseudo-translation from a language into the same language, in lieu of manually re-tagging such releases.

Translation suggestions

Many artists release multiple tracks with the same title. When this happens, it should be possible to provide "recommended" translations for a title to save time and effort. It should not force the same translation to be used, since there are legitimate use cases for the same original text being translated in different ways depending on context (word play, puns, artist intent, etc).