-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Use xliff (xml) as first option in the configuration-block #11671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
👎 As I explained in #11523
|
I extracted the |
OK I am fine with that, but In this case we should preserve the same order in the other files, too. TLDR; |
@OskarStark I don't think we should do that. We should, for once and for all, fix this inconsistency:
|
I think, if you read the previous issues about this, that the general consensus within the Symfony community is:
I think that's also the main point for disagreement on this topic for the past years: Yaml is for writting, Xliff is for generating. Docs showing generated code examples are often not great, so that would favor the Yaml, Xliff, PHP order. Anyway, that's in full agreement with what's proposed with @javiereguiluz in the comment above. 👍 |
Sorry Javier, maybe I don’t get it, the first of your sentence looks to be against my proposal, but the rest is talking about „fixing inconsistency“ which would point me in the opposite direction 🧐🤓 What do you mean by „fixing this inconsistency“ and how? Thank you for your feedback 👌🏻👍🏻😊 |
Let's close this without merging. For new people reading the docs, it's important that YAML is shown first so you can focus on the translation syntax and not in other syntaxes (YAML, XLIFF, etc.) For those that visit symfony.com regularly, they have preselected their preferred format (XML, YAML or PHP) so reordering this wouldn't affect them in any way. Thanks. |
No description provided.