Translations: improve translatable objects concept introduction #21512
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
carsonbot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I've started to translate a project recently. I've read the whole documentation and I've completely gone through the "Translatable Objects" section.
After I faced an issue with translating the content of objects like enumerations, and figured out the approach of the documentation about this subject was meaningless.
Then I've found this issue symfony/symfony#60049 that make me understand. So I wanted to integrate a better context for introducing the TranslatableInterface concept into the documentation itself.
I've based the branch on v6.4 as it's not a bug but it's applicable since v6.4 and before