Originally Posted by NLP-er (Post 1850935)

It wouldn't :) DB has set indexes and data access is instant and constant :)

Originally Posted by Neutral Singh (Post 1850753)

Amazing Mod! Is it possible to add other languages? If yes what is simplest approach to it... i would like to have Brazilian and a few other in the list... how could i do it? Thanks again!!

Originally Posted by imported_silkroad (Post 1850907)

I think the stated goal of this mod is to increase search engine referral traffic. Converting new visits to members (active or not) is a completely different process. Any "stats" in this area would be misleading, IMHO.

Originally Posted by 45wheelgun (Post 1851057)

This script is only limited by what Google Translation offers. At this point it is 28 languages. As for "Brazilian", I am not sure what part of Brazil speaks Brazilian, but in most of Brazil they speak Portuguese, which Google translation already offers....:)

Originally Posted by imported_silkroad (Post 1850951)

OK, I'll put that aside and change the subject.

Let's discuss Google indexing and translateflags.php.

If we assume that Google has limited resources to index a site, and that GoogleBot does not distinguish between the various language flags, then this seems to imply that it will be more efficient, and generate more search traffic, in the beginning of the translation process, to only expose the top ten or so Internet-language flags.

The reason for this is that if Google indexes all translation languages equally, Google will index languages with very small Internet-populations with the same priority of languages with high Internet populations.

So, unless I am wrong, which I could be :) it seems to indicate that to optimize search referral results, in the first month or two, a site should expose only the top 10 or so flags (from an Internet-usage perspective) and not expose the minor languages.

Is this how you see things as well?

Originally Posted by imported_silkroad (Post 1850911)

I have a related question.

Would it be more efficient and faster to have database tables for each translation instead of "small" and "medium" mega tables for an entire site?

We have been running this mod for just a few days, and at the current tables growth rate, our translation database will be nearly 1.2 Terrabytes in three dB tables when it is all "done and dusted" as they say, hahaha. I calculate this, perhaps incorrectly, as it seems Google has have cached around 200 pages (for each of 28 languages =~ 6000 pages) out out nearly 400Kpages, and the translation dB is currently 600MB. If we assume approximate linear growth, the full transation dB would be 400K/200 * 600 MB or 1.2 TB

I notice that our translated pages are much slower loading than the same page not in the translation dB (by quite a large factor, much slower, even though there are less MySQL queries for the translated page).

Why not put the translated pages, at least, in their own tables?

Originally Posted by Dave Hybrid (Post 1851073)

The database can only be so fast, the work has to be done behind the scenes so the translated pages will never match the non translated pages.

That said my site is not noticeable, I also checked your site and the speed was pretty identical for both types of pages.

Are you sure your not comparing a page never cached to one that is cached vs a normal page?

Originally Posted by Sweeks (Post 1851082)

Are their plans to update this mod when vb4 is out if it is needed :D

Originally Posted by 45wheelgun (Post 1851101)

Dave,

Is there any way to add the option to make the translation "sticky"? I mean so that once a user chooses to translate a page, all other pages (either per session or permanently) are translated?

I would like the option of having members who always see the forum in their native language.

Thanks again for this amazing mod....I'm loving it.