Re: Translating parameters names

From: Date: Mon, 17 Nov 2014 19:56:35 +0000
Subject: Re: Translating parameters names
References: 1 2 3 4 5  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969385250@lists.php.net to get a copy of this message
On 17 November 2014 19:50, Andrea Faulds <ajf@ajf.me> wrote: > > > On 17 Nov 2014, at 19:43, Peter Cowburn <petercowburn@gmail.com> wrote: > > > > > > > > On 17 November 2014 19:25, Andrea Faulds <ajf@ajf.me> wrote: > > > > > On 17 Nov 2014, at 15:48, Peter Cowburn <petercowburn@gmail.com> > wrote: > > > > > > So long as things are consistent, at this point in time I think we > should stick with variables names being translated, or not, consistently on > a per-language basis. > > > > No. We should have variable names be untranslated across all languages. > Otherwise we’ll be in for problems if/when named > > parameters come by. > > > > That’s something we only need to worry about if/when named parameters > come by. > > Not true, Reflection already exists. > I can see the reflection argument, but catering for named parameters is something we don’t need to worry about right now. Fact. > > > If/when named parameters do come by, the nature of the documentation > sources means that we really don’t have to care what the “current” (at the > time of changing) variable names are in the docs: we just plonk in the > variable names from The Source. > > Actually, no: the variable names in the source would need to match the > documentation. > “The Source” was written that way to explicitly not mention whether “The Source” was php-src or doc-en. > > > Whether the translation has “<parameter>pagliaio</parameter>” or > “<parameter>haystack</parameter>” is of little consequence. > > Except all the people using the “translated” variable names will find out > they don’t work. > Yes that’s right, but only if/when named parameters become part of the language. > > -- > Andrea Faulds > http://ajf.me/ > > > > >

« previous php.doc (#969385250) next »