I'd just figured out a few days ago that the author was using T_ as:
T_('Put any kind of text you want here'), in conjunction with get-text, which serves as a general translator.
---
so, if your default language was English and the code snippet looked thus:
Code:
T_('How is the weather today?')
it would be displayed as:
Code:
T_('Wie ist das wetter huete?')
after selecting the german language file (provided, of course, that there is actually a german language file to choose from)
.
.
.
This is my first time encountering get-text.
Myself personally, I favour the way i've seen this same thing done in just about every script i've ever seen...
You have a lang file for each language, and instead of writing something like: T_('How is the weather today?')
you just call a variable like: $weather_greeting
which is referenced in a (selected) lang file.
.
.
.
This is, however, what get-text does.
Except, with get-text, there is a bit too much code being written to handle such a simple task. The "saving" point, if we can call it that- is that it stores all of these values in a .MO file- which is great for execution speed.
However, the cache-22 on this is that; for something this simple, it's really not necessary at all to look forward to this .MO file's execution speed when you can just make a simple variable call to a generic lang file.