Friday, July 22, 2011

Re: utf8 in bake

I barely understand what are you talking about but can say one major
thing: there should NO be BOM mark in ANY file. For PHP it's just data
outside code and it will be outputed. Output of this excess character
cause not set headers and doctype ignorance in some browsers.

If you so worry about your editor treat source files as ANSI just set
there UTF-8 as default encoding. Problem solved with minimal efforts.
It works for me and everyone I work with for 5 years already.

On Jul 21, 5:31 pm, lyba <l...@poczta.fm> wrote:
> I am not sure if utf-8 encoding is/should be default but if the answer
> is yes
> then placing an utf-8 character in the template file (4 of them) that
> come with the cake
> installation package would neither be a big work nor for nothing as
> many
> countries use specific utf-8 characters and quite a few of them work
> in Windows.
>
> There are comments in all baked files so it will have no impact on
> anything.
> Even if people use ANSI not utf-8 the file with corrupted utf
> character in the
> source code comment will change nothing.
>
> Few months back when I researched the problem I found quite a few
> references
> on the internet where people had the same problem. Of course it can be
> ignored
> as strings will come from PO files and comments in source code will
> not matter.
>
> But if this is such a small issue as placing 1 extra character in 4
> files then why not do it?
>
> Unless there is a different way to overcome the problem? Anyone?

--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.


To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate