Skip to content

Provide an optional argument to define the encoding used in the json file #59

@smarie

Description

@smarie

Currently it seems that the json file generated uses system encoding. Unfortunately WebVOWL does not load the file using the system encoding, but rather UTF-8.

OWL2VOWL could at least use utf-8 by default to encode, or propose a commandline option to define the encoding to use.

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