whoo ... this one's a doozy....
There are two parts to Realspeak: we call them the "base files" and the "language files". You need both parts to have TTS. The "base" files are shared among all languages, while the "language" files are specific to a language. (Now you know why we call them that. ;-)
The problem is that both of these have a version number. So your base files can be at version X and your languages files can be at version Y. (If you have a multilingual Unity, each language can be at a different version too -- ENU can be at version A while DEU can be at version B, etc. It gets real messy real fast!)
To make matters worse yet, Realspeak has an "internal" version number and an "external" version number. The internal number is what appears on all their dll's. The external number is what they tell folks like us. (And what we then tell you.) The reason we don't use the internal number is that not all of their dll's have the same internal number at one release. In fact, not all of their files even have an internal number.
The more important of the two is the base file version. I'll give you a mapping below of the version reported by a particular dll to the "external" version number of the release. Find the file: commserver\realspeak\api\lib\lhstts.dll
Then look at the file version number. If it says:
2.1.0.0, you have "Realspeak 2.01"
2.11.0.0, you have "Realspeak 2.11"
2.12.0.0, you have "Realspeak 3.00"
2.13.0.0, you have "Realspeak 3.01"
This is what we generally mean when we say "Realspeak 3.01".
There's a separate table like that for each language, but we usually don't talk about the language version as the "Realspeak version". Just the base version. Let me know if you're still interested and I can try to dig language tables up as well... though I don't think we maintain them so well.
Michael Kale, mkale@cisco.com
