Better support XML Unicode storage in OCAF

Vico Liang's picture

There might be history reason, OCCT OCAF doesn't well support for Unicode XML. Unicode is essential in nowadays application. LDOMBasicString is mainly designed for ASCII string though it has Unicode encoding by adding prefix unreadable magic number ##feff. The encoded Unicode storage is not user friendly and readable from XML file. I propose to improve the XML feature of OCAF to fully support Unicode. Does OCCT team have any plan for such feature?

mpv's picture

minor issue

Hello Vico,

OCCT OCAF supports store and restore unicode strings in XML formats without losing data. #feff is well known byte order mark.
Changing of this may cause problems of backward compatibility. So, this note is considered as very minor issue.

Vico Liang's picture

worth to do

Dear mpv,

I agree that OCAF supports store and restore unicode string in xml formats without losing data.

But A very important feature of XML is its user friendly readable feature. Current OCAF XML storage looks like this:

##feff6d4b8bd54ee378014ee378010031

Do you know what the content is from the above unicode xml?

I see OCCT is innovating. Though this is a minor issue, it's still worth to make a improvement. I believe there must be ways to resolve the problem of backward compatibility.

VL

mpv's picture

acceleration of development

Dear Vico,

Indeed it is a minor issue and it is not a priority for us at the moment and as result is unscheduled.
If you are interested in corresponding development acceleration you may
a) make contribution via the Development portal
b) contact us via our Contact Form (we will discuss with you possible ways of the issue solving)

Vico Liang's picture

Might be necessary in future

Dear mpv,

In the short run it is a minor issue. Maybe i'm a completist. I do insist that this should be revised. Anyway, it depends on the resource and plan of OCCT team. I'm not so urgent to acceleration the development. I just give some advise to help OCCT better.

VL

www.opencascade.com

Copyright 2011-2019
OPEN CASCADE SAS
Contact us