Special Characters and Umlauts (ÄÖÜß) 2

JSN

In the attached File there is a single IfcSpace with Property Set “Raum”, where you can find Property “123ÖÄÜß4567” with the same Value “123ÖÄÜß4567”. So the first entry in the Ifc is the Property, followed by their Value:

This was also my problem described here …
https://society.solibri.com/topic/2405/solibri-9-13-4-has-been-released/11?_=1688572605287

@marchi said in Special Characters and Umlauts (ÄÖÜß) 2:

Mine was UTF-8 and then I changed it to (default)Windows-1252 (Europa) and the new imported IFCs are OK. In the SMC Files I had to Update all the Models, for the changes to take effect.

The (default)Windows-1252 (Europa) did not work for me, had to change it to UTF-8, so hope that it won’t have to change it constantly. Still don’t get why this is happening in the first place as exports from my computers are working fine and those from other project partners won’t. The windows encoding and AC xml seems to be identically though so not sure how to prevent this.

m.neustadt

which is your authoring software? When you work with Vectorworks you should set the checkbox in the ifc export dialogue with the setting “export text as unicode” or sth similar.
Otherwise, you won’t get any “Umlauts”.

JSN

@m-neustadt said in Special Characters and Umlauts (ÄÖÜß) 2:

which is your authoring software? When you work with Vectorworks you should set the checkbox in the ifc export dialogue with the setting “export text as unicode” or sth similar.

The model I got which causes problem was exported from Archicad 25. However I have no issues with AC on my computer and I think there is not really a possibility to specify that in the translator settings. I know there is an xml where you can change some stuff if you have problems within AC but that’s not the case here. Moreover the OS settings in terms of region settings and charcter set seem to be fine as well. And actually the IFC encoding itself is looking good as well and as the import setting change helps for now I doubt that it’s (solely) an export failure. However I don’t understand why it’s only happening for some models from the same export software.

m.neustadt

What about checking

a) an Archicad forum/board online

b) checking your local Archicad reseller. There must exist an issue regarding Umlauts, unicode,…

Pasi Paasiala

I was able to open both files with UTF-8 setting in latest Solibri (9.13.4.19). I also checked the files. They both have encoded the umlaut characters, although in different ways.

AC 25 does it like this:

#1132= IFCPROPERTYSINGLEVALUE(‘123\X2\00D600C400DC00DF\X0\456’,$,IFCLABEL(‘123\X2\00D600C400DC00DF\X0\4567’),$);

and AC26 like this:

#259=IFCPROPERTYSINGLEVALUE(‘123\X\D6\X\C4\X\DC\X\DF456’,$,IFCLABEL(‘123\X\D6\X\C4\X\DC\X\DF4567’),$);

They both seem valid. We may have had some problems with the way AC25 did the encoding and that is fixed in the latest version.

JSN

@Pasi-Paasiala said in Special Characters and Umlauts (ÄÖÜß) 2:

They both seem valid. We may have had some problems with the way AC25 did the encoding and that is fixed in the latest version.

It’s not just affecting models from Archicad 25 but e.g. also Revit 2021 and those models have worked well in the past. Seems like this just broke recently in one of the latest Solibri versions but good to hear that this has been already adressed.

Pasi Paasiala

@JSN If there are any IFC files with these kinds of problems with the latest version, please let us know.

JSN

@Pasi-Paasiala To make this clear, this is still happening with 9.13.4.19.

Pasi Paasiala

@JSN Please share an example IFC or even just a line from the IFC that contains the string that does not get properly decoded.

JSN

@Pasi-Paasiala I’ve elaborated it here: https://society.solibri.com/topic/2405/solibri-9-13-4-has-been-released/11?_=1689078829846
where I have also mentioned the difference in encoding you pointed out by refering to the specific lines of the IFC:

Also another incompatible file I got today, exported from Revit 2021, is encoded the same way as the following line illustrates:

#34059= IFCPROPERTYSINGLEVALUE(‘Reference’,$,IFCTEXT(‘UV_O5_Freifl\X2\00E4\X0\che’),$);

I have to check if I can share a smaller model, but I guess it’s pretty obvious.