On Dec 3, 2007, at 2:31 PM, Hannes Magnusson wrote:
On Dec 3, 2007 9:33 PM, Edward Z. Yang
<[EMAIL PROTECTED]> wrote:
Hannes Magnusson wrote:
Thats not a good idea, translators will hunt you down and smack
you in
the face if you mix content changes with markup fixes :]
Hmm... what should
On Dec 3, 2007 9:33 PM, Edward Z. Yang <[EMAIL PROTECTED]> wrote:
> Hannes Magnusson wrote:
> > Thats not a good idea, translators will hunt you down and smack you in
> > the face if you mix content changes with markup fixes :]
>
> Hmm... what should I do with the already revised documentation page
On Dec 3, 2007 9:35 PM, Edward Z. Yang <[EMAIL PROTECTED]> wrote:
> Hannes Magnusson wrote:
> > IMO it shouldn't, not. They should look at the "class view" if they
> > want further details on how its defined, the 'detailed property'
> > listing should only contain the description of it.
>
> Ok, tha
On Dec 3, 2007 9:42 PM, Edward Z. Yang <[EMAIL PROTECTED]> wrote:
> Hannes Magnusson wrote:
> > Better indexing+rendering, but linkends are OK as a "workaround"
> > (don't harm anyway)
>
> The only trouble is that linkend doesn't cause a link to be rendered. :-)
Don't be such a nitpicking prick! :
Hannes Magnusson wrote:
> We don't, but it seems reasonable to have one as extensions are often
> one-to-one mapping of libraries/specifications with "minor
> adjustments" here and there.
Ok. I'll add some to the global snippets entity file.
--
Edward Z. YangGnuPG: 0x869
Hannes Magnusson wrote:
> XPointered XInclude, not XPath :P
Ah yes. (glares at self for making mistake numerous times)
> Better indexing+rendering, but linkends are OK as a "workaround"
> (don't harm anyway)
The only trouble is that linkend doesn't cause a link to be rendered. :-)
> Good idea,
Hannes Magnusson wrote:
> IMO it shouldn't, not. They should look at the "class view" if they
> want further details on how its defined, the 'detailed property'
> listing should only contain the description of it.
Ok, that sounds fine. It might, then, be useful to have a link back from
the detaile
Hannes Magnusson wrote:
> Thats not a good idea, translators will hunt you down and smack you in
> the face if you mix content changes with markup fixes :]
> Well, actually, its OK for the REF_STRUCT_DEV branch, but when we
> merge it to HEAD its gonna be paaain to separate the content fixes
> from
Hey, guys and gals, just a quick fix that should be done, if
anyone is working on the area.
On the date functions page of the website
(http://us3.php.net/manual/en/function.date.php) in example #1, this
should be changed:
// Prints something like: Monday 15th of August 2005 03:12:
Keryx Web wrote:
> Can I get all updates to the manual as an RSS or ATOM feed? Or do I have
> to implement my own?
http://news.php.net/group.php?group=php.doc.cvs&format=rss
Jakub Vrana
On 03.12.2007 16:02, Gascon Saint-Reikin wrote:
> Hello.
> I'm an IT-related specialist from Russia.
> Want to help in PHP docs translation into Russian language.
> I suppose there is a "Russian translation team" also? How can we communicate?
> With best regards, Sergey Semenov.
[EMAIL PROTECTED]
Hello.
I'm an IT-related specialist from Russia.
Want to help in PHP docs translation into Russian language.
I suppose there is a "Russian translation team" also? How can we communicate?
With best regards, Sergey Semenov.
This question should be directed to the PHP internals mailinglist,
[EMAIL PROTECTED]
I have honestly no idea :]
-Hannes
On Nov 26, 2007 9:15 PM, Keryx Web <[EMAIL PROTECTED]> wrote:
> Hi again!
>
> And please forgive a relative newbie on the list for asking dumb questions.
>
> Am I correct in as
On Nov 26, 2007 9:29 PM, Keryx Web <[EMAIL PROTECTED]> wrote:
> Hi again!
>
> I tried the site and Google to no avail. Here is my question:
>
> Can I get all updates to the manual as an RSS or ATOM feed? Or do I have
> to implement my own?
You mean a changelog of some sort so you can know which do
Hello,
I'm translating en/appendices/migration52.xml to IT, but I found a
couple of non existent functions referenced in it:
mb_list_encodings_alias_names (line 864)
mb_list_mime_names (line 870)
The related XMLs were removed from the CVS by Jakub on August 17th.
Will they be re-added to the Mul
On Dec 1, 2007 7:57 AM, Edward Z. Yang <[EMAIL PROTECTED]> wrote:
> Do we have any mechanism for this? (see subject) For example, the DOM
> extension is based off of the DOM Level 3 specification, but we have
> some backwards-compatibility properties, some extra properties, etc. Do
> we have standa
On Dec 1, 2007 8:02 AM, Edward Z. Yang <[EMAIL PROTECTED]> wrote:
> Working with PhD's output for object oriented documentation, here are my
> current pet peeves:
>
> * Properties are not inherited in class synopsises (need another crazy
> XPath)
XPointered XInclude, not XPath :P
> * Properties a
On Dec 1, 2007 8:03 AM, Edward Z. Yang <[EMAIL PROTECTED]> wrote:
> There's often extra information such as type, readonly and initializer
> that can be specified in the classsynopsis. Should this information be
> duplicated below in the detailed property location? (I don't think so,
> but I do thi
On Dec 1, 2007 8:05 AM, Edward Z. Yang <[EMAIL PROTECTED]> wrote:
> P.S. Work on DOM is chugging along slowly but surely. There's a bit of
> revising of the documentation that I'm doing while the conversion is
> taking place.
Thats not a good idea, translators will hunt you down and smack you in
t
19 matches
Mail list logo
