On Jul 22, 8:39 am, lyba wrote:
> I am only concerned with files generated by a console for reasons
> stated above.
>
> I suspect it's easy to ignore the problem if you do not experience it.
> It is possible that I am in minority and such decisions is justified.
>
> However, I would ask all subs
The bake templates should be saved as utf-8 encoded files with LF line
endings. Currently vim is showing the bake template files as utf-8
with Unix file endings, which is expected and correct. Perhaps the
problem is your tool/editor and not the file.
-Mark
On Jul 21, 3:09 am, lyba wrote:
> Hi,
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
I am only concerned with files generated by a console for reasons
stated above.
I suspect it's easy to ignore the problem if you do not experience it.
It is possible that I am in minority and such decisions is justified.
However, I would ask all subsequent readers to cast a vote in this
topic whe
yes:
- windows
- only baked files
I am only concerned with files generated by console as there are
always a lot of them and during development very often I do not work
with PO files hence very often I will place comments directly in
views, validation messages in model files
On Jul 21, 9:15 am, Ho
where will you start? and where end?
there are css files which need different commenting chars as js or php
or html for that matter
it will make the code look more ugly in my opinion.
a year ago i used to have the exact same trouble accepting a simple
fact: it simply isn't worth the act
at that t
I assume you're using Windows in this case ? And the files you're
talking about are generated by the console ?
On Jul 21, 9:09 am, lyba wrote:
> Hi,
>
> Cake bake (1.3.x recently tried 2.0.) generates files as no utf-8
> files.
>
> To be precise they can be interpreted as utf-8 files but since t
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
i must say - quite a bit of work for nothing
you said it yourself: as long as there is no utf8 character those
files are identical, no matter if they are saved as ansi or utf8
and that is actually the case. they are 100% the same. so there is no
need to go through them and manually set those files
Hi,
Cake bake (1.3.x recently tried 2.0.) generates files as no utf-8
files.
To be precise they can be interpreted as utf-8 files but since they do
not contain utf-8 character they in fact are pure ANSI encoded files.
The result is that when I open any view file for editing and type
utf-8 chara
10 matches
Mail list logo
