Skip to content

Problem with encoding on accessing STRING and CHAR #4

Description

@pmamod

In v1.0.1 you have implemented the fixed encoding 'ascii' which unfortunately only use 7 bits per character. So any char code above 0x7f will be read as an ascii code and the information of bit 7 is lost.
My proposal is to integrate a support for more encodings: The default encoding for STRING and CHAR should be 'latin1' (equal to 'binary') which handles all 8 bits. For unicode I think the use of other keywords could be a solution: for example USTRING and UCHAR with 'utf8' encoding, WSTRING and WCHAR with 'ucs2' encoding (which meens WideString & WideChar like defined in MS Windows)
What do you think about this? If you like I could modify the code of s7items.js an send you as a proposal.
Looking forward to your answer.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions