[PHP-DOC] cvs: phpdoc /de/language types.xml
moh Sat Feb 2 22:29:35 2002 EDT Modified files: /phpdoc/de/language types.xml Log: small correction of misspelling Index: phpdoc/de/language/types.xml diff -u phpdoc/de/language/types.xml:1.19 phpdoc/de/language/types.xml:1.20 --- phpdoc/de/language/types.xml:1.19 Mon Jan 21 05:11:07 2002 +++ phpdoc/de/language/types.xmlSat Feb 2 22:29:35 2002 @@ -524,13 +524,13 @@ -Einfache Anführungszeichen (single qouted) +Einfache +Anführungszeichen (single quoted) -Doppelte Anführungszeichen (double qouted) +Doppelte +Anführungszeichen (double quoted) @@ -544,7 +544,7 @@ - Einfache Anführungszeichen (Single qouted) + Einfache Anführungszeichen (Single quoted) Der leichteste Weg einen einfachen String zu schreiben, ist der Einschluss in einfache Anführungszeichen @@ -662,7 +662,7 @@ wird der Backslash ebenfalls ausgegeben! - Der wichtigste Vorteil von double-qouted Strings ist die Tatsache, + Der wichtigste Vorteil von double-quoted Strings ist die Tatsache, dass Variablennamen ausgewertet werden. Für Details siehe String Analyse (parsing)
Re: [PHP-DOC] cvs: phpdoc /kr/functions crack.xml cybermut.xml cyrus.xml dbplus.xml dbx.xml dio.xml dotnet.xml fbsql.xml fribidi.xml iconv.xml iisfunc.xml ircg.xml java.xml mailparse.xml mbstring.xml ming.xml msession.xml muscat.xml ncurses.xml notes.xml overload.xml pcntl.xml printer.xml qtdom.xml vpopmail.xml w32api.xml xmlrpc.xml zip.xml
Could you please *first* translate the things and then import them? 650k import/commits is in any way rather tough, but when it is just a copy of the english man it doesnt make sense. During the building process all missing files in a translated directory are automatically taken from the English manual. thx and best regards -moh Jin Tae-Young wrote: > > fuzzy74 Sat Jan 5 12:01:29 2002 EDT > > Added files: > /phpdoc/kr/functionscrack.xml cybermut.xml cyrus.xml dbplus.xml > dbx.xml dio.xml dotnet.xml fbsql.xml > fribidi.xml iconv.xml iisfunc.xml ircg.xml > java.xml mailparse.xml mbstring.xml ming.xml > msession.xml muscat.xml ncurses.xml notes.xml > overload.xml pcntl.xml printer.xml qtdom.xml > vpopmail.xml w32api.xml xmlrpc.xml zip.xml > Log: > add function files to korean translate docs > > > > > >fuzzy74-20020105120129.txtName: fuzzy74-20020105120129.txt > Type: Plain Text (text/plain)
Re: [PHP-DOC] RE: Zend API documentation.
Philip Olson wrote: > > > I just talked to Hartmut at the phpconf in Frankfurt and there were > > ideas of moving it to phpdoc and also to make it up2date :-) > > ...I though don't want talk for anyone. So I'll wait and see what he > > has to say this "progress" now :-) > > Sounds good. Here are a couple initial options that come to mind: > > a) Add a Warning entity on outdated zend api pages until the given page is >up-to-date. OR > b) Don't include any zend api docs until all is up-to-date. In order not to omit 90% of the apiddoc (this is just a tiny little exaggerated estimation!) I think a) will make the majority of us more happy :-) ehh, what was c) again? :-) -moh
Re: [PHP-DOC] RE: Zend API documentation.
James Cox wrote: > > I'm guessing that much could be out of date, however that would be one of > the core things of getting it into the hands of the phpdoc team. :) > > James I just talked to Hartmut at the phpconf in Frankfurt and there were ideas of moving it to phpdoc and also to make it up2date :-) ...I though don't want talk for anyone. So I'll wait and see what he has to say this "progress" now :-) -moh
Re: [PHP-DOC] RE: Zend API documentation.
James Cox wrote: > > I spoke to Zeev in IRC shortly, and he has given me permission to move the > Zend API documentation into the phpdoc tree. I checked it out a short while > ago, and am going through cleaning it up to phpdoc style. > > I am not going to commit this just yet -- i wanted to get any comments > first, since i'm not an old pro at phpdoc yet - so i want to check > everything out first. great deal! let's do it :-) I had checked out the zapidoc @ zendcvs some time ago and it seemed that some things are outdated and from the book by till/tobias. is that right or am I wrong? -moh
Re: [PHP-DOC] New documentation of sockets
Jan Lehnardt wrote: > > Hi, > I'd like to redocument the socket extension, since it has changed > completely. Now I'd like to know if there is an automated way of > transforming the function prototypes in the C Source file > (ext/sockets/sockets.c) into a documentation skeleton? plz correct me, if I am wrong but prototypes of undocumented functions are already in the documentation. -moh
[PHP-DOC] ext/sockets
Markus Fischer wrote: > > No, but my point is the interface isn't going to be changed > tomorrow. Not even next week. Very true! Well, I was thinking about sockets documentation for while after the bigger changes came. I just talked with Jan about it and we will go for it, writing the English doc as well as the German translation. Hope we can rely on you when having questions, Markus? :-) The diff between the cvs version and the 4.1.0 release version looks *big*. Are there so many enormous differences? Anyways, I guess "no documentation" is always worse than "small inconsistencies". best regards and happy xmas everybody -Richard
[PHP-DOC] cvs: phpdoc /de Translators
moh Thu Nov 29 08:44:18 2001 EDT Modified files: /phpdoc/de Translators Log: taking now care of the german trans. of pcre, conni gave me her already translated part! Index: phpdoc/de/Translators diff -u phpdoc/de/Translators:1.217 phpdoc/de/Translators:1.218 --- phpdoc/de/Translators:1.217 Sun Nov 25 16:31:55 2001 +++ phpdoc/de/Translators Thu Nov 29 08:44:18 2001 @@ -29,6 +29,7 @@ stefan_saasen Stefan Saasen [EMAIL PROTECTED] georg Georg Richter [EMAIL PROTECTED] nohn Sebastian Nohn [EMAIL PROTECTED] +mohRichard Samar [EMAIL PROTECTED] Verzeichnis/Datei Übersetzer Status = @@ -121,7 +122,7 @@ oracle.xml Martin Samesch fertig (Rev. 1.19) outcontrol.xml ovrimos.xml -pcre.xmlRalf Ebert in Arbeit +pcre.xmlRichard Samar in Arbeit pdf.xml Uwe Steinmann in Arbeit pfpro.xml Sebastian Nohn fertig (bis V. 1.9) pgsql.xml Catharina Paulsen Änderungen