Hi Paul, First, I was glad to finally meet you in person at Berlin semtech, and I enjoyed your talk there.
We have been looking into this issue. We've identified it as a bug in the sml:ExportToTextFile module and entered it into our Bug Tracker system. We are planning on fixing it but currently have no estimated date for completing the fix. For now, as you saw, you can count on sml:ExportToXMLFile to pass along the content in the UTF-8 encoding, although as you also saw it's not as quick as sml:ExportToTextFile because it validates the XML before writing it to disk. Bob DuCharme TopQuadrant On Mon, Feb 20, 2012 at 7:57 AM, PaulZH <[email protected]> wrote: > Context: TBCME Version: 3.5.4.v20120206-0955R > MS-Windows 7 > > I recently changed following SPARLMOTION script > > 1) read RDF/XML (UTF-8) from file system > 2) XSLT Transform 1 to XML > 3) XSLT Transform 2 to XHTML > 4) save to file system as XML (sml:ExportToXMLFile) as {label}.html > > to > > 4) save to file system as text (sml:ExportToTextFile) as {label}.html > > This has been done due to performance reasons. > See > http://groups.google.com/group/topbraid-users/browse_thread/thread/9aad79e068afc198/87c0fd2a27d201d5?lnk=gst&q=paulzh#87c0fd2a27d201d5 > > However although: > - the XSLT contains <xsl:output indent="yes" encoding="UTF-8" > method="xhtml"/> > - the generated XHTML contains <meta http-equiv="Content-Type" > content="application/xhtml+xml; charset=utf-8"/> > - the folder in which the output is generated has in the eclipse > properties view, text file encoding UTF-8 > - the eclipse preference for html files has been set to UTF-8 > > the generated HTML file is NOT UTF-8 and generates well-formdness > errors. > IOException-Got a character coding exception. > To ignore these errors or to replace invalid characters > please change in preferences the "Encoding errors handling" > from REPORT to IGNORE or REPLACE. > UTF8 - java.nio.charset.MalformedInputException [Input length = 1] > > Additional input: > - Running the stylesheets outside TBCME generate the output as aimed. > - replacing > step 3 with XSLT Transform 2 to XML (not XHTML) > step 4 with save to file system as text (sml:ExportToTextFile) > as {label}.xml doesn't give the encoding issue. > - changing in Firefox the encoding from UTF-8 to Western (ISO-8859-1) > gives the correct characters. > > Any idea how to get the correct encoding? > > > > -- > You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include Enterprise > Vocabulary Network (EVN), TopBraid Composer, > TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. > To post to this group, send email to > [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/topbraid-users?hl=en > -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
