Word to PDF error: Requested default value for an unknown attribute


#1

WORDSNET-16295 has not been solved yet.
Calling the latest aspose. Words. DLL - 18.9.0 will throw the exception “Requested default value for an unknown attribute”


Urgent Help: 8 Problems in our application
#2

@PowerHu,

Thanks for your inquiry. Please ZIP and upload your input Word document and piece of source code here for testing. We will then investigate the issue on our end and provide you more information.


#3

16KP_01pcs.zip (111.3 KB)
EX4TK1C3.zip (1.0 MB)
It will be thow the exception: Requested default value for an unknown attribute when 16KP_01pcs.doc covert pdf format.

word to pdf : the code as bellow.
Aspose.Words.Document doc = new Aspose.Words.Document(sourcePath);

doc.Save(targetPath, Aspose.Words.SaveFormat.Pdf);

It will be show the exception: Shape to image Error when convert EX4TK1C3.xlsx to pdf format.

excel to pdf :sample code as bellow

Aspose.Cells.Workbook wb = new Aspose.Cells.Workbook(sourcePath);

wb.Save(targetPath, Aspose.Cells.SaveFormat.Pdf);


#4

@PowerHu,

Thanks for your inquiry. We tested the scenarios and have managed to reproduce the same problems on our end. For the sake of correction, we have logged the following issues in our issue tracking system.

WORDSNET-17430: System.InvalidOperationException occurs during rendering DOC to PDF (related to 16KP_01pcs.doc)

CELLSNET-46331: Exception “Shape to image Error” when converting an XLSX file to PDF file format (related to EX4TK1C3.xlsx)

We will further look into the details of these problems and will keep you updated on the status of these issues. We apologize for your inconvenience.


#5

@PowerHu,

This is to inform you that we have fixed your issue (logged earlier as “CELLSNET-46331”) now. We will soon provide you the fixed version after performing QA and incorporating other enhancements and fixes.


#6

The issues you have found earlier (filed as CELLSNET-46331) have been fixed in Aspose.Cells for .NET v18.9. This message was posted using BugNotificationTool from Downloads module by Amjad_Sahi


#7

It had been fixed exception "shape to image error " when converting an XLSX filt to pdf .There are some different original documents after converting pdf,when we used the Aspose.cells for .NEt v18.9. please reference the CELLSNET-46331.png.CELLSNET-46331.png (373.2 KB)EX4TK1C3.xlsx.pdf (264.0 KB)


#8

@PowerHu,

We were able to observe the issue but we need to look into it more. We have logged the issue in our database for investigation and for a fix. Once, we will have some news for you, we will update you in this topic.

This issue has been logged as

CELLSNET-46348 - Differences when converting an XLSX file to PDF

#9

The issues you have found earlier (filed as WORDSNET-17430) have been fixed in this Aspose.Words for .NET 18.10 update and this Aspose.Words for Java 18.10 update.


#10

It had been fixed exception "Requested default value " when converting an word file to pdf .There are some different original documents after converting pdf,when we used the Aspose.words for .NEt v18.10. please reference the png file.16KP_01pcs.doc.pdf (401.9 KB)
WordSNET-17430.png (323.6 KB)


#11

@PowerHu,

While using the latest version of Aspose.Words i.e. 18.10, we managed to reproduce this issue on our end. We have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-17583. Your thread has been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.


#12

@PowerHu,

Regarding WORDSNET-17583, please run the following code on your machine and provide console output and resulting image.

using (Bitmap bmp = new Bitmap(1000, 100))
{
    using (Graphics gr = Graphics.FromImage(bmp))
    {
        Font fnt = new Font("DFKai-SB", 100, FontStyle.Regular);
        Console.WriteLine(fnt.FontFamily.Name);
        using (GraphicsPath path = new GraphicsPath())
        {
            path.AddString("環球旅行第五十五期", fnt.FontFamily, (int) FontStyle.Regular, 100, PointF.Empty, StringFormat.GenericTypographic);
            gr.FillPath(new SolidBrush(Color.Black), path);
        }
        bmp.Save("out.png");
    }
}

#13

The console output is “標楷體”, and please check the resulting image .
out.png (2.7 KB)


#14

@PowerHu,

Thanks for the details. We will keep you posted on any further updates.


#15

@PowerHu,

It seems that we have identified the problem. Aspose.Words currently searches the font family by English name but on your machine, FontFamily.Name seems to be returning the localized name.

Please also run the following code and provide the console output.

Font fnt = new Font("DFKai-SB", 100, FontStyle.Regular);
Console.WriteLine(fnt.FontFamily.GetName(0));
Console.WriteLine(fnt.FontFamily.GetName(new CultureInfo("en-US").LCID));

#16

The console output is as bellow.out.png (2.7 KB)


#17

@PowerHu,

It seems that you have again attached the same out.png that you attached earlier in your this post.

Please execute the following code and provide the output shown in visual studio’s console.

Font fnt = new Font("DFKai-SB", 100, FontStyle.Regular);
Console.WriteLine(fnt.FontFamily.GetName(0));
Console.WriteLine(fnt.FontFamily.GetName(new CultureInfo("en-US").LCID));

#18

I am sorry for upload the old output . I have upload the new output .outputex.png (460 Bytes)


#19

@PowerHu,

Thanks for the details. We will keep you posted on any further updates.


#20

The issues you have found earlier (filed as WORDSNET-17583) have been fixed in this Aspose.Words for .NET 18.11 update and this Aspose.Words for Java 18.11 update.