What are the differences between the different unicode options in a connector?

Solved365 views
2
0 Comments

By working on a connector that must support Unicode, I found that we have two possible configurations in the driver:

  1. In the Type tag (Protocol->Type), options="unicode" (as described in our documentation)
  2. The Encoding tag (Options->Encoding), value unicode (available from our protocol schema when editing in VS)

I tried both with the same apparent result, so I wonder what the differences are and which one we should use as the best practice.

Gelber Mahecha [SLC] [DevOps Enabler] Selected answer as best 12th April 2023

1 Answer

2
3.74K 1 Comment

Hi Gelber,

The encoding tag will tell the xml parsers, both in your editor such as visual studio and the parser used inside dataminer that the protocol file may contain unicode characters.

The Protocol->Type options="unicode" attribute will tell dataminer and the client applications that e.g. certain parameter descriptions can contain unicode characters. Without this tag the parameter descriptions that contain unicode characters would not be displayed correctly in the UI.

Gelber Mahecha [SLC] [DevOps Enabler] Selected answer as best 12th April 2023
Gelber Mahecha [SLC] [DevOps Enabler] commented

Thanks, Michiel. We need therefore Protocol->Type options attribute for our case.
You are viewing 1 out of 1 answers, click here to view all answers.