Closed hason closed 7 years ago
@guilhermeblanco what do you think about this? I still haven't looked at the class so deep, but I agree that using a common php ext/library would be better that writing the component from scratch.
F*ck! It totally makes sense. It'd simplify the code a lot.
+1 that would make it easier
@DavidBadura Have a look at https://github.com/webfactory/icu-translation-bundle. We developed that bundle specifically for message formatting. Might help.
I have a yet to be finished patch laying around somewhere... will submit for 3.0. I also did the same work as webfactory's, but I deal with fallbacks too, so if it doesn't work with Intl, it tries the Symfony old style.
Any news on progress for this?
@fkrauthan see linked PRs above
@fkrauthan Will soon be closed by https://github.com/symfony/symfony/pull/18314 :)
@HeahDude I just skipped thru that article and it seems like the step into the right direction but it seems like that https://github.com/webfactory/icu-translation-bundle would still be superior as it allows you to mix multiple formattings (e.g. select for gender + count + number formatting for count - see https://github.com/webfactory/icu-translation-bundle/blob/master/Resources/doc/index.rst#nested-conditions). Or will that be possible with #18314 too?
Instead of reinventing wheel in #4797, #4884, #5547, we should use the MessageFormatter class. Read more: