Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #5494 > unrolled thread

session question

Back to article view | Back to comp.lang.php

Contents

  session question William Gill <noreply@domain.invalid> - 2012-04-12 12:43 -0400
    Re: session question Scott Johnson <noonehome@chalupasworld.com> - 2012-04-12 09:56 -0700
    Re: session question "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-04-12 19:43 +0200
    Re: session question "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-04-12 19:59 +0200
    Re: session question Captain Paralytic <paul_lautman@yahoo.com> - 2012-04-13 02:18 -0700
    Re: session question Denis McMahon <denismfmcmahon@gmail.com> - 2012-04-13 13:27 +0000
      Re: session question William Gill <noreply@domain.invalid> - 2012-04-13 13:51 -0400
        Re: session question Jerry Stuckle <jstucklex@attglobal.net> - 2012-04-13 15:54 -0400
        Re: session question William Gill <nospam@domain.invalid> - 2012-04-20 02:40 -0400
          Re: session question "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-04-20 10:55 +0200
          Re: session question Erwin Moller <erwinmollerusenet@xs4all.nl> - 2012-04-20 11:25 +0200
          Re: session question Jerry Stuckle <jstucklex@attglobal.net> - 2012-04-20 08:11 -0400
            Re: session question William Gill <noreply@domain.invalid> - 2012-04-20 10:59 -0400
              Re: session question William Gill <noreply@domain.invalid> - 2012-04-20 11:32 -0400
              Re: session question Michael Fesser <netizen@gmx.de> - 2012-04-20 17:50 +0200
                Re: session question William Gill <nospam@domain.invalid> - 2012-04-20 12:04 -0400
                  Re: session question Tim Streater <timstreater@greenbee.net> - 2012-04-20 18:17 +0100
                    Re: session question "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-04-20 20:08 +0200
                      Re: session question Tim Streater <timstreater@greenbee.net> - 2012-04-20 20:36 +0100
                        Re: session question William Gill <nospam@domain.invalid> - 2012-04-21 18:13 -0400
                  Re: session question Jerry Stuckle <jstucklex@attglobal.net> - 2012-04-20 14:22 -0400
                    Re: session question William Gill <nospam@domain.invalid> - 2012-04-20 15:04 -0400
                      Re: session question The Natural Philosopher <tnp@invalid.invalid> - 2012-04-20 22:09 +0100
                    Re: session question Michael Fesser <netizen@gmx.de> - 2012-04-20 21:13 +0200
                      Re: session question Jerry Stuckle <jstucklex@attglobal.net> - 2012-04-20 15:45 -0400
                        Re: session question Tim Streater <timstreater@greenbee.net> - 2012-04-20 23:11 +0100
                          Re: session question The Natural Philosopher <tnp@invalid.invalid> - 2012-04-20 23:23 +0100
                            Re: session question Tim Streater <timstreater@greenbee.net> - 2012-04-21 13:14 +0100
                          Re: session question Jerry Stuckle <jstucklex@attglobal.net> - 2012-04-20 18:45 -0400
                          Re: session question Michael Fesser <netizen@gmx.de> - 2012-04-21 01:24 +0200
                            Re: session question The Natural Philosopher <tnp@invalid.invalid> - 2012-04-21 01:28 +0100

Page 2 of 2 — ← Prev page 1 [2]

#5605

On 4/20/2012 12:04 PM, William Gill wrote:
> On 4/20/2012 11:50 AM, Michael Fesser wrote:
>> .oO(William Gill)
>>
>>> I know what the documentation says, and I know what's actually
>>> happening. I have checked "my code"
>>>
>>> from the test page:
>>>
>>>
>>> <?php session_start(); ?>
>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
>>> "http://www.w3.org/TR/html4/strict.dtd">
>>>
>>> the first 5 characters in the file are "<?php".
>>
>> Are you using UTF-8? Then there might be a BOM at the very beginning of
>> the file.
>>
>> Micha
>>
> And we have a winner ladies and gentlemen!
>
> Thank you very much Micha, at my age pulling my hair out isn't recommended.

IOW, you screwed up and the others here were right.  <?php was NOT the 
first thing in your file!

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#5606

On 4/20/2012 2:22 PM, Jerry Stuckle wrote:
> IOW, you screwed up and the others here were right. <?php was NOT the
> first thing in your file!
>
Right Jerry.  I will remember how finely we should split hairs when 
examining future posts.

Of course if I was as smart as you, I wouldn't have had to ask for any 
help in the first place.

Note to self: Only the Pope and Jerry are infallible, but the Pope is 
limited to "matters of faith", Jerry has no such restriction.

[toc] | [prev] | [next] | [standalone]

#5612

William Gill wrote:
> On 4/20/2012 2:22 PM, Jerry Stuckle wrote:
>> IOW, you screwed up and the others here were right. <?php was NOT the
>> first thing in your file!
>>
> Right Jerry.  I will remember how finely we should split hairs when 
> examining future posts.
> 
> Of course if I was as smart as you, I wouldn't have had to ask for any 
> help in the first place.
> 
> Note to self: Only the Pope and Jerry are infallible, but the Pope is 
> limited to "matters of faith", Jerry has no such restriction.

+1

-- 
To people who know nothing, anything is possible.
To people who know too much, it is a sad fact
that they know how little is really possible -
and how hard it is to achieve it.

[toc] | [prev] | [next] | [standalone]

#5607

.oO(Jerry Stuckle)

>IOW, you screwed up and the others here were right.  <?php was NOT the 
>first thing in your file!

But this issue is not the most obvious, so you can't blame it on him.
Some editors store a BOM without giving notice, others hide such
settings somewhere deep in the preferences.

Hopefully this problem will completely vanish with native Unicode
support in PHP 6.

Micha

-- 
http://mfesser.de/blickwinkel

[toc] | [prev] | [next] | [standalone]

#5610

On 4/20/2012 3:13 PM, Michael Fesser wrote:
> .oO(Jerry Stuckle)
>
>> IOW, you screwed up and the others here were right.<?php was NOT the
>> first thing in your file!
>
> But this issue is not the most obvious, so you can't blame it on him.
> Some editors store a BOM without giving notice, others hide such
> settings somewhere deep in the preferences.
>
> Hopefully this problem will completely vanish with native Unicode
> support in PHP 6.
>
> Micha
>

That's why you should never use a UTF-8 editor.  Of, if you need to, 
ensure that it's saving in ASCII mode.

And if you want to ensure that the <?php is the first thing in the file, 
look at the file in a hex editor.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#5615

In article <jmsedj$44p$1@dont-email.me>,
 Jerry Stuckle <jstucklex@attglobal.net> wrote:

> On 4/20/2012 3:13 PM, Michael Fesser wrote:
> > .oO(Jerry Stuckle)
> >
> >> IOW, you screwed up and the others here were right.<?php was NOT the
> >> first thing in your file!
> >
> > But this issue is not the most obvious, so you can't blame it on him.
> > Some editors store a BOM without giving notice, others hide such
> > settings somewhere deep in the preferences.
> >
> > Hopefully this problem will completely vanish with native Unicode
> > support in PHP 6.

> That's why you should never use a UTF-8 editor.  Of, if you need to, 
> ensure that it's saving in ASCII mode.

Rubbish. All my files are saved in UTF-8, which is no BOM by default. 
For the most part this means they are the same as ASCII files, but if I 
want to add chars like ƒ (curlique-f or whatever it's called), I can do 
that.

I got fed up when my email client (written in PHP and JavaScript) kept 
displaying chinese as rubbish characters. A decision to use UTF-8 
throughout, paying careful attention to the charsets that the received 
data said it was using, converting to UTF-8 where appropriate in PHP, 
sending the right headers, and doing the right thing on the JS side has 
meant that displayed mails look correct.

Windows-generated mails have a habit of lying about the charset they are 
using, but that's easy to fix up.

-- 
Tim

"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted"  --  Bill of Rights 1689

[toc] | [prev] | [next] | [standalone]

#5616

Tim Streater wrote:
> In article <jmsedj$44p$1@dont-email.me>,
> Jerry Stuckle <jstucklex@attglobal.net> wrote:
> 
>> On 4/20/2012 3:13 PM, Michael Fesser wrote:
>> > .oO(Jerry Stuckle)
>> >
>> >> IOW, you screwed up and the others here were right.<?php was NOT the
>> >> first thing in your file!
>> >
>> > But this issue is not the most obvious, so you can't blame it on him.
>> > Some editors store a BOM without giving notice, others hide such
>> > settings somewhere deep in the preferences.
>> >
>> > Hopefully this problem will completely vanish with native Unicode
>> > support in PHP 6.
> 
>> That's why you should never use a UTF-8 editor.  Of, if you need to, 
>> ensure that it's saving in ASCII mode.
> 
> Rubbish. All my files are saved in UTF-8, which is no BOM by default. 
> For the most part this means they are the same as ASCII files, but if I 
> want to add chars like ƒ (curlique-f or whatever it's called), I can do 
> that.

wiki has this to say:

The Unicode Standard does permit the BOM in UTF-8,[2] but does not 
require or recommend its use.[3] Byte order has no meaning in UTF-8[4] 
so in UTF-8 the BOM serves only to identify a text stream or file as UTF-8.

> 
> I got fed up when my email client (written in PHP and JavaScript) kept 
> displaying chinese as rubbish characters. A decision to use UTF-8 
> throughout, paying careful attention to the charsets that the received 
> data said it was using, converting to UTF-8 where appropriate in PHP, 
> sending the right headers, and doing the right thing on the JS side has 
> meant that displayed mails look correct.
> 
> Windows-generated mails have a habit of lying about the charset they are 
> using, but that's easy to fix up.
> 
Never found a reliable way to do that..



-- 
To people who know nothing, anything is possible.
To people who know too much, it is a sad fact
that they know how little is really possible -
and how hard it is to achieve it.

[toc] | [prev] | [next] | [standalone]

#5628

In article <jmsnke$ste$1@news.albasani.net>,
 The Natural Philosopher <tnp@invalid.invalid> wrote:

> Tim Streater wrote:

> > Windows-generated mails have a habit of lying about the charset they are 
> > using, but that's easy to fix up.
> > 
> Never found a reliable way to do that..

I display the html-mail by shoving it in an iFrame, and letting the 
browser worry about rendering it. But on the fly, and before actually 
doing the shoving-in, if I see a <meta> containing ISO-8859-1, I change 
that to UTF-8.

-- 
Tim

"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted"  --  Bill of Rights 1689

[toc] | [prev] | [next] | [standalone]

#5617

On 4/20/2012 6:11 PM, Tim Streater wrote:
> In article <jmsedj$44p$1@dont-email.me>,
> Jerry Stuckle <jstucklex@attglobal.net> wrote:
>
>> On 4/20/2012 3:13 PM, Michael Fesser wrote:
>> > .oO(Jerry Stuckle)
>> >
>> >> IOW, you screwed up and the others here were right.<?php was NOT the
>> >> first thing in your file!
>> >
>> > But this issue is not the most obvious, so you can't blame it on him.
>> > Some editors store a BOM without giving notice, others hide such
>> > settings somewhere deep in the preferences.
>> >
>> > Hopefully this problem will completely vanish with native Unicode
>> > support in PHP 6.
>
>> That's why you should never use a UTF-8 editor. Of, if you need to,
>> ensure that it's saving in ASCII mode.
>
> Rubbish. All my files are saved in UTF-8, which is no BOM by default.
> For the most part this means they are the same as ASCII files, but if I
> want to add chars like ƒ (curlique-f or whatever it's called), I can do
> that.
>

Correct.  Without the BOM, UTF-8 is the same as ASCII.  Just the 
extended characters (> 127) can have different meanings - but then ASCII 
doesn't define meanings for those, anyway.

> I got fed up when my email client (written in PHP and JavaScript) kept
> displaying chinese as rubbish characters. A decision to use UTF-8
> throughout, paying careful attention to the charsets that the received
> data said it was using, converting to UTF-8 where appropriate in PHP,
> sending the right headers, and doing the right thing on the JS side has
> meant that displayed mails look correct.
>

It's all in how you want to define the extended characters.

> Windows-generated mails have a habit of lying about the charset they are
> using, but that's easy to fix up.
>


-- 
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#5618

.oO(Tim Streater)

>In article <jmsedj$44p$1@dont-email.me>,
> Jerry Stuckle <jstucklex@attglobal.net> wrote:
>
>> That's why you should never use a UTF-8 editor.  Of, if you need to, 
>> ensure that it's saving in ASCII mode.
>
>Rubbish. All my files are saved in UTF-8, which is no BOM by default.

But a BOM is still allowed to identify the file as UTF-8. And some
editors do that, which causes problems in current PHP.

Micha

-- 
http://mfesser.de/blickwinkel

[toc] | [prev] | [next] | [standalone]

#5619

Michael Fesser wrote:
> .oO(Tim Streater)
> 
>> In article <jmsedj$44p$1@dont-email.me>,
>> Jerry Stuckle <jstucklex@attglobal.net> wrote:
>>
>>> That's why you should never use a UTF-8 editor.  Of, if you need to, 
>>> ensure that it's saving in ASCII mode.
>> Rubbish. All my files are saved in UTF-8, which is no BOM by default.
> 
> But a BOM is still allowed to identify the file as UTF-8. And some
> editors do that, which causes problems in current PHP.
> 
mainly microsnot editors of course

> Micha
> 


-- 
To people who know nothing, anything is possible.
To people who know too much, it is a sad fact
that they know how little is really possible -
and how hard it is to achieve it.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.php

csiph-web