but it
works on the previous example.
It's not the case with my real data but it's another problem to solve now
;).
Thanks a lot for your help
Best regards
Roland.
Andreas Röhler easy-emacs.de> writes:
>
> Am 08.05.2013 22:50, schrieb Roland Donat:
> >>> Yes, you're right Andreas. It "fails" to show the accented characters
if
> > you
> >>> try to print the entire tuple.
> >>> It fail
r,
> > that is :
> > | \xc3\xa9 | a |
> > | a| '\xc3\xa0' |
> >
> > In addition, when I try to save my buffer, Emacs doesn't recognize the
> > encoding of characters \303\251 and \303\240 and asks me to choose an
> > enco
Andreas Röhler easy-emacs.de> writes:
>
> Am 08.05.2013 15:20, schrieb Roland Donat:
> >
> >>
> >> hmm, indeed, shows up nicely now.
> >> Please close, cheers,
> >>
> >> Andreas
> >>
> >>
> >
> > Th
>
> hmm, indeed, shows up nicely now.
> Please close, cheers,
>
> Andreas
>
>
That's right, it works with python3 but that is not the case with python2...
Cheers,
Roland.
el builds a table from a Python list
of lists but I have to confess that I'm afraid of reading Lisp programs,
though Emacs is my best friend ;)...
Well, I'll keep on investigating on that subject
Thanks again for your help!
Roland.
rc
#+RESULTS: test2
| \303\251 | a|
| a| \303\240 |
I don't understand why the accented characters are replaced by some codes
when the results is interpreted as org-table...
Any idea, workaround to solve my problem would be much appreciated!
I use Org-mode version 8.0.2 (8.0.2-
On Sun Feb 10 2013 Bastien wrote:
> Please provide a patch.
I'd much appreciate if the org developers could do that. I have
enough such things on my own emacs agenda,
On Sun Feb 10 2013 Bastien wrote:
> > Why put this in a separate FAQ? Aren't the info pages the first
> > source of information for such things?
>
> Depends. We try to keep the info manual readable, and it's already
> quite long. If you can find a good place in the manual, please send
> a patch.
on structural markup
> > elements does not mention such a possibility.
>
> Mhh.. yes, I'll perhaps update the manual, or just add a Worg
> FAQ for this.
Why put this in a separate FAQ? Aren't the info pages the first
source of information for such things?
Roland
time.
Regards,
Roland.
2011/10/5 Nicolas Goaziou
> Hello,
>
> Roland writes:
>
> > Hello again,
> >
> > I just add some complements to the problem.
> >
> > First, here is a more compact buffer to reproduce the bug :
> >
> > == Cut here begin
Hello again,
I just add some complements to the problem.
First, here is a more compact buffer to reproduce the bug :
== Cut here begin ==
# -*- coding: utf-8 -*-
#+TITLE: Title
#+AUTHOR: Roland
#+OPTIONS: H:3 num:t toc:nil \n:nil @:t ::t |:t ^:{} f:t TeX:t author:t
#+LaTeX_CLASS: article
Hello everyone,
I am experience a very strange problem so that any help would be
appreciated!
I precise that I use org-mode 7.7 on Linux/Debian.
I tried to perform latex export of the following org file :
=== cut here begin ===
# -*- coding: utf-8 -*-
#+TITLE: Title
#+AUTHOR: Roland
#+OPTIONS
rface, I'd find it
unfortunate if such a feature was lost in org-mode to preserve
backward compatibility.
Roland
On Sun May 15 2011 Roland Winkler wrote:
> It would probably be good if the needs of org-mode could be
> incorporated into the new BBDB before we declare that BBDB v3 has
> reached a beta stage.)
I forgot to say:
It is an item on the todo list for BBDB v3 to provide a more complete
lis
v2 are already incorporated into v3 in one
or the other way. It would probably be good if the needs of org-mode
could be incorporated into the new BBDB before we declare that BBDB
v3 has reached a beta stage.)
Roland
. The patch which is listed there should *not* be applied. A
second and corrected patch was attached in the last message, but it
seems to not have been picked up by the framework.
How do I replace the patch above with the code from:
<http://patchwork.newartisans.com/patch/802/>
--
Roland.
ree as of revision 62d4dd,
but the problem still remains.
I am grateful for feedback on its lackings, if the patch is deemed
unsatisfactory in any way. In case it simply got lost amidst all the
other traffic, I resubmit it, updated so it applies to the current revision.
--
Roland.
trick. (This supersedes the previous patch against
htmlize.el).
Thanks to Hrvoje for suggesting this approach and providing the code
to reset the face attribute.
--
Roland.
0001-Markup-on-same-line-as-text.patch
Description: Binary data
___
Emacs-o
(i.e. proposal for
change in htmlize dropped). Thank you for the feedback!
--
Roland.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
42)) ; meaning of l.u.e.
(print x)) ; (ref:2)
#+END_SRC")
(save-buffer)
(org-mode)
(org-export-as-html nil))
--
Roland.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
I have tested this with all three kinds of htmlize-output-type, and it
seems to give the expected result.
--
Roland.
>From 86f1508f58dd304471d768481944d34e220e24f1 Mon Sep 17 00:00:00 2001
From: Roland Kaufmann
Date: Thu, 6 Jan 2011 11:22:49 +0100
Subject: [PATCH] Markup on same line as tex
101 - 122 of 122 matches
Mail list logo
