El Fri, 04 Jul 2014 16:08:10 +0200 Alan Schmitt va escriure:
>
> On 2014-06-26 18:07, Daniel Clemente writes:
>
> >>
> >> #+BEGIN_SRC python :prefix # -*- coding: utf-8 -*- :results output
> >> print(u'é')
> >> #+END_SRC
> >>
> >
> > I also see the same problem here. Even if you include # -
On 2014-06-26 18:07, Daniel Clemente writes:
>>
>> #+BEGIN_SRC python :prefix # -*- coding: utf-8 -*- :results output
>> print(u'é')
>> #+END_SRC
>>
>
> I also see the same problem here. Even if you include # -*- coding: utf-8
> -*-as the first line.
>
> Shouldn't org-babel already be us
>
> #+BEGIN_SRC python :prefix # -*- coding: utf-8 -*- :results output
> print(u'é')
> #+END_SRC
>
I also see the same problem here. Even if you include # -*- coding: utf-8 -*-
as the first line.
Shouldn't org-babel already be using utf-8 instead of ASCII for input/output?
By the way, w
On 2014-06-26 09:35, Alan Schmitt writes:
> #+BEGIN_SRC python :prefix # -*- coding: utf-8 -*- :results output
> print(u'∀')
> #+END_SRC
I see that somewhere the email did not get through, the character above
is a "forall" character. I have the same problem with a simpler accent
#+BEGIN_SRC pyt
Hello,
I'm having trouble with the babel evaluation of python blocks containing
utf-8 encoded characters (which is the encoding of my org file).
I tried the approach suggested in this message
https://lists.gnu.org/archive/html/emacs-orgmode/2010-12/msg00086.html
in the following block
#+BEGIN_SR
