![]() ![]() If you enabled CanBreak and CanShrink properties, then, when rendering a report, the text component will take a size corresponding to the height of the text on the basis of preset font size. Notice: The Shrink Font To Fit is a post-processing property and this should be taken into account when adjusting the text component. When the Shrink Font To Fit property is set to true, the text in the viewer will look like on the picture below I converted the SQL view to csv, and when using a csv file encoded with unicode as the data source, the asian characters do show up. When the Shrink Font To Fit property is set to false, the text in the viewer will look like on the picture below The asian characters show up if they are set as static text the problem is only when the field with the asian characters is pulled from the SQL database Im using. CompatibleMode160 is compatible with version 1.60, which was released 15 years ago, and after which this scaling was added. But as a whole, the kind of report in a preview, after the print and in a pdf-file are same. thats why the font is smaller in the pdf file. The picture below shows a component with the text, which is clearly larger than the size of the component. And when printing and exporting, all sizes are scaled to match the preview. By default, the property is set to false. The property can take two values: true and false, respectively, that means the property is enabled or disabled. The async method for MacOS was added in the 2017.1. This property can be found on the Properties Panel. You can learn more about altering these values from the Configuring Telerik Reporting Config Section help article.The Shrink Font To Fit property of a text component is used when it is necessary to adjust the height of the text to the size of the text component. the user that is going to read that pdf should have Arial Unicode installed on his machine. ![]() ![]() ![]() Specifying the Subset option will embed only font glyphs that are used, thus reducing output file size while maintaining portability, while specifying None would not embed that font at all (i.e. This behavior however is controlled by the FontEmbedding device setting and can be changed to Subset or None. The problem occurs in the method that works without any changes for years. However note that Arial Unicode is around 23 Mb and by default the exported pdf file from the report would embed the whole font, so that it is readable on a machine that does not have it installed. The problem is about using non standard Persian fonts, fonts like Mitra, Nazanin, Yekan and others is not standard and in situations that we mix Persian and Latin characters or sometimes when using numbers, will show squares in PDF export. As far as we couldnt reproduce the issue and the problem occurs in Windows GDI we couldnt provide you the solution of the problem. stimulsoft20121203.zip updated report data & files (9.05 KiB) Downloaded 187 times. I hope this text makes my problems a little clearer and you will be able to help me solve my problem(s), I updated the report files. For example you can change the font you use to MS Arial Unicode font, which supports wide varieties of characters. I am new to the Stimulsoft support forum but I have been working with Stimulsoft Reports.Net for a little. This font should support all foreign characters you would be using in your report. The problem is most probably due to the font you have specified for the textbox items. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |