View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000372610000-008: Data AccessSpecpublic2017-01-31 17:112017-05-30 16:22
ReporterJim Luth Assigned ToKarl Deiretsbacher  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0003726: Some special characters in UNECE_to_OPCUA.csv appear as '?'
Description

Looks like some characters, at least Ohm, have not been exported to the

https://opcfoundation.org/UA/EngineeringUnits/UNECE/UNECE_to_OPCUA.csv

instead they are written as '?'

That's what I see, if I look at it with 'less' in OSX, whereas other special characters display with their code, so I assume they are not correct in the file.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0003471 closedrandyarmstrong NodeSets, XSDs and Generated Code Some special characters in UNECE_to_OPCUA.csv appear as '?' 

Activities

Karl Deiretsbacher

2017-01-31 17:11

developer   ~0007825

From Thomas Kugler (ascolab):
In code we are representing the special characters in octal notation. For OHM the DisplayName is "\342\204\246". In a gui this is displayed as "Ω".
The reason for the octal notation is that some IDE like Visual Studio are changing the encoding of the file without notifying if special characters like Ω are in the file.

BjarneBostrom

2017-01-31 17:11

reporter   ~0007826

The problem is that the file actually contains
OHM;5195853;ohm;?

With the ? being an actual '?' character and not something that cannot be displayed.

Could be please get this file as UTF-8? Preferably without Byte Order Mark.

BjarneBostrom

2017-01-31 17:11

reporter   ~0007827

Also the row
D62;4470322;second [unit of angle];""""
is wrong, it should only have a single "

randyarmstrong

2017-01-31 17:11

administrator   ~0007828

Can now autogenerate the file from the UNECE master.
The BOM is necessary to ensure it loads into Excel properly.

Jim Luth

2017-01-31 17:12

administrator   ~0007829

Part 8 needs to be updated to indicate the latest version of the UNCEFACT that this version of UA is tied to.

Karl Deiretsbacher

2017-05-30 16:22

developer   ~0008192

Fixed in Part 8 1.04.04/

Jim Luth

2017-05-30 16:22

administrator   ~0008193

Agreed to changes in telecon.

Issue History

Date Modified Username Field Change
2017-01-31 17:11 Jim Luth New Issue
2017-01-31 17:11 Jim Luth Status new => assigned
2017-01-31 17:11 Jim Luth Assigned To => Karl Deiretsbacher
2017-01-31 17:11 Jim Luth Issue generated from: 0003471
2017-01-31 17:11 Jim Luth Relationship added related to 0003471
2017-01-31 17:12 Jim Luth Note Added: 0007829
2017-01-31 17:13 Jim Luth Project NodeSets, XSDs and Generated Code => 10000-008: Data Access
2017-01-31 17:13 Jim Luth Category Api Change => Spec
2017-01-31 17:13 Jim Luth Target Version => 1.04
2017-05-30 16:22 Karl Deiretsbacher Note Added: 0008192
2017-05-30 16:22 Karl Deiretsbacher Status assigned => resolved
2017-05-30 16:22 Karl Deiretsbacher Fixed in Version => 1.04
2017-05-30 16:22 Karl Deiretsbacher Resolution open => fixed
2017-05-30 16:22 Jim Luth Note Added: 0008193
2017-05-30 16:22 Jim Luth Status resolved => closed