Forum Display Enhancements - vB Enterprise Translator

2.3.15 RELEASED - TRANSLATIONS NEVER WERE SO FAST!!!

Great thanks to all who nominate vBET and allow us to win MOTM :up:

This mod translates your forum using FREE translations for over 30 languages from Yandex API. It is 100% FREE in version described here (2.x).
Note: using this mod (vBET 2.x) is free and bound by license agreement (see below)

Yandex translation gives you 1 000 000 FREE characters per DAY to translate. Please note that Yandex do not supports all language pairs, but vBET detects automatically which are supported for your forum language.

Version for vBulletin 4.0 is here: vBET 2.4.x for vBulletin 4.0

vBET 3.x released!
Please note that vBET 3.x is developed as separate product line and it is available here: vBET 3.x. Full version is paid, it supports 53 languages each to each translation, using: Google, Microsoft, Apertium, Yandex, SDL BeGlobal and DetectLanguage. It has lot of optimizations for booth performance and translations costs.

LIVE DEMO - note that demo shows functionality of full version (3.x/4.x), which has more features than 2.x
See also screen shots below, for configuration options

Features:
- Translation by Yandex (in PRO version supports 53 languages using several translation providers)
- Optimized cache, algorhitms and more performance options - PRO version only
- Translates URLs and RSS - PRO version only
- Supports multi language communities (allows to write in different languages) - PRO version only
- Links appropriate for SEO consensus (configurable) - even without any SEO mod
- Long texts are translated no matter how big those are
- Translation cache (after first translation results are cached and next page generation is much faster)
- Doesn't translate BB codes for code, php and html (must refresh post cache to see effect on existing posts Admin CP -> Maintenance -> Update Counters -> Rebuild Post Cache)
- Easy installation - just upload files and import product file
- Highly configurable and easy configuration - by Admin CP (see screenschots)
- Configurable place for flags - simply select in options where you want to have translation flags. NO MANUAL TEMPLATE MODIFICATION. Supported: Footer-Bottom, Footer-Top, Navbar-Bottom, Navbar-Top, Custom
- Possible custom place for flags - in such case just edit template which you want and add $vbenterprisetranslatorflags
- Translates also archive pages
- Reverse page direction for Arabic, Hebrew and Persian languages
- Not translated save areas - if you need something to be not translated simply edit appropriate template and put it between
<!--START vBET NOT TRANSLATED AREA--> and <!--END vBET NOT TRANSLATED AREA--> (note: you cannot use any mod which removes comments to use this functionality)

Installation:
1. Download zip package (last release - see index at the end of file name)
2. Upload to your forum directory on server everything inside upload directory
3. Import in vB Admin CP -> Plugins & Products -> Manage Products -> Add/Import Product -> Choose product file, set Allow Overwrite to yes and click Import
4. Click here: "Mark as Installed" Thanks!
5. Configure in AdminCP -> vBulletin Options -> vBulletin Options -> vB Enterprise Translator
You MUST configure at least Forum language and Yandex Translation API key. NOTE that there are some other important options - especially if your forum is in subdirectory or if you use vbSEO.

For MORE INFO and troubleshooting please read first post There is FAQ. So save your time for writing questions which are already answered and get your solution faster

Known issues:
- link for page on which you are doesn't track translation, cause it has same URL as flag for forum default language

ENJOY! :up:

And thanks for nominations

Already donated (great thanks:up:
PossumX, adwade, roymogg, zipperty, CoZmicShReddeR, RedHacker, john devost, mandingo, chris, smnoel, Audax666, Damas, TurkeySub, nectons, Scalemotorcars, TheWite, Cybershaolin, burlesque, Ransy72560, chick, jaryx, linuxututs, cormee, dai-kun x2 :up:, imported_silkroad, Megatr0n, KrisP, CareyCrew, ghisirds, vitoreis, cyc, mosz, CThiessen, actolearn, jaconi, andie215, yahoooh, bollie

LICENSE AGREEMENT - using this mod you agree for those conditions:
- you are NOT allowed to remove credit link under any conditions
- removing credit link means BREAKING LICENSE AGREEMENT and you lose your rights to use this mod
- using it after that is illegal, it is software PIRACY and it will be notified in vBulletin community and other places, including appropriate government/police units in your country
- author of this mod reserves the right to change the terms of this license agreement at any time. Failure to receive notification of a change does not make those changes invalid. A current copy of this license is and will be available here.

Please note that in full vBET version there is possibility to buy branding free license. There is no such possibility in free version included here.

Version history:
2.3.15 Changes:
- Fixed canonical link
- Fixed issue with SSL verification
2.3.14 Changes:
- Added 48 new languages pairs
- Updated link to Yandex in configuration
- When translation limit is reached now we show original text instead of empty message
2.3.13 Updated link to Yandex API key
2.3.12 Google changed to Yandex translations
2.3.11 Added "Affiliate Program" parameter
2.3.10 Footer bug corrected
2.3.9 userip added to Google translation request + small bug fixed
2.3.8 Small bug fixed - now all supported languages can be chosen as forum default language
2.3.7 Bugs fixed:
- weird redirections with vbet_lang
- double language in URL
- changing text direction for specific languages
Added support for:
- usernames not translated in who is online
- supported URL replacements for canonical URL
2.3.6 Important fix! - there was issue with sending referrer header which is necessary by Google conditions. This one was fixed + issue with # in translation links
2.3.5 Important change - According to Google conditions referrer header must be added to each translation query - otherwise you can be banned by Google. Install this version to avoid any troubles.
Changes:
- Added referrer header for Google translation queries
- Corrected bug for returning to forum main page from translated page
Also according to actual Google conditions your "Powered by Google" information should have Google logo. So please change text for flags in your vBET configuration to something like this:

Automatic Translations (Powered by <span style="vertical-align:sub;"><img src="http://www.google.com/uds/css/small-logo.png" alt="Powered by Google" border="0"/></span>):

You can customize it but "Powered by Google" should stay.
2.3.4 Important bug fixed! Corrected translation of meta keywords and description
2.3.3 Important bug fixed! And also some other bugs fixed
- Fixed bug with shifted results caching
- Fixed bug for URLs to javascript functions
- Fixed bug for not translating usernames in postbit
- Little cosmetic changes
2.3.2 Really little changes.
- Changed default value of "Links title" attribute, to be more accurate for Google conditions
- Little template changed for flags, so "Link title" font will be smaller (just like vB info in footer)
- Small bug fixed
2.3.1 Some little bug fixes. Confirmed working with vbSEO 3.3.1 and confirmed working SEO links on forums with vbSEO and subdirectory in URL
2.3.0 Great news for those without vbSEO
- Supports translation SEO links even without vbSEO
- Translate Google Maps (configurable)
- Little optimizations (i.e. included only necessary things for not translated pages)
- Supports several cache cleaning strategies (optimization for really big forums) and automatically disables cache for cleaning time to avoid read/write conflicts
2.2.1 Small bug fixed with returning to default language for main page and SEO links (happens only for specific vbSEO configuration, so you don't need to update if 2.2.0 is working for you)
2.2.0 Translation tracking is working even when redirection by some mod occures (configurable reaction time)
2.1.0 9 new translation languages added! Also:
- Redirect to user language functionality - configurable (disabled, forced, after asking user does he want to be redirected).
- Fixed bug for SEO links with forums acting like directories by id.
- Corrected several flags
Update note: if you use SEO links you must change .htaccess file according to description in first post. If you changed any vbseo.php rules ? un-change those.
2.0.3 Quick bug fixing (issue with bitfields in options panel)
2.0.2 Added option to set your forum main domain for tracking URL's in subdomains
2.0.1 Small bug fixed and added direction changing suport also for Hebrew
2.0.0 Some small or medium changes and one big - for vbSEO users now SEO consensus links available.
What's new:
- Links appropriate for SEO consensus (configurable)
- Persian support added
- Doesn't translate BB codes for code, php and html (must refresh post cache to see effect on existing posts Admin CP -> Maintenance -> Update Counters -> Rebuild Post Cache)
- Reverse page direction for Arabic and Persian languages
- Option to set forum directory if not linked to domain
- Few bugs fixed
1.1.1 Some little changes and bugs fixed
- Re-encode not translated parts, so there is no strange signs in scripts, images title etc.
- Corrected flag for Sweden
- Few harmless bug fixed in translation tracking and cache disabling
- Respecting Google conditions default flags title have link to Google (configurable)
1.1.0 Lot of new features and no longer in beta stage
- Long texts are translated no matter how big those are
- Cache is working for chosen languages (you simply select for each language does translations should be cached)
- Option to add Google Translate API key for translation requests
- Configurable cache time to live and scheduled task which automatically remove old cache.
- Option to show flags only for guests
- Option to easily remove flags border (without any style changing)
- Option to not translate usernames
- During translation changes param lang in html tag
- Option to translate messages changed by vBSEO to JavaScript (it has such functionality for SEO purposes)
1.0.5 Flags showing correctly for forums in subdirectory + corrected returning to base language
1.0.4 Bug fixed with translation of '0' string. Also added little feature - if some parts of your forum uses vbSEO and some are not then now flags will have appropriate URL's everywhere
1.0.3 Big bug fixed Mod doesn't mess in template anymore (it did in some specific cases)
1.0.2 Small bug fixed - error with array merge solved
1.0.1 Small bug fixed - now choosing supported languages in options works fine
1.0.0 Great mod released

[NLP-er]

Originally Posted by Audax666

Awesome Addon!
Installed & donated

I'm using the english, french and spanish translation (home language is german).
My problem is, I'm using my brand name in title and at the french language translate it.

Any idea how to fix that? Maybe a blacklist for words not to translate?

Just use not translated area See mod description - details in features list

[NLP-er]

Originally Posted by imported_silkroad

Where is this in the Google TOS?

I just checked the API, and there was no text in the TOS requiring a logo, only "Powered by Google".

Please provide a link to the TOS where a logo is also required. Thanks.

Below you will find mail from Google to one site which was blocked because of not fitting into Google TOS. You can set your flags description as you want (that's why I made it configurable ) - I only give suggestions which in my mind are the best for users of my mod

Originally Posted by google

Thanks for clarifying your usage of the API. I should be able to get your site unblocked momentarily.

Please draw your attention to our terms of use:
http://code.google.com/apis/ajaxlanguage/terms.html

Specifically, I wanted to make sure that you're aware that you're only allowed to cache results for up to 15 days - no translations should be stored on your servers beyond that period, without being refreshed. Also, please notice the requirements regarding attribution. I appreciated that you've included a note at the bottom that translations are powered by Google, but you should also include "Powered by Google" branding on every page that includes translations from the API so that it's clear that the current text is machine translated. The API will provide this branding automatically:
http://code.google.com/apis/ajaxlang...tion/#Branding

[imported_silkroad]

Originally Posted by NLP-er

Below you will find mail from Google to one site which was blocked because of not fitting into Google TOS. You can set your flags description as you want (that's why I made it configurable ) - I only give suggestions which in my mind are the best for users of my mod

Yes, that email from Google clearly points to the same TOS as I posted and no where in Google's email or TOS do they require the Google logo.

That is why I am confused because you said there was a "change in the TOS" but there has been no change in the Google TOS.

Also, you said that Google requires their logo or that they will ban the user. That is also not correct. Google's TOS does not require a logo. It requires "Powered by Google." (text).

Having said that... the Google logo is very nice and we use it

Also, there is nothing in the Google TOS that requires a referral header during database queries.

[imported_silkroad]

Originally Posted by NLP-er

Important change! According to new Google conditions referrer header must be added to each translation query - otherwise you can be banned by Google.

This is not in the Google TOS (sorry to correct you). So, this statement is not correct. In addition, when Google blocks access to their API this is not "banned by Google" ... it is called "blocked to use the API".

Originally Posted by NLP-er

Also according to actual Google conditions your "Powered by Google" information should have Google logo

Sorry, but this is also incorrect. There is no text in the Google TOS that requires the use of their logo. I am confused why you post incorrect information like this. You are normally accurate. Google's TOS has not changed. There is no requirement in the same TOS for referral headers and no requirement for a logo.

It might be "good" or "nice" to add the logo, but it is certainly not required by the "actual Google conditions" (and you said).

This is unlike you NPL-er !! You are normally very factual. Are you under some stress or pressure?

Take it easy!!!

[Kolbi]

Originally Posted by NLP-er

About Sitemap Generator - try to disable generation of some links (i.e. for members pages). No other hints - it is not my product, so have no idea what else you could do. Maybe change number of links to even less. This is first time when somebody have an issue with this (as I remember ). Maybe some logs are created?...

I tried to reduce the links. Perhaps my server is really the problem
It really a little bit overloaded.

[Audax666]

Thanks for the help.
Everything is fine now. :up:

[NLP-er]

Originally Posted by imported_silkroad

Yes, that email from Google clearly points to the same TOS as I posted and no where in Google's email or TOS do they require the Google logo.

When I see direct recommendation given to forum which was already banned, then I prefer to give good advice to all my users and apply myself, than discuss with Google how they should interpret their own TOS after they ban my page It is simple matter of avoid potential issues which can take much more time that just change configuration of one parameter. + and -... I see much more + in applying to Google request

Also please take attention that there was 2 links. And under this one (http://code.google.com/apis/ajaxlang...tion/#Branding) you can find:
When your application uses the Google AJAX Language APIs, it is important to communicate the Google brand to your users

And of course you can discuss that vBET is not using Google AJAX API, but CURL, and you can discuss that it is recommendation, but what for waiting till Google ban your forum to make this discussion?...

Originally Posted by imported_silkroad

That is why I am confused because you said there was a "change in the TOS" but there has been no change in the Google TOS.

Yes you have completely right - it is not in TOS
Sorry for confusion.

Originally Posted by imported_silkroad

Also, you said that Google requires their logo or that they will ban the user. That is also not correct. Google's TOS does not require a logo. It requires "Powered by Google." (text).

See the source - you have answer from Google to forum which was already banned. I'm just the messenger here - do not shut the messenger. Go to message author if you want to discuss the issue - go to Google. I simply cannot be responsible and cannot explain others position. So if you think that Google interpret wrong their own TOS - please contact Google for explanation.

At this moment I have information straight from Google that "Powered by Google" should include the logo and I will fit it in default configuration. Every user can make own decision about keeping it or not - it is configurable I will not put my users in risk to be banned because of unclarity in TOS or wrong understanding of TOS by Google own personnel if I have simple way to avoid any potential issues in this area. This is how I manage the risk. Sorry for confusion - I didn't read whole TOS from the begging - I just used information straight from Google, and still I think that it is wiser to set Google logo than put yourself in the risk of being banned.

Originally Posted by imported_silkroad

Having said that... the Google logo is very nice and we use it

Great

Originally Posted by imported_silkroad

Also, there is nothing in the Google TOS that requires a referral header during database queries.

First of all - it is not about database queries (there are no headers), but about HTTP GET queries to Google service. And you are wrong about referral header.
You assumed that all conditions are in one place - and this is not safe assumption. You can find TOS on other pages too - this particular you will find here:
http://code.google.com/intl/pl-PL/ap...l#_intro_fonje

"Applications MUST always include a valid and accurate http referer header in their requests."

Big letters in MUST are not added by me - it is written this way in Google documentation, so i think that clearly marks Google position in this area

[NLP-er]

Originally Posted by imported_silkroad

This is not in the Google TOS (sorry to correct you). So, this statement is not correct.

I see no problem in correcting
Also you are wrong about referral header. You assumed that all conditions are in one place - and this is not safe assumption. You can find TOS on other pages too - this particular you will find here:
http://code.google.com/intl/pl-PL/ap...l#_intro_fonje

"Applications MUST always include a valid and accurate http referer header in their requests."

Big letters in MUST are not added by me - it is written this way in Google documentation, so i think that clearly marks Google position in this area

Originally Posted by imported_silkroad

In addition, when Google blocks access to their API this is not "banned by Google" ... it is called "blocked to use the API".

Different word - same meaning and same results. And I think that everybody understood it correctly.

BTW - Are you a lawyer? I'm looking one, because some guy stole my code, and I see that you like to use exact words, even if substitute has same meaning, so I thought that maybe you can help me with my issue If yes please PM me - thanks:up:

Originally Posted by imported_silkroad

Sorry, but this is also incorrect. There is no text in the Google TOS that requires the use of their logo. I am confused why you post incorrect information like this. You are normally accurate. Google's TOS has not changed. There is no requirement in the same TOS for referral headers and no requirement for a logo.

I'm confused why you are still confused - you get exact answer from Google. So if you think they are wrong, please contact them and discus their position. I cannot tell you why they interpret it in such way. But I can tell you that not applying you put yourself in a risk to be banned ("blocked to use the API"). And if you want to know why I give this information to my user, then the answer is very simple: because I care about my users

So is there really any issue or it is only about using exact words from documentation and being better in reading it?
You are better and I still care about my users, so my recommendation is still the same - use Google logo

Reading 2 posts in row about the same + PM, I get impression that it is only about proving some point and It has totally no reflection in reality since you applied Google logo yourself. So what is the real point here, and can we close it?

Originally Posted by imported_silkroad

It might be "good" or "nice" to add the logo, but it is certainly not required by the "actual Google conditions" (and you said).

Yes I said.

Originally Posted by imported_silkroad

This is unlike you NPL-er !! You are normally very factual. Are you under some stress or pressure?

Stress - not at all. Pressure - of course yes. Every second counts when my users are in danger of being banned ("blocked to use the API" - sorry, but banned is just simpler ), so I made all changes, made tests and give people what makes them safe as fast as I could. I didn't thought to discuss with Google about wrong TOS interpretation by their own staff.

Truly saying I still don't see the point - what is the point of having right when you loose and your forum is banned?...

When people are with me, they are with the man who thinks how to win...

Sounds like commercial haha

Originally Posted by imported_silkroad

Take it easy!!!

Booth way?...

[NLP-er]

Originally Posted by Kolbi

I tried to reduce the links. Perhaps my server is really the problem
It really a little bit overloaded.

You know it best Just play with configuration - vBSEO stuff make really good generator and there is lot of configuration possibilities.
Always you can just remove from sitemap some translations or all of those - at the end spiders will find it by links on forum, but you have less control then and it can take longer (i think ).

[NLP-er]

Originally Posted by Audax666

Thanks for the help.
Everything is fine now. :up:

Great to hear HAVE FUN with vBET!!! :up: