Laravel: Single to Multi-Language - Practical Demo

[@afulay-hy2oy]

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

[@neerajsinghtangariya2587]

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

[@holyhd7505]

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

[@nabeelyousafpasha]

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.

[@bernardonigbinde]

Thank you Povilas. Great tip.

[@carlmenger4964]

yeah but he doesn't know what a sentence is. He just runs on without a break, it's confusing as hell.

[@learningtutorial3960]

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

[@learningtutorial3960]

Good tutorial

[@nurharizulaimanmatharith4023]

This is what im looking for

[@7sujit12]

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

[@MikailAziev]

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.

[@PovilasKorop]

Good question. In my opinion, json file is about TRANSLATION but not about FORMATTING of it. So I would vote for storing in one case (whatever you choose) and then use helpers whenever you have to. Remember, json file formatting is convenient for non-technical people, so there's a chance that people would translate without even knowing whether it will be in uppercase or lowercase in the website, they will look just at json file.

[@Lusikable]

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

[@mulualemabate3193]

thanks sir

[@Mardiantopersonal]

Nice tutorial and explain good job

[@ivan.silicin]

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?

[@LaravelDaily]

Because in your case you don't have the flexibility to adding unlimited amount of languages, without changing the database structure.

[@maryte9801]

Thank you

[@MrTarwinder]

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

[@PovilasKorop]

Camtasia for Mac.

[@nurawadahismail02]

@@PovilasKorop I love to use ShareX for windows

[@majdibrahem1399]

thanks bro

[@papalevies]

What about translated URL slugs?

[@PovilasKorop]

You add those as translatable fields in that package I mentioned. Of course, they won't be translated automatically for all languages, you need to do it manually. Maybe this video will help: kzbin.info/www/bejne/jqm3n6h8mLSmaqs

[@JamesAutoDude]

Its too bad they don't have some kinda automatic method where you don't have to manually type each thing and each translation

[@abdmaster]

what to do if clients need RTL language support?

[@PovilasKorop]

I haven't worked with RTL projects, so unfortunately can't comment on this.

[@razisayyed]

RTL languages needs extra work on frontend. Usually u use some postcss plugins with webpack to achieve this like rtlcss.