FAQ

Andrei Zmievski wrote:
So, we'll keep author names in Credits in Latin-1? Why not use UTF-8?
We could, but we'd need to teach developers that ext/*/CREDITS and credits.c should
be kept UTF-8; else it'll break if anyone commits non-ASCII and nobody watches.

BTW, phpcredits() and phpinfo() generate content in output_encoding.

--
Michael

Search Discussions

  • Andrei Zmievski at Dec 12, 2006 at 5:43 pm

    We could, but we'd need to teach developers that ext/*/CREDITS and
    credits.c should
    be kept UTF-8; else it'll break if anyone commits non-ASCII and nobody
    watches.
    And what's wrong with that? Latin-1 is legacy crud, UTF-8 is the
    present and the future.
    BTW, phpcredits() and phpinfo() generate content in output_encoding.
    That makes sense.

    -Andrei
  • Ilia Alshanetsky at Dec 12, 2006 at 5:58 pm

    On 12-Dec-06, at 12:43 PM, Andrei Zmievski wrote:

    We could, but we'd need to teach developers that ext/*/CREDITS and
    credits.c should
    be kept UTF-8; else it'll break if anyone commits non-ASCII and
    nobody watches.
    And what's wrong with that? Latin-1 is legacy crud,
    Wow, when did this happen?


    Ilia Alshanetsky
  • Andrei Zmievski at Dec 12, 2006 at 6:02 pm

    On Dec 12, 2006, at 9:56 AM, Ilia Alshanetsky wrote:

    And what's wrong with that? Latin-1 is legacy crud,
    Wow, when did this happen?
    When we switched to XXI century.

    -Andrei
  • Michael Wallner at Dec 12, 2006 at 6:31 pm

    Andrei Zmievski wrote:
    We could, but we'd need to teach developers that ext/*/CREDITS and
    credits.c should
    be kept UTF-8; else it'll break if anyone commits non-ASCII and nobody
    watches.
    And what's wrong with that? Latin-1 is legacy crud, UTF-8 is the present
    and the future.
    I'm fine with converting a single CREDITS file to utf8 and placing a NOTE on top of credits.
    Should the php_info_* API assume it gets utf8 passed instead of latin1?

    --
    Michael
  • Andrei Zmievski at Dec 12, 2006 at 6:42 pm
    I think that would be a good thing for going forward.

    -Andrei
    On Dec 12, 2006, at 10:31 AM, Michael Wallner wrote:

    Andrei Zmievski wrote:
    We could, but we'd need to teach developers that ext/*/CREDITS and
    credits.c should
    be kept UTF-8; else it'll break if anyone commits non-ASCII and
    nobody
    watches.
    And what's wrong with that? Latin-1 is legacy crud, UTF-8 is the
    present
    and the future.
    I'm fine with converting a single CREDITS file to utf8 and placing a
    NOTE on top of credits.
    Should the php_info_* API assume it gets utf8 passed instead of latin1?

    --
    Michael

    --
    PHP Internals - PHP Runtime Development Mailing List
    To unsubscribe, visit: http://www.php.net/unsub.php

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupphp-internals @
categoriesphp
postedDec 12, '06 at 7:00a
activeDec 12, '06 at 6:42p
posts6
users3
websitephp.net

People

Translate

site design / logo © 2022 Grokbase