4

I read official docs about translation and i18n and say that xliff files must be put inside bundle or in app/Resources/translations directory. I have many bundles with your own strings, but some strings are used in others bundles too. Which is best strategy to manage/share common translation strings between bundles?

smoreno
  • 3,129
  • 3
  • 32
  • 49

1 Answers1

3

Personally, I don't use bundles for app specific code, so I keep all resources — views, translations, assets, etc — in app/Resources. You could consider this approach as well.

Otherwise, if you think you really need bundles, you could keep common translations in app/Resources/translations — or CommonBundle which I lately suggest to avoid — while keeping the bundle specific translations in themselves.

Community
  • 1
  • 1
Elnur Abdurrakhimov
  • 44,533
  • 10
  • 148
  • 133
  • I like your approach very much :). I always said. Could work my OrderBundle without my ProductBundle? Definitively not. I think will put all code together now – smoreno Jul 24 '12 at 18:49
  • One problem with this that you cannot build translation files automatically with _console translation:update_. – Tadas Sasnauskas Jul 23 '14 at 09:05