Laravel: Single to Multi-Language - Practical Demo

Localisation with Laravel + Inertia.js = Vue is something I would like to learn from you.
Nearly no serious resources about this.
Thank you

Please help improve this article or section by expanding it. Ex: If locale us English saves the text as locale en but when we change locale to fr let it save as locale fr without having to create multiple language forms

Good tutorial

thanks sir

i need multi language system with loading first for big project which package or how to make for this

thanks bro

That's it what i need to implement. Thank you sir.

Thank you

Thank you, but I have a question.
Why just not add fields in start table named like en_title, it_title, ru_title etc. and not complicate the project by adding other tables?

This is what im looking for

What about amount field ? I have seen people entered amount in thier own language.

What about translated URL slugs?

Thanks for the video.

Did anyone think about this: in which case will be better store keys in JSON language files. For example, we may need the string "Login" in both title case and lower case. Yes, we can store it in lower case and use helpers to convert it to title case when we need.

If we store different keys in dirrefent cases in looks messy. We will not remember how string is stored and we will need to check it many times.
If we store everything in same case it will make our code dirty with many many strings wrapped with helpers.

Good tutorial, but project is very simple and one of sensitive topic was not touched - is a multilang article tags. I hope this theme will be appeared in the next videos

Hello laravel business, please can you tell me which software you are using for your video and screen recording...

Nice tutorial and explain good job

what to do if clients need RTL language support?

The approach i used was:
Created two tables
1) table named `translations` having attributes `locale`, `group`, `item`, `text`

2) table named `custom_translations` having attributes `fk_translation_id`, `text`

All the main array indexes are saved in group and inner indexes are in item. With en as locale and english text in text nullable column.

Then schedule a artisan console command to get en locale and text and using Google Translate Api translate it against other provided locales and save them in db translations table.

If a user need any other translation then he can modify locale text and it would be saved in Custom_translations.

This approach might help anybody.

Thank you Povilas. Great tip.