On Thursday, May 29, 2014 6:40:19 AM UTC+3, george thomas wrote: > > > > On Wednesday, May 28, 2014 8:13:07 PM UTC-4, Lex Trotman wrote: >> >> On 29 May 2014 03:49, george thomas <[email protected]> wrote: >> > >> > >> > I encountered the originally reported problem a few days ago with >> asciidoc >> > 8.6.9 with Python 2.7.6 on 64-bit Windows 7 SP1. The problem arises >> from a >> > change that was submitted to fix a problem with MIME types for SVG when >> > using data-uri. >> > >> > The thread for the problem with MIME types for SVG: >> > https://groups.google.com/forum/#!topic/asciidoc/29-vg4-T4CA >> > The accepted change for this problem: http://bit.ly/1pycQRy >> > >> > The call to print fouls things up on Windows: The output of print is >> > displayed on the terminal and the process of generating the content for >> > data-uri hangs. What is clearly expected is that the mime header >> created by >> > the call to print and the base64-encoded image data be written to a >> > temporary file before being written to the output document as the >> content of >> > the img element's source attribute. >> > >> > For what it's worth, when I used Ctrl+C on the hung process on Windows >> I saw >> > the following traceback: >> > >> > Traceback (most recent call last): >> > File "<string>", line 1, in <module> >> > File "C:\Python27\lib\base64.py", line 288, in encode >> > s = input.read(MAXBINSIZE) >> > KeyboardInterrupt >> > >> > I wish I knew enough to recommend an alternative that would work on >> both >> > Linux and Windows. >> >> Did you try the \x22 suggestion? >> >> Cheers >> Lex >> > > I really should have. I think I didn't quite see how it would help. I was > wrong. I just changed print 'src=\"data to print 'src=\x22data in the > "shelled" command and the command ran successfully, generating a temporary > file containing the content to be added as the value of the img element's > src attribute. > > On a whim, I tried this on Linux as well and things worked there as well. > > Would this make \x22 an acceptable change that will work everywhere just > as it has on both Windows and Linux? >
I encountered the same symptoms (running asciidoc on windows with data-uri enabled hangs) today. If this is the solution indeed, any specific reasons it has not been committed? -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
