Translating SQL has a high likelihood of inducing unrecoverable error. The translation parser already just *barely* works as it is for HTML::Template::Pro files. I wouldn't trust it, or extending a custom tangle of code like it to handle a totally different language in files that are necessary to even begin installation.
-- Joe Atzberger LibLime - Open Source Library Solutions On Wed, Jul 29, 2009 at 11:04 AM, Michael Hafen <mdha...@tech.washk12.org>wrote: > Would it be possible to have the current translation process include the > SQL files. Then it's just a matter of having the .po files parsed prior > to packaging a release, and have the SQL files for other languages > created that way. > > There would probably need to be a user defined function in the database > for _(), as that is what the translation script watches for as I > understand it. > > On Wed, 2009-07-29 at 15:12 +0200, Zeno Tajoli wrote: > > Hi Ricardo and all, > > > yes, the only fields to translate in Unimarc/MARC21 SQL files > > are liblibrarian and libopac. > > > > But how can we do the translation ? > > This is a problem that sometime appers in this list. > > > > I try to find a solution or an open source tool, but I never found a > solution > > > > Bye > > > > Zeno Tajoli >
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
