Buffer.toString docs != actual

[Bonuspunkt]

• Version: v6.7.0
• Platform: Win10 x64 v1511

according to the docs

const buf2 = Buffer.from('tést');

// Prints: tés
console.log(buf2.toString('utf8', 0, 3));

the actual output is

té

[addaleax]

The start and end indices of .toString() refer to byte offsets in the Buffer, and are not character counts.

So, when looking at buf2, which contains the bytes 74 c3 a9 73 74, what gets decoded are the first 3 bytes, namely 74 c3 a9, and those correspond to té.

So, yeah, this is expected behaviour, and the docs are not wrong here either, but they could be a little clearer.

[addaleax]

Oh, right, sorry, the docs are wrong here. They don’t even use the right buf2 variable in the example.

(That doesn’t change that returning té is the expected behaviour, though.)