You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no documentation about custom loaders and dumpers for the translation component. Custom loaders/dumpers can be used to support old/custom formats for translation files.
@raulfraile thanks for creating this issue and for taking part in the DX initiative. We really appreciate it!
I'm 👍 about your proposal. Given that the translation component already supports lots of common formats, this is a feature that it's not very commonly used by end developers. However, I'd like to document it precisely for being such a dark part of Symfony. Moreover, this could be a clear example of how Symfony is flexible enough to adapt to your needs, no matter how custom they are.
By the way, congratulations on your series of blog posts, which I read and enjoyed!
This PR was merged into the 2.3 branch.
Discussion
----------
Translation custom loaders
| Q | A
| ------------- | ---
| Doc fix? | no
| New docs? | yes
| Applies to | all
| Fixed tickets | #4156
This PR adds a documentation section for creating custom loaders and dumpers to support other formats.
Commits
-------
69491ae Improved custom formats article based on comments
c0f3b0a Fixed wrong indentation
629a008 Extra improvements based on comments
bfd78b3 Improvements based on comments
105a168 Cleanups
e2fd5fa Small fixes
dee7fb2 Link from introduction section
8b6c584 Added custom format page to translation component
There is no documentation about custom loaders and dumpers for the translation component. Custom loaders/dumpers can be used to support old/custom formats for translation files.
The idea would be to port what I wrote in this post: http://blog.servergrove.com/2014/03/18/symfony2-components-overview-translation/ ("custom loaders" part). If you think it can be useful, I can do it in the next DX hackday.
The text was updated successfully, but these errors were encountered: