Hi Chaim,

First of all, thank you very much for sharing the files with us. If this is not too much to ask, do you mind telling us which language strings need to fix from our end? Or maybe you can tell which files need to be fixed so that we can do a 'diff' from our copies and yours

Hope this help and have a nice day

Sam,

I only included files that I made changes to. Most of the files uploaded had the term behavior misspelled (you can search for the term behavior).

I made many changes in com_easysocial, I would run a diff on them as I didn't document the location of changes made (as they were quite a few).

Hope this helps,
Chaim

Hi Sam,

Just having updated the English - US version translation, I noticed that the issue still applies in many areas in the original translation file; the same is true for ED & Komento.

Hi Chaim,

Thanks for sharing. We'll see if we can update the language string in the future releases.

Have a nice day.

One other thought, wouldn't it be easier if there were only 2 language files for he extension (that would include the modules)? I noticed that there are a lot of "duplicate" strings when editing the modules (for example the world yes can be repeated 3 or 4 times based on the amonut of modules).

Would that increase the site speed?

HI Chaim,

Thanks for your suggestion.
Yes it can minimize the duplication and it can be done technically. I have checked this with our developers and agreed that we will not compile the language files together. Because this can minimize the confusion in the future.

Hope this helps and thanks again for your suggestion.

Yes it can minimize the duplication and it can be done technically. I have checked this with our developers and agreed that we will not compile the language files together. Because this can minimize the confusion in the future.

Can you please clarify what you mean by minimizing confusion in the future, wouldn't this make it easier to maintain?

Also, what is the easiest way to download all the language files?

Hello Chaim,

We are actually following the standards that Joomla impose by having language files for each module rather than having them all set from the component. It makes sense in a way because if you are loading a module that's not going to use any of the extensions language files, there's no point loading the entire language file from the component. It uses much more CPU because Joomla will have to parse every single string that's available in that language file.

Mohd Yasser wrote:
Thanks for sharing. We'll see if we can update the language string in the future releases.

Mohad, looking through the current language files the issue still exists (across all of the products)

Is there an easy way to override the entire language file (essentially create my own version of the translation files)? If I go the route of using the language override feature, can I disable the language files from the component and will my site load slower with one giant file containing the entire ES (ED, EB) language files?

Thanks,
Chaim

Hi Ck,

Sorry for late reply to this.

May i know which "current language files the issue still exists (across all of the products)"?

So that I can help you check on this?

By the way, unfortunately that was too heavy if all the whole Joomla site language convert into 1 file. ;(

Hi Arlex,

Pretty much every time the words behavior & favorite (the en-US way) are used they are spelled the wrong way (at least for the en-GB spelling), the correct spelling should be behaviour and favourite (en-GB).

I also want to make some changes to the error messages and some general constancies improvements across all the language files (hence my question how large the override file can get).

Is there a better way to manage the language files (other than replacing them with my own and having to worry about them being replaced every time I update my site)?

Thanks,
Chaim

Another example, consistent terms for notifications (the email notification is worded differently than the site notification); doesn't it make sense to have a single term used across both notification types?

Hi Ck,

I'm really sorry that delayed of this reply,

Is there a better way to manage the language files (other than replacing them with my own and having to worry about them being replaced every time I update my site)?

What my suggestion is you can using Joomla language override feature as you suggested in your previous reply ( https://docs.joomla.org/J3.x:Language_Overrides_in_Joomla ), take a look of my 3 screenshot below.
Once you created 1 language override string in Joomla, it will auto generated a new file for this en-GB.override.ini (If you override in en-GB)
After that you can move all your "en-GB" modified language constant in this file "en-GB.override.ini", so you no need to worry about the next update will remove it.

Another example, consistent terms for notifications (the email notification is worded differently than the site notification); doesn't it make sense to have a single term used across both notification types?

It sound like make sense. Thanks for your suggestion, I will consult with our developer regarding this and see what we can do in the future.

Hi team,

With the upcoming V2 release, I figure that it now would be a good time to review the language files for grammar and misspelling.

Please let me know if/how I can help,
Chaim

The language files for ES2 would be available at https://www.transifex.com/stack-ideas/es2/dashboard/