So we are implementing a big and very complete localization management system on my company. The system has great features, indeed, but:

1. We cannot use the browser back button, because it is js and it appears no one cared about it (I am not a js Dev, but you can UAE the back button on my site that has js);

2. It is very customizable, but not intuitive. So you have one million options and you never know where to change what you need;

3. It has a save button everywhere, but most options are saved automatically, so you never know when you need to save. Actually, people from the webapp company use the save button as refresh, once we cannot use the browser refresh button;

4. Combo boxes load the elements while you scroll them, so to scroll to the bottom, you need to keep scrolling several times, waiting it to load the elements;

5. It does not allow you to open more than one tab of it at the same time. So if you need to see more than one information from different items, you need to navigate and wait the loading times to see what you need;

6. Emails are not sent in a different thread. So each action that send emails you need to keep waiting until the emails are sent (sometimes there are several emails sent in one action) to continue using it;

7. They not only store and send back your password by email if you loose it, but, as admin, if I click the button to send the user password to him/her, it keeps a copy of the email with the user password in my sent items;

8. To be able to send emails (they are really necessary), I need to include my SMTP info with login and password. So they have not only the system password saved, but everyone email login and password as well.

I am sure there is more, but I can't remember for now, and we are still trying to figure it out how to back our data, as it appears the only possible backup is their own.

Sometimes you read a translation so bad that you realize it has to be from Google Translator. And sometimes you read a translation **so bad** that you realize it has to be from a person.

Please tell me why my boss thinks instead of just implimenting a language picker, it's a good idea to:

1) store the browser's language option in the DB only for new users, but only the first time they log in, never again.

2) never give existing users the ability to change language, and just default them to English.

3) deal with all upcoming language change tickets by having devs manually do DB updates ON THE LIVE PROD DB.

I'm screaming.

I started asking to get draft templates in German language. So at least we'll know what the site will look like what when text is very long and customers are called "Sebastian Wiedenmann" instead of "John Doe".

Remember English is a very concise language and you always get bad CSS surprises when applying translations.

Internationalization be like:
Yo dawg, look, you can use mutliple languages now!

Suddenly gettext won't find any language files and every string is empty ;_;

WHY HAVE YOU FORSAKEN ME GNU?!

eleventy localization still lacks good examples and useful best practice. Localizing symfony projects seemed way more easy and logical to me