[mb-style] Re: RFV: Translation Transliteration Relationship Type

[Alexander Dupuy]

Okay, Rob fixed the bug with the test server, and I created a 
{transtype} attribute for the new transl-tracklisting on the test 
server.  Tried it out with the attribute optional, then made it 
required.  Created some ARs for mini-moni. 
(http://test.musicbrainz.org/show/artist/?artistid=174327) albums, and 
also Twelve Girls Band 
(http://test.musicbrainz.org/show/artist/?artistid=175461) Beautiful Energy.

All in all, I'm still not convinced that having an attribute to 
explicitly mark translation vs. transliteration is really worth the 
extra hoop-jumping, and although I tried to fit the parameter into the 
link phrase, it's still rather awkward, especially for the "original" 
(forward) phrase.  (Changing {transtype} to {transl-ated} might help a 
bit when selecting the new AR type in the UI).

But anyhow, play around with it.  Suggest alternate link phrases (and 
descriptions) - with and without the attribute - that are clearer and 
less awkward (put 'em on the Wiki).  Or even alternate approaches - one 
that just occurred to me would be to call the attribute {iter}, make it 
optional (with no sub-values), and write "transl{iter}ated titles" in 
the link phrase.  I don't know if there would end up being strange 
spacing on that, though - and the {phrases} show up in the menu when 
selecting the relationship type, which is going to look intimidating in 
the UI (this phrase is already several times longer than all the other 
release-release relationship link phrases).

I do think this demonstrates that the idea of attributes for this AR 
type needs more consideration and experimentation before we make a 
decision to adopt it (or not).

@alex

-- 
mailto:alex.dupuy at mac.com