PowerTools for Open XML

New Post: Lost image after convert docx to html.

akshay904 — Thu, 09 May 2013 06:27:26 GMT

I am also facing same problem. Images are not converted while converting word document to HTML.

I can not use the (.DOC) file for conversion to HTML - Exception - File contains corrupted data.
So, I have to use the (.DOCX) files for conversion to HTML. Is this the limitation?
If file contains some images it is not correctly converted. If I Open the HTML file in browser.I can not see the images

Following code I am using -

public static void ConvertToHTMLUsingOpenXml(string fUpload, string htmlFile, string imagePath)

   {

       string sourceDocumentFileName = fUpload;

       string imageDirectoryName = Path.GetFileNameWithoutExtension(sourceDocumentFileName) + "_files";

       int imageCounter = 0;

       byte[] byteArray = File.ReadAllBytes(sourceDocumentFileName);

       using (MemoryStream memoryStream = new MemoryStream())

       {

           memoryStream.Write(byteArray, 0, byteArray.Length);

           WordprocessingDocument doc =

               WordprocessingDocument.Open(memoryStream, true);

           {

               HtmlConverterSettings settings = new HtmlConverterSettings()

               {

                   PageTitle = Path.GetFileNameWithoutExtension(sourceDocumentFileName),

                   ConvertFormatting = true,

               };

               XElement html = HtmlConverter.ConvertToHtml(doc, settings,

                   imageInfo =>

                   {

                       DirectoryInfo localDirInfo = new DirectoryInfo(imagePath + imageDirectoryName);//Server.MapPath(HTML_FILE_PATH + imageDirectoryName));

                       if (!localDirInfo.Exists)

                           localDirInfo.Create();

                       ++imageCounter;

                       string extension = imageInfo.ContentType.Split('/')[1].ToLower();

                       ImageFormat imageFormat = null;

                       if (extension == "png")

                       {

                           extension = "jpeg";

                           imageFormat = ImageFormat.Jpeg;

                       }

                       else if (extension == "bmp")

                           imageFormat = ImageFormat.Bmp;

                       else if (extension == "jpeg")

                           imageFormat = ImageFormat.Jpeg;

                       else if (extension == "tiff")

                           imageFormat = ImageFormat.Tiff;

                        if (imageFormat == null)

                           return null;

                        string imageFileName = imagePath+ imageDirectoryName + "\\image" + // Server.MapPath(HTML_FILE_PATH + imageDirectoryName) + "/image" +

                            imageCounter.ToString() + "." + extension;

                       try

                       {

                           imageInfo.Bitmap.Save(imageFileName, imageFormat);

                       }

                       catch (System.Runtime.InteropServices.ExternalException)

                       {

                           return null;

                       }

                       XElement img = new XElement(Xhtml.img,

                           new XAttribute(NoNamespace.src, imageFileName),

                           imageInfo.ImgStyleAttribute,

                           imageInfo.AltText != null ?

                               new XAttribute(NoNamespace.alt, imageInfo.AltText) : null);

                       return img;

                   });

               File.WriteAllText(htmlFile, html.ToString());

           }

           memoryStream.Close();

       }

   }

Updated Release: PowerTools for OpenXML 2.2 (Jan 22, 2012)

EricWhiteDpe — Tue, 07 May 2013 16:41:14 GMT

May 7, 2013 - Updated PresentationBuilder - fixed bug where it could create an invalid presentation.

January 14, 2013 - Added PresentationBuilder.

November 4, 2012 - Added spreadsheet formula example.

October 25, 2012 - Fixed some problems with the pivot table configuration and getting cell values.

April 29, 2012 - Added pivot table configuration of rows, columns, filters and data values.

April 23, 2012 - Updated spreadsheet cell styles with lots of options.

March 25, 2012 - New spreadsheet data generation with cell styles.

Feb 8, 2012 - Patched problem with PowerTools Core 2.2.2

Version 2.2 of the source code.

Oct 25, 2011 - added DocumentBuilder-2-0.zip. There is a minor bug fix to code that merges documents that contain numbered items.

Nov 9, 2011 - added Core code with examples of how to use from your own C# program.

Released: PowerTools for OpenXML 2.2 (Jan 22, 2012)

Tue, 07 May 2013 16:41:14 GMT

Updated Release: PowerTools for OpenXML 2.2 (Jan 22, 2012)

