MantisBT
Mantis Bug Tracker Workflow

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0031670Community[OCCT] OCCT:Data Exchangepublic2020-07-16 23:262020-07-24 13:03
Reporterrobertlipman 
Assigned Togka 
PrioritynormalSeverityminor 
StatusnewResolutionopen 
PlatformOSOS Version
Product Version[OCCT] 7.3.0 
Target VersionFixed in Version 
Summary0031670: Data Exchange - cp1251 Cyrillic characters in STEP file
DescriptionCyrillic characters in STEP files are not always correctly displayed by CAD Assistant. I cannot figure out why sometimes it works and other times it doesn't. This issue might be similar to other OCC issues regarding text characters in STEP files.
Steps To ReproduceTwo STEP files are attached in a zip file. Import them to CAD Assistant. In the Model Browser, block-russian.stp displays the correct characters. russian.stp does not.
TagsNo tags attached.
Test case number
Attached Fileszip file icon russian-step.zip (510,774 bytes) 2020-07-16 23:26
png file icon cadass_step_locale.png (66,888 bytes) 2020-07-24 12:56
png file icon cadass_step_win1251.png (78,994 bytes) 2020-07-24 12:56

- Relationships
related to 0028454assignedgka Data Exchange - Names with Special Characters Cannot Be Read from STEP or IGES Files 
related to 0031589newgka Data Exchange - unable to read STEP file containing mangled characters 

-  Notes
(0093288)
kgv (developer)
2020-07-24 13:03

> I cannot figure out why sometimes it works and other times it doesn't
This is because block-russian.stp is encoded in UTF-8, while russian.STEP is encoded into cp1251. STEP format does not provide information about used text encoding (it is supposed to be UTF-8) and OCCT STEP reader has no logic automatically detecting encodings nor complete list of conversion tables.

So far, it is only possible specifying "System locale" as alternative to "UTF-8" to STEP translator, but this will work only if STEP file is opened on Windows with exactly in the same locale as where it has been written, and will corrupt any other encoding (legacy way to encode text files before UTF-8 become used everywhere).

- Issue History
Date Modified Username Field Change
2020-07-16 23:26 robertlipman New Issue
2020-07-16 23:26 robertlipman Assigned To => gka
2020-07-16 23:26 robertlipman File Added: russian-step.zip
2020-07-24 12:38 kgv Summary Cyrillic characters in STEP file => Data Exchange - Cyrillic characters in STEP file
2020-07-24 12:40 kgv Summary Data Exchange - Cyrillic characters in STEP file => Data Exchange - Windows-1251 Cyrillic characters in STEP file
2020-07-24 12:55 kgv Relationship added related to 0028454
2020-07-24 12:56 kgv File Added: cadass_step_locale.png
2020-07-24 12:56 kgv File Added: cadass_step_win1251.png
2020-07-24 13:03 kgv Note Added: 0093288
2020-07-24 13:03 kgv Relationship added related to 0031589
2020-07-24 13:03 kgv Summary Data Exchange - Windows-1251 Cyrillic characters in STEP file => Data Exchange - cp1251 Cyrillic characters in STEP file


Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker