|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #16015 Online Documentation Differs in languages
Submitted: 2002-03-12 05:35 UTC Modified: 2005-09-02 13:34 UTC
From: ronnie at bit dot nl Assigned:
Status: Not a bug Package: Documentation problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Bug Type:
From: ronnie at bit dot nl
New email:
PHP Version: OS:


 [2002-03-12 05:35 UTC] ronnie at bit dot nl
I have found a difference in two PHP manuals which both are online at...

De Dutch page contains information about superglobals and the english page about Apache Variables.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2002-03-12 05:44 UTC]
The Dutch manual appears to be in the middle of updating,
and got that part of the Dutch version done before it did
the English. Changes to the manual can take a while to 

 [2002-07-16 02:11 UTC]
Making this a documentation feature request to help lesson the impact of outdated translations. 
Idea #1: 
Use the revision and translator files, along with whatever else comes to mind, to let the reader know they're reading an outdated translation.  Does a small change to en/ instantly make the nl/ outdated? No. How about two small changes?  Maybe not.  One large sweeping change?  Sure, I think so...  This of course is why no such super system exists, maybe one will be thought of ...  What information could be extracted to help the reader?  Maybe asking a lot :) 
Idea #2 
Here's a start.  Keep all function methodsynopsis information up-to-date, automagically, in all languages.  The simplest way is to make this information identical for all translations.  One copy, in en/.  For example, let's take rtrim(): 
  string rtrim ( string str [, string charlist]) 
That could easily remain the same in all manual translations ... in English, Finnish, Dutch, etc.  A string is a string.  If parameter names should change or not, who knows, it'd be easier if not :)  AFAICT parameter names are rarely translated/changed anyways.  Where should the methodsynopsis info be kept?  I would assume in the en/ function files.  If also in the translated files somehow it needs to be kept in sync.  Anyway, this phpdoc feature request doesn't need to get *too* specific :)  Look at fopen() for an example on why this feature request is good.
 [2005-09-02 13:34 UTC]
I've implemented (in livedocs) a warning if the file is outdated.
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Wed Oct 27 01:03:34 2021 UTC