How to Embed Angular Components Inside a Transloco Translation String
Or how to use parameterized translations inside parameterized translations
“What? Isn’t the application available in Swedish?”
I was talking to my accountant on the phone, but I could literally hear him cringe none the less.
Earlier that week, I had shown it to my stepfather and gotten the same reaction from him. And come to think of, didn’t my buddy Mike make a remark about this as well?
So far, my application had been English only. With a global aim, it felt natural. And these days, most people are comfortable enough with the English language, so there shouldn’t really be necessary to translate it, right?
Think again.
Of course, it depends on what kind of application you are offering. But if you are targeting a traditional market segment as I do, you better face the music.
Flowmine, as my product is called, is an ERP application. It’s all about fun admin stuff like time-tracking, expense reporting, accounting, and invoicing.
And while I might beat a lot of my competition in terms of UX and general look and feel, they still had one thing I didn’t:
