Hello Yannis Your system must have the specified locale installed, or else the setlocale function won't work. You can check whether it's working or not by doing this:
$l = 'es_ES'; echo "trying to set locale to $l..."; $x = setlocale( LC_ALL, $l ); echo $x ? "locale successfully set<br>" : "couldn't set locale<br>"; In linux, you can check the installed locales by typing, in the terminal # locale -a or by listing the contents from /usr/share/locale/locale.alias (ubuntu) (Don't know how to do it on Windows ou OSX, sorry). The $l variable in the example above should be _exactly_ as listed in the command above, or else setlocale will fail. Hope that helps, dfcp On Jul 29, 7:34 am, Yannis <[email protected]> wrote: > Thank you guys, > > Djogo, what exactly do you mean here?? > > > - check if the locale is installed in your system. sometimes it's > > lang.encoding, like pt_BR.UTF-8 instead of pt_BR > > Where do I check that? > > On Jul 28, 2:33 pm, djogo <[email protected]> wrote: > > > Hey > > > I spent many time trying to figure out how to make i18n work... I'm > > not following this topic realtime, but I'd like to post some tips that > > would really had helped me back then: > > > - always use utf-8, no matter what's the language you're i18ng > > - check if the locale is installed in your system. sometimes it's > > lang.encoding, like pt_BR.UTF-8 instead of pt_BR > > - do not use non-ascii (?) characters in the source code messages. > > like, _("Tá certo") won't work with gettext. You'll probably want to > > use _("Ta certo") > > - for that reason, if your main language is not english or something > > that doesn't use non-ascii characters, you'll need to "translate it" > > if you want to display the correct words > > - it's frustrating to try to change the .mo files real-time, as you'll > > need to reload apache (or whatever) everytime. the reason is that > > apache likes to keep .mo files cached, and won't reload it unless you > > shut it down and start it again. > > > that's all I remember for now. hope it helps. fell free to contact me > > pvtly. > > > dfcp > > > On Jul 28, 5:37 am, leop <[email protected]> wrote: > > > > I can't see what is causing the problem, but it is a warning rather > > > than an error. It seems to indicate that the code executed okay, but > > > the headers had already been sent. If you have copied & pasted the > > > code, you may have picked up a space after the ?> in p28n.php (I see > > > by swiping the code that there is one in my fragment). > > > > L > > > > On Jul 28, 7:29 am, Yannis <[email protected]> wrote: > > > > > Hi leop, > > > > > Thanks for the code. I've used it but I get the following error: > > > > Warning (2): Cannot modify header information - headers already sent > > > > by (output started at .../config/routes.php:49) [CORE/cake/libs/ > > > > controller/components/cookie.php, line 364] > > > > > If that rings any bell?!?! > > > > > Looks like the line that is causing this is the p28n.php: > > > > $this->change(($this->Cookie->read('lang') ? $this->Cookie->read > > > > ('lang') : 'eng')); > > > > > Have you had that? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
