Nils Hörrmann
Nils Hörrmann
> Otherwise why are we displaying handles for the included elements and not their friendly strings Because we are setting up the XML output which is handle based.
Shall we add this to 2.4? We are breaking compatibility already.
Just to let you know: This has been discussed years ago, too, and there is no such thing as "required" labels in Symphony (there is only _optional_: anything that's not...
Ah, and I just saw the attached milestone: from an UI/UX point of view this would be a breaking change requiring a major release (currently `3.0.0`).
I totally understand. Nevertheless, it should not be fixed until Symphony 3.0.0 in my eyes. Otherwise, you'd make a confusing interface decision even more confusing due to the resulting incoherence.
Maybe it's a good idea to finally separate core (PHP API) and UI so both could be versioned separatelly.
> So how can we solve this? I have no idea to be honest. The system language (not the author's language) should be used as standard. So the system language...
> Again, what if the frontend is multilingual? Ah, right, sorry. A two-step idea: - Make the core handle creation accept a language parameter that overrides the system language. -...
> Wouldn't it be much simpler to not replace characters with language specific terms at all? Can you elaborate, please?