Yes. This is expected behavior and scripts of need to be altered to use Base64EncodeRFC. Annoying but that is how it is.
hi bigtom I would consider it expected behaviour if it had also changed in Windows, but it hasn't.
That means that the function is not consistent between the two OS.
I did not know this. I will have to see how it works with PSOS and FMS OS.
OS dependency is something that should be documented at the least.
2 of 2 people found this helpful
Do you have the issue really only on Mac?
On Windows 7 I saw same issue.
Code(Base64Encode("0")) is 100001300061000610006500077, having CRLF at the end.
I wrote assumption in another thread,
and keeping old function with upper compatible new function makes no sense, if old function change its behavior.
In addition I found another issue? that
Length(Base64Encode("0")) is 5 !!
but this is not related to Base64, CRLF is counted as 1 also on FM15.
you are correct, it was probably an hallucination. the behaviour is the same on Windows 10.
I will amend the description.
I didn't know there was an existing thread.
And I agree with "keeping old function with upper compatible new function makes no sense, if old function change its behavior": if it's completely superseded by the new one, keeping it it's only interesting for back compatibility, and we lose it here
you didn't know because it wasn't true... i did a mistake (see new posts below)