EricWhiteDpe — Tue, 07 May 2013 16:39:57 GMT

January 14, 2013 - Added PresentationBuilder.

November 4, 2012 - Added spreadsheet formula example.

October 25, 2012 - Fixed some problems with the pivot table configuration and getting cell values.

April 29, 2012 - Added pivot table configuration of rows, columns, filters and data values.

April 23, 2012 - Updated spreadsheet cell styles with lots of options.

March 25, 2012 - New spreadsheet data generation with cell styles.

Feb 8, 2012 - Patched problem with PowerTools Core 2.2.2

Version 2.2 of the source code.

Oct 25, 2011 - added DocumentBuilder-2-0.zip. There is a minor bug fix to code that merges documents that contain numbered items.

Nov 9, 2011 - added Core code with examples of how to use from your own C# program.

Updated Release: PowerTools for OpenXML 2.2 (Jan 22, 2012)

EricWhiteDpe — Tue, 07 May 2013 16:37:50 GMT

New Post: PowerTools 2.2 source code cannot be Referenced in another project

fenilrathod — Mon, 06 May 2013 12:18:47 GMT

Himanshu,

I am not sure but adding references to "DocumentFormat.OpenXml" and "WindowsBase" apart from OpenXmlPowerTools dll in your project can resolve your issue.

-- Fenil.

New Post: PowerTools 2.2 source code cannot be Referenced in another project

maverickht — Thu, 02 May 2013 12:02:44 GMT

Hi,
I'm trying to use the PowerTools 2.2 in my project, I need to use the MarkupSimplifier class as in Eric's blog post - http://ericwhite.com/blog/2011/03/09/getting-started-with-open-xml-powertools-markup-simplifier.

I’m using it with Visual Studio 2010 in the source code. I’ve included the PowerTools 2.2 project that I downloaded from codeplex to my solution and then added the reference to OpenXmlPowerTools in my project so I can use MarkupSimplifier.
When I try to debug the solution initially it loads fine but later gives an exception:

System.IO.FileNotFoundException was caught
Message=Could not load file or assembly ‘OpenXmlPowerTools, Version=2.2.0.0, Culture=neutral, PublicKeyToken=981466f262afc448′ or one of its dependencies. The system cannot find the file specified.
I’m really stumped, I’ve tried adding reference to only the OpenXmlPowerTools DLL but that doesn’t seem to work either and gives same message.

Also, I’m using Windows Server 2008 R2, and Sharepoint 2010 with Powershell 2.0

Not sure what might be causing the exceptions?
Please could someone help.

Many thanks
Himanshu

Created Issue: ArgumentNullException in RevisionAccepter [10961]

Jcoolsen — Thu, 02 May 2013 11:04:14 GMT

In RevisionAccepter in method AddBlockLevelContentControls the tools throws ArgumentNullException when there is a content control (sdt) without runs. There is this comment in the code that shows this to be a known issue:
// TODO - Need a slight modification here. If there is a paragraph
// in the content control that contains no runs, then because the paragraph isn't included in the
// content control, because the following triggers off of runs.
// To see an example of this, see example document "NumberingParagraphPropertiesChange.docxs"

I report it here anyway because I found no existing issue with this information. My workaround is to insert this line:

if (runsInNewDocument.Count==0) continue;

just after the line "var runsInNewDocument = ..."
It is most certainly not an entirely correct solution, but it makes the tools not break in this case.

I hope this helps someone until the problem is fixed properly.

The whole class of the RevisionAccepter seems overly complex to me. I find the process of tagging and copying content hard to grasp and I suspect it could have been done much simpler.

Thanks.

New Post: Multiple OleObjects (Linked Objects) are not getting merged properly using DocumentBuilder

fenilrathod — Wed, 24 Apr 2013 12:02:00 GMT

Hi Eric,

I've just resolve the issue by making the unique ids for all the shape, shapeTypes and objects associates with each other. And this simple solution have resolve my issue. Below is the code, Let me know if anything is unusual.

 private static void FixUpEmbeddedObjectIds(WordprocessingDocument outputWPDocument)
 {
     foreach (EmbeddedObject obj in outputWPDocument.MainDocumentPart.Document.Descendants<EmbeddedObject>())
     {
         var shapeType = obj.Descendants<DocumentFormat.OpenXml.Vml.Shapetype>().FirstOrDefault();
         var shape = obj.Descendants<DocumentFormat.OpenXml.Vml.Shape>().FirstOrDefault();
         var oleObject = obj.Descendants<OleObject>().FirstOrDefault();

         if (shapeType != null && shape != null)
         {
             shapeType.Id = Guid.NewGuid().ToString();
             shape.Type = shapeType.Id;
         }
         if (shape != null && oleObject != null)
         {
             shape.Id = Guid.NewGuid().ToString();
             oleObject.ShapeId = shape.Id;
         }
     }
 }

Cheers,
Fenil.

New Post: Multiple OleObjects (Linked Objects) are not getting merged properly using DocumentBuilder

EricWhiteDpe — Fri, 12 Apr 2013 19:46:31 GMT

In DocumentBuilder, you will find a class that it uses to prevent duplication of images. The correct approach is to make a variation of that class that prevents duplication of the OleObject. The code will be almost identical. It could be possible to modify the class to prevent image duplication so that it prevents duplication of multiple types of things, i.e. images and OleObjects, but it is a small class and it is probably more effort that it is worth. I would probably just create a new class that is nearly identical to that one.

Cheers, Eric

New Post: Multiple OleObjects (Linked Objects) are not getting merged properly using DocumentBuilder

fenilrathod — Fri, 12 Apr 2013 17:38:16 GMT

Thanks again for your quick response.

Today, After investigating further I found that during merging, OleObjects getting duplicated with same id with duplicated shape and shapetypes as well. Probably that could be an issue.

I'll look into it further and will try to solve it if possible.

If you can provide any suggestions it will be helpful.

Thanks again for your time.

Regards,
Fenil.

New Post: Multiple OleObjects (Linked Objects) are not getting merged properly using DocumentBuilder

EricWhiteDpe — Fri, 12 Apr 2013 17:03:17 GMT

I haven't done the analysis of what would be required to support OleObjects. There probably should be some check to make sure that the same OleObject isn't duplicated in the destination document. Then to test a number of scenarios, making sure all bases are covered.

It will be some time before I can get to this. I am over-booked for the next 2 1/2 months.

I do have PowerTools on my agenda, and that includes some important enhancements to DocumentBuilder.

Cheers, Eric

New Post: Multiple OleObjects (Linked Objects) are not getting merged properly using DocumentBuilder

fenilrathod — Fri, 12 Apr 2013 13:16:16 GMT

Thanks Eric for the response.

I guess DocumentBuilder supporting OleObjects and I've successfully able to merge OleObjects(Linked Objects, e.g, Excel file) if they are in only one source document.

But as soon as multiple documents have OleObjects, after merging they links of OleObjects are getting broken apart from the first OleObject in the document. If possible I could share demo application for this issue.

Regards,
Fenil.

New Post: Multiple OleObjects (Linked Objects) are not getting merged properly using DocumentBuilder

EricWhiteDpe — Fri, 12 Apr 2013 09:51:56 GMT

Hi Fenil,

That is an issue with DocumentBuilder. Currently it does not support merging documents that reference OleObjects. It is a great idea for a future enhancement.

Regards, Eric

New Post: Multiple OleObjects (Linked Objects) are not getting merged properly using DocumentBuilder

fenilrathod — Fri, 12 Apr 2013 07:42:23 GMT

Hi,

I'm getting issues during merging multiple documents having OleObjects (Linked Objects) having external relationships to files using DocumentBuilder.

You can reproduce this issue by having multiple linked objects in it and try to merge them using DocumentBuilder.

As a result you will have a merged document with OleObjects with broken external relationship and you will no longer able to update those objects by clicking them.

I just want to know if this is the issue with DocumentBuilder or I am doing something wrong?

Fenil.

Commented Issue: Style numbering disappear after merge [10590]

HomerSimpian — Fri, 08 Mar 2013 22:00:09 GMT

I have word document X.docx. I get a list of elements from it and try to insert to another document Y.docx via powertools DocumentBuilder.BuildDocument. In case I apply style to paragraph (X.docx) which contain numbering in StyleDefinitionsPart, after merging I lose all numbering in resulting document.
Document.xml

-

-
When is necessary to use … ?

–
Style.xml

. . .

-

-

In result I get document where style referring to numId , but there no element w:num with this numId in NumberingPart

DocumentBuilder.BuildDocument
1) void CopyStartingParts (…)
{…
// Note: Do not copy the numbering part. For every source, create new numbering definitions from
// scratch.
//NumberingDefinitionsPart numberingPart = sourceDocument.MainDocumentPart.NumberingDefinitionsPart;
}
Why?
2) CopyNumbering(…)
{
foreach (XElement numReference in newContent.DescendantsAndSelf(W.numPr))
but it doesn’t take into account the numbering in StyleDefinitionsPart
}
Comments: ** Comment from web user: HomerSimpian **

For whatever it is worth, I have found that for my purposes and with the documents I am merging, I needed to re-instate the commented out code at line 1721 or so in DocumentBuilder.cs. I'm not saying this is a fix for everyone, as there must be a valid reason it was commented out to begin with. That said, it does appear to fix my problems by re-adding it in.

Without it, I am missing the numbering.xml entirely and my styles are no longer 'valid'. The headings become bullets or nothing at times. Hope this bit helps.

Commented Issue: Style numbering disappear after merge [10590]

HomerSimpian — Fri, 08 Mar 2013 22:00:07 GMT

Without it, I am missing the numbering.xml entirely and my styles are no longer 'valid'. The headings become bullets or nothing at times. Hope this bit helps.

New Post: Change to allow a partial importation of KeepSection

marc_al — Thu, 28 Feb 2013 07:41:59 GMT

Hello,

I have tried to merge some documents but by keeping the informations of the first document. So, when I added a source for the first document I had to add True to KeepSection. For the other documents as I needed to keep the header and footer of the first document I had to put False. The problem was that a custom margin was only allowed for the content of the first document and the other documents had lost the custom margins.
I have made the following change (in case someone is interested :
In the file
DocumentBuilder.cs
Function BuildDocument
In the end of the function there is

else

FixUpSectionProperties(output);

I have put the two lines in comment so the new code is

//else

            //    FixUpSectionProperties(output);

the end of the function looks like that

if (!sources.Any(s => s.KeepSections))

            {
                using (OpenXmlMemoryStreamDocument streamDoc = new OpenXmlMemoryStreamDocument(sources[0].WmlDocument))
                using (WordprocessingDocument doc = streamDoc.GetWordprocessingDocument())
                {
                    var sectPr = doc.MainDocumentPart.GetXDocument().Root.Element(W.body)
                        .Elements().Last();
                    if (sectPr.Name == W.sectPr)
                    {
                        AddSectionAndDependencies(doc, output, sectPr, images);
                        output.MainDocumentPart.GetXDocument().Root.Element(W.body).Add(sectPr);
                    }
                }
            }
            //else
            //    FixUpSectionProperties(output);
        }
        foreach (var part in output.GetAllParts())
            if (part.Annotation<XDocument>() != null)
                part.PutXDocument();
    }

With this change I can keep the header / footer / margins of the first documents without losing parameters from the other ones.

Marc

Commented Issue: Style numbering disappear after merge [10590]

HomerSimpian — Sat, 23 Feb 2013 21:21:49 GMT

I'm seeing the same issue as dadawley before wrote. The loss of the multilevel numbering is crucial when applied to heading styles! I don't know if I have time to look closely at this, but this is very much a setback for my use.

Commented Issue: DocumentBuilder doesn't work properly with Bookmarks at the end [10762]

EricWhiteDpe — Mon, 21 Jan 2013 15:33:30 GMT

If you concatenate 2 files with the DocumentBuilder and the first document has a `w:bookmarStart` and `w:bookmarkEnd` tag between the final paragraph and the document end `w:sectPr`, the resulting document won't be correct. The first paragraph of the the second document will be part of the first document. The markup then looks like this:
```
w:p
whatever the content
w:p/
w:bookmarkStart/
w:bookmarkEnd
w:pPr
w:sectPr/
w:pPr/
w:bookmarkEnd/
```
It seems that the document end `w:sectPr` is added (along with an additional `w:pPr`) to the tag before it, whatever that tag is. It should be added to the last `w:p` before it.

Sorry, you'll have to think the brackets for yourselves. The issue tracker swallowed them along with their content even though they were formatted as code
Comments: ** Comment from web user: EricWhiteDpe **

Hi, I am pretty sure about what the issue is, and that I can fix it. I'll take a look as soon as I am available to do so.

-Eric