Another thing is the performance and translation itself. Nearly all big Open Source projects are using gettext and I see no reason why we should move away from the actual state-of-the-art system. Even KDE with much more strings than OpenCA uses gettext. What happens if the database fails? The GNU stuff of gettext is always available.

Any arguments why we should invest the time in an own system?

I agree with Michael - espacially I think the load on the database will grow rapidly when we use it for translation issues. Gettext is a proven system, even if not a perfect one...we should not waiste ressources on this issue - at leat it will create new bugs when we exchange the translation system

Oliver
--
Diese Nachricht wurde digital unterschrieben
oliwel's public key: http://www.oliwel.de/oliwel.crt
Basiszertifikat: http://www.ldv.ei.tum.de/page72

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



Reply via email to