Chan Min Wai (dcmwai) asked how to print the UTF-8 grd and the utf-8 db(printing on an html files or PDF files). He was talking about the month2.grd which all unicode is UTF-8 when using grcvs to get and html /pdf the output isn't utf-8. Jan Ischebeck (siesel) solved the problem by correcting pdf.py for pdfs and setting textEncoding=utf-8 in gnue.conf [common] section.

Reinhard Müller (reinhard) announced that common, forms, designer, and reports have made it into sarge, appserver and navigator have entered sid. Thanks to Jeff Bailey!!!

Jan Ischebeck (siesel) announced he was beginning to split the GTrigger code into language specific and trigger specific parts to achieve two goals: 1. make it easy to reuse from appserver 2. add new trigger languages. He of course has faced some problems - a naming issue: what about putting the language specific stuff in subdirectorys of gnue/common/logic/connector like gnue/common/logic/connector/python/. The "connector" was chosen as "language connector". James Thompson (jamest) noticed that connector makes me think of networking for some reason, same could be said for logic/interface. Jan thought of adding a "remote connector" which calls the trigger on the application server. Nothing application specific should go in there. James liked the split idea.

Another problem - namespace issue - the namespace stuff is very python specific. So we'd end up with a generic trigger system that manages triggers.

On mailing list Jan announced available support for ECMAscript triggers, support for C# is planned.

Jan Ischebeck (siesel) said he had stopped using TriggerError, as it would be "Trigger" specific. He had named it to LangIfError, like Language Interface Error. if an error in a trigger /procedure occurs it raises an XXX Error, which is catched by the Language Interface and replaced with a LangIfError. Depending on the time the error occurs its an LangIfRuntime or an LangIfCompileError which are both inheriting LangIfError, so you just have to name it in an except statement.