Also, most of the time for actually using the alias, the real problem is that the target language to display the alias with is not explicitly provided, and treating aliases like buckets does not really solve that in itself. I do think if CMI for aliases happen, that would in itself solve this issue btw, but that needs a streamlined storage. <a href="http://drupal.org/node/1553358">http://drupal.org/node/1553358</a><span></span><div>
<br></div><div>Gabor<br><br>On Saturday, June 2, 2012, sun wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Turning each alias into a bucket holding language-specific values would indeed be consistent and in line with multilingual fields as well as configuration values in D8.<br>
<br>
I'd also guess it'd improve the UI in many places, since we'd be able to expose the path translations as a. single set. And of course, when updating an alias, hooks could appropriately act on all aliases in the set.<br>
<br>
So yes, at least creating an issue for this would make sense.<br>
</blockquote></div>