Font display issues when publishing any two or more DWG files with Chinese fonts into a bim file

[guanhuaming]

When using the snapshot tool to publish any two or more DWG files with Chinese fonts into a BIM file, there are font display issues. Only the content of the first DWG file is displayed correctly.

These are the two DWG files I tested:
file.zip

This is the result after publishing them into a BIM file:

[pmconne]

Thank you for providing the files.
Is this a duplicate of #6849?
@jffmarker @abeesh

[guanhuaming]

Presumably the two models were created from two separate jobs from the two DWG files. @guanhuaming, is it possible that the two files were from two different folders, and one folder contained font file FangSong_GB2312.ttf while the other did not? If both folders have the font file, we'd need this file in hopes to reproduce what you have seen.

I placed the FangSong_GB2312.ttf font in the font directory of RealDwgBridge, instead of placing it in the same directory as the DWG files. The two DWG files are located in the same directory.

If I place the font in the RealDwgBridge font directory, should all DWG files share this font during conversion?

The font directory of RealDwgBridge is as follows:
C:\Users\Administrator\AppData\Local\imodelbridges\RealDwgBridge\Fonts

By the way, the FangSong_GB2312.ttf font is a standard system font in Windows 7. I am currently using Windows 11.
FangSong_GB2312.ttf font download:
FangSong_GB2312.zip

[donhfu]

Since you are running a local connector, you have done it correctly placing fonts under \Fonts\ sub-folder. I have trouble reproducing the inconsistent display from the two files when placing your font under \Fonts. They both are displayed correctly for me. But my box is in English locale which might be different than yours. We will try some more tests and see if we can reproduce the incorrect display.

[donhfu]

@guanhuaming, please try opening and editing file \Assets\ConvertConfig.xml, find the font mapping section in middle of the file, and add a new entry:

    <TrueTypeFont TypeFace="仿宋_GB2312" AltTypeFace="FangSong_GB2312" AltShxName=""/>

This will get around the mismatched family name for the true type font. We will get the root problem fixed in a future connector release. When the release will get deployed, you will no longer have to manually map your font (although you still can keep the mapping as you wish). Please give this a shot and see if it works for you. Thanks for brining this issue to our attention!

[guanhuaming]

This will get around the mismatched family name for the true type font. We will get the root problem fixed in a future connector release. When the release will get deployed, you will no longer have to manually map your font (although you still can keep the mapping as you wish). Please give this a shot and see if it works for you. Thanks for brining this issue to our attention!

Tested and it works for me. Thank you very much.