Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

String decoding #533

Open
simonedd opened this issue Nov 14, 2023 · 2 comments
Open

String decoding #533

simonedd opened this issue Nov 14, 2023 · 2 comments

Comments

@simonedd
Copy link

simonedd commented Nov 14, 2023

I have a file with some "special" characters, as in the following Beam definition.
#857=IFCBEAM('3Lt4H72Y9CHQEeh3VllZNY',#6,'\S\Z\S\�l. n\S\ametk. krokev',$,$,#821,#840,$);

After the parsing, the instance of the Beam is empty.
{#857=IFCBEAM('3Lt4H72Y9CHQEeh3VllZNY',#6,$,$,$,$,$,$);}

Thanks.

@martin1cerny
Copy link
Member

IFC file is defined to be an ASCII file. Your example seems to combine Unicode(or some other encoding) and IFC string encoding. This is likely causing the scanner to fail to parse the data. Bear in mind this is an illegal IFC file.

@simonedd
Copy link
Author

simonedd commented Jan 5, 2024

Sorry to come back to this so late. I agree, but you should skip invalid characters instead of failing the reading of the entire entity. All other readers I've tried can import the entity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants