From: Katharina W. <wol...@fh...> - 2012-05-29 11:54:52
|
Hi Oliver, I've managed to find the translate()-function in the vufind-documentation. ;-) I'm afraid that this function (though good to know of it) wouldn't help me solve my current problem, since it only translates _into_ the language currently defined in web/conf/config.ini (for me that would be from English into German) whereas I need translation from my current language _into_ English, so that vufind in turn can translate the "term/phrase" into whatever language I want to display. I think it would be nice if vufind were to be able to translate in both directions (from English into the local language and from the local language into English), but at the moment, that isn't the case. Perhaps that would be something for vufind 2.x? Kate Am 29.05.2012 12:26 schrieb Oliver Goldschmidt: > Hi Katharina, > > I think there is no need for another translation method located in the > driver or anywhere else. There are already two places to make > translations: at the driver or (IMO the better place for something like > that) in the template. Vasek showed the place where to translate terms > in the template (its just a smarty function). > >>From my understanding translation works this way: the term originally > recieved by the ILS-driver is set into the frontend. If the driver > translates it (using $foo->translate()), the term is presented > translated. The template takes the term recieved by the record driver > (which is calling the template). On this level the translate method > might be called again (using {$foo|translate}). > > It maybe good to see the strings the driver returns as variable names, > not as terms. These variables can be translated in any language using > the ini files. So your driver could send any variable name you want and > there is no need to set a (translated) term. > > Hope that helps! > Oliver |