FAQ
Edit report at http://pear.php.net/bugs/bug.php?id=16559&edit=1

ID: 16559
Updated by: [email protected]
Reported By: daniel dot oconnor at gmail dot com
Summary: Unmigrated data vs UTF8 output
Status: Open
Type: Bug
Package: pearweb
Package Version: CVS
PHP Version: 5.2.5
Roadmap Versions:
New Comment:

Example:
http://test.pear.php.net/bugs/bug.php?id=12916


Previous Comments:
------------------------------------------------------------------------

[2009-09-01 09:22:26] doconnor

Description:
------------
http://validator.w3.org/check?uri=http%3A%2F%2Ftest.pear.php.net%2Fbugs%2Fbug.php%3Fid%3D12916&charset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654

We need to:
1. SELECT * FROM pearweb
2. If !utf8; convert to UTF8 from ISO-8859-2 or whatever it is encoded
as
3. REPLACE :D

------------------------------------------------------------------------

Search Discussions

  • Daniel Oconnor at Sep 1, 2009 at 8:00 am
    Edit report at http://pear.php.net/bugs/bug.php?id=16559&edit=1

    ID: 16559
    Updated by: [email protected]
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Unmigrated data vs UTF8 output
    Status: Open
    Type: Bug
    Package: pearweb
    Package Version: CVS
    PHP Version: 5.2.5
    Roadmap Versions:
    New Comment:

    (4:56:03 PM) cweiske: do we use iconv?
    (4:56:03 PM) cweiske: no
    (4:56:48 PM) cweiske: it's an apache vhost estting
    (5:23:05 PM) CloCkWeRX: alright; i think i have this straight in my
    head
    (5:23:21 PM) cweiske: CloCkWeRX, you do have access to sg1?
    (5:23:26 PM) CloCkWeRX: not right now
    (5:23:32 PM) cweiske: ohk
    (5:24:26 PM) CloCkWeRX: 1) pearweb spat out ISO whatever for quite a
    while, so bug reports form data was ISO when posted back, and stuck into
    an ISO database
    (5:24:26 PM) CloCkWeRX: 2) We swapped the table storage to UTF-8; using
    an ALTER TABLE CONVERT TO CHARACTER SET; and migrated all of the data
    then
    (5:25:01 PM) cweiske: iso-8850-15
    (5:25:04 PM) cweiske: iso-8859-15
    (5:26:14 PM) CloCkWeRX: 3) time went by and we kept INSERTing ISO data
    which was fine-ish (ie, pearweb still said it was ISO); even though
    mysql allocated enough space to store it as (mangled) UTF8
    (5:26:27 PM) cweiske: 3 sound possible
    (5:26:52 PM) CloCkWeRX: 4) ; and now I've made pearweb say it's
    producing UTF-8, which is actually ISO in the database / internal
    handling; it gets rendered in its mangled UTF8 form to the browser; and
    everyone has noticed :(
    (5:27:26 PM) yunosh [[email protected]] entered the
    room.
    (5:27:32 PM) CloCkWeRX: can you check the charset of the bugdb table to
    see if #3 is likely?
    (5:27:44 PM) cweiske: not now, having a meeting now


    Previous Comments:
    ------------------------------------------------------------------------

    [2009-09-01 09:22:51] doconnor

    Example:
    http://test.pear.php.net/bugs/bug.php?id=12916

    ------------------------------------------------------------------------

    [2009-09-01 09:22:26] doconnor

    Description:
    ------------
    http://validator.w3.org/check?uri=http%3A%2F%2Ftest.pear.php.net%2Fbugs%2Fbug.php%3Fid%3D12916&charset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654

    We need to:
    1. SELECT * FROM pearweb
    2. If !utf8; convert to UTF8 from ISO-8859-2 or whatever it is encoded
    as
    3. REPLACE :D

    ------------------------------------------------------------------------
  • Cweiske at Sep 2, 2009 at 7:49 am
    Edit report at http://pear.php.net/bugs/bug.php?id=16559&edit=1

    ID: 16559
    Updated by: [email protected]
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Unmigrated data vs UTF8 output
    Status: Open
    Type: Bug
    Package: pearweb
    Package Version: CVS
    PHP Version: 5.2.5
    Roadmap Versions:
    New Comment:

    It could be we just need to "SET NAMES 'utf8'" and are done.


    Previous Comments:
    ------------------------------------------------------------------------

    [2009-09-01 10:00:44] doconnor

    (4:56:03 PM) cweiske: do we use iconv?
    (4:56:03 PM) cweiske: no
    (4:56:48 PM) cweiske: it's an apache vhost estting
    (5:23:05 PM) CloCkWeRX: alright; i think i have this straight in my
    head
    (5:23:21 PM) cweiske: CloCkWeRX, you do have access to sg1?
    (5:23:26 PM) CloCkWeRX: not right now
    (5:23:32 PM) cweiske: ohk
    (5:24:26 PM) CloCkWeRX: 1) pearweb spat out ISO whatever for quite a
    while, so bug reports form data was ISO when posted back, and stuck into
    an ISO database
    (5:24:26 PM) CloCkWeRX: 2) We swapped the table storage to UTF-8; using
    an ALTER TABLE CONVERT TO CHARACTER SET; and migrated all of the data
    then
    (5:25:01 PM) cweiske: iso-8850-15
    (5:25:04 PM) cweiske: iso-8859-15
    (5:26:14 PM) CloCkWeRX: 3) time went by and we kept INSERTing ISO data
    which was fine-ish (ie, pearweb still said it was ISO); even though
    mysql allocated enough space to store it as (mangled) UTF8
    (5:26:27 PM) cweiske: 3 sound possible
    (5:26:52 PM) CloCkWeRX: 4) ; and now I've made pearweb say it's
    producing UTF-8, which is actually ISO in the database / internal
    handling; it gets rendered in its mangled UTF8 form to the browser; and
    everyone has noticed :(
    (5:27:26 PM) yunosh [[email protected]] entered the
    room.
    (5:27:32 PM) CloCkWeRX: can you check the charset of the bugdb table to
    see if #3 is likely?
    (5:27:44 PM) cweiske: not now, having a meeting now

    ------------------------------------------------------------------------

    [2009-09-01 09:22:51] doconnor

    Example:
    http://test.pear.php.net/bugs/bug.php?id=12916

    ------------------------------------------------------------------------

    [2009-09-01 09:22:26] doconnor

    Description:
    ------------
    http://validator.w3.org/check?uri=http%3A%2F%2Ftest.pear.php.net%2Fbugs%2Fbug.php%3Fid%3D12916&charset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654

    We need to:
    1. SELECT * FROM pearweb
    2. If !utf8; convert to UTF8 from ISO-8859-2 or whatever it is encoded
    as
    3. REPLACE :D

    ------------------------------------------------------------------------
  • Cweiske at Sep 4, 2009 at 8:07 am
    Edit report at http://pear.php.net/bugs/bug.php?id=16559&edit=1

    ID: 16559
    Updated by: [email protected]
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Unmigrated data vs UTF8 output
    Status: Open
    Type: Bug
    Package: pearweb
    Package Version: CVS
    PHP Version: 5.2.5
    Roadmap Versions:
    New Comment:

    http://test.pear.php.net/qa/


    Previous Comments:
    ------------------------------------------------------------------------

    [2009-09-02 09:48:58] cweiske

    It could be we just need to "SET NAMES 'utf8'" and are done.

    ------------------------------------------------------------------------

    [2009-09-01 10:00:44] doconnor

    (4:56:03 PM) cweiske: do we use iconv?
    (4:56:03 PM) cweiske: no
    (4:56:48 PM) cweiske: it's an apache vhost estting
    (5:23:05 PM) CloCkWeRX: alright; i think i have this straight in my
    head
    (5:23:21 PM) cweiske: CloCkWeRX, you do have access to sg1?
    (5:23:26 PM) CloCkWeRX: not right now
    (5:23:32 PM) cweiske: ohk
    (5:24:26 PM) CloCkWeRX: 1) pearweb spat out ISO whatever for quite a
    while, so bug reports form data was ISO when posted back, and stuck into
    an ISO database
    (5:24:26 PM) CloCkWeRX: 2) We swapped the table storage to UTF-8; using
    an ALTER TABLE CONVERT TO CHARACTER SET; and migrated all of the data
    then
    (5:25:01 PM) cweiske: iso-8850-15
    (5:25:04 PM) cweiske: iso-8859-15
    (5:26:14 PM) CloCkWeRX: 3) time went by and we kept INSERTing ISO data
    which was fine-ish (ie, pearweb still said it was ISO); even though
    mysql allocated enough space to store it as (mangled) UTF8
    (5:26:27 PM) cweiske: 3 sound possible
    (5:26:52 PM) CloCkWeRX: 4) ; and now I've made pearweb say it's
    producing UTF-8, which is actually ISO in the database / internal
    handling; it gets rendered in its mangled UTF8 form to the browser; and
    everyone has noticed :(
    (5:27:26 PM) yunosh [[email protected]] entered the
    room.
    (5:27:32 PM) CloCkWeRX: can you check the charset of the bugdb table to
    see if #3 is likely?
    (5:27:44 PM) cweiske: not now, having a meeting now

    ------------------------------------------------------------------------

    [2009-09-01 09:22:51] doconnor

    Example:
    http://test.pear.php.net/bugs/bug.php?id=12916

    ------------------------------------------------------------------------

    [2009-09-01 09:22:26] doconnor

    Description:
    ------------
    http://validator.w3.org/check?uri=http%3A%2F%2Ftest.pear.php.net%2Fbugs%2Fbug.php%3Fid%3D12916&charset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654

    We need to:
    1. SELECT * FROM pearweb
    2. If !utf8; convert to UTF8 from ISO-8859-2 or whatever it is encoded
    as
    3. REPLACE :D

    ------------------------------------------------------------------------
  • Cweiske at Sep 4, 2009 at 8:08 am
    Edit report at http://pear.php.net/bugs/bug.php?id=16559&edit=1

    ID: 16559
    Updated by: [email protected]
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Unmigrated data vs UTF8 output
    Status: Open
    Type: Bug
    Package: pearweb
    Package Version: CVS
    PHP Version: 5.2.5
    Roadmap Versions:
    New Comment:

    http://test.pear.php.net/support/books.php


    Previous Comments:
    ------------------------------------------------------------------------

    [2009-09-04 10:07:32] cweiske

    http://test.pear.php.net/qa/

    ------------------------------------------------------------------------

    [2009-09-02 09:48:58] cweiske

    It could be we just need to "SET NAMES 'utf8'" and are done.

    ------------------------------------------------------------------------

    [2009-09-01 10:00:44] doconnor

    (4:56:03 PM) cweiske: do we use iconv?
    (4:56:03 PM) cweiske: no
    (4:56:48 PM) cweiske: it's an apache vhost estting
    (5:23:05 PM) CloCkWeRX: alright; i think i have this straight in my
    head
    (5:23:21 PM) cweiske: CloCkWeRX, you do have access to sg1?
    (5:23:26 PM) CloCkWeRX: not right now
    (5:23:32 PM) cweiske: ohk
    (5:24:26 PM) CloCkWeRX: 1) pearweb spat out ISO whatever for quite a
    while, so bug reports form data was ISO when posted back, and stuck into
    an ISO database
    (5:24:26 PM) CloCkWeRX: 2) We swapped the table storage to UTF-8; using
    an ALTER TABLE CONVERT TO CHARACTER SET; and migrated all of the data
    then
    (5:25:01 PM) cweiske: iso-8850-15
    (5:25:04 PM) cweiske: iso-8859-15
    (5:26:14 PM) CloCkWeRX: 3) time went by and we kept INSERTing ISO data
    which was fine-ish (ie, pearweb still said it was ISO); even though
    mysql allocated enough space to store it as (mangled) UTF8
    (5:26:27 PM) cweiske: 3 sound possible
    (5:26:52 PM) CloCkWeRX: 4) ; and now I've made pearweb say it's
    producing UTF-8, which is actually ISO in the database / internal
    handling; it gets rendered in its mangled UTF8 form to the browser; and
    everyone has noticed :(
    (5:27:26 PM) yunosh [[email protected]] entered the
    room.
    (5:27:32 PM) CloCkWeRX: can you check the charset of the bugdb table to
    see if #3 is likely?
    (5:27:44 PM) cweiske: not now, having a meeting now

    ------------------------------------------------------------------------

    [2009-09-01 09:22:51] doconnor

    Example:
    http://test.pear.php.net/bugs/bug.php?id=12916

    ------------------------------------------------------------------------

    [2009-09-01 09:22:26] doconnor

    Description:
    ------------
    http://validator.w3.org/check?uri=http%3A%2F%2Ftest.pear.php.net%2Fbugs%2Fbug.php%3Fid%3D12916&charset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.654

    We need to:
    1. SELECT * FROM pearweb
    2. If !utf8; convert to UTF8 from ISO-8859-2 or whatever it is encoded
    as
    3. REPLACE :D

    ------------------------------------------------------------------------
  • Cweiske at Sep 4, 2009 at 8:17 am
    Edit report at http://pear.php.net/bugs/bug.php?id=16559&edit=1

    ID: 16559
    Updated by: [email protected]
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Unmigrated data vs UTF8 output
    Status: Open
    Type: Bug
    Package: pearweb
    Package Version: CVS
    PHP Version: 5.2.5
    Roadmap Versions:
    New Comment:

    http://test.pear.php.net/pepr/
    http://test.pear.php.net/user/nepto
    http://test.pear.php.net/user/padraic


    Previous Comments:
    ------------------------------------------------------------------------

    [2009-09-04 10:08:33] cweiske

    http://test.pear.php.net/support/books.php

    ------------------------------------------------------------------------

    [2009-09-04 10:07:32] cweiske

    http://test.pear.php.net/qa/

    ------------------------------------------------------------------------

    [2009-09-02 09:48:58] cweiske

    It could be we just need to "SET NAMES 'utf8'" and are done.

    ------------------------------------------------------------------------

    [2009-09-01 10:00:44] doconnor

    (4:56:03 PM) cweiske: do we use iconv?
    (4:56:03 PM) cweiske: no
    (4:56:48 PM) cweiske: it's an apache vhost estting
    (5:23:05 PM) CloCkWeRX: alright; i think i have this straight in my
    head
    (5:23:21 PM) cweiske: CloCkWeRX, you do have access to sg1?
    (5:23:26 PM) CloCkWeRX: not right now
    (5:23:32 PM) cweiske: ohk
    (5:24:26 PM) CloCkWeRX: 1) pearweb spat out ISO whatever for quite a
    while, so bug reports form data was ISO when posted back, and stuck into
    an ISO database
    (5:24:26 PM) CloCkWeRX: 2) We swapped the table storage to UTF-8; using
    an ALTER TABLE CONVERT TO CHARACTER SET; and migrated all of the data
    then
    (5:25:01 PM) cweiske: iso-8850-15
    (5:25:04 PM) cweiske: iso-8859-15
    (5:26:14 PM) CloCkWeRX: 3) time went by and we kept INSERTing ISO data
    which was fine-ish (ie, pearweb still said it was ISO); even though
    mysql allocated enough space to store it as (mangled) UTF8
    (5:26:27 PM) cweiske: 3 sound possible
    (5:26:52 PM) CloCkWeRX: 4) ; and now I've made pearweb say it's
    producing UTF-8, which is actually ISO in the database / internal
    handling; it gets rendered in its mangled UTF8 form to the browser; and
    everyone has noticed :(
    (5:27:26 PM) yunosh [[email protected]] entered the
    room.
    (5:27:32 PM) CloCkWeRX: can you check the charset of the bugdb table to
    see if #3 is likely?
    (5:27:44 PM) cweiske: not now, having a meeting now

    ------------------------------------------------------------------------

    [2009-09-01 09:22:51] doconnor

    Example:
    http://test.pear.php.net/bugs/bug.php?id=12916

    ------------------------------------------------------------------------

    The remainder of the comments for this report are too long. To view
    the rest of the comments, please view the bug report online at
    http://pear.php.net/bugs/bug.php?id=16559
  • Daniel Oconnor at Sep 4, 2009 at 1:51 pm
    Edit report at http://pear.php.net/bugs/bug.php?id=16559&edit=1

    ID: 16559
    Updated by: [email protected]
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Unmigrated data vs UTF8 output
    Status: Open
    Type: Bug
    Package: pearweb
    Package Version: CVS
    PHP Version: 5.2.5
    Roadmap Versions:
    New Comment:

    [288045] does SET NAMES, whcih resolves the display of umlauts.

    However, locally, the format-bug-strip-only-some-html stuff is broken
    for Bug #12916


    Previous Comments:
    ------------------------------------------------------------------------

    [2009-09-04 10:17:02] cweiske

    http://test.pear.php.net/pepr/
    http://test.pear.php.net/user/nepto
    http://test.pear.php.net/user/padraic

    ------------------------------------------------------------------------

    [2009-09-04 10:08:33] cweiske

    http://test.pear.php.net/support/books.php

    ------------------------------------------------------------------------

    [2009-09-04 10:07:32] cweiske

    http://test.pear.php.net/qa/

    ------------------------------------------------------------------------

    [2009-09-02 09:48:58] cweiske

    It could be we just need to "SET NAMES 'utf8'" and are done.

    ------------------------------------------------------------------------

    [2009-09-01 10:00:44] doconnor

    (4:56:03 PM) cweiske: do we use iconv?
    (4:56:03 PM) cweiske: no
    (4:56:48 PM) cweiske: it's an apache vhost estting
    (5:23:05 PM) CloCkWeRX: alright; i think i have this straight in my
    head
    (5:23:21 PM) cweiske: CloCkWeRX, you do have access to sg1?
    (5:23:26 PM) CloCkWeRX: not right now
    (5:23:32 PM) cweiske: ohk
    (5:24:26 PM) CloCkWeRX: 1) pearweb spat out ISO whatever for quite a
    while, so bug reports form data was ISO when posted back, and stuck into
    an ISO database
    (5:24:26 PM) CloCkWeRX: 2) We swapped the table storage to UTF-8; using
    an ALTER TABLE CONVERT TO CHARACTER SET; and migrated all of the data
    then
    (5:25:01 PM) cweiske: iso-8850-15
    (5:25:04 PM) cweiske: iso-8859-15
    (5:26:14 PM) CloCkWeRX: 3) time went by and we kept INSERTing ISO data
    which was fine-ish (ie, pearweb still said it was ISO); even though
    mysql allocated enough space to store it as (mangled) UTF8
    (5:26:27 PM) cweiske: 3 sound possible
    (5:26:52 PM) CloCkWeRX: 4) ; and now I've made pearweb say it's
    producing UTF-8, which is actually ISO in the database / internal
    handling; it gets rendered in its mangled UTF8 form to the browser; and
    everyone has noticed :(
    (5:27:26 PM) yunosh [[email protected]] entered the
    room.
    (5:27:32 PM) CloCkWeRX: can you check the charset of the bugdb table to
    see if #3 is likely?
    (5:27:44 PM) cweiske: not now, having a meeting now

    ------------------------------------------------------------------------

    The remainder of the comments for this report are too long. To view
    the rest of the comments, please view the bug report online at
    http://pear.php.net/bugs/bug.php?id=16559
  • Cweiske at Sep 8, 2009 at 5:47 am
    Edit report at http://pear.php.net/bugs/bug.php?id=16559&edit=1

    ID: 16559
    Updated by: [email protected]
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Unmigrated data vs UTF8 output
    -Status: Open
    +Status: Closed
    Type: Bug
    Package: pearweb
    Package Version: CVS
    PHP Version: 5.2.5
    -Assigned To:
    +Assigned To: doconnor
    Roadmap Versions:
    New Comment:

    -Status: Open
    +Status: Closed
    -Assigned To:
    +Assigned To: doconnor
    Thank you for your bug report. This issue has been fixed
    in the latest released version of the package, which you can download
    at
    http://pear.php.net/get/




    Previous Comments:
    ------------------------------------------------------------------------

    [2009-09-04 15:51:38] doconnor

    [288045] does SET NAMES, whcih resolves the display of umlauts.

    However, locally, the format-bug-strip-only-some-html stuff is broken
    for Bug #12916

    ------------------------------------------------------------------------

    [2009-09-04 10:17:02] cweiske

    http://test.pear.php.net/pepr/
    http://test.pear.php.net/user/nepto
    http://test.pear.php.net/user/padraic

    ------------------------------------------------------------------------

    [2009-09-04 10:08:33] cweiske

    http://test.pear.php.net/support/books.php

    ------------------------------------------------------------------------

    [2009-09-04 10:07:32] cweiske

    http://test.pear.php.net/qa/

    ------------------------------------------------------------------------

    [2009-09-02 09:48:58] cweiske

    It could be we just need to "SET NAMES 'utf8'" and are done.

    ------------------------------------------------------------------------

    The remainder of the comments for this report are too long. To view
    the rest of the comments, please view the bug report online at
    http://pear.php.net/bugs/bug.php?id=16559

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppear-bugs @
categoriesphp
postedSep 1, '09 at 7:23a
activeSep 8, '09 at 5:47a
posts8
users2
websitepear.php.net

2 users in discussion

Cweiske: 5 posts Daniel Oconnor: 3 posts

People

Translate

site design / logo © 2023 Grokbase