emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Roland DONAT <roland.donat@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-babel, python, encoding and table
Date: Wed, 29 May 2013 12:18:33 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130529T141634-491@post.gmane.org> (raw)
In-Reply-To: 518A0E9E.7070309@easy-emacs.de

Andreas Röhler <andreas.roehler <at> easy-emacs.de> writes:

> 
> Am 07.05.2013 18:41, schrieb Eric Schulte:
> >> #+NAME: test2
> >> #+begin_src python :results value :preamble # -*- coding: utf-8 -*- 
:return
> >> a
> >> a = ( ( "é", "a" ), ( "a", "à" ) )
> >> b = "é"
> >> #+end_src
> >>
> >> #+RESULTS: test2
> >> | \303\251 | a        |
> >> | a        | \303\240 |
> >>
> >
> > Maybe this isn't an execution problem, but is rather a buffer encoding
> > problem.  I executed your example above in a small buffer (attached).  I
> > then saved this buffer and was forced to specify an encoding, I selected
> > utf8.  If I cat the resulting file from disk, the accented characters
> > appear correctly.
> >
> 
> Confirming this.
> 
> BTW also return a[0][0] displays correct so far.
> 
> Cheers,
> 
> Andreas
> 
> 

Hello,

Just an update about this post.

I've kept on digging on the problem of org-babel python results that 
produces encoding problems in
the emacs buffer when the requested results is turned into a org table.

To remind and illustrate the problem, here is an example :
#+name: pytab-test
#+begin_src python :results value :session :preamble # -*- coding: utf-8 -*- 
:return a
a = ( ( "é", "a" ), ( "a", "à" ) )
a
#+end_src

#+TBLNAME: pytab-test
| \303\251 | a        |
| a        | \303\240 |


I have then two problems :
1. The characters are not well displayed in the buffer
2. If I try to save the buffer, emacs doesn't recognize the encoding and 
tells me that "utf-8-unix cannot encode these: \303 \251 [...]

So I decided to inspect what happened during the Python session...
Basically, Org-babel just write the str conversion of my tuple ( ( "é", "a" 
), ( "a", "à" ) ) (that appears (('\xc3\xa9',
'a'), ('a', '\xc3\xa0')) in the python interpreter) in a temporary file.

Then looking in this temporary file, I see that the strange characters are 
written directly \xc3, \xa9, etc.

Consequently, my guess is that org-babel has maybe some difficulties to deal 
with these characters
while reading the temporary file before displaying the results in the 
buffer. 

Unfortunately, this is just a guess and even less a solution... But am I on 
relevant lead???

Thanks in advance for any help...

Roland.

  reply	other threads:[~2013-05-29 12:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 12:55 org-babel, python, encoding and table Roland Donat
2013-05-07 16:41 ` Eric Schulte
2013-05-07 17:34   ` Andreas Röhler
2013-05-07 18:18     ` Eric Schulte
2013-05-07 18:45       ` Andreas Röhler
2013-05-07 19:20         ` Nick Dokos
2013-05-07 19:40           ` Andreas Röhler
2013-05-07 20:05             ` Nick Dokos
2013-05-08  6:21               ` Andreas Röhler
2013-05-07 19:44           ` Roland Donat
2013-05-07 19:52             ` Andreas Röhler
2013-05-08  8:36   ` Andreas Röhler
2013-05-29 12:18     ` Roland DONAT [this message]
2013-05-29 13:00       ` Eric Schulte
2013-05-29 23:54         ` Christian Wittern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20130529T141634-491@post.gmane.org \
    --to=roland.donat@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).