Hi there!
Goba,
after a long time I've now done the hu-manual to check:
http://www.t0.or.at/~sunny/php/manual_hu.pdf.zip
if it's OK, would you please ask Derick to copy also the updated en- and
de- versions to rsync space?
http://www.t0.or.at/~sunny/php/manual_de.pdf.zip
http://www.t0.or.at/~sun
Hartmut Holzgraefe wrote:
DocBook 4 has an tag that may be used to add default
values to a function parameter
A parameter that has a default / initializer value is now considered
optional and the default value is shown in italics.
Example:
Ask
string
query_str
bool
single_step
Gabor Hojtsy wrote:
Hum. I have tried to fix the errors you are talking about, but I cannot
see any. Make test and make test_xml says no errors are found. You
probably have an old hu checkout...
Hi,
sorry that's my fault. I've got a bunch of errors, but this just because
I didn't have the miss
Gabor Hojtsy wrote:
OK, I've made en and de, if you (for hu) and others are willing to
check their language, I'll provide also other langs.
http://www.t0.or.at/~sunny/php/manual_de.pdf.zip
http://www.t0.or.at/~sunny/php/manual_en.pdf.zip
Great! Derick, can you please copy these to rsync space?
Gabor Hojtsy wrote:
From my (XSLT) point of view, we could also start now (and make all
the small design-changes later), but there's one K.O.-criteria, I
didn't get any response/info about: we need to be on one of the
building-machines with 1GB RAM, and Java!
For a first healing it would be muc
Gabor Hojtsy wrote:
...
Hm. I think I would have enough swap. But it does not seem to attempt to
use swap at all... Anyway, I'll try to contact the FOP team, and some
linux support guys here ;) BTW I am not going to invest in any more
SDRAM modules. Ron offered me a huge help in funding, I am aw
Gabor Hojtsy wrote:
...
Sorry, I didn't follow this discussion completely (have 1.600 unread
posts:), but I think this kind of "application" shouldn't be necessary
at all.
We all know who contributes regularly, so I think making such a list
is pure waste of time which could be used more product
Hi Goba,
I can't tell you WHY (maybe a bug in xsltproc, but didn't take the time
to check it in detail), it just fixes the errors below (caused by the 0
bytes phpweb.ent, directly followed by the %global.entities;).
But for the organised look: If you like, I can place it after the
"%build.vers
Gabor Hojtsy wrote:
Last I heard the discussion on the authors list for the PHP manual
distilled
down to contributors submitting a "resume" of involvement in the
documentation project. To that end I've got a merge of a scan though CVS
and my own memory below including links to diffs and/or compil
Gabor Hojtsy wrote:
sorry, if this is a known limitation of the xslt-sheets.
xslt generated html (didn't test phpweb) lacks the version info from
the functions.
AFAIK the phpweb stuff has them. There are specific codes for this in
the xsl sheets...
I've just tried it, and the're really gone i
Hi Goba,
Gabor Hojtsy wrote:
Hi Thomas and all!
I have tried to make a PDF to see how it looks with XSL FO and FOP. The
fo file is perfectly generated. Then when I run FOP, I get several
errors. I know that FOP is not mature enough, also used it in smaller
projects, so I was not afraid of thos
Gabor Hojtsy wrote:
as you can see on the newly committed xsl-styles, the html and bightml
versions seem to work fine (some design-improvements are always
possible ;), but I have a problem with the fo-styles (or the
FOP-behavior):
Well, I don't have any idea to your problem, but I need to ask
Hi all,
as you can see on the newly committed xsl-styles, the html and bightml
versions seem to work fine (some design-improvements are always possible
;), but I have a problem with the fo-styles (or the FOP-behavior):
xsltproc does output-escaping also on quotes (" -> "), but FOP
stops with a
Hi there,
there an entry in .cvsignore - so the question is: Damien, did you try a
tricky thing, or doesn't .cvsignore work correctly, or is my expectation
of it's behavior completely wrong?
Cu,
Thomas
Gabor Hojtsy wrote:
Modified files:
/phpdoc/en/reference/fbsql functions.xm
Gabor Hojtsy wrote:
I'll start to adapt the xsl-stylesheets in the next days, but my
priority is the html-version, and then I'll do the fo-version (Will
take 1-3 weeks).
But I don't think that it will be provided as autogenerated files to
download that soon, so you'd have to be familiar with pr
Hi Damien,
first I have to thank you for your regular efforts!
On the other hand I'd like to ask you to think also about the
'translators' (I like the term 'maintainer', since this is much more
effort than just translating), which get permanent changes in 'their'
en-files.
So would you please
Johan wrote:
Hi!
Just a quick question, when is a new version of the PHP manual going to
show up in form of PDF?
Why I wonder is because if there is coming one up soon,
I will not have to make my own.
Thx
Hi Johan,
I'll start to adapt the xsl-stylesheets in the next days, but my
priority is the
Philip Olson wrote:
On Thu, 27 Feb 2003, Hartmut Holzgraefe wrote:
No bribe from me as PDF isn't _that_ cool :) The manual is
a live thriving entity so I'm sorta against all downloadable
versions of the manual because downloads become outdated.
Hehe: When was the last online-build - Jan 26??
Der
Hi there,
looking at the current - esp. for newbies sometimes confusing - manual,
where several old info and even functions simply disappeared, but
several exlanations and even whole chapters (like 'Migrating from PHP/FI
2 to PHP 3') for PHP 3 still exist, etc., one thought came into my mind:
I cannot check it on *nix, I would probably commit and wait to see
if it works or not, unless noone replys with some negative comments ;)
Goba
Done.
I just have to correct myself: the cli-story is different due to the
working-dirs, but I tried it just with my batchfiles, which always step
dir
Hi all,
I can't see any differences in the behavior of "../" between cgi- and
cli-version (at least on my win-box, and I would wonder if it is on
Linux, and if, somebody should report it to qa), but it seems to be the
old story of currentdir, workdir, etc. on the different machines.
If I'm rig
Gabor Hojtsy wrote:
IDK, part of me
thinks that any incomplete PDF version shouldn't be
listed at all...
I have removed the PDFs from the downloadable documents
listings, we have too many complaints about it... Hartmut
told me, that he strongly beleives that the one simple
thing to do to solve
Gabor Hojtsy wrote:
>
>>2.) Change the age-criteria for "critical" files to the last change-date
>> of the en-file
>>Currently, if you've synced a file >30 days ago, and today the corresp.
>>en-file gets changed, the status becomes immediately "critical".
>>If we change this to the last ch
Hi all,
I'd like to change some things in the revcheck-system, but want to agree
upon it first. The changes I mean are:
1.) Change the filesize-criteria for "critical" files from 10kB to 2kB
Since the bananasplit, the filesizes devreased dramatically, and the
chance, that a 2kB file increases
Hello André,
if you mean just the output (status) of
reference/filesystem/functions/copy.xml,
it's fixed in cvs.
Cu,
Thomas
André lfs bacci wrote:
> The revcheck system is not workink proprerly in revision-tags with CREDITS:.
>
> See in the source of
> http://www.php.net/manual/pt_BR/revche
Hi Goba,
sorry for this late answer, but I simply forgot this message after I've
got ill last week.
Many thanks for the answer, but no, I don't have a common workaround
(not even thought about it yet, but maybe when I've finished all the old
tranl.-files).
But I don't consider this behavior
Gabor Hojtsy wrote:
> Yes. As usual, the configure is not run form the phpdoc checkout
> dir on the generator machine. What getcwd() returns, is the PHP
> scripts directory, AFAIK, as PHP set the current directory to be
> the script's directory (there may be a setting for it?). Thus the
> value re
Hi there,
after a vry long break, I try to use some of my still very limited
time to follow the list again, and sync at least my "critical"
trasnslation-files.
Unfortunately, a configure is not so easy, because the file-entities.ent
can't be created at my Cygwin-config.
file-entities.php
Hi there,
Gabor Hojtsy wrote:
>>>To clear this up, does that mean that you'll volunteer in doing this
>>>cleanup? ;)))
>>
>>Not alone.
>>
>>To be precise, I can
>>physically move the files (except ZentAPI for the moment), and
>>move the 3 parts from the manual into the new document (adapting the
Gabor Hojtsy wrote:
>>>Well, I think it still can be stored under phpdoc-LANG/phpdevel,
>>>but it needs a separate root XML file. This may add some new
>>>bits to the configure script, but IMHO we should not duplicate
>>>the configure system [one of the phpdoc meeting ideas was to
>>>open a comp
>>Keep them for a while more...and after all there is a big notice at the
>>beginning of each file.
>
>
> And they should always be kept somewhere at least,
> as they are a good historical archive (changelog).
Right.
Just for the long term: we should keep that "somewhere" in mind as an
issu
Since this is not the first time...
Would it be too early to delete these files?
Thomas
Gabor Hojtsy wrote:
>>k.schroeder Sun Jun 2 15:03:06 2002 EDT
>>
>> Modified files:
>>/phpdoc/en/functions filesystem.xml
>> Log:
>> Bug #13292 file_exists works with UNC names
>
>
Hi all,
> Well, I think it still can be stored under phpdoc-LANG/phpdevel,
> but it needs a separate root XML file. This may add some new
> bits to the configure script, but IMHO we should not duplicate
> the configure system [one of the phpdoc meeting ideas was to
> open a completely new reposit
> Very nice idea ;) As I tried to propagte the idea of having a separate
> (!) for developing PHP, and providing it in a separate download,
> I fully agree on at least consolidating these sections all in one place
> in the manual. BTW I still think it would be better to open a new book
> on devel
Hi Lior,
there was a XML-error, but it should work now.
Thomas
Lior Hammer wrote:
> The html dir is empty.
> "Gabor Hojtsy" <[EMAIL PROTECTED]> wrote in message
> 012f01c20976$03312ae0$de37a3d5@home">news:012f01c20976$03312ae0$de37a3d5@home...
>
>>>It's working, thank you.
>>>
>>>autoconf
>>>
Hi there,
if you want to make one section with all the developer-info in it, I'm
fully with you, and would go one step further, to structure like
- developing PHP
- Building PHP from source (from Win-install-section, it's just
confusing newbies which just downloaded the bin-distri)
- ex
t.
> i'm using the phpdoc-he
> 10Q
> "Thomas Schöfbeck" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>
>>Hi Lior,
>>
>>If you checkout phpdoc-, you get automatically
>>everything to build th
Hi there,
missed that one, but I feel obliged to explain the revcheck-system to
one of the authors:
> Since there are over 1500 files without the normal Revision tag and over
> 700 without the EN Revision, including the "normal" could be done
> better by a shell sript or so, than doing this al
Hi Lior,
If you checkout phpdoc-, you get automatically
everything to build the manual in your lang as well as in en.
If the build doesn't work (cd into phpdoc->lang-code>, autoconf,
./configure..., make html), we need more info to be able to help you.
Thomas
Lior Hammer wrote:
> There are
Hi Jan,
> +1 for having them in (it does not harm anybody)
for which reason? Just for having 25kB Overhead?
> -1 for inconsitency. mark tried to have all files similar (as he pointed
> out in a previous mail).
As I've wrote already to Mark: If there's no reason than consistency,
why not go t
> AFAIK we had them in all files before the split.
> Some have them in, some dont. I just wanted to
> put a straight line.
Hi Mark,
that's simply not true. Jeroen implemented them 1 year ago into the
EN-files (EN!) as a basis for the revcheck-system (compares them with
the revcheck-tag in the
Hi Mark,
Since your last message was empty I can't see whom you wanted to help
with this action, but in general I'd like to say:
If you want these tags in your files for a special reason or kind of
working, no problem.
But please leave them out from files you don't work on (especially mine,
Hi there,
everything back, I've learned a new rule ;) never talk about stories
from others!
Couldn't sleep, upgraded to 4.2.1, and checked it for myself, but
everything's still working fine!
And Goba, you're right: Since Rafel's problem seems to be the good old
register_globals story, and AF
Hi!
Goba, I hope you didn't get me wrong with the php.bat, because it worked
well till PHP 4.1.2, but PHPs behavior has changed since PHP 4.2.0 (at
least on win, don't have a Linux-box at hand). Before we do a general
workaround, we should check if this behavior-change was on purpose, or
if
Hi Rafael,
It works fine for me, but:
be sure that the arguments get through into your file-entities.php (e.g.
"./script/file-entities.php" + "." + "es"). If not, you get except the install-part
(which is handled separately) only file-entities pointing to */en/* (in chapters.ent),
which makes an
Hi Derick,
it works. The error you wrote occurs, because you haven't run
autoconf (!)
./configure
with the new Configure.in
To the "bogus" things:
As I wrote in my initial personal mail, do I don't know the exact
environment on the server (script that calls "make", etc..).
I just try to fix bu
Hi all,
if there are no complaints, I'll delete in the next vew days all the
/reference/functions.xml files to finally activate the
automatic fallback to the English functions if there is no
translation available.
Thomas
Hi all,
I don't know if there was a private answer from Hartmut, but I want to
restart the discussion, since the expected (main) benefit of the
file-split doesn't work, but we already live with the disadvantages.
Additional to Goba's comments below, Slawomir has also outlined, that
all /refer
Hi all,
I've had a short glance at the user-notes at
http://www.php.net/manual/en/language.oop.php, and I saw that many
people write things which are already described in the following pages.
While thinking why they would do that, one of the possibilities which
came to mind was that the titles o
Hello Hartmut,
didn't recognize that the phpscript is already ready, but adding
--with-php= works fine.
Many thanks for the hint,
Thomas
Hartmut Holzgraefe wrote:
> Thomas Schöfbeck wrote:
> > Hi all,
> >
> > after the file-split a simple "make test" o
Hi all,
after the file-split a simple "make test" of the doc got a real pain,
since the echoing of untranslated files now takes a serious amount of
time.
Is there any reason against taking this endlessly output out? (Maybe
this would motivate some of the translators to test their erroreanous
fil
Hi Goba,
you're fully right (I was just driven by the still too large html-output
before I went to bed, without thinking about anything :).
I have to leave now, but I'll change that tomorrow.
Cu,
Thomas
Gabor Hojtsy wrote:
> > +print << > +Introduction |
> > +Translators |
> > +File summary
Hi Goba,
I know the link, which unfortuntely pointed "only" to an "ugly" commandline-tool
(who reads the text till the end? ;). That's the reason why I've moved the para
about the "colorful" tools to almost the top.
Cu,
Thomas
Gabor Hojtsy wrote:
> > the arguments for both gz and bzip2 make s
Hi all,
the arguments for both gz and bzip2 make sense to me (user-friendliness and
dl-size).
We Austrians tend alsways to a compromise ;)
If it stays at bzip2: Why not write a link at the doc-download-page to the
somewhere mentioned FAQ-Page, and list there some Freeware for Win like
UltimateZ
Hi slawomir,
anyhow, you can't use §itle.runtime; in your translation, because it would
make
Runtime Configuration and not the needed Runtime
Configuration or a simple text. Also consider the fiddling in serveral
files for just a title, which is in about 85% a function name, which doesn't
need to
Gabor Hojtsy wrote:
> Well, actually I was only refering to those 4-5
> titles used at the top of newly structured function
> pages, like pcre.xml. Putting all titles into entities
> would not make any sense to me, as it would make
> the work harder IMHO.
>
+1
Thomas
Hello,
you both are right. But since I've found out that en-file was already 5
times bigger than the de-version, I thought 100% English info is better
than 20% German.
And from the translation point of view it's in such a case also better
to start from scratch than to look for some reuseable wor
Well done,
thanks!
Cu,
Thomas
Gabor Hojtsy wrote:
> gobaSat Mar 23 17:44:03 2002 EDT
>
> Modified files:
> /phpdoc/scripts revcheck.php
> Log:
> Renewed revcheck code, separated logic from presentation [mostly],
> added color types, revision types, colors to transla
22 18:30:33 2002
> @@ -16,6 +16,7 @@
> # +------+
> # | Authors:Thomas Schöfbeck <[EMAIL PROTECTED]> |
> # | Gabor Hojtsy <[EMAIL PROTECTED]>
Hi Goba,
sorry that I didn't write it explicitely, but this message was adressed to
the german ones :)
Cu,
Thomas
Gabor Hojtsy wrote:
> > 2.) General switch-over:
> > The only missing information in revcheck are the missing
> > revision-numbers and maintainers in the missing revcheck-tags (89
Hello,
just to prevent confusion: There is nothing to do in translation.xml,
just the historical Translators
should be maintained extra.
But to prevent the active de-translators from (IMHO) unnecessarary work,
I have 2 proposals, and I'd volunteer for the necessary work to realize
that:
1.) Mea
(and searched them in CVS, because this
info isn't available in the historical Translators).
Cu,
Thomas
Egon Schmid wrote:
> Please update Translators and translation.xml.
>
> -Egon
>
> From: "Thomas Schöfbeck" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
Hi Guys,
are you shure, that everybody is still working with this instead of the
"new" revcheck?
(see the howto at http://cvs.php.net/cvs.php/phpdoc/howto/howto.html.tar.gz,
and
http://at.php.net/manual/de/revcheck.html)
Just a thought, the actual states of "my" files are all only actual in
revc
Hi Friehelm, Egon,
I don't agree to rely on "historical" structures, especially in
this case, where the old translation doesn't seem to be equal
to the current one (the old info.xml where the history was only
a part of had 6kB, appendices/history.xml curr. has 13 kB, so
IMHO it's better to leave
Hi Egon,
I've just synced to the en-tree, where this section is also deleted
(also don't know why :)
Cu,
Thomas
Egon Schmid wrote:
> From: "Thomas Schoefbeck" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, March 06, 2002 8:11 PM
> Subject: [PHP-DOC] cvs: phpdoc /de/chapters i
Hi Egon,
I've just synced to the en-tree, where this section is also deleted
(also don't know why :)
Cu,
Thomas
Egon Schmid wrote:
> From: "Thomas Schoefbeck" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, March 06, 2002 8:11 PM
> Subject: [PHP-DOC] cvs: phpdoc /de/chapters i
Hi all,
after a long break I'm back again, and it wouldn't be me,
if I didn't want to turn around everything :)
What I've recognized is that the page-width of
http://www.php.net/manual/en/security.database.php causes difficulties
to read this chapter for people with a smaller screen-resolution.
Hi,
you were of course right, and was "a little" scatter-brained yesterday,
sorry (and thanks for the fast revert!).
Cu,
Thomas
Derick Rethans wrote:
> On Tue, 20 Nov 2001, Gabor Hojtsy wrote:
>
> > comitted... I think a revert is needed here...
>
> I already did that.
>
> Derick
Hi Sebastian,
it looks great!
I'd just suggest to put the "See also" below the "Examples", and to
consider
splitting up the "see also"-links into some columns, since the number
can get
big (and so the list long :).
Cu,
Thomas
Sebastian Mordziol wrote:
> Hi, The link below is my contribution
Hi Conni,
It's a pity that Egon and you don't see the advantages, but you don't
have to use it.
But since Egon wrote "no need", and not "it's forbidden", at least I'll
use it for my files.
Cu,
Thomas
another german translator :)
Cornelia Boenigk wrote:
> > To make the story short. German tran
Egon Schmid wrote:
>
> To make the story short. German translators don´t need a revision
> number or a revision comment. We need the diffs up to that date,
> when the original translator or maintainer leaved the project. It is
> impossible to make a script which tells a new translator he have to
Hojtsy gábor wrote:
>Yes, it would be good to get some opinions from the people
>administrating the servers what would be a good strategy
for
>naming files to avoid those 87 redirects Sascha mentioned
>about. It makes sysadmin work just hell to remember
what
>they are and why...
It is not jus
Hi!
Is Catharina still active?? (The assignment is 19 months old).
Greetz,
Thomas
Mark Kronsbein wrote:
> mk Wed May 16 17:50:39 2001 EDT
>
> Modified files:
> /phpdoc/de/features remote-files.xml
> Log:
> remote-files.xml is assigned to Catharina Paulsen in Translators
Hojtsy Gabor wrote:
> > > > Is
> > > >
> > Right.. or like I've already said
> >
> >
> > Directory/File Translator Status/EN
> > =
> > bookinfo.xml perugini T1.13
> >
> >
> >
> > > >
> >
> > We can use
> > //CVS/Entries
> >
> >
> > on
Hi Luca,
Thanks for the offer from your last posting!
As Goba already explained, we should check on the translation-side the
comment in the file ().
Even the is really useful for the
working-copies,
(as also very good explained by Goba :), I think that it doesn't matter
if we
check against the
> Is
>
> a good idea? It is (on purpose) very similar to:
>
Great!
Hi Luca,
thanks you for this proposal, your d-param is what I meant, but only
from within the file (That saves sometimes a second commit, and has
other advantages).
But it shows, that others are also working on this issue.
Maybe we should really try to agree on a common solution for this?
Cu,
Hojtsy Gabor wrote:
> > No. One revision is not enough. We need the revision history and that
> > should no be in the documentation. Your way is also possible, but to what
> > revision?
>
> How is the revision history is useful?? Why a simple revision
> number is not enough? OK, lets draw a tab
[EMAIL PROTECTED] wrote:
> On Tue, Aug 07, 2001 at 04:55:14PM +0200, Hojtsy Gábor wrote:
> > >> So we have a $Revision tag in the english file, showing the actual
> > >> english version number. We can have a comment in the translated
> > >> version, about what english version number it correspo
[EMAIL PROTECTED] wrote:
> On Tue, Aug 07, 2001 at 11:39:53AM +0200, Thomas wrote:
> > [EMAIL PROTECTED] wrote:
> >
> > > On Tue, Aug 07, 2001 at 10:46:25AM +0200, Thomas wrote:
> > > > Hojtsy gábor wrote:
> > >
> > > > > >>I too think that this is not needed for translations. I can't think
> > >
Egon,
DOCBOOK-XML, look into the result!
If the first parameter is optional, the second parameter is also optional!
Please look at bug #12550, look what I and you have done, and correct it.
Regards,
Thomas
Egon Schmid wrote:
> eschmid Mon Aug 6 23:38:28 2001 EDT
>
> Modified
Hi there,
this problem exists for all languages, and many other files.
I didn't go deep into it (I have no karma for PHPweb [or didn't get at
least
an answer to the request at the time with the chm-manuals], so somebody
else has to take this task), but IMHO the problem seems to be the style.css
Hello all,
(hope) I'm finally back again (had probs with my eyes, and don't have a 27"
monitor, so I was "offline" :).
That seems to be a "reserved" file with "Edit" in CVS. This might occur more
often in the future, since some CVS-clients work with this function by default
(like, WinCVS).
Cu,
Hi Egon,
[EMAIL PROTECTED] wrote:
> You don´t need additional libraries for the Windows version. They are
> compiled in. Look at php4win.de or at zend.com.
I don't wanna document the php4win.de-version, since Daniel packs a lot of
unsofficial stuff in it.
But if you're sure about zend.com (whi
Hi Phil,
Phil Driscoll wrote:
> ...
> As far as I am aware...
> Many of the extensions are interfaces to external programs, databases, and so
> on. If you don't have the relevent external programs installed on your
> machine, many of teh extensions won't start up as they depend on dlls whic
Hi!
Hi!
Thanks for the explanation, didn't know this cvs-feature.
This sounds very good, as it saves a second commit in the translators.
But the bigger task would be reach out the message (We had this
"version-issue" for Germans already, and also Egon seemed to agree
in his message from 01-04-
Hi Jeroen,
thanks for this answer, and I also didn't doubt that he's really
ready (NOW, but not in half a year, if he has to go to the hospital
tomorrow).
> Even better, IMO, is to include the en-version as a comment in the xml file
> itself.
>
> What about a $Revision: $ comment in all english
ve the best of the people, but what if Martin (or anybody else)
has to stop to work for the manual, or - as it was with Wolfgang -
has no time left for a long time.
OK, some other silly guy (like me now) might do all the unnecessary
stuff again.
Thomas
P.S.: Wasn't it you who wrote as comm
Hi all,
during the translation of install.xml I've stumbled twice over this
sentence in the Windows-part:
** snip **
Some extensions require you to have additional libraries installed
on your system for the module to work correctly. The PHP FAQ has
more information on where to get supporting lib
tom Wed Jul 11 05:16:59 2001 EDT
Modified files:
/phpdoc/de/functionsarray.xml
Log:
change wrong parameters (Bug#12037)
Index: phpdoc/de/functions/array.xml
diff -u phpdoc/de/functions/array.xml:1.17 phpdoc/de/functions/array.xml:1.18
--- phpdoc/de/
tom Sun Jul 1 18:05:13 2001 EDT
Modified files:
/phpdoc/de/functionserrorfunc.xml
Log:
Corrected link
Index: phpdoc/de/functions/errorfunc.xml
diff -u phpdoc/de/functions/errorfunc.xml:1.2 phpdoc/de/functions/errorfunc.xml:1.3
--- phpdoc/de/func
tom Thu Jun 28 15:36:55 2001 EDT
Modified files:
/phpdoc/de Translators
Log:
changed status of com.xml, and maintainer of install.xml (as agreed with Wolfgang)
tom Thu Jun 28 15:29:33 2001 EDT
Modified files:
/phpdoc/de/functionscom.xml
Log:
transl. now ready
.xml Thomas Schöfbeckfertig (bis V 1.68)
+array.xml Thomas Schöfbeckfertig (bis V 1.72)
aspell.xml Uwe Steinmann fertig
bc.xml Uwe Steinmann fertig
bzip2.xml Th
tom Sun Jun 24 19:00:26 2001 EDT
Modified files:
/phpdoc/de/functionsfilesystem.xml
Log:
added changes from en-v1.65 to 1.68, is now ready till en-v1.69
Index: phpdoc/de/functions/filesystem.xml
diff -u phpdoc/de/functions/filesystem.xml:1.24 phpdoc
tom Sun Jun 24 18:54:46 2001 EDT
Modified files:
/phpdoc/de/functionsarray.xml
Log:
added changes en-v1.68 to 1.71, now equiv. to v 1.72
Index: phpdoc/de/functions/array.xml
diff -u phpdoc/de/functions/array.xml:1.14 phpdoc/de/functions/array.xml:1.
iebrock [[EMAIL PROTECTED]] :)
+
+Written by Gabor Hojtsy ([EMAIL PROTECTED]), and adapted by
+Thomas Schöfbeck ([EMAIL PROTECTED]). Contact them or the phpdoc list
+([EMAIL PROTECTED]) if you have any questions or suggestions...
+
+Last modified: 2001/06/24
\ No newline at end of file
tom Sun Jun 24 18:17:23 2001 EDT
Modified files:
/phpdoc make_chm_fancy.php
Log:
looks now directly in lang-dir for the fancy-index
Index: phpdoc/make_chm_fancy.php
diff -u phpdoc/make_chm_fancy.php:1.5 phpdoc/make_chm_fancy.php:1.6
--- phpdoc/make_chm_
tom Sun Jun 24 18:14:40 2001 EDT
Modified files:
/phpdoc make_chm.bat
Log:
makes fancy-dir automatically now, and cleans up .hh*-files
Index: phpdoc/make_chm.bat
diff -u phpdoc/make_chm.bat:1.5 phpdoc/make_chm.bat:1.6
--- phpdoc/make_chm.bat:1.5 Sat
tom Mon May 21 12:39:31 2001 EDT
Modified files:
/phpdoc/de/functionsarray.xml
Log:
Typo, transl. a function
Index: phpdoc/de/functions/array.xml
diff -u phpdoc/de/functions/array.xml:1.11 phpdoc/de/functions/array.xml:1.12
--- phpdoc/de/functions/
1 - 100 of 102 matches
Mail list logo
