Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-19386

Multibyte characters garbled when importing a json file by API Designer

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • fuse-7.11.1-GA
    • fuse-7.10.2-GA
    • Apicurito
    • None
    • False
    • None
    • False
    • Release Notes
    • % %
    • Todo
    • Release Note
    • Hide

      A possible workaround is to not load the OpenAPI doc from file, but create a new API, choose the Source tab, switch to JSON mode and copy paste the content of attached openapi-spec.json into the text area. Then save it.
      When switching back to Design tab, alll characters seem to be displayed correctly.

      Show
      A possible workaround is to not load the OpenAPI doc from file, but create a new API, choose the Source tab, switch to JSON mode and copy paste the content of attached openapi-spec.json into the text area. Then save it. When switching back to Design tab, alll characters seem to be displayed correctly.
    • Hide

      Red Hat Integration - API Designer 7.10.3 is installed by the operator hub.

      • Open "API Designer".
      • Click "Open API".
      • Select the attached json file, "openapi-spec.json".
      • Check the characters under INFO -> Description.
      Show
      Red Hat Integration - API Designer 7.10.3 is installed by the operator hub. Open "API Designer". Click "Open API". Select the attached json file, "openapi-spec.json". Check the characters under INFO -> Description .

      An exported json file is UTF-8 encoding and Multibyte characters are displayed with cat command or any text editors.
      However when API Designer, apicurito, imports the file, Japanese characters are garbled.

            parichar@redhat.com Paul Richardson
            rhn-support-hfuruich Hisao Furuichi
            Aneta Cadova Aneta Cadova
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: