How does smarty deal with unicode, specifically UTF-8 templates and
passed string vars? Does it "just work", or are there steps I need to
take to make it happen?

Also does anyone have any links to articles on converting projects
from 8-bit encodings to unicode? I've not found anything that's much
good so far.

Marcus
--
Marcus Bointon
Synchromedia Limited: Putting you in the picture
marcus@synchromedia.co.uk | http://www.synchromedia.co.uk

I believe your PHP and HTML will drive how well UTF-8 works. Smarty
doesn't care what encoding is used. If your template is UTF-8, then be
sure your assigned template vars are UTF-8 too.

Marcus Bointon wrote:

> How does smarty deal with unicode, specifically UTF-8 templates and
> passed string vars? Does it "just work", or are there steps I need to
> take to make it happen?
>
> Also does anyone have any links to articles on converting projects
> from 8-bit encodings to unicode? I've not found anything that's much
> good so far.
>
> Marcus

On 28 Feb 2006, at 17:28, Vicente Werner wrote:

> My experience is that it just works, no need to do anything -I made
> a BIG, BIG proyect on it- the main issue with unicode, it's not
> smarty, it's PHP itself.
> PHP has a terrible problem with it, since it's not supported
> natively and the mb extension just sucks -in order to be useable it
> should be a full replacement for all string related functions,
> which is not

Yup, I've been keeping tabs on the progress of PHP 6, and I watched a
database system do the big switch a couple of years ago. Given the
lack of unicode safety in PHP, I would expect to run into problems
with things like modifier plugins - all it takes is a single
preg_replace or str_replace and it's going to break, so I was
wondering how you go about ensuring that doesn't happen.

Marcus
--
Marcus Bointon
Synchromedia Limited: Putting you in the picture
marcus@synchromedia.co.uk | http://www.synchromedia.co.uk

On 28 Feb 2006, at 17:57, Vicente Werner wrote:

> Regex don't even work, so if you're goin' to use regular
> expressions, you're out of luck for non latin languages

So given that it apparently does work, is it therefore true that the
Smarty compiler and all standard plugins are regex-free?

Marcus
--
Marcus Bointon
Synchromedia Limited: Putting you in the picture
marcus@synchromedia.co.uk | http://www.synchromedia.co.uk

On Tue, Feb 28, 2006 at 06:07:32PM +0000, Marcus Bointon wrote:
> On 28 Feb 2006, at 17:57, Vicente Werner wrote:
>
> >Regex don't even work, so if you're goin' to use regular
> >expressions, you're out of luck for non latin languages
>
> So given that it apparently does work, is it therefore true that the
> Smarty compiler and all standard plugins are regex-free?

no. first of all: all plugins that care about encoding (like
capitalize, lower or truncate) may not (or very likely won't) work.

regearding regexes: i don't see a problem why an ascii reges shouldn't
match on utf-input. if you stick to ascii with with your variable
names and identifiers, then utf-8 templates should be transparent to
smarty.

> Marcus
> --
> Marcus Bointon
> Synchromedia Limited: Putting you in the picture
> marcus@synchromedia.co.uk | http://www.synchromedia.co.uk
>
> --
> Smarty General Mailing List (http://smarty.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEBKjIubKPpFA4n0URAhXDAJ42BaYcYr9wTyHiZsGbiI y2G6XA3ACgg355
cmGoerYLlxNEa/0wwx2tX6c=
=xXAk
-----END PGP SIGNATURE-----

--- Marcus Bointon <marcus@synchromedia.co.uk> wrote:
> On 28 Feb 2006, at 17:57, Vicente Werner wrote:
> > Regex don't even work, so if you're goin' to use regular
> > expressions, you're out of luck for non latin languages
>
> So given that it apparently does work, is it therefore true that the
> Smarty compiler and all standard plugins are regex-free?

I'm not following this discussion but that statement is fallacious -- Smarty is
very much built on regex parsing. perhaps the problem is defining "it works".


xo boots

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

---------- Forwarded message ----------
From: Vicente Werner <vwerner@gmail.com>
Date: Mar 1, 2006 9:06 AM
Subject: Re: [SMARTY] Smarty and Unicode
To: messju mohr <messju@lammfellpuschen.de>

Regex's in PHP5.x or lower don't work correctly for UTF-8 strings, it does
match correctly ascii chars, but not UTF-8 ones (despite claiming support
for it..) it won't be ready and fully useable until PHP-6.


On 2/28/06, messju mohr <messju@lammfellpuschen.de> wrote:
>
> On Tue, Feb 28, 2006 at 06:07:32PM +0000, Marcus Bointon wrote:
> > On 28 Feb 2006, at 17:57, Vicente Werner wrote:
> >
> > >Regex don't even work, so if you're goin' to use regular
> > >expressions, you're out of luck for non latin languages
> >
> > So given that it apparently does work, is it therefore true that the
> > Smarty compiler and all standard plugins are regex-free?
>
> no. first of all: all plugins that care about encoding (like
> capitalize, lower or truncate) may not (or very likely won't) work.
>
> regearding regexes: i don't see a problem why an ascii reges shouldn't
> match on utf-input. if you stick to ascii with with your variable
> names and identifiers, then utf-8 templates should be transparent to
> smarty.
>
> > Marcus
> > --
> > Marcus Bointon
> > Synchromedia Limited: Putting you in the picture
> > marcus@synchromedia.co.uk | http://www.synchromedia.co.uk
> >
> > --
> > Smarty General Mailing List (http://smarty.php.net/)
> > To unsubscribe, visit: http://www.php.net/unsub.php
>
>
>


--
Vicente Werner y Sánchez


--
Vicente Werner y Sánchez

On Wed, Mar 01, 2006 at 09:12:44AM +0100, Vicente Werner wrote:
> ---------- Forwarded message ----------
> From: Vicente Werner <vwerner@gmail.com>
> Date: Mar 1, 2006 9:06 AM
> Subject: Re: [SMARTY] Smarty and Unicode
> To: messju mohr <messju@lammfellpuschen.de>
>
> Regex's in PHP5.x or lower don't work correctly for UTF-8 strings, it does
> match correctly ascii chars, but not UTF-8 ones (despite claiming support
> for it..) it won't be ready and fully useable until PHP-6.

correct. but the smarty syntax is ascii and not utf-8. the regexes
correctly match the stuff inside {} and correctly ignore the stuff
outside {}.

> On 2/28/06, messju mohr <messju@lammfellpuschen.de> wrote:
> >
> > On Tue, Feb 28, 2006 at 06:07:32PM +0000, Marcus Bointon wrote:
> > > On 28 Feb 2006, at 17:57, Vicente Werner wrote:
> > >
> > > >Regex don't even work, so if you're goin' to use regular
> > > >expressions, you're out of luck for non latin languages
> > >
> > > So given that it apparently does work, is it therefore true that the
> > > Smarty compiler and all standard plugins are regex-free?
> >
> > no. first of all: all plugins that care about encoding (like
> > capitalize, lower or truncate) may not (or very likely won't) work.
> >
> > regearding regexes: i don't see a problem why an ascii reges shouldn't
> > match on utf-input. if you stick to ascii with with your variable
> > names and identifiers, then utf-8 templates should be transparent to
> > smarty.
> >
> > > Marcus
> > > --
> > > Marcus Bointon
> > > Synchromedia Limited: Putting you in the picture
> > > marcus@synchromedia.co.uk | http://www.synchromedia.co.uk
> > >
> > > --
> > > Smarty General Mailing List (http://smarty.php.net/)
> > > To unsubscribe, visit: http://www.php.net/unsub.php
> >
> >
> >
>
>
> --
> Vicente Werner y Sánchez
>
>
> --
> Vicente Werner y Sánchez

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEBVslubKPpFA4n0URAkdeAJ0dH2ud0aBNNFq6WPWgH3 aFIFPuSwCfQXHr
/hji3ss3B2aOi1XLF1NBi1E=
=BPJY
-----END PGP SIGNATURE-----