On Mon, Dec 29, 2008 at 9:15 AM, Ryan Higgins wrote:
> I intend to submit a patch this week that will add an include to the
> staff side: base-js.inc , which includes js that needs to be processed
> by H::T::P. It will include a global 'koha' object, which could store an
> array of strings for tr
I intend to submit a patch this week that will add an include to the
staff side: base-js.inc , which includes js that needs to be processed
by H::T::P. It will include a global 'koha' object, which could store an
array of strings for translation. If accepted, the same could be done
for the opac.
The convention is to use _(), BUT tmpl_process doesn't parse the ".js"
files. So they're not putted in po translation files and translators
cannot translate them.
Only
I think the convention has been to use the underscore function to designate
translatable string literals like:
alert( _("Error: barcode empty!") );
Whether that is actually working or not, I'll have to leave for someone else
to answer.
--Joe
On Mon, Dec 29, 2008 at 10:25 AM, Nahuel ANGELINETTI w
Hi all,
We saw the javascript files(.js) are not translated. In fact,
only .tmpl and .inc strings are exported in po files.
Some developers added some strings to be translated in javascript files
(Like "Cart" button in OPAC), so when we translate in french, there is
no translation for those string
