Free Support Forum -

Unhandeled exception while setting font name

There is a problem using the TextFontName in the FormField control of type Text. If I write the following piece of code:

textBox.TextFontName = "Arial,Bold";

I will get an unhandeled exception which states: Font 'Arial,Bold' with 'windows-1252' is not recognized.

Is there a workaround?

Also I have problems setting the position of the form elmement of type text after a regular text element. In addition when I set the form text element to multiline only one line shows in center until you click on it, then the rest of the lines show.

Any help appreciated.

This is the call stack:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ApplicationException: Font 'Arial,Bold' with 'windows-1252' is not recognized.
at ࢷ.എ.ൖ(String ࢨ, String ਞ, Boolean ൌ, Boolean ൗ, Byte[] ൘, Byte[] ൙)
at ග.ᐶ.ᐷ(ૺ ࣢, ୁ ࿔)
at ࢚.ᐯ.ᐴ(ૺ ࣢)
at ࢚.ጠ.କ(ૺ ࣢)
at ྛ.᜴.᜵(ྪ ྡ, Pdf _ᖩ, ऌ ख़, Boolean ᜶)
at ྛ.ᡣ.ᡤ(ྪ ྡ, Pdf _ᖩ)
at ྛ.ሏ.ሔ(ྪ ྡ, Pdf ሕ)
at Aspose.Pdf.Pdf.Save(String pdfFile)
at PdfTest.Form1.button3_Click(Object sender, EventArgs e) in c:\documents and settings\kks\my documents\my projects\pdftest\form1.cs:line 208
at System.Windows.Forms.Control.OnClick(EventArgs e)

************** Loaded Assemblies **************
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/
Assembly Version: 1.0.2340.27786
Win32 Version: 1.0.2340.27786
CodeBase: file:///C:/Documents%20and%20Settings/kks/My%20Documents/My%20Projects/PdfTest/bin/Debug/PdfTest.exe

In the current version Bold and Italic font is not supported. As a workaround, please don't use bold font. Our developers will check this issue and tell you when we can support Bold and Italic.

The problem is still there. The same happens when I don't use bold. Like this:

textBox.TextFontName = "Arial";

Could u provide the segment codes that can reproduce the same error?

I have reproduced this error. We will fix this bug ASAP.