You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We work with IBM Z Open Editor in a Git repository context.
As standard, Git repositories use UTF-8 encoding for source management.
The ZOE extension provides line overflow management, and triggers a warning if a line exceeds the line length limit, set by default to 80 characters (modifiable).
But in the presence of multi-byte characters, as is the case in UTF-8, the length in characters is incorrectly calculated: it is the length in number of bytes that is used, and which causes the wrong emission of a warning message.
ZOE reports that the warning message can be wrongly emitted, but it would be better if it did not emit it and did a correct calculation of length in characters and not in bytes.
Depending on whether the check is done by the Language Server, probably coded in Java, or by the VS Code extension's own code, probably coded in TypeScript, there must be routines to calculate a string length based on the encoding used for the file (in our case UTF-8).
The Euro character is encoded on 3 bytes in UTF-8: 0xE2, 0x82 and 0xAC
COBOL can calculate a length in characters on a UTF-8 string... COBOL better than Java or TypeScript? 💪 🤣
FYI, the following setting does not solve the problem:
Description of the enhancement requested
Hi,
We work with IBM Z Open Editor in a Git repository context.
As standard, Git repositories use UTF-8 encoding for source management.
The ZOE extension provides line overflow management, and triggers a warning if a line exceeds the line length limit, set by default to 80 characters (modifiable).
But in the presence of multi-byte characters, as is the case in UTF-8, the length in characters is incorrectly calculated: it is the length in number of bytes that is used, and which causes the wrong emission of a warning message.
ZOE reports that the warning message can be wrongly emitted, but it would be better if it did not emit it and did a correct calculation of length in characters and not in bytes.
Depending on whether the check is done by the Language Server, probably coded in Java, or by the VS Code extension's own code, probably coded in TypeScript, there must be routines to calculate a string length based on the encoding used for the file (in our case UTF-8).
The Euro character is encoded on 3 bytes in UTF-8: 0xE2, 0x82 and 0xAC
COBOL can calculate a length in characters on a UTF-8 string... COBOL better than Java or TypeScript? 💪 🤣
FYI, the following setting does not solve the problem:
Thanks.
The text was updated successfully, but these errors were encountered: