Here you are, Ludek.
I tried to attach the rpt file, but got a message that the .rpt content type is not allowed to be attached, so I renamed it to .txt -- you will need to change the extension back to .rpt.
The report has hard-coded Select statements in a Command object and displays 2 rows: the first one is the errant one, displaying squares where the Asian characters should be rendered; the second one is the correct output, showing the Asian characters displaying with the correct font size (24pt.). The first column shows the proper Asian characters; the second column is the test case for each Select statement.
Here is the SQL query for the report:
Select N'看雲聊弄翰,把酒更題詩。' as 'Unicode Content', N'<SPAN style="FONT-FAMILY: SimSun; FONT-SIZE:24pt">看雲聊弄翰,把酒更題詩。</SPAN>' as 'Unicode Content With HTML Markup'
Union
Select N'看雲聊弄翰,把酒更題詩。' as 'Unicode Content', N'<SPAN style="FONT-FAMILY:SimSun;FONT-SIZE:24pt">看雲聊弄翰,把酒更題詩。</SPAN>' as 'Unicode Content With HTML Markup'
This example illustrates 2 variations of the same problem -- an intervening space between either the attribute property and its associated value OR between attribute properties will cause at least some of the attribute properties to fail. The white space should be ignored by CR.
Thanks,
Ethan