Skip to content

Code no longer enforces UTF-8 conversion, results in encoding problems #62

@jvsherwood

Description

@jvsherwood

data = new InputStreamReader(entity.getContent());

Not sure the full reason why, but the prior versions of the SDK specifically read the content as UTF-8, the new code dropped this, and is causing encoding problems when reading content. Old SDK continues to work. For example, reading a story that contains an empty line in its description will show encoding problems using the new SDK vs older.

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