Hi Dimitris-
Please revert this from the English tree.
Regards,
Philip
On Sun, 20 Jul 2003, Dimitris Glezos wrote:
> subbieSat Jul 19 20:09:10 2003 EDT
>
> Modified files:
> /phpdoc/en/reference/mail/functions ezmlm-hash.xml mail.xml
> Log:
> add
subbie Sat Jul 19 20:09:10 2003 EDT
Modified files:
/phpdoc/en/reference/mail/functions ezmlm-hash.xml mail.xml
Log:
added mail
Index: phpdoc/en/reference/mail/functions/ezmlm-hash.xml
diff -u phpdoc/en/reference/mail/functions/ezmlm-hash.xml:1.9
phpdoc/en/r
betzSat Jul 19 15:37:59 2003 EDT
Modified files:
/phpdoc/en/language constants.xml operators.xml
Log:
WS fix, no tabs
Index: phpdoc/en/language/constants.xml
diff -u phpdoc/en/language/constants.xml:1.33 phpdoc/en/language/constants.xml:1.34
--- phpdoc/en
> > > some files under /language are really huge and a pain ;-) to translate.
> > > What do you think about splitting them up to make them a bit easier to
> > > handle and translate?
> > > e.g.:
> > > control-structures: split by structure
> > > types: split by type
> > > ...
> > >
> > > opinions?
On Saturday 19 July 2003 18:31, Gabor Hojtsy wrote:
> > internals@ have this imho nice feature, getting a mail once per month
> > (?). Might it be possible to have this for phpdoc too? A bug summary of
> > doc bugs once per month send to the doc list? Having this feature would
> > probably drive mo
On Saturday 19 July 2003 18:27, Gabor Hojtsy wrote:
> > some files under /language are really huge and a pain ;-) to translate.
> > What do you think about splitting them up to make them a bit easier to
> > handle and translate?
> > e.g.:
> > control-structures: split by structure
> > types: split
internals@ have this imho nice feature, getting a mail once per month (?).
Might it be possible to have this for phpdoc too? A bug summary of doc bugs
once per month send to the doc list? Having this feature would probably drive
more attention to doc bugs (didn't want to say that there is too les
some files under /language are really huge and a pain ;-) to translate.
What do you think about splitting them up to make them a bit easier to handle
and translate?
e.g.:
control-structures: split by structure
types: split by type
...
opinions?
+1, *but* please provide a plan on what the exact fi
Hi,
internals@ have this imho nice feature, getting a mail once per month (?).
Might it be possible to have this for phpdoc too? A bug summary of doc bugs
once per month send to the doc list? Having this feature would probably drive
more attention to doc bugs (didn't want to say that there is to
Following are the top 20 pages of the manual, sorted by the number
of user notes contributed. These sections could use a polish, those
notes represent 11.1% of the 10029 total user notes.
Notes | Page
---+-
86 | http://php.net/manua
Hi,
some files under /language are really huge and a pain ;-) to translate.
What do you think about splitting them up to make them a bit easier to handle
and translate?
e.g.:
control-structures: split by structure
types: split by type
...
opinions?
Regards
Friedhelm
--
PHP Documentation Mai
than giving more hours to work to dozens of translators, just because
this method seems to be cleaner. Or are you confident, noone really
cares about the diffs? Then why do we have those translation CVS
modules??
So you're saying we should keep the English docs a 'mess' because of the
translations
On Sat, 19 Jul 2003, Gabor Hojtsy wrote:
> Second maintaining some compatibility code in the processing system is
> much easier to handle,
It's just the wrong way to fix it... you're also not patching IE or
Mozilla to make your sites look good in it.
> than giving more hours to work to dozens
I am for adding those tags by the way for clarity, but I didn't like the
way it was done, and I am not in favor of such mass commits, especially
in cases where the target of the commit is not critical, it can be
easily overcome in the processing system...
Hell no, tags should be there in the scr
14 matches
Mail list logo
