![]() CSS language states that readers (visual agents) must ignore any unknown constructions if only they have valid general syntax. Strictly speaking non-standard CSS attributes should not be a problem. But section breaks and column breaks probably need more than just Boolean options. I agree with you that Microsoft specific "magic" should be optional in HTML and disabled by default. By default all these options are disabled. In other cases we provide options, for instance SaveOptions.HtmlExportDocumentProperties, to enable some "magic". In some cases we cannot roundtrip features without huge "magic" overhead and simply sacrifice roundtrip to HTML purity. Our general policy is to avoid Microsoft "magic" wherever possible. ![]() Of course we cannot roundtrip every feature but such things are always in focus.Īnother issue you pointed is using Microsoft Word specific attributes such as mso-break-type and mso-column-break-before to export section breaks and column breaks. But since Aspose.Words is primarily oriented to processing Microsoft Word documents we need to think about bidirectional roundtrip with this application. This construction can be considered for export and import. Page-break-before:always clear:both mso-break-type:section-break"> First of all, sections are represented in output HTML as In rare cases people would like to replace line breaks with paragraph starts or suppress page breaks. Page break is also good since it occurs insideĪnd doesn’t have any Microsoft specific attributes. This is pretty legal even in strict XHTML and must be well understood by all visual agents. There are four types of breaks we need to export:įirst two of them are fully compliant in both Aspose.Words and Microsoft Word HTML export. Let’s consider problems we meet and think about possible solutions. ![]() Please note that HTML output with SaveOptions.HtmlExportXhtmlTransitional is transitional but not strict XHTML. Especially this is needed when exporting to IDPF EPUB format. We usually pay attention to XHTML compliance and other compatibility issues. Here are some considerations regarding the issue with section breaks. I’m Viktor, the developer responsible for HTML export. Thank you for your thoughtful post and your patience.
0 Comments
Leave a Reply. |