title: angular-i18n work-around for translations in code?
body: <p>We have to wait until Angular 6 for angular-i18n to support translations in code for error messages and such.</p>
  
  <p>For those that are using angular-i18n (instead of ngx-translate for instance) what are you doing in the meantime to handle translations in code? It occurs to me that if there are not many strings then a simple language service with methods to get translations by language code and an id would work, but I am interested in something more elegant and "angular".</p>
  
  <p>I do not know what the promised code translations support will look like but any temporary solution would ideally be easily converted to the angular-i18n way when it goes live.</p>
  
  <p>What are people out there doing to handle this issue? Any ideas?</p>