php.net |  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
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
21 - 18 = ?
Subscribe to this entry?

 
 [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...

http://nl.php.net/manual/nl/language.variables.predefined.php
http://nl.php.net/manual/en/language.variables.predefined.php

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

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-03-12 05:44 UTC] torben@php.net
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 
propagate.


Torben
 [2002-07-16 02:11 UTC] philip@php.net
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] nlopess@php.net
I've implemented (in livedocs) a warning if the file is outdated.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Mar 28 18:01:29 2024 UTC