|
From: Karsten D. <k.d...@tu...> - 2001-03-26 18:44:19
|
On Mon, Mar 26, 2001 at 02:41:50PM +0200, Karsten Dambekalns wrote: > impact on speed. But I would use a different scheme. I would include the > appropriate language file, which would contain statements like > $TRANSLATE["xxx"]=3D"fgdsfhsk"; OK, I did that. I am able to produce an appropriate sed file and the corresponding *.lang files. > This way we could introduce this very easily into the existing code base.= In > fact I am going to code this, and make it available as one more "language" > when running makedistro.sh. Does anyone object on this? I think we should= at > least try this... Here I have been too fast. It is in fact easy to let sed do the work. But there are 2 cases: 1. We have something like echo "TRANSLATE[[Login]]" This could be replaced by echo "".$TRANSLATE["Login"]."" very easily, and all should be well. But this would break if there was one statement like echo TRANSLATE[[something]] (note the missing quotes) which is unlikely (I think) but would come out of the process as echo "$TRANSLATE["something"]" (note the wrong quotes) All in all not very nice, but it would work (read: until we have a better solution) 2. We have something like <?php ... ?> <p>TRANSLATE[[Login]]</p> <?php ... ?> Now this breaks about everything. This doesn't work. Sigh. Please consider my steeping forward to be grinded to a unwanted halt. That is - unless someone has a very bright idea... besides seperating code and presentation very cleanly. Regards, Karsten --=20 Why do we have to hide from the police, daddy? Because we use emacs, son. They use vi. ----------------------------- mailto:k.d...@tu... w=B3: http://www.k-fish.de/ gpg: http://www.k-fish.de/mykeys.gpg |