You might be correct from a scientifical or theoretical point if view. In real world average users expect a "kilobyte" to be 1024 bytes.

I disagree, many users don't even know that 'kB' and 'KiB' are different things 
but 
instead there is just 'kb' to them (I have no factual evidence to support this, 
however that is what can normally be seen from real-world users), therefore 
they're 
not going to know that a kilobyte should be 1024 bytes or 1000 bytes.

The documentation should reflect the correct term and/or value - since this has 
caused me quite a bit of confusing when reading over it. It stated it 'K' was 
for 
Kilobyte but has a value of 1024; what is the correct meaning of 'K'? It has to 
be 
one or the other.

I agree with the submitter; the correct name (kibibyte) should be used to denote 
1024 bytes. Some people do know the difference between the SI and IEC prefixes 
and this can confuse them. For the people that don't know, it's an opportunity to 
learn about this.

Can we get an update on this? I don't feel this bug report has been handled with 
much communication to resolve an issue that clearly exists, but is being ignored 
even though you agree it is a bug.

It's not a bogus bug.

Just because some standards body wants to redefine words does not change how 98% of people use those words.

People who say kibibyte = libtards.

Where are you getting this 98% from? It's just air facts. Everyone so far has 
agreed this bug exists, yet are refusing to change 1 simple word for no reason at 
all.

Is it even worth reporting bugs against PHP documentation?

Just to reiterate, I'm not asking to change the value of K, just to change the 
wording. No code will be effected by changing this.

There is one comment that agrees with you on this bug.  Saying "Everyone" here is 
rather overstating things, don't you think?  Nobody is arguing that it isn't 
technically correct, but in the real world, people don't actually know what a 
kibibyte is.  I have taken a couple of quick straw polls of the audience at my 
various PHP talks and typically there are 1 or 2 people in an audience of 50 who 
know what it is.  The PHP documentation is not the place for evangelizing this.

By the way, since you are being pedantic, it is "affected" not "effected" in that 
context.

For 'everyone' sorry I was referring to the mailing list discussion regarding this 
bug.

But surely those that don't know what a kibibyte is can (like I've said in the 
mailing list) A) keep reading to see the value mentioned (as the PHP documentation 
does currently or B) Google what a kibibyte is. Anyone with half a braincell could 
do either.

All this does is add confusion for those that know the difference and expect the 
value of kibibyte to *be* the value of a kibibyte, not what ever PHP decides a 
kibibyte should be. I see 100% no reason for the documentation to directly use the 
wrong *word* when using the correct word would not affect (thank you for the 
correction...).

I'm not saying change the value, just 1, simple word.

Replace all 'kibibyte' with 'kilobyte' in the third paragraph of my previous 
comment, sorry typos on my part.

I added a few words on the subject.