RE: [PEAR-DEV] RE: yet another template

Dear all, I personally needed template engine that could handle Japanese safely. I tried XSLT first, but designer at my client company complained it was too complex and couldn't handle with off the shelf Home Page editor they had. So I start writing my class. My personal requirements were: handle muti-byte text output plaintext for email and HTML for web low overhead template should be modified by off the shelf Home Page editor template syntax easily understood by novice web designer. I am currently trying to add a new feature that would allow my class to parse the template to php code and save it for reuse. I agree with standardization and I do not intend to create new language or anything. It's just that I didn't find what I needed and I wrote it myself. Finally, I post it here to see if my class fits somebody else's requirement and might help things out. Questin would be to choose one from these two: Making standard template syntax for PEAR or Choosing already standardized syntax availlable today. Or maybe think up some radical way to separate presentation from logic? Best regards, Naoki Shima