Home > Archive > PHP Documentation > July 2006 > Re: [PHP-DOC] Starting on Unicode docs
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: [PHP-DOC] Starting on Unicode docs
|
|
| Sean Coates 2006-07-19, 6:58 pm |
| Welcome,
> I just wanted to shoot a quick email to the list to see when we could
> start work on docs for Unicode upgrades (PHP 6). The main thing, IMO, is
> having a way to mark functions as Unicode compatible and also have a
> section (per-function) for any Unicode-related notes. Any other thoughts
> on this?
A few things..
First, phpdoc contribution seems to be at a low. There's not much going
on right now, and seemingly not many people willing to pitch in (myself
included -- I've been lax lately).
That said, technically, we could probably pretty easily add a proto "U"
parser and add a &unicode.safe; entity to most applicable
functions/sections.
Adding unicode notes could be done on a function-by-function basis; no
need for a dedicated section, as this hopefully won't affect most
functions. If the same issues affect a large subset of functions, we can
come up with entities for this, too.
Another thing that you and I have discussed, but I've never passed on to
the list is the new proto markup for traditional strings vs. unicode
strings vs. binary strings. Anyone got thoughts on this?
S
| |
| Philip Olson 2006-07-19, 6:58 pm |
|
On Jul 19, 2006, at 10:41 AM, Sean Coates wrote:
> Welcome,
>
>
> A few things..
>
> First, phpdoc contribution seems to be at a low. There's not much
> going
> on right now, and seemingly not many people willing to pitch in
> (myself
> included -- I've been lax lately).
>
> That said, technically, we could probably pretty easily add a proto
> "U"
> parser and add a &unicode.safe; entity to most applicable
> functions/sections.
>
> Adding unicode notes could be done on a function-by-function basis; no
> need for a dedicated section, as this hopefully won't affect most
> functions. If the same issues affect a large subset of functions,
> we can
> come up with entities for this, too.
>
> Another thing that you and I have discussed, but I've never passed
> on to
> the list is the new proto markup for traditional strings vs. unicode
> strings vs. binary strings. Anyone got thoughts on this?
>
Since all appropriate functions will be unicode compatible in PHP
6.0.0 this seems like information overload and not something that
should be mentioned in every functions documentation. Perhaps have a
list offsite, maybe on docweb, for alpha/beta testers.
Regards,
Philip
| |
| Andrei Zmievski 2006-07-19, 6:58 pm |
| I think what we discussed last time was this:
unicode - for parameters that are -required- to be Unicode strings
binary - for parameters that are -required- to be binary strings
string - for parameters that can be either type
-Andrei
On Jul 19, 2006, at 10:41 AM, Sean Coates wrote:
>
> Another thing that you and I have discussed, but I've never passed on
> to
> the list is the new proto markup for traditional strings vs. unicode
> strings vs. binary strings. Anyone got thoughts on this?
>
| |
| Andrei Zmievski 2006-07-19, 6:58 pm |
| I think this information could be useful since people will most likely
want to use online manual even before PHP 6.0 final is out. Making them
go to a separate site to look up which function is Unicode-safe or not
is not very user-friendly.
-Andrei
> Since all appropriate functions will be unicode compatible in PHP
> 6.0.0 this seems like information overload and not something that
> should be mentioned in every functions documentation. Perhaps have a
> list offsite, maybe on docweb, for alpha/beta testers.
>
| |
| Nuno Lopes 2006-07-19, 6:58 pm |
| But we have a big problem: the translators. We can't simply modify all files
and then say to translators that they are lagging behind the English
version.
That said, I can only agree with Philip, from a practical point of view. In
the first alpha version I expect most (if not all) functions to be
unicode-compatible, and I think no one except the PHP developers will want
to use PHP 6 before that release.
Nuno
[color=darkred]
>I think this information could be useful since people will most likely want
>to use online manual even before PHP 6.0 final is out. Making them go to a
>separate site to look up which function is Unicode-safe or not is not very
>user-friendly.
>
> -Andrei
>
| |
| Sean Coates 2006-07-19, 6:58 pm |
| > Since all appropriate functions will be unicode compatible in PHP 6.0.0
> this seems like information overload and not something that should be
> mentioned in every functions documentation. Perhaps have a list offsite,
> maybe on docweb, for alpha/beta testers.
Good point. I agree.
This list already exists:
http://www.php.net/~scoates/unicode/
S
|
|
|
|
|