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
Iagree. You Are Correct.
On 6/2/12, sun wrote:
> 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.
>
> I'd also guess it'd improve the UI in many places, since we'd be able t
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.
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
I've been working on a multilingual site and the fact that URL aliases are
selectively available based on language seems a little awkward. I like that
the path module is language aware and stores a language, however I view as
as more of a language provider, than translatable content.
I wrote up so
