Oh. My. God.

Boss JUST NOW after months of development has told me that anything the user sees needs to be i18n wrapped

*Bangs head on desk*

Why wasn't I told this?
Why isn't it this way anywhere else in the code?! Wtf!

Lol at least today will be laid back and easy, albeit tedious

@irene i18n, a common way of signaling online that said person is over the legal age and available for sex

@irene it is one of the main used internationalization standards
https://book.cakephp.org/2.0/en/...

https://en.m.wikipedia.org/wiki/...

@irene multilanguage localization

@anolis have a look at https://serge.io

@heyheni thanks for the reference, fortunately it is built into CakePHP

I'm actually more surprised that in 2019 there's new software developed *not* supporting i18n.

@VaderNT it boggles my mind that this wasn't brought up during any of the talks I've had with the team, I'm the new dev on the project and .. yea idk seems like something important to mention lol

@anolis continous localization is not about i18n directly. It's a tool to automate the content translation process via git and continous integration.

After programmaticly adding the source copy into the git repo it automaticly assigns the text directly to different translation bureaus / or a machine translator like https://www.deepl.com/docs-api.html . After translation it puts the translation back into CakePHP / digital product automaticly. So no more manual copy pasting into a crm.

It saves marketing / the content creator hours and money as the don't have to deal with translating agencies by email.

also in combination with www.percolate.com it let's marketing plan the content and send it to translation with one click via continous localization like serge.io.

@heyheni this is fantastic info! Thanks